Method for displaying real-time status of application, and electronic device

Abstract

The present application relates to a method for displaying a real-time status of an application, and an electronic device. The method may be applied to a first electronic device, the first electronic device may be configured to initiate a first task of an application, and the first task may comprise at least two nodes. The method may comprise: acquiring a real-time status of each node among at least two nodes; and in response to each acquisition of the real-time status of one of the at least two nodes, executing the following steps: on the basis of the real-time status of a current node, obtaining a real-time status image of the current node; and displaying the real-time status image of the current node, wherein the real-time status image of the current node comprises a theme element and a status element, the status element corresponding to the real-time status of the current node, and theme elements in real-time status images of nodes among the at least two nodes being the same. On the basis of the technical solution, by displaying real-time status images containing identical theme elements, the electronic device can enhance visual appeal and help increase user retention.

Description

Methods and electronic devices for displaying the real-time status of applications

[0001] This application claims priority to Chinese Patent Application No. 202510241771.8, filed on February 28, 2025, entitled "Method and Electronic Device for Displaying Real-Time Status", and Chinese Patent Application No. 202510733697.1, filed on May 30, 2025, entitled "Method and Electronic Device for Displaying Real-Time Status of an Application", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to the field of electronic device technology, and in particular to a method and electronic device for displaying the real-time status of an application (APP). Background Technology

[0003] Currently, in the process of electronic devices responding to user-initiated actions, the real-time status of each application node is displayed through capsule-shaped or card-shaped windows, resulting in a relatively homogeneous experience that cannot further improve the user experience. Summary of the Invention

[0004] This application provides a method and electronic device for displaying the real-time status of an application to further improve the user experience.

[0005] In a first aspect, embodiments of this application provide a method for displaying the real-time status of an application, applicable to a first electronic device. This first electronic device initiates a first task of the application, which may include at least two nodes. The method may include:

[0006] Obtain the real-time status of each node in at least two nodes;

[0007] In response to acquiring the real-time status of at least one of the two nodes, the following steps can be performed:

[0008] Obtain the real-time status image of the current node based on its real-time status.

[0009] Displays the real-time status image of the current node. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node.

[0010] Among them, the subject elements in the real-time status images of at least two nodes are the same.

[0011] For example, the theme elements may or may not be related to the primary task.

[0012] For example, a task can be a real-time activity, which can be an ongoing task or activity that the user is focused on, such as hailing a ride, booking tickets, taking a flight / high-speed rail, or queuing. The real-time state can be the status of the real-time activity. A task can contain a series of nodes, such as at least two nodes, generated to achieve the task's goal (e.g., the goal of a food delivery task is for the user to receive the food, the goal of a ride-hailing task is to hail a ride, etc.). The nodes contained in a task are the core elements constituting the task flow, representing specific operations, decision points, or state transitions within the task flow. This series of nodes can be generated sequentially; for example, with food delivery, when a user places an order through a food delivery app, the initiated task includes five nodes: payment, order acceptance, pickup, delivery, and receipt. For example, a task can be created or initiated through different applications; for example, a food delivery task can be initiated through user operations. APP Initiated by apps, etc. Real-time status messages can be messages that contain real-time status information. For example, a message can contain format fields, data fields, etc. The content of the data fields can be status information corresponding to the real-time status, such as "Payment", "Pending payment of x yuan", "Estimated delivery in y minutes", etc.

[0013] Based on the above technical solution, electronic devices can increase visual appeal and avoid experience homogenization by displaying real-time status images containing the same theme elements. Furthermore, the real-time status of different nodes can continuously attract users' attention by presenting images containing the same theme elements, which helps to increase user stickiness.

[0014] In one possible implementation, the theme elements in the real-time status image of the current node are the same as the interface theme elements of the first electronic device. The interface theme elements are user-specified theme elements that are displayed on any one or a combination of the lock screen, unlock screen, or screen-off screen.

[0015] In one possible implementation, displaying the real-time status image of the current node may include displaying the real-time status image of the current node on a lock screen, unlock screen, or always-on screen. For example, the unlock screen may be a system desktop or other interface displayed by the first electronic device after the user successfully unlocks the device by entering a password on the lock screen. For instance, the user can operate on the system desktop without needing to enter an unlock password.

[0016] In one possible implementation, the above method may further include: the unlocking interface responds to the user's page-turning operation by swiping the unlocking interface, moving the real-time status image of the current node from the first page of the unlocking interface to the second page.

[0017] In one possible implementation, after displaying the real-time status image of the current node, the method may further include: stopping the display of the real-time status image of the current node when the display time meets a preset duration or in response to a user operation.

[0018] In one possible implementation, obtaining the real-time state image of the current node based on its real-time state may include:

[0019] Obtain an initial image containing the aforementioned thematic elements;

[0020] By combining the real-time state of the current node with the initial image, a real-time state image of the current node is obtained.

[0021] In one possible implementation, obtaining the initial image containing the aforementioned subject elements includes:

[0022] Retrieve the interface theme elements for the user's signed-up agreement;

[0023] Use the image in the resource library of the interface theme elements that corresponds to the real-time state of the current node as the initial image.

[0024] In one possible implementation, the aforementioned interface theme element is the wallpaper specified by the user.

[0025] In one possible implementation, the first electronic device may establish a scene-coordinated connection with the second electronic device, and after obtaining the real-time status of each of the at least two nodes, it may further include:

[0026] The real-time status of the current node is sent to the second electronic device through scene-based collaborative connection. This allows the second electronic device to obtain and display a real-time status image of the current node.

[0027] In one possible implementation, before sending the real-time status of the current node to the second electronic device via scene-coordinated connection, the following may also be included:

[0028] When the second electronic device subscribes to the first task mentioned above, the real-time status of the current node is sent to the second electronic device through scene collaboration connection.

[0029] Secondly, embodiments of this application provide a method for notifying an application of its real-time status, comprising:

[0030] Receive real-time status messages from the application. The application runs a first task, which includes at least two nodes. The application's real-time status messages indicate the real-time status of one of the at least two nodes.

[0031] Get the real-time status of the current node from the real-time status message;

[0032] The notification process for triggering the application's real-time status includes:

[0033] Obtain the real-time status image of the current node based on its real-time status.

[0034] Displays the real-time status image of the current node. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node.

[0035] Among them, the subject elements in the real-time status images of at least two nodes are the same.

[0036] In one possible implementation, obtaining the real-time status of the current node from the real-time status message includes:

[0037] Based on preset matching rules, obtain information about the first task and the status information of the current node from real-time status messages.

[0038] In one possible implementation, before obtaining the real-time status of the current node from the real-time status message, the following steps are also included:

[0039] If the first task is subscribed to, obtain the real-time status of the current node from the real-time status message.

[0040] For example, the real-time status of the current node obtained from the real-time status message can be the content expressed by all or part of the status information carried by the real-time status message.

[0041] In one possible implementation, obtaining the real-time status of the current node from the real-time status message may include:

[0042] Parse the real-time status messages to obtain information about the first task;

[0043] Based on the information matching rules of the first task, the real-time status message is parsed to obtain the status information of the current node.

[0044] For example, if the rule stipulates that the real-time status message should be fully parsed, then all the status information carried by the real-time status message can be obtained; if the rule stipulates that only part of the content of the real-time status message can be parsed, then parsing the real-time status message can obtain only part of the status information carried by the current node's real-time status message.

[0045] The aforementioned preset matching rules may include rules for matching information of the first task, and may also include the matching relationship between information of the first task and the rules.

[0046] In one possible implementation, after parsing the real-time status message to obtain the information of the first task, the process may further include:

[0047] Determine whether the first task has been subscribed to; if so, parse the real-time status message according to the matching rules between the subscribed content and the information of the first task to obtain the status information of the current node.

[0048] In one possible implementation, the above-mentioned rules for matching the subscribed content and the information of the first task to parse the real-time status message and obtain the current node's status information may include:

[0049] If the first task is subscribed to by the first subscriber, the real-time status message is parsed according to the matching rules between the content subscribed to by the first subscriber and the information of the first task to obtain the status information of the current node.

[0050] In one possible implementation, the above-mentioned rules for matching the subscribed content and the information of the first task to parse the real-time status message and obtain the current node's status information may include:

[0051] If the first task is subscribed to by both the first and second subscribers, the real-time status message is parsed according to the matching rules between the content subscribed to by the second subscriber and the information of the first task.

[0052] Based on the results of parsing the real-time status message and the content subscribed by the first subscriber, the status information of the current node is obtained. The result of parsing the real-time status message is all or part of the status information contained in the real-time status message.

[0053] In one possible implementation, if the first task is subscribed to by both a first subscriber and a second subscriber, the real-time status message is parsed according to the matching rules between the content subscribed to by the first subscriber and the information of the first task to obtain the status information of the current node.

[0054] In one possible implementation, before determining whether the first task has been subscribed, the following may also be included:

[0055] Perform permission verification on the subscription request of the first subscriber;

[0056] If the verification passes, the first task is subscribed to by the first subscriber.

[0057] In one possible implementation, the second subscriber may be located in a second electronic device, which may have a scene-coordinated connection with the first electronic device. The method may also include:

[0058] Based on the content subscribed by the second subscriber, the current node's status information is obtained from the result of parsing the real-time status message and sent to the second subscriber. This enables the second subscriber to generate an image containing the current node's real-time status, which is then displayed on the second electronic device. In this possible implementation, the result of parsing the real-time status message is the result of parsing the real-time status message according to the rules matching the content subscribed by the first subscriber and the information of the first task. Since the content subscribed by the second subscriber may be overwritten by the content subscribed by the first subscriber, the current node's status information sent to the second subscriber may be less than the status information obtained by the first subscriber. Consequently, the real-time status image of the current node displayed by the second electronic device may contain fewer status elements than the real-time status image of the current node displayed by the first electronic device.

[0059] In one possible implementation, after parsing the real-time status message according to the matching rules between the content subscribed by the second subscriber and the information of the first task, when the first task is subscribed to by both a first subscriber and a second subscriber, the implementation may further include:

[0060] The result of parsing the real-time status message is sent to the second subscriber, which is located in the second electronic device. The second electronic device can connect with the first electronic device in a scene-coordinated manner.

[0061] In one possible implementation, after parsing the real-time status message, the process may further include: saving the result of parsing the real-time status message.

[0062] In one possible implementation, after obtaining the real-time state of the current node, the process may further include: saving the real-time state of the current node.

[0063] In one possible implementation, obtaining the real-time status of the current node may include: after the system restarts, obtaining the real-time status of the current node based on the result of parsing the saved real-time status message, so that the first electronic device can regenerate and display the real-time status image of the current node.

[0064] In one possible implementation, before displaying the real-time status image of the current node, the following may also be included:

[0065] Based on the information from the first task and the real-time status of the current node, obtain the corresponding initial image;

[0066] By combining the real-time state of the current node with the initial image, a real-time state image of the current node is obtained.

[0067] In one possible implementation, displaying the real-time status image of the current node may include: displaying the real-time status image of the current node floating on the lock screen interface.

[0068] In one possible implementation, the real-time status image of the current node can be displayed in a blank area of ​​the unlock interface.

[0069] In one possible implementation, the aforementioned blank area can be automatically created by moving the icon in the unlock screen.

[0070] In one possible implementation, after the unlock interface stops displaying the real-time status image of the current node, the icon can be moved back to the blank area.

[0071] In one possible implementation, the real-time status image of the current node may also include information about the second task.

[0072] In one possible implementation, the method may further include: the information of the second task and the real-time status of the current node can move in the real-time status image of the current node in response to the user's operation.

[0073] In one possible implementation, the method may further include: in response to the user's operation on the real-time status of the current node, jumping to the application interface related to the first task.

[0074] In one possible implementation, the method may further include: in response to a user's operation on information related to the second task, jumping to an application interface related to the information related to the second task.

[0075] In one possible implementation, the above-mentioned display of the real-time status image of the current node may include: displaying the real-time status of the current node in the form of a window when displaying the real-time status image of the current node.

[0076] In one possible implementation, the first task mentioned above may have a time-sensitive nature.

[0077] Thirdly, embodiments of this application provide a method for displaying the real-time status of an application, applicable to a second electronic device. The second electronic device can establish a scene-coordinated connection with a first electronic device. The first electronic device can be used to initiate a first task of the application, the first task comprising at least two nodes. The method may include:

[0078] Receive the real-time status of the current node sent by the first electronic device, wherein the current node is one of the above at least two nodes;

[0079] Obtain the real-time status image of the current node based on its real-time status.

[0080] Displays the real-time status image of the current node. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node.

[0081] Among them, the subject elements in the real-time status images of at least two nodes are the same.

[0082] In one possible implementation, before receiving the real-time status of the current node sent by the first electronic device, the method may further include: sending a subscription request to the first electronic device, the subscription request being used to subscribe to the first task;

[0083] Accordingly, receiving the real-time status of the current node sent by the first electronic device may include: receiving the real-time status of the current node sent by the first electronic device when the first task is successfully subscribed.

[0084] In one possible implementation, before displaying the real-time status image of the current node, the following may be included:

[0085] Based on the real-time status of the first node, obtain the corresponding initial image;

[0086] By combining the real-time state of the first node with the initial image, we obtain the image of the real-time state of the current node.

[0087] In one possible implementation, the above-mentioned display of the real-time status image of the current node may include:

[0088] Display the real-time status image of the current node on the lock screen, unlock screen, or always-on screen.

[0089] In one possible implementation, the above method may further include: displaying a real-time status image of the current node floating on the lock screen interface.

[0090] In one possible implementation, the method may further include: when the real-time status image of the current node is displayed on the unlock interface, the real-time status image of the current node moves from the first page to the second page of the unlock interface in response to the user's page-turning operation on the unlock interface.

[0091] In one possible implementation, the real-time status image of the current node can be displayed in a blank area of ​​the unlock interface.

[0092] In one possible implementation, the aforementioned blank area can be automatically created by moving the icon in the unlock screen.

[0093] In one possible implementation, after the unlock interface stops displaying the real-time status image of the current node, the icon can be moved back to the blank area.

[0094] In one possible implementation, the real-time status image of the current node may also include information about the second task.

[0095] In one possible implementation, the method may further include: the information of the second task and the real-time status of the current node moving in the image in response to the user's operation.

[0096] In one possible implementation, the method may further include: in response to a user's operation on the real-time status of the current node in the real-time status image of the current node, jumping to an application interface related to the first task mentioned above.

[0097] In one possible implementation, the above method may further include: in response to the user's operation on the information of the second task, jumping to the application interface related to the second task.

[0098] In one possible implementation, the display of the real-time status image of the current node stops when the time for displaying the real-time status image of the current node meets a preset duration or in response to a user operation.

[0099] In one possible implementation, the aforementioned second electronic device could be a smartwatch.

[0100] In one possible implementation, the first task mentioned above has a time-sensitive nature.

[0101] Fourthly, embodiments of this application provide a real-time status display system for an application, which may include a first electronic device and a second electronic device. A scene collaboration connection may be established between the first electronic device and the second electronic device. The first electronic device may also be used to execute the method described in either the first or second aspect above.

[0102] The second electronic device may be used to perform the method described in any of the third aspects above.

[0103] Fifthly, embodiments of this application provide an electronic device. The electronic device may include one or more processors and a memory, the one or more processors being coupled to the memory. The memory can be used to store computer program code, the computer program code including computer instructions. When the one or more processors execute the computer instructions, the electronic device can perform the methods provided in any of the first to third aspects described above.

[0104] Sixthly, embodiments of this application provide a chip. The chip may include a processor and a communication interface, and the processor may invoke computer programs or instructions through the communication interface to execute the methods provided in any one of the first to third aspects described above.

[0105] In conjunction with the sixth aspect, as one possible implementation, the chip may also include a memory containing computer programs or instructions, and connected to a processor via a communication interface. The processor may use the communication interface to call and execute the computer programs or instructions stored in the memory, and perform the methods provided in any one of the first to third aspects.

[0106] In a seventh aspect, embodiments of this application provide a computer program product. When the computer program product is run on a computer, the computer can execute the methods provided in any one of the first to third aspects described above. Exemplarily, the computer can be a mobile terminal device. Exemplarily, the computer program product can be a program product on a mobile device operating system.

[0107] Eighthly, embodiments of this application provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is run on a computer, the computer can perform the method described in any one of the first to third aspects above. Attached Figure Description

[0108] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below. The drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0109] Figures 1a to 1f are schematic diagrams of capsule-shaped windows;

[0110] Figure 1g is a schematic diagram of the display of the capsule-shaped window on the desktop interface;

[0111] Figures 1h to 1m are schematic diagrams of card-shaped windows;

[0112] Figure 1n is a schematic diagram of the display of a card-shaped window on the desktop interface;

[0113] Figure 10 shows a schematic diagram of a card-shaped window displayed in the notification center;

[0114] Figure 1p is a schematic diagram of the display of a card-shaped window in the lock screen interface;

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

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

[0117] Figure 4 is a flowchart illustrating a method for displaying the real-time status of an application according to an embodiment of this application;

[0118] Figure 5a is a partial flowchart of a method for displaying the real-time status of an application provided in an embodiment of this application;

[0119] Figure 5b is another part of the flowchart of the method for displaying the real-time status of an application provided in the embodiments of this application;

[0120] Figure 5c is a partial flowchart of the method for displaying the real-time status of an application provided in an embodiment of this application;

[0121] Figure 6 is a schematic diagram of the subscription process of the method for displaying the real-time status of an application provided in an embodiment of this application;

[0122] Figure 7 is a schematic diagram of a system architecture for implementing a method for displaying the real-time status of an application, as provided in an embodiment of this application.

[0123] Figure 8a shows another system architecture example of a method for implementing the real-time status of a display application provided in an embodiment of this application;

[0124] Figure 8b is an example of a method for the first electronic device shown in Figure 8a to implement the real-time status of the display application;

[0125] Figure 9a is another system architecture diagram of a method for implementing the real-time status of a display application provided in an embodiment of this application;

[0126] Figure 9b is a schematic diagram of the method for subscribing to and displaying the real-time status of the application in the system shown in Figure 9a;

[0127] Figure 10(1a) is an example of a first electronic device displaying a real-time status image of a first node according to an embodiment of this application;

[0128] Figure 10(2a) is an example of a real-time status image of a second node displayed by a first electronic device according to an embodiment of this application;

[0129] Figure 10(3a) is an example of a real-time status image of a third node displayed by a first electronic device according to an embodiment of this application;

[0130] Figure 10(4a) is an example of a real-time status image of a fourth node displayed by a first electronic device provided in an embodiment of this application;

[0131] Figure 10(5a) is an example of a real-time status image of a fifth node displayed by a first electronic device according to an embodiment of this application;

[0132] Figure 10(6a) is an example of a real-time status image of a sixth node displayed by a first electronic device provided in an embodiment of this application;

[0133] Figure 10(1b) is an example of a real-time status image of the first node displayed on a watch according to an embodiment of this application;

[0134] Figure 10(2b) is an example of a real-time status image of the second node displayed on a watch according to an embodiment of this application;

[0135] Figure 10(3b) is an example of a watch displaying a real-time status image of a third node provided in an embodiment of this application;

[0136] Figure 10(4b) is an example of a real-time status image of the fourth node displayed on a watch according to an embodiment of this application;

[0137] Figure 10(5b) is an example of a real-time status image of the fifth node displayed on a watch according to an embodiment of this application;

[0138] Figure 10(6b) is an example of a real-time status image of the sixth node displayed on a watch according to an embodiment of this application;

[0139] Figure 11a is a schematic diagram of another method for displaying the real-time status of an application provided in an embodiment of this application;

[0140] Figure 11b is a schematic diagram of another method for displaying the real-time status of an application provided in an embodiment of this application;

[0141] Figure 11c is an example of step 11021 in the method for displaying the real-time status of an application provided in an embodiment of this application;

[0142] Figures 12a and 12b are examples of real-time status images moving in response to user operations, as provided in embodiments of this application.

[0143] Figures 13a and 13b are another example of real-time status images provided in the embodiments of this application;

[0144] Figure 14 is yet another example of a real-time status image provided in an embodiment of this application;

[0145] Figure 15 is a schematic diagram of another method for displaying the real-time status of an application provided in an embodiment of this application;

[0146] Figure 16 is a schematic diagram of another method for displaying the real-time status of a second electronic device according to an embodiment of this application;

[0147] Figure 17 is a schematic diagram of a method for notifying an application of its real-time status according to an embodiment of this application;

[0148] Figure 18 is another structural schematic diagram of the electronic device provided in the embodiment of this application. Detailed Implementation

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

[0150] The real-time state of an application is used to represent the real-time state of a specific task within the application, such as the real-time state of a food delivery task in a food delivery application, the real-time state of a ride-hailing task in a ride-hailing application, and the real-time state of a booked flight in a travel application.

[0151] As shown in Figures 1a to 1f, one way to display the real-time status of an application is as a capsule-shaped window. Capsule-shaped windows are typically displayed on the desktop interface. As shown in Figure 1g, a capsule-shaped window 11 is displayed in the upper left corner of the desktop interface.

[0152] As shown in Figures 1h to 1m, another display form of the application's real-time status is a card-shaped window. As shown in Figure 1n, the card-shaped window 12 is displayed on the desktop interface. As shown in Figure 1o, window 12 is displayed in the notification center; as shown in Figure 1p, window 12 is displayed on the lock screen interface.

[0153] As can be seen from Figures 1a-1p, displaying the real-time status of an application through a window suffers from visual homogenization. When the application's real-time status changes, it may go unnoticed by the user and be overlooked, thus failing to improve the user experience. Therefore, this application provides a method for displaying the real-time status of an application to overcome this homogenization and improve the user experience.

[0154] The electronic device used in the method for displaying the real-time status of an application provided in this application embodiment can be a device or apparatus with data connectivity, data calculation and processing, and interface display functions.

[0155] For example, the electronic device used in the method for displaying the real-time status of an application provided in this application embodiment can be a tablet computer, personal computer (PC), laptop computer, computer, netbook, in-vehicle computer, smartphone, smart wearable device (e.g., smartwatch, smart bracelet, smart glasses, etc.). Of course, the electronic device can also be various portable devices, as well as in-vehicle terminal devices, personal digital assistants (PDAs), smart home devices (e.g., smart TVs, etc.), and other smart devices. This application does not limit the specific form of the electronic device.

[0156] This application provides an electronic device capable of implementing the method for displaying the real-time status of an application provided in this application. The structure of the electronic device provided in this application will be described below with reference to FIG2.

[0157] As shown in Figure 2, the electronic device 200 may include: a processor 210, an external memory interface 220, an internal memory 221, a USB interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a SIM card interface 295, etc.

[0158] Processor 210 may include one or more processing units. For example, processor 210 may include a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of electronic device 200. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0159] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can retrieve it directly from this memory. By providing a memory, the number of times the processor 210 accesses data in the internal memory 221 can be reduced, thus reducing the processor 210's waiting time and improving system efficiency.

[0160] The method for displaying the real-time status of an application provided in this application embodiment can be implemented by the processor 210 controlling or calling other components, such as calling the software program of this application embodiment stored in the internal memory 221 to generate a real-time status image and control the display screen 294 to display the real-time status image. The processor 210 may include different devices. For example, when integrating a CPU and a GPU, the CPU and GPU can cooperate to execute the method for displaying the real-time status of an application provided in this application embodiment. For example, part of the software operation in the method is executed by the CPU, while another part of the algorithm related to the user interface (UI) display is executed by the GPU to obtain faster processing efficiency.

[0161] Display screen 294 can be used to display images, videos, etc. Display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 200 may include one or N displays 294, where N is a positive integer greater than 1. Display screen 294 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces (GUIs). For example, display screen 294 can display real-time status images, windows, photos, videos, web pages, or documents, etc. Furthermore, it is understood that in some embodiments, the status bar may also include a Bluetooth icon, a wireless fidelity (WiFi) icon, an external device icon, etc. In some embodiments, when the processor 210 detects a user's finger (or stylus, etc.) touching the display screen, in response to the touch operation, the processor 210 can execute the action corresponding to the touch operation. In some embodiments, when the processor 210 detects an input event from an external input device (e.g., mouse, keyboard, etc.) of the electronic device 200, in response to the input event, the processor 210 can execute the action corresponding to the input event. When the processor 210 runs the method for displaying the real-time state of an application provided in this application embodiment, the processor 210 can control the display screen 294 to display the real-time state image in the user interface, such as a static image or an image with animation effects.

[0162] For example, the electronic device 200 can be a single-screen electronic device or a multi-screen electronic device. For instance, when the electronic device 200 is a foldable electronic device, one of its displays 294 can be a single flexible display, or it can be a spliced ​​display consisting of two rigid screens and a flexible screen located between the two rigid screens. When the user performs a folding operation, the display can change its folding state. Optionally, in the method provided in the embodiments of this application, when the electronic device is in a folded state, the electronic device can display a real-time status image on the outer screen (the display exposed on the outside); when the electronic device is in an unfolded state, the electronic device can display a real-time status image on the inner screen or the unfolded screen (e.g., the display of a dual-screen or triple-screen display in a tri-fold phone).

[0163] Camera 293 can be used to capture still images or videos. Optionally, electronic device 200 may include 1 to N cameras 293. For example, camera 293 may include a front-facing camera or a rear-facing camera, or a single camera 293 may function as both a front-facing and a rear-facing camera. Typically, camera 293 may include a photosensitive element such as a lens assembly and an image sensor. The lens assembly includes multiple lenses (convex or concave lenses) for collecting light signals reflected from the object to be photographed and transmitting the collected light signals to the image sensor. The image sensor generates a raw image of the object to be photographed based on the light signals.

[0164] Internal memory 221 can be used to store computer executable program code, which includes instructions. Processor 210 executes various functional applications and data processing of electronic device 200 by running the instructions stored in internal memory 221. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system (OS), program code for at least one application, etc. The data storage area may store data created by electronic device 200 during use.

[0165] The internal memory 221 may also store one or more computer programs for performing the methods provided in the embodiments of this application. These one or more computer programs, stored in the internal memory 221 and configured to be executed by one or more processors 210, include instructions that can be used to perform the various steps in the embodiments of this application.

[0166] In addition, the internal memory 221 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0167] The sensor module 280 may include a fingerprint sensor, a touch sensor, a pressure sensor, a magnetic sensor, an ambient light sensor, a barometric pressure sensor, a bone conduction sensor, etc.

[0168] A touch sensor, also known as a "touch panel," may be disposed on the display screen 294. The touch sensor can be used to detect touch operations performed on or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event, and can also provide visual output related to the touch operation through the display screen 294. In other embodiments, the touch sensor may also be disposed on the surface of the electronic device 200, at a different location than the display screen 294.

[0169] The wireless communication function of electronic device 200 can be realized through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor and baseband processor.

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

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

[0172] The modem processor may include a modulator and a demodulator. The modulator modulates a low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal can be transmitted to the application processor. The application processor can output sound signals through an audio device (not limited to speaker 270A, receiver 270B, etc.) or display images or videos through the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and housed within the same device as the mobile communication module 250 or other functional modules.

[0173] The wireless communication module 260 provides solutions for wireless communication applications on the electronic device 200, including wireless local area networks (WLAN) (such as Wi-Fi), Bluetooth, global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), and ultra-wideband (UWB). The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 can receive electromagnetic waves via antenna 2, frequency modulate and filter the electromagnetic wave signal, and send the processed signal to processor 210. The wireless communication module 260 can also receive signals to be transmitted from processor 210, frequency modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2. In this embodiment, the electronic device 200 can establish wireless communication connections with other electronic devices through the wireless communication module 260 for data interaction, or the electronic device 200 can access an access point through the wireless communication module 260, thereby sending instructions and data with network devices or other electronic devices through the access point. For example, electronic device 200 can establish a wireless communication connection with other electronic devices through wireless communication module 260, and transmit information related to real-time status messages through wireless communication module 260.

[0174] In addition, the electronic device 200 can implement audio functions, such as music playback and recording, through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, and an application processor. The electronic device 200 can receive input from buttons 290, generating key signal inputs related to user settings and function control. The electronic device 200 can use a motor 291 to generate vibration alerts. The indicator 292 in the electronic device 200 can be an indicator light, used to indicate charging status, battery level changes, messages, missed calls, notifications, etc. The SIM card interface 295 in the electronic device 200 can be used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to achieve contact and separation with the electronic device 200.

[0175] In addition, in some scenarios, the electronic device 200 may also have an input device interface for connecting input devices such as keyboards, mice, and gamepads. This input device interface may reuse the USB interface 230 or be a separately designed dedicated interface; this application does not limit this.

[0176] It should be understood that the electronic device 200 shown in Figure 2 is merely an example and does not constitute a limitation on the electronic device. In practical applications, the electronic device 200 may have more or fewer components than shown, may combine two or more components, or may have different component configurations. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0177] The electronic device provided in this application embodiment can implement its functions and provide services to users by running an operating system stored in the program storage area. Exemplarily, this operating system can be various operating systems used in industry, such as an operating system developed based on OpenHarmony, for example... Or other operating systems, such as Mobile operating system etc.; it can also be various open-source operating systems or their derivatives, such as OS, and other embedded operating systems; or future new operating systems, such as AI operating systems based on artificial intelligence (AI).

[0178] An operating system can be a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interactions. In electronic devices, the operating system can interface downwards with the physical devices at the hardware layer and provide a runtime environment for application software (APPs) upwards.

[0179] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer may include a series of software providing various services to application developers, or it may be a framework providing various services such as databases, multimedia, and graphics, or it may provide capabilities such as distributed scheduling and system expansion. For example, the middleware layer may include a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer may include a set of core system capabilities, providing services to applications through the framework layer. The kernel layer can be a layer between hardware and software. The kernel layer may include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer may also support functions such as memory management and system process management.

[0180] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. The basic functions implemented by the electronic devices provided in this application embodiment can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of this application embodiment under a specific operating system, Figure 3 shows... Based on the architecture, those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as... Implementation under operating systems, etc.

[0181] As shown in Figure 3, the software architecture of the electronic device provided in this application embodiment can be divided into several layers. In some embodiments, from bottom to top, they are: kernel layer, system service layer, framework layer, and application layer. The layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem granularity in different device deployment scenarios, and each subsystem can also be tailored, added, or combined at the functional granularity.

[0182] For example, the kernel layer may include a kernel subsystem, a kernel abstract layer (KAL), and a driver subsystem.

[0183] The kernel subsystem includes multiple OS kernels, allowing for the selection of a suitable OS kernel for different resource-constrained devices, and is not limited to... Kernel, HarmonyOS kernel, LiteOS (Lite Operating System) kernel, etc.

[0184] The kernel abstraction layer can shield the differences between multiple kernels and provide basic kernel capabilities to the upper layers, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0185] The driver subsystem may include the Hardware Driver Foundation (HDF). The HDF is the foundation for the open HarmonyOS hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The HDF may include: display drivers, camera drivers, audio drivers, Bluetooth drivers, and sensor drivers, etc.

[0186] The system service layer is the core set of capabilities of the system, which can provide services to applications through the framework layer. This layer may include, but is not limited to, the following subsystem sets: basic system capability subsystem set, basic software service subsystem set, enhanced software service subsystem set, and hardware service subsystem set, etc.

[0187] The system's basic capability subsystems may include a distributed soft bus, distributed data management, distributed task scheduling, Ark multi-language runtime subsystem, and common basic library subsystem. It may also include a multi-modal input subsystem, graphics subsystem, security subsystem, AI subsystem, etc., which can be used to provide basic capabilities for the operation, scheduling, migration, and other operations of distributed applications on multiple HarmonyOS devices.

[0188] For example, distributed task scheduling can realize distributed service management (such as discovery, synchronization, registration, invocation, etc.), and can be used to support operations such as remote startup, remote invocation, remote connection and migration of applications across devices.

[0189] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0190] Distributed softbus can provide communication-related capabilities for seamless interconnection between multiple devices, such as WLAN service capabilities, Bluetooth service capabilities, softbus capabilities, Remote Procedure Call (RPC) capabilities, and StarFlash capabilities.

[0191] The Ark Multilingual Runtime Subsystem is a unified compilation and runtime platform that can be used to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0192] The basic software service subsystem set may include an event notification subsystem, a telephone subsystem, a multimedia subsystem, a DFX (Design For X) subsystem, an MSDP&DV subsystem, etc., which can be used to provide common and general software services for HarmonyOS.

[0193] The event notification subsystem can be used to provide applications with the ability to subscribe to, publish to, and unsubscribe from public events. For example, the event notification subsystem can be used to receive real-time status messages of nodes sent by applications and display them on the screen of electronic devices through processing by desktop applications and driver subsystems, etc.

[0194] The enhanced software service subsystem suite may include proprietary business subsystems for smart screens, proprietary business subsystems for wearables, and proprietary business subsystems for the Internet of Things (IoT), which can be used to provide HarmonyOS with differentiated capability-enhancing software services for different devices.

[0195] The hardware service subsystem set may include a location service subsystem, a unified identity and access management (IAM) subsystem, a biometric identification subsystem, a wearable proprietary hardware service subsystem, an IoT proprietary hardware service subsystem, etc., which can be used to provide hardware services for HarmonyOS.

[0196] For example, for deployment environments with different forms of electronic devices, the basic software service subsystem set, the enhanced software service subsystem set, and the hardware service subsystem set can be tailored at the subsystem granularity, and each subsystem can also be tailored at the functional granularity.

[0197] The framework layer provides application programming interfaces (APIs) and programming frameworks for the application layer (APP), which may include UI frameworks, user application frameworks, and capability frameworks. Different electronic devices may run different operating systems, and therefore support different APIs.

[0198] UI frameworks provide a complete infrastructure for UI development of system applications, including UI functionalities such as components, layouts, animations, and interactive events, as well as real-time interface preview tools. Ability frameworks are lightweight applications that schedule and manage the operation and lifecycle of Abilities.

[0199] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. The HarmonyOS API includes audio services (Audio API), push services (Push API), and account services (Account API), among others.

[0200] Applications at the application layer can include system applications and extended / third-party applications. System applications can include the desktop, theme widgets, control bar, settings, contacts, phone, camera, etc., while extended / third-party applications can include social apps, travel apps, food delivery apps, etc.

[0201] It should be noted that Figure 3 is an example of the software structure of an electronic device, which only simply lists some layers and software modules and does not constitute any limitation on the software structure of the electronic device. In practical applications, the operating system of an electronic device may also include other layers, or each layer may also include other software modules for implementing one or more functions or services. In addition, the embodiments of this application do not limit the specific layer in which each software module is located. For example, some system services in the system service layer may be deployed in the application framework layer or in the kernel layer.

[0202] For example, any electronic device in the above embodiments may have multiple applications installed to initiate the same or different tasks. For instance, a mobile phone may have food delivery apps, video apps, lifestyle apps, fitness apps, etc. When a user orders food delivery using a food delivery app, the mobile phone responds to this operation and initiates a food delivery task.

[0203] An embodiment of the method for displaying the real-time status of an application is shown in Figure 4. This method can be applied to a first electronic device, which can be any of the electronic devices provided in the above embodiments, running an application (such as a travel app, a food delivery app, or a queuing app) to initiate a first task (such as travel, food delivery, or queuing). This first task may include at least two nodes that are executed sequentially. For example, a user operates a ride-hailing app on their mobile phone to initiate a ride-hailing task. The nodes of this ride-hailing task may include a "driver accepted order" node (an example of a first node) and a "driver arrived" node (an example of a second node).

[0204] In this embodiment, the method for displaying the real-time status of an application may include:

[0205] Step 401: Obtain the real-time status message of the first node.

[0206] For example, the first node can be any of the above at least two nodes.

[0207] For example, the first electronic device can obtain real-time status messages by receiving real-time status messages sent by the application's server. For instance, when the first electronic device responds to a first task initiated by a user's operation of the application and enters or after entering the first node, the application's server can send the real-time status message of the first node in the first task to the first electronic device. For example, after a mobile phone initiates a ride-hailing task, when a driver accepts the order, the ride-hailing app's server sends the mobile phone a real-time status message of the first node in the ride-hailing task (which can be described as a driver acceptance message). For example, the first electronic device can obtain real-time status messages by receiving them from its server through the application. For example, the first electronic device can obtain real-time status messages by creating them through the application. For example, the real-time status message for food delivery can be created by a food delivery app installed on the first electronic device.

[0208] For example, the first electronic device obtaining the real-time status message of the first node may include an application receiving the real-time status message of the first node sent by the server, and the operating system of the first electronic device obtaining the real-time status message of the first node through the application. For example, a ride-hailing app receives a message from the server indicating that the driver has accepted the order.

[0209] Step 402: Obtain the real-time status image of the first node based on the real-time status message of the first node.

[0210] For example, step 402 may include, as shown in FIG5a:

[0211] Step 501: Obtain the real-time status of the first node from the real-time status message of the first node.

[0212] In some embodiments, step 501 may include: parsing the real-time status message of the first node to obtain the real-time status of the first node.

[0213] In this embodiment, the real-time status of a specific task may include or node names. The real-time status of a specific task may also include information related to nodes or node names.

[0214] For example, the first task is a ride-hailing task, and the real-time status of the first node may include the node name "order accepted"; the real-time status of the first node may also include information related to "order accepted", such as "vehicle type xxx", "X color car", "license plate xxxxxxxxxx", "estimated waiting time x minutes", etc.

[0215] For example, data fields in real-time status messages can carry real-time status information. For instance, a driver's accepted order message can carry information reflecting the real-time status of a ride-hailing task, such as "order accepted" (node / node name), vehicle type, license plate, vehicle color, estimated arrival time, and estimated waiting time.

[0216] For example, the real-time status message of the first node may contain multiple data fields. For instance, the real-time status message of the first node may contain five data fields: the first data field is used to fill in task information, the second data field is used to fill in the node (or node name), and the third to fifth data fields are used to fill in information related to the node (or node name). Taking a "driver accepted an order" message as an example, suppose the real-time status message of this first node contains five data fields: the first data field is filled in with the task information "ride-hailing," the second data field is filled in with the node "driver accepted an order," the third data field is filled in with the information "blue," the fourth data field is filled in with the information "boundary," the fifth data field is filled in with the information "license plate XXXXXX," and so on. For example, task information, nodes, and node-related information can be filled in using text, strings, numbers, etc., or in other words, the content of the data fields in the real-time status message can be in the form of text, images, strings, numbers, etc., without limitation.

[0217] In some embodiments, step 501 may include steps 5011-5012 as shown in FIG5b:

[0218] Step 5011: Parse the real-time status message of the first node to obtain the information of the first task. For example, parse the real-time status message of "order accepted" in the food delivery task to obtain the information that the first task is food delivery. Or, for example, parse the real-time status message of "driver accepted" in the ride-hailing task to obtain the information that the first task is ride-hailing, and so on.

[0219] Step 5012: Based on the information matching rules of the first task, parse the real-time status message of the first node to obtain the real-time status of the first node.

[0220] The first electronic device can be pre-configured with rules corresponding to different tasks. For example, the rules may include a first rule and a second rule. The first rule is task-related, specifying which data fields in the real-time status messages of different tasks can be parsed and which cannot. The second rule can be used to parse data fields in the real-time status messages. For example, the second rule may include text parsing rules, character parsing rules, number parsing rules, image parsing rules, icon parsing rules, and so on. When the content of a data field is text, the information entered in the data field can be parsed according to the text parsing rule; when the content of a data field is a string, the information entered in the data field can be parsed according to the character parsing rule; when the content of a data field is a number, the information entered in the data field can be parsed according to the number parsing rule; when the content of a data field is an image, the information entered in the data field can be parsed according to the image parsing rule; when the content of a data field is an icon, the information corresponding to the icon can be parsed according to the icon parsing rule; and so on.

[0221] For example, the first electronic device may pre-store rules and a correspondence table between the first task and the first rule. The first electronic device may first parse the task information of the real-time status message of the first node, find the corresponding first rule according to the first task information and the correspondence table, then find the parsable data fields according to the first rule, and then parse the parsable data fields according to the second rule to obtain the real-time status of the first node.

[0222] Step 502: Based on the information of the first task and the real-time status of the first node, obtain the corresponding initial image;

[0223] For example, the initial image may be a motion effect or a picture. In some embodiments, the first electronic device may select the appropriate motion effect or picture based on information from the first task and a mapping table between the real-time status of the first task and the initial image.

[0224] For example, the mapping relationship table can be shown in Table 1 below.

[0225] Table 1

[0226] For example, the mapping table and initial image resources (such as mp4 files, png files, etc. in Table 1) may be stored in the first electronic device or in an external device associated with the first electronic device, such as a server, storage device, etc.

[0227] For example, the initial image can be a similar, vivid description or portrait of an objective object, such as a static image of a landscape, a person, an animal, a cartoon, or a dynamic image.

[0228] Step 503: Combine the real-time status of the first node with the initial image to obtain the real-time status image of the first node.

[0229] For example, the state information of the first node can be processed, such as rendering, to present its content in the initial image, thus obtaining the real-time state image of the first node. For instance, the corresponding initial image obtained in step 502 could be a "running human figure". Combining the state information of the first node, such as "blue", "boundary", and "license plate XXXXXX", the resulting real-time state image of the first node can be: a "running blue" humanoid figure with "boundary" marked on its forehead and "license plate XXXXXX" marked on its arm. ",etc.

[0230] In the method for displaying the real-time status of an application provided in this application embodiment, the real-time status image of the first node not only presents the real-time status of the first node but also has the visual effects of the initial image. In this way, the visual effects of the real-time status image can attract the user's attention, thereby drawing focus to the real-time status in the image and enhancing the user experience.

[0231] In some embodiments, step 402 includes: the first electronic device can directly select the real-time status image of the first node corresponding to the real-time status message of the first node. For example, the first electronic device can preset a correspondence table between the real-time status and the real-time status image in a certain task, and save the real-time status image. When the first electronic device obtains the real-time status message of a certain node, it can find the real-time status image of the node according to the correspondence table.

[0232] Step 403: Display the real-time status image of the first node. The real-time status image of the first node includes the first subject element and the status elements corresponding to the real-time status of the first node.

[0233] For example, displaying the real-time status image of the first node can be done by displaying the real-time status image of the first node on any one or more of the lock screen, unlock screen and always-on screen of the first electronic device.

[0234] For example, when the lock screen of the first electronic device displays a real-time status image of the first node, the real-time status image of the first node can be suspended on the lock screen.

[0235] When the unlock screen of the first electronic device displays a real-time status image of the first node, the real-time status image of the first node may be displayed in a blank area of ​​the unlock screen. In some embodiments, when the unlock screen of the first electronic device displays a real-time status image of the first node, the real-time status image of the first node may also push other content displayed on the unlock screen (such as icons) to other locations (such as other pages on the desktop interface) to free up blank area to display the real-time status image of the first node.

[0236] In some embodiments, the method for displaying the real-time status of an application may further include: when a real-time status image of a first node is displayed on the unlock screen, the real-time status image of the first node moves from a first page of the unlock screen to a second page in response to a user's page-turning operation on the unlock screen. For example, when a user swipes to turn pages on the desktop interface, the real-time status image of the first node may follow and be displayed on the current page. Similarly, when a user swipes to turn from the first page to the second page on the desktop interface, the real-time status image of the first node displayed on the first page may follow and be displayed on the second page, and so on.

[0237] In some embodiments, the real-time status image of the first node can move along with the icon displayed on the unlock screen, appearing in the position vacated by the icon's movement. When the unlock screen stops displaying the real-time status image of the first node and / or the real-time status image of the second node, the icon is displayed again in its previous position. For example, as the real-time status image of the first node is displayed, the icon on the unlock screen moves to another location, such as another page, until the unlock screen displays the complete real-time status image of the first node. When the unlock screen stops displaying the real-time status image of the first node, as the real-time status image of the first node disappears, the icon that was previously moved to another location returns to its original position, and so on.

[0238] For example, the subject element can refer to an objective object in the aforementioned initial image or real-time state image, or it can be the core content or focus of expression in the initial image or real-time state image. For instance, the subject element can be a character (such as...). (e.g., landscapes, animals, pets, etc.). In some embodiments, the subject element can be all elements of the initial image.

[0239] For example, in addition to the main subject element, the aforementioned initial image or real-time status image may also include auxiliary elements such as color, lines, motion design, font and text design, and the image of the objective object. In some embodiments, color, lines, font and text design, or motion design may also be used as main subject elements, which is not limited here.

[0240] For example, the theme element can be task-related. For instance, when a mobile phone initiates a task in response to a user's action to hail a ride using a ride-hailing app, the task is "ride-hailing," and the corresponding theme element could be... For example, when the driver's car is blue, the theme element can be blue. etc.

[0241] For example, the theme element may be unrelated to the task. For instance, when the task is food delivery, the theme element could be "pets," or for example, food delivery, flight travel, and ride-hailing could all use the "astronaut" theme element, and so on.

[0242] For example, the first theme element can be a theme element, where "first" can be understood as a certain one.

[0243] For example, a status element can be one of the elements in the aforementioned real-time status image used to represent the real-time status, corresponding to the real-time status of a task or application. Status elements can represent the real-time status in an explicit way, such as a user-visible way, while status information can represent the real-time status in a program-understandable way, such as code. When a status element corresponds to status information, the content they express can be the same. A status element can also correspond to task information.

[0244] For example, the state element corresponding to the real-time state in a task may express content including nodes (or node names) and other data related to the nodes.

[0245] In some embodiments, the display of the real-time status image of the first node is stopped when the time for displaying the real-time status image of the first node meets a preset duration or in response to a user operation.

[0246] One possible scenario is that the task in the first node might require user completion. For example, if a user orders takeout but hasn't paid, the first node would be "pending payment." In this case, if the user doesn't execute the task within a preset timeframe after the first node is generated, it can be considered that the first electronic device has ended the task initiated by the user's application. For instance, when the task ends, the first electronic device can receive task completion information from the application's server, such as "transaction closed," or a message indicating that the application has completed the task creation process.

[0247] For example, the method for displaying the real-time status of an application provided in this application embodiment can be applied to the scenarios listed in Table 2.

[0248] Table 2

[0249] In some embodiments, the method for displaying the real-time status of an application provided in this application may further include:

[0250] Obtain the real-time status message of the second node, for example, similar to step 401;

[0251] The real-time status image of the second node is obtained based on the real-time status message of the second node, for example, similar to step 402;

[0252] Display the real-time status image of the second node, which includes a first subject element and a status element corresponding to the real-time status of the second node, for example, similar to step 403.

[0253] For example, the second node can be generated based on the completion of the task of the first node. The real-time status image of the second node and the real-time status image of the first node may contain the same subject element—the first subject element. The first subject element may be an animal, landform, plant, sky, or human character, etc. The real-time status image of the first node may further contain status elements corresponding to the real-time status of the first node, and the content presented by the status elements may be such as "Order accepted" (node / node name), "vehicle type xxx", "license plate xxxxxxxxxx", "x color car", "estimated waiting time x minutes", etc.; the real-time status image of the second node may further contain status elements corresponding to the real-time status of the second node, and the content presented by the status elements may be such as "driver has arrived" (node / node name), "vehicle type xxx", "license plate xxxxxxxxxx", "x color car", etc.

[0254] For example, one example of the above method for obtaining the real-time status message of the second node is that after the driver arrives at the designated departure point, the server of the ride-hailing APP sends a real-time status message indicating that the driver has arrived to the mobile phone (an example of the real-time status message of the second node). Alternatively, the ride-hailing APP can create a real-time status message, as described in the relevant descriptions in the foregoing embodiments.

[0255] Similar to the real-time status messages of the first node, the real-time status messages of the second node can carry status information corresponding to the real-time status of the second node. For example, the real-time status message indicating that the driver has arrived can carry status information such as "arrived" (the node name of the second node), vehicle type, license plate, vehicle color, and arrival location.

[0256] For example, the real-time state image of the second node can be similar to that of the first node, used to display the real-time state of the second node through an initial image with visual effects (see the foregoing description). For example, the real-time state image of the second node can be obtained by embedding the real-time state of the second node into the initial image.

[0257] For example, the first electronic device may display a real-time status image of the second node in the following ways: the real-time status image of the second node covers the real-time status image of the first node, making it impossible to display the real-time status image of the first node; or the real-time status image of the first node is stopped from being displayed before the real-time status image of the second node is displayed; or the real-time status image of the second node is stopped from being displayed and then displayed; and so on.

[0258] For example, the real-time status image of the first node and the real-time status image of the second node may contain different auxiliary elements in addition to the same main subject element. Assume that both the real-time status image of the first node and the real-time status image of the second node contain the first main subject element. The real-time status image of the first node can show a running human figure. The second node's real-time status image includes status elements such as "Order accepted," "Car is blue with borders visible," and "License plate number is XXXXXX," reflecting the real-time status of the first node. The real-time status image of the second node can show the shape of a car waiting with its door open. And status elements such as "Arrived at location Y" that reflect the real-time status of the second node. Understandably, the real-time status images of the first and second nodes contain different auxiliary elements— The shape, but the main elements are... The consistent style and different auxiliary elements add fun and visual appeal, further overcoming the visual homogenization of existing technologies that display the application's real-time status in a window format. It can continuously attract users' attention, solve the problem of the application's real-time status being ignored due to experience homogenization, and further improve the user experience, which helps to increase user stickiness.

[0259] For example, the second node can be the end node of the task. For instance, when the phone displays a real-time status image of the second node containing status elements such as "arrived at location Y", the user may have already reached their destination and hailed a ride. In this case, the task initiated by the phone can be considered complete, meaning the second node is the end node of the task.

[0260] In some embodiments, the real-time status image of the first node and / or the real-time status image of the second node may also simultaneously display information published by another application. This other application can be a system app or a third-party app. For example, the real-time status image (an example of the real-time status image of the first node and / or the real-time status image of the second node) may include not only the real-time status of food delivery tasks, but also weather data published by a weather app, battery data published by a system application, etc. In some embodiments, the real-time status image may contain status elements of more than one task, or may display the real-time status of more than one task, such as simultaneously displaying the real-time status of food delivery and flights, etc.

[0261] In some embodiments, after the first electronic device displays the real-time status image of the first node and / or the real-time status image of the second node, it can jump to the relevant page of the application in response to the user's click on the real-time status image of the first node and / or the real-time status image of the second node. For example, when the user clicks on the "Delivering" status element in the real-time status image of the first node, the mobile phone can jump to the order status page of the corresponding food delivery APP.

[0262] In some embodiments, the real-time status image of the first node and / or the real-time status image of the second node may contain status elements from more than one application. For example, assuming the aforementioned application is the first application, the real-time status image may contain not only the status elements of the first application but also information published by the second application. In this case, the first electronic device may also, in response to a user clicking on information published by the second application, navigate to the relevant page of the second application. For example, when a user clicks on a card displaying battery information in the real-time status image, the interface navigates to the battery-related page.

[0263] In some embodiments, when the real-time status image of the first node and / or the real-time status image of the second node contains content published by multiple applications, the first electronic device may respond to a user's swipe operation on the multiple pieces of content, with the content published by the multiple applications moving and displayed accordingly. For example, the real-time status image of "Orders Received" displays multiple cards, where one card displays the real-time status, another card displays weather data, and yet another card displays the battery data of the electronic device. When the user swipes on the card displaying the weather data, that card moves, and the cards displaying the battery data and the real-time status also move accordingly.

[0264] Table 1 shows that in some embodiments, the real-time status image of the first node and / or the real-time status image of the second node may also include an application icon.

[0265] For example, in the above method for displaying the real-time status of an application, the generation of the real-time status images of the first node and the second node can be implemented by the operating system of the first electronic device. For instance, the operating system of the first electronic device may include a first component and a second component. The first component can be used to parse the real-time status messages of the first and second nodes, and the second component can be used to generate the real-time status images of the first and second nodes. For example, the first component can be located in the event notification subsystem of the system shown in Figure 3. For example, the second component can be a system theme component of the first electronic device. The first component can also be named a scene data component, etc., without limitation, depending on actual needs (such as readability requirements).

[0266] The second component can provide an initial image with visual effects, and can also obtain the real-time states of the first node and the second node from the first component, and combine the real-time states of the first node and the second node with the corresponding initial images to generate real-time state images of the first node and the second node, respectively. For example, the second component can obtain the initial image corresponding to the real-time state of the first node and the initial image corresponding to the real-time state of the second node according to the aforementioned mapping table.

[0267] In some embodiments, after parsing the real-time status message of the first node to obtain the information of the first task, the method may further include: determining whether the first task has been subscribed to. Accordingly, step 5012 may include: if the first task has been subscribed to, parsing the real-time status message of the first node to obtain the real-time status of the first node according to the rules for matching the subscribed content and the information of the first task. For example, when the real-time status of a task can only be displayed through subscription as shown in Figure 4, the operating system of the first electronic device, after receiving the real-time status message of the first node, may first determine whether the task has been subscribed to. If not, it may be displayed in a window instead of as shown in Figure 4. Accordingly, parsing the real-time status message of the first node according to the rules for matching the information of the first task may include: if the task has been subscribed to, the first electronic device may parse the real-time status message of the first node according to the rules for matching the subscribed content and the information of the task.

[0268] In some embodiments, the real-time status of the second node can be obtained in the same manner.

[0269] In some embodiments, when the first task is subscribed to, parsing the real-time status message of the first node according to the matching rules between the subscribed content and the information of the first task to obtain the real-time status of the first node may include:

[0270] If the first task is subscribed to by the first subscriber, the real-time status message of the first node is parsed according to the matching rules between the content subscribed to by the first subscriber and the information of the first task, so as to obtain the real-time status of the first node.

[0271] In some embodiments, the real-time status of the second node can be obtained in the same manner.

[0272] For example, the first subscriber may be a second component. In some embodiments, there may be multiple second components in the first electronic device, or there may be multiple subscribers in the first electronic device.

[0273] In some embodiments, the second component can subscribe to tasks through the first component. For example, the second component can send a subscription request to the first component when the operating system of the first electronic device starts up. For instance, the startup of the operating system of the first electronic device can trigger the second component to send a subscription request to the first component.

[0274] In some embodiments, when the second component subscribes to a task, different real-time states can be subscribed to for different tasks. For example, for a "ride-hailing" task, the second component can subscribe to one or more of the following: node (node ​​name), "vehicle color," "vehicle type," and "license plate," to be displayed in conjunction with the initial image. Exemplarily, during further parsing, which fields can continue to be parsed can be determined comprehensively based on the first rule and the content subscribed to by the second component. For instance, if the first rule specifies that the 2nd, 3rd, and 5th data fields in the real-time status message "driver has accepted an order" can be parsed, and the content subscribed to by the second component is the content of the 2nd, 4th, and 5th data fields, then the data fields that can continue to be parsed in the "real-time status message of driver has accepted an order" are the 2nd and 5th data fields.

[0275] For example, the above-mentioned method of parsing the real-time status message of the first node according to the matching rule between the content subscribed by the first subscriber and the information of the first task to obtain the real-time status of the first node may include: assembling the result of parsing the real-time status message of the first node into the real-time status of the first node according to the subscribed content. For example, when the content of the "ride-hailing" task subscribed by the second component is the content of the 2nd, 4th, and 5th data fields in the "real-time status message of driver accepted order", the content of the 2nd, 4th, and 5th data fields in the "real-time status message of driver accepted order" can be sequentially filled into the corresponding positions according to the preset data format of the subscribed content. In some embodiments, when the 4th data field in the "real-time status message of driver accepted order" is not parsed due to the first rule, the corresponding position in the preset data format may be left blank, or a preset character or number may be used to indicate that the content at that position is empty. For example, the real-time status of the second node can be obtained in a similar manner.

[0276] In some embodiments, the second component may not need to subscribe to tasks, and the real-time status of all tasks can be displayed in a manner similar to the real-time status image of the first node.

[0277] In some embodiments, before determining whether the first task has been subscribed to, the steps shown in Figure 6 may also be included:

[0278] Step 601: Perform permission verification on the subscription request of the first subscriber. For example, the second component initiates a subscription request to the first component. The subscription request may include task information and subscribed content. Exemplarily, the task information may be the task name, identifier (ID), number, etc. The subscribed content is detailed in the foregoing description. The first component may perform permission verification on the subscriber in the subscription request, or on the information of the first task and / or the subscribed content in the subscription request. Exemplarily, permission verification may be performed according to preset rules or preset conditions.

[0279] Step 602: If the verification passes, the first task is subscribed to by the first subscriber. For example, when the first component determines that the verification object (such as the subscriber or the information of the first task in the subscription request and / or the subscribed content) meets the preset rules, the first task is successfully subscribed to by the first subscriber. Alternatively, when the first component determines that the verification object (such as the subscriber or the information of the first task in the subscription request and / or the subscribed content) meets the preset conditions, the first task is successfully subscribed to by the first subscriber.

[0280] For example, the first electronic device can perform permission verification on the first subscriber (such as the second component) that initiated the subscription request, based on a whitelist. For instance, if the second component is in the whitelist, it can be determined that the second component has permission, and the permission verification passes; if the information of the second component cannot be found in the whitelist, it can be determined that the second component does not have permission, and the permission verification fails. If the verification passes, the information of the first subscriber and the content subscribed by the first subscriber can be further saved. For example, if the subscription request of the second component passes verification, the first component can save the information of the second component, the task information, and the subscribed content.

[0281] In some embodiments, determining whether the first task is subscribed may include: determining whether the first task is subscribed based on the saved content subscribed by the subscriber and the parsed information of the first task. For example, if the saved content subscribed by the subscriber contains information about the first task, then the first task is determined to be subscribed; otherwise, it is determined that the first task is not subscribed. For instance, if the content subscribed to by the second component saved by the first electronic device contains information about the first task, then the first task is determined to be subscribed.

[0282] In some embodiments, the first task described above may be subscribed to by multiple subscribers. For example, when the content subscribed to by the first subscriber includes all content subscribed to by the other subscribers among the multiple subscribers, the process of parsing the real-time status message of the first node to obtain the real-time status of the first node based on the matching rules between the subscribed content and the information of the first task, when the first task is subscribed to, may include:

[0283] If the first task is subscribed to by the first subscriber, the real-time status message of the first node is parsed according to the matching rules between the content subscribed to by the first subscriber and the information of the first task to obtain the real-time status of the first node. For example, the real-time status of the second node can be obtained in a similar manner.

[0284] In some embodiments, when the first task is subscribed to by at least a first subscriber and a second subscriber, and the content subscribed to by the second subscriber includes all the content subscribed to by the first subscriber, for example, in the case where the first task is subscribed to, the real-time status message of the first node is parsed according to the rules for matching the subscribed content and the information of the first task to obtain the real-time status of the first node. As shown in Figure 5c, this includes:

[0285] Step 504: If the first task is subscribed to by both the first subscriber and the second subscriber, parse the real-time status message of the first node according to the matching rules between the content subscribed by the second subscriber and the information of the first task.

[0286] For example, since the content subscribed by the second subscriber includes all the content subscribed by the first subscriber, the real-time status of the first node obtained by parsing the real-time status message of the first node according to the matching rules between the content subscribed by the second subscriber and the information of the first task includes the real-time status of the first node subscribed by the first subscriber.

[0287] Step 505: Based on the result of parsing the real-time status message of the first node and the content subscribed by the first subscriber, obtain the real-time status of the first node. The result of parsing the real-time status message of the first node can be all or part of the status information of the first node contained in the real-time status message. For example, if the result of parsing the real-time status message of the first node is: node "Driver has accepted an order", vehicle type "XXX", license plate "XXXXXXXXXX", and the content subscribed by the first subscriber is the node name and vehicle type, then based on the result of parsing the real-time status message of the first node and the content subscribed by the first subscriber, the real-time status of the first node is obtained as: node "Driver has accepted an order", vehicle type "XXX". For example, the real-time status of the second node can be obtained in a similar manner.

[0288] For example, the generation and display principle of the real-time status image of the second node can be found in the description of the real-time status image of the first node in the above embodiment.

[0289] In some embodiments, the duration for which the real-time status images of the first node and / or the second node are displayed at the display entry point may be a predetermined duration, such as 1 minute, etc., which is not limited here. The display entry point may be: a lock screen interface, an unlock interface, or a screen-off interface. For example, when the predetermined duration is long, such as 3 minutes, 5 minutes, 10 minutes, or even longer, the real-time status image of the first node may be replaced by the real-time status image of the second node, so that the display duration is less than the predetermined duration.

[0290] In some embodiments, the second subscriber may be located in or within a second electronic device, and the first electronic device may establish a scene-coordinated connection with the second electronic device. Scene coordination refers to establishing a connection based on communication technologies such as Bluetooth, WiFi, and StarFlash in different electronic devices and scenes, and cooperating based on this connection to improve user experience and work efficiency. Scene coordination connection is a connection established based on communication technologies such as Bluetooth, WiFi, and StarFlash to achieve scene coordination. The method for displaying the real-time status of an application provided in this application embodiment, when the first task is subscribed to by the second subscriber, may further include:

[0291] Based on the content subscribed by the second subscriber, the real-time status of the first node is obtained from the result of parsing the real-time status message of the first node, and then sent to the second subscriber. For example, when the content subscribed by the first subscriber includes all the content subscribed by the second subscriber, the real-time status of the first node sent to the second subscriber can be obtained from the result of parsing the real-time status message of the first node, based on the content subscribed by the second subscriber. For example, the real-time status of the second node can be obtained in a similar manner.

[0292] Alternatively, the method for displaying the real-time status of an application provided in this application embodiment may further include: sending the result of parsing the real-time status message of the first node to the second subscriber. For example, if the first task is subscribed to by both the first and second subscribers, after parsing the real-time status message of the first node according to the matching rules between the content subscribed by the second subscriber and the information of the first task, the result of parsing the real-time status message of the first node may be further sent to the second subscriber. Similarly, the result of parsing the real-time status message of the second node may be sent to the second subscriber.

[0293] For example, sending the real-time status of the first node to the second subscriber may include:

[0294] The first electronic device sends the real-time status of the first node to the second electronic device through scene-based collaborative connection. For example, the second electronic device can be any electronic device provided in the device embodiment, such as a smartwatch, smart car window, etc. Similarly, the real-time status of the second node can be sent to the second subscriber.

[0295] For example, the real-time status image of the first node displayed by the second electronic device (which may be simply referred to as the third image) and the real-time status image of the first node displayed by the first electronic device may belong to different themes. For example, the real-time status image of the first node displayed by the second electronic device and the real-time status image of the first node displayed by the first electronic device may contain different thematic elements. For example, the real-time status image of the first node displayed by the second electronic device may contain second thematic elements. For example, the generation and display of the real-time status image of the first node displayed by the second electronic device may be similar to the method by which the first electronic device generates and displays the real-time status image of the first node. The advantage of the technical solution provided in this embodiment is that, during the user's driving process, the real-time status can be displayed in a way that is easy for the user to view, such as being displayed on a smart car window or on a smartwatch, etc. Furthermore, displaying real-time status images with different themes on different electronic devices can further enhance the user experience.

[0296] Similar to the second electronic device described above acquiring the real-time status of the first node and displaying a real-time status image of the first node,

[0297] The first electronic device can send the real-time status of the second node to the second electronic device through scene collaboration connection; the second electronic device displays a real-time status image of the second node (which may be referred to as the fourth image). For example, the third and fourth images may contain the same second theme element. For instance, when the first electronic device is a mobile phone and the second electronic device is a watch, the first theme corresponding to the "ride-hailing" task on the mobile phone may be... The second theme corresponding to the "Ride-hailing" task on the watch can be... The initial image in the third image could be a running scene. The initial image in the fourth image could be an image of a car door open and waiting. etc.

[0298] In some embodiments, the first electronic device may send real-time status to the second electronic device if the second electronic device has subscribed.

[0299] For example, before the first electronic device sends the real-time status of the first node to the second electronic device via scene collaboration connection, it may further include: the first electronic device receiving a subscription request sent by the second electronic device and performing permission verification according to the subscription request; correspondingly, the first electronic device sending the real-time status of the first node to the second electronic device via scene collaboration connection may include: the first electronic device sending the real-time status of the first node to the second electronic device via scene collaboration connection if the permission verification is passed; the first electronic device sending the real-time status of the second node to the second electronic device via scene collaboration connection may include: the first electronic device sending the real-time status of the second node to the second electronic device via scene collaboration connection if the permission verification is passed.

[0300] In some embodiments, the duration of the third and / or fourth images displayed is similar to that of the real-time status images of the first and second nodes, and may be a predetermined duration.

[0301] In some embodiments, the first electronic device may also establish scene collaboration connections with more electronic devices, so that the real-time status of the first node and / or the real-time status of the second node can be displayed through the display entry of more electronic devices.

[0302] For example, when other electronic devices subscribe to tasks from the first electronic device, they can initiate a subscription request when establishing a connection with the first electronic device.

[0303] As shown in Figure 7, a system architecture example for implementing the method for displaying the real-time status of an application provided in this application embodiment is established between a desktop computer, a laptop computer, a tablet computer, a mobile phone, an in-vehicle system, a smart screen (including a TV), a watch, and a wristband. When the mobile phone is the first electronic device, it can send real-time status (such as the real-time status of a first node, the real-time status of a second node, etc.) to the desktop computer, laptop computer, tablet computer, watch, and wristband. The desktop computer, laptop computer, tablet computer, watch, and wristband can display the real-time status image at their respective display entrances, further improving the convenience of user viewing. Exemplarily, any one of the desktop computer, laptop computer, and tablet computer can also act as the first electronic device and send real-time status to the other electronic devices. The method for displaying the real-time status of the application can be similar to the method for displaying the real-time status of the application when the mobile phone is the first electronic device.

[0304] In some embodiments, multiple electronic devices that have established scene-coordinated connections with the first electronic device may display images with different themes. For example, for the real-time status of different nodes in the same task, a mobile phone may display different images under theme A at the display entry point, a desktop computer may display different images under theme B at the display entry point, a laptop may display different images under theme C at the display entry point, a tablet computer may display different images under theme D at the display entry point, a watch may display different images under theme E at the display entry point, a wristband may display different images under theme F at the display entry point, and so on.

[0305] For example, in the above embodiments, the first electronic device and other electronic devices that coordinate with the scene can communicate through communication technologies such as Bluetooth and the same wireless local area network.

[0306] In some embodiments, the second node may not be the end node of the task, and the task may include more nodes, such as a third node after the second node, and so on. Exemplarily, the method for displaying the real-time status of the third node and other nodes can be similar to the method for displaying the real-time status of the first node and the second node.

[0307] Another system architecture example for implementing the method for displaying the real-time status of an application provided in this application embodiment is shown in Figure 8a. After a first electronic device initiates a task in response to a user's operation on the application, the application can create and update real-time status messages. For example, all real-time status messages in the task (such as the real-time status messages of the first node, the second node, etc.) can be created by the application. Alternatively, the application can create real-time status messages, and the server can send updated real-time status messages. For example, the first real-time status message in the task is created by the application, and subsequent real-time status messages are sent by the server. The server can also create and update real-time status messages, for example, all real-time status messages in the task are sent by the server. Afterwards, the application can forward the real-time status message to the first component through the live window notification service module. The first component can parse the real-time status message to obtain the real-time status. The first component can also send the real-time status to the second and third components to generate a real-time status image. The first electronic device can simultaneously display the real-time status in both window and real-time status image formats, and the second electronic device can display the real-time status image. For example, the live window notification service module can be set in the event notification subsystem shown in Figure 3. For example, the method for parsing real-time status messages by the first component can be detailed in the description of the above method embodiments. For example, the image displayed by the first electronic device may be the same as or different from the image displayed by the second electronic device. For example, when the second electronic device is a watch, the third component may be a watch face component (which can be understood as using a watch face component to implement the function of the third component); when the second electronic device is a mobile phone, tablet computer, or other electronic device, the third component may be a system theme component (which can be understood as using a system theme component to implement the third function), and so on.

[0308] For example, if the first electronic device does not establish a scene collaboration connection with the second electronic device, the second electronic device in Figure 8a can be omitted.

[0309] For example, the first component in FIG8a may further include the function of generating a real-time status image, in which case the second component may be omitted.

[0310] For example, the first electronic device in FIG8a may only display a real-time status image.

[0311] In some embodiments, the real-time notification service module can also perform parameter verification, permission verification, and frequency control on real-time status messages.

[0312] An example of a method for implementing the real-time status of a display application using the first electronic device shown in Figure 8a is shown in Figure 8b, which may include:

[0313] Step 811: The second component sends a subscription request to the first component to subscribe to a task of the application.

[0314] The first component can be used to parse the real-time status messages of the first node and the second node, while the second component can be used to generate real-time status images of the first node and the second node. For example, the first component can be set in the event notification subsystem of the system shown in Figure 3. For example, the second component can be a system theme component of the first electronic device. The first component can also be named a scene data component, etc., without limitation.

[0315] Step 812: The first component performs permission verification on the second component to determine whether the second component has permission to subscribe to the task. If the verification passes, the next step is to proceed to step 813; if the verification fails, the subscription ends.

[0316] Step 813: The first component saves the subscription information.

[0317] More specifically, the first component stores information about the second component, information about the task, and specific content subscribed to under the task, thus completing the subscription.

[0318] Step 821: After receiving the real-time status message for the task, the application sends the real-time status message to the Real-Time Window Notification Service Module.

[0319] Step 822: The real-time status notification service module forwards the real-time status message to the display entry.

[0320] The entry point for displaying information can be the lock screen, unlock screen, or always-on screen. Real-time status messages can be displayed in the form of windows as shown in Figures 1a-1f.

[0321] Step 823: The Real-Time Notification Service module forwards the real-time status message to the first component.

[0322] Step 824: The first component extracts the real-time status.

[0323] The first component parses the real-time status message to obtain the real-time status. When the second component successfully subscribes to the task, the first component extracts the content subscribed by the second component from the real-time status.

[0324] Step 825: The first component sends the real-time status of its subscription to the second component.

[0325] Step 826: Generate a real-time status image.

[0326] Specifically, the second component combines the received real-time state with the corresponding initial image according to the stored mapping table between real-time state and initial image (as shown in Table 1) to generate a real-time state image. For example, the initial image can also be a video resource, and the real-time state of each node can be displayed by playing the same or different video resources.

[0327] Step 827: The second component sends a real-time status image to the display entry.

[0328] Step 828: Display the real-time status image at the entry point.

[0329] In some embodiments, steps 822 and 823 may be performed simultaneously.

[0330] In some embodiments, the second component can directly obtain the real-time status of the task from the application, or can directly subscribe to the real-time status of the task from the application. In this case, the first component can be omitted.

[0331] In some embodiments, the above application may be a system application of the first electronic device.

[0332] In some embodiments, the second component described above can be made available to developers to obtain more design ideas and resources. At the same time, developers can also perform interactive design to enable the first electronic device to obtain more initial image resources, further increasing the fun and watchability of the real-time status display, thereby meeting the real-time status display experience needs of more tasks and further increasing user stickiness.

[0333] For example, the developer could design a theme around pets, with initial images such as cats or dogs. Taking a dog theme as an example, the initial images could be different breeds of dogs; or, the initial images could be the same breed of dog wearing different clothes, or the same breed of dog with different hairstyles, and so on. When the dog in the real-time status image matches the user's dog breed, it further attracts the user's attention and increases user engagement. In some embodiments, users can choose their preferred theme to display their real-time status.

[0334] In some embodiments, the operating system of the first electronic device may further include a live interface module, which is connected between the application and the live window notification service module to provide a communication interface between the application and the live window notification service module.

[0335] In some embodiments, the first component may include multiple modules, which may be derived according to the functional division of the first component. Understandably, the number of modules and module names of the first component may have various possibilities depending on the functional division.

[0336] Figure 9a shows another system architecture example for implementing the method for displaying the real-time status of an application provided in this application embodiment. In this embodiment, the system for displaying the real-time status of an application includes a first electronic device, a second electronic device, and a watch, and the first electronic device, the second electronic device, and the watch establish a scene collaboration connection. The first electronic device and the second electronic device can be a mobile phone, a desktop computer, a laptop computer, a tablet computer, etc.

[0337] As shown in Figure 9a, the first electronic device may include a first component, a theme component, a live window notification service module, a live interface module, and a display entry point. The first electronic device also has an application installed. The first component may include a subscription module, a verification module, a subscription data module, a rule data module, an analysis module, a live data module, and an assembly module. For example, the first component, the live window notification service module, and the live interface module may be configured in the event notification subsystem shown in Figure 3. The display entry point can be implemented through the desktop and driver subsystem, etc.

[0338] The second electronic device includes a theme component and a display entry point; for example, a watch includes a watch face component and a display entry point. For ease of description, the theme component in the first electronic device will be referred to as the first theme component, and the theme component in the second electronic device will be referred to as the second theme component.

[0339] Assuming the application is a food delivery app, this embodiment takes displaying the real-time status of a food delivery task as an example to further explain the method for displaying the application's real-time status. As shown in Figure 9a, the method for displaying the application's real-time status before the user initiates a food delivery task may include:

[0340] Step 911: When the operating system of the first electronic device starts, the first theme component sends a subscription request to the first component, requesting to subscribe to the food delivery app. This subscription request may include information about the first theme component, information about the food delivery app, and its real-time status. The real-time status may include the real-time status of multiple nodes, such as "Pending Payment," "Order Accepted," "Pickup in Progress," "Arrived at Store," "Delivery in Progress," and "Arrived." The real-time status of different nodes among the multiple nodes may include the node (or node name). The real-time status of different nodes among the multiple nodes may also include information related to the node (or node name) (such as the amount to be paid, estimated delivery time, etc.).

[0341] Step 912: After receiving the subscription request, the subscription module in the first component sends a permission verification request to the verification module.

[0342] The permission verification request may contain some or all of the information carried in the subscription request.

[0343] The verification module performs permission verification on the first topic component based on the permission verification request, as detailed in the relevant descriptions in the aforementioned embodiments.

[0344] In this embodiment, the verification module can notify the subscription module whether the permission verification has passed.

[0345] Step 913: If the permission verification is successful, the subscription module sends the information of the first topic component and its subscribed content to the subscription data module for storage.

[0346] Step 911a: When the second electronic device establishes a scene collaboration connection with the first electronic device, the second theme component sends a subscription request to the subscription module, requesting to subscribe to a food delivery app. This subscription request may include information about the second theme component, information about the food delivery app, and its real-time status. The real-time status may be the same as the real-time status in step 911.

[0347] Subsequently, similar to steps 912 and 913, the subscription module requests the verification module to perform permission verification. If the permission verification passes, the subscription data module saves the information of the second topic component and the task information and real-time status of the second topic component subscription.

[0348] Step 911b: When the watch establishes a scene collaboration connection with the first electronic device, the watch face component sends a subscription request to the subscription module, requesting to subscribe to a food delivery app. This subscription request may include information about the watch face component, information about the food delivery app, and real-time status. The status information in the real-time status subscribed to in this subscription request may be less than the status information in the real-time status in step 911; for example, the status information in the real-time status subscribed to in this subscription request may only include the node (or node name). In some embodiments, the status information in the real-time status subscribed to in this subscription request may be the same as the status information in the real-time status in step 911.

[0349] Then, similar to steps 912 and 913, the subscription module requests the verification module to perform permission verification. If the permission verification passes, the subscription data module saves the information of the dial component and the task information (takeout) and real-time status (status information is a node or node name) subscribed to by the dial component.

[0350] Understandably, step 911b may be performed simultaneously with step 911a, or it may be performed earlier than step 911a.

[0351] When a user orders food delivery through a food delivery app, the first electronic device initiates the delivery task. Assuming the user submits the order, the nodes in this task can be sequentially included as follows: Pending payment (referred to as the first node), Order accepted (referred to as the second node), Picking up (referred to as the third node), Arrived at the store (referred to as the fourth node), Delivery in progress (referred to as the fifth node), and Delivered (referred to as the sixth node), totaling six nodes.

[0352] Step 921: Food delivery apps send a pending payment status message (an example of a real-time status message in the first node) to the real-time notification service module via the real-time interface module. This pending payment status message can carry information such as the amount to be paid. The pending payment status message can be created by the food delivery app or originate from the food delivery app's server.

[0353] Step 922: The Real-Time Notification Service module sends the pending payment status message to both the display entry and the first component. The real-time status in the real-time status message is displayed as a window in the notification center, status bar, lock screen, and unlock screen.

[0354] Step 923: After receiving the real-time status message to be paid, the analysis module in the first component parses the task information to find that it is a food delivery app, and then queries the subscription data module for the subscription information of the food delivery app.

[0355] In this embodiment, the subscription data module queries whether the first theme component, the second theme component, and the watch face component have subscribed to food delivery apps, and returns relevant information about the subscriptions of the first theme component, the second theme component, and the watch face component to the analysis module. For example, the relevant information may be shown in Table 3.

[0356] Table 3

[0357] Step 924: When a food delivery app is subscribed to, the first component queries the rule data module for the first and second rules corresponding to the food delivery app.

[0358] The analysis module, based on the first rule and the relevant information subscribed to by the first topic component, the second topic component, and the dial component, determines which data fields in the real-time status message pending payment, excluding the data field carrying task information, can be parsed. In this embodiment, the data fields carrying "pending payment" information and "amount 25.5 yuan" information can both be parsed.

[0359] The analysis module parses the data field carrying the information "to be paid" and "amount 25.5 yuan" according to the second rule, and obtains the node (or node name) "to be paid" and the information "amount 25.5 yuan" related to the node (or node name).

[0360] In some embodiments, the analysis module may further save the parsed results to the live data module to prevent the loss of parsed results due to a sudden power outage or shutdown of the first electronic device.

[0361] Step 925: After the analysis module completes the parsing, it sends the subscriber list and parsing results to the assembly module.

[0362] Step 926: The assembly module queries the subscription data module for the content subscribed by each subscriber in the subscriber list, as shown in Table 3.

[0363] According to Table 3, the assembly module combines the "to be paid" information and the "amount 25.5 yuan" information together for the first and second theme components, and extracts the "to be paid" information separately for the dial component.

[0364] For example, when the first electronic device experiences a power outage or shutdown before step 925, after the first electronic device restarts, the process may further include: step 9261: the assembly module extracts the subscriber list and parsing results from the live data module.

[0365] Step 927: The assembly module sends the real-time status of each subscriber's subscription to the subscription module.

[0366] Step 9281: The subscription module forwards its subscription status "pending payment" and "amount 25.5 yuan" to the first topic component.

[0367] The first theme component determines the initial image corresponding to the payable node under the food delivery task as the astronaut holding a plaque, based on the mapping table between tasks, nodes (or node names) and initial images.

[0368] The first theme component combines "Pending Payment" and "Amount 25.5 Yuan" with the initial image to generate a real-time status image.

[0369] Step 9282: The first theme component sends the real-time status image to the display entry for display.

[0370] In some embodiments, the real-time status message may also include the application's icon and / or product information. Accordingly, the first component may parse the application's icon and / or product information from the real-time status message and send it to subscribers to be displayed in the real-time status image, further enhancing the user experience.

[0371] Figure 10(1a) shows an example of a real-time status image of a first node displayed by a first electronic device. The main element in the real-time status image displayed on the phone's always-on screen is an astronaut. To the left of the astronaut in the real-time status image is an icon of a food delivery app and a picture of the food ordered by the user. The rectangular sign in the astronaut's hand shows that the current real-time status of the food delivery is 25.5 yuan pending payment. It should be noted that in reality, the area outside the real-time status image in the always-on screen shown in Figure 10(1a) can be black. Here, for the sake of illustration, it is not filled with black. The following embodiments are similar.

[0372] Step 9281a is similar to step 9281, and step 9282a is similar to step 9282.

[0373] Step 911b: The subscription module forwards its subscription status "Amount 25.5 yuan" to the dial component.

[0374] The dial component determines that the initial image corresponding to the payment node under the food delivery task is a panda holding a sign, based on the mapping table between tasks, nodes (or node names) and initial images.

[0375] The dial component combines the "to be paid" message with the initial image to generate a real-time status image.

[0376] Step 9282: The dial component sends the real-time status image to the display entry for display.

[0377] An example of the watch displaying the real-time status image of the first node is shown in Figure 10(1b). The main element of the real-time status image displayed on the watch face's always-on display screen is a panda. To the left of the panda in this real-time status image is the icon (logo) of a food delivery app, and to the right is a picture of the food ordered by the user. The panda's belly displays the current real-time status of the food delivery as pending payment.

[0378] The real-time status display method for the other nodes in the food delivery task is similar to that of the first node, and steps 921 to 9282, 9282a, and 9282b are executed.

[0379] For example, an example of the real-time status image of the second node displayed by the first electronic device is shown in Figure 10(2a). The difference between this example and the one shown in Figure 10(1a) is that: 1) the real-time status image is floating on the lock screen interface, and the astronaut is wearing a chef's hat. The node (or node name) is marked as "order accepted," and the information related to the node (or node name) is the estimated delivery time, such as "expected delivery at 13:10"; 2) Window 13 is also displayed in the upper left corner of the lock screen interface, and the node (or node name) contained in Window 13 is also marked as "order accepted." It can be seen that the real-time status image of the astronaut floating on the lock screen interface is more attractive to the user than Window 13.

[0380] An example of the watch displaying a real-time status image of the second node is shown in Figure 10(2b). The difference between this example and the one shown in Figure 10(1b) is that the panda in the real-time status image is wearing a chef's hat and the node (or node name) is marked as having accepted an order.

[0381] For example, an example of the real-time status image of the third node displayed by the first electronic device is shown in Figure 10(3a), which differs from the example shown in Figure 10(2a) in that the astronaut in the real-time status image is not wearing a chef's hat and is riding a rocket, and the node (or node name) is in the process of picking up goods.

[0382] An example of the watch displaying a real-time status image of a third node is shown in Figure 10(3b). The difference between this example and the one shown in Figure 10(2b) is that the real-time status image is displayed on the off screen, the panda is not wearing a chef's hat, and the node (or node name) is in the process of picking up goods.

[0383] For example, an example of the first electronic device displaying a real-time status image of the fourth node is shown in Figure 10(4a), which differs from the example shown in Figure 10(3a) in that the astronaut in the real-time status image is in a restaurant and the node (or node name) is "arrived".

[0384] An example of the watch displaying the real-time status image of the fourth node is shown in Figure 10(4b). The difference between this example and the one shown in Figure 10(3b) is that the panda in the real-time status image is in the restaurant, and the node (or node name) is "arrived at the restaurant".

[0385] For example, an example of the real-time status image of the fifth node displayed by the first electronic device is shown in Figure 10(5a), which differs from the example shown in Figure 10(4a) in that the astronaut in the real-time status image is carrying a package containing food and traveling in a rocket, and the node (or node name) is in the delivery process.

[0386] An example of the watch displaying the real-time status image of the fifth node is shown in Figure 10(5b). The difference between this example and the one shown in Figure 10(4b) is that the panda in the real-time status image is holding a package containing food, and the node (or node name) is in the delivery phase.

[0387] For example, an example of the real-time status image of the sixth node displayed by the first electronic device is shown in Figure 10(6a), which differs from the example shown in Figure 10(5a) in that the rocket has shut down in the real-time status image, the astronaut has arrived at a house, and the node (or node name) is marked as delivered.

[0388] An example of the watch displaying the real-time status image of the sixth node is shown in Figure 10(6b). The difference between this example and the one shown in Figure 10(5b) is that a small house is also displayed in the real-time status image, and the node (or node name) is marked as delivered.

[0389] In some embodiments, the real-time status image displayed on the watch face may also include information related to the node (or node name), such as the amount to be paid, the estimated delivery time, etc.

[0390] In some embodiments, the watch face may also display information such as altitude, steps, and time.

[0391] In some embodiments, the subscription module may also have caching and querying functions, allowing the topic component to query and request cached real-time status. For example, if the first electronic device restarts its system while the topic component is displaying the real-time status image of the first node, the system restart of the first electronic device may trigger the topic component to send a query request to the subscription module in the first component. If the subscription module caches the real-time status of the first node, it can return the real-time status of the first node it subscribed to to the topic component. After receiving the real-time status of the first node, the topic component can continue to display the real-time status image of the first node. When the subscription module caches the real-time status of the second node, it can return the real-time status of the second node it subscribed to to the topic component. After receiving the real-time status of the second node, the topic component can continue to display the real-time status image of the second node, and so on.

[0392] Another method for displaying the real-time status of an application, as shown in FIG11a, is provided in this application embodiment. This method can be applied to a first electronic device, which initiates a first task of the application, the first task comprising at least two nodes. The method for displaying the real-time status of the application may include:

[0393] Step 1101: Obtain the real-time status of each node in at least two nodes.

[0394] In this embodiment of the application, the real-time status of each node among the at least two nodes included in the first task may include the node name. The real-time status of each node among the at least two nodes included in the first task may also include information related to the node or the node name.

[0395] For example, the first task is a ride-hailing task. The real-time status of the first node among the at least two nodes included in the ride-hailing task may include the node name "order accepted". The real-time status of the first node may also include information related to "order accepted", such as "vehicle type xxx", "color of vehicle", "license plate xxxxxxxxxx", "estimated waiting time x minutes", etc.

[0396] In some embodiments, the real-time status of the current node can be obtained by parsing the real-time status message, as detailed in step 501 of the embodiment shown in Figure 5a.

[0397] In some embodiments, parsing the real-time status message to obtain the real-time status of the current node may include:

[0398] Parse the real-time status messages to obtain the information of the first task. See step 5011 for the method of obtaining the information of the first task.

[0399] Based on the information matching rules of the first task, the real-time status message of the current node is parsed to obtain the real-time status of the current node. See step 5012 for the method of obtaining the real-time status of the first node. For the rules, see the examples of the rules, the first rule, and the second rule in step 5012 above. For parsing the real-time status message of the current node, see the examples of parsing the real-time status message of the first node in the aforementioned embodiments.

[0400] In some embodiments, the first task is time-sensitive. For example, as shown in Figure 11b, the first electronic device initiates a task (such as food delivery) in response to a user's operation on an APP (such as a food delivery APP). The task may include multiple nodes executed sequentially, from node A to node E (such as food delivery including payment, order acceptance, pickup, delivery and signature nodes in sequence).

[0401] When the task reaches node A, the first electronic device acquires the real-time status of node A; when the task reaches node B, the first electronic device acquires the real-time status of node B; when the task reaches node C, the first electronic device acquires the real-time status message of node C; when the task reaches node D, the first electronic device acquires the real-time status of node D; when the task reaches node E, the first electronic device acquires the real-time status of node E; and so on. The method of acquiring the real-time status message can be detailed in the relevant descriptions of the foregoing embodiments, such as the method by which the first electronic device acquires the real-time status of the first node and the method by which the first electronic device acquires the real-time status of the second node in the embodiment shown in Figure 4.

[0402] Step 1102: In response to acquiring the real-time status of at least one of the two nodes, perform the following steps:

[0403] Obtain the real-time status image of the current node based on its real-time status.

[0404] Displays the real-time status image of the current node. The real-time status image of the current node can contain subject elements and status elements, and the status elements correspond to the real-time status of the current node.

[0405] Among them, the subject elements in the real-time status images of at least two nodes are the same.

[0406] For example, the subject element and status element can be found in the relevant description of step 403 in the foregoing embodiments.

[0407] In some embodiments, steps 1102 and 1101 may be executed in an overlapping manner, as shown in FIG11b, where the first electronic device executes step 1102 after executing step 1101 at node A and before executing step 1101 at node B.

[0408] In some embodiments, step 1102 may include:

[0409] Step 11021: Obtain the real-time status image of the current node based on its real-time status.

[0410] For example, as shown in Figure 11b, the task includes nodes A to E: obtain the real-time state image of node A based on the real-time state of node A, obtain the real-time state image of node B based on the real-time state of node B, obtain the real-time state image of node C based on the real-time state of node C, obtain the real-time state image of node D based on the real-time state of node D, and obtain the real-time state image of node E based on the real-time state of node E.

[0411] For example, the theme element in the real-time status image of the current node can be the same as the interface theme element of the first electronic device. The interface theme element can be a theme element specified by the user for display on any one or a combination of the lock screen, unlock screen, or always-on screen. For example, if the interface theme element displayed on the lock screen of the first electronic device is a pet, the theme element in the real-time status image of the current node can also be a pet, and so on. As another example, if the user specifies that the interface theme element of the lock screen of the first electronic device is a pet, the interface theme element of the unlock screen is a landscape, and the interface theme element of the always-on screen is a dog, then the theme element in the real-time status image of the current node can be one of a pet, a landscape, or a dog, and the real-time status image of the current node can be displayed on any one or a combination of the lock screen, unlock screen, or always-on screen. For example, the real-time status image of the previous node can display theme elements on the lock screen, unlock screen, or always-on screen in combination; for example, the real-time status image of the previous node can display theme elements such as a dog on the lock screen, unlock screen, and always-on screen.

[0412] In some embodiments, obtaining the real-time status image of the current node based on its real-time status can be as shown in Figure 11c, including:

[0413] Step 110211: Obtain the initial image containing the subject elements.

[0414] This step can be found in step 502 and the relevant description in Table 1 of the foregoing embodiments.

[0415] In some embodiments, obtaining an initial image containing subject elements may include:

[0416] Retrieve the interface theme elements for the user's signed-up agreement;

[0417] The image corresponding to the real-time state of the current node in the resource library of the interface theme elements is used as the initial image.

[0418] For example, the aforementioned interface theme element can be a wallpaper specified by the user.

[0419] For example, a theme component can provide multiple resource libraries corresponding to different interface theme elements. Alternatively, an interface theme element can have a resource library containing different images (or multiple images), all of which contain that interface theme element. For instance, a mobile phone's (an example of an electronic device) theme settings interface displays multiple theme names, each linking to a resource library providing images. These theme names specify what interface theme elements are in the linked resource library. In some embodiments, a user can select the corresponding interface theme element by clicking on the theme name; in this case, the user can use the interface theme element's resource library without a subscription. In some embodiments, when a user selects an interface theme element, they further need to pay for the selected interface theme element to use it. In this case, the user needs a subscription to use the interface theme element's resource library. In response to a user subscribing to an interface theme element, the lock screen, unlock screen, and always-on screen displayed by the electronic device can all contain the subscribed interface theme element, along with real-time status images for different tasks.

[0420] In some embodiments, a UI theme element may also correspond to a mapping table. This mapping table indicates the correspondence between different tasks and / or status information and corresponding images in the UI theme element's resource library. In response to a user selecting a UI theme element, the images displayed on each interface are determined according to the mapping table. This mapping table may also indicate the correspondence between the lock screen, unlock screen, and always-on screen and corresponding images in the UI theme element's resource library.

[0421] In some embodiments, the initial image containing the theme elements may differ from the user-signed interface theme elements. For example, when the electronic device does not receive a real-time status message from the application, the lock screen may display a wallpaper set by the user, assuming the wallpaper presents a landscape image. When the electronic device receives a real-time status message from the application, the lock screen may switch to the application's real-time status image (see the description in the foregoing embodiments). The theme elements of this real-time status image are different from those of the wallpaper, such as an astronaut as the theme element in the real-time status image.

[0422] In some embodiments, users may sign up for theme elements, which may be different from the interface theme elements.

[0423] In some embodiments, theme elements are similar to interface theme elements. A theme element can correspond to a resource library and a mapping table. When a user selects a theme element, it also means that the initial image for different states of different tasks has been determined.

[0424] Step 110212: Combine the real-time state of the current node with the initial image to obtain the real-time state image of the current node.

[0425] See the description of the real-time status image in step 402 of the foregoing embodiments.

[0426] In some embodiments, after parsing the real-time status message of the current node to obtain the information of the first task, the process may further include:

[0427] Determine if the first task has been subscribed to.

[0428] This step can be referred to in the example illustration of the first electronic device determining whether a task has been subscribed in step 5012 of the foregoing embodiments. In some embodiments, the first electronic device may also determine whether a first task has been subscribed through stored subscription information. When a task is subscribed, it is equivalent to all applications used to implement that task being subscribed.

[0429] For example, when a food delivery task is subscribed to, it can indicate... All food delivery tasks created by food delivery apps are subscribed to. For example, a subscriber can subscribe to the real-time status of all or part of the nodes of a task. For instance, a task may have nodes A, B, and C; nodes A and C might be subscribed to by user A, and nodes A, B, and C might be subscribed to by user B. For example, all or part of the information of a node in a task can also be subscribed to, or in other words, all or part of the real-time status of a node can also be subscribed to. For example, different subscribers may subscribe to the same, partially the same, or none of the real-time status of the current node. For example, a task may have nodes A, B, and C. The total state information of node A may include a1-a5. Subscriber A and subscriber B may both subscribe to state information a2, a3, and a4 in node A. Alternatively, subscriber A may subscribe to state information a1, a2, and a3 in node A, while subscriber B may subscribe to state information a3 and a4. Another possibility is that subscriber A subscribes to state information a1, a2, and a3 in node A, while subscriber B subscribes to state information a4 and a5 in node A, and so on.

[0430] Accordingly, the process of parsing the real-time status message of the current node according to the information matching rules of the first task to obtain the real-time status of the current node may include: when the first task is subscribed to, parsing the real-time status message of the current node according to the subscription content and the information matching rules of the first task to obtain the real-time status of the current node. For details, please refer to the example description of parsing the real-time status message of the first node in step 5012 of the aforementioned embodiments. For example, when the first task is not subscribed to, the real-time status of the current node can be displayed in a window format, as shown in Figures 1g, 1n-1o.

[0431] In some embodiments, the above-described method of parsing the real-time status message of the current node according to the matching rules between the subscribed content and the information of the first task when the first task is subscribed to, to obtain the real-time status of the current node, may include: when the first task is subscribed to by a first subscriber, parsing the real-time status message of the current node according to the matching rules between the information of the first task and the content subscribed by the first subscriber, to obtain the real-time status of the current node. For details, please refer to the relevant descriptions in the foregoing embodiments. For example, the first subscriber may be the aforementioned second component. Specifically, please refer to the example description of how the first component parses the real-time status message of the first node according to the matching rules between the subscribed content and the subscribed scenario when the second component subscribes.

[0432] For example, if the first task is subscribed to by the first subscriber, the first task may also be subscribed to by other subscribers. If the content subscribed to by other subscribers is overridden by the content subscribed to by the first subscriber (e.g., the state information of a node subscribed to by the first subscriber includes a1, a2, a3, and a4, and the state information of the same node subscribed to by other subscribers also includes a1, a3, and a4), or if the content subscribed to by the first subscriber covers all the content subscribed to by other subscribers, then when parsing the real-time state message of the current node, the parsing can be performed according to the information matching rules of the first task and the content subscribed to by the first subscriber. The parsing result contains the state information corresponding to the content subscribed to by all subscribers. Subsequently, based on the saved subscription information, the state information subscribed to by each subscriber can be extracted from the parsing result and distributed. For example, when the first subscriber subscribes to the real-time status, outstanding payment amount, and last payable time or remaining time in a food delivery task, and other subscribers, such as the second subscriber and the third subscriber, subscribe to the real-time status and outstanding payment amount of the payment node, the first electronic device, after obtaining the real-time status message of the payment node and determining that the first task is a food delivery task, can continue to parse the real-time status message of the payment node according to the rules for matching food delivery tasks and the content subscribed by the first subscriber. This will yield status information subscribed by the first subscriber, such as "Outstanding Payment" (node ​​or node name), "Outstanding Payment Amount XX Yuan," and "Latest Payment Time / Remaining Payment Time." Subsequently, based on the content subscribed by the second subscriber, "Outstanding Payment" can be extracted from the parsing results; based on the content subscribed by the third subscriber, "Outstanding Payment" and "Outstanding Payment Amount XX Yuan" can be extracted from the parsing results, and so on. Alternatively, please refer to the relevant description in the embodiment shown in Figure 9a.

[0433] In some embodiments, when the first task is subscribed to, parsing the real-time status message of the current node according to the matching rules between the subscribed content and the information of the first task to obtain the real-time status of the current node may include:

[0434] If the first task is subscribed to by both the first and second subscribers, the real-time status message of the current node is parsed according to the matching rules between the content subscribed by the second subscriber and the information of the first task.

[0435] The real-time status of the current node is obtained by parsing the results of the real-time status message of the current node and the content subscribed by the first subscriber. The result of parsing the real-time status message of the current node is all or part of the real-time status of the current node contained in the real-time status message of the first node.

[0436] For example, when the content subscribed by the second subscriber overlaps with the content subscribed by the first subscriber—such as when the second subscriber subscribes to the real-time status of the payment node in a food delivery task (payment, amount to be paid, and the last time or remaining time available for payment), and the first subscriber subscribes to the real-time status of the payment node (payment and amount to be paid)—then, after the first electronic device obtains the real-time status message of the payment node and determines that the first task is a food delivery task, it can continue to parse the real-time status message of the payment node according to the rules for matching food delivery tasks and the content subscribed by the second subscriber. This allows it to obtain the real-time statuses subscribed to by the second subscriber, such as "Pending Payment" (node ​​or node name), "Amount to be Paid XX Yuan," and "Latest Time to Pay / Remaining Time to Pay." Subsequently, based on the content subscribed by the first subscriber, it can extract "Pending Payment," "Amount to Pay XX Yuan," etc., from the parsing results. See the relevant description in the embodiment shown in Figure 9a.

[0437] For example, the aforementioned second subscriber could be a topic component.

[0438] In some embodiments, prior to determining whether the first task has been subscribed to, the method may further include:

[0439] Perform permission verification on the subscription request of the first subscriber.

[0440] Specifically, please refer to the relevant description of step 601 in the foregoing embodiments.

[0441] If the verification passes, the first task is subscribed to by the first subscriber.

[0442] Specifically, please refer to the relevant description of step 602 in the foregoing embodiments, and also to the description of subscription in the embodiments shown in Figures 8b, 9a and 9b.

[0443] In some embodiments, the first electronic device may establish a scene-coordinated connection with the second electronic device. The second electronic device may have a second subscriber. If the first task is subscribed to by the second subscriber, the method may further include: obtaining the real-time status of the current node from the result of parsing the real-time status message of the current node according to the content subscribed by the second subscriber, and sending it to the second subscriber so that the second subscriber generates a real-time status image of the current node. In this way, the second electronic device can display the real-time status image of the current node.

[0444] For example, when the content subscribed by the second subscriber is overwritten by the content subscribed by the first subscriber, the real-time status of the current node can be obtained based on the result of parsing the real-time status message of the current node according to the rules and the content subscribed by the first subscriber, and the corresponding real-time status of the current node can be obtained based on the result of parsing the real-time status message of the current node and the content subscribed by the second subscriber, as mentioned above, "the 'pending payment' can be extracted from the parsing result based on the content subscribed by the second subscriber", and so on.

[0445] For example, the second subscriber can refer to the description of the third component in the embodiment shown in Figure 8a, and also to the description of the topic component in the second electronic device in the embodiment shown in Figure 9a. The first electronic device sends the real-time status of the current node to the second subscriber, as described in the description of the first electronic device sending the real-time status to the second topic component in the embodiments shown in Figures 9a and 9b.

[0446] For example, the second electronic device displays a real-time status image of the current node, as shown in Figures 10(1b) to 10(6b).

[0447] In some embodiments, the second subscriber may be located in a second electronic device, which may be connected to the first electronic device in a scene-coordinated manner. The method may further include sending the result of parsing the real-time status message of the current node to the second subscriber. This enables the second subscriber to generate a real-time status image of the current node based on the result of parsing the real-time status message, thereby allowing the second electronic device to display the real-time status image containing the current node.

[0448] For example, when the content subscribed to by the second subscriber overlaps with the content subscribed to by the first subscriber, the first electronic device continues to parse the real-time status message of the current node according to the content subscribed to by the second subscriber and the matching rules of the first task. The result obtained is the real-time status of the current node subscribed to by the second subscriber. The result of the first electronic device sending the parsed real-time status message of the current node to the second subscriber can be found in the aforementioned explanation of the first electronic device sending real-time status to the second electronic device or the second topic component, such as Figure 8a, or Figures 9a and 9b and their related explanations.

[0449] In some embodiments, after parsing the real-time status message of the current node, the process may further include: saving the result of parsing the real-time status message of the current node. For example, saving the result of parsing the real-time status message of the current node can prevent data loss. For instance, if the first electronic device system restarts after parsing the real-time status message of the current node, the first electronic device does not need to perform parsing again and can directly read the saved result of parsing the real-time status message of the current node. For example, see the relevant description of the real-time data module saving the parsing result in the embodiment shown in Figure 9a, such as the relevant description of step 9261.

[0450] In some embodiments, after obtaining the real-time status of the current node, the method may further include: saving the real-time status of the current node. For example, saving the real-time status of the current node can prevent data loss. If the first electronic device has already determined or sent the corresponding real-time status of the current node to each subscriber, and then the first electronic device restarts, the first electronic device does not need to parse the real-time status message of the current node again, nor does it need to determine the corresponding real-time status of the current node for each subscriber again. It can directly read the saved real-time status of the current node and distribute it to each subscriber, as illustrated in the example of the caching function of the subscription module in the foregoing embodiments.

[0451] In some embodiments, obtaining the real-time status of the current node may include: obtaining the real-time status of the current node based on the saved results after a system restart. For example, see the example description of the query function of the subscription module in the foregoing embodiments.

[0452] Step 11022: Display the real-time status image of the current node. The real-time status image of the current node includes a subject element and a status element. The status element corresponds to the real-time status of the current node. The subject elements are the same in the real-time status images of at least two nodes (e.g., nodes A to E). For details on the status element and subject element, please refer to the relevant descriptions in the foregoing embodiments.

[0453] For example, after obtaining the real-time state of node A, the real-time state image of node A is displayed, which contains state elements corresponding to the real-time state of node A; after obtaining the real-time state of node B, the real-time state image of node B is displayed, which contains state elements corresponding to the real-time state of node B; after obtaining the real-time state of node C, the real-time state image of node C is displayed, which contains state elements corresponding to the real-time state of node C; after obtaining the real-time state of node D, the real-time state image of node D is displayed, which contains state elements corresponding to the real-time state of node D; after obtaining the real-time state of node E, the real-time state image of node E is displayed, which contains state elements corresponding to the real-time state of node E; and so on. The real-time state images of nodes A through E also contain the same theme elements.

[0454] For example, the theme elements may or may not be related to the primary task.

[0455] For example, the first electronic device may sequentially display: real-time status images of node A, node B, node C, node D, and node E, which may contain the same subject element, such as a pet. Furthermore, as shown in Figures 10(1a) to 10(6a), the first electronic device may sequentially display: real-time status images of items pending payment, items accepted for order processing, items being picked up, items arriving at the store, items being delivered, and items delivered, which may contain the same subject element, an astronaut.

[0456] Based on the above technical solution, electronic devices can increase visual appeal and avoid homogenization of experience by displaying real-time status images of the current node. Furthermore, displaying the real-time status of different nodes through images containing the same theme elements can continuously attract users' attention and help increase user stickiness.

[0457] In some embodiments, displaying the real-time status image of the current node may include: displaying the real-time status image of the current node floating on the lock screen interface, as shown in Figure 10(2a).

[0458] In some embodiments, displaying the real-time status image of the current node may include: displaying the real-time status image of the current node on the lock screen, unlock screen and / or screen-off screen, as shown in Figures 10(1a), 10(3a)-10(6a).

[0459] In some embodiments, the method may further include: in response to a user's page-turning operation by swiping the unlock screen, the real-time status image of the current node is moved from the first page of the unlock screen to the second page. As shown in Figures 12a and 12b, the real-time status image "astronaut" moves from the page shown in Figure 12a to the page shown in Figure 12b when the page is turned.

[0460] In some embodiments, the size of the real-time status image of the current node can adaptively increase when it moves from a first page to a second page. For example, the real-time status image "astronaut" shown in FIG12a increases in size when it moves to the page shown in FIG12b to match the blank area. Exemplarily, when the first electronic device moves from a second page to a second page in response to a user's page-turning operation, its size can adaptively decrease. For example, when the real-time status image "astronaut" moves from the page shown in FIG12b to the page shown in FIG12a, its size adaptively decreases to match the blank area of ​​the page shown in FIG12a.

[0461] In some embodiments, the real-time status image of the current node can be displayed in a blank area of ​​the unlock interface, as shown in Figures 12a and 12b.

[0462] In some embodiments, the aforementioned blank area can be automatically obtained by the movement of the icon in the unlock interface. As shown in Figure 13a, when the first electronic device displays the real-time status image of the current node on the unlock interface, the APP icon in the unlock interface moves in the direction indicated by the dotted arrow until, as shown in Figure 13b, the APP icon moves to a suitable position, and the space left by the movement of the APP icon displays the real-time status image of the current node.

[0463] In some embodiments, after the unlock interface stops displaying the real-time status image of the current node, the icon can be moved back to the blank area. For example, after the real-time status image "astronaut" in the unlock interface shown in FIG13b stops displaying, the icon moves back to the previous position shown in FIG1g.

[0464] In some embodiments, the real-time status image of the current node may further include information about the second task. For example, the second task may belong to the same application as the first task; for instance, both the first and second tasks may be initiated by the same application in response to a user's operation. Alternatively, the first and second tasks may belong to different applications, or they may be initiated by different applications in response to a user's operation; for example, the first task may be initiated by a first application in response to a user's operation, and the second task may be initiated by a second application in response to a user's operation.

[0465] For example, the second task may not be time-sensitive. As shown in Figure 14, the real-time status image of the payment node displayed on the screen-off interface includes the theme element of a pet dog and the status element "payment pending 25.5 yuan". The image also includes the current weather information published by the weather app (an example of the second task) and the battery information published by the system (another example of the second task), etc.

[0466] In some embodiments, the method may further include: the information of the second task and the real-time status of the current node may move in the image in response to a user's operation. For example, in the image of the real-time status of the current node, the real-time status of the current node and the information of the second task may be set in cards. For instance, the image may include a card displaying the real-time status of the current node (referred to as the real-time status card) and a card displaying the information of the second task (the second task card). When the user performs a movement operation on the real-time status card and / or the second task card (e.g., moves a finger on one or more cards), the real-time status card and the second task card move accordingly, that is, the real-time status of the current node and the information of the second task move accordingly. For example, when the user places their finger on any one of the real-time status, weather information, or battery information of the node to be paid in the image shown in Figure 14 and slides it to the right or left, the real-time status, weather information, and battery information of the node to be paid may move to the right or left in response to this operation.

[0467] In some embodiments, the method may further include: responding to a user's operation on the real-time status of the current node, jumping to the relevant interface of the application for initiating the task. For example, when a user clicks on the real-time status of the current node in the image of the current node's real-time status, the first electronic device jumps to the relevant application interface. For instance, when the first task is food delivery, if the user clicks on the real-time status of food delivery in the image, the first electronic device jumps to the relevant page of the food delivery app that initiated the first task, and this relevant page may be related to the real-time status of the current node. For example, when the real-time status of the current node is displayed as a card in the image, the user can click on the card to jump to the application page related to the real-time status of the current node. For instance, when a user clicks on the box containing the real-time status of the node to be paid in Figure 14, the electronic device jumps from the current off-screen interface to the payment page of the food delivery app (the app corresponding to the food delivery app logo in Figure 14).

[0468] In some embodiments, before redirecting to the payment page, the electronic device may further include redirecting to an unlock screen. Once the user unlocks the device, the electronic device redirects to the payment page. For example, the unlock screen may be an interface requiring the user to enter a password, image, or fingerprint. After the user unlocks this interface, further operations can be performed on the electronic device.

[0469] In some embodiments, the method may further include: in response to a user's operation on information related to the second task, navigating to an application interface related to the second task. For example, when a user clicks the box containing the battery information shown in Figure 14, the electronic device navigates from the current interface to a system-related interface for the battery.

[0470] In some embodiments, before redirecting to the payment page, the electronic device may further include: redirecting to the unlocking interface; after the user enters and passes the password, the electronic device redirects to the battery's system-related interface.

[0471] In some embodiments, after displaying the real-time status image of the current node, the method may further include: stopping the display of the real-time status image of the current node when the display time meets a preset duration or in response to a user operation. For example, if the user does not perform a payment operation within the preset display time for the real-time status image of the node to be paid in the interface shown in Figure 13b, the interface shown in Figure 13b will stop displaying the real-time status image of the node to be paid.

[0472] In some embodiments, the above-mentioned display of the real-time status image of the current node may include: displaying the real-time status of the current node in the form of a window when displaying the real-time status image, as shown in Figures 10(2b), 12a, 13a and 13b.

[0473] This application provides another method for displaying the real-time status of an application, which can be applied to a second electronic device. The second electronic device, as described in the foregoing embodiments, can establish a scene-coordinated connection with the first electronic device. The first electronic device can initiate a first task (see the relevant description of the first task in the foregoing embodiments for details). The first task may include at least two nodes executed sequentially (see the relevant description of tasks and nodes in the foregoing embodiments for details). In this embodiment, the method for displaying the real-time status of an application is as shown in Figure 15, including:

[0474] Step 1501: Receive the real-time status of the first node sent by the first electronic device. The real-time status of the first node is obtained by the first electronic device based on the real-time status message of the first node. The first node is one of the above at least two nodes.

[0475] In some embodiments, before receiving the real-time status of the first node sent by the first electronic device, the process may further include: sending a subscription request to the first electronic device, the subscription request being used to subscribe to a first task, as shown in steps 911, 911a, and 911b in the embodiments shown in Figures 9a and 9b; correspondingly, receiving the real-time status of the first node sent by the first electronic device may include: if the first task has been successfully subscribed to, receiving the real-time status of the first node sent by the first electronic device, as shown in steps 9281, 9281a, and 9281b in the embodiments shown in Figures 9a and 9b.

[0476] Step 1502: Display the real-time status image of the first node.

[0477] In some embodiments, before displaying the real-time status image of the first node, the following may be included:

[0478] Based on the real-time status of the first node, obtain the corresponding initial image;

[0479] The real-time status of the first node is combined with the acquired initial image to obtain the real-time status image of the first node.

[0480] See steps 110212-110213. For example, see the example of generating the real-time status image of the first node in the foregoing embodiments.

[0481] In some embodiments, displaying the real-time status image of the first node may include: displaying the real-time status image of the first node floating on the lock screen interface, as shown in FIG10(2a).

[0482] In some embodiments, displaying the real-time status image of the first node may include displaying the real-time status image of the first node on the lock screen, unlock screen, or screen-off screen, as shown in Figures 10(1a), 10(3a)-10(6a).

[0483] In some embodiments, the above method may further include: the real-time status image of the first node moves from the first page of the unlock interface to the second page in response to the user's page-turning operation of sliding the unlock interface, as shown in Figures 12a and 12b.

[0484] In some embodiments, the real-time status image of the first node can be displayed in a blank area of ​​the unlock interface, as shown in Figures 12a and 12b.

[0485] In some embodiments, the aforementioned blank area can be automatically obtained by moving the icon in the unlock interface, as shown in Figures 13a and 13b.

[0486] In some embodiments, after the unlocking interface stops displaying the real-time status image of the first node, the icon can be moved back to the blank area, as described in the relevant description in the foregoing embodiments.

[0487] In some embodiments, the real-time status image of the first node may also include information about the second task, as can be seen in the relevant description in the foregoing embodiments, as shown in Figure 14.

[0488] In some embodiments, the above method may further include: the real-time status of the first node and the information of the second task moving in the image in response to the user's operation, as described in the relevant descriptions in the foregoing embodiments.

[0489] In some embodiments, the above method may further include: in response to the user's operation on the real-time status of the first node, jumping to the relevant interface of the application for initiating the task, as described in the foregoing embodiments.

[0490] In some embodiments, the above method may further include: in response to the user's operation on the second task information, jumping to the application interface related to the second task, as can be seen from the relevant description in the foregoing embodiments.

[0491] In some embodiments, after displaying the real-time status image of the first node at the display entry, the method may further include: stopping the display of the real-time status image of the first node after a preset time period, as described in the relevant description in the foregoing embodiments.

[0492] Step 1503: Receive the real-time status of the second node sent by the first electronic device. The real-time status of the second node is obtained by the first electronic device based on the real-time status message of the second node. The second node is another node among the aforementioned at least two nodes. For example, the acquisition and reception of the real-time status of the second node can be performed in the same way or in the same principle as in step 1501.

[0493] Step 1504: Display the real-time status image of the second node; wherein the real-time status image of the first node and the real-time status image of the second node contain the same subject elements, the real-time status image of the first node also contains status elements corresponding to the real-time status of the first node, and the real-time status image of the second node also contains status elements corresponding to the real-time status of the second node. Exemplarily, the subject elements and status elements can be found in the foregoing description. Exemplarily, the method for displaying the real-time status image of the second node can be similar to or the same as step 1502.

[0494] Another method for real-time status display in a second electronic device, as shown in FIG16, provided in this application embodiment, includes:

[0495] Step 1601: Receive the real-time status of the current node sent by the first electronic device, where the current node is one of at least two nodes. The second electronic device establishes a scene collaboration connection with the first electronic device, and the first electronic device initiates a first task of the application, which includes the at least two nodes. The first task may refer to a specific task. The real-time status of the current node can be obtained by the first electronic device based on the current node's real-time status message. For details, please refer to the relevant descriptions in the foregoing embodiments, such as the descriptions in Figures 9a and 9b regarding the second electronic device or watch obtaining the real-time status of the current node from the first electronic device.

[0496] Step 1602: Obtain the real-time status image of the current node based on its real-time status. See the relevant descriptions in the preceding embodiments for details.

[0497] Step 1603: Display the real-time status image of the current node. The real-time status image of the current node may contain subject elements and status elements. The status elements correspond to the real-time status of the current node. The subject elements in the real-time status images of at least two nodes are the same, so that the real-time status images of at least two nodes belong to the same subject, as shown in Figures 10(1b) to 10(6b).

[0498] This application provides a method for notifying an application of its real-time status, as shown in Figure 17, including:

[0499] Step 1701: Receive a real-time status message from the application. The application is running a first task, which includes at least two nodes. The real-time status message indicates the real-time status of one of the at least two nodes. For example, the first component may receive the application's real-time status message from the application; see the description of the real-time status message in the foregoing embodiments for details.

[0500] Step 1702: Obtain the real-time status of the current node from the real-time status message.

[0501] For example, this step may include: obtaining information about the first task and the status information of the current node from the real-time status message according to a preset matching rule. See the foregoing explanation of real-time status message parsing for details.

[0502] Step 1703: Trigger the application's real-time status notification process. The application's real-time status notification process includes:

[0503] Obtain the real-time status image of the current node based on its real-time status.

[0504] Displays the real-time status image of the current node. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node.

[0505] In this configuration, the subject elements in the real-time status images of at least two nodes are identical. See the relevant descriptions in the foregoing embodiments for details.

[0506] For example, the notification process can be used to notify the user of the real-time status of a task by displaying a real-time status image.

[0507] In some embodiments, before step 1702, the method may further include: determining whether the first task has been subscribed to; if so, then performing step 1702. For details regarding the subscription of the first task and the acquisition of the current node's status information related to the subscription, please refer to the relevant descriptions in the foregoing embodiments.

[0508] Another embodiment of the electronic device can be referred to FIG18. As shown in FIG18, the electronic device 1800 may include a processor 1801, a memory 1802, and a communication interface 1803. The processor 1801, the memory 1802, and the communication interface 1803 are coupled to each other. Optionally, the memory 1802 may be used to store instructions executed by the processor 1801, or to store input data required by the processor 1801 to execute instructions, or to store data generated after the processor 1801 executes instructions. The communication interface 1803 may be a transceiver or an input / output interface. When the processor 1801 reads and executes the instructions stored in the memory 1802, the electronic device may implement any of the methods provided in the embodiments of this application. Exemplarily, the electronic device may be the aforementioned first electronic device or the aforementioned second electronic device.

[0509] Optionally, referring to Figure 18, the processor 1801, the memory 1802, and the communication interface 1803 are interconnected via a bus 1804. The bus 1804 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in Figure 18, but this does not indicate that there is only one bus or one type of bus.

[0510] Another embodiment of the first electronic device may include: a first component for implementing any of the methods provided in the above embodiments for displaying the real-time status of the first electronic device. In some other embodiments, the first electronic device may also include the hardware system of FIG2 and the remaining parts of the software system shown in FIG3, excluding the first component.

[0511] The first electronic device is used to initiate a first task, which may include at least two nodes, as detailed in the foregoing embodiments. The first component can be used to acquire real-time status messages of each of the at least two nodes, and obtain the real-time status of each node based on the real-time status messages. It can also, in response to acquiring the real-time status message of one of the at least two nodes, obtain a real-time status image of the current node based on the real-time status message of the current node. See the foregoing embodiments for further details.

[0512] The first component can be used to parse the real-time status message of the current node to obtain the information of the first task and the real-time status of the current node. For example, the first component can be used to parse the real-time status message of the current node to obtain the information of the first task; and according to the matching rules of the information of the first task, parse the real-time status message of the current node to obtain the real-time status of the current node.

[0513] The first component can be used to parse the real-time status message of the current node to obtain the information of the first task; and to parse the real-time status message of the current node according to the information matching rules of the first task to obtain the real-time status of the current node. For details, please refer to the relevant descriptions in the foregoing embodiments. For example, the first component can be used to parse the real-time status message of the first node (one of the at least two nodes mentioned above) to obtain the information of the first task; and to parse the real-time status message of the first node according to the information matching rules of the first task to obtain the real-time status of the first node. Exemplarily, the first component can be used, after parsing the real-time status message of the current node and obtaining the information of the first task, to determine whether the first task has been subscribed to; if the first task has been subscribed to, to parse the real-time status message of the current node according to the subscribed content and the information matching rules of the first task to obtain the real-time status of the current node. For example, the first component can be used, after parsing the real-time status message of the first node and obtaining the information of the first task, to determine whether the first task has been subscribed to, and, if the first task has been subscribed to, to parse the real-time status message of the first node according to the subscribed content and the information matching rules of the first task.

[0514] The first component can also be used to assemble the real-time state of the first node based on the subscribed content and the result of parsing the real-time state message of the first node, after continuing to parse the real-time state message of the first node.

[0515] The first component can also be used to parse the real-time status message of the current node and obtain the real-time status of the current node, based on the matching rules between the content subscribed by the first subscriber and the information of the first task, when the first task is subscribed to by the first subscriber.

[0516] The first component can also be used to parse the real-time status message of the current node according to the matching rules between the content subscribed by the second subscriber and the information of the first task when the first task is subscribed by the first subscriber and the second subscriber; and to obtain the real-time status of the current node according to the result of parsing the real-time status message of the current node and the content subscribed by the first subscriber, wherein the result of parsing the real-time status message of the current node is all or part of the real-time status in the real-time status message of the first node.

[0517] The first component can also be used to: perform permission verification on the subscription request of the first subscriber before determining whether the first task is subscribed; if the verification passes, the first task is subscribed to by the first subscriber.

[0518] The first electronic device can establish a scene-coordinated connection with the second electronic device. The second electronic device can have a second subscriber. When the first task is subscribed to by the second subscriber, the first component can also be used to: obtain the real-time status of the current node from the result of parsing the real-time status message of the current node based on the content subscribed to by the second subscriber, and send it to the second subscriber. This enables the second subscriber to generate a real-time status image of the current node, thereby allowing the second electronic device to collaboratively display the real-time status image of the current node. The number of status elements corresponding to the real-time status of the current node collaboratively displayed by the second electronic device can be less than or equal to the number of status elements corresponding to the real-time status of the current node displayed by the first electronic device.

[0519] The aforementioned second subscriber may be located in a second electronic device, which may be connected to the first electronic device in a scene-coordinated manner. The first component may also be used for:

[0520] Based on the rules for matching the content subscribed by the second subscriber with the information of the first task, the real-time status message of the current node is parsed, and the result of parsing the real-time status message of the current node is sent to the second subscriber. This enables the second subscriber to generate a real-time status image of the current node based on the result of parsing the real-time status message, thereby allowing the second electronic device to collaboratively display the real-time status image of the current node. In this case, the number of status elements corresponding to the real-time status of the current node collaboratively displayed by the second electronic device may be greater than or equal to the number of status elements corresponding to the real-time status of the current node displayed by the first electronic device.

[0521] The first component can also be used to save the result of parsing the real-time status message of the current node after parsing the real-time status message of the current node.

[0522] The first component can also be used to save the real-time state of the current node after obtaining the real-time state of the current node as described above.

[0523] The first component can also be used to obtain the real-time status of the current node based on the saved results after a system restart. See the relevant descriptions in the foregoing embodiments for details.

[0524] The first component, as detailed in the foregoing embodiments, can be used to acquire the real-time status message of the first node and display the real-time status image of the first node at the display entry. The real-time status of the first node is obtained from the real-time status message of the first node, and the real-time status message of the first node is related to the first node. The first component can also be used to acquire the real-time status message of the second node, obtain the real-time status of the second node based on the real-time status message of the second node, and display the real-time status image of the second node. The first node and the second node are different nodes in a task. The second node is generated based on the completion of the task of the first node. This task can be initiated by the first electronic device in response to the user's operation on the application. The real-time status image of the second node and the real-time status image of the first node belong to the first topic.

[0525] In some embodiments, the first electronic device may further include a second component. The first component can be used to obtain the real-time status of the current node based on the real-time status message of the current node, and send it to the second component. The second component can be used to generate a real-time status image of the current node based on the real-time status of the current node. For example, before displaying the real-time status image at the display entry, the second component can obtain a corresponding initial image based on the information of the first task and the real-time status of the current node; and combine the real-time status of the current node with the initial image to obtain the real-time status image of the current node. The generation of the real-time status image of the current node can be found in the relevant descriptions in the foregoing embodiments.

[0526] The second component is detailed in the description of the foregoing embodiments. The second component can be used to select an appropriate initial image based on the first task information and the real-time status of the current node, after the first component has obtained the information of the first task and the real-time status of the current node; and combine the appropriate initial image with the real-time status of the first node to generate a real-time status image of the first node.

[0527] Before the first component determines whether the first task has been subscribed to, the second component can be used to subscribe to the first task from the first component. In some embodiments, the first subscriber can also initiate a subscription request after determining whether the first task has been subscribed to. For example, the second component can be used to subscribe to the first task from the first component after the first component has determined whether the first task has been subscribed to.

[0528] The second component can be used to initiate a subscription request to the first component, which includes information about the first task and the content to be subscribed; see the relevant description in the foregoing embodiments for details.

[0529] Accordingly, the first component can be used to verify the permissions of the subscription request. If the permission verification passes, the first task is subscribed to by the second component. For example, when the first task is subscribed to, the first component can also be used to save information about the second component, information about the first task, and content subscribed by the second component.

[0530] The aforementioned first component can be used to determine whether the first task has been subscribed based on the information saved in the second component and the information of the first task.

[0531] The first component can also be used to obtain a message indicating the completion of the first task if the current node has not been executed by the user within a preset time period after the real-time status image of the current node is displayed in the display entry. For example, this message can be created by the application or received from the application's server.

[0532] The first component can be used to send the real-time status of the current node to the second electronic device after receiving the real-time status message of the current node. For example, the first component can be used to send the real-time status of the first node to the second electronic device after receiving the real-time status message of the first node; the first component can also be used to send the real-time status of the second node to the second electronic device after receiving the real-time status message of the second node.

[0533] The first component can be used to receive a subscription request sent by the second electronic device before sending the real-time status of the current node to the second electronic device, and to perform permission verification based on the subscription request; the first component can also be used to send the real-time status of the current node to the second electronic device if the permission verification passes. For example, the first component can be used to receive a subscription request sent by the second electronic device before sending the real-time status of the first node to the second electronic device, and to perform permission verification based on the subscription request; the first component can also be used to send the real-time status of the first node and the real-time status of the second node to the second electronic device if the permission verification passes.

[0534] The first task mentioned above may be time-sensitive.

[0535] This application provides a system for displaying the real-time status of an application, which may include the aforementioned first electronic device and the aforementioned second electronic device. A scene collaboration connection may be established between the first electronic device and the second electronic device. The first electronic device may be used to initiate a first task of the application, which may include at least two nodes. The first electronic device may also be used to execute:

[0536] Obtain the real-time status message of the first node, which is one of the above at least two nodes, for example, see the relevant description in the foregoing embodiments;

[0537] The real-time status of the first node is obtained based on the real-time status message of the first node, and the real-time status of the first node is sent to the second electronic device through scene collaboration connection, for example, see the relevant description in the foregoing embodiment;

[0538] The second electronic device can be used to perform:

[0539] Receive the real-time status of the first node and generate a real-time status image of the first node, as can be seen in the relevant description in the foregoing embodiments;

[0540] Display the real-time status image of the first node, for example, refer to the relevant description in the foregoing embodiments;

[0541] The first electronic device can also be used to perform:

[0542] Obtain the real-time status message of the second node, which is another node among the above at least two nodes, for example, see the relevant description in the foregoing embodiments;

[0543] The real-time status of the second node is obtained based on the real-time status message of the second node, and the real-time status of the second node is sent to the second electronic device through scene coordination connection, for example, see the relevant description in the foregoing embodiment;

[0544] The second electronic device can also be used to perform:

[0545] Receive the real-time status of the second node and generate a real-time status image of the second node, as can be seen in the relevant description in the foregoing embodiments;

[0546] Display the real-time status image of the second node, for example, refer to the relevant description in the foregoing embodiments;

[0547] The real-time status image of the first node and the real-time status image of the second node may contain the same subject elements. The real-time status image of the first node also contains status elements corresponding to the real-time status of the first node, and the real-time status image of the second node also contains status elements corresponding to the real-time status of the second node. For example, please refer to the relevant description in the foregoing embodiments.

[0548] The first electronic device can be used to implement any of the methods for displaying the real-time status of the application provided in the above embodiments, as detailed in the description of the first electronic device in the foregoing embodiments. The second electronic device can establish a scene collaboration connection with the first electronic device and can be used to collaboratively display real-time status images, as detailed in the description of the second electronic device in the foregoing embodiments.

[0549] In some embodiments, the system for displaying the real-time status of an application may further include a third electronic device, which may be any of the electronic devices provided in the foregoing embodiments. This third electronic device may be similar to the second electronic device, acquiring the real-time status of the application from the first electronic device and cooperating with the first and second electronic devices to display a real-time status image of the application. The subject of the real-time status image of the application displayed by the third electronic device may differ from that of the first or second electronic device; this is not limited here.

[0550] In some embodiments, the system for displaying the real-time status of an application may not be limited to the first electronic device, the second electronic device, and the third electronic device, but may also include a fourth electronic device, a fifth electronic device, and so on. The fourth electronic device and the fifth electronic device may be any of the electronic devices provided in the foregoing embodiments. These electronic devices, such as the fourth and fifth electronic devices, may be similar to the second electronic device, acquiring the real-time status of the application from the first electronic device and collaboratively displaying the real-time status image of the application with the first, second, and third electronic devices. The real-time status images displayed by each electronic device in the system may belong to the same theme (e.g., containing the same thematic elements) or to different themes (e.g., containing different thematic elements).

[0551] The chip provided in this application embodiment can be any chip or chip system in the aforementioned electronic device that has the function of implementing the method provided in this application embodiment. Exemplarily, the chip may integrate a processor, a communication interface, and a memory. The memory stores computer programs or instructions, and the processor is connected to the memory through the communication interface to read and execute the computer programs or instructions stored in the memory to implement any of the methods provided in this application embodiment. In some embodiments, the memory may be omitted from the chip; in this case, the processor can call the computer programs or instructions from an external storage device through the communication interface. In some embodiments, the chip system may be composed of chips. Exemplarily, the chip system may include a processor chip, a communication interface chip, and a memory chip. The processor chip is connected to the memory chip through the communication interface chip to read and execute the computer programs or instructions stored in the memory chip to implement any of the methods provided in this application embodiment. In other embodiments, the chip system may include chips and other discrete devices.

[0552] It should be understood that the embodiments described in this application are only some embodiments, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0553] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” as used herein is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character “ / ” in this document generally indicates that the preceding and following related objects are in an “or” relationship.

[0554] In a specific implementation, the present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program, when executed, may include some or all of the steps in the various method embodiments provided by the present invention. The storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0555] In a specific implementation, the present invention also provides a computer program product, wherein the computer program product includes executable instructions, which, when executed on a computer, cause the computer to perform some or all of the steps in the various method embodiments provided by the present invention.

[0556] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present invention.

[0557] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the device embodiments and terminal embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

Claims

1. A method for displaying the real-time status of an application, characterized in that, Applied to a first electronic device, the first electronic device being used to initiate a first task of the application, the first task comprising at least two nodes, the method includes: Obtain the real-time status of each of the at least two nodes; In response to acquiring the real-time status of one of the at least two nodes, the following steps are performed: The real-time status image of the current node is obtained based on the real-time status of the current node; The real-time status image of the current node is displayed. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node. Among them, the subject elements in the real-time status images of each of the at least two nodes are the same.

2. The method according to claim 1, characterized in that, The theme elements in the real-time status image of the current node are the same as the interface theme elements of the first electronic device. The interface theme elements are theme elements specified by the user for display on any one or a combination of the lock screen, unlock screen, or screen-off screen.

3. The method according to claim 1 or 2, characterized in that, The display of the real-time status image of the current node includes: The real-time status image of the current node is displayed on the lock screen, unlock screen, or always-on screen.

4. The method according to claim 3, characterized in that, Also includes: The unlock interface responds to the user's page-turning operation by swiping the unlock interface, moving the real-time status image of the current node from the first page of the unlock interface to the second page.

5. The method according to any one of claims 1-4, characterized in that, After displaying the real-time status image of the current node, the method further includes: When the display time meets the preset duration or in response to the user's operation, stop displaying the real-time status image of the current node.

6. The method according to claim 1, characterized in that, The step of obtaining the real-time status image of the current node based on the real-time status of the current node includes: Obtain an initial image containing the aforementioned subject elements; The real-time status of the current node is combined with the initial image to obtain the real-time status image of the current node.

7. The method according to claim 6, characterized in that, The step of obtaining an initial image containing the subject element includes: Retrieve the interface theme elements for the user's signed-up agreement; The image corresponding to the real-time state of the current node in the resource library of the interface theme elements is used as the initial image.

8. The method according to claim 2 or 7, characterized in that, The interface theme element is the wallpaper specified by the user.

9. The method according to claim 1, characterized in that, A scene collaboration connection is established between the first electronic device and the second electronic device. After obtaining the real-time status of each of the at least two nodes, the method further includes: The real-time status of the current node is sent to the second electronic device through the scenario collaborative connection.

10. The method according to claim 9, characterized in that, Before sending the real-time status of the current node to the second electronic device through the scenario collaborative connection, the method further includes: When the second electronic device subscribes to the first task, the real-time status of the current node is sent to the second electronic device through the scenario collaboration connection.

11. A method for notifying an application of its real-time status, characterized in that, include: Receive a real-time status message from an application, wherein a first task is running in the application, the first task comprising at least two nodes, and the real-time status message of the application indicates the real-time status of one of the at least two nodes. Obtain the real-time status of the current node from the real-time status message; The notification process for the real-time status of the application is triggered, and the notification process for the real-time status of the application includes: The real-time status image of the current node is obtained based on the real-time status of the current node; The real-time status image of the current node is displayed. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node. Among them, the subject elements in the real-time status images of each of the at least two nodes are the same.

12. The method according to claim 11, characterized in that, The step of obtaining the real-time status of the current node from the real-time status message includes: According to the preset matching rules, the information of the first task and the status information of the current node are obtained from the real-time status message.

13. The method according to claim 11 or 12, characterized in that, Before obtaining the real-time status of the current node from the real-time status message, the method further includes: If the first task is subscribed to, the real-time status of the current node is obtained from the real-time status message.

14. A method for displaying the real-time status of an application, characterized in that, The method is applied to a second electronic device, which establishes a scene-coordinated connection with a first electronic device. The first electronic device initiates a first task of the application, which includes at least two nodes. Receive the real-time status of the current node sent by the first electronic device, wherein the current node is one of the at least two nodes; The real-time status image of the current node is obtained based on the real-time status of the current node; The real-time status image of the current node is displayed. The real-time status image of the current node includes subject elements and status elements, and the status elements correspond to the real-time status of the current node. Among them, the subject elements in the real-time status images of each of the at least two nodes are the same.

15. An electronic device, characterized in that, include: One or more processors and a memory, the one or more processors being coupled to the memory, the memory being used to store computer program code, the computer program code including computer instructions, wherein when the one or more processors execute the computer instructions, the electronic device performs the method as described in any one of claims 1-14.

16. A chip, characterized in that, include: A processor and a communication interface, wherein the processor invokes a computer program or instruction through the communication interface to execute the method as described in any one of claims 1-14.

17. A computer program product, characterized in that, When the computer program product is run on a computer, the computer performs the method described in any one of claims 1-14.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, performs the method according to any one of claims 1-14.

Images