Information pushing method and wearable device

Abstract

Embodiments of the present application relate to the technical field of terminals, and provide an information pushing method and a wearable device. The problem of information pushing of wearable devices is solved. The specific scheme is: displaying a first interface, the first interface being a user interface of a wearable device; displaying a first capsule, the first capsule being used for pushing first information; and, in response to a first operation by a user, switching from the first interface to display a second interface, and continuing to display the first capsule.

Description

Information push method and wearable device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 3, 2023, with application number 202311461360.7 and invention name “A method for pushing information and a wearable device”, and the Chinese patent application filed with the State Intellectual Property Office on December 26, 2023, with application number 202311820559.4 and invention name “A method for pushing information and a wearable device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the technical field of terminal devices, and in particular to an information push method and a wearable device. Background Art

[0003] With the rapid development of smart terminal technology, the variety of applications (APPs) and services is increasing, and correspondingly, the amount of information that needs to be pushed to users is also increasing. Currently, if users want to view pushed information through wearable devices, they need to instruct the wearable devices to switch to a specific user interface. For users who are not familiar with wearable devices, the human-computer interaction efficiency of viewing pushed information is low.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide an information push method and a wearable device, which are used to improve the human-computer interaction efficiency of a user viewing pushed information on a wearable device.

[0006] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0007] In a first aspect, an information push method provided by an embodiment of the present application is applied to a wearable device, the method comprising: displaying a first interface, which is a user interface of the wearable device; displaying a first capsule, which is used to push first information; and in response to a first operation of the user, switching from the first interface to display a second interface, continuing to display the first capsule, which is another user interface of the wearable device.

[0008] For example, the first and second interfaces may be two different user interfaces provided by the wearable device, and the first operation may be an operation indicating a switch between the different user interfaces. For example, when the first interface is an AOD interface and the second interface is a watch face interface, the first operation may be an operation of lighting up the display screen of the wearable device. For another example, when the first interface is a watch face interface and the second interface is a smart interface, the first operation may be a left swipe or a right swipe operation.

[0009] In the above embodiment, after the first capsule is displayed on the first interface, the other user interfaces are switched. The first capsule can continue to be displayed in the other user interfaces. In other words, the first capsule can be displayed globally, and when the user needs to view the first information, there is no need to return to the first interface, thereby improving the human-computer interaction efficiency of the user viewing the first information.

[0010] In some embodiments, when the first information is information of the first type, after the wearable device displays the first capsule for a first duration, the first capsule continues to be displayed; and in response to a user operation on the first capsule, the first capsule is canceled.

[0011] In the above embodiment, the first capsule can persist for a long time when no user operation is received, so that the user can check the first information pushed by the first capsule at any time. Of course, the user can also indicate to cancel the first capsule to avoid the first capsule from interfering with the user.

[0012] In some embodiments, when the first information is of a second type, the method further includes: after the wearable device displays the first capsule for a first duration, canceling the display of the first capsule, wherein the first type of information is different from the second type of information.

[0013] In the above embodiment, the first capsule that pushes the first type of information is displayed for an unlimited time unless a user action is taken. The first capsule that pushes the second type of information is displayed for a limited time unless a user action is taken. This prevents all types of pushed information from being pushed for an extended period of time, which could cause excessive disruption to the user.

[0014] In some embodiments, the push confidence of various types of information can be pre-evaluated. The push confidence is used to represent the probability that the pushed information is information that the user actually needs to view. The first type of information includes information with a push confidence greater than or equal to a preset value, which is information with deterministic intent. The second type of information includes information with a push confidence less than the preset value, which is information with non-deterministic intent.

[0015] In the above embodiment, whether the display of the corresponding first capsule is subject to a time limit is determined according to the push confidence of the pushed information, so that the push is more intelligent and accurate, and the interference of the pushed information on the user is reduced.

[0016] In other embodiments, it may also be determined whether the display of the corresponding first capsule is subject to a time limit according to the importance and urgency of the pushed information, so as to prevent the user from missing important and urgent information.

[0017] In some embodiments, the first type of information includes taxi notification information, navigation notification information, food delivery information, game information, and itinerary reminders; the second type of information includes access control service information, attendance reminder information, payment service information, subway service information, and express pickup information.

[0018] In the above embodiment, the first type of information may be information that the user explicitly indicates they need to view. For example, the first type of information may be notifications generated by services initiated in response to user actions (such as taxi services, navigation services, food delivery services, flight services, train services, and gaming services). The second type of information is information that the device predicts the user may need to view.

[0019] In some embodiments, when the first information is information of the first type, the operation on the first capsule includes a click operation on the first capsule; after canceling the display of the first capsule, the method further includes: displaying a third interface, which is a user interface for processing the first information; detecting a second operation in which the user indicates to exit, displaying the second interface again, and not displaying the first capsule.

[0020] In the above embodiment, after the user operates the wearable device to process the first information, for example, after clicking to view it, the first capsule can be canceled to avoid excessive interference of the first information to the user.

[0021] In some embodiments, when the first information is information of a first type, the operation on the first capsule includes a sliding operation relative to the first capsule.

[0022] In some embodiments, after switching from the first interface to the second interface in response to the user's first operation, the method further includes: displaying a fourth interface in response to the user's third operation, the fourth interface including a first card or a first icon for pushing the first information; canceling the display of the first capsule; displaying the second interface again in response to the user's fourth operation, and displaying the first capsule again.

[0023] In the above embodiment, the wearable device avoids multiple access points to the first information on the same interface by temporarily canceling the display of the first capsule, thereby achieving information deduplication.

[0024] In some embodiments, when the first information is information of the first type, after displaying the first capsule, the method further includes: displaying a second capsule, and canceling the display of the first capsule, the second capsule being used to push second information, the push confidence of the second information being lower than the push confidence of the first information, the push confidence being used to characterize the probability that the pushed information is information that the user actually needs to view, and the push time point of the second information being later than the first information; after the wearable device displays the second capsule for a second time period, canceling the display of the second capsule and displaying the first capsule again.

[0025] In the above embodiment, the first message is of the first type, and the second message has a lower push confidence than the first message and is pushed later than the first message. When the second message needs to be pushed, the first capsule can be temporarily hidden and the second capsule displayed to ensure that the second message reaches the user. After the second duration, the first capsule is restored and the second capsule is removed, ensuring that the message with higher push confidence effectively reaches the user.

[0026] In some embodiments, when the first information is information of the first type, after displaying the first capsule, the method further includes: displaying a third capsule, and canceling the display of the first capsule, wherein the third capsule is used to push third information, the third information is also information of the first type, and the push time point of the third information is later than the push time point of the first information.

[0027] In the above embodiment, when pushing information of the same first type, the information is pushed in the order of the pushing time points.

[0028] In some embodiments, in response to a status update of the first information, the third capsule is canceled from display, and the first capsule is displayed again.

[0029] In the above embodiment, the first information that has been canceled from display can be triggered to display the first capsule again after being updated, to ensure that the updated first information can reach the user.

[0030] In some embodiments, the first information includes progress information updated in real time, and the method further includes: in response to the progress information being updated to indicate completion of progress, determining a status update of the first information.

[0031] In some embodiments, the first information includes first content and second content, and the first capsule is used to scroll and display the first content and the second content.

[0032] In some embodiments, the wearable device is communicatively connected to the first device, and before displaying the first capsule, the method further includes: receiving a first indication from the first device, the first indication including an identifier representing the push of the first information and a display attribute corresponding to the first capsule; when the first information is information of the second type, the first capsule corresponds to a first attribute value, and when the first information is information of the first type, the first capsule corresponds to a second attribute value, the first attribute value indicates that the first capsule is displayed within a limited time, and the second attribute value indicates that the display time of the first capsule is not limited.

[0033] In some embodiments, before displaying the first capsule, the method further includes: displaying a first pop-up window, where the first pop-up window is used to push the first information; and canceling the display of the first pop-up window after the first pop-up window is displayed for a third time period.

[0034] In some embodiments, the wearable device is communicatively connected to a first device, and before displaying the first capsule, the method further includes: receiving a first indication from the first device for the Nth time, the first indication including an identifier representing the push of the first information; wherein N is a preset positive integer, and the first information is information of the second type; displaying the first capsule includes: displaying the first capsule for the Nth time in response to the first indication; canceling the display of the first capsule after the time for displaying the first capsule reaches a first duration; during the first N times of displaying the first capsule, if no user operation on the first capsule is detected, the method further includes: receiving the first indication for the N+1th time; and not displaying the first capsule.

[0035] In the above embodiment, if no user operation on the first capsule is detected during the first N times the first capsule is displayed, it can be recognized that the user is not interested in the first information. In this scenario, the number of pushes is adjusted to avoid excessive interference to the user caused by frequent pushes.

[0036] In some embodiments, the method also includes: responding to user operations, displaying an AOD interface for screen off; receiving an indication to push a fourth message, not displaying a capsule for pushing the fourth message, the fourth message being information of the second type; responding to user operations, switching the display of a dial interface from the AOD interface, displaying a fourth capsule on the dial interface, the fourth capsule being used to push the fourth message; responding to user operations, displaying the screen off display interface again; and responding to fifth information, displaying a fifth capsule for pushing the fifth message, the fifth message being information of the first type.

[0037] In the above embodiment, the first capsule corresponding to the first type of information can be displayed on all user interfaces of the wearable device, achieving unlimited global display. The first capsule corresponding to the second type of information can be displayed on most user interfaces of the wearable device, achieving limited global display, and avoiding excessive interference of the second type of information to the user.

[0038] In other embodiments, the notification center interface and the dynamic notification pop-up window may not display the second type of information.

[0039] In a second aspect, an information push method provided by an embodiment of the present application is applied to a first device and a wearable device that communicate with each other, and the method includes: the first device displays a card or capsule for pushing first information, and the wearable device displays a first interface, where the first interface is any user interface of the wearable device; the first device sends a first indication to the wearable device, where the first indication corresponds to the first information; the wearable device displays a first capsule in response to the first indication, where the first capsule is used to push the first information; the wearable device switches from the first interface to display the second interface in response to the user's first operation, and continues to display the first capsule.

[0040] In a third aspect, an embodiment of the present application provides a wearable device, comprising: a display screen, a processor, and a memory, wherein the memory is used to store computer instructions, and the display screen is used to push information to a user. When the processor executes the computer instructions, the wearable device executes the method described in the first aspect and its possible real-time examples.

[0041] In a fourth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions. When the computer instructions are executed on a wearable device, the wearable device executes the method of the first aspect and its possible embodiments. When the computer instructions are executed on the wearable device and the first device, the wearable device and the first device collaboratively execute the method of the second aspect and its possible embodiments.

[0042] In a fifth aspect, the present application provides a computer program product, which, when executed on the wearable device, enables the wearable device to execute the method of the first aspect and its possible embodiments. When the computer program product is executed on the wearable device and the first device, enables the wearable device and the first device to collaboratively execute the method of the second aspect and its possible embodiments.

[0043] In a sixth aspect, the present application provides a chip system, which is applied to a wearable device and a first device, and stores a computer program. When the computer program is executed, the wearable device and the first device execute the method in the above-mentioned first aspect and its possible embodiments.

[0044] It can be understood that the electronic devices, computer storage media and computer program products provided in the above aspects are all applied to the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] FIG1 is an example diagram of a method for pushing information of different importance and urgency levels by a mobile phone according to an embodiment of the present application;

[0046] FIG2 is one of example diagrams of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0047] FIG3 is a second example diagram of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0048] FIG4A is a third example diagram of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0049] FIG4B is a fourth example diagram of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0050] FIG5 is a fifth example diagram of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0051] FIG6 is a sixth example diagram of an interface for information push by a mobile phone in an actual usage scenario provided by an embodiment of the present application;

[0052] FIG7A is an example diagram of a scenario in which a mobile phone cooperates with a smartwatch to push information according to an embodiment of the present application;

[0053] FIG7B is an example diagram of an interface in which a smartwatch pushes information using icons in an actual usage scenario provided by an embodiment of the present application;

[0054] FIG7C is an example diagram of an interface in which a smartwatch pushes information using icons in an actual usage scenario provided by an embodiment of the present application;

[0055] FIG8 is an example diagram of an interface for a smartwatch to push information in the form of a card in an actual usage scenario provided by an embodiment of the present application;

[0056] FIG9 is an example diagram of an interface in which a smartwatch uses dynamic full-screen pop-up windows and cards to push information in an actual usage scenario provided by an embodiment of the present application;

[0057] FIG10A is one of example diagrams of an interface in which a smartwatch uses a suspended capsule to push information in an actual usage scenario provided by an embodiment of the present application;

[0058] FIG10B is a second example diagram of an interface for a smartwatch using a suspended capsule to push information in an actual usage scenario provided by an embodiment of the present application;

[0059] FIG11A is an example diagram of classifying information types according to importance and urgency provided by an embodiment of the present application;

[0060] FIG11B is an example diagram of FIG11A;

[0061] FIG11C is another example diagram of FIG11A;

[0062] FIG12A is a diagram showing examples of displays of a transient capsule in different usage scenarios provided by an embodiment of the present application;

[0063] FIG12B is an example diagram of the display of the resident capsule in different usage scenarios provided by an embodiment of the present application;

[0064] FIG13 is an example diagram of an instruction to cancel a resident capsule according to an embodiment of the present application;

[0065] FIG14A is a diagram illustrating an example of a display scene of a transient capsule provided in an embodiment of the present application;

[0066] FIG14B is an example diagram of a suspended capsule scrolling to display multiple key contents according to an embodiment of the present application;

[0067] FIG15 is an example diagram of a smartwatch according to an embodiment of the present application using a dynamic full-screen pop-up window and a floating capsule to push information;

[0068] FIG16 is an example diagram of deduplication of push messages when a smartwatch according to an embodiment of the present application uses a resident capsule to push messages;

[0069] FIG17 is an example diagram of deduplication of push messages during information push by a smartwatch using a transient capsule according to an embodiment of the present application;

[0070] FIG18 is one of the exemplary diagrams of a smartwatch according to an embodiment of the present application using a suspended capsule to push multiple target information in sequence;

[0071] FIG19 is a second example diagram of a smartwatch according to an embodiment of the present application using a suspended capsule to push multiple target information in sequence;

[0072] FIG20 is a third example diagram of a smartwatch according to an embodiment of the present application using a suspended capsule to push multiple target information in sequence;

[0073] FIG21 is one of the example diagrams of a smartwatch according to an embodiment of the present application using a suspended capsule to push download progress information;

[0074] FIG22 is a second example diagram of a smartwatch using a suspended capsule to push download progress information according to an embodiment of the present application;

[0075] FIG23 is an example diagram of various capsules provided in an embodiment of the present application;

[0076] Figure 24 is an example diagram of the structure of the smart watch provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0078] The implementation of this embodiment will be described in detail below with reference to the accompanying drawings.

[0079] The present application provides an information push method for use in an electronic device pushing information to a user. The pushed information may include various types of messages, such as system messages and application messages. The pushed information may also include various functions, such as application services. The pushed information may also include application programs that need to be recommended to the user.

[0080] Exemplarily, the above-mentioned electronic device is a device equipped with a display screen. For example, the electronic device can be a portable computer (such as a mobile phone), a wearable device (such as a smart watch), a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, as well as a cellular phone, a personal digital assistant (PDA), a media player, and other devices with a screen (or display screen). The embodiments of the present application do not impose any special restrictions on the specific form of the electronic device.

[0081] Among them, the mobile phone can select an appropriate push form (or contact entry) to push information to the user according to the importance and urgency of the information. Exemplarily, the above push form (or contact entry) may include: cards, icons, capsules, etc.

[0082] The cards and capsules can display text or graphic identifiers related to the pushed information. For example, they can display the key content, status (progress) information, detailed content, and / or graphic identifiers of the pushed information. Information can include one or more key contents, and different key contents can describe the information from different dimensions. In addition, all key contents can constitute the detailed content corresponding to the information. The status (progress) information can indicate how a key content of the information changes over time.

[0083] The icon may display a graphic identifier related to the pushed information. For example, if the pushed information is an application message, the icon may be the application icon of the application that provided the application message. If the pushed information is an application service, the icon may be the application icon of the application that provides the application service, or the service icon corresponding to the application service.

[0084] The capsules can be displayed on any display interface, such as the application interface provided by system applications or third-party applications. If the information being pushed is an application service or application, the phone can choose to use the capsule to display information related to the application service or application.

[0085] In addition, the capsules may include status bar capsules and suspension capsules.

[0086] Status bar capsule

[0087] Exemplarily, the status bar capsule can be displayed in the signal bar. The layer corresponding to the signal bar is located above the layer corresponding to the real-time displayed interface. In the process of switching the display interface of the mobile phone, the display position of the signal bar remains unchanged. Of course, when the mobile phone enables full-screen display mode (such as displaying the game interface provided by the game application), the mobile phone can hide the signal bar. When the display mode of the mobile phone switches between horizontal display mode and vertical display mode, the display position of the signal bar can change.

[0088] In some examples, the status bar capsule can be used to display pushed information with progress updates and high real-time performance, such as taxi notifications (notifications from taxi travel services that prompt users to go to the pick-up point and wait for the car), navigation services, download progress, etc. For example, when the pushed information is an application service, the status bar capsule can display relevant information such as the real-time status or service progress of the above application service. When the pushed information is an application, the status bar capsule can also display the application icon of the above application. The user can click on the status bar capsule to indicate the switch to display the application service interface corresponding to the pushed application service, or to switch to display the application main interface corresponding to the pushed application.

[0089] Suspension capsules

[0090] Exemplarily, the above-mentioned suspended capsule can be displayed at any position of the display interface, for example, at the right edge of the display interface.

[0091] In some examples, the floating capsule can display the key content corresponding to the pushed information. For example, if the pushed information is a taxi notification, the key content may be the license plate number of the vehicle. For another example, if the pushed information is a payment service, the key content may be the text "payment code." Furthermore, the floating capsule can also display a graphic logo corresponding to the pushed information. For example, if the pushed information is a taxi notification, the graphic logo may be a vehicle image.

[0092] By clicking on the floating capsule, the user can instruct the phone to display the application interface corresponding to the pushed information. If the pushed information is a message, the corresponding application interface can be a details interface containing the details of the pushed information; if the pushed information is an application service, the corresponding application interface can be the application service interface.

[0093] In addition, the floating capsule can correspond to an expanded state and a folded state. Compared with the floating capsule in the folded state, the floating capsule in the expanded state occupies a larger display space, can display more content, and can display more relevant information. The mobile phone displays the floating capsule in the folded state by default. In response to the user's operation on the floating capsule, the floating capsule in the expanded state is displayed. For example, the mobile phone uses a folded floating capsule to display the icon of the map application to prompt the user to pay attention to the map application. Afterwards, in response to the user's operation, the floating capsule in the expanded state can be displayed. The above-mentioned floating capsule in the expanded state includes multiple configuration items, and each configuration item corresponds to an application service entrance related to the map application, including the entrance of the application service in the map application (such as the entrance of the navigation service), and also includes the entrance of the application service provided by other applications (such as the address collection service provided by the note application).

[0094] The above cards can be displayed on the main interface, negative one screen, always on display (AOD) interface, lock screen interface, notification bar interface and other application interfaces.

[0095] The main interface is a split screen of the desktop, which can be a user interface provided by a desktop application (a system application used to manage application icons of installed applications). After the phone is unlocked, the main interface can be displayed. After that, the phone can respond to user operations and display other split screens corresponding to the desktop. The split screen corresponding to the desktop also includes a negative first screen, which is used to centrally display the information the user has subscribed to and the information assessed by the user to view.

[0096] The AOD interface can be the interface displayed on a phone with the AOD function enabled, after the screen is locked or off. Cards displayed on the AOD interface can be called AOD cards. Users can view information pushed by the phone through AOD cards without unlocking the phone.

[0097] While the phone is displaying the main interface (or the negative one screen), the phone detects a triggering event that requires pushing information to the user, and displays a card containing the pushed information in the display area of ​​the main interface (or the negative one screen), guiding the user to pay attention to the pushed information. It can be understood that according to pre-configured business rules, different pushed information can correspond to different triggering events. For example, the phone detects that the device is approaching a courier storage point, and can determine that it needs to push a pickup code related to the courier storage point, such as the pickup code corresponding to the courier stored at the courier storage point and belonging to the user.

[0098] In addition, the above-mentioned cards may also include dynamic notification cards and dynamic pop-up cards. For example, when other application interfaces are displayed, the mobile phone detects a triggering event that requires pushing information to the user, and may display a dynamic notification card or a dynamic pop-up card. After the dynamic notification card is displayed, if the display duration of the dynamic notification card reaches a preset duration of 1, the mobile phone may cancel the display of the dynamic notification card. The dynamic message card may display the key content and / or the corresponding status (progress) information corresponding to the pushed information, so that the user can keep abreast of services or messages with higher real-time requirements when using other applications on the mobile phone.

[0099] After displaying a dynamic pop-up card, the phone can cancel the display of the dynamic pop-up card in response to a user's action on the dynamic pop-up card. Compared to dynamic notification cards, these dynamic pop-up cards are more eye-catching and occupy more display space. They can interrupt the user's current mobile phone usage, ensuring that the user pays attention to the pushed information and that the pushed information reaches the user effectively.

[0100] In the above embodiment, among the push forms cited, dynamic pop-up cards belong to global interruptive reminders, dynamic notification cards belong to global large-area reminders, floating capsules and status bar capsules belong to global strong reminders, main interface cards and negative one-screen cards belong to small-scale weak reminders, and icons belong to reminders that do not disturb and can be viewed at any time. Among them, the corresponding reach efficiencies of the above-mentioned "global interruptive reminders", "global large-area reminders", "global strong reminders", "small-scale weak reminders" and "non-disturbing and viewable reminders" gradually decrease. It can be understood that the above-mentioned reach efficiency can represent whether the user can effectively pay attention to the information after the information is pushed. Among them, the higher the reach efficiency, the higher the probability that the user can effectively pay attention to the information after the information is pushed using this push form.

[0101] In some embodiments, the higher the urgency and / or importance of the information, the higher the reach efficiency of the optional push form.

[0102] In some embodiments, the urgency of the information is measured by whether it requires immediate attention to view, process, or use the service immediately. For example, in one example, the urgency of the service notification may include very urgent, urgent, general, or non-urgent.

[0103] For example, a very urgent notification requires the user to process it within a first preset time (such as 60 seconds), for example, a notification that reinforces a warning to the user, such as a taxi notification.

[0104] Urgent notifications need to be processed within a second preset time (eg, 15-60 minutes).

[0105] Generally refers to services that are in progress within 24 hours. For example, if a user purchases a flight ticket for 5 days in advance, the flight travel service will remind the user one day in advance of relevant flight reminders, such as check-in and boarding.

[0106] Non-urgent notifications generally do not require user action.

[0107] In one embodiment, the importance is measured by whether ignoring the information will cause significant impact, such as loss of life, property, time, opportunity, etc. In one example, the importance of service notifications may include very important, important, moderately important, and unimportant.

[0108] Very important means that if the user does not handle it, it may threaten the user's life, for example, notifications about major natural disasters such as earthquakes and typhoons.

[0109] Important means that if the user does not handle it, property may be damaged, for example, taxi notifications, express delivery timely pickup notifications, etc.

[0110] Generally important means that if the user misses it, it may cause a waste of user time, for example, a notification during express delivery.

[0111] Unimportant means that if the user misses it, it will have no impact on the user, for example, the system reminds the user of the healthy use of mobile phone time.

[0112] In some embodiments, as shown in FIG1 , the horizontal axis represents the importance of information, and the vertical axis represents the urgency of information. The importance and urgency of information jointly determine the optional push form for this type of information.

[0113] In other words, FIG1 shows different types of information, such as information with different urgency and / or different importance, and corresponding one or more optional push forms.

[0114] Mobile phone developers or users can select the push form actually used for each information (service, message or application) from the optional push forms according to actual business needs, such as the target push form, and configure the mobile phone to push the information using the target push form.

[0115] As shown in Figure 1, for very important and urgent information, the optional push formats include all push formats provided by the mobile phone. Taking the very important and urgent earthquake warning notification as an example, the mobile phone can pre-configure the target push format of the earthquake warning notification as a dynamic pop-up card. The high reach efficiency of the dynamic pop-up card enables users to pay attention to the earthquake warning notification in a timely manner. Taking the very important and urgent typhoon notification as another example, the mobile phone can pre-configure the target push format of the typhoon notification as a dynamic notification card. The timeliness and eye-catching nature of the dynamic notification card can prompt users to pay attention to the real-time typhoon situation without excessively affecting their mobile phone use.

[0116] In addition, for very important and very urgent information, the mobile phone can also combine multiple push forms to push the information to the user. For example, the mobile phone can pre-configure the target push form of this type of information, including dynamic pop-up cards, dynamic notification cards, AOD cards, cards on the lock screen interface (lock screen cards), cards on the negative one screen (negative one screen cards), cards on the main interface (main interface cards), status bar capsules, floating capsules, notifications on the notification bar interface, etc. When it is detected that very important and very urgent information needs to be pushed, the mobile phone can use a dynamic pop-up card to display the information to ensure that the information can effectively reach the user. In addition, if the mobile phone is displaying the AOD interface, the AOD card corresponding to the information can be displayed on the AOD interface. If the mobile phone is displaying the negative one screen, the card corresponding to the information can be displayed on the negative one screen. If the mobile phone is displaying the main interface, the card corresponding to the information can also be displayed on the main interface. After detecting that the user instructs to cancel the display of the dynamic pop-up card, the user can also pay attention to the above-mentioned very important and very urgent information through the card displayed on the AOD interface (or, the negative one screen, the main interface). In other examples, after canceling the display of the dynamic pop-up card, the mobile phone can also display the status (progress) information of the very important and very urgent information through a status bar capsule. Alternatively, a floating capsule is used to display an entrance for viewing the very important and very urgent information.

[0117] As shown in Figure 1, for unimportant and non-urgent information, there are fewer push formats available, such as only cards on the negative one screen. Therefore, for unimportant and non-urgent information, the phone can pre-configure the target push format to be cards on the negative one screen. During actual operation, when the phone detects that unimportant and non-urgent information needs to be pushed, it pushes the information via the card on the negative one screen. In this scenario, after the phone responds to the user's action and displays the negative one screen, the user can focus on the information, avoiding frequent reminders and interruptions to the user.

[0118] In addition, FIG1 also shows other types of information and the corresponding optional push forms, which will not be described in detail here.

[0119] The following describes the process of mobile phones using various push forms to push information through several common scenarios.

[0120] In the scenario where a user uses their mobile phone to hail a ride online: After the mobile phone detects the user's request to hail a ride, for example, after detecting that the user has configured a trip and clicked the control indicating a matching vehicle, it can push corresponding ride notifications to the user at one or more process nodes, such as when a suitable vehicle is matched, when the vehicle is about to arrive at or has arrived at the user's designated departure location, when the passenger has boarded the vehicle, or when the vehicle has arrived at the user's designated destination. The ride notification corresponding to the process node "matched with a suitable vehicle" may include the vehicle's appearance, license plate, and driver information. The ride notification corresponding to the process node "vehicle is about to arrive at or has arrived at the user's designated departure location" may include the vehicle's license plate, appearance, driver information, road conditions for the vehicle to the departure location, and the estimated time it will take for the vehicle to arrive at the departure location. The ride notification corresponding to the process node "passenger has boarded the vehicle" may include the license plate, appearance, driver information, and the estimated time it will take for the vehicle to arrive at the destination. The ride notification corresponding to the process node "vehicle has arrived at the user's designated destination" may include a trip end reminder and fare settlement information.

[0121] Taking the taxi notification corresponding to the node "The vehicle is about to arrive at or has arrived at the departure point specified by the user" as an example, the taxi notification corresponding to the node "The vehicle is about to arrive at or has arrived at the departure point specified by the user" is very urgent and important information. The optional push forms include: cards on the lock screen interface, cards on the main interface, cards on the negative one screen, cards on the notification bar interface, dynamic notification cards, status bar capsules, floating capsules, etc. In addition, when the AOD function is enabled on the mobile phone, the optional push forms also include: AOD cards. It can be understood that when the AOD function is enabled, after the mobile phone's display screen is turned off, at least one type of information can be displayed in part of the display screen without lighting up the entire display screen, for example, displaying time, animation, etc. in part of the display screen.

[0122] In some embodiments, the mobile phone can select the most efficient push form from the available push forms, such as a dynamic notification card, to push the aforementioned taxi-hailing notification. In other embodiments, the mobile phone can flexibly select one or more push forms from the available push forms based on the actual display scenario to push the aforementioned taxi-hailing notification.

[0123] In one of the exemplary scenarios, the mobile phone detects the user's instruction to take a taxi and matches the vehicle required for the user's travel (such as a travel vehicle), and then the mobile phone can receive the real-time location of the travel vehicle. When the mobile phone detects the user's instruction to turn off the screen, such as clicking the power button of the mobile phone, the AOD interface 201 as shown in Figure 2 can be displayed. The AOD interface 201 includes an AOD card 202, and the AOD card 202 displays the matched vehicle information. In addition, before the mobile phone displays the AOD card 202, the mobile phone can also display a dynamic notification card 302. After canceling the display of the dynamic notification card 302, the above-mentioned AOD card 202 is displayed again.

[0124] After displaying AOD interface 201, the mobile phone continues to receive the real-time location of the traveling vehicle. When the distance between the real-time location of the traveling vehicle and the user-specified departure point is less than a distance value of 1, the current process node is determined to be "The vehicle is about to or has arrived at the user-specified departure point." Furthermore, in response to the distance between the real-time location of the traveling vehicle and the user-specified departure point being less than the distance value of 1, the mobile phone may also update the display content on AOD card 202, for example, by adding an estimated time of arrival at the boarding point.

[0125] The AOD card 202 is used to present a taxi notification. The AOD card 202 may include key information about the taxi notification, such as the vehicle's license plate information and the estimated time of arrival at the pickup point. This AOD card 202 can be used to direct the user's attention to the fact that the vehicle is about to arrive at or has arrived at the user's designated departure point when viewing the AOD interface.

[0126] Afterwards, the mobile phone detects an operation instructing the user to light up the screen, such as the user clicking the display screen, and the mobile phone can light up the entire display screen and display the lock screen interface 203 as shown in FIG. 2 .

[0127] Among them, the lock screen interface 203 includes a lock screen card 204, which is also used to present a taxi notification. Compared with the taxi notification displayed by the AOD card 202, it has more key content. For example, in addition to the license plate information of the traveling vehicle, it also includes an estimated duration 1. The above-mentioned estimated duration 1 is an assessment of the time required for the traveling vehicle to arrive at the departure point configured by the user.

[0128] In addition, during the AOD card 202, in response to the user clicking the AOD card 202, the mobile phone can also light up the entire display screen and display the lock screen interface 203 as shown in Figure 2, which includes a lock screen card 204.

[0129] In some embodiments, in response to a user unlocking operation, the mobile phone may display a home interface 205 as shown in FIG. This home interface 205 may include a home interface card 206. The home interface card 206 is also used to present the aforementioned taxi notification. Compared to the lock screen card 204, the home interface card 206 not only contains the key content of the taxi notification, but also includes a functional entry for processing the taxi notification, such as a control 207 for contacting the driver of the vehicle. In response to the user's operation of control 207, the mobile phone can display a detailed interface containing the driver's contact information, or directly dial the driver's reserved phone number.

[0130] It is understandable that the user can process the taxi notification through the main interface card 206. In addition, the main interface card 207 is only displayed on the main interface 205. To a certain extent, it can improve the human-computer interaction efficiency of processing the taxi notification while avoiding interfering with the user's normal use of the mobile phone.

[0131] In some embodiments, in response to a user's instruction to view the negative first screen, for example, in response to a right swipe while displaying the main interface 205, the mobile phone may display the negative first screen 208 shown in FIG2 . The negative first screen 208 may also include a negative first screen card 209 for presenting a taxi-hailing notification. The negative first screen card 209 may prompt the user to pay attention to the taxi-hailing notification while the user is viewing the negative first screen.

[0132] In addition, the taxi notification corresponding to "The vehicle is about to or has arrived at the user's designated departure location" is a taxi notification that can update its status in real time. Correspondingly, the cards used to display the taxi notification (e.g., lock screen card 204, home interface card 206, and negative one screen card 209) can also dynamically update their display content. For example, the lock screen card 204, home interface card 206, and negative one screen card 209 all display an estimated duration of 1. This estimated duration 1 can decrease as the vehicle approaches the departure location. Until the vehicle arrives at the departure location, the estimated duration 1 is no longer displayed, and an indicator indicating that the vehicle has arrived is displayed.

[0133] In the second exemplary scenario, after the mobile phone detects a user's instruction to hail a taxi and matches the user with a vehicle required for the trip (e.g., a travel vehicle), the mobile phone can receive the real-time location of the travel vehicle. The user can then use other applications on the phone normally. For example, in response to a user's instruction to run a memo app, the mobile phone can run the memo app and display the application interface provided by the memo app, such as note interface 301 in Figure 3.

[0134] After displaying note interface 301, the mobile phone continues to receive the real-time location of the traveling vehicle. When the distance between the real-time location of the traveling vehicle and the user-specified departure point is less than a distance value of 1, the current process node is determined to be "The vehicle is about to or has arrived at the user-specified departure point." Furthermore, in response to the distance between the real-time location of the traveling vehicle and the user-specified departure point being less than a distance value of 1, the mobile phone may also display a dynamic notification card 302 on note interface 301. This dynamic notification card 302 may be used to present a taxi notification, for example, displaying key information regarding the taxi notification, such as the license plate information and the estimated time 1.

[0135] In some embodiments, when the display duration of the dynamic notification card 302 reaches a preset duration 1 (eg, 3 seconds) and no user instruction to process the dynamic notification card 302 is received, the mobile phone may cancel the display of the dynamic notification card 302 .

[0136] After deselecting the dynamic notification card 302, the phone may display the notification interface 303 shown in FIG3 in response to a user's instruction to view the notification bar, such as a swipe down on the note interface 301. Notification interface 303 may display notifications that have been pushed to the user and for which the user has not indicated a response. For example, if the user has not indicated a response to a taxi notification, notification interface 303 may include a notification card 304 for presenting the taxi notification.

[0137] In addition, after canceling the display of the dynamic notification card 302, the mobile phone can continue to push the taxi notification to the user by displaying a capsule in the status bar.

[0138] For example, as shown in FIG4A , after the dynamic notification card 302 is deactivated, a status bar capsule 402 corresponding to the taxi hailing notification is displayed on the status bar 401. It is understood that the estimated time 1 corresponding to the taxi hailing notification may change as the distance between the vehicle and the departure point changes. The status bar capsule 402 can display the estimated time 1 corresponding to the taxi hailing notification in real time, allowing the user to easily understand the real-time progress of the vehicle before it arrives at the departure point.

[0139] In other embodiments, after the user instructs the mobile phone to enable a specific type of service (eg, a translation service), when the mobile phone recognizes a scenario applicable to the service again, a floating capsule may be displayed to push the service to the user.

[0140] As shown in Figure 4B, the electronic device displays an application interface 403 provided by the novel application, and in response to the user's instruction to translate word 404 (standing), displays a translation window 405. The translation window 405 displays the translation content corresponding to word 404. In this scenario, it can be determined that the user has enabled the translation service.

[0141] The electronic device then responds to the user's operation by displaying an application interface 406. This application interface 406 can be provided by a novel application or another application. When English text 407 is included in application interface 406, the electronic device can recognize that the translation service is currently being used and display a floating capsule 408, which recommends the translation service to the user.

[0142] In a scenario where a user browses images on a mobile phone, the mobile phone responds to the user selecting a target image. Based on the target image, the mobile phone can evaluate the application service the user currently needs to use, such as the target service, and push the target service to the user. As shown in Figure 5, the mobile phone displays a chat application interface 501, which includes multiple chat records, such as image data 502 sent by contact A. In response to the user long-pressing image data 502, the mobile phone can determine that image data 502 is the target image and, based on the target image, evaluate the target application service the user currently needs to use.

[0143] Illustratively, the target application services include application services for processing image data, such as image sharing services, image printing services, and search services. Furthermore, the target application services may include application services determined based on the content of the target image. For example, if image data 502 shows shoes, the target application services may include an application service for querying shoe prices, such as a price comparison service.

[0144] In some embodiments, in response to determining the target application service, the mobile phone may display a portal interface 503 , wherein the portal interface 503 includes a search icon 504 , a price comparison icon 505 , a print icon 506 and an analysis icon 507 .

[0145] For example, in response to a user clicking on search icon 504, the mobile phone may activate a search service to search for data related to image data 502. In response to a user clicking on price comparison icon 505, the mobile phone may activate a price comparison service to query price information for shoes in image data 502. In response to a user clicking on print icon 506, the mobile phone may send image data 502 to a printer, instructing the printer to print image data 502. In response to a user clicking on share icon 507, the mobile phone may display ways to share image data 502.

[0146] In some embodiments, for very important and very urgent information, such as earthquake early warning notification, if a dynamic pop-up window is used to push the earthquake early warning notification in advance, the mobile phone receives the earthquake early warning notification from the earthquake early warning server, as shown in Figure 6, and a dynamic pop-up window card 601 can be directly displayed. The dynamic pop-up window card 601 includes the key information of the earthquake early warning notification, such as the time required for the earthquake wave to arrive at the user's current position, the epicenter position, the distance between the epicenter and the user's current position, and the earthquake level. In other embodiments, for very important and very urgent information, such as earthquake early warning notification, after using a dynamic pop-up window to push, it is also possible to select an adapted push form according to the current display scene of the mobile phone and continue to push the earthquake early warning notification. For example, the mobile phone is displaying the AOD interface, and the AOD card is selected to continue to push the earthquake early warning notification.

[0147] In the above embodiments, the mobile phone can push information to the user through one or more push forms to ensure that the information can effectively reach the user. In fact, whether the information can effectively reach the user is also affected by other factors, such as whether the user is using the mobile phone. In order to improve the efficiency of information reaching the user during the period when the user is not using the mobile phone, the mobile phone can also cooperate with the user's wearable device, such as a smart watch, to push information to the user. The above-mentioned smart watch can be a smart watch with a round dial or a smart watch with a square dial. This embodiment of the present application does not specifically limit this. In the subsequent embodiments, the smart watch with a round dial is mainly used as an example.

[0148] In some embodiments, as shown in FIG7A , after a connection is established between a mobile phone and a smartwatch, the mobile phone determines target information to be pushed to the user. In addition to using its own display to push the target information, the mobile phone can also instruct the smartwatch to push the target information. For example, the mobile phone can send a push notification to the smartwatch, and the smartwatch can respond to the push notification from the mobile phone by pushing the target information to the user in the form of an icon, card, and / or dynamic full-screen pop-up window.

[0149] For example, in response to a push collaboration notification from a mobile phone, the smart watch can display an icon representing the target information in the smart interface and / or the negative one screen. For example, when the target information is an application, the above icon can be an application icon of the application. For another example, when the target information is an application service, the above icon can be a service icon corresponding to the application service.

[0150] Taking the target information as payment service information as an example, as shown in FIG7B , when the mobile phone displays a lock screen interface 705 , if it is determined that the payment service information needs to be pushed, the mobile phone may display an icon 706 on the lock screen interface 705 .

[0151] As shown in FIG7C , when the mobile phone displays the main interface 706 , if it is determined that payment service information needs to be pushed, the mobile phone may also display a service entry icon 707 for the payment service on the main interface 706 .

[0152] When the mobile phone displays the payment service icon (eg, icon 706 or service entry icon 707), if the user clicks icon 706 (or service entry icon 707), the mobile phone may display the application interface corresponding to the payment service in response to the operation.

[0153] In addition, after determining that payment service information needs to be pushed, the mobile phone can also instruct the smart watch to push the payment service information, for example, by sending a push cooperation notification to the smart watch. When the smart watch displays the smart interface 701, in response to the push cooperation notification from the mobile phone, the smart watch can display a service icon 702 of the payment service on the smart interface 701.

[0154] If the smartwatch has a payment program installed for providing payment services, in response to clicking the service icon 702, the smartwatch may display an application interface of the payment program, such as an interface containing payment key information. If the payment program is not installed on the smartwatch, the smartwatch may display a prompt message, which may remind the user to activate the payment service by operating the mobile phone.

[0155] In addition, the smartwatch can also respond to user operations by displaying a watch negative screen 703 while the smartwatch is displaying the smart interface. The negative screen 703 includes a service icon 704. The service icon 704 and the service icon 702 on the smart interface 701 are both service icons corresponding to payment services.

[0156] For example, in response to a push notification from a mobile phone, the smartwatch may also display a card in the smart interface, notification bar interface, and / or negative one screen to present the target information. For example, if the target information is a notification message, the card may display the key content of the notification message.

[0157] Taking the taxi-hailing notification as an example, as shown in Figure 8 , when the smartwatch displays smart interface 801, in response to a push notification from a mobile phone, the smartwatch can display a push card 802 on smart interface 801. Push card 802 displays the key content of the taxi-hailing notification, prompting the user to pay attention to the notification. Furthermore, in response to the user clicking push card 802, the smartwatch can display a full-screen display interface corresponding to the taxi-hailing notification, which contains the detailed content of the taxi-hailing notification.

[0158] In some examples, while smart interface 801 is displayed, a negative screen 803 may be displayed in response to a user action. Negative screen 803 may also include a push card 804, which displays key information about the taxi notification, prompting the user to pay attention to the notification. In response to the user clicking push card 804, the smartwatch may display a full-screen interface corresponding to the taxi notification.

[0159] In some examples, while displaying the smart interface 801, a notification bar interface 805 may also be displayed in response to a user operation. The notification bar interface may also include a notification card 806, which displays the key content of the taxi notification. Compared to card 804, the key content displayed in notification card 806 is more. In addition, the notification bar interface 805 may also include other unprocessed notification cards, such as notification card 807. Notification card 807 displays the key content of an application notification from a reading application. Of course, in response to a user sliding operation on the notification bar interface 805, the smartwatch may also display other hidden and unprocessed notification cards.

[0160] As another example, in response to a push notification from a mobile phone, the smartwatch can also display a dynamic full-screen pop-up window. As shown in Figure 9, when the smartwatch is displaying the negative one screen 901, it receives a push notification from the mobile phone. The push notification can control the smartwatch to push a taxi notification. In response to the push notification, the smartwatch can display a dynamic full-screen pop-up window 902, which includes the key content corresponding to the taxi notification and a details control 903. In response to clicking the details control 903, a full-screen display interface of the taxi notification can be displayed, which includes the detailed content of the taxi notification.

[0161] Additionally, while dynamic full-screen pop-up window 902 is displayed, in response to a user instruction to return to the original interface, such as by swiping up, the smartwatch may also display negative one screen 904. Compared to negative one screen 901, negative one screen 904 includes a newly added push card 905. In response to clicking push card 905, a full-screen display interface for a taxi-hailing notification may be displayed.

[0162] As you can understand, the display space corresponding to the smartwatch display is relatively small, and it is usually necessary to pre-configure a permanent interface. This permanent interface is the user interface that is displayed by default after the smartwatch turns on the screen. The above-mentioned permanent interface is also the user interface that is displayed by default when the smartwatch displays other interfaces in response to the user's instruction to return to the operation.

[0163] In some embodiments, the resident interface can be one of a smart interface, a negative one screen, and a custom watch face interface. The custom watch face interface can be a watch face interface generated by the smartwatch based on a user-selected image (background image), function controls, and time display mode (digital time or pointer time), or it can be a watch face interface provided by a third-party application.

[0164] In addition, the icons and cards (push cards and notification cards) used to push information must be displayed on the smart interface and / or the negative one screen. When the resident interface is a customized watch face interface, the user needs to manually switch the interface displayed on the smart watch, for example, from the customized watch face interface to the smart interface (or negative one screen), in order to view the pushed target information.

[0165] Obviously, in this scenario, the efficiency of targeted information reaching users is still low, and the human-computer interaction efficiency of users viewing the pushed targeted information through smartwatches is also low. In addition, if all targeted information is pushed using dynamic full-screen pop-up windows, the degree of interference to users will also be relatively high.

[0166] To address the aforementioned issues, the present invention provides an information push method that can be applied to wearable devices. Taking a smartwatch as an example, when a mobile phone and the smartwatch are working together to push target information, the smartwatch can display a floating capsule for pushing the target information. This ensures that the target information reaches the user while reducing interference with the user and improving the efficiency of human-computer interaction for the user in processing the target information through the smartwatch.

[0167] The following, combined with the accompanying drawings, introduces the implementation details of how a mobile phone collaborates with a smart watch to push target information to users.

[0168] In some embodiments, target information may be divided into deterministic service information (first type of target information) and service information of uncertain intent (second type of target information).

[0169] Exemplarily, the first type of target information refers to information that the user has a clear intention to view, such as information whose corresponding push confidence is assessed to be greater than a first value (90%). The above push confidence can represent the probability that the target information is the information actually needed by the user. Usually, the information that the user indicates needs to be viewed (such as information that is triggered to be pushed after the user configures the order information) has a corresponding push confidence greater than the first value. For example, it can include taxi notification information, navigation notification information, food delivery information, game information, itinerary reminders, etc.

[0170] For example, the second type of target information refers to information that the user has not shown an intention to view, and the mobile phone predicts that the user may need to view. For example, the corresponding push confidence is assessed to be no greater than the first value (90%). In other words, the push confidence of the second type of target information is lower than the push confidence of the first type of target information. For example, it may include access control service information, attendance reminder information, payment service information, subway service information, and express pickup information.

[0171] As shown in Figures 2 and 10A, when both the mobile phone and the smart watch display the AOD interface, for example, the mobile phone displays the AOD interface 201 and the smart watch displays the AOD interface 1001. In response to determining that the target information is the first type of target information (e.g., a taxi notification), the mobile phone can display the AOD card 202 and send a push collaborative notification 1 to the smart watch. In response to pushing the collaborative notification 1, the smart watch displays a suspended capsule 1002 on the AOD interface 1001. The suspended capsule 1002 displayed by the smart watch and the AOD card 202 displayed by the mobile phone are used to push the same taxi notification.

[0172] In the example of Figure 10A, the taxi-hailing notification is the first information, the AOD interface 1001 can be called the first interface, and the floating capsule 1002 can be called the first capsule. The push collaborative notification 1 is the first indication and can carry an identifier representing the push of the first information.

[0173] In some embodiments, the above-mentioned suspended capsule 1002 can be displayed globally. For example, in response to the user's operation of lighting up the smart watch, the smart watch can display a permanent interface. Taking the case where the permanent interface is a customized dial interface (such as the dial interface 1003 shown in Figure 10A) as an example, a suspended capsule 1002 is also displayed on the dial interface 1003 of the smart watch. While ensuring that the target information can reach the user, it does not affect the user's normal use of the smart watch. In the example of Figure 10A, the dial interface 1003 can be referred to as the second interface. The above-mentioned operation of lighting up the smart watch can trigger the smart watch to switch the display interface, such as switching the display dial interface 1003 by the AOD interface 1001. Correspondingly, the above-mentioned operation of lighting up the smart watch can be referred to as the first operation. Among them, the first operation is an operation to switch between different user interfaces, and the specific form of the first operation is not limited.

[0174] For example, taking Figure 10B as an example, when the mobile phone displays any interface and recognizes a scenario where the second type of target information (such as payment service information) needs to be pushed, the mobile phone can display a floating capsule 1004 for pushing payment services. After that, the mobile phone can instruct the smart watch to push the payment service information, for example, the smart watch displays a floating capsule 1006 on the dial interface 1005.

[0175] In addition, the above-mentioned floating capsule is also a functional entrance for users to quickly process target information. For example, in response to the user clicking the floating capsule 1002, the smart watch can display a full-screen display interface corresponding to the taxi notification.

[0176] In some embodiments, the suspended capsule may include a permanent capsule and a transient capsule, wherein the permanent capsule and the transient capsule have the following differences:

[0177] 1. The types of target information pushed are different.

[0178] For example, a resident capsule may be used to push a first type of target information, and a transient capsule may be used to push a second type of target information.

[0179] As an implementation manner, the mobile phone may distinguish whether the target information belongs to the first type of information or the second type of information according to the importance and urgency of the target information.

[0180] As shown in FIG. 11A , information with a general (or unimportant) importance and a general (or unurgent) urgency can be determined as the second type of information.

[0181] As shown in FIG. 11A , information with an importance level of important and an urgency level of urgent (or very urgent) can be determined as first type information.

[0182] In addition, the types of information pushed also include the third type. The third type of target information refers to information that must reach the user. As shown in Figure 11A, information with a very high importance can be determined as the third type of information. For the third type of target information, the mobile phone can instruct the smartwatch to push it in a dynamic full-screen pop-up window until the user has processed the target information.

[0183] Figure 11B shows the importance and urgency of the taxi notifications that need to be pushed to the user at different points during the online taxi-hailing process. The following taxi notifications need to be pushed to the user at different points during the online taxi-hailing process: Taxi Notification 1, indicating the end of a trip; Taxi Notification 2, indicating the ongoing trip; Taxi Notification 3, indicating a successful vehicle match; and Taxi Notification 4, indicating a vehicle is about to arrive at or has arrived at the user's designated departure location. As shown in Figure 11B , it can be determined that Taxi Notifications 1 through 4 all belong to the first type of information.

[0184] In addition, FIG11C shows that the importance of the payment service information is general and the urgency is also general. As shown in FIG11C , it can be determined that the payment service information belongs to the second type of information.

[0185] As another implementation manner, the mobile phone may determine whether the target information belongs to the first type or the second type according to a generation scenario of the target information.

[0186] For example, if the target information is determined based on the user's usage habits, the target information belongs to the second type of information. For example, the user's usage habits recorded by the mobile phone include: the user is likely to activate the ride code service at 8 o'clock in the morning on weekdays. Based on the above user usage habits, the mobile phone can identify the target information to be pushed as the ride code service at 8 o'clock in the morning on weekdays, and determine that the target information (ride code service) belongs to the second type of information.

[0187] As another example, if the target information is the information that needs to be pushed when the mobile phone executes one or more services, the target information belongs to the first type of information. Among them, one or more services can be services that are actively triggered by the user to execute on the mobile phone. For example, the user's instruction to take a taxi can trigger the mobile phone to execute an online taxi service, and the online taxi service belongs to the one or more services mentioned above. Correspondingly, in the process of the mobile phone executing the online taxi service, the taxi notification that needs to be pushed belongs to the first type of information. For another example, the user's instruction to download a file can trigger the mobile phone to execute a data download service, and the data download service belongs to the one or more services mentioned above. Correspondingly, in the process of executing the data download service, the download progress information that needs to be pushed also belongs to the first type of information. For another example, the user's operation of configuring the alarm time can trigger the mobile phone to execute a timed reminder service, and the timed reminder service belongs to the one or more services mentioned above. In the process of executing the timed reminder service, the time reminder notification that needs to be pushed also belongs to the first type of information.

[0188] After determining the type of target information, the mobile phone can instruct the smart watch to use a resident capsule or a transient capsule to display the target information. For example, the first instruction sent to the smart watch also includes the display attributes of the first capsule used to push the target information (such as the first information), such as the first attribute value and the second attribute value. When the first information is information that the user is predicted to pay attention to, such as the second type of information, the first capsule corresponds to the first attribute value, and the first attribute value indicates that the first capsule is displayed within a limited time. When the first information is information that the user indicates to pay attention to, such as the first type of information, the first capsule corresponds to the second attribute value, and the second attribute value indicates that the display time of the first capsule is not limited.

[0189] For example, a mobile phone instructs a smartwatch to push payment service information and then a taxi notification. The payment service information is the second type of target information, while the taxi notification is the first type of target information. The mobile phone sends a push notification 2 to the smartwatch, and the smartwatch responds to this push notification by using a transient capsule to push the payment service.

[0190] As an implementation method, the push notification 2 may carry an identifier representing the payment service information and an identifier representing the transient capsule. Accordingly, in response to the push notification 2 from the mobile phone, the smartwatch may recommend the user to use the payment service through the transient capsule.

[0191] The mobile phone sends a push notification 1 to the smartwatch. In response to this notification, the smartwatch uses a resident capsule to push the taxi notification. As an implementation, this push notification 1 can include the taxi notification and an identifier representing the resident capsule. Correspondingly, the smartwatch, in response to the push notification 1 from the mobile phone, can alert the user to the taxi notification through the resident capsule.

[0192] 2. The conditions for canceling the display are different.

[0193] For example, when a smartwatch displays a transient capsule, it can cancel the display of the transient capsule after the display duration of the transient capsule reaches a preset duration 2 (e.g., the first duration). Furthermore, before the display duration of the transient capsule reaches the preset duration 2, if the smartwatch detects a user operation on the transient capsule, it can also cancel the display of the transient capsule. If the user processes the target information corresponding to the transient capsule through the mobile phone, the smartwatch can also cancel the display of the transient capsule.

[0194] As shown in FIG12A , while the smartwatch is displaying watch face interface 1201, for example, at time T0, in response to push collaboration notification 2 from the mobile phone, capsule 1202 may be displayed. Capsule 1202 includes a payment service icon and a description of the payment service's functionality. When capsule 1202 is displayed for a predetermined duration 2 and no user action is taken on capsule 1202, for example, at time T3, the smartwatch stops displaying capsule 1202.

[0195] As shown in FIG12A , while the smartwatch is displaying watch face interface 1201, for example, at time T0, in response to a push notification 2 (also referred to as a payment service push notification) from a mobile phone, capsule 1202 may be displayed. Before capsule 1202 has been displayed for a predetermined duration 2, for example, at time T1, a user action on capsule 1202, such as clicking capsule 1202, is detected. The smartwatch may then display an application interface 1204 corresponding to the payment service (e.g., a third interface). This application interface 1204 provides payment-related services. After application interface 1204 is displayed, for example, at time T2, in response to a user instruction to exit (or return), for example, a second action, watch face interface 1201 is redisplayed. The redisplayed watch face interface 1201 does not contain capsule 1202.

[0196] In other embodiments, if the smart watch pushes the same target information through a transient capsule N times and no user operation on the transient capsule is detected, the smart watch will no longer display the transient capsule corresponding to the target information within a preset time interval, where N is a preconfigured positive integer.

[0197] In an exemplary scenario, N is 2, and the preset time interval is the time interval between the current time and midnight that evening. The smartwatch receives a first push notification 2 from the mobile phone. In response to this notification, the smartwatch pushes payment service information to the user using a transient capsule, such as displaying capsule 1202. While capsule 1202 is displayed, no user interaction with capsule 1202 is detected. After capsule 1202 has been displayed for a preset duration of 2, capsule 1202 is removed from display. Subsequently, the smartwatch receives a second push notification 2 from the mobile phone. In response, the smartwatch again pushes payment service information to the user using a transient capsule, such as displaying capsule 1202. While capsule 1202 is displayed again, no user interaction with capsule 1202 is detected. After capsule 1202 has been displayed for a preset duration of 2, capsule 1202 is again removed from display. In this scenario, the smartwatch has already pushed the payment service information twice using transient capsules, and no user interaction with the transient capsule has been detected. Correspondingly, the smartwatch will no longer push payment service information to the user via the transient capsule on that day. For example, if the smartwatch receives a third push notification 2 from the phone, it may not respond to it. For another example, if the smartwatch receives a third push notification 2 from the phone, it may respond to it and push payment service information to the user using other methods, such as displaying a service icon corresponding to the payment service information on the smart interface or the negative one screen.

[0198] As another example, if a resident capsule is displayed on the smartwatch, the smartwatch may continue to display it unless the user has made any action on the resident capsule. As shown in FIG12B , while the smartwatch is displaying watch face interface 1201, for example, at time T4, in response to a push notification 1 from the mobile phone, capsule 1203 may be displayed. Capsule 1203 contains key information about the taxi-hailing notification, such as taxi-hailing progress information. When capsule 1203 is displayed for a preset duration 2, for example, at time T7, the smartwatch continues to display capsule 1203.

[0199] When the smartwatch detects an operation on a resident capsule, it can cancel the display of the resident capsule. The operation on the resident capsule may include an operation of instructing to process the target information corresponding to the resident capsule.

[0200] As shown in FIG12B , while the smartwatch is displaying watch face interface 1201, for example, at time T4, in response to a push notification 1 (also referred to as a push notification for a taxi) from a mobile phone, capsule 1203 may be displayed. After displaying capsule 1203, for example, at time T5, if a user action on capsule 1203 is detected, such as a click on capsule 1203, the smartwatch may display a full-screen display interface 1205 corresponding to the taxi notification. This full-screen display interface 1205 may display the details of the taxi notification. After displaying full-screen display interface 1205, for example, at time T6, in response to a user exit (or return) action, watch face interface 1201 is re-displayed. The re-displayed watch face interface 1201 does not include capsule 1203.

[0201] The aforementioned operations on a resident capsule may also include an operation to instruct the resident capsule to be canceled. For example, while a resident capsule is displayed, the smartwatch may cancel the display of the resident capsule in response to a user operation. The operation to instruct the resident capsule to be canceled may be a swipe down operation, where the starting point of the swipe down operation is within the display space of the resident capsule, which may be referred to as a swipe down operation relative to the resident capsule.

[0202] Taking FIG. 13 as an example, while the smartwatch displays the dial interface 1201 including the capsule 1203 , in response to a user sliding down the dial interface 1203 , the capsule 1203 in the dial interface 1201 is canceled.

[0203] In some embodiments, when a mobile phone executes the same service, it may go through one or more service process nodes. At different service nodes, the mobile phone can instruct the smartwatch to push corresponding information. Among them, the one or more service process nodes include nodes marked as key and nodes marked as ordinary. For example, the taxi service includes process nodes such as matching with a suitable vehicle, the vehicle is about to or has arrived at the user-specified departure point, the passenger has boarded the vehicle, and the vehicle has arrived at the user-specified destination. Among them, matching with a suitable vehicle, the vehicle is about to or has arrived at the user-specified departure point can be pre-configured as key nodes, and the passenger has boarded the vehicle and the vehicle has arrived at the user-specified destination can be pre-configured as ordinary nodes.

[0204] During the taxi-hailing service, when a taxi-hailing notification corresponding to the "matched vehicle" node is pushed, the phone detects an instruction to cancel the push notification and can notify the smartwatch to cancel the display of the taxi-hailing notification corresponding to the "matched vehicle" node. Subsequently, in response to the service process entering a key node (i.e., the "vehicle is about to or has arrived at the user-specified departure location" node), the phone notifies the smartwatch to push the taxi-hailing notification related to the "vehicle is about to or has arrived at the user-specified departure location" node.

[0205] When pushing the taxi notification corresponding to the "Vehicle is about to or has arrived at the user-specified departure point" node, if the mobile phone detects an operation indicating cancellation of the push, it can notify the smartwatch to cancel the display of the taxi notification corresponding to the "Vehicle is about to or has arrived at the user-specified departure point" node. After that, the business process enters the normal node (that is, the "Passenger has boarded the vehicle" node), and the mobile phone does not display the taxi notification related to the "Passenger has boarded the vehicle" node, nor does it notify the smartwatch to push. If the user's instruction to cancel the push is not detected, the business process enters the normal node (that is, the "Passenger has boarded the vehicle" node), the mobile phone switches to displaying the taxi notification related to the "Passenger has boarded the vehicle" node, and notifies the smartwatch to push synchronously.

[0206] In one possible example, the smartwatch detects an action instructing to cancel push notifications and can cancel the display of the taxi notification corresponding to the "matched vehicle" node. Subsequently, when the phone instructs the smartwatch to push a taxi notification for a key node (i.e., the "vehicle is about to or has arrived at the user-specified departure location" node), the smartwatch will push the taxi notification associated with the "vehicle is about to or has arrived at the user-specified departure location" node.

[0207] When a taxi notification corresponding to the "Vehicle is about to or has arrived at the user's designated departure location" node is pushed, if the smartphone detects an instruction to cancel the push notification, it can cancel the display of the taxi notification corresponding to the "Vehicle is about to or has arrived at the user's designated departure location" node. Subsequently, when the smartphone instructs the smartwatch to push a taxi notification for a normal node (i.e., the "Passenger has boarded the vehicle" node), the smartwatch may not respond.

[0208] For example, when the smartwatch displays a resident capsule for pushing information 1, it responds to a user operation (an operation instructing to cancel the push) and cancels the resident capsule. During the process of executing the service corresponding to information 1, if the smartwatch is instructed to push information 2 of a common node of the service, the smartwatch will not respond to the instruction. If the smartwatch is instructed to push information 3 of a key node of the service, the smartwatch will respond to the instruction and display the resident capsule for pushing information 3.

[0209] In addition, if the user processes the target information using the mobile phone, he or she can also instruct the smart watch to cancel the display of the resident capsule corresponding to the target information.

[0210] 3. The display range of permanent capsules and transient capsules is different.

[0211] Among them, the above-mentioned permanent capsule can be displayed on all user interfaces of the smart watch, such as the AOD interface, the customized dial interface, the negative one screen, the smart interface, the application list interface (displaying the application icons of the applications installed in the smart watch), the notification bar interface, etc. When the smart watch displays any user interface, it can ensure that the first type of target information can reach the user efficiently.

[0212] The above-mentioned transient capsule can be displayed on one or more user interfaces, such as a smart interface, a negative one screen, and a customized dial interface. By limiting the user interface that can be displayed by the transient capsule, the second type of target information (that is, information that is inferred that the user needs to view, or information that is unimportant and non-urgent) can be reduced from causing excessive interference to the user. As shown in Figure 10B, if the mobile phone instructs the smart watch to push payment service information, the smart watch displays the dial interface 1005, and the smart watch can display a suspended capsule 1006 on the dial interface 1005, which is the access point for the payment service. If the mobile phone instructs the smart watch to push payment service information, the smart watch may not display the access point for the payment service when displaying the AOD interface, notification center interface, or dynamic notification pop-up window.

[0213] As shown in FIG14A , the smartwatch displays an AOD interface 1406. While displaying AOD interface 1406, the mobile phone instructs the smartwatch to push payment service information (fourth information). In response to the payment service information belonging to the second type of information, the smartwatch does not display a payment service push capsule on AOD interface 1406. Subsequently, the smartwatch responds to the user's operation by displaying a watch face interface 1407, on which a transient payment service push capsule 1408 may be displayed.

[0214] As shown in FIG10 , while the smart watch displays the AOD interface 1001 , the mobile phone instructs the smart watch to push a taxi notification (fifth information). In response to the taxi notification belonging to the first type of information, the smart watch displays a floating capsule 1002 for pushing the taxi notification on the AOD interface 1001 .

[0215] 4. Transient capsules can only provide an entry point for processing target information. Normal capsules not only provide an entry point for processing target information, but can also present part or all of the target information.

[0216] For example, as shown in Figure 12A, a transient capsule can display a small amount of text and a graphic logo. The graphic logo can be a dynamic image or a static image, without specific limitation. The small amount of text can be text that can represent the target information. For example, if the target information is an application, the text content displayed in the transient capsule can be the application name or main function name of the application.

[0217] Exemplarily, the persistent capsule can also display a graphical identifier. Different from the transient capsule, the persistent capsule can display more text content. Additionally, the text content displayed by the persistent capsule can be the key content corresponding to the pushed information.

[0218] In some embodiments, due to the limited display space of the persistent capsule, when there is a large amount of text content that needs to be displayed by the persistent capsule, the persistent capsule can scroll to display the text content.

[0219] As shown in FIG. 14B, during the display of the watch face interface 1401 on the smartwatch, in response to the push collaboration notification 1 from the mobile phone, the capsule 1402 is displayed, and this capsule 1402 is used to push a taxi notification. As shown in FIG. 14B, the capsule 1402 can display an icon 1403 indicating the taxi notification, and the key content corresponding to the taxi notification, such as the license plate information "Beijing A****5" and the trip reminder information "The driver has arrived", etc. When the capsule 1402 cannot display "Beijing A****5" and "The driver has arrived" simultaneously, the key content 1404 (such as the text "Beijing A****5") can be displayed first, and after an interval of a specified duration (such as 2 s), the key content 1405 (such as the text "The driver has arrived") is switched to be displayed. After displaying the key content 1405, after an interval of a specified duration, the key content 1404 is switched to be displayed again, and so on in a cycle.

[0220] In the above example, the taxi notification is the first information, "Beijing A****5" can be referred to as the first content, and "The driver has arrived" can be referred to as the second content.

[0221] It can be understood that in some embodiments, the transient capsule can also adopt a scrolling display method to display multiple pieces of text content. Specifically, refer to the persistent capsule, and details are not described herein again.

[0222] In other embodiments, when the smartwatch responds to the push collaboration notification and displays the corresponding persistent capsule or transient capsule, it can also use vibration to prompt the user to pay attention to the pushed target information.

[0223] In some embodiments, the smartwatch can also adopt multiple push forms to push the same target information.

[0224] Exemplarily, for the first type of target information, in addition to using the persistent capsule for pushing, the smartwatch can also adopt multiple push forms such as cards, dynamic full-screen pop-ups, icons, etc. to push this target information.

[0225] Taking the taxi notification as an example, as shown in FIG15 , while the smartwatch is displaying the watch face interface 1501, in response to the push collaborative notification 1 from the mobile phone, a full-screen pop-up window 1502 is displayed, such as the first pop-up window. After the duration of the full-screen pop-up window 1502 reaches a preset duration 3 (such as the third duration), or after detecting the user's instruction to cancel the display of the full-screen pop-up window 1502, the watch face interface 1504 is displayed.

[0226] As shown in Figure 15 , watch face interface 1504 displays a new capsule 1505 (the first capsule) compared to watch face interface 1501. When the taxi notification is of the first type of target information, capsule 1505 is a permanent capsule. Unless the user indicates to cancel the display of capsule 1505, the smartwatch may continue to display capsule 1505.

[0227] 15 , in response to the user clicking on capsule 1505, the smartwatch may display the full-screen pop-up window 1502 again. Before the user processes the taxi notification, the user may trigger the smartwatch to switch the push mode of the taxi notification between the full-screen pop-up window 1502 and the capsule 1505.

[0228] In some embodiments, as shown in FIG15 , a full-screen pop-up window 1502 includes a control 1503 for viewing the details of the taxi notification. In response to a user clicking control 1503, the smartwatch may also display a full-screen interface corresponding to the taxi notification, such as interface 1506. Interface 1506 includes the details of the taxi notification. After displaying the full-screen interface, it may be determined that the user has processed the taxi notification. Subsequently, in response to a user instruction to cancel display of interface 1506, the watch face interface 1501 may be displayed again, which may not include the capsule 1505.

[0229] In some embodiments, when a mobile phone executes the same service, it can instruct the smartwatch to push different targeted information at one or more service process nodes. For example, when a mobile phone executes an online taxi service, it can instruct the smartwatch to push corresponding taxi notifications at process nodes such as when a suitable vehicle is matched, when the vehicle is about to or has arrived at the user's designated departure location, when the passenger has boarded the vehicle, and when the vehicle has arrived at the user's designated destination.

[0230] In the process of executing a business process on a mobile phone, in the scenario where the target information to be pushed all belongs to the first type of information, the smartwatch responds to the instruction of the mobile phone and pushes the first target information related to the business. It can first use a dynamic full-screen pop-up window to push the target information, and then use a floating capsule to push the target information. The implementation details can be referred to in Figure 15 and will not be described here. Afterwards, when the smartwatch responds to the instruction of the mobile phone and pushes the i-th target information related to the business, it will no longer use a dynamic full-screen pop-up window to push the target information, but only use a floating capsule to push the target information. Wherein, the above i can be a positive integer greater than 1.

[0231] If after pushing the i-th target information related to the service, the smartwatch responds to the user's operation and cancels the display of the resident capsule used to push the target information. When the smartwatch responds to the phone's instruction to push the i+1-th target information related to the service, it can first push the target information using a dynamic full-screen pop-up window and then push the target information using a floating capsule.

[0232] As another example, for the second type of target information, in addition to using transient capsules for push, the smart watch can also use cards, icons and other push forms to push the target information.

[0233] In some embodiments, when a smartwatch uses multiple push forms to push target information, it can also use a deduplication strategy to avoid using multiple push forms (or so-called access points) in the same user interface to repeatedly recommend the same target information and interfere with the user.

[0234] As shown in Figure 16 , in response to a push notification from a mobile phone, the smartwatch displays capsule 1602 (referred to as the first capsule) on watch face interface 1601. Capsule 1602 is a portal to a taxi-hailing notification (referred to as the first message) and is also a normal capsule. In response to a user instruction to display the negative one screen (referred to as the third operation), the smartwatch may display negative one screen 1603 (referred to as the fourth interface). If card 1604 for pushing the taxi-hailing notification (referred to as the first card) is already displayed on negative one screen 1603, this card 1604 is also a portal to the taxi-hailing notification. In response to the inclusion of card 1604 in negative one screen 1603, the smartwatch may remove capsule 1602 from display, leaving only card 1604 as the portal to the taxi-hailing notification on negative one screen 1603. Furthermore, in response to the user's fourth operation, the smartwatch may switch to displaying another interface that does not contain a portal to the first message, such as returning to watch face interface 1601 (the second interface), and may display capsule 1602 again.

[0235] If the negative first screen 1603 does not contain the card corresponding to the taxi notification, but only contains the card 1605 corresponding to the express notification, the smart watch can continue to display the capsule 1602.

[0236] As shown in Figure 17, in response to a push notification from a mobile phone, the smartwatch displays capsule 1702 on watch face interface 1701. Capsule 1702 is a portal to a payment service (e.g., the first message) and is also a transient capsule. In response to a user instruction to display the negative first screen, the smartwatch may display negative first screen 1703. If negative first screen 1703 already displays an icon 1704 for pushing the payment service, e.g., the first icon, this icon 1704 is also a portal to the payment service. In response to the inclusion of icon 1704 in negative first screen 1703, the smartwatch may cancel the display of capsule 1702, retaining only icon 1704 as a portal to the payment service on negative first screen 1703. If negative first screen 1703 does not contain an icon corresponding to the payment service, the smartwatch may continue to display capsule 1702 until a user action on capsule 1702 is detected, or until the display duration of capsule 1702 reaches a preset duration 2.

[0237] In some embodiments, the mobile phone can sequentially instruct the smartwatch to display multiple target information. The multiple target information may include first type information, second type information, and third type information. The multiple target information may also include target information that needs to be pushed at different process nodes when the mobile phone executes the same service. The multiple target information may also include target information that needs to be pushed when the mobile phone executes different services.

[0238] When the smartwatch displays different target information in sequence, the corresponding resident capsule or transient capsule is displayed according to the last-come-first-served rule.

[0239] In some embodiments, after the smartwatch displays a first capsule for pushing a first message, it may, in response to an instruction from the mobile phone, cancel the display of the first capsule and then display a second capsule for pushing a second message. The time at which the instruction to push the second message is later than the time at which the instruction to push the first message is later than the time at which the instruction to push the first message is later than the time at which the instruction to push the second message is later than the time at which the instruction to push the first message is later. Based on the principle of last-in-first-out, the second capsule for pushing the second message may be displayed instead of the first capsule for pushing the first message.

[0240] If the push confidence of the second message is lower than that of the first message, for example, if the second message is of the second type and the first message is of the first type, after the second capsule is displayed for the second duration (preset duration 4), the first capsule is restored and the second capsule is canceled. For another example, if both the second and first messages are of the second type, and the push confidence of the second message is lower than that of the first message, the smartwatch displays the first capsule at time a, then cancels the first capsule at time b and displays the second capsule. The second capsule is then canceled at time c, where the time interval between time b and time c is the preset duration 4. If the time interval between time a and time c is less than the preset duration 2, the first capsule may be displayed again. At time d, the first capsule is canceled. The time interval between time d and time a is the preset duration 2. If the time interval between time a and time c is not less than the preset duration 2, the first capsule is no longer displayed.

[0241] If the push confidence of the second information is equal to that of the first information, or the difference is less than a set value, the first capsule will be canceled and will not be restored after it is displayed. If the push confidence of the second information is greater than that of the first information, the first capsule will be canceled and will not be restored after it is displayed. As shown in Figure 18, an example is taken in which a smartwatch first displays a permanent capsule in response to a mobile phone instruction, and then displays a transient capsule in response to the instruction. While the smartwatch is displaying watch face interface 1801, at time T8, in response to an instruction from the mobile phone (e.g., push collaborative information 3), capsule 1802 is displayed. Capsule 1802 is used to push a taxi notification, which belongs to the first type of target information. Accordingly, capsule 1802 is a permanent capsule. At time T9, in response to an instruction from the mobile phone (e.g., push collaborative notification 2), capsule 1803 is displayed. Capsule 1803 is used to push payment service information, which belongs to the second type of target information. Accordingly, capsule 1803 is a transient capsule.

[0242] When the display duration of capsule 1803 reaches a preset duration 4 (e.g., 10 seconds), for example, when the time reaches time T10 and the time interval between T10 and T9 is equal to the preset duration 4, the smartwatch may cancel the display of capsule 1803 and re-display capsule 1802. In some examples, the preset duration 4 may be equal to the preset duration 2. In other examples, the preset duration 4 may be shorter than the preset duration 2. This is not specifically limited in the present embodiment.

[0243] As shown in FIG19 , a smartwatch is taken as an example in which the smartwatch first displays a transient capsule in response to an instruction from a mobile phone, and then displays a normal capsule in response to the instruction.

[0244] While the smartwatch displays watch face interface 1901, at time T11, in response to an instruction from the mobile phone (e.g., "pushing collaborative information 2"), capsule 1902 is displayed. Capsule 1902 is used to push payment service information, which belongs to the second type of target information. Accordingly, capsule 1902 is a transient capsule. At time T12, in response to an instruction from the mobile phone (e.g., "pushing collaborative notification 1"), capsule 1903 is displayed. Capsule 1903 is used to push a taxi notification, which belongs to the first type of target information. Accordingly, capsule 1903 is a normal capsule. The time interval between T11 and T12 is less than a preset duration 2. Subsequently, at time T13, in response to a user instruction to cancel the display of capsule 1903, watch face interface 1901 may be displayed. Furthermore, even if the time interval between T11 and T13 is less than the preset duration 2, after capsule 1903 is canceled, watch face interface 1901 does not display capsule 1902.

[0245] As shown in Figure 20, while the smartwatch is displaying watch face interface 2001, at time T14, in response to an instruction from the mobile phone (e.g., pushing collaborative information 3), capsule 2002 is displayed. Capsule 2002 is used to push a taxi notification, which belongs to the first type of target information. Accordingly, capsule 2002 is a permanent capsule. At time T15, in response to an instruction from the mobile phone (e.g., pushing collaborative notification 5), capsule 2003 is displayed. Capsule 2003 is used to push an alarm reminder notification, which also belongs to the first type of information. Accordingly, capsule 2003 is a permanent capsule. At time T16, in response to an instruction from the mobile phone (e.g., pushing collaborative notification 2), capsule 2004 is displayed. Capsule 2004 is used to push payment service information, which belongs to the second type of target information. Accordingly, capsule 2004 is a transient capsule.

[0246] When the display duration of capsule 2004 reaches a preset duration of 4, for example, at time T17, where the time interval between T17 and T16 is equal to the preset duration of 4, the smartwatch may cancel the display of capsule 2004 and re-display capsule 2003. It is understood that both capsules 2003 and 2002 are permanent capsules, but capsule 2003 is displayed after capsule 2002. According to the last-in-first-out rule, after the transient capsule (capsule 2004) is canceled, the smartwatch displays capsule 2003.

[0247] As shown in Figures 18, 19, and 20, whether pushing the first or second type of information, the "later-arrived target information is displayed first" rule must be met. The difference is that in scenarios where a transient capsule is displayed before a regular capsule, the interrupted transient capsule will no longer be displayed after the permanent capsule is canceled. In scenarios where a permanent capsule is displayed before a transient capsule, the regular capsule can be restored after the transient capsule is canceled.

[0248] In other embodiments, the priority of target information corresponding to a specific type of service may be configured to be higher than that of other target information. For example, the priority of target information corresponding to call services and target information corresponding to alarm reminder services may be configured to be higher than that of other target information. During the period when the smartwatch is pushing target information corresponding to call services (or target information corresponding to alarm reminder services), if the mobile phone instructs the smartwatch to push other target information, the smartwatch may push other target information within a limited time (preset duration 4). After that, the target information corresponding to the above-mentioned call services (or target information corresponding to alarm reminder services) may continue to be pushed. Target information corresponding to multiple specific types of services may be pushed according to the last-in-first-out rule.

[0249] In some embodiments, when the target information is information representing real-time progress, such as download progress information, taxi notification, etc., if the content representing the progress in the target information (such as the progress value) changes, the status of the target information is not updated. If the progress value in the target information is replaced with an identifier indicating the end of the progress, the status of the target information is updated.

[0250] Taking download progress information as an example, as shown in Figure 21, the smartwatch displays a dial interface 2101 and, in response to instructions from the mobile phone, can display a capsule 2102. Capsule 2102 is a resident capsule used to push download progress information to the user. The download progress information includes a percentage value (i.e., a progress value) indicating the completion of the file download. Changes in the progress value in the download progress information do not trigger a status update of the download progress information.

[0251] For example, as shown in FIG. 21 , while the progress value in the download progress information changes from 0% to 100%, the status of the download progress information is not updated.

[0252] The progress value in the download progress information is replaced with an indicator indicating the end of the progress (e.g., the text content "File download completed"). As shown in FIG21 , capsule 2103 displays "File download completed," and the status of the download progress information is updated.

[0253] It is understandable that after the smartwatch cancels display of the suspended capsule for pushing target information, if the status of the target information is updated, the suspended capsule for pushing the target information may be displayed again.

[0254] For example, as shown in Figure 22, while the smartwatch is displaying watch face interface 2201, in response to an instruction from the phone (e.g., pushing collaborative message 5), capsule 2202 is displayed. Capsule 2202 is used to push download progress information. Subsequently, as the phone's actual file download progress changes, the smartwatch can be instructed to update the progress value displayed in capsule 2202. As shown in Figure 22, capsule 2202 can dynamically update from displaying "File downloaded 0%" to displaying "File downloaded 10%." Subsequently, in response to an instruction from the phone (e.g., pushing collaborative message 2), capsule 2202 is removed from display and capsule 2203 is displayed. Capsule 2203 is used to push a taxi notification and is a permanent capsule. While capsule 2203 is displayed, the phone's actual file download progress continues to change, and changes in the progress value do not update the status of the download progress information. In this way, the smartwatch continues to display capsule 2203 only when the progress value changes. When the mobile phone actually completes the file download, the progress value in the download progress information is replaced by an identifier indicating the end of the progress, and the status corresponding to the download progress information is updated. In response to the status update, the smart watch can cancel the display of capsule 2203 and display capsule 2204. Capsule 2204 and capsule 2202 are both resident capsules for pushing download progress information.

[0255] In the above example, the download progress information is the first information, and the taxi notification is the third information. The push time of the third information is later than the push time of the first information. Correspondingly, capsules 2202 and 2204 are the first capsules, and capsule 2203 is the third capsule.

[0256] In addition, when the target information is information that the user needs to grasp in real time, the smartwatch can identify the status update of the target information based on the real-time situation of the target information. Exemplarily, the target information that the user needs to grasp in real time may include information that needs to be pushed generated by the order information of each application (the creation of order information is related to user operations), such as flight notifications, express pickup information, high-speed rail notifications, taxi notifications, movie notifications, and real-time game status notifications. Correspondingly, the status capsule is shown in Figure 23. Exemplarily, the target information that the user needs to grasp in real time may also include information that needs to be pushed generated by the business information of each application (business information is related to the services provided by the application), such as call services, download progress information, timer notifications, alarm reminder notifications, sports health notifications, recording notifications, etc. Correspondingly, the status capsule is shown in Figure 23.

[0257] In other embodiments, tool services developed by electronic device manufacturers, such as microphone mode switching, media control, screen projection, etc., can also provide users with corresponding access entrances by displaying corresponding capsules. The specific details are not described in detail in the embodiments of this application.

[0258] An embodiment of the present application further provides an electronic device, which may include: a memory and one or more processors. The memory and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform the steps performed by the mobile phone in the above embodiment. Of course, the electronic device includes but is not limited to the above memory and one or more processors.

[0259] Wherein, the above-mentioned electronic device may include a wearable device. Taking the wearable device as a smart watch as an example, as shown in Figure 24, the above-mentioned smart watch includes a processor 110, a memory 120, a display screen 130, a sensor module 140 and a wireless communication module 150. The processor 110 may include one or more interfaces for connecting to other components of the smart watch. Wherein, the one or more interfaces may include: input / output (I / O) interface (also known as I / O pin), interrupt pin and data bus interface, etc. Wherein, the data bus interface may include: one or more of the interfaces such as serial peripheral interface (SPI), integrated circuit (inter-integrated circuit, I2C) interface, etc. For example, in an embodiment of the present application, the processor 110 can be connected to the sensor module 140 via an I / O pin, an interrupt pin or a data bus interface.

[0260] The memory 120 can be used to store program code, such as program code for wireless communication between the smartwatch and a mobile phone, and program code for UI display on the smartwatch. The processor 110 can be used to execute the above application code and call related modules to implement the functions of the smartwatch in the embodiments of the present application. For example, the smartwatch can implement UI display functions, motion monitoring functions, wireless communication functions, etc.

[0261] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. Different processing units may be independent devices or integrated into one or more processors 110.

[0262] The smartwatch implements its display functionality through a GPU, display 130, and an application processor. The GPU is a microprocessor for image processing that connects the display 130 and the application processor. The GPU is used to perform mathematical and geometric calculations and render graphics. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0263] The display screen 130 is used to display images, videos, and application interfaces. The display screen 130 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, or a quantum dot light-emitting diode (QLED).

[0264] Among them, the display screen 130 in the embodiment of the present application can be a touch screen. That is, a touch sensor is integrated in the display screen 130. The touch sensor can also be called a "touch panel". That is, the display screen 130 may include a display panel and a touch panel, and the touch sensor and the display screen 130 form a touch screen, also known as a "touch screen". The touch sensor is used to detect touch operations acting on or near it. After the touch operation is detected by the touch sensor, it can be passed to the upper layer by the driver of the kernel layer to determine the type of touch event. Visual output related to the touch operation can be provided by the display screen 130. In other embodiments, the touch sensor can also be set on the surface of the smart watch, at a different position from the display screen 130. In an optional embodiment, the touch sensor may include a screen capacitor, and the capacitance value of the screen capacitor may vary according to different pressures.

[0265] The sensor module 140 may include sensors such as an accelerometer and a gyroscope to monitor parameters such as the number of steps and exercise time of the user.

[0266] The wireless communication module 150 can support data exchange between smart watches and other smart watches through wireless communications including Bluetooth, global navigation satellite system (GNSS), wireless LAN, frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0267] It is understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on smart watches. They may have more or fewer components than those shown in FIG24 , may combine two or more components, or may have different component configurations. The various components shown in FIG24 may be implemented in hardware, including one or more signal processing or application-specific integrated circuits, software, or a combination of hardware and software.

[0268] The software system of the smartwatch can adopt a layered architecture, including an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the LiteOS™ system as an example to illustrate the software structure of the smartwatch. It should be understood that the system in the embodiment of the present application can also be other systems, such as the Android™ system, etc., and the present application does not limit this.

[0269] The present application also provides a chip system that can be applied to the smartwatch described in the aforementioned embodiment. The chip system includes at least one processor and at least one interface circuit. The processor can be the processor in the aforementioned smartwatch. The processor and the interface circuit can be interconnected via a circuit. The processor can receive and execute computer instructions from the memory of the aforementioned smartwatch via the interface circuit. When the computer instructions are executed by the processor, the smartwatch can perform the various steps performed by the mobile phone in the aforementioned embodiment. Of course, the chip system can also include other discrete components, which are not specifically limited in the present application.

[0270] In some embodiments, through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment and will not be repeated here.

[0271] The functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0272] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art 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 a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0273] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. An information push method, characterized in that: Applied to a wearable device, the method comprises: Displaying a first interface, where the first interface is a user interface of the wearable device; displaying a first capsule, where the first capsule is used to push first information; In response to a first operation by the user, the first interface is switched to display a second interface, the first capsule continues to be displayed, and the second interface is another user interface of the wearable device.

2. The method according to claim 1, characterized in that When the first information is information of a first type, the method further includes: after the wearable device displays the first capsule for a first duration, continuing to display the first capsule; in response to a user's operation on the first capsule, canceling the display of the first capsule; When the first information is information of the second type, the method further includes: after the wearable device displays the first capsule for a first duration, canceling display of the first capsule; The first type of information is different from the second type of information.

3. The method according to claim 2, characterized in that The first type of information includes information whose push confidence is greater than or equal to a preset value, and the second type of information includes information whose push confidence is less than the preset value. The push confidence is used to characterize the probability that the pushed information is the information that the user actually needs to view.

4. The method according to claim 2 or 3, characterized in that: The first type of information includes taxi notification information, navigation notification information, food delivery information, game information, and itinerary reminders; The second type of information includes access control service information, attendance reminder information, payment service information, subway service information, and express delivery pickup information.

5. The method according to claim 2, characterized in that: When the first information is information of the first type, the operation on the first capsule includes a click operation on the first capsule; after canceling the display of the first capsule, the method further includes: displaying a third interface, where the third interface is a user interface for processing the first information; A second operation of the user indicating exit is detected, the second interface is displayed again, and the first capsule is not displayed.

6. The method according to claim 2, characterized in that When the first information is information of the first type, the operation on the first capsule includes a sliding operation relative to the first capsule.

7. The method according to claim 1, characterized in that After the first interface switches to display the second interface in response to the first operation of the user, the method further includes: In response to a third operation of the user, displaying a fourth interface, wherein the fourth interface includes a first card or a first icon for pushing the first information; canceling display of the first capsule; In response to a fourth operation of the user, the second interface is displayed again, and the first capsule is displayed again.

8. The method according to claim 1, characterized in that: In the case where the first information is information of the first type, after displaying the first capsule, the method further includes: Displaying a second capsule, and canceling displaying the first capsule, wherein the second capsule is used to push second information, the push confidence of the second information is lower than the push confidence of the first information, the push confidence is used to represent the probability that the pushed information is information that the user actually needs to view, and the push time point of the second information is later than that of the first information; After the wearable device displays the second capsule for a second time period, the second capsule is canceled and the first capsule is displayed again.

9. The method according to claim 1, characterized in that: When the first information is information of the first type, after displaying the first capsule, the method further includes: A third capsule is displayed, and the first capsule is canceled, wherein the third capsule is used to push third information, the third information is also the first type of information, and the pushing time point of the third information is later than the pushing time point of the first information.

10. The method according to claim 9, characterized in that The method further comprises: In response to the status update of the first information, the third capsule is canceled from being displayed, and the first capsule is displayed again.

11. The method according to claim 10, characterized in that The first information includes progress information updated in real time, and the method further includes: in response to the progress information being updated to progress completion, determining a status update of the first information.

12. The method according to any one of claims 1 to 11, characterized in that: The first information includes first content and second content, and the first capsule is used to scroll and display the first content and the second content.

13. The method according to any one of claims 1 to 12, characterized in that: The wearable device is communicatively connected with the first device, and before displaying the first capsule, the method further includes: receiving a first indication from the first device, where the first indication includes an identifier representing pushing the first information and a display attribute corresponding to the first capsule; When the first information is information of the second type, the first capsule corresponds to a first attribute value; when the first information is information of the first type, the first capsule corresponds to a second attribute value, the first attribute value indicates that the first capsule is displayed within a limited time, and the second attribute value indicates that the display time of the first capsule is not limited.

14. The method according to any one of claims 1 to 13, characterized in that: Before displaying the first capsule, the method further includes: Display a first pop-up window, where the first pop-up window is used to push the first information; After the first pop-up window is displayed for a third time period, the first pop-up window is canceled.

15. The method according to claim 1 or 2, characterized in that: The wearable device is communicatively connected with the first device, and before displaying the first capsule, the method further includes: receiving a first indication from the first device for the Nth time, the first indication including an identifier representing the push of the first information; wherein N is a preset positive integer, and the first information is information of the second type; displaying the first capsule includes: displaying the first capsule in response to the first indication for the Nth time; After the first capsule is displayed for a first time period, canceling the display of the first capsule; During the first N times of displaying the first capsule, if no operation of the first capsule by the user is detected, the method further includes: receiving the first instruction for the N+1th time; The first capsule is not shown.

16. The method according to claim 2, characterized in that The method further comprises: In response to user operations, the AOD interface is displayed; receiving an instruction to push fourth information, and not displaying a capsule for pushing the fourth information, the fourth information being information of the second type; In response to a user operation, the AOD interface switches to display a dial interface, the dial interface displays a fourth capsule, and the fourth capsule is used to push the fourth information; In response to user operations, the screen-off display interface is displayed again; In response to fifth information, a fifth capsule for pushing the fifth information is displayed, the fifth information being information of the first type.

17. An information push method, characterized in that: Applied to a first device and a wearable device communicating with each other, the method comprises: The first device displays a card or a capsule for pushing the first information, and the wearable device displays a first interface, where the first interface is any user interface of the wearable device; The first device sends a first indication to the wearable device, where the first indication corresponds to the first information; The wearable device displays a first capsule in response to the first indication, where the first capsule is used to push the first information; In response to a first operation of a user, the wearable device switches from the first interface to display a second interface, and continues to display the first capsule.

18. A wearable device, characterized in that: The wearable device includes: a display screen, a processor and a memory, wherein the memory is used to store computer instructions, and the display screen is used to push information to a user. When the processor executes the computer instructions, the wearable device executes the method as described in any one of claims 1-16.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium comprises a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 16.

Images