CN114138140B

CN114138140B - Information management method, electronic device, and storage medium

Info

Publication number: CN114138140B
Application number: CN202111252115.6A
Authority: CN
Inventors: 胡少哲
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-10-25
Filing date: 2021-10-25
Publication date: 2022-10-04
Anticipated expiration: 2041-10-25
Also published as: CN114138140A

Abstract

The embodiment of the application discloses an information management method, electronic equipment and a storage medium, and relates to the technical field of intelligent terminals. The information management method of an embodiment of the application includes: upon receiving a message, a banner notification of the message is displayed. And responding to a first operation of the user on the banner notice, and displaying a bubble notice window which is used for displaying a chat interface of the user and the contact. Wherein the contact includes an important contact or a common contact. User icons for a plurality of contacts are displayed in proximity to the bubble notification window, with the user icons for important ones of the plurality of contacts ranked first. And responding to a second operation of the user on the bubble notification window, and displaying a bubble floating window which is used for stacking and displaying user icons of a plurality of contacts. And in the bubble floating window, setting a user icon for displaying the important contact at the top. The embodiment of the application can optimize information management of the bubble notification.

Description

Information management method, electronic device, and storage medium

Technical Field

The embodiment of the application relates to the technical field of intelligent terminals, in particular to an information management method, electronic equipment and a storage medium.

Background

Message top-loading is generally a message sent by a contact in a single application top-loading, and when the contact message needs to be checked, the corresponding application is often required to be accessed. At present, a Bubble (Bubble) notification mode is provided on an Android system, and is used for quickly starting a conversation application, floating a message on an upper layer of other applications, and enabling a user to easily view and participate in a conversation.

The bubble notification function can uniformly display bubble notification messages of different applications, and when a user receives message notifications of a plurality of contacts applying the bubble notification function at the same time, the user needs to find the message of the concerned contact by searching. In some applications, friends of particular interest may be set as desktop shortcuts to facilitate viewing their messages, but are not convenient to manage.

Disclosure of Invention

The embodiment of the application discloses an information management method, electronic equipment and a storage medium, which are used for optimizing information management of bubble notification.

A first aspect of the present application discloses an information management method, including: upon receiving a message, a banner notification of the message is displayed. And responding to a first operation of the user on the banner notice, and displaying a bubble notice window, wherein the bubble notice window is used for displaying a chat interface of the user and the contact. Wherein the contact includes an important contact or a common contact. User icons of a plurality of contacts are displayed in the vicinity of the bubble notification window, with the user icons of important ones of the plurality of contacts ranked first. And responding to a second operation of the user on the bubble notification window, and displaying a bubble floating window which is used for stacking and displaying user icons of a plurality of contacts. And in the bubble floating window, setting a user icon for displaying the important contact at the top.

In one embodiment, the information management method further includes: thumbnail controls are set behind user icons for multiple contacts. When the thumbnail control is triggered, the user icon showing more contacts is expanded.

In another embodiment, the information management method further includes: and displaying two rows of user icons of the contacts near the bubble notification window, wherein one row is the user icon of the important contact, and the other row is the user icon of the common contact.

In another embodiment, the information management method further includes: a status icon is added near the user icon of the contact. The status icon is used to display different colors to distinguish between read messages and unread messages.

In another embodiment, the information management method further includes: a quick browse control is added in the vicinity of the thumbnail control. And after the quick browsing control is triggered, switching to display the message content of the unread message in the bubble notification window.

In another embodiment, the information management method further comprises: and displaying an information notification window in the vicinity of the bubble suspension window, wherein the information notification window is used for displaying the message content of the bubble notification. The information notification window preferentially displays bubble notifications for important contacts.

In another embodiment, a user icon for top-displaying important contacts includes: a user icon for a contact is added to the top. A balloon notification service is initiated that reads parameters of the balloon notification, wherein the parameters of the balloon notification include the user, the contact, and the pending intent. And adding parameters of the bubble notification into a top table, wherein the top table is used for storing the parameters of the bubble notification.

In another embodiment, the top-displaying user icons of important contacts further comprises: a bubble notification is obtained. Parameters of the bubble notification are matched in the top-set table to determine whether the contact of the bubble notification is an important contact.

In another embodiment, after the user icon of the important contact is displayed on top, the information management method further comprises: and canceling the user icon of the important contact. The bubble notification service is initiated. The parameters of the bubble notification are removed from the set-top table.

In another embodiment, a user icon for a top display important contact includes: a user icon for a contact is added to the top. And starting a notification management service, wherein the notification management service is used for adding a set-top field in the bubble notification, and the set-top field comprises the ispop = true or the ispop = false. A set-top field ispop = true is added in the bubble notification.

In another embodiment, the method further comprises the step of top displaying a user icon of the important contact, further comprising: a bubble notification is obtained. The top field of the bubble notification is queried to determine if the contact of the bubble notification is an important contact.

In another embodiment, after the user icon of the important contact is displayed on top, the information management method further comprises: and canceling the user icon of the important contact. A notification management service is initiated. The top field is modified in the bubble notification to be ispop = false.

The method and the device for notifying the contact persons are based on the bubble notification function, the messages sent by the contact persons applying multiple applications are managed, and the message of the contact person concerned is conveniently found by a user by using a set-top scheme, so that the user experience is improved.

A second aspect of the present application discloses an electronic device, which includes a memory, a processor, and a display screen, where the display screen is used to display a graphical user interface, the memory is used to store a computer program, and when the computer program is executed by the processor, the information management method of the embodiment of the present application is implemented.

A third aspect of the present application discloses a storage medium for storing a computer program, which, when executed by a processor, implements the information management method of the embodiments of the present application.

For technical effects brought by the second aspect to the third aspect of the present application, reference may be made to the related description of the information management method of the first aspect, and details are not repeated here.

Drawings

Fig. 1 is a schematic diagram of a hardware configuration of an electronic device according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a software structure of an electronic device according to an embodiment of the present application.

Fig. 3 is a flowchart of an information management method according to an embodiment of the present application.

Fig. 4 is an interface schematic diagram of an information management method according to an embodiment of the present application.

Fig. 5 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 6 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 7 is an interface diagram of an information management method according to another embodiment of the present application.

Fig. 8 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 9 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 10 is an interface diagram of an information management method according to another embodiment of the present application.

Fig. 11 is an interface diagram of an information management method according to another embodiment of the present application.

Fig. 12 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 13 is an interface diagram of an information management method according to another embodiment of the present application.

Fig. 14 is a flowchart of an information management method according to another embodiment of the present application.

Fig. 15 is an interface schematic diagram of an information management method according to another embodiment of the present application.

Fig. 16 is an interface diagram of an information management method according to another embodiment of the present application.

Fig. 17 is a flowchart of an information management method according to another embodiment of the present application.

Fig. 18 is a flowchart of an information management method according to another embodiment of the present application.

Fig. 19 is a flowchart of an information management method according to another embodiment of the present application.

Fig. 20 is a flowchart of an information management method according to another embodiment of the present application.

Fig. 21 is a flowchart of an information management method according to another embodiment of the present application.

Detailed Description

In the embodiments of the present application, "at least one" means one or more, "and" a plurality "means two or more. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B may represent: a alone, A and B together, and B alone, wherein A and B may be singular or plural. The terms "first," "second," "third," "fourth," and the like in the description and in the claims and drawings of the present application, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

It is further noted that the methods shown in the methods or flowcharts disclosed in the embodiments of the present application include one or more steps for implementing the methods, and the execution orders of the steps may be interchanged with each other, and some steps may be deleted without departing from the scope of the claims.

Fig. 1 is a schematic diagram of a hardware structure of an electronic device 100 according to an embodiment of the present application.

Referring to fig. 1, the electronic device 100 may include a processor 110, a memory 120, and a display 130. The display screen 130 is used for displaying a graphical user interface. The processor 110 may execute the computer program or code stored in the memory 120 to implement the information management method of the embodiment of the present application.

Processor 110 may include one or more processing units. For example, the Processor 110 may include, but is not limited to, an Application Processor (AP), a modem Processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband Processor, a Neural-Network Processing Unit (NPU), and the like. The different processing units may be separate devices or may be integrated into one or more processors.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory.

In some embodiments, processor 110 may include one or more interfaces. The Interface may include, but is not limited to, an Integrated Circuit (I2C) Interface, an Integrated Circuit built-in audio (I2S) Interface, a Pulse Code Modulation (PCM) Interface, a Universal Asynchronous Receiver/Transmitter (UART) Interface, a Mobile Industry Processor Interface (MIPI), a General-Purpose Input/Output (GPIO) Interface, a Subscriber Identity Module (SIM) Interface, a Universal Serial Bus (USB) Interface, and the like.

It should be understood that the connection relationship between the modules illustrated in the embodiment of the present application is only an exemplary illustration, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Fig. 2 is a schematic diagram of a software structure of the electronic device 100 according to an embodiment of the present application.

Referring to fig. 2, the software system of the electronic device 100 may adopt any one of the following architectures: a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android Runtime (Android Runtime) and system library, and a kernel layer from top to bottom, respectively.

The application layer may include a series of application packages. For example, the application packages may include, but are not limited to, camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc. applications.

The Application framework layer provides an Application Programming Interface (API) and a Programming framework for the Application programs of the Application layer. The application framework layer includes a number of predefined functions.

The application framework layers may include, but are not limited to, a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include, but is not limited to, video, images, audio, phone calls made and answered, browsing history and bookmarks, phone books, and the like.

The view system includes visual controls, such as controls that display text and/or pictures, etc. The view system may be used to build applications. The display interface may include one or more views. For example, the display interface including the sms notification icon may include a view displaying text and/or pictures.

The phone manager is used to provide communication functions of the electronic device 100. Such as management of call status (including on, off, etc.).

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

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. For example, a notification manager is used to inform download completion, message alerts, and the like. The notification manager may also be a notification that appears in the form of a chart or scrollbar text in a status bar at the top of the system, such as a notification of a running application in the background, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android Runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is the function that the Java language needs to call, and the other part is the kernel library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface Manager (Surface Manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

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

The media library supports playback and recording in a variety of commonly used audio/video formats, as well as still image files, and the like. The media library may support a variety of audio-video encoding formats, e.g., MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

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

The kernel layer is a layer between hardware and software. The kernel layer may include a display driver, a camera driver, an audio driver, a sensor driver, and the like.

Referring to fig. 3, the information management method may be applied to the electronic device 100. The information management method may include:

s101, after receiving a message, displaying a banner notice of the message.

Wherein the banner notification of the message comprises a bubble notification control. When the electronic device 100 receives the instant message, a banner notification of the message may be displayed on the screen. When the bubble notification control is triggered, the instant message may be displayed as a bubble.

It will be appreciated that the instant message may originate from one or more instant messaging software or applications, such as short messages, weChat, QQ, teams, federation, etc. The instant messaging software or application supports a Bubble notification function, and the instant message can be displayed as a Bubble through adapting a Bubble API.

The instant message is displayed as a bubble, and the following parameters are configured: chat objects (e.g., user and contact), message type (MessageStyle), and pending intent (Pendingintent). Where Pendingintent is used to point to a target Activity (Activity). Activity is used for displaying a user interface, and a user can complete related operations through Activity interaction. For example, activity is displayed as a bubble notification window 200. The bubble notification window 200 may fill the screen, may be smaller than the screen, or float above other windows.

S102, in response to a first operation by the user on the banner notification, a bubble notification window 200 is displayed.

Wherein, the bubble notification window 200 is used to display the chat interface between the user and the contact. When the bubble notification control is triggered, a bubble notification window 200 may pop up on the screen to display the user's chat interface with the contact.

It is understood that the first operation is to start the bubble notification function of the electronic apparatus 100. The first operation includes touching or clicking a bubble notification control.

For example, referring to FIG. 4, the electronic device 100 receives an instant message and pops up a banner notification of the message on the screen. The banner notification of the message may include the name and icon of the message source application, the name of the contact (e.g., contact a), at least a portion of the message content, and a bubble notification control (. When the bubble notification control is triggered, a bubble notification window 200 pops up on the screen. The bubble notification window 200 may include the name of the contact, the message content of the user and the contact, and a dialog box 210. The dialog box 210 is configured to receive input content of a user, and the user may click or touch an input control (#), and directly reply to a message on the dialog box 210. For example, the bubble notification window 200 may present a chat interface of the user with the contact on the WeChat application.

S103, a user icon of the important contact is preferentially displayed near the bubble notification window 200.

In some embodiments, referring again to FIG. 4, a user icon area may be provided adjacent to the bubble notification window 200 to display user icons for one or more contacts. The user icon may include a user avatar or other custom image, among other things. The user may present the user's chat interface with a contact within bubble notification window 200 by touching or clicking on the user icon for the contact.

In this embodiment, the user can set a contact as an important contact by long-pressing the user icon of the contact. Important contacts have priority over normal contacts. For example, when the user icon area displays user icons for a plurality of contacts, the user icon for the important contact among them is preferentially displayed.

In other embodiments, the user may reset an important contact to a normal contact by long-pressing the user icon for the important contact.

In one embodiment, when there are multiple important contacts, the user icons of the multiple important contacts are ordered in the time dimension. For example, the user icons of the important contacts that have recently sent the message are ordered top.

In another embodiment, a first flag may be set to distinguish important contacts from ordinary contacts. For example, the user icons of the contacts may be sorted according to their priorities and time dimensions, and then a separation line may be set between the user icons of the important contacts and the user icons of the normal contacts.

In another embodiment, a thumbnail control may be set after the user icons of multiple contacts to reduce the space occupied by the user icon area on the screen. For example, an thumbnail control may be added after the user icons of three contacts. When the thumbnail control is triggered, user icons for more contacts may be expanded.

For example, referring to FIG. 5, contacts A, B, C, D, E, and F are all important contacts, and bubble notification window 200 currently displays a chat interface with contact A. The user icon area shows the user icons of contacts A, B, C, and an abbreviated control (+). After the user clicks or touches the thumbnail control, the user icons for contacts D, E, F may be presented. The user icon area firstly shows user icons of contacts A, B, C and D. After the user slides the user icon area on the screen from right to left, the user icon area shows the user icons of contacts C, D, E, F.

In another embodiment, a first thumbnail control may be set after user icons for a plurality of important contacts. Setting a second thumbnail control after the user icons of the plurality of common contacts. Wherein, after the first thumbnail control is triggered, the user icons of more important contacts are expanded. After the second thumbnail control is triggered, the user icons of more common contacts are expanded.

In another embodiment, after sorting the user icons of the contacts by priority and time dimension of the contacts, the user may show more user icons of the contacts by sliding the screen. For example, the user icon of the top-ranked contact is preferentially shown. The user can slide and show the user icons of the contacts which are sequenced at the back and hidden outside the user icon area by sliding the user icon area on the screen.

For example, referring to FIG. 6, contacts A, B, and C are all important contacts, contacts D, E, and F are all normal contacts, and bubble notification window 200 displays a chat interface with contact A. The user icon area first shows the user icons of contacts a, B, C. After the user slides the user icon area on the screen from right to left, the user icon area shows the user icons of contacts D, E, F.

In another embodiment, two rows of user icons may be displayed within the user icon area, one row being user icons for important contacts and the other row being user icons for normal contacts. Wherein a first marker, such as adding an aperture or VIP sign, may be added near the user icon of the important contact.

For example, referring to fig. 7, contacts a, B, and C are all important contacts, contacts D, E, and F are all normal contacts, and the bubble notification window 200 displays a chat interface with contact a. The user icon area shows two rows of user icons. The first row shows user icons of contacts a, B, C, a first thumbnail control (+), and a separation line (|). The second row shows the user icons for contacts D, E, F, and a second thumbnail control (+).

In another embodiment, a second flag may be set to distinguish between read messages and unread messages. For example, a status icon may be added near the user icon of the contact. The status icon may appear red when there is an unread message between the contact and the user. The status icon may be displayed green when there are no unread messages between the contact and the user. It will be appreciated that the status icon may be displayed in other different colors when distinguishing between read and unread messages.

In another embodiment, the number of unread messages may be displayed near the user icon of the contact.

For example, referring to FIG. 8, contacts A, B, and C are all important contacts, and bubble notification window 200 displays a chat interface with contact A. The number of unread messages displayed near the user icon of contact B is 5. The number of unread messages is 15 displayed near the user icon of contact C.

In another embodiment, a quick-view control may be provided in proximity to the thumbnail control to toggle the message content of the unread message within the bubble notification window 200. After the quick browsing control is triggered, the bubble notification window 200 switches to display the message content of the unread message, and the user does not need to slide the screen to find the contact with the unread message, so that the time for the user to browse the unread message is reduced, and the user experience is improved.

In some embodiments, after sorting the user icons of the contacts by their priority and time dimensions, the bubble notification window 200 may switch the message content exhibiting the unread messages in order of the user icons.

For example, referring to fig. 9, contacts a, B, and C are all important contacts, and contact J is a normal contact. Wherein unread messages exist between contacts B, J and the user. Bubble notification window 200 displays a chat interface with contact a. The user icon area shows the user icons of contacts A, B, C, the thumbnail control (+), the quick browse control (\8230;), and the isolation line (|). After the user first clicks or touches the quick browse control, bubble notification window 200 toggles from displaying the chat interface with contact a to revealing the chat interface with contact B. After the user clicks or touches the quick browse control a second time, bubble notification window 200 toggles to reveal the chat interface with contact J.

S104, in response to the second operation of the user on the bubble notification window 200, the bubble levitation window 300 is displayed.

It will be appreciated that the second operation is to initiate the bubble suspension function. The second operation includes touching or clicking a bubble hover control on the bubble notification window 200.

The bubble levitation window 300 can include a user icon, an application icon, and a status icon. The application icon and the status icon may be disposed in proximity to the user icon. The application icon is used to show the source application of the bubble notification. The status icon is used to distinguish between read messages and unread messages.

In some embodiments, after bubble notification window 200 displays the user's chat interface with the contact, the user may touch or click on the bubble hover control on bubble notification window 200, such that bubble notification window 200 and the user icon area are hidden and bubble hover window 300 is displayed on the screen.

In other embodiments, after bubble notification window 200 displays the user's chat interface with the contact, the user may touch or click on the bubble hover control on bubble notification window 200, such that bubble notification window 200 is hidden and the user icon area shrinks to form bubble hover window 300.

In one embodiment, and referring to FIG. 10, bubble notification window 200 includes a bubble hover control (^) that the bubble notification window 200 and the user icon area hide after the user touches or clicks on the bubble hover control. If the user does not receive a new message, a bubble levitation window 300 is displayed on the screen. Wherein the bubble floating window 300 shows the user icon of the contact who recently sent the message.

In another embodiment, referring to fig. 11, after the bubble notification window 200 and the user icon area are hidden, if the user receives a new message, the bubble levitation window 300 and the information notification window 400 are displayed on the screen. Here, the information notifying window 400 is displayed in the vicinity of the bubble floating window 300. The information notification window 400 is used to present the message content of the new message. The user icon for the new message contact is displayed in bubble hover window 300.

S105, in the bubble floating window 300, a user icon of the important contact is displayed at the top.

In some embodiments, referring to fig. 12, a stack of user icons for multiple contacts is shown in bubble hover window 300. Wherein, the user icon of the important contact is displayed at the top.

In one embodiment, when a plurality of important contacts are arranged, the user icons of the important contacts are sorted according to the time dimension, and the user icon of the important contact which is sorted in the front is displayed at the top. For example, when the user does not receive a new message, the user icon for the important contact that has recently sent the message is displayed on top.

In another embodiment, when the user receives a new message, the user icon for the new message contact is displayed on top in bubble hover window 300.

For example, referring to FIG. 13, when a user receives a new message from a common contact (assume A), the user icon of the common contact is displayed on top of the bubble-floating window 300 and the message content of the new message is displayed in the information-notification window 400. After a preset time (e.g., 3 s) has elapsed, the infomercial window 400 is hidden and the bubble-suspended window 300 is replaced with the user icon showing the important contact (e.g., B).

In another embodiment, when the user receives new messages sent by multiple contacts at the same time, the user icon of the important contact is displayed on top of the bubble floating window 300, and the new message of the important contact is preferentially displayed in the information notification window 400.

In the embodiment, the contact of the bubble notification is distinguished as an important contact or a normal contact, and the priority of the important contact is higher than that of the normal contact. In the vicinity of the bubble notification window 200, the user icons of the important contacts are preferentially displayed. In bubble hover window 300, a user icon showing important contacts is placed on top. In this way, the user can view the messages of the concerned contact in time.

Referring to fig. 14, the step S105 of displaying the user icon of the important contact at the top may include:

s201, responding to the third operation, and adding the user icon of the important contact to the top.

Wherein the third operation may comprise a long-press of a bubble notification, or a long-press of a user icon of a contact.

For example, referring again to fig. 13, when the user receives a new message, the bubble suspension window 300 and the information notification window 400 are displayed on the screen. Therein, the information notification window 400 shows a bubble notification, which includes the message content of the new message. The user icon of the new message contact is displayed at the top of the bubble floating window 300, and the user icons of other contacts are sequentially stacked below the user icon of the new message contact.

In one embodiment, referring to FIG. 15, the user may set the new message contact as an important contact by long-pressing the bubble notification of the new message to top the user icon for the important contact in the bubble-flyover window 300.

In another embodiment, referring to FIG. 16, the user may set the new messaging contact as an important contact by long-pressing the user icon of the new messaging contact to top the user icon of the important contact in the bubble hover window 300.

S202, a bubble notification service (notifiationbubberservice) is started.

The bubble notification service is used for reading parameters of the bubble notification. Parameters of the bubble notification may include a User (User) and a contact (People), and a pending intention (pending intention).

In some embodiments, the bubble notification service may write parameters of the bubble notification into a Top-List (Top-List).

S203, creating a Top List (Top-List), and adding the parameters of the bubble notification in the Top List.

The set-top table is used for storing parameters of the bubble notification. The set top table stores at least the following parameters: contacts (peoples) and pending intentions (Pendingintent).

In some embodiments, when the user receives a new message, the bubble notification window 200 refreshes, and the bubble notification service reads the parameters of the bubble notification in the set top table to determine if the new message contact is an important contact. It will be appreciated that the contacts (peoples) stored in the set-top table are all important contacts.

In one embodiment, when the new message contact is an important contact, the information notification window 400 preferentially displays the bubble notification of the new message, and the bubble floating window 300 is set to display the user icon of the new message contact.

In another embodiment, when the new message contact is a regular contact, the information notification window 400 presents bubble notifications of the new message in chronological order of the unread message. For example, the information notification window 400 preferentially presents the oldest received unread message. The bubble floating window 300 displays the user icon of the new messaging contact on top for a preset time. After a preset time, the bubble levitation window 300 is reset to display the user icons of the important contacts.

S204, saving the bubble notification.

In some embodiments, the bubble notification may be saved by SharedPreferences (hereinafter SP) storage. The SP stores in a Map (Map) mode, submits and stores data by using Key-Value pairs (Key-Value), and the stored data is stored in a local folder in an xml format, so that lightweight data can be stored conveniently.

For example, the SP may construct the parameters of the bubble notification as a key-value pair, such as { People: pending }. The Peer and the Pendingintent form a mapping relation, and the Pendingintent can be accessed by inquiring the Peer.

S205, the electronic device 100 or the System interface (System UI) is restarted.

In some embodiments, it may be checked whether the bubble notification has been saved by restarting the electronic device 100 or a System interface (System UI).

S206, inquiring whether to store the bubble notification. If the bubble notification is stored, the process ends. If the bubble notification is not stored, step S203 is executed.

In some embodiments, after restarting the electronic device 100 or System interface (System UI), the bubble notification service may query whether there is a previously saved bubble notification in the SP. If the bubble notification stored previously exists in the SP, the bubble notification is successfully stored. If there is no previously saved bubble notification in the SP, the failure of saving the bubble notification is explained. When it is determined that the bubble notification storage fails, the bubble notification service rewrites the parameters of the bubble notification in a Top-set table (Top-List).

In this embodiment, through a notification service (notificationbubbeleservice), the bubble suspension window 300 is set to display a user icon of an important contact.

Referring to fig. 17, in step S105, the step of displaying the user icon of the important contact at the top may include:

s301, responding to the third operation, adding the user icon of the important contact to the top.

In some embodiments, referring again to fig. 15 and 16, the user may set the new message contact as an important contact by long pressing the bubble notification of the new message, or the user icon of the new message contact, to top up the user icon of the important contact in the bubble flyover window 300.

S302, a notification management service (notificationanagervice) is started.

Wherein the notification management service is configured to add a set-top field in the bubble notification. The set-top field may include ispop = true, or ispop = false. The isTop = true indicates that the bubble notifies the user icon of the corresponding contact that the top has been added. ispop = false indicates that the bubble notifies the user icon of the corresponding contact that no top is added.

S303, add a set-top field to the bubble notification.

In some embodiments, the bubble notification is stored in notification _ policy. The notification management service may query the bubble notification in notification _ policy.xml to add a set-top field ispop = true in the bubble notification.

In the present embodiment, the bubble levitation window 300 displays a user icon of an important contact on top through a notification management service (NotificationManagerService).

Referring to fig. 18, after the step S105 of displaying the user icon of the important contact at the top, the method may include:

s401, responding to the fourth operation, and enabling the user icon of the important contact person to be set to the top in a cancelling mode.

Wherein the fourth operation may comprise long-pressing a bubble notification of the set top, or long-pressing a user icon of an important contact.

In some embodiments, the user may set the important contact as a normal contact by long pressing the bubble notification that has been set to the top, or by long pressing the user icon of the important contact, to set the user icon of the contact to the top in the bubble hover window 300.

S402, starting a bubble notification service (notifiationbubbleservice).

In some embodiments, the bubble notification service may remove parameters of the bubble notification in a Top-List (Top-List).

S403, removing the parameters of the bubble notification in a set-Top List (Top-List).

In some embodiments, when the user receives a new message, the bubble notification window 200 refreshes, and the bubble notification service reads the parameters of the bubble notification in the set-top table. And when the bubble notification service inquires that the new message contact exists in the set-top table, removing the parameter of the bubble notification corresponding to the new message contact.

In this embodiment, the user icon of the important contact displayed at the top in the bubble suspension window 300 is cancelled through a notification service (notificationbubbeleservice).

Referring to fig. 19, after the step S105 of displaying the user icon of the important contact at the top, the method may include:

s501, responding to the fourth operation, and enabling the user icon of the important contact person to be set to the top in a cancellation mode.

Wherein the fourth operation may comprise long-pressing a bubble notification that has been set top, or long-pressing a user icon of an important contact.

In some embodiments, the user may set the important contact to a normal contact by long-pressing the bubble notification that has been set to the top, or long-pressing the user icon of the important contact, to set the user icon of the contact to the top in the bubble hover window 300.

S502, a notification management service (notificationanagervice) is started.

Wherein the notification management service is configured to add a set-top field in the bubble notification. The set-top field may include ispop = true, or ispop = false. The istap = true indicates that the bubble notifies the user icon of the corresponding contact that the vertex has been added. ispop = false indicates that the bubble notifies the user icon of the corresponding contact that is not topped.

S503, modifying the top field in the bubble notification.

In some embodiments, the bubble notification is stored in notification _ policy. The notification management service may query the bubble notification in notification _ policy.xml to modify the set-top field to ispop = false in the bubble notification.

In the present embodiment, the user icon of the important contact displayed at the top in the bubble floating window 300 is cancelled by a notification management service (notificationanagervice).

Referring to fig. 20, the information management method may include:

s601, acquiring the bubble notification.

Referring again to fig. 13, when the user receives a new message, a bubble levitation window 300 and an information notification window 400 are displayed on the screen. Therein, the information notification window 400 shows a bubble notification, which includes the message content of the new message. The bubble floats in window 300 and the user icon for the new messaging contact is displayed at the top.

S602, a notification bubble service (notifiationbubbleservice) is started.

S603, the parameter of the bubble notification in the Top-up table (Top-List) is queried.

In some embodiments, when the user receives a new message, the bubble notification window 200 refreshes, and the bubble notification service reads the parameters of the bubble notification in the set top table to determine if the new message contact is an important contact.

And S604, determining whether the contact notified by the bubble is an important contact. If the contact notified by the bubble is an important contact, step S605 is executed. If the contact notified by the bubble is a normal contact, step S607 is executed.

It will be appreciated that the contacts (peoples) stored in the set-top table are all important contacts.

In some embodiments, the bubble notification service may traverse the contacts of the bubble notification in a set-top table. If the contact person of the bubble notification exists in the top-set table, the contact person of the bubble notification is an important contact person. If the contact person of the bubble notification does not exist in the top setting table, the contact person of the bubble notification is a common contact person.

S605 sets a user icon of the contact notified by the bubble on top of the bubble floating window 300.

In one embodiment, when the contact of the bubble notification is an important contact, the bubble-floating window 300 is positioned to display the user icon of the contact of the bubble notification.

S606, the bubble notification is displayed in the information notification window 400.

In one embodiment, the information notification window 400 preferentially presents the bubble notification for the new message when the contact of the bubble notification is an important contact.

S607, the user icon of the contact notified by the bubble is displayed in the bubble floating window 300 at the top within the preset time.

In one embodiment, when the contact of the bubble notification is a normal contact, the bubble floating window 30 displays the user icon of the contact of the bubble notification within a preset time (e.g., 3 s). After a preset time, the bubble levitation window 300 is reset to display the user icons of the important contacts.

S608, in the information notification window 400, the bubble notification is displayed within a preset time.

In one embodiment, the information notification window 400 presents the bubble notifications in chronological order of the unread messages when the contacts of the bubble notifications are normal contacts. For example, the information notification window 400 preferentially presents a bubble notification of the earliest received unread message.

In another embodiment, the information notification window 400 presents the bubble notification of the new message for a preset time (e.g., 3 s) when the contact of the bubble notification is a normal contact. After a preset time, the information notification window 400 re-presents the bubble notification of the oldest received unread message.

In the present embodiment, the bubble notification of the new message is matched in the Top-List (Top-List) by the bubble notification service (notificationbubbeleservice) to determine whether the contact of the bubble notification is an important contact.

Referring to fig. 21, the information management method may include:

s701, acquiring a bubble notification.

S702, a notification management service (notificationanagervice) is started.

Wherein, the notification management service is used for adding a set-top field in the bubble notification. The set-top field may include ispop = true, or ispop = false. The istap = true indicates that the bubble notifies the user icon of the corresponding contact that the vertex has been added. ispop = false indicates that the bubble notifies the user icon of the corresponding contact that no top is added.

S703, inquiring the top field of the bubble notification.

In some embodiments, the bubble notification is stored in notification _ policy. The notification management service can query the set-top field of the bubble notification in notification _ policy.

S704, whether the contact of the bubble notification is an important contact is determined. If the contact notified by the bubble is an important contact, step S705 is executed. If the contact notified by the bubble is a normal contact, step S707 is executed.

It is understood that the top field of the bubble notification, ispop = true, indicates that the contact of the bubble notification is an important contact. The top field of the bubble notification, ispop = false, indicates that the contact of the bubble notification is a normal contact.

S705, the user icon of the contact notified by the bubble is set on top of the bubble suspension window 300.

In one embodiment, the bubble-floating window 300 is positioned to display the user icon of the contact of the bubble notification when the contact of the bubble notification is an important contact.

S706, in the information notification window 400, a bubble notification is displayed.

In one embodiment, the information notification window 400 preferentially presents the bubble notification for new messages when the contact of the bubble notification is an important contact.

S707, in the bubble floating window 300, the user icon of the contact notified by the bubble is displayed at the top within the preset time.

In one embodiment, when the contact of the bubble notification is a normal contact, the bubble floating window 300 displays the user icon of the contact of the bubble notification at the top within a preset time (e.g., 3 s). After a preset time, the bubble levitation window 300 is reset to display the user icons of the important contacts.

S708, in the information notification window 400, a bubble notification is displayed within a preset time.

In one embodiment, when the contact of the bubble notification is a regular contact, the information notification window 400 presents the bubble notification in chronological order of the unread messages. For example, the information notification window 400 preferentially presents a bubble notification of the earliest received unread message.

In the present embodiment, the top field of the bubble notification is queried by a notification management service (notificationanagervice) to determine whether the contact of the bubble notification is an important contact.

The embodiment of the present application further provides a storage medium for storing a computer program or code, and when the computer program or code is executed by the processor 110, the information management method of the embodiment of the present application is implemented.

Storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Storage media include, but are not limited to, random Access Memory (RAM), read-Only Memory (ROM), electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Memory, compact Disc Read-Only Memory (CD-ROM), digital Versatile Disc (DVD) or other optical Disc storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

The embodiments of the present application have been described in detail with reference to the drawings, but the present application is not limited to the embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present application.

Claims

1. An information management method, characterized in that the method comprises:

after receiving a message, displaying a banner notification of the message;

responding to a first operation of a user on the banner notification, and displaying a bubble notification window which is used for displaying a chat interface of the user and a contact person; wherein the contact comprises an important contact or a common contact;

displaying user icons of a plurality of the contacts in the vicinity of the bubble notification window, wherein the user icons of important contacts in the plurality of the contacts are ranked in the top;

in response to a second operation of the user on the bubble notification window, displaying a bubble floating window, wherein the bubble floating window is used for stacking and displaying user icons of a plurality of contacts;

and in the bubble suspension window, a user icon of the important contact is displayed at the top.

2. The information management method according to claim 1, wherein the method further comprises:

setting a thumbnail control after user icons of a plurality of the contacts;

and after the thumbnail control is triggered, expanding user icons for displaying more contacts.

3. The information management method according to claim 1 or 2, wherein the method further comprises:

and displaying two rows of user icons of the contact persons near the bubble notification window, wherein one row is the user icon of the important contact person, and the other row is the user icon of the common contact person.

4. The information management method according to any one of claims 1 to 3, characterized in that the method further comprises:

adding a status icon near the user icon of the contact;

the status icons are used to display different colors to distinguish between read messages and unread messages.

5. The information management method according to claim 2, wherein the method further comprises:

adding a quick browsing control near the thumbnail control;

and after the quick browsing control is triggered, switching to display the message content of the unread message in the bubble notification window.

6. The information management method according to any one of claims 1 to 5, wherein the method further comprises:

displaying an information notification window near the bubble suspension window, wherein the information notification window is used for displaying message content of bubble notification;

and the information notification window preferentially displays bubble notifications of the important contacts.

7. The information management method of any one of claims 1 to 6, wherein the top-displaying the user icon of the important contact comprises:

adding a user icon of one contact to a top;

starting a bubble notification service, wherein the bubble notification service is used for reading parameters of a bubble notification, and the parameters of the bubble notification comprise a user, a contact and a pending intention;

and adding the parameters of the bubble notification into a top-set table, wherein the top-set table is used for storing the parameters of the bubble notification.

8. The information management method of claim 7, wherein the top-displaying the user icon of the important contact further comprises:

acquiring a bubble notification;

matching parameters of the bubble notification in the set top table to determine whether the contact of the bubble notification is the important contact.

9. The information management method of claim 7 or 8, wherein after the top-up displaying the user icon of the important contact, the method further comprises:

canceling the user icon of the important contact;

starting the bubble notification service;

removing parameters of the bubble notification from the set-top table.

10. The information management method of any of claims 1 to 6, wherein the top-displaying user icons of the important contacts comprises:

adding a user icon of one contact to a top;

starting a notification management service, wherein the notification management service is used for adding a set-top field in the bubble notification, and the set-top field comprises ispop = true or ispop = false;

adding the set-top field ispop = true in the bubble notification.

11. The information management method of claim 10, wherein the top-displaying the user icon of the important contact further comprises:

acquiring a bubble notification;

and querying a top field of the bubble notification to determine whether the contact of the bubble notification is the important contact.

12. The information management method of claim 10 or 11, wherein after the top-displaying the user icon of the important contact, the method further comprises:

canceling the user icon of the important contact;

starting the notification management service;

modifying the set-top field in the bubble notification to isptop = false.

13. An electronic device comprising a memory, a processor and a display screen, the display screen being adapted to display a graphical user interface, the memory being adapted to store a computer program, wherein the computer program, when executed by the processor, implements the information management method of any one of claims 1 to 12.

14. A storage medium storing a computer program for implementing an information management method according to any one of claims 1 to 12 when the computer program is executed by a processor.