Information display method and device
By displaying the main card and secondary cards on the terminal device interface and utilizing the scene assistant to provide human-computer dialogue, the problem of insufficient information in smart cards is solved, enabling user-friendly information acquisition and filtering, and improving the user experience.
Patent Information
- Application Number
- PCT/CN2025/114078
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-09-02
- Filing Date
- 2025-08-12
- Publication Date
- 2026-03-05
AI Technical Summary
Due to the limited area of the control panel, the smart cards on existing terminal devices cannot meet users' needs for information volume, and users need to launch third-party applications to filter information, resulting in cumbersome operation and poor user experience.
The terminal device's interface displays a main card and secondary cards. The main card displays primary service information, while secondary cards are displayed by triggering actions to obtain more related service information. Combined with a scene assistant, human-computer dialogue is provided to meet user needs.
Users can access various related service information without downloading third-party applications, which improves user experience, simplifies the information filtering process, and meets users' information acquisition needs.
Smart Images

Figure CN2025114078_05032026_PF_FP_ABST
Abstract
Description
An information display method and device
[0001] This application claims priority to Chinese Patent Application No. 202411223506.9, filed on September 2, 2024, entitled "An Information Display Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This invention relates to the field of terminal technology, and in particular to an information display method and device. Background Technology
[0003] Today, many terminal devices have a "smart card" function. Smart cards are typically displayed on the main interface of the terminal device and can be used to display reminders relevant to the user, such as reminders for user-created work schedules or flight schedules. However, due to the limited area of the smart card, the amount of information it can provide often falls short of user needs.
[0004] Application content
[0005] The purpose of this invention is to provide an information display method and device for providing users with more service information through smart cards in various service scenarios.
[0006] In a first aspect, the present invention provides an information display method, comprising: displaying a first interface, the first interface including a first main card, the first main card being used to display first main service information related to a first service scenario; and, in response to a triggering operation on the first main card, displaying a second interface, the second interface including the first main card and at least one first secondary card, the first secondary card being used to display first secondary service information related to the first service scenario, the first secondary service information being related to the first main service information.
[0007] In the above implementation, the terminal device can display main cards corresponding to different service scenarios on the first interface. Users can obtain the main service information for the corresponding service scenario through the main cards. When the main service information can meet the user's information needs, the user will not need to perform any operation. When the main service information cannot meet the user's information needs, the user can trigger the display of at least one secondary card for the corresponding service scenario by performing a simple trigger operation on any main card on the first interface. Thus, the user can obtain more information about related services in that service scenario from at least one secondary card. Through the above technical solution, multiple related service information can be intuitively provided to users in various service scenarios based on their needs, without requiring users to specifically download and launch third-party applications or passively filter information from redundant information. This satisfies the user's information acquisition needs and improves the user experience.
[0008] In one of the information display methods described above, in some implementations of the first aspect, the second interface includes a first main card and at least one first secondary card, comprising: the second interface includes at least one display area for a service scenario, the display area for at least one service scenario includes a first display area for a first service scenario, the first display area includes a first main card and at least one first secondary card, and the size of the first main card is larger than that of the first secondary card.
[0009] With this implementation, when the main card of the first service scenario is displayed in the first interface, the second interface may include a display area for the first service scenario, in which the main card of the first service scenario and its associated sub-cards are displayed. At the same time, the second interface may also include a display area for other service scenarios, in which the main cards and sub-cards of other service scenarios are displayed.
[0010] In some implementations of the information display method described above, the first display area further includes a first control; the method further includes: in response to a triggering operation on the first control, switching the first display area to a collapsed state, wherein in the collapsed state, the first display area does not include a first card.
[0011] In this implementation, the first control can be a collapse control, which can be used to control the display state of the display area, including a collapsed state and an expanded state. In the collapsed state, the height of the display area will be lower than in the expanded state. Also, in the collapsed state, the individual cards within the display area are no longer displayed. In the expanded state, the main card and all individual cards will be displayed simultaneously within the display area. Through this implementation, users can flexibly and individually control the display state of individual cards in the display area of each service scenario.
[0012] In some implementations of the information display method described above, the first display area further includes a second control, which displays tag information of a scene assistant corresponding to the first service scenario. The method further includes: in response to a trigger operation on the second control, displaying a first dialog pop-up window on a second interface; the first dialog pop-up window is a dialog pop-up window between the user and the scene assistant corresponding to the first service scenario, and includes an instruction input control; in response to an input operation in the instruction input control, acquiring an input instruction and displaying a first chat information display control within the first dialog pop-up window, the first chat information display control including the input instruction; and according to the input instruction, displaying a second chat information display control within the first dialog pop-up window, the second chat information display control including service information matching the input instruction.
[0013] In this implementation, the second control serves as the trigger control for the scene assistant. When the user clicks the second control, a dialog pop-up window for the scene assistant is displayed. The user can then engage in a human-computer dialogue with the scene assistant within this pop-up window to obtain other service scenarios required for that specific service context. This implementation method allows for the provision of more comprehensive intelligent recommendation services to users based on scenario-specific assistants.
[0014] In some implementations of the information display method described above, the method further includes: in response to a closing operation of a first dialog pop-up, redisplaying a second interface, wherein a first display area of the redisplaying second interface includes a second main card and / or at least one second secondary card; the second main card is used to display second main service information related to the first service scenario, the second main service information being at least partially different from the first main service information, and the second main service information being determined based on service information matched with an input instruction; the second secondary card is used to display second secondary service information related to the first service scenario, the second secondary service information being at least partially different from the first secondary service information, and the second secondary service information being determined based on service information matched with an input instruction.
[0015] In this implementation, after a user obtains the required service information through human-computer interaction in a dialog pop-up window with a scene assistant, upon returning to the second interface, the content of the main card and secondary cards displayed in the display area of that service scene on the second interface is adaptively updated. In this way, the information interaction between the user and each scene assistant can provide feedback and adjustment to the display content of the smart cards displayed in each service scene, ensuring that the displayed smart cards better meet the user's needs.
[0016] In some implementations of the information display method described above, the first display area further includes multiple third controls, each of which is used to identify different scene nodes of the first service scenario. The method further includes: detecting a switch to a target scene node; changing the control style of the target third control, which is used to identify the target scene node; updating the first display area according to the target scene node; the updated first display area includes a third master card and / or at least one third slave card; the third master card displays third master service information related to the first service scenario, which differs from at least some of the first master service information, and is determined based on the target scene node; the third slave card displays third slave service information related to the first service scenario, which differs from at least some of the first slave service information, and is determined based on the target scene node.
[0017] In this implementation, the third control is an identifier control for different scene nodes. When a scene node changes, on the one hand, the terminal device can control the style of the identifier control for the corresponding scene node to change, such as changing the control's shape, size, and color, so that the user can intuitively determine the current scene node. On the other hand, the terminal device can update the display content of the main card and the secondary cards within the display area of the service scene, so that the display content of each card in the service scene can match the scene node.
[0018] In some implementations of the information display method described above, the detection of switching to the target scene node includes: detecting a trigger operation on the target third control.
[0019] In this implementation, changes to scene nodes can be passively initiated based on user actions. For example, when a user clicks on the identifier control of a scene node, the terminal device switches to the corresponding scene node. This approach allows users to flexibly view the main cards and sub-cards of other scene nodes from any scene node.
[0020] In one of the information display methods described above, in some implementations of the first aspect, detecting a switch to a target scene node includes: obtaining scene information of a first service scene, the scene information including time information, user location information, and user behavior information; and determining a switch to a target scene node based on the scene information.
[0021] In this implementation, changes to scene nodes can be proactively made based on changes in the scene. For example, the terminal device can automatically detect changes in the current time to determine the scene node. For instance, the terminal device can determine the scene node to switch from a departure node to a boarding node after detecting that the time remaining between the current time and the departure time is less than a set threshold. Alternatively, the terminal device can determine changes in the scene node by detecting the user's location or by obtaining user behavior information. This implementation allows for automatic service orchestration and related service information recommendations based on changes in scene nodes.
[0022] In some implementations of the information display method described above, the second interface further includes a fourth control for switching different time options; the method further includes: determining the switched time option in response to a trigger operation on the fourth control; updating the second interface according to the switched time option, wherein the updated second interface includes a display area for at least one target service scenario, wherein the at least one target service scenario is determined according to the switched time option, and the display area of the at least one target service scenario includes a main card and at least one secondary card of the at least one target service scenario.
[0023] In this implementation, the fourth control can be a time switching control. This control allows users to switch between different times, such as the day before yesterday, yesterday, today, and the future, to view service information for various service scenarios at different times. This implementation method facilitates users' flexible viewing of past, present, and future service information for various service scenarios, enhancing their sense of control.
[0024] In some implementations of the information display method described above, the method further includes: deleting any first sub-card in response to a deletion operation on any first sub-card; and determining a new first sub-card and displaying the new first sub-card in the first display area.
[0025] In this implementation, the user can delete any of the sub-cards displayed on the second interface. When any sub-card is deleted, the terminal device can automatically generate a new sub-card and display it in the position where the deleted sub-card was displayed.
[0026] In some implementations of the information display method described above, the method further includes: deleting a first display area in response to a deletion operation on a first main card.
[0027] In this implementation, the user can delete any of the main cards displayed on the second interface, and when any main card is deleted, the terminal device can directly delete the display area of the service scenario corresponding to that main card.
[0028] In some implementations of the information display method described above, the first interface further includes at least one fourth main card, which is used to display main service information corresponding to multiple different service scenarios, and the multiple different service scenarios are different from the first service scenario.
[0029] In this implementation, the first interface can display multiple main cards, each corresponding to a different service scenario.
[0030] In one of the information display methods described above, in some implementations of the first aspect, the display area of at least one service scenario in the second interface further includes multiple display areas for different service scenarios. Each of the multiple display areas for different service scenarios includes a main card and at least one secondary card for a different service scenario. The arrangement order of the multiple display areas for different service scenarios and the first display area in the second interface is consistent with the arrangement order of at least one fourth main card and the first main card in the first interface.
[0031] In this implementation, when multiple main cards corresponding to multiple service scenarios are superimposed on the first interface, when the user triggers the display of the second interface, the second interface can sequentially display the display areas of the service scenarios corresponding to the multiple main cards according to the arrangement order of the multiple main cards in the first interface, and display the main card and associated secondary card of the corresponding service scenario in the display area of each service scenario respectively.
[0032] In some implementations of the information display method described above, the triggering operation for the first main card includes: long-pressing the first main card and swiping down.
[0033] Secondly, this technical solution provides an electronic device, including: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the device, cause the device to perform the method of the first aspect or any possible implementation thereof.
[0034] Thirdly, the present invention also provides a chip, the chip including a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface and executes the method in the first aspect or any possible implementation thereof.
[0035] Optionally, as one implementation, the chip may further include a memory storing instructions, and the processor is configured to execute the instructions stored in the memory. When the instructions are executed, the processor is configured to perform the method in the first aspect or any possible implementation of the first aspect.
[0036] Fourthly, the present invention also provides a computer-readable storage medium storing program code for execution by a device, the program code including instructions for performing the method in the first aspect or any possible implementation thereof. Attached Figure Description
[0037] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0038] Figure 1 is a schematic diagram of a scenario of the information display method provided in an embodiment of this application;
[0039] Figure 2 is a schematic diagram of an electronic device provided in an embodiment of this application;
[0040] Figure 3 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0041] Figure 4 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0042] Figure 5 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0043] Figure 6 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0044] Figure 7 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0045] Figure 8 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0046] Figure 9 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0047] Figure 10 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0048] Figure 11 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0049] Figure 12 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0050] Figure 13 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0051] Figure 14 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application;
[0052] Figure 15 is a schematic diagram of another scenario of the information display method provided in the embodiments of this application. Detailed Implementation
[0053] Many terminal devices feature "smart card" functionality. Smart cards can display reminders related to user events, such as reminders for user-created work schedules, flight information, weather updates, and step counts. Smart cards allow users to quickly and directly access information relevant to their daily lives and work without needing to access specific applications, providing greater convenience.
[0054] Figure 1 illustrates several common display methods for "smart cards" in related technologies. In one implementation, as shown in Figure 1, the smart card 11 can be displayed on the main interface of the terminal device. Alternatively, as shown in Figure 1, the smart card 11 can also be displayed on the negative one screen of the terminal device.
[0055] In the common display methods shown in Figure 1, although multiple smart cards can be displayed simultaneously, on the one hand, the display area of each smart card is limited, and the information that each smart card can display is relatively limited, which cannot well meet the user's demand for information. On the other hand, each smart card provides a single service reminder in a single scenario. Taking the three smart cards displayed in the negative one screen interface shown in Figure 1 as an example, if the user has created an office schedule, smart card 111 only provides reminders for the office schedule in the office scenario; if the user has booked a flight ticket, smart card 112 only provides reminders for flight information in the travel scenario. However, in real-world scenarios, taking the travel scenario as an example, the information needed by users is not only basic flight information, but also many other service information related to the travel scenario, such as routes to the airport, airport dining recommendations, distance to the boarding gate, VIP lounge benefits, etc. Based on the smart card shown in Figure 1, when users need more service information about travel scenarios, they also need to launch relevant third-party applications to find the required information. This increases the user's workload. On the other hand, third-party applications often suffer from information overload, with a lot of redundant and invalid information on their pages, such as coupon recommendations, insurance recommendations, and personal flight data statistics. Users need to filter the required information from the complex information on the third-party application interface, which is inefficient and results in a poor user experience.
[0056] Therefore, the technical solution of the embodiments of this application is proposed.
[0057] In this embodiment, the terminal device may include a suggestion application, which can be used to implement intelligent reminder functions. For example, it could be the "YOYO Suggestions" application. Specifically, the suggestion application can identify the user's behavioral intent in different service scenarios based on behavioral data generated by the user on the terminal device, such as created schedule data, note data, order data, etc., and display at least one smart card on the first interface of the terminal device based on the identification results of the user's behavioral intent in different service scenarios. The first interface can be, for example, the main interface of the terminal device, or the negative one screen interface, etc., and this embodiment does not impose any limitations. In this embodiment, for ease of description, each smart card displayed on the first interface is referred to as a "main card." For any service scenario, the number of main cards that can be displayed simultaneously at any given time can be, for example, one. In this way, each main card displayed on the first interface can correspond to a different service scenario, used to display "main service information" under different service scenarios. Possible service scenarios may include, for example, travel scenarios, office scenarios, life scenarios, entertainment scenarios, etc. The main service information can be service information that the user must query under the corresponding service scenario, determined based on user group data, user profile data, etc. For example, in a travel scenario, users will inevitably need to query service information, such as flight information, which will specifically include departure and landing times, ticketing reminders, check-in reminders, etc.
[0058] In this embodiment, the main service information displayed on the main card differs for different service scenarios. The main service information that can be displayed on the main card for each service scenario can be preset, and the types of main service information that can be displayed on the main card for each service scenario can be different or the same. For example, in a travel scenario, the main card can display two types of main service information, such as flight information for a booked ticket or train / high-speed rail information. In an office scenario, the main card can display only one type of main service information, such as reminder information for a schedule created by the user.
[0059] Furthermore, the main cards for each service scenario in the first interface can be displayed triggered by scenario events. Specifically, when an event corresponding to the main service information in a given service scenario is detected and the event's reminder conditions are met, the main card for that service scenario can be displayed on the first interface; otherwise, the main card for that service scenario will not be displayed on the first interface. Meeting the event reminder conditions can be the arrival of the event's reminder time. For example, in a travel scenario, when an event indicating that a user has booked a flight is detected, and the current time is one day before the flight's departure time, the main card for the travel scenario can be displayed on the first interface, showing the flight information.
[0060] When the terminal device detects a user's trigger operation on any of the main cards displayed on the first interface, it can display the target interface. The target interface can be, for example, the application interface of the aforementioned suggested application; this embodiment does not limit this. The user's trigger operation can be, for example, clicking the main card and swiping down, or tapping the back of the terminal device. The target interface can display the main card triggered by the user, and can also display at least one secondary card. For ease of distinction, the size of the main card can be, for example, larger than the secondary card. The secondary card can be used to display other service information in the service scenario corresponding to the main card. For ease of description, this embodiment refers to this as "secondary service information." Secondary service information can be service information that the user may need to query in this service scenario, determined based on user group data, user profile data, etc., and the secondary service information is related to the main service information. For example, in a travel scenario, the service information that the user may need to query could be destination weather, airport pick-up and drop-off service information, early morning alarm recommendations, etc.
[0061] For any given service scenario, there can be multiple types of associated secondary service information. Multiple secondary cards can be set to display all secondary service information for that service scenario, or at least one secondary card can be set to display a portion of the secondary service information for that service scenario. In this embodiment, the number of secondary cards displayed in each service scenario can be the same or different, and for the same service scenario, the number of secondary cards displayed each time can be the same or different.
[0062] In one implementation scenario, the sub-service information displayed in each sub-card can be determined based on the degree of relevance between each sub-service information and the user. For example, sub-service information with a relevance higher than a set threshold can be filtered and displayed in the sub-card. The degree of relevance to the user can be determined based on the frequency with which the user obtains the service information in that service scenario. For instance, the terminal device can learn from the user's historical behavior regarding obtaining service information in different service scenarios, considering the user's group or the user's own history, to determine the frequency with which the user obtains various types of service information in different service scenarios. For ease of understanding, taking a travel scenario as an example, if the terminal device determines from historical data that the user frequently obtains wake-up time suggestions and pre-cached video data before traveling, then these two service information items can be considered to have a high degree of relevance to the user.
[0063] In the above technical solution, the terminal device can display main cards corresponding to different service scenarios on the first interface based on scene events. Users can obtain the main service information for the corresponding service scenario through the main cards. When the main service information can meet the user's information needs, the user will not need to perform any operation. When the main service information cannot meet the user's information needs, the user can perform a simple trigger operation on any main card on the first interface to trigger the display of at least one secondary card for the corresponding service scenario. Thus, the user can obtain more information about related services in that service scenario from at least one secondary card. Through the above technical solution, multiple related service information can be intuitively provided to users in various service scenarios based on their needs, without requiring users to specifically download and launch third-party applications or passively filter information from redundant information, thus meeting the user's information acquisition needs and improving the user experience.
[0064] Figure 2 shows a schematic diagram of the structure of the electronic device 100 provided in an embodiment of this application.
[0065] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a fingerprint sensor 180H, a pressure sensor 180A, a touch sensor 180K, an ambient light sensor 180L, a proximity light sensor 180G, a temperature sensor 180J, a distance sensor 180F, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer 180E, a bone conduction sensor 180M, etc.
[0066] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0067] Processor 110 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.
[0068] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.
[0069] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
[0070] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.
[0071] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 100.
[0072] The MIPI interface can be used to connect the processor 110 and the display screen 194. The processor 110 and the display screen 194 communicate through the DSI interface to realize the display function of the electronic device 100.
[0073] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.
[0074] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.
[0075] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.
[0076] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.
[0077] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of electronic device 100, etc. In addition, internal memory 121 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. Processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory disposed in the processor.
[0078] The following embodiments of this application will use an electronic device with the structure shown in FIG2 as an example to specifically illustrate the information display method provided by the embodiments of this application. For ease of explanation, the following embodiments of this application will use a scenario where the first interface is the main interface of the terminal device as an example to illustrate the information display method provided by the embodiments of this application. However, it should be understood that when the first interface is a negative one screen interface or any other interface that can display smart cards, the information display method provided by the embodiments of this application is still applicable.
[0079] Figure 3 is a schematic diagram of a scenario of the information display method provided in this application embodiment. As shown in Figure 3, the main interface of the terminal device can display at least one main card, and each main card can be used to display main service information under different service scenarios. These different service scenarios can be, for example, travel scenarios, office scenarios, life scenarios, entertainment scenarios, etc. The travel scenario can be further divided into business travel scenarios and commuting scenarios. This application embodiment does not impose any limitations on this.
[0080] When multiple main cards are displayed on the main interface, these cards can be stacked, forming a "card set" or "card stack." As shown in Figure 3, users can switch between different main cards by swiping on them to view main service information for different service scenarios. For example, the main interface can display a main card 311 for a travel scenario and a main card 312 for an office scenario. The main service information displayed on the main card 311 for the travel scenario could be flight information, such as departure time, departure airport, arrival time, arrival airport, check-in progress, etc. The main service information displayed on the main card 312 for the office scenario could be schedule reminder information, such as schedule name, start time, etc.
[0081] For any main card displayed on the main interface, if a user wants to obtain more service information than what is shown on that main card in a given scenario, the user can trigger an action on that main card to display more related service information for the corresponding service scenario on the terminal device. This triggering action could be, for example, long-pressing and swiping down on the main card, or double-tapping any part of the back of the terminal device.
[0082] In response to the user's trigger operation on any main card in the main interface, the terminal device can display a target interface. This target interface can be provided by a suggestion application provided by the terminal device system, such as the "YOYO Suggestions" application, which is used to implement the smart reminder function. The target interface may include a display area corresponding to at least one service scenario. In one possible implementation, the at least one service scenario may only include the service scenario corresponding to the main card triggered by the user. In another possible implementation, the at least one service scenario may include the service scenarios corresponding to each main card displayed on the terminal device's main interface. Alternatively, based on the above two implementations, the display area corresponding to at least one service scenario may also include a display area for a smart recommendation scenario. The display area for the smart recommendation scenario can be used to display service information that the user may be interested in based on the user's potential preferences, serving as a supplement to the service information displayed in other service scenarios.
[0083] When multiple service scenario display areas are displayed on the target interface, the display area for the service scenario corresponding to the main card triggered by the user can be located above the other display areas. If the target interface cannot fully display all service scenario display areas, the user can scroll through the display areas corresponding to different service scenarios on the target interface by swiping, thereby viewing the display areas corresponding to different service scenarios. Each service scenario display area can display a main card and at least one secondary card for that service scenario. The secondary card can be used to display secondary service information associated with the main service information displayed on the main card within the corresponding service scenario. In this embodiment, the number of secondary cards in the display areas corresponding to different service scenarios can be the same or different, and for the same service scenario, the number of secondary cards displayed each time can be the same or different.
[0084] Figure 4 is a schematic diagram of another scenario of the information display method provided in this application embodiment. As shown in Figure 4, when multiple main cards corresponding to service scenarios are superimposed on the main interface of the terminal device, for example, the terminal device can display the target interface 40 in response to the user's trigger operation on the main card 311 corresponding to the travel scenario on the main interface. The trigger operation on the main card 311 can be a long press and swipe down. Referring to Figure 4, when multiple main cards are superimposed on the main interface, during the user's swipe down operation, the terminal device can first sequentially display each main card superimposed on the main card 311, and then, when the swipe distance exceeds a threshold, the terminal device can be triggered to display the target interface 40. The target interface 40 can display the display area 41 corresponding to the travel scenario. The display area 41 corresponding to the travel scenario can include the main card 311 of the travel scenario (i.e., the main card triggered by the user on the main interface) and at least one secondary card 411. For example, it can include two secondary cards, which can respectively display suggested wake-up time information and prompts for pre-cached videos. Simultaneously, the target interface 40 can also display a display area 42 corresponding to the intelligent recommendation scenario. This display area 42 can be used to display service information that the user may be interested in based on their potential preferences, serving as a supplement to the service information displayed in other service scenarios. Unlike other service scenarios, the cards 421 displayed in the display area 42 corresponding to the intelligent recommendation scenario do not distinguish between main and secondary cards. For example, the cards displayed in the display area 42 corresponding to the intelligent recommendation scenario may not be displayed on the main interface, the negative one screen, or other primary interfaces of the terminal device. By displaying the cards of the intelligent recommendation scenario in the target interface, the user's potential needs can be better met.
[0085] Figure 5 is a schematic diagram of another scenario of the information display method provided in this application embodiment. As shown in Figure 5, when multiple main cards corresponding to service scenarios are superimposed on the main interface of the terminal device, for example, when main cards corresponding to travel scenarios and main cards corresponding to office scenarios are superimposed, the terminal device can display the target interface 40 in response to the user's trigger operation on the main card 311 corresponding to the travel scenario on the main interface. In the target interface 40, the display area 41 corresponding to the travel scenario and the display area 43 corresponding to the office scenario can be displayed sequentially according to the superposition order of multiple main cards on the main interface. The display area 43 corresponding to the office scenario can include the main card 312 of the office scenario and at least one secondary card 431. For example, it can include three secondary cards, which can respectively display the prompt information of missed calls, the prompt information of unread messages in office applications, and the prompt information of unread saved content in the collection space. At the same time, the target interface 40 can also display the display area corresponding to the intelligent recommendation scenario, and display at least one card in the display area to display the service information intelligently recommended by the terminal device based on user preferences. Since the user triggers the main card 311 corresponding to the travel scenario on the main interface, the display area 41 corresponding to the travel scenario can be located above the display area 43 corresponding to the office scenario. Alternatively, in another implementation, regardless of the user's triggering operation, the display areas corresponding to each service scenario in the target interface 40 can be arranged sequentially according to their inherent priorities.
[0086] In another implementation of this application, the target interface may further display a scene assistant trigger control 61 in the display area of each service scenario. The scene assistant trigger control 61 may display the tag information of the scene assistant corresponding to the service scenario. The scene assistant of the service scenario can be used to achieve human-computer dialogue with the user, meeting more service needs of the user in different service scenarios. Figure 6 is a schematic diagram of another scenario of the information display method provided in this application embodiment. As shown in Figure 6, in the target interface, the scene assistant trigger control 61 may be located at the bottom of the display area of each service scenario. For example, for the display area corresponding to the travel scenario, the tag information displayed by the scene assistant trigger control 61 may be "Travel Assistant"; for the display area corresponding to the office scenario, the tag information displayed by the scene assistant trigger control 61 may be "Office Assistant"; for the display area corresponding to the intelligent recommendation scenario, the tag information displayed by the scene assistant trigger control 61 may be "Understanding Assistant".
[0087] The trigger control for the scene assistant can be used to trigger the display of a dialog pop-up window with the scene assistant. This dialog pop-up window can be, for example, a pop-up window displayed on the target interface. For any service scenario, if the service information displayed in the main card and various sub-cards of the service scenario's display area still cannot meet the user's information needs, the user can obtain more scenario service information based on the dialog window with the scene assistant. As shown in Figure 7, taking the travel scenario as an example, in response to the trigger operation of the "Travel Assistant" control, the terminal device can display a dialog window 71 with the scene assistant on the target interface. The dialog window 71 with the scene assistant can display a command input control 711, which can be used by the user to input command information and obtain other required service information through human-computer dialogue. The user can input command information into the command input control 711 via keyboard input or voice input. In response to receiving the user's input command information, the terminal device can determine the matching scenario service information and display that scenario service information in the dialog window 71. Specifically, after receiving the user's input command information, the terminal device can display a first chat information display control in the dialog window 71, and display the input command in the first chat information display control. The first chat information display control can be the chat bubble corresponding to the user. Furthermore, based on the user's input command, the terminal device can display a second chat information display control in the dialog window 71, and display service information matching the input command in the second chat information display control. The second chat information display control can be the chat bubble corresponding to the scene assistant.
[0088] Furthermore, in another implementation, to simplify user operation, as shown in Figure 7, multiple preset terms 712 can be displayed above the information input control. The terminal device can respond to the user's triggering operation on any of the preset terms 712, determine the matching scenario service information, and display the scenario service information in the dialog window. The multiple preset terms 712 can be determined, for example, based on the service scenario and the information acquisition habits of the user's group or individual within that scenario. Taking a travel scenario as an example, the preset terms could include, for example, "Shenzhen Food" or "Shenzhen Attractions Recommendations."
[0089] Furthermore, in another implementation, as shown in Figure 7, the top area of the dialogue window with the scene assistant can also display the main card for the corresponding service scene. The area below the main card, 713, can display prompts for more scene services available under the corresponding service scene. For example, taking a travel scenario, the prompts could be something like, "Hello, based on your itinerary, I can help you with even more services. Try saying to me: Do I need to take a shuttle bus at the airport for this flight? / How can I upgrade to a higher class at a lower price? / How can I book an airport lounge?" Based on the displayed prompts, users can quickly understand the functions of the scene assistant and flexibly obtain the more scene services they need.
[0090] In another embodiment, the terminal device can also return to the target interface in response to a back operation triggered by the user in the dialogue window with the scene assistant. After returning to the target interface, the terminal device can also update the main card and / or secondary card displayed in the display area corresponding to the respective service scene based on the dialogue content between the user and the scene assistant of each service scene. Updates may include, for example, modification, addition, replacement, deletion, etc.
[0091] For example, for any service scenario, at least some of the information displayed in the main card can be updated based on the dialogue between the user and the scenario assistant. For instance, as shown in Figure 7, after a user requests check-in from the scenario assistant, when the user returns to the target interface, the content related to "Check-in Counter" in the main card can be changed to "Seat Number". Furthermore, for any service scenario, a sub-card can be added to the display area of that service scenario based on the dialogue between the user and the scenario assistant. The added sub-card can display the service information obtained by the user from the dialogue window with the scenario assistant. Alternatively, the sub-cards displayed in the display area of the service scenario can be replaced based on the dialogue between the user and the scenario assistant. For example, any sub-card can be replaced, or the sub-card with the lowest relevance to the user can be replaced. The replaced sub-card can display the service information obtained by the user from the dialogue window with the scenario assistant.
[0092] This approach allows for feedback adjustments to the smart cards displayed in various service scenarios based on the user's information acquisition behavior, enabling the displayed smart cards to better meet the user's needs for acquiring relevant information within the scenario.
[0093] In another embodiment of this application, as shown in Figure 8, each service scenario's display area may also display a folding control 81. The folding control 81 can be used to control the display state of the display area, including a folded state and an unfolded state. For any service scenario's display area, in the folded state, the height of the display area is reduced. At this time, the various sub-cards in the display area will no longer be displayed, and only the main card will be displayed. In the unfolded state, the main card and various sub-cards will be displayed normally in the display area.
[0094] In this embodiment, after the target interface is displayed, the display areas of each service scenario can be in an expanded state by default. For any service scenario's display area, in response to the triggering operation of the collapse control 81, as shown in Figure 8, the display area of that service scenario can be switched to a collapsed state, thereby stopping the display of each sub-card within the display area of that service scenario and only displaying the main card of that service scenario. In this way, the display height of the display area corresponding to the collapsed service scenario is significantly reduced, so more of the display area of the service scenario below it can be displayed in the target interface. Through the above solution, the display state of the sub-cards in the display area of each service scenario can be flexibly and individually controlled.
[0095] In another implementation, the display status of slave cards in various service scenarios can be uniformly controlled. Specifically, in one possible implementation, the YOYO recommendation application on the terminal device may include a setting button for the display status of slave cards. Based on the user's triggering of this setting button, the terminal device can control the display status of the display areas for various service scenarios on the target interface, thus allowing all service scenario display areas to show slave cards, or none to show slave cards. Alternatively, in another possible implementation, the terminal device's settings application may include a setting button for the display status of slave cards. Based on the user's triggering of this setting button, the terminal device can control the display status of the display areas for various service scenarios on the target interface, thus allowing all service scenario display areas to show slave cards, or none to show slave cards.
[0096] Furthermore, in this embodiment, the user can edit the display area of any service scenario displayed on the target interface. Editing operations can include, for example, deletion, addition, and modification of display style. Specifically, as shown in Figure 9, for any service scenario display area, the terminal device can respond to the user's trigger operation (such as a long press) on that display area and display an operation list 91 below that display area. The operation list 91 can include multiple operation buttons, such as delete, edit default style, YOYO suggested settings, and Honor Quick Service. The delete button can be used by the user to delete the corresponding service scenario display area. In another implementation, for any service scenario display area, the user can also delete it by clicking on the display area and swiping left. In this embodiment, after the display area of any service scenario displayed on the target interface is deleted, the terminal device can delete the main card of that service scenario on the main interface and the negative one screen. Therefore, when a user returns to the main interface or the negative one screen based on the back operation on the target interface, the main card of that service scenario will no longer be seen. If the target interface displays two or more service scenario display areas, when one service scenario's display area is deleted, the display areas of subsequent service scenarios will sequentially fill the space of the previous service scenario. The "Edit Default Style" button allows users to change the display style of the corresponding service scenario's display area, such as color. "YOYO Suggestions Settings" allows users to navigate to the settings interface of the YOYO Suggestions application within the settings app, enabling more settings operations. "Honor Quick Service" allows users to navigate to the Honor Quick Service application interface. The Honor Quick Service application is an application provided by the terminal device system and can provide users with various addable smart cards and service scenarios. In other implementations, the Honor Quick Service application can have other names; this application embodiment does not limit this. Based on the user's addition of an identifier control corresponding to any service scenario within the Honor Quick Service application, the terminal device can add a display area for that service scenario on the target interface and display the corresponding main card and at least one secondary card in the newly added display area. Furthermore, the terminal device can overlay the main card of the newly added service scenario with the existing main card on the main interface and the negative one screen. Therefore, when a user triggers a return operation on the target interface to return to the main interface or the negative one screen, they can access the main card of the newly added service scenario on either the main interface or the negative one screen.
[0097] In another implementation, for any service scenario display area on the target interface, the user can also edit the main card and any of the sub-cards displayed therein. Editing operations can include, for example, deletion, addition, and modification of display style. As shown in Figure 10, for any service scenario display area, the terminal device can respond to the user's trigger operation (such as a long press) on the main card displayed therein, displaying an operation list below the main card. The operation list can include multiple operation buttons, such as delete, edit default style, YOYO suggested settings, and Honor Quick Service. The functions of each operation button can be referred to the aforementioned description. For deletion, in another implementation, for any service card (main card or sub-card), the user can also delete the service card by clicking on it and swiping left. It should be noted that when the user triggers the deletion operation on the main card, it means that the user no longer needs the main service information in that service scenario. Therefore, the terminal device will not need to continue displaying the sub-service information associated with the main service information. Thus, when a deletion operation on the main card is detected, the terminal device can directly delete the display area of the corresponding service scenario. Furthermore, as shown in Figure 11, for any service scenario display area, the terminal device can also respond to user trigger operations (such as long press) on the displayed sub-cards, displaying an operation list below the sub-card. The operation list can include multiple operation buttons, such as delete, edit default style, YOYO suggested settings, and Honor Quick Service. The functions of each operation button are described above. Unlike the main card, when a trigger operation is detected on the delete button of any sub-card, the terminal device can delete only that sub-card.
[0098] In another implementation, as shown in Figure 12, the target interface may also include an add control 31. The add control 31 can be used by the user to add display areas for other service scenarios on the target interface, and display the main card and secondary cards of the corresponding scenario in these display areas. For example, in response to a trigger operation on the add control 31, the application interface of a related application (such as the Honor Quick Service application) can be displayed. This application interface may include multiple service scenarios, such as fitness scenarios and dating scenarios. Furthermore, the terminal device can add the service scenario to the target interface in response to a trigger operation on the identifier control corresponding to any service scenario. Specifically, a new display area corresponding to the service scenario can be added to the target interface, and the main card and at least one secondary card corresponding to the service scenario can be displayed in this display area. Further, the terminal device can also overlay the newly added service scenario's main card with the existing main card on the main interface and the negative one screen. Then, when the user triggers a return operation on the target interface to return to the main interface or the negative one screen, the user can obtain the newly added service scenario's main card on the main interface or the negative one screen.
[0099] Through the above implementation method, users can flexibly manage the service scenarios contained in the target interface and the cards corresponding to each service scenario, so that the information provided by the same service scenario and each card in the service scenario is more consistent with the user's needs.
[0100] In real life, the service information needed by users at different points in the same service scenario is often not entirely consistent. Taking office or daily life scenarios as an example, the service information needed by users may differ at different times of day, such as early morning, midday, and evening. For instance, in the early morning, users might need check-in reminders or navigation tips, while during the day, they might need unread notifications from various office applications. Or, taking travel scenarios as an example, the service information needed by users is clearly not constant at different event points, such as departure, boarding, and arrival.
[0101] To address the above situation, in another embodiment of this application, the display area of each service scenario in the target interface can display different scene node identification controls. For any service scenario, when the scene node changes, on the one hand, the terminal device can control the control style of the corresponding scene node's identification control to change, such as changing the control's shape, size, color, etc., so that the user can intuitively determine the current scene node. On the other hand, the terminal device can update the display content of the main card and / or secondary card in the display area of the service scenario, so that the display content of each card in the service scenario can match the scene node.
[0102] For example, referring to Figure 13, taking an office scenario as an example, the target interface can display three scene nodes—morning, daytime, and evening—within the display area of the office scenario, represented by identification controls 51. For any given node, when the user is in that node, the corresponding identification control has a bar shape, while the controls for the other nodes have a circular shape. Simultaneously, when in the morning node, the main card can be used to display, for example, time information, the day's schedule, and a ride-hailing redirect control. Sub-cards can be used to display, for example, missed call notifications, unread messages in office applications, unread saved content in the collection application, and generated notes in the note-taking application. When in the daytime node, the main card can be used to display upcoming schedule information and a schedule redirect control. Sub-cards can be used to display various office auxiliary function prompts. When in the evening node, the main card can be used to display work summary information and a work review redirect control. Sub-cards can be used to display check-in reminders, etc.
[0103] For example, referring to Figure 14, taking a travel scenario as an example, the target interface can display three scenario nodes—departure, boarding, and arrival—within the display area. For any given node, when the user is at that node, the corresponding icon is a bar shape, while the icons for the other nodes are circular. Simultaneously, when at the departure node, the main card can display information such as flight check-in counters and seat selection navigation. Sub-cards can display information such as suggested wake-up times and prompts for pre-caching videos. When at the boarding node, the main card can display information such as flight check-in counters, gate information, and boarding pass navigation. Sub-cards can display information such as gate distance, nearby restaurants, and airport lounge access information. When at the arrival node, the main card can display information such as baggage carousel information. Sub-cards can display information such as navigation and hotel services.
[0104] In this embodiment, the changes to the aforementioned scene nodes can be passively changed based on user operations, or actively changed based on changes in the scene. These two implementation methods are described below.
[0105] In one implementation, for any service scenario's display area, in response to a user's triggering operation on the identifier control of any scenario node, the terminal device can switch to the corresponding scenario node. Then, the terminal device can update the main card and all sub-cards displayed in the display area according to the scenario node. Updating the main card (or sub-card) can involve modifying part of the main service information (or sub-service information) displayed on the main card (or sub-card), or it can replace all the main service information (or sub-service information) displayed on the main card (or sub-card). Through this implementation, the display content of the main card and all sub-cards of the corresponding service scenario can be updated based on the user's triggering operation on the scene node switching control. In this way, the user can flexibly view the display content of the main card and all sub-cards corresponding to other scene nodes at any scene node.
[0106] In another implementation, for any service scenario, the terminal device can automatically detect scenario changes and, upon determining that a scenario node has changed, modify the control style of the corresponding identifier controls for each scenario node. Furthermore, the terminal device can update the main card and all secondary cards displayed in the display area based on the switched scenario node. For example, the terminal device can detect scenario changes by detecting the current time, the user's location, or obtaining user behavior information. Obtaining user behavior information can be done by receiving notification messages from third-party applications. For ease of understanding, taking a travel scenario as an example, the terminal device can determine that the scenario node changes from the departure node to the boarding node after detecting that the user has arrived at the airport and / or that the time remaining between the current time and the departure time is less than a set threshold. Alternatively, the terminal device can pre-obtain data permissions from third-party applications provided by airlines or other third parties. Then, after the user completes boarding, the terminal device can receive a notification message from the third-party application confirming that the user has boarded, thus determining that the scenario node changes from the departure node to the boarding node.
[0107] The technical solution provided by the embodiments of this application can be used to orchestrate services and recommend related service information in a targeted manner according to scene nodes. At the same time, users can flexibly view the intelligent recommendation services of each scene node.
[0108] Furthermore, in many cases, users may need to check service information not only when the reminder for a particular event arrives, but also in advance before the reminder, or even after the event has been completed. For example, if a user has booked multiple flights on different dates, they might need to check the reminders for each flight before their scheduled reminder time to better plan their work. Alternatively, users might want to verify the completion status of past reminders, such as whether a package has been picked up or a credit card payment has been made.
[0109] In another embodiment of this application, the terminal device can also support viewing service information for past, present, and future service scenarios on the target interface. Past service information may include archives of service information for already occurred scenario events, displaying the complete status of the scenario events (e.g., payment made, item picked up). Present service information may include service information based on currently occurring scenario events. Future service information may include service information for order-related events that have been created but have not yet reached their reminder time, such as travel events like flights and train tickets, and office events like meeting schedules.
[0110] Specifically, in this embodiment of the application, as shown in Figure 15, the target interface may include a time switching control 41. The time switching control 41 can be used by the user to switch between different times, such as the day before yesterday, yesterday, today, and the future, so as to view service information for various service scenarios at different times. As shown in Figure 15, in response to the user switching the time to "yesterday" based on the time switching control 41, the terminal device can display the display areas corresponding to the various service scenarios generated yesterday in the target interface, and display the service information of the scenario events in the display areas of the various service scenarios generated yesterday. For example, if the service scenario generated yesterday is a life scenario, the display area corresponding to the life scenario can be displayed in the target interface, and information such as the express delivery has been signed for, the credit card has been repaid, and the birthday information of relatives can be displayed in the display area. In response to the user switching the time to "today" based on the time switching control 41, the terminal device can display the display areas corresponding to the various service scenarios generated today in the target interface, and display the service information of the scenario events in the display areas of the various service scenarios generated today. For example, the service scenarios generated today are a travel scenario and an office scenario. The target interface can display the corresponding display areas for the travel scenario and the office scenario respectively. Flight information is displayed in the travel scenario display area, and office schedule information is displayed in the office scenario display area. In response to the user switching the time to "future" using the time switching control 41, the terminal device can display the display areas corresponding to the various service scenarios for order-type events created by the user but not yet reaching their reminder time on the target interface. Service information for these order-type events is then displayed in each service scenario within each display area. For example, this could include information such as train tickets and flights booked by the user in the travel scenario.
[0111] The solution provided by this application addresses the drawback of being unable to view service information before or after the reminder time has arrived, allowing users to flexibly view service information for various service scenarios in the past, present, and future, thus enhancing their sense of control.
[0112] It should be understood that the electronic equipment described here is embodied in the form of functional units. The term "unit" here can be implemented in software and / or hardware, without specific limitation. For example, a "unit" can be a software program, hardware circuit, or a combination of both that implements the above-described functions. The hardware circuit may include application-specific integrated circuits (ASICs), electronic circuits, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. Whether a function is implemented in hardware or in a manner driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments.
[0113] The module division in this embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods are possible. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing module. The integrated modules described above can be implemented in hardware.
[0114] This application also provides an electronic device, which includes a storage medium and a central processing unit. The storage medium may be a non-volatile storage medium, and a computer-executable program is stored in the storage medium. The central processing unit is connected to the non-volatile storage medium and executes the computer-executable program to implement the above-described information display method.
[0115] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform various steps of the information display method of this application.
[0116] This application also provides a computer program product containing instructions, which, when run on a computer or any at least one processor, causes the computer to execute the various steps of the information display method of this application.
[0117] This application also provides a chip, including a processor and a data interface. The processor reads instructions stored in a memory through the data interface to execute corresponding operations and / or processes performed by the information display method provided in this application.
[0118] Optionally, the chip further includes a memory connected to the processor via a circuit or wire, the processor being used to read and execute computer programs stored in the memory. Further optionally, the chip includes a communication interface to which the processor is connected. The communication interface is used to receive data and / or information that needs to be processed, the processor obtaining the data and / or information from the communication interface and processing the data and / or information. The communication interface can be an input / output interface.
[0119] The memory can be read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types of dynamic storage devices that can store information and instructions. It can also be electrically erasable programmable read-only memory.
[0120] (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer.
[0121] In this embodiment, "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, or the existence of B alone. A and B can be singular or plural. The character " / " generally indicates that the preceding and following associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0122] Those skilled in the art will recognize that the units and algorithm steps described in the embodiments disclosed herein can be implemented using electronic hardware, computer software, or a combination of electronic hardware and software. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0123] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0124] In the several embodiments provided in this application, any function, if implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0125] The above description is merely a specific embodiment of this application. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application. The protection scope of this application should be determined by the protection scope of the claims.
Claims
An information display method, characterized in that, include: The first interface is displayed, which includes a first main card. The first main card is used to display first main service information related to the first service scenario. In response to a trigger operation on the first master card, a second interface is displayed. The second interface includes the first master card and at least one first slave card. The first slave card is used to display first slave service information related to the first service scenario. The first slave service information is related to the first master service information. The method according to claim 1, characterized in that, The second interface includes the first master card and at least one first slave card, including: The second interface includes a display area for at least one service scenario. The display area for the at least one service scenario includes a first display area for the first service scenario. The first display area includes the first main card and at least one first secondary card. The size of the first main card is larger than that of the first secondary card. The method according to any one of claims 2, characterized in that, The first display area further includes a first control; the method further includes: In response to a trigger operation on the first control, the first display area is switched to a collapsed state, wherein the first card is not included in the first display area in the collapsed state. The method according to claim 2, characterized in that, The first display area further includes a second control, which displays the tag information of the scene assistant corresponding to the first service scene; the method further includes: In response to the triggering operation of the second control, a first dialog pop-up window is displayed in the second interface. The first dialog pop-up window is a dialog pop-up window between the user and the scene assistant corresponding to the first service scene. The first dialog pop-up window includes an instruction input control. In response to an input operation in the instruction input control, an input instruction is obtained, and a first chat information display control is displayed in the first dialog pop-up window, wherein the first chat information display control includes the input instruction; Based on the input command, a second chat information display control is displayed within the first dialog pop-up window, and the second chat information display control includes service information that matches the input command. The method according to claim 4, characterized in that, The method further includes: In response to the closing operation of the first dialog pop-up, the second interface is redisplayed, and the first display area of the redisplayed second interface includes a second main card and / or at least one second secondary card; The second main card is used to display second main service information related to the first service scenario. The second main service information is different from the first main service information in at least part. The second main service information is determined based on service information that matches the input instruction. The second secondary card is used to display second secondary service information related to the first service scenario. The second secondary service information is different from the first secondary service information in at least part. The second secondary service information is determined based on service information that matches the input instruction. The method according to claim 2, characterized in that, The first display area also includes a plurality of third controls, which are respectively used to identify different scene nodes of the first service scenario; the method further includes: Upon detecting a switch to a target scene node, the control style of the target third control is changed; the target third control is used to identify the target scene node. Based on the target scene node, the first display area is updated, and the updated first display area includes a third main card and / or at least one third secondary card; The third main card is used to display third main service information related to the first service scenario. The third main service information is different from the first main service information in at least part of the information. The third main service information is determined according to the target scenario node. The third secondary card is used to display third secondary service information related to the first service scenario. The third secondary service information is different from the first secondary service information in at least part. The third secondary service information is determined according to the target scenario node. The method according to claim 6, characterized in that, The detection of switching to the target scene node includes: A trigger operation on the target third control was detected. The method according to claim 6, characterized in that, The detection of switching to the target scene node includes: Obtain scenario information for the first service scenario, including time information, user location information, and user behavior information; Based on the scene information, determine the target scene node to switch to. The method according to claim 2, characterized in that, The second interface also includes a fourth control, which is used to switch between different time options; the method further includes: In response to a trigger operation on the fourth control, determine the time option after switching; The second interface is updated according to the switched time option. The updated second interface includes a display area for at least one target service scenario. The at least one target service scenario is determined according to the switched time option. The display area of the at least one target service scenario includes a main card and at least one secondary card for the at least one target service scenario. The method according to claim 2, characterized in that, The method further includes: In response to a delete operation on any first slave card, delete the any first slave card; and, Identify a new first card and display the new first card in the first display area. The method according to claim 2, characterized in that, The method further includes: In response to the deletion operation on the first main card, the first display area is deleted. The method according to claim 2, characterized in that, The first interface also includes at least one fourth main card, which is used to display main service information corresponding to multiple different service scenarios, and the multiple different service scenarios are different from the first service scenario. The method according to claim 12, characterized in that, The display area of the at least one service scenario in the second interface also includes display areas of multiple different service scenarios, and the display areas of the multiple different service scenarios respectively include the main card of the multiple different service scenarios and at least one secondary card; The display areas for the multiple different service scenarios and the arrangement order of the first display area in the second interface are consistent with the arrangement order of the at least one fourth main card and the first main card in the first interface. The method according to claim 1, characterized in that, The triggering operation for the first main card includes: long-pressing the first main card and swiping down. An electronic device, characterized in that, include: One or more processors; Memory; And one or more computer programs, wherein the one or more computer programs are stored in the memory, the one or more computer programs including instructions that, when executed by the device, cause the device to perform the method as described in any one of claims 1-14. A chip characterized in that, The chip includes a processor and a data interface. The processor reads instructions stored in the memory through the data interface and executes the method as described in any one of claims 1-14. A storage medium, characterized in that, The storage medium stores program instructions that, when run on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-14.
Citation Information
Patent Citations
Information display method and device, and computer readable storage medium
CN107273006A
Service recommendation method and electronic equipment
CN115700451A
Method and device for processing service information
CN116027933A
Desktop management method and electronic equipment
CN118502624A
Desktop launcher
US20200081592A1