CN115525199B - Card display method and device - Google Patents

Abstract

The present application provides a card display method and device, which can display a card corresponding to a conversation type APP on the desktop of an electronic device, that is, a first card. The first card includes the name of a contact in a conversation application. The user can directly click on the card to enter the conversation interface corresponding to the contact. There is no need to open the conversation APP or open the notification bar first, and then enter the conversation interface corresponding to the first contact. Therefore, the operation for the user to enter the conversation interface is simplified and improves the user experience. It improves the efficiency of computer interaction and improves user experience.

Description

Card display method and device

Technical field

The present application relates to the field of terminal technology, and in particular to card display methods and devices.

Background technique

Currently, when an electronic device receives a message, in one scenario, the user needs to first open the application, find the corresponding contact conversation interface, and then view or reply to the message. In another scenario, the user can find the notification message of the corresponding contact from the notification list, and then click the notification message to enter the corresponding conversation interface to view or reply to the message. It can be seen that in the current usage scenario, the operation for users to view or reply to messages is relatively complicated, resulting in low efficiency of human-computer interaction.

Contents of the invention

In view of this, this application provides a card display method and device to solve the above technical problems. The disclosed technical solutions are as follows:

In a first aspect, this application provides a card display method, which is applied to an electronic device. The electronic device includes a conversational application. The method includes: displaying a first desktop, the first desktop including a first card, and the first card including a first card. The name of the first contact in the conversation application; receiving the first conversation message sent by the first contact; responding to the first conversation message, displaying the first conversation message in the first card; receiving the first input of the user on the first card. Operation; in response to the first operation, jump from the first desktop to a conversation interface with the first contact in the first conversation application, where the conversation interface includes the first conversation message. In this way, the user can click the first card to directly enter the conversation interface of the first contact. There is no need to first open the first conversation application or enter the first conversation application by opening the notification bar, and then enter the conversation interface corresponding to the first contact. Therefore, , which simplifies the user's operation to enter the contact's conversation interface, improves the efficiency of human-computer interaction, and also improves the user experience.

In a possible implementation of the first aspect, in response to the first conversation message, displaying the first conversation message in the first card includes: in response to the first conversation message, the first card includes the name of the first contact Updated to include the first conversation message and the name of the first contact.

In another possible implementation of the first aspect, the method further includes: receiving a second conversation message sent by the first contact; in response to the second conversation message, updating the first conversation message in the first card to the second Conversation messages. It can be seen that after the first conversation message is displayed in the first card, if the second conversation message sent by the first contact is received again, the conversation message in the first card is updated to the latest second conversation message. This makes it easier for users to view the latest news.

In yet another possible implementation of the first aspect, the method further includes: receiving a third conversation message sent to the first contact; in response to the third conversation message, displaying the first conversation message in the first card. Third session message. It can be seen that the first card can also display the conversation messages sent by the user to the first contact, so that the user can learn the latest conversation with the first contact by viewing the first card, which further improves the efficiency of human-computer interaction.

In yet another possible implementation of the first aspect, in response to the first session message, displaying the first session message in the first card includes: after monitoring that the notification center receives the new notification message, obtaining information about the new notification message, The information of the new notification message includes message content, contact information and status information. The status information indicates whether the notification message is a session type message; based on the status information and contact information corresponding to the new notification message, it is determined that the message content of the new notification message is the first After the conversation message, the first mapping relationship is queried to obtain the target card identification associated with the globally unique identification of the first contact; the first conversation message is displayed in the card corresponding to the target card identification; wherein the first mapping relationship includes the card identification of the card There is a correspondence relationship between the globally unique identifier of the contact corresponding to the card, the globally unique identifier is used to uniquely identify the contact of the conversational application, and the card identifier is used to uniquely identify the card on the first desktop.

In another possible implementation of the first aspect, the method further includes: after monitoring that the notification message in the notification center is removed, obtaining information about the removed notification message, where the information about the notification message includes contact information, and Status information, the status information represents whether the notification message is a session type message; based on the status information and contact information corresponding to the removed notification message, after determining that the message content of the removed notification message is the first session message, delete the first The content of the message displayed in the card. It can be seen that this solution synchronizes and dynamically updates the display content of related cards by monitoring the updates of notification messages in the notification center. For example, after monitoring that the first conversation message of the first contact is removed from the notification center, it is considered that the user has learned the third message. The content of a conversation message is synchronized to delete the first conversation message displayed in the first card to avoid repeated operations by the user.

In yet another possible implementation of the first aspect, a third conversation message sent to the first contact is received, and in response to the third conversation message, the third conversation is displayed in the first card. The message includes: after monitoring the update of the session message, obtaining updated session message information, where the session message information includes the contact information of the session message and the session message content; determining the relationship with the third session message based on the contact information. After the conversation message between a contact is updated, the updated conversation message is displayed in the first card. It can be seen that this solution directly monitors the update of session messages to obtain the latest session messages of the contact to make up for the session messages that cannot be obtained by monitoring the notification center, such as the session messages that the user replies to the first contact, so that the user can directly view the first contact's session messages. You can get the latest conversation messages with the first contact through the card.

In yet another possible implementation of the first aspect, the method further includes: receiving a second operation from the user on the second desktop; in response to the second operation, displaying a first interface, and the first interface displays the function type corresponding to the card, The function type includes a session type; in response to the user's operation of selecting the session type, a third desktop is displayed, and the third desktop includes a blank card of the session type; in response to the user's operation of inputting the blank card, a second interface is displayed, and the second interface includes the session The recent contact list corresponding to the type application; in response to the user's operation of selecting the first contact in the recent contact list, the blank card is updated to the first card. It can be seen that through the above operation process, the user can add a card of a contact in the conversation application on the desktop, which greatly facilitates the user to view and enter a certain contact conversation interface, and improves the user experience.

In another possible implementation of the first aspect, in response to the user's input operation on the blank card, displaying the second interface includes: in response to the editing operation on the blank card, displaying the recent message viewing interface, and the viewing recent message interface includes: View the recent contacts portal; in response to the click operation on the view recent contacts portal, display a second interface, and the second interface includes a recent contact list. In this way, it is convenient for users to select corresponding contacts according to their own needs from the recent contact list, and the flexibility of adding cards is improved.

In yet another possible implementation of the first aspect, the electronic device includes a notification manager; after responding to the click operation of viewing the recent contact entry, the method further includes: detecting that the user clicks the operation of viewing the recent contact entry. , send a request to obtain recent session notifications to the notification manager. Recent session notifications are session type notification messages received by the notification manager within the first time period up to the current moment; receive recent session notifications sent by the notification manager, Sort by the timestamp of recent conversation notifications from earliest to latest to get a list of recent contacts. It can be seen that this solution can collect contacts by monitoring the notification messages received in the notification center without calling the interface of the third-party conversation application. It realizes the decoupling between the card display method and the third-party application during the development and debugging process, and improves the Improves the development and debugging efficiency of the card display method.

In yet another possible implementation of the first aspect, in response to the user's operation of selecting the first contact in the recent contact list, the blank card is updated to the first card, including: if the first contact exists in the notification center, send For a conversation message, the first card includes the name of the first contact and the conversation message; if there is no conversation message sent by the first contact in the notification center, the first card includes the name of the first contact. It can be seen that after adding the corresponding contact to the card, different content can be displayed on the card according to the different situations of the contact. For example, if there is a conversation message notification of the first contact in the notification center, the first contact will be displayed in the notification center. Display the conversation message in the card; if there is no conversation message notification for the contact in the notification center, you can only display the contact's information, such as name, avatar, etc., in the card.

In another possible implementation of the first aspect, after responding to the user's operation of selecting the first contact in the recent contact list, the method further includes: adding the card identification of the first card in the first mapping relationship The first mapping relationship includes a corresponding relationship between the card identifier of the card and the globally unique identifier of the contact corresponding to the card.

In yet another possible implementation of the first aspect, the method further includes: in response to the user's editing operation on the first card, displaying a second interface; in response to the user's operation of selecting the second contact in the recent contact list , the contact displayed on the first card is updated from the first contact to the second contact. In this way, users can modify the contacts associated with the card at any time, reducing user operation complexity and improving user experience.

In yet another possible implementation of the first aspect, after the contact displayed on the first card is updated from the first contact to the second contact, the method further includes: combining the first card and the first contact in the first mapping relationship. The mapping relationship data between contacts is updated to the mapping relationship data between the first card and the second contact.

In another possible implementation of the first aspect, after displaying the first desktop, the method further includes: in response to a user's deletion operation on the first card, deleting the first card from the first desktop.

In yet another possible implementation of the first aspect, the first desktop includes at least two cards displayed in a stacked manner. In this way, the area occupied by cards can be reduced, allowing more cards to be placed on the desktop.

In yet another possible implementation of the first aspect, the first card further includes a first control; the method further includes: in response to the user's input operation on the first control, the first card displays an information input box and a sending control; responding In response to the user's click operation on the information input box, the first card displays a content input interface; in response to the user's click operation on the sending control, the first card displays the conversation message sent to the first contact. In this way, users can reply to conversation messages directly on the card, further simplifying the user's operation of replying to contact messages and further improving user experience.

In another possible implementation of the first aspect, the first card further includes a second control; the method further includes: receiving an operation input by the user on the second control, where the second control is a mark read control or a delete control; responding For operations input to the second control, delete the conversation message displayed in the first card. In this way, the user can mark the message as read or delete the message directly on the card without entering the conversation interface, further improving the user experience.

In yet another possible implementation of the first aspect, the message content displayed on the card includes at least one of text, pictures, audio, and video.

In a second aspect, this application also provides an electronic device. The electronic device includes: one or more processors, memories, and a touch screen; the memory is used to store program code; the processor is used to run the program code, so that The electronic device implements the card display method described in any possible implementation manner of the first aspect.

In a third aspect, the application also provides a computer-readable storage medium on which instructions are stored. When the instructions are run on an electronic device, the electronic device causes the electronic device to execute any possible implementation as in the first aspect. The card display method described in the method.

It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be achieved in any single embodiment. On the contrary, it can be understood that the description of features or beneficial effects means that specific technical features, technical solutions or beneficial effects are included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions or beneficial effects in this specification do not necessarily refer to the same embodiments. Furthermore, the technical features, technical solutions and beneficial effects described in this embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that embodiments can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects may also be identified in specific embodiments that do not embody all embodiments.

Description of the drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are: For some embodiments of the present invention, those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application;

Figure 2 is a schematic diagram of the software architecture of an electronic device provided by an embodiment of the present application;

Figures 3 to 7 are schematic interface diagrams of a process of adding conversation cards provided by embodiments of the present application;

Figures 8 to 9 are schematic diagrams of the dimensions of conversation cards provided by embodiments of the present application;

Figure 10 is a schematic diagram of the interface for adding multiple blank conversation cards on the desktop provided by the embodiment of the present application;

Figures 11 to 12 are schematic diagrams of the display effect of the card pile provided by the embodiment of the present application;

Figures 13 to 18 are schematic diagrams of the interface for adding contacts to a card provided by embodiments of the present application;

Figure 19 is a schematic diagram of a contact list provided by an embodiment of the present application;

Figure 20 is a schematic diagram of the display effect of multiple conversation cards with messages provided by the embodiment of the present application;

Figures 21 to 23 are schematic diagrams of the interface for deleting conversation cards provided by the embodiment of the present application;

Figures 24 to 26 are schematic interface diagrams of operation cards displaying information provided by embodiments of the present application;

Figures 27 to 28 are schematic diagrams of conversation interfaces jumping from conversation cards to conversation applications provided by embodiments of the present application;

Figure 29 is a flow chart of a conversation card editing process provided by an embodiment of the present application;

Figure 30 is a flow chart of a process of deleting conversation cards provided by an embodiment of the present application;

Figure 31 is a flow chart for updating session card display information provided by an embodiment of the present application.

Detailed ways

The terms “first”, “second”, “third”, etc. in the description, claims and drawings of this application are used to distinguish different objects, rather than to limit a specific order.

In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "exemplary" or "such as" is intended to present the concept in a concrete manner.

In order to describe the following embodiments clearly and concisely, a brief introduction to related technologies is first given:

A widget (web widget, widget, also called a component) is a derivative of Web 2.0, similar to a small application that can be applied to mobile devices. Widget can be a clock, a diary, a video, a weather forecast, a flash game, etc.

"Widget", "Card", and "Card Stack" are all forms of widgets, used to display various related information, such as text, images, buttons, maps, etc.

As mentioned before, when the mobile phone receives a conversation type message, such as a short message or For other instant messaging messages, the user needs to open the corresponding application or notification bar, and then enter the interactive interface of the contact corresponding to the message to view or reply to the message. It can be seen that in the above two scenarios, the user needs at least two steps to enter the interactive interface corresponding to the contact in the message, resulting in low efficiency of human-computer interaction.

In order to solve this problem, the present application provides a card display method, which can display the corresponding card (ie, the first card, the first card includes the name of a contact in a conversation application) on the desktop of the electronic device. , the user can directly click on the card to enter the conversation interface corresponding to the contact. There is no need to open the conversation APP or open the notification bar first, and then enter the conversation interface corresponding to the first contact. Therefore, the operation for the user to enter the conversation interface is simplified and improves the efficiency. Human-computer interaction efficiency and improved user experience.

For example, the electronic device in this application can be a portable computer (such as a mobile phone), a tablet computer, a notebook computer, a personal computer (PC), a wearable electronic device (such as a smart watch), or augmented reality. AR)/virtual reality (VR) equipment, vehicle-mounted computers, etc. The following examples do not impose special restrictions on the specific form of the electronic equipment.

Taking the electronic device as a mobile phone as an example, as shown in FIG. 1 , a schematic structural diagram of an electronic device provided by an embodiment of the present application is shown.

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

It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 102. In other embodiments, the electronic device 102 may include more or fewer components than illustrated, or some components may be combined, or some components may be separated, or may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units.

The internal memory 121 may be used to store computer executable program code, which may include an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The executable program code includes instructions, and the processor 110 executes the instructions stored in the internal memory 121 to cause the electronic device to perform various functional applications and data processing.

The display screen 194 is used to display images, videos, a series of graphical user interfaces (graphical user interface, GUI), etc. For example, in this embodiment of the present application, the display screen can be used to display widget cards.

The operating system of an electronic device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of this application takes the Android system with a layered architecture as an example to illustrate the software structure of the electronic device.

Figure 2 shows a software structure block diagram of the terminal device according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. Taking the Android system as an example, in some embodiments, the Android system is divided into four layers, from top to bottom: application layer (application, APP), application framework layer (Framework), class library layer, and kernel layer. (Kernel).

Figure 2 only shows the software layer related to the card display method provided by the embodiment of the present application and the modules included in the software layer.

As shown in Figure 2, the application layer can include a series of application packages. For example, the application package may include desktop, instant messaging, video, call, browser, calendar, map, music, camera and other APPs.

Among them, the conversational application involved in this application refers to an APP that can generate conversational messages, such as instant messaging and short messages as shown in Figure 2. Among them, instant messaging refers to a type of applications with instant messaging functions, such as WeChat, QQ, DingTalk, etc.

In an exemplary embodiment of the present application, a desktop application (which may be called a desktop, a home screen, or a Launcher, etc.), for example, in an Android system, the desktop is also called a desktop launcher (Launcher). For convenience of description, they are collectively referred to as the desktop in this article.

In this embodiment of the present application, a card can be created on the desktop. The meeting card here refers to a service card displayed on the desktop that can display conversation messages with contacts in a conversation APP. For example, display the contact's avatar, name, conversation message, etc. in the card. Furthermore, the user can also jump directly to the contact's conversation interface by clicking on the card. For example, a card with WeChat contact "Cat" is added to the desktop. When the user clicks on the card of "Cat", the WeChat application is triggered to open "Cat". ” dialogue interface.

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

In an exemplary embodiment, as shown in Figure 2, the application framework layer may include a notification manager (Notification Manager), a session manager (People Manager), and a card manager (App WidgetManager). Can also include resource managers, window managers, view systems, content providers, etc.

Among them, the notification manager, Notification Manager, is used to manage received notification messages, for example, after receiving notification changes, update the status of the notification.

The session manager is an interface on the Framework side, responsible for parsing dialogue notifications and generating corresponding session messages.

The card manager is used to provide an interface for placing cards on the desktop, and is responsible for the card generation, update and other processes.

The system library layer includes functional functions that need to be called by the Java language, as well as the core library of Android. This layer also includes the Android runtime (Android runtime), which is responsible for the scheduling and management of the Android system. In an exemplary embodiment, the system library layer includes a surface manager, a three-dimensional graphics processing library, a media library, a two-dimensional graphics engine, etc.

The kernel layer is a layer between hardware and software. In an exemplary embodiment, the kernel layer includes a display driver, a camera driver, a sensor driver, an audio driver, etc.

It should be noted that the embodiment of this application takes the Android system as an example for description, but its basic principles are also applicable to terminal devices using other operating systems. This application does not limit the operating system used by the terminal device.

The following takes the electronic device as a mobile phone as an example, and introduces a process of adding conversation cards on the desktop provided by the embodiment of the present application in conjunction with Figures 3 to 7. For example, a conversation type APP can include SMS, QQ, DingTalk, etc.

In an exemplary embodiment, as shown in Figure 3, the mobile phone displays a desktop, and the user performs a two-finger pinch operation on the desktop to jump to the display interface shown in Figure 4.

In another exemplary embodiment, a desktop card item is provided in the setting application of the operating system, and the user can enter the desktop card setting item through the setting application. The embodiment of the present application does not limit the method of entering the desktop card setting interface.

As shown in Figure 4, the interface is a desktop editing interface. The upper area of the interface displays an editable desktop page 10, and the desktop page can be replaced by sliding the desktop page left or right. The bottom area of the display interface displays operation options, such as wallpaper, desktop card 20, switching effects, desktop settings, etc.

After the user clicks on the desktop card 20 shown in Figure 4, the display interface jumps from the interface shown in Figure 4 to the interface shown in Figure 5.

As shown in Figure 5, a card type display interface 100 is displayed on the display interface. The interface includes one or more card types, such as conversation 101, clock, memo, weather, gallery, and contacts. After the user clicks the session 101 option shown in Figure 5, the display interface jumps to the interface shown in Figure 6.

Among them, the session 101 option shown in Figure 5 is a general term for session type APPs, that is, the session here does not specifically refer to one APP, but includes multiple APPs of session type, such as, SMS, QQ, DingTalk, etc., the embodiments of this application do not limit conversational APPs.

As shown in FIG. 6 , the display screen displays the session card interface 110 , which includes the size and style of the card 111 . In an exemplary embodiment, the user can slide the conversation card interface 110 left or right to switch to display cards of other sizes and styles.

In other embodiments, cards of other sizes and styles can be switched and displayed in other ways, such as sliding the page up and down, and the user sliding the interface up and down to switch the cards displayed on the interface. This application does not limit the specific method of switching display cards.

For example, the size of the card 111 shown in Figure 6 is 2×2. The card can also be of other sizes. The size of the card 111 shown in Figure 8 is 4×2, and the size of the card 111 shown in Figure 9 is 2×1. The embodiment of the present application does not limit the size of the card.

In an exemplary embodiment, the style of the card may include various parts of the content displayed on the card (such as avatar, contact name (or nickname), message content, etc.), card display content layout, transparency, card color, etc., this application There are no restrictions on card styles. Users can choose the corresponding style based on the card styles provided by the session card interface.

In addition, as shown in FIG. 6 , an exit control 112 is also provided at the top of the session card interface 110. After the user clicks the exit control 112, the user exits the session card interface. In addition, a return control 113 is provided in the upper left corner of the conversation card interface 110. After the user clicks the return control 113, the user returns to the upper level interface of the conversation card interface 110, that is, the card type display interface 100 shown in Figure 5.

For example, after selecting card 111, the user can drag card 111. When the card 111 is dragged out of the conversation card interface 110, the conversation card interface 110 can automatically disappear, so that the mobile phone displays the desktop located under the conversation card interface 110. Furthermore, the user can continue to drag the card 111 and place the card 111 on any desktop page. At this time, as shown in FIG. 7 , the card 111 displayed on the desktop is a blank card, and the type of the card 111 is a conversation type. Blank cards are cards without any information.

During the process of adding card 111 to the desktop, the user can place the card 111 at the target location on the desktop by dragging the card 111. As shown in Figure 7, the user can place the card 111 at the lower left of other application icons on the desktop.

After the card 111 is added, the user can also move the card 111 on the desktop by dragging the card 111. As shown in Figure 7, the user can move the card 111 from the position to the dotted area 114. In addition, the card 111 can also be moved to other desktop pages by dragging and dropping.

In another scenario, at least two blank cards are added to the desktop, as shown in Figure 10. Each blank card is laid flat on the desktop. The layout of the blank cards can be determined according to the size of each blank card. This is not discussed here. Repeat.

As shown in FIGS. 7 and 10 , in an exemplary embodiment, a universal avatar is displayed on the blank card, and the universal avatar is located in the middle of the blank card. Of course, in other embodiments, the position of the universal avatar in the blank card can be adjusted, and this application does not limit this.

The user can adjust the position of the card 111 on the desktop according to the needs and the size of the blank area on the desktop. The blank area refers to an area where no application icon is placed, and the embodiment of the present application does not limit the specific location of the card 111 .

In a scenario where multiple cards 111 are placed on the desktop, multiple cards can also be displayed in a stacked manner. As shown in Figure 11, three cards 111-1, 111-2 and 111-3 are stacked together, and the cards are displayed in the current view. 111-1, card 111-2 is blocked by card 111-1, and only the edge of the card can be displayed. Similarly, card 111-3 is blocked by card 111-2.

The user can click on any card in the card pile, and the clicked card switches to the current view. For example, after the user clicks on card 111-2, card 111-2 switches to the current view, that is, all cards 111-2 can be displayed. This At this time, card 111-1 is blocked by card 111-2.

In addition, cards of different sizes can also be displayed in a stacked manner. Cards of different sizes can be stacked in order from small to large. For example, as shown in Figure 12, cards 111-4, 111-5, and 111-6 are stacked. Together, the current view displays card 111-4, and part of card 111-5 is blocked by card 111-4. Similarly, part of card 111-6 is blocked by card 111-5. The way of viewing the card pile shown in Figure 12 is the same as the way of viewing the card pile shown in Figure 11, and will not be described again here.

Figures 11 and 12 are only schematic diagrams of possible card piles, and the card piles can also be displayed in other stacking styles, which is not limited by this application.

Subsequently, you can edit the blank card of the conversation type added to the desktop, such as adding a conversation contact, that is, binding the card to the conversation contact, thereby directly displaying the contact's relevant information on the card, such as avatar, name and conversation. Content etc.

The process of editing cards provided by the embodiment of the present application will be introduced below with reference to Figures 13 to 20.

As shown in Figure 13, the user can long press the blank card 111 to jump to the display interface shown in Figure 14.

In an exemplary embodiment, as shown in FIG. 14 , a card operation interface 200 is displayed on the upper layer of the desktop, a blank card 111 is displayed on the card operation interface 200 , and a card operation tab 210 is displayed above the blank card 111 .

The card operation tab 210 displays operation options, such as options for removing, editing cards, and more "session" cards. Of course, other options may also be included, such as hiding, etc. This application does not limit the number and content of options displayed on the card operation tab 210.

In addition, in other exemplary embodiments, the card operation tab 210 can also be displayed at other locations on the card operation interface 200. This application does not limit the display location of the card operation tab.

After the user clicks the "Edit Card" option shown in Figure 14, the page jumps to the interface shown in Figure 15. As shown in Figure 15, a recent message interface 220 is displayed on the upper layer of the desktop. The recent message interface 220 includes the "Recent Contacts" ” option 221. After the user clicks the “Recent Contacts” option 221, the user can check the most recent contacts. For example, the page jumps to the recent contact list page 230 as shown in Figure 16. In addition, the description here only takes recent contacts as an example. For example, all contacts who have sent conversation messages within a period of time can be viewed, or all contacts who have sent conversation messages can be viewed.

In an example, as shown in FIG. 15 , the recent message interface 220 may also include prompt information for “view recent messages” and “quickly reply to messages”. Among them, the prompt message "View recent messages" can remind the user that after adding a contact's card on the desktop, the user can view recent conversation messages with the contact directly on the card. The prompt message of "Quickly reply to messages" can remind users that after adding a contact's card on the desktop, they can reply to the message directly on the card. Of course, in other examples, the recent message interface 220 may not include the above-mentioned "view recent messages" and "quickly reply to messages" prompts, or may further include other prompt information, which is not limited in this application.

As shown in Figure 16, one or more contacts are displayed in the recent contact list page 230. These contacts can be contacts that have received notification messages from all conversation type APPs in the recent period, such as WeChat contacts, SMS contacts, QQ contacts, etc.

In one scenario, as shown in Figure 19, there are a large number of contacts in the recent contact list, and only some of the contacts can be displayed on one screen. For example, as shown in Figure 16, only 7 contacts can be displayed on one screen. , that is, from contact "Cat" to contact "CCC", all contacts cannot be displayed. The user can slide up the recent contact list page 230 to display other contacts after "CCC" as shown in Figure 19.

For example, each contact option in the contact list shown in Figure 16 includes the contact's avatar and name. For example, in Figure 16, Cat, Dog, Parrot, Lion, AAA, BBB and CCC all represent the names set by the contact in the session APP to which they belong.

In an exemplary embodiment, the contact avatar is the personal avatar set by the contact in the conversational APP to which it belongs. Furthermore, in order to indicate the APP to which each contact belongs, the icon of the conversation APP to which the contact belongs can also be displayed in the lower right corner of the personal avatar. For example, in the contact list shown in Figure 16, the first two contacts are from The avatars of these two contacts are displayed in the lower right corner/> icon.

In an exemplary embodiment, as shown in FIG. 16 , a hidden control 231 and a search bar 232 may be provided at the top of the recent contact list page 230 . After the user clicks on the hidden control 231, the recent contact list page 230 is hidden, and the desktop or other pages can be displayed. This application does not limit this.

The user clicks on the search bar 232 to enter the search page, where he or she can input at least part of a contact's name to quickly filter out contacts containing the name, which simplifies the user's operation of finding contacts and improves the efficiency of human-computer interaction.

The user can click on any contact row in the recent contact list page 230 to add the selected contact to the card 111 . As shown in Figure 16, after the user clicks on the contact "Parrot", it jumps to the interface shown in Figure 17 or Figure 18.

In one scenario, the contact "Parrot" is a historical contact, and a historical contact refers to a session type notification message (which can also be called a session notification message, or session notification) that has been received by the contact within a period of time. However, the notification center does not contain the conversation message of the contact. In this scenario, as shown in Figure 17, only the contact's avatar and name can be displayed on the card 111.

In another scenario, the contact "Parrot" is an active contact, and the active contact refers to the session type notification message containing the contact in the notification center. In this scenario, as shown in Figure 18, in addition to displaying the avatar and name of the contact "Parrot", the card 111 can also display the content of the recently received message from Parrot.

As shown in Figure 20, the types of message content displayed by the card include but are not limited to text, pictures, videos, audios, links, etc. The embodiment of the present application does not limit the types of message content that can be displayed by the card.

In addition, after adding a contact to a blank card, you can also modify the contact associated with the card through the edit card option. For example, as shown in Figure 17, the contact associated with card 111 is the SMS contact "Parrot". The user can long press the card 111 in Figure 17 to enter the card operation interface 200 shown in Figure 14, and further click the "Edit Card" option to enter the interface shown in Figure 15 or 16. The user can select the card from the contact list shown in Figure 16 After selecting a new contact, the latest contact information is finally displayed on card 111.

In yet another scenario, the user can also delete the card 111 on the desktop. The card deletion process provided by the embodiment of the present application will be introduced below with reference to Figures 21 to 23.

As shown in Figure 21, after the user long presses the card 111, it jumps to the interface of the card operation tab 210 shown in Figure 22. After the user clicks the "Remove" option, the card 111 on the desktop is deleted, and the user jumps to the interface shown in Figure 22. The desktop page shown in 23.

The above content is the user's operation process on the card. In another exemplary embodiment, the user can also operate on the content of the card. The process of operating the card content will be introduced below with reference to Figures 24 to 26.

As shown in Figure 24, the contact's avatar, name ("Parrot") and latest message are displayed on the card 111, and "reply" and "mark read" controls can also be displayed. After the user clicks the "reply" control displayed on the card 111, the display interface of the card 111 is updated to the interface shown in Figure 25.

As shown in FIG. 25 , a reply column 310 is displayed in the bottom area of the card 111 , and a send icon 320 is displayed on the right side of the reply column 310 . The user can input the content to be replied in the reply column 310. After inputting the content, the user clicks the send icon 320 to send the reply message. As shown in Figure 26, the message content display area 330 of the card 111 is updated with the message replied by the user, that is, the message in the card 111 is updated with the latest message with the contact "Parrot".

After adding a contact's card on the desktop, after receiving a conversation message sent by the contact, the message can be updated and displayed on the contact's card.

In one scenario, as shown in Figure 17, the card 111 added on the desktop does not include the contact's message. After that, after receiving the contact's message, the received message is displayed in the card 111, as shown in Figure 18 As shown, the card 111 also includes message content. For example, the message content can be displayed on the right side of the avatar.

In another scenario, as shown in Figure 18, the card 111 added on the desktop includes the contact's conversation message (which can be called the first conversation message). After receiving the second conversation message sent by the contact, the card The first message displayed in 111 is updated as the second conversation message, that is, the message in the card will be updated as the conversation content is updated.

In another scenario, after the user replies to the conversation message to the contact, as shown in Figure 18, the card 111 displays the conversation message (such as the first conversation message) sent by the contact "Parrot", and then the user replies to " Parrot" replied to a conversation message (such as the third conversation message). At this time, the message content in the card 111 is updated from the first conversation message to the third conversation message. For example, the user can directly reply to the third conversation message in the notification containing the first conversation message in the notification center, or the user can directly reply to the third conversation message in the conversation application; for another example, as shown in Figure 24, the user can also directly reply to the third conversation message. Reply to the third conversation message on the contact's card. This application does not limit the ways in which users can reply to conversational messages.

Furthermore, in an exemplary embodiment, the conversation messages displayed in the card may be unread conversation messages from the contact. For example, unread conversation messages can be messages that the user has not viewed. For example, after receiving the conversation message sent by the contact, the user did not reply to any message, did not mark the message as read, did not delete the message from the notification center, etc. Correspondingly, if the user marks the conversation message sent by the contact as read, or directly deletes the conversation message from the notification center, the content displayed in the card will be updated synchronously, that is, the conversation message displayed in the card will be deleted.

The process of jumping from a card to a conversational APP interface provided by the embodiment of the present application will be introduced below with reference to Figures 27 and 28.

After the user clicks on the card displayed on the desktop, the display interface of the mobile phone jumps directly to the conversation interface of the application to which the contact associated with the card belongs. As shown in Figure 27, after the user clicks on the card 111 of the SMS contact "Parrot", the user jumps to the interface shown in Figure 28, which is the conversation interface of the contact "Parrot" in the SMS application.

It can be seen from the above that the card display method provided by the embodiment of the present application can add a Widget card corresponding to the session type APP on the desktop, and further can add associated contacts to the Widget card. When the user clicks on the card, it jumps directly to the conversation interface corresponding to the contact, which simplifies user operations and improves the efficiency of human-computer interaction.

On board In electronic devices of 12 years old and above, when the electronic device is turned on, the class PeopleSpaceWidgetProvider that implements desktop gadgets registers the card component with the desktop (System UI). After the registration is completed, the card is displayed in the card type display interface 100 shown in Figure 5 Session options are displayed in the type list. After the user clicks the session option, it jumps to the session card interface shown in Figure 6. The user can select a card of any size to add to the desktop.

Configure the styles of each interface and the requests generated by clicking options on the interface in the System UI configuration file.

For example, the configured interface may include a card type display interface 100, a conversation card interface 110, a card operation tab 210, a recent message interface 220, a contact list interface 230, etc. For example, clicking the edit card option on the card operation tab 210 generates a request to call the contact list, or, for example, clicking a card to which a contact has been added generates a request to jump to the contact dialogue interface of the corresponding application.

After adding the card to the desktop, you can edit the card, such as adding contacts, etc. The editing process of the session type card provided by the embodiment of the present application will be introduced below with reference to Figure 29.

As shown in Figure 29, the process of editing a card may include:

S110: After receiving the card editing operation, the session selection interface (PeopleSpaceActivty) sends a request to obtain recent contacts to the session card manager (PeopleSpaceWidgetManager).

PeopleSpaceActivty is the session selection interface when adding session type cards. For example, the conversation selection interface includes the recent message interface 220 shown in FIG. 15 .

PeopleSpaceWidgetManager is the manager of session type cards. One of its functions is to listen for notifications (Notification), that is, it can sense changes in notification messages.

As shown in Figure 15, after the user clicks the recent contact option 221 in the recent message interface 220, PeopleSpaceActivty will receive a contact acquisition request and initiate a request to call the recent session acquisition method in PeopleSpaceWidgetManager.

S120. The session card manager (PeopleSpaceWidgetManager) initiates a request to the notification manager (NotificationManager) to obtain recent contacts.

Recent contacts include active contacts and historical contacts. The recent contacts here refer to the session notification messages sent by the contact received within a period of time, where the end time of the period of time here is the current timestamp.

The active contact refers to the session notification message containing the contact in the notification message. A historical contact refers to a contact that has received session notification messages within a period of time, but the current notification message does not contain the session notification message of this contact, for example, the session notification message has been cleared from the notification.

PeopleSpaceWidgetManager obtains the active contacts in the notification by calling the getPriorityTiles method, and obtains the historical contacts by calling the getRecentTiles method.

After PeopleSpaceActivty calls the getPriorityTiles method and getRecentTiles method of PeopleSpaceWidgetManager, it triggers PeopleSpaceWidgetManager to initiate a call to NotificationManager's recent session acquisition method.

Among them, after the getPriorityTiles method is called, PeopleSpaceWidgetManager will call the getconversation(true) method of NotificationManager. The getconversation(true) method is used to obtain Conversations whose isImportantConversation field of NotificationChannel is true.

After the getRecentTiles method is called, PeopleSpaceWidgetManager will call the getconversation(false) method of NotificationManager. The getconversation(false) method is used to obtain Conversations in NotificationChannel without limiting the value of the isImportantConversation field.

S130, the notification manager (NotificationManager) returns the recent session to the session card manager (PeopleSpaceWidgetManager).

After the getconversation(true) method is called, NotificationManager returns the active session to PeopleSpaceWidgetManager. The returned active session may include active contact information (such as avatar and name), session content, and the timestamp corresponding to the last session content, etc.

After the getconversation(false) method is called, NotificationManager returns the historical conversation to PeopleSpaceWidgetManager. The returned historical conversations may include historical contact information and the timestamp corresponding to the last conversation content.

S140. The conversation card manager (PeopleSpaceWidgetManager) sorts the recent conversation timestamps from early to late to obtain a recent contact list.

The getPriorityTiles method in PeopleSpaceWidgetManager sorts the timestamps of active sessions from early to late, obtains active contact information, and obtains active contacts.

The getRecentTiles method sorts the historical session timestamps from early to late to obtain historical contacts.

For example, if the timestamp of one session is 16:00 on 2022.02.01, and the timestamp corresponding to another session is 17:00 on 2022.02.01, then the session corresponding to 16:00 is ranked before the session corresponding to 17:00.

After obtaining the active contact list and the historical contact list, create a corresponding PeopleSpace Tile View (contact list item view) for each contact, and arrange the historical contacts after the active contacts to finally form a contact list.

Among them, PeopleSpaceTileView is the view layout of a single list item in the contact list, as shown in Figure 16 and Figure 19. The display content layout of a contact.

S150, the session card manager (PeopleSpaceWidgetManager) returns the recent contact list to the session selection interface (PeopleSpaceActivty).

S160, the session selection interface (PeopleSpaceActivty) displays the recent contact list.

In this scenario, the session selection interface includes the contact list interface 230 shown in FIG. 16 .

In an exemplary embodiment, the recent contact list displayed on the session selection interface may only display the contact's information, such as avatar and name, so as to facilitate the user to intuitively view the contact's information. For example, the recent contact list may adopt the layout shown in Figure 16 or Figure 19.

S170, after detecting the operation of selecting a contact, the session selection interface (PeopleSpaceActivty) calls the card update method of the session card manager and transmits the information of the clicked contact (ie, the first target contact) to the session card manager. .

After the user clicks any list item in the contact list displayed by PeopleSpaceActivty, PeopleSpaceActivty passes the first target contact information (such as avatar, name, conversation content, etc.) to PeopleSpaceWidgetManager, and calls the card update method updateWidgets in PeopleSpaceWidgetManager so that Update the contacts and interface display of the conversation card.

S180. The session card manager (PeopleSpaceWidgetManager) obtains the first target view interface of the first target card based on the information corresponding to the first target contact.

The view interface in this application may include a display interface composed of the style and layout of each display element in the card, and the interface is presented in the form of a card.

For example, the elements displayed on the card may include the contact's avatar and name, or may also include controls such as reply, mark as read, and delete. The avatar, name, and controls are the display elements of the card. The display interface of the card can be obtained according to the style and layout of each display element.

In this scenario, the first target card is the currently edited blank card.

PeopleSpaceWidgetManager calls the updateWidgets method and further calls the updateAppWidgetViews method. The updateAppWidgetViews method assembles the view interface of the first target card based on the information corresponding to the first target contact (such as avatar, name, conversation content), that is, the first target view interface.

The updateAppWidgetViews method will call the createRemoteViews of the PeopleTileViewHelper method to create RemoteViews.

PeopleTileViewHelper is the Helper class of PeopleTileView, which provides a display view for PeopleSpaceWidgetManager when it updates the session card.

If the first target contact is an active contact, the first target view interface includes the contact's avatar, name, content of the latest conversation, and the display layout of various information, for example, card 111 shown in Figure 18 The information displayed and the display layout of each information.

If the first target contact is a historical contact, the first target view interface includes the contact's avatar, name, and display layout of various information. For example, the information displayed on the card 111 and the display layout of each piece of information are shown in FIG. 17 .

S190. The session card manager (PeopleSpaceWidgetManager) sends the unique identifier of the first target card and the first target view interface to the desktop card manager (AppWidgetManager).

The desktop card manager (AppWidgetManager) is located at the application framework layer in the electronic device software architecture. It is used to provide an interface for placing cards on the desktop and is responsible for card generation, updating, etc. Furthermore, AppWidgetManager generates a unique identification (i.e., card ID) for each card. PeopleSpaceWidgetManager can get the ID of the currently added card from AppWidgetManager.

PeopleSpaceWidgetManager calls the updateAppWidget method of AppWidgetManager to send the assembled first target view interface and the unique identification of the first target card (i.e. card ID) to AppWidgetManager so that AppWidgetManager can update the View (i.e. first target view interface) to AppWidget( That is the first target card).

S1100. The desktop card manager (AppWidgetManager) updates the interface of the first target card to the first target view interface.

AppWidgetManager determines the card whose interface is to be updated based on the received card ID, and further updates the card's interface to the received first target view interface, thereby completing the card interface update. For example, the card is updated from the interface shown in Figure 13 to the interface shown in Figure 17 or Figure 18.

S1110. The session card manager (PeopleSpaceWidgetManager) updates the mapping relationship between the globally unique identifier of the first target contact and the unique identifier of the first target card into the mapping relationship table.

The operating system of the electronic device creates a globally unique identifier, that is, a Key, for each contact in the contact list, which is used to uniquely identify the contact.

The electronic device maintains a mapping relationship between the card ID and the globally unique identifier (ie, Key) of the contact added to the card. For example, the ID of a certain card is abc, and the Key of the contact added to the card is 123. Then establish the mapping relationship between abc and 123.

In an exemplary embodiment, there may be a one-to-one or one-to-many mapping relationship between contacts and cards. In other words, a conversation card may be created for one contact, or a conversation card may be created for the same contact. At least two conversation cards. If there is a one-to-many relationship between contacts and cards, the view interfaces of at least two conversation cards corresponding to the contact are updated simultaneously.

After the user adds the first target contact in the first target card, PeopleSpaceWidgetManager will save the mapping relationship between the card ID of the first target card and the Key of the first target contact into the above-mentioned mapping relationship table.

In another scenario, the user can also change the contact associated with the conversation card to which the contact has been added. The process of changing the contacts associated with a card is similar to the process of adding contacts to a blank card and will not be described in detail here. Among them, the process shown in S1120 to S1180 in the figure is the process of changing the contact person associated with the card:

S1120: After receiving the card editing operation, the session selection interface (PeopleSpaceActivty) calls the method of the session card manager (PeopleSpaceWidgetManager) to obtain recent contacts.

Similar to the process of editing a blank card, after PeopleSpaceActivty receives the user's click on the "Edit Card" option shown in Figure 14, it calls the getPriorityTiles method and getRecentTiles method of PeopleSpaceWidgetManager to obtain active contacts and historical contacts respectively, and further obtains active contacts including active contacts. Contact list of contacts and historical contacts.

It should be noted that the contact list obtained by PeopleSpaceWidgetManager in this step may be different from the contact list obtained in S140.

As time goes by, the session notification messages received by the electronic device will be updated, and the active contacts obtained in S140 may become historical contacts obtained in this step. The contact list obtained in this step may not include some historical contacts obtained by S140. Therefore, the contact list obtained at different times may be different. However, the method of obtaining the contact list is the same and will not be repeated here.

S1130. The session card manager returns the contact list to the session selection interface.

S1140: After receiving the operation of selecting a contact, the session selection interface calls the card update method of the session card manager and transmits the information of the second target contact to the session card manager.

The contact selected by the user is the second target contact. The process of this step is the same as that of S170 and will not be described again here.

S1150. The conversation card manager uses the information of the second target contact to obtain the second target view interface of the second target card.

The second target card refers to the currently edited card, and the second target view interface is the target view interface corresponding to the second target card.

S1160. The session card manager sends the card ID corresponding to the second target card and the second target view interface to the desktop card manager.

S1170. The desktop card manager updates the interface of the second target card to the second target view interface.

S1180. The conversation card manager updates the contact corresponding to the second target card in the mapping relationship table to the second target contact.

The session card manager searches the mapping relationship table and updates the contact's key in the mapping relationship data corresponding to the card ID of the second target card to the key of the second target contact.

In a possible implementation, the process of modifying the contact associated with the card may be: replacing the first contact associated with the card with the second contact. For example, as shown in Figure 17, the original contact associated with card 111 is "Parrot". After modification, the contact associated with card 111 becomes “Cat”, that is, card 111 displays the information of WeChat contact “Cat”.

In another possible implementation, the process of modifying the contacts associated with the card may also be: adding another contact based on the original contact of the card, that is, one card is associated with two contacts. For example, as shown in Figure 17, the original contact of card 111 is "Parrot". After modification, the contacts of card 111 become "Parrot" and "Cat", that is, card 111 displays the SMS contact "Parrot" and the WeChat contact Information about the person "Cat". Of course, in other possible implementations, a card can also be associated with a larger number of contacts, for example, 3 or more. The number of contacts that the card can be associated with can be determined according to the size of the card. For example, the larger the size of the card, the greater the number of contacts. The more contacts you can associate.

The card display method provided in this embodiment can create a conversation card on the desktop, and then add a contact to the conversation card, so that the card displays the contact's information, such as avatar, name, conversation message content, etc. The process of editing cards is simple. Moreover, after adding a conversation type card, the conversation messages of the contacts associated with the card can be displayed directly on the card. The user does not need to open the notification bar to view the notification messages, nor does he need to open the conversation type APP to view the messages of the corresponding contact, which simplifies The user's operation of viewing conversation type messages improves the efficiency of human-computer interaction and improves the user experience.

In addition, according to the process shown in Figures 21 to 23, the user can also delete the session type card added to the desktop. As shown in Figure 30, the process of deleting session cards is as follows:

S210, after receiving the event of deleting the session type card, the PeopleSpaceWidgetProvider calls the delete card method of the desktop card manager and passes the card ID of the target card to the desktop card manager.

For example, the user clicks the "Remove" option shown in Figure 22 to delete a card that has been added to the desktop.

PeopleSpaceWidgetProvider is a class that implements desktop gadgets. When the touch screen of the electronic device detects that the user clicks the "Remove" option, an event to delete the card is generated and passed to PeopleSpaceWidgetProvider.

After receiving the event of deleting a card, PeopleSpaceWidgetProvider passes the card ID of the target card to AppWidgetManager and calls the delete card method of AppWidgetManager to delete the target card. The target card is the card to be deleted.

S220: The desktop card manager calls a method of deleting a card to delete the target card on the desktop based on the card ID of the target card.

As shown in Figure 22, after the user clicks the "Remove" option in the card operation tab 210, the desktop page shown in Figure 23 is displayed, and the desktop page does not include the card 111.

S230: The desktop card manager returns a message that the card is successfully deleted to the PeopleSpaceWidgetProvider.

S240, PeopleSpaceWidgetProvider calls the method in the session card manager to update the mapping data of the target card.

PeopleSpaceWidgetProvider passes the action to update the mapping data, such as deletion, and the card ID of the target card to PeopleSpaceWidgetManager, so that PeopleSpaceWidgetManager can delete the data entry corresponding to the card ID in the mapping relationship table.

S250: The session card manager deletes the mapping data entry corresponding to the target card in the mapping relationship table based on the card ID of the target card.

In the process of deleting a card provided by this embodiment, after detecting the user's operation of deleting a card on the desktop, the method of deleting the card is executed, and at the same time, the mapping relationship table that stores the mapping relationship between the card ID and the associated contact is deleted. Mapping data corresponding to the deleted card in , ensuring that the data in the mapping relationship table is accurate.

After adding a contact to a card on the desktop, when the contact's conversation message is received, the latest conversation message will be updated to the card corresponding to the contact. For example, as shown in Figure 17, after adding the contact "Parrot" to the card 111, the card 111 only displays the avatar and name of the contact "Parrot". After receiving the conversation message of "Parrot", the card 111 is updated to the view interface shown in Figure 18, that is, the card 111 not only displays the avatar and name of the contact "Parrot", but also displays the content of the latest conversation message of "Parrot".

The process of updating the conversation messages displayed on the conversation card will be introduced below with reference to Figure 31. As shown in Figure 31, the process of updating the session message displayed on the card can include two situations. One can be a process of updating the view interface of the corresponding card by monitoring the notification message update action of the notification center, as shown in S310 to S380 in Figure 31. The other process is to directly monitor the update action of the session message to update the view interface of the corresponding card, such as the process shown in S390 to S3140 in Figure 31.

The notification message in this article refers to the message received by NotificationListener by monitoring NotificationService. For example, the notification message can include the following fields: update action (receive or remove), whether it belongs to the session type (true or false), and the application to which the notification belongs (i.e. The application that sent the notification message), the notification contact (the contact that sent the notification), the notification content, etc.

The conversation message in this article refers to the interactive message between the user and a contact in the conversation APP. The conversation message can include the following fields: the application to which the conversation belongs, the conversation contact and the conversation message content.

In the scenario where the corresponding card is updated by listening to the notification message, the notification center receives a notification message of session type (that is, whether the field of whether it belongs to the session type is true), and then extracts the application, notification contact, and notification to which the notification belongs from the notification message. Content and other content obtain conversation messages, and then update these messages to the corresponding cards.

The following first introduces the process of updating the card view interface shown in S310 to S380:

S310: After the operating system of the electronic device is started, the session card manager is triggered to monitor the notification listening service.

One of the main functions of PeopleSpaceWidgetManager (session card manager) is to monitor the NotificationListenerService of the application framework layer to monitor Notification (system notification).

After the operating system of the electronic device is started, the start method of the Status Bar component of the desktop (SystemUI) attaches the notification handler (Notification Handler) of the PeopleSpaceWidgetManager to the instance mNotificationListener of the NotificationListener by calling the attach method of the PeopleSpaceWidgetManager. PeopleSpaceWidgetManager monitors the NotificationListenerService of the application framework layer.

Among them, NotificationListener belongs to System UI and is an inherited class of NotificationListenerService. It mainly implements the interface exposed by NotificationListenerService.

S320: After listening to the update of the notification message, the notification listener obtains the information of the notification message.

NotificationListener includes onNotificationPosted method and onNotificationRemove method. When the system receives a new notification, NotificationListener will call back the onNotificationPosted method to obtain relevant information about the notification received by the system, such as update action (ie, reception), notification content, notification contact, whether it is a session type notification, etc.

When it detects that a notification is deleted, NotificationListener will call back the onNotificationRemove method to obtain relevant information about the deleted notification, such as update action (ie, removal), notification content, notification contact, whether it is a session type notification, etc.

S330: The notification listener delivers the notification message information that needs to be updated to the session card manager.

PeopleSpaceWidgetManager's NotificationHandler also includes onNotificationPosted method and onNotificationRemove method.

After the NotificationListener calls back its own onNotificationPosted method and onNotificationRemove method, it will call the Notification Handler's onNotificationPosted method and onNotificationRemove method, thereby passing the obtained notification message information to the People SpaceWidget Manager.

S340, the session card manager determines whether the updated notification message belongs to a session type notification; if so, continue to execute S350; if not, end the current process.

After receiving the updated notification message information delivered by the notification, PeopleSpaceWidgetManager further calls the updateWidgetsWithNotificationChanged method to determine whether the updated notification message is a session type notification.

The relevant information of the notification message passed by NotificationListener to PeopleSpaceWidgetManager includes status information of whether it is a session type notification.

For example, a binary number "1" may be used to indicate that the notification message is a session type notification, and "0" indicates that the notification message is not a session type notification. PeopleSpaceWidgetManager parses the status information to determine whether the updated notification message is a session type notification. If it is determined that the updated notification message is a session type notification, continue to determine other information items to determine whether the interface of the desktop card needs to be updated.

S350: The conversation card manager determines whether the contact of the updated notification message has added a conversation card; if so, execute S360; if not, end the current process.

If it is determined that the updated notification is a conversation type notification, PeopleSpaceWidgetManager continues to determine whether a corresponding conversation card has been added to the contact of the notification by calling the updateWidgetsWithNotificationChanged method. If a conversation card has been added to the contact, it is determined that the interface of the conversation card needs to be updated. .

As mentioned before, the electronic device maintains a mapping relationship between the conversation card on the desktop and the associated contact, that is, the mapping relationship between the card ID and the key of the contact.

PeopleSpaceWidgetManager can find whether the mapping relationship table contains the mapping data of the notification contact's Key. If it does, it indicates that a conversation card has been added to the contact. Further queries obtain the card ID of the card associated with the notification contact.

If the mapping relationship table does not contain the key of the contact, it means that the conversation card is not added to the contact.

S360: The session card manager obtains the third target view interface of the third target card based on the updated notification message information.

Wherein, the third target card is a card associated with the contact of the updated notification message (ie, the third target contact).

After PeopleSpaceWidgetManager determines that the contact of the updated notification message has a corresponding conversation card, it calls the updateAppWidgetViews method. The updateAppWidgetViews method assembles the view interface of the first target card based on the information corresponding to the third target contact (such as avatar, name, conversation content). That is, the third target view interface.

In the scenario of receiving a new notification message, update the information that needs to be updated in the new notification message to the interface of the target card, for example, update the session content displayed on the third target card to the latest session content.

In the scenario where the notification message is removed, the conversation content displayed on the target card is deleted.

In addition, whether a new notification message is received or a notification message is removed, if the avatar and/or name of the notification contact delivered by the notification are updated, the avatar and name of the contact displayed on the target card will be updated to the latest avatar. ,name.

S370: The session card manager passes the card ID of the third target card and the third target view interface to the desktop card manager.

PeopleSpaceWidgetManager calls the updateAppWidget method of AppWidgetManager to update the third target view interface to the third target card.

S380, the desktop card manager updates the third target card interface to the third target view interface.

AppWidgetManager determines the card whose interface is to be updated based on the received card ID, and further updates the card's interface to the received third target view interface, thereby completing the card interface update.

In addition, in some embodiments, the message displayed by the card may be updated following the update of the notification message in the notification center, and the status of the notification message in the notification center may not change due to the update of the card message.

For example, if the notification center receives a new message notification from contact A, and card A associated with contact A is added to the desktop, in this case, the message on card A is updated to the latest message from contact A. At the same time, the notification center's method of notifying users of new messages received from Contact A can remain unchanged. For example, the new message notification of Contact A can be displayed in the notification bar, and the screen can also be automatically turned on when the screen is turned off when receiving notifications. Show to show a preview of the new notification's content.

Of course, in other embodiments, the status of the notification message in the notification center can also change with the update of the card message. For example, after the message in the card is updated to the latest message in the notification center, the corresponding message notification in the notification center can be deleted. Prevent users from repeating operations on the same message.

For another example, if the notification center has received a new message notification from contact A, and then the user adds card A associated with contact A on the desktop, that is, before adding contact A's card, there is Messages from contact A. In this case, after adding contact A to card A, card A not only displays contact A’s information (such as avatar, name, etc.), but also displays new messages from contact A. . Moreover, the update of card A will not affect the status of contact A's new messages in the notification center. That is, after card A displays the contact's new message, the message for contact A in the notification center does not need to be deleted.

Of course, in other embodiments, the contact's message notification in the notification center can also be deleted to avoid repeated operations by the user.

For another example, after the user deletes an unread message in the notification center, and a card of the contact corresponding to the message is added to the desktop, the unread message in the card will be deleted simultaneously. However, if the user deletes an unread message on the card, the corresponding unread message in the notification center does not need to be deleted.

Of course, in other embodiments, the corresponding unread message in the notification center can also be deleted, thereby preventing the user from repeating operations on the same unread message.

NotificationListener can only listen to notification messages (i.e., messages in the notification center) and cannot monitor changes in the session, such as messages directly replied by the user in the session application (or notification center), or messages related to the contact pushed by the session APP. Information (such as friend's birthday reminder), because the sender of the push message of the conversation APP is the conversation APP system, not the contact, the conversation message cannot be obtained by monitoring the notification center. In this scenario, there is also a need to update the conversation messages replied by the user or the messages pushed by the APP to the corresponding card.

The following will introduce the process of updating card display content by directly monitoring session changes in combination with S390 ~ S3140:

S390, the session card manager (PeopleSpaceWidgetManager) registers session monitoring and monitors the session status.

Another main function of PeopleSpaceWidgetManager is to monitor the session changes of the application framework layer (FWK) in order to timely update the view interface of the session card.

In an exemplary embodiment, when adding a contact to a conversation card, PeopleSpaceWidgetManager obtains the PeopleManager service of FWK in the construction method and registers the interface of PeopleManager.ConversationListener with PeopleManager to bind the TileConversationListener interface to implement a conversation with the contact. Monitor.

S3100: After monitoring the session update, the session manager obtains the updated session information.

When PeopleManager listens to changes in the conversation, it obtains updated conversation information, such as the conversation's contact information (such as contact key), conversation content, etc.

S3110: The session manager transmits updated session information to the session card manager.

When listening to Conversation changes, PeopleManager calls back the onConversationUpdate method and passes the updated session information to PeopleSpaceWidgetManager through the TileConversationListener interface.

S3120: The conversation card manager obtains the target view interface (ie, the fourth target view interface) of the fourth target card corresponding to the fourth target contact according to the updated conversation information.

According to the contact key corresponding to the updated session, PeopleSpaceWidgetManager queries the mapping relationship table between contacts and session cards to obtain the card ID of the session card (ie, the fourth target card) associated with the contact key.

Further, PeopleSpaceWidgetManager calls the updateAppWidgetViews method to assemble the view interface corresponding to the fourth target card, that is, the fourth target view interface, based on the updated session information.

S3130: The session card manager passes the card ID of the fourth target card and the fourth target view interface to the desktop card manager.

S3140, the desktop card manager updates the view interface of the fourth target card to the fourth target view interface.

In an exemplary embodiment, PeopleSpaceWidgetManager determines the fourth target card that needs to be updated based on the card ID, and further calls the updateAppWidget method of AppWidgetManager to update the view interface of the fourth target card to the fourth target view interface.

For example, the user directly replies to the contact's conversation message in the "Reply" control provided in the notification bar. In this scenario, the conversation message replied by the user is updated to the conversation card corresponding to the contact through the above steps S390 to S3140.

For another example, a conversational APP pushes reminder information about a friend to the user, such as a friend's birthday. In this scenario, this solution can be used to update the reminder information to the conversation card corresponding to the friend.

The card message update process provided in this embodiment further updates the information displayed on the target session card based on the information corresponding to the changed session notification message by monitoring the notification message. And, by monitoring the session messages, the information displayed on the target session card is further updated according to the information of the changed session messages.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

In the several embodiments provided in this embodiment, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be The combination can either be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of this embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment. The aforementioned storage media include: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (19)

1. A card display method, characterized by being applied to an electronic device, the electronic device including a conversation-like application, the method comprising:

displaying a third desktop, wherein the third desktop comprises a blank card of a session type;

responding to the editing operation of the blank card, displaying a latest message viewing interface, wherein the latest message viewing interface comprises a latest contact person viewing inlet;

after detecting that a user clicks the operation of checking the recent contact entry, acquiring a recent session notification from a notification manager, sorting the recent session notification according to the time stamp of the recent session notification from early to late to acquire a recent contact list, and displaying a second interface containing the recent contact list, wherein the recent session notification is a notification message of at least two session applications received by the notification manager in a first time period from the expiration to the current time;

responding to the operation of selecting a first contact person in the recent contact person list by a user, updating the blank card into a first card, wherein the first card comprises the name of the first contact person;

displaying a first desktop, the first desktop including a first card;

Receiving a first session message sent by the first contact;

displaying the first session message in the first card in response to the first session message;

receiving a first operation input by a user on the first card;

and in response to the first operation, jumping from the first desktop to a dialogue interface with the first contact in a first dialogue application, wherein the dialogue interface comprises the first dialogue message.

2. The method of claim 1, wherein the displaying the first session message in the first card in response to the first session message comprises:

in response to the first session message, the first card is updated from including the name of the first contact to including the first session message and the name of the first contact.

3. The method according to claim 2, wherein the method further comprises:

receiving a second session message sent by the first contact;

in response to the second session message, the first session message in the first card is updated to the second session message.

4. A method according to any one of claims 1-3, wherein the method further comprises:

Receiving a third session message sent to the first contact;

and in response to the third session message, displaying the third session message in the first card.

5. A method according to any of claims 1-3, wherein said displaying a first session message in said first card in response to said first session message comprises:

after the monitoring notification center receives a new notification message, acquiring information of the new notification message, wherein the information of the new notification message comprises message content, contact person information and state information, and the state information characterizes whether the notification message is a session type message or not;

based on the state information and the contact person information corresponding to the new notification message, after determining that the message content of the new notification message is the first session message, inquiring a first mapping relation to obtain a target card identifier associated with the global unique identifier of the first contact person;

displaying the first session message in the card corresponding to the target card identifier;

the first mapping relation comprises a corresponding relation between a card identifier of a card and a global unique identifier of a contact corresponding to the card, wherein the global unique identifier is used for uniquely marking the contact of the session application, and the card identifier is used for uniquely marking the card on the first desktop.

6. The method according to claim 1, wherein the method further comprises:

after the notification message of the notification center is removed, acquiring information of the removed notification message, wherein the information of the notification message comprises contact information and state information, and the state information characterizes whether the notification message is a session type message or not;

and deleting the message content displayed in the first card after determining that the message content of the removed notification message is the first session message based on the state information and the contact information corresponding to the removed notification message.

7. The method of claim 4, wherein the receiving a third session message sent to the first contact, in response to the third session message, displaying the third session message in the first card comprises:

after monitoring the updating of the session message, acquiring updated information of the session message, wherein the information of the session message comprises contact information and session message content of the session message;

and after the session message update between the first contact person and the contact person is determined based on the contact person information, displaying the updated session message in the first card.

8. The method according to any one of claims 1-4, further comprising:

receiving a second operation of a user on a second desktop;

responding to the second operation, displaying a first interface, wherein the first interface displays a function type corresponding to the card, and the function type comprises the session type;

and displaying a third desktop in response to the user selecting the session type.

9. The method of claim 8, wherein the updating the blank card to the first card in response to a user selecting a first contact in the recent contact list comprises:

if a session message sent by the first contact exists in the notification center, the first card comprises the name of the first contact and the session message;

if there is no conversation message sent by the first contact in the notification center, the first card includes a name of the first contact.

10. The method of claim 8, wherein after the operation responsive to the user selecting the first contact in the recent contact list, the method further comprises:

And adding a corresponding relation between the card identifier of the first card and the global unique identifier of the first contact in a first mapping relation, wherein the first mapping relation comprises a corresponding relation between the card identifier of the card and the global unique identifier of the contact corresponding to the card.

11. The method of claim 8, wherein the method further comprises:

responding to the editing operation of the user on the first card, and displaying the second interface;

and responding to the operation of selecting a second contact person from the recent contact person list by a user, and updating the contact person displayed by the first card into the second contact person by the first contact person.

12. The method of claim 11, wherein after the contact displayed by the first card is updated by the first contact to the second contact, the method further comprises:

and updating the mapping relation data between the first card and the first contact in the first mapping relation to the mapping relation data between the first card and the second contact.

13. The method of claim 1, wherein after displaying the first desktop, the method further comprises:

And deleting the first card from the first desktop in response to a user deleting operation of the first card.

14. The method of claim 1, wherein the first desktop includes at least two cards displayed in a stacked manner.

15. The method of claim 1, wherein the first card further comprises a first control; the method further comprises the steps of:

responding to the operation of the user input to the first control, and displaying an information input box and a sending control by the first card;

responding to clicking operation of a user on the information input box, and displaying an interface of content input by the first card;

and responding to clicking operation of the sending control, and displaying a session message sent to the first contact by the first card.

16. The method of claim 1 or 15, wherein the first card further comprises a second control; the method further comprises the steps of:

receiving the operation of the user input to the second control, wherein the second control is a mark read control or a delete control;

and deleting the session message displayed in the first card in response to the operation input to the second control.

17. The method of claim 1, wherein the message content displayed by the card comprises at least one of text, pictures, audio, and video.

18. An electronic device, the electronic device comprising: one or more processors, memory, and a touch screen; the memory is used for storing program codes; the processor is configured to execute the program code to cause the electronic device to implement the card display method of any one of claims 1 to 17.

19. A computer readable storage medium having instructions stored thereon which, when executed on an electronic device, cause the electronic device to perform the card display method of any one of claims 1 to 17.