Display control method, electronic equipment and computer readable storage medium

Abstract

The invention provides a display control method, electronic equipment and a computer readable storage medium, and relates to the technical field of terminals. In order to solve the technical problem that viewing operation of related data of application services is tedious, the electronic equipment calls multiple notification entries to display the application services, such as a desktop, a negative one screen, a fast application center, a notification center, a control center, a status bar, a lock screen interface and a continuous display AOD interface. And the electronic equipment determines a target notification entry for displaying the service information for the application service, and in response to different operations, the service information of the first application service is displayed when corresponding entry interfaces are displayed at different target notification entries. And the electronic equipment displays the service information of the on-going application service on the entrance interfaces of the plurality of notification entrances so as to form a prompt effect of touching a user on multiple interfaces. The electronic equipment simplifies the operation of checking the order information by the user, and improves the user experience.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of terminals, and in particular, to a display control method, an electronic device, and a computer-readable storage medium. Background Art

[0002] Smartphones are becoming more and more powerful, providing users with services such as hailing a taxi, ordering takeout, booking train tickets, flights, watching movies, etc. Different applications are installed in the mobile phone, and different applications provide different services. After a taxi-hailing application on the mobile phone starts a taxi-hailing order, the progress of the taxi-hailing order is displayed in the interface of the taxi-hailing application. Similarly, when the takeout application on the mobile phone starts a takeout order, the progress of the takeout order is displayed in the display interface of the takeout application.

[0003] There are many types of applications that can provide services on the mobile phone, and the services provided by various applications are also relatively numerous. Different services may have different service statuses. The service status of each service is only displayed in the corresponding application interface, and the display reach effect is poor. Summary of the Invention

[0004] The embodiments of the present application provide a display control method, an electronic device, and a computer-readable storage medium, which are used to solve the technical problem that the display reach effect of the service progress of the applications provided by the existing mobile phone is poor.

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

[0006] In a first aspect, a display control method is provided and applied to an electronic device. The electronic device includes multiple notification entrances, such as the desktop, the negative first screen, the quick application center, the notification center, the control center, the status bar, the lock screen interface, and the AOD interface, etc. The electronic device is installed with a first application program. On the first interface of the first application program, the electronic device can receive a first operation of the user and generate a first application service. The electronic device can also display an indication information indicating that the first application has been started.

[0007] One or more devices are externally connected to the electronic device, such as a watch or a car machine connected to the mobile phone. The electronic device can determine a target device corresponding to the first application service from the externally connected one or more devices. The electronic device sends the service information of the first application service to the target device, so that the service information of the first application service is displayed on the entrance interface of the notification entrance of the target device. In this way, whether the user is using the electronic device or the externally connected target device, the service information of the first application service can be viewed in a timely manner, and the latest dynamics of the order can be grasped.

[0008] The electronic device generates a first application service and determines a target notification entry corresponding to the first application service from all provided notification entries. The electronic device determines at least two different target notification entries for the first application service, including a first notification entry and a second notification entry. For example, the first notification entry can be the negative first screen, and the second notification entry can be the lock screen interface.

[0009] The electronic device can receive a user's operation and switch to the notification entry of the local device or the notification entry of the target device to display the service information of the first application service. During the operation of the first application service, if the switched notification entry is the target notification entry corresponding to the first application service, the service information of the first application service is displayed on the entry interface of this target notification entry. The service information displayed by the electronic device can include corresponding service data and service status.

[0010] In one case, the electronic device receives a second operation from the user, and the electronic device sends the service information of the first application service to the target device, and the target device displays the service information of the first application service.

[0011] In another case, the electronic device receives a third operation from the user, and the service information of the first application service is displayed on the target notification entry of the electronic device. The second operation and the third operation responded by the electronic device can be the same operation or different operations.

[0012] During the operation of the first application service, the electronic device has the ability to display the service information of the first application service on different target notification entries successively, which does not limit that the electronic device will display the service information of the first application service on different target notification entries.

[0013] For example, during the operation of the first application service, the electronic device can only display the second interface corresponding to the first notification entry. Or, the electronic device can also only display the third interface corresponding to the second notification entry. Or, the electronic device can first display the second interface corresponding to the first notification entry and then display the third interface corresponding to the second notification entry. Or, the electronic device can first display the third interface corresponding to the second notification entry and then display the second interface corresponding to the first notification entry, without limitation.

[0014] For the display control method provided in this embodiment, the electronic device displays the service information of the ongoing application service on the entry interfaces of multiple notification entries to form a prompt effect of reaching the user on multiple interfaces. The electronic device simplifies the operation of the user to view order information and improves the user experience.

[0015] In a specific implementation of the first aspect, the electronic device matches the corresponding target device and target notification entry according to the importance and urgency level of the first application service. The importance and urgency levels of different application services are different, and the corresponding display and reach requirements are also different. The electronic device can display the service information of different application services through different target devices and notification entries.

[0016] After the electronic device generates the first application service, it can obtain the importance and urgency level of the first application service. The importance and urgency level can be used to indicate the importance degree and / or urgency degree of the first application service. The electronic device can rely on the intention prediction model on the intelligent side to obtain the importance and urgency level of the first application service, or can calculate the importance and urgency level of the first application service through other relevant algorithms.

[0017] The electronic device determines the importance and urgency level of the first application service, determines the target device and target notification entry corresponding to the first application service from all the notification entries that the electronic device can provide, and then displays the service information of the first application service through the notification entries of the selected target devices and the target notification entry of the electronic device.

[0018] There will be updates to the service information and service status of the first application service generated by the electronic device. During the operation of the first application service, the electronic device needs to update the displayed service information according to the updates of the service information and service status.

[0019] In a specific implementation, the electronic device can adjust the corresponding display control scheme according to the service status update. The first application service has multiple service statuses, and the corresponding importance and urgency levels of different service statuses may be different. During the operation of the first application service, the service status will change, and the importance and urgency level of the first application service will also change. The electronic device can determine the current importance and urgency degree corresponding to the current service status according to the current service status at different time periods during the operation of the first application service, and then determine the current corresponding target notification entry according to the importance and urgency degree of the current service status.

[0020] During the operation of the first application service, the service status of the first application service obtained by the electronic device may sequentially include a first service status and a second service status. The first service status is the service status in the first time period, and the second service status is the service status in the second time period. The second time period is a time period after the first time period.

[0021] In the first time period, the electronic device determines the first importance and urgency level corresponding to the first service status according to the first service status in which the first application service is currently located, and determines the target device and target notification entry currently corresponding to the first application service according to the first importance and urgency level.

[0022] In the second time period, in response to the update of the service status of the first application service, the electronic device determines the second importance and urgency level corresponding to the second service status according to the updated second service status of the first application service, and updates the target device and the target notification entry corresponding to the first application service according to the second importance and urgency level corresponding to the second service status. The target notification entry corresponding to the first service status may be the same as or different from the target device and the target notification entry corresponding to the second service status.

[0023] During the operation of the first application service, the electronic device can re-determine the current importance and urgency level and the target device and the target notification entry corresponding to the importance and urgency level each time the service status of the first application service is updated, and display the current service information of the first application service on the entry interface of the current corresponding target device and the notification entry and the target notification entry. In this way, the electronic device can switch the matching display control scheme according to the display reach requirements of different service statuses, further optimize the display reach effect, and improve the user experience.

[0024] In another specific implementation manner, the electronic device can adjust the corresponding display control scheme according to the update of the service information. The electronic device can obtain the action of the update of the service information of the first application service. The action can be actively notified by the first application program that generates the first application service, or the electronic device can actively query and obtain it according to the pre-set update frequency.

[0025] In response to the update of the service information of the first application service, the electronic device sends the service information of the first application service and the view file corresponding to the first display form to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service in the first display form. The electronic device can also display the updated service information of the first application service on the entry interface of the target notification entry corresponding to the current service status.

[0026] In this way, the electronic device displays the latest service information on the entry interfaces of the target notification entry and the notification entry of the target device, facilitating the user to timely grasp the latest service status of the order.

[0027] In a specific implementation manner of the first aspect, the electronic device displays the service information of the first application service on the entry interfaces of the target notification entry and the notification entry of the target device, and can also display it in different display forms. The display forms supported by the entry interface of the notification entry may include at least one of a card, a capsule, and a banner. The electronic device can match the target display form for the first application service, and display the service information of the first application service in the target display form on the entry interfaces of the respective target notification entries after determining the respective target notification entries.

[0028] The electronic device determines multiple target notification entrances for the first application service, and can match different display forms to different notification entrances. For example, the electronic device determines a first display form corresponding to the notification entrance of the target device and a second display form corresponding to the target notification entrance.

[0029] The electronic device sends the service information of the first application service to the target device, and the watch displays the service information of the first application service in the first display form. The electronic device displays the service information of the first application service in the target notification entrance in the second display form.

[0030] Electronic devices have added various display forms such as cards, capsules, banners, etc. to enrich the display effect of business information of the first application business and further enhance the user experience.

[0031] In a specific implementation of the first aspect, the electronic device adds a scheme for determining the target display form. In this implementation, the electronic device determines the target display form corresponding to the first application service based on the first application program that generates the first application service, and then displays the service information of the first application service in the target display form.

[0032] Each first application installed on the electronic device can determine in which display form the business information of the first application service generated by it will be displayed when it is displayed on the entry interface of each notification entry. When the application is installed on the electronic device, one or more supported display forms can be registered at the same time. In this way, the application can also generate a view file of the corresponding display form based on the business information of the application service, and provide it to the notification entry to display the business information in the display form.

[0033] When generating the first application service, the electronic device searches for the display form previously registered by the first application program generating the first application service, and uses the searched display form as the target display form corresponding to the first application service.

[0034] In a specific implementation of the first aspect, the scheme for the electronic device to determine the target display form is further limited. In this embodiment, the electronic device comprehensively determines the target display form associated with the first application service by referring to the application program and the notification portal.

[0035] Each notification portal provided by the electronic device can also register the supported display forms in advance. For example, each time the electronic device is turned on, the notification portal initiates a registration application to apply for permission to obtain business information and display it on the portal interface. Each notification portal can correspond to one or more display forms.

[0036] Specifically, the electronic device obtains one or more display forms corresponding to the first application, one or more display forms corresponding to the target notification entry, and one or more display forms corresponding to the target device. The electronic device uses the same display forms among the one or more display forms corresponding to the first application and the one or more display forms corresponding to the target device as the first display form. Further, the electronic device uses the same display forms among the one or more display forms corresponding to the first application and the one or more display forms corresponding to the target notification entry as the second display form.

[0037] In a specific implementation of the first aspect, a display control solution is added after the electronic device and the target device are disconnected and then reconnected. After the electronic device and the target device are disconnected, the target device may send a full push request to the electronic device. The electronic device may send full service information to the target device in response to the reconnection after the disconnection between the electronic device and the target device. The full service information is used for the target device to adjust the service information displayed on the entry interface of the second type of system entry; the full service information includes the service information of all the application services currently enabled in the electronic device.

[0038] Specifically, if the full service information includes the service information of the first application service, the target device will update the service information of the first application service to be updated and displayed on the entry interface of the second type of system entry.

[0039] If the full service information does not include the service information of the first application service, the target device will stop displaying the service information of the first application service on the entry interface of the second type of system entry.

[0040] If the full service information newly adds the service information of the second application service, the target device will also newly display the service information of the second application service on the entry interface of the second type of system entry.

[0041] In a specific implementation of the first aspect, the electronic device looks up the target notification entry and the target device corresponding to the important and urgent level of the first application service based on the entry mapping table. The electronic device pre-maintains an entry mapping table, which includes different mapping relationships between the important and urgent levels of application services and notification entries and devices.

[0042] The entry mapping table stored in the electronic device can be a system default mapping table, or a user-defined mapping table, or a mapping table selected by the user from multiple mapping tables provided by the system.

[0043] The electronic device determines the current important and urgent level corresponding to the current service state of the first application service, and searches in the pre-defined entry mapping table for the notification entry and device corresponding to the current important and urgent level of the first application service, as the current corresponding target notification entry and target device.

[0044] Generally speaking, the higher the important and urgent level, the more target notification entries are determined, and the stronger the display reach effect. The electronic device selects the notification entry for displaying service information according to the important and urgent level of the application service, and the display effect adaptability is better, which better meets the user's needs.

[0045] In another specific implementation manner of the first aspect, when the electronic device finds the notification entry corresponding to the current important and urgent level in the entry mapping table according to the important and urgent level of the first application service, it will also determine whether the notification entry corresponding to the important and urgent level of the first application service has been registered beforehand, so as to verify whether the notification entry corresponding to the current important and urgent level has the ability to display service information.

[0046] If the electronic device determines that the notification entry corresponding to the important and urgent level of the first application service has initiated a registration application, it takes the notification entry corresponding to the important and urgent level of the first application service as the target notification entry, and calls the target notification entry to display the service information of the first application service.

[0047] If the electronic device determines that the notification entry corresponding to the important and urgent level of the first application service has not initiated a registration application, it will not take the notification entry corresponding to the important and urgent level of the first application service as the target notification entry, and will not call the notification entry to display the service information of the first application service subsequently.

[0048] In a specific implementation manner of the first aspect, the electronic device has also added a solution to stop displaying service information. The electronic device can obtain an indication that the first application service has ended. The indication that the first application service has ended can be actively sent by the first application program that generates the first application service, or can be actively queried and obtained by the electronic device according to the pre-set update frequency.

[0049] In response to the end of the first application service, the electronic device stops displaying the service information of the first application service at the target notification entry to timely remind the user that the first application service has ended. In addition, the electronic device can also send an indication message to stop displaying to the target device, so that the target device stops displaying the service information of the first application service.

[0050] In summary, in the display control method provided in the embodiments of the present application, during the process of the first application generating the operation of the first application service, the electronic device can display the service information of the latest first application service in different display forms on the notification entry of the target device and the entry interface of the target notification entry of the electronic device respectively. The electronic device promptly displays the latest service information on each entry interface of the electronic device, so that the service information can reach the user as much as possible, simplifies the cumbersome operation of the user to view information, and greatly improves the user experience.

[0051] In a second aspect, the present application provides a display control method, which is applied to a first device, and the first device can be the target device described in any one of the first aspect. The first device establishes a communication connection with the electronic device.

[0052] The first device receives the service information of the first application service sent by the first device; wherein, the first application service is generated by the first application program of the electronic device. The first device, in response to a fourth operation, displays the service information of the first application service on the entry interface of the notification entry of the first device.

[0053] In a specific implementation manner of the second aspect, the notification entry of the first device includes at least one of a desktop, a negative first screen, a quick application center, a notification center, a control center, a global, a lock screen interface, and a continuous display AOD interface.

[0054] In a specific implementation manner of the second aspect, the first device can display the updated service information of the first application service in response to the updated service information of the first application service sent by the electronic device.

[0055] In a specific implementation manner of the second aspect, the first device can also receive the indication information sent by the electronic device to stop displaying, and stop displaying the service information of the first application service on the entry interface of the notification entry of the target device.

[0056] In a specific implementation manner of the second aspect, the first device can also, in response to the restoration of the connection after the first device is disconnected from the electronic device, send a full-volume service push request to the electronic device;

[0057] Receive the full-volume service information sent by the electronic device, and update the service information displayed on the entry interface of the notification entry of the first device entry according to the full-volume service information; wherein, the full-volume service information is the service information of all the application services currently enabled in the electronic device.

[0058] In a specific implementation of the second aspect, if the full volume of service information includes the service information of the first application service, the first device may also update the service information of the first application service displayed on the entry interface of the notification entry of the first device;

[0059] If the full volume of service information does not include the service information of the first application service, the first device may also stop displaying the service information of the first application service on the entry interface of the notification entry of the first device.

[0060] In a specific implementation of the second aspect, the first device may be a wearable device, and the wearable device includes a smart watch.

[0061] In a third aspect, the present application provides an electronic device, which includes a display, a memory, and a processor, and both the display and the memory are coupled to the processor;

[0062] The memory stores computer-executable instructions;

[0063] The processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the display control method according to any one of the first aspect, or the display control method according to any one of the second aspect.

[0064] In a fourth aspect, a control device is provided, and the control device can execute the display control method according to any one of the first aspect, or the display control method according to any one of the second aspect.

[0065] In a fifth aspect, an electronic device is provided, and the electronic device has the function of implementing the display control method of the above-mentioned first aspect or second aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0066] In a sixth aspect, an electronic device is provided, including: a processor and a memory; the memory is used to store computer-executable instructions, and when the electronic device runs, the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the display control method according to any one of the above-mentioned first aspect, or the display control method according to any one of the second aspect.

[0067] In a seventh aspect, a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium. When it runs on a computer, the computer can execute the display control method according to any one of the first aspect, or the display control method according to any one of the second aspect.

[0068] In an eighth aspect, there is provided a computer program product including instructions which, when running on a computer, enable the computer to execute the display control method according to any one of the above first aspects or the display control method according to any one of the second aspects.

[0069] Among them, for the technical effects brought by any one of the design manners in the second aspect to the eighth aspect, reference may be made to the technical effects brought by different design manners in the first aspect, which will not be elaborated here. Description of the Drawings

[0070] Figure 1 It is a schematic diagram of the interface of a mobile phone;

[0071] Figure 2 It is a schematic flowchart of the display control method provided by an embodiment of the present application;

[0072] Figure 3 It is a partial interface diagram of a mobile phone provided by an embodiment of the present application for displaying service information at multiple target notification entrances;

[0073] Figure 4 It is another partial interface diagram of a mobile phone provided by an embodiment of the present application for displaying service information at multiple target notification entrances;

[0074] Figure 5 It is another schematic flowchart of the display control method provided by an embodiment of the present application;

[0075] Figure 6 It is a schematic diagram of the process of a mobile phone provided by an embodiment of the present application for executing the display control method;

[0076] Figure 7 It is a schematic diagram of the software framework of a mobile phone provided by an embodiment of the present application;

[0077] Figure 8 It is a schematic flowchart of the display control method executed based on the software framework provided by an embodiment of the present application;

[0078] Figure 9 It is a general schematic diagram of the software framework for implementing the display control method provided by an embodiment of the present application;

[0079] Figure 10 It is a schematic diagram of the software framework of an electronic device corresponding to the Widget architecture provided by an embodiment of the present application;

[0080] Figure 11 It is a schematic flowchart of the display control method executed based on the Widget architecture by an electronic device provided by an embodiment of the present application;

[0081] Figure 12 It is another schematic flowchart of the display control method executed based on the Widget architecture by an electronic device provided by an embodiment of the present application;

[0082] Figure 13 Schematic flow diagram of the notification entry registration operation involved in the display control method provided by the embodiment of the present application;

[0083] Figure 14 Schematic flow diagram of the process of displaying the Widget card at the notification entry involved in the display control method provided by the embodiment of the present application;

[0084] Figure 15 Schematic flow diagram of the process of displaying updated service information at the notification entry involved in the display control method provided by the embodiment of the present application;

[0085] Figure 16 Schematic flow diagram of the process of automatically updating the display of the Widget card by the interactive display framework involved in the display control method provided by the embodiment of the present application;

[0086] Figure 17 Schematic flow diagram of the process of simultaneously transmitting the view files of the capsule and the card involved in the display control method provided by the embodiment of the present application;

[0087] Figure 18 Interface schematic diagram of the capsule and the card involved in the display control method provided by the embodiment of the present application;

[0088] Figure 19 Schematic flow diagram of the process of the electronic device simultaneously transmitting the view files of the capsule and the card data provided by the embodiment of the present application;

[0089] Figure 20 Schematic diagram of the interaction between the mobile phone and the smartwatch involved in the display control method provided by the embodiment of the present application;

[0090] Figure 21 Schematic diagram of the interaction between the mobile phone and the smartwatch and the in-vehicle infotainment system respectively involved in the display control method provided by the embodiment of the present application;

[0091] Figure 22 Schematic diagram of the connection between the mobile phone and the smartwatch involved in the display control method provided by the embodiment of the present application;

[0092] Figure 23 Schematic flow diagram of the process of the mobile phone transmitting service information to an external device involved in the display control method provided by the embodiment of the present application;

[0093] Figure 24 Schematic diagram of the mobile phone supporting multi-device transmission display involved in the display control method provided by the embodiment of the present application;

[0094] Figure 25 Schematic flow diagram of the process of transmitting service information to an external device involved in the display control method provided by the embodiment of the present application;

[0095] Figure 26 The flowchart of the process for pushing full information involved in the display control method provided by the embodiments of this application;

[0096] Figure 27 The hardware structure diagram of the electronic device provided by the embodiments of this application. Detailed implementation manners

[0097] The following describes exemplary embodiments of this application with reference to the accompanying drawings. Various details of the embodiments of this application are included to facilitate understanding, and they should be considered merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, descriptions of well-known functions and structures are omitted below for clarity and conciseness.

[0098] For ease of understanding, some common technical knowledge related to the embodiments of this application is introduced first.

[0099] Various application programs can be installed in an electronic device (such as a mobile phone) to implement different application services. The application programs installed on the mobile phone can include system applications and third-party applications. System applications such as calls and alarms, and third-party applications such as taxi-hailing applications and shopping applications. The desktop interface of the mobile phone displays the icons of each application program. After the mobile phone receives a click operation on the icon of a certain application program on the desktop, it can enter the corresponding application program and display the application interface of the application program to the user.

[0100] As Figure 1 shown, it is a schematic diagram of the mobile phone interface. As Figure 1 shown in (a) therein, the mobile phone can display the icons corresponding to each application program on the desktop. For example, the icon of the taxi-hailing application (such as Figure 1 101 shown in (a) therein). If the icon of the taxi-hailing application on the desktop receives a click operation by the user, it enters the taxi-hailing application interface as shown in Figure 1 shown in (b) therein. A taxi-hailing requirement input box is displayed on the taxi-hailing application interface. The user can input or select taxi-hailing requirements, such as information on the departure place, destination, vehicle type, etc., and click on the "Confirm to hail a taxi" control (such as Figure 1 102 shown in (b) therein) to initiate a taxi-hailing order. The taxi-hailing application will enter the taxi-hailing application interface as shown in Figure 1 shown in (c) therein, and the order status of the taxi-hailing order will be displayed on the interface and continuously updated, including the order receiving status, driver arrival status, trip status, etc. of the taxi-hailing order.

[0101] During the entire process of the taxi-hailing order, the user can exit the taxi-hailing application interface and click to enter the application interface of other application programs on the mobile phone, or the user can also lock the screen of the mobile phone. AsFigure 1 As shown in (d) of , during the process of a taxi-hailing order, the user exits the taxi-hailing application interface and locks the screen. The mobile phone does not display the order status of the taxi-hailing application on the locked screen, so that the user cannot obtain the real-time status of the taxi-hailing order in a timely manner. If the user wants to obtain the real-time status of the taxi-hailing order, they need to unlock the mobile phone and enter the taxi-hailing application interface again to view the real-time status and progress of the taxi-hailing order. That is to say, in the existing display control scheme, the operations that need to be performed by the user are relatively cumbersome, and the user experience is poor.

[0102] Based on this, the embodiments of the present application provide a display control method, which is applied to an electronic device. The electronic device provides a display scheme for displaying relevant data of an application service on an entry interface of multiple notification entries for the application services generated by various application programs. Compared with the scheme of only displaying service data through an application interface, the display control method provided by the embodiments of the present application realizes the synchronous display of service data on the interfaces of multiple notification entries. The display effect is more intuitive, and the service data can be presented to the user without receiving many user operations, simplifying the operations for the user to view the application service and improving the user experience.

[0103] The electronic device to which the embodiments of the present application are applied may include an electronic device with a touch screen such as a personal computer (PC), a tablet computer, a laptop computer, a portable computer (such as a mobile phone), a wearable electronic device (such as a smart watch), an augmented reality (AR) / virtual reality (VR) device, an in-vehicle computer, etc. The following embodiments do not make special restrictions on the specific form of the electronic device. For ease of description, the embodiments of the present application mainly use a mobile phone as an example to explain the specific implementation manner of the electronic device executing the display control method.

[0104] Embodiment 1

[0105] As shown in Figure 2 , the flowchart of the display control method provided by the embodiments of the present application is shown. The provided display control method mainly includes the following processes:

[0106] S201: In response to a first operation on a first interface of a first application program, display an indication information of a first application service of the first application program.

[0107] A first application program is installed on the mobile phone. The first application program can receive a first operation from the user, generate a first application service, and the mobile phone can display the indication information of the generated first application service.

[0108] The first application program involved in this embodiment may be a system application, a third-party application, a quick application, a small program application carried on a third-party application, etc. installed on the mobile phone.

[0109] The first application service involved in this embodiment can be understood as an application order initiated by a first application program on a mobile phone and requiring continuous operation for a certain period of time to complete. The application order can be a consumption order involving a payment transaction or a task order not involving a payment transaction.

[0110] In one example, the first application program can be a taxi-hailing application, and the first interface of the first application program can be the application interface of the taxi-hailing application. When the mobile phone receives the first operation of the user, a consumption order for the taxi-hailing service is generated. The consumption order for the taxi-hailing service is an application order that requires continuous operation for a certain period of time and can be used as a first application service. Similarly, the first application program can also be a food delivery application, a courier application, etc.

[0111] In another example, the first application program can be an alarm clock or a stopwatch. The alarm clock or the stopwatch receives the click operation of the user and generates a timing service for an alarm reminder or a countdown. The timing service does not involve a payment transaction but still requires continuous operation for a certain period of time to complete, and the timing service can also be used as an application service. The first application program can also be a sports event result broadcast application, a flight dynamic reminder application, a smart home control application, a flight itinerary application, a train itinerary application, etc.

[0112] An application program can initiate multiple different application services simultaneously. For example, a taxi-hailing application can initiate two different taxi-hailing services simultaneously. One taxi-hailing service is to take a taxi from place A to place B, and the other taxi-hailing service is to take a taxi from place C to place D. Considering that different application services correspond to different user needs, that is, different application services are usually not related to each other and have their own display and touch requirements. To achieve a better display effect, in the embodiment of the present application, the mobile phone uses a single application service as a processing object for the display control method. If the same application program initiates two application services respectively, the mobile phone can execute the corresponding display control methods for these two application services respectively.

[0113] In addition, each application service involves multiple types of service information, which can be mainly divided into service data and service status. Among them, the service data provided by the mobile phone can be data related to the current application service and needs to be displayed to the user, and the service status of the application service provided by the mobile phone can be information used to indicate the relevant status of the current application service.

[0114] In one example, the first application service is a taxi-hailing service. Information such as the current queuing number, driver vehicle information and personal information, the distance between the current vehicle position and the passenger pick-up point, navigation route, distance to the destination, estimated arrival time, and estimated taxi fare provided by the mobile phone belongs to business data. Information corresponding to the order status of the taxi-hailing service, such as queuing, waiting for the driver to arrive, the driver has arrived, the passenger has boarded, and the destination has been reached, provided by the mobile phone belongs to business status.

[0115] When each first application program starts a new first application service, it can create a business process corresponding to the first application service. The first business process starts when the first application service is created and ends when the first application service ends. During the existence of the business process, the mobile phone will display relevant information such as the business data or business status of the first application service within the application interface of the first application program. During the existence of the business process of each first application service, the business status and / or business data of the first application service may also be updated. Then, the mobile phone will also update and display the business status and / or business data corresponding to the first application service within the first application interface of the first application program until the first application service ends, and the business process will also end accordingly.

[0116] For example, the first application program is a taxi-hailing application. The mobile phone generates a taxi-hailing service and creates an application process corresponding to the taxi-hailing service.

[0117] In one case, the application process of the taxi-hailing service is created when the taxi-hailing service is generated and continuously follows several business statuses such as the driver accepting the order, the driver arriving, traveling to the destination, and reaching the destination. When reaching the destination, the taxi-hailing service ends, and the corresponding application process of the taxi-hailing service also ends.

[0118] In another case, the application process of the taxi-hailing service is created when the taxi-hailing service is generated. When the order is not accepted within the timeout period, the user actively cancels the taxi-hailing, or other abnormal situations occur, the taxi-hailing service ends, and the taxi-hailing process also ends.

[0119] That is to say, the first application service processed in the embodiments of the present application can be an application service that starts and ends normally, or an application service that starts normally and ends abnormally, without limitation.

[0120] As Figure 1 shown in (b) of Figure 1 , the first application program is a taxi-hailing application, and the first application service is a taxi-hailing service. The mobile phone displays the application interface of the taxi-hailing application and responds to the click operation on the "confirm car-hailing" control (such as 102 shown in (b) of Figure 1 ) to form a taxi-hailing order. As shown in (c) of Figure 1 , the mobile phone displays the indication information of the generated taxi-hailing service within the application interface of the taxi-hailing application.

[0121] S202: Determine the target notification entry corresponding to the first application service.

[0122] The mobile phone provides multiple notification entries, and each notification entry can display notification messages. The notification entries provided by the mobile phone may include: the desktop, the negative first screen, the notification center, the control center, the lock screen interface, the status bar, the Always On Display (AOD) interface, and the quick application center, etc.

[0123] The mobile phone can match multiple target notification entries for the first application service. When the mobile phone displays the entry interface on the target notification entry, it can display the service information of the first application service on the entry interface.

[0124] There are various solutions for the mobile phone to determine the target notification entry corresponding to the first application service.

[0125] In the first solution, the mobile phone determines the associated target notification entry according to the first application program.

[0126] In one example, when the mobile phone installs the first application program, it can register the notification entries supported by the first application program.

[0127] When the mobile phone detects that the first application program generates a new first application service, it determines the notification entry pre-registered by the first application program as the target notification entry matched by the first application service.

[0128] For example, when the mobile phone installs a taxi-hailing application, the notification entries supported by the taxi-hailing application registration include the desktop, the negative first screen, the lock screen interface, the status bar, and the AOD interface. When the taxi-hailing application generates a new taxi-hailing service, the target notification entries that can be matched for the taxi-hailing service may include the desktop, the negative first screen, the lock screen interface, the status bar, and the AOD interface.

[0129] In the second solution, the mobile phone determines the corresponding target notification entry according to the first application service.

[0130] The mobile phone generates multiple first application services, and the importance and urgency levels of different first application services are different. The mobile phone can determine the importance and urgency level of the first application service, and then match the corresponding target notification entry according to the importance and urgency level of the first application service.

[0131] In one example, the mobile phone can pre-store an entry mapping table, and the entry mapping table stores different notification entries corresponding to different importance and urgency levels. The mobile phone determines the importance and urgency level of the first application service, searches for the notification entry corresponding to the importance and urgency level of the first application service in the entry mapping table, and determines it as the target notification entry corresponding to the first application service.

[0132] The notification entry provided by the mobile phone enables device reach, such as mobile phone reach or tablet reach. The reach methods provided by the mobile phone at each notification entry can be visual reach.

[0133] In another example, the mobile phone can also display service information in different display forms at different notification entries. For example, the display forms can include capsules, cards, and banners. The cards provided by the mobile phone can be further divided into card sets and card collapsed states, corresponding to cards of different specifications.

[0134] As shown in Table 1 below, it is an entry mapping table pre-stored in the mobile phone. The entry mapping table stored in the mobile phone can store the mapping relationship between the important and urgent levels of application services and the notification entries, and can also store device reach and reach methods.

[0135] Table 1

[0136]

[0137]

[0138] As shown in Table 1, the mobile phone can also store the identifiers corresponding to different important and urgent levels of application services in the entry mapping table. The mobile phone can first determine the important and urgent level of the first application service, search for the identifier (such as L11, L21, etc.) corresponding to the important and urgent level of the first application service in Table 2 below, and then search for the target notification entry and display form corresponding to the first application service in Table 1 according to the identifier.

[0139] Table 2

[0140]

[0141] The above example provides a solution for the mobile phone to determine the corresponding target notification entry for the first application service according to the entry mapping table. In other examples, the mobile phone can also determine the target notification entry corresponding to the first application service through user-defined settings, neural network model prediction, etc., without limitation.

[0142] In another example, during the operation of the first application service on the mobile phone, there are also different service states, and the important and urgent degrees of different service states are different. The mobile phone can also determine different target notification entries according to different service states of the first application service.

[0143] For example, during the operation of the first application service, the service states of the first application service obtained by the electronic device can sequentially include a first service state and a second service state. The first service state is the service state in the first time period, and the second service state is the service state in the second time period. The second time period is a time period after the first time period.

[0144] In the first time period, the electronic device determines the first importance and urgency level corresponding to the first service state according to the current first service state of the first application service, and determines the target notification entry corresponding to the first application service currently according to the first importance and urgency level.

[0145] In the second time period, in response to the update of the service state of the first application service, the electronic device determines the second importance and urgency level corresponding to the second service state according to the updated second service state of the first application service, and updates the target notification entry corresponding to the first application service according to the second importance and urgency level corresponding to the second service state. The target notification entry corresponding to the first service state and the target notification entry corresponding to the second service state may be the same or different.

[0146] For example, in the first time period, the service state of the taxi-hailing service obtained by the mobile phone is queuing, and the importance and urgency level is of general importance and urgency. The mobile phone looks up the corresponding identifier L23 in Table 2 and the corresponding target notification entries in Table 1 are: AOD interface, lock screen, negative first screen, desktop, and notification center.

[0147] In the second time period, the service state of the taxi-hailing service obtained by the mobile phone is that the driver has accepted the order, and the importance and urgency level is of general importance and urgency. The mobile phone looks up the corresponding identifier L23 in Table 2 and the corresponding target notification entries in Table 1 are: AOD interface, lock screen, negative first screen, desktop, and notification center.

[0148] In the third time period, the service state of the taxi-hailing service obtained by the mobile phone is that the passenger has got on the car, and the importance and urgency level is of general importance and general urgency. The mobile phone looks up the corresponding identifier L22 in Table 2 and the corresponding target notification entries in Table 1 are: negative first screen, desktop, and notification center.

[0149] In this example, when the taxi-hailing service of the mobile phone is in the queuing state and the driver has accepted the order, the mobile phone can be displayed on the entry interfaces of these 5 types of notification entries: AOD interface, lock screen, negative first screen, desktop, and notification center. When the taxi-hailing service of the mobile phone is switched to the state that the passenger has got on the car, the mobile phone is displayed on the entry interfaces of these 3 types of notification entries: negative first screen, desktop, and notification center, and stops being displayed on the AOD interface and the lock screen.

[0150] S203: During the operation of the first application service, in response to the second operation, display the second interface corresponding to the first notification entry.

[0151] S204: In response to the third operation, display the third interface corresponding to the second notification entry.

[0152] During the operation of the first application service, the mobile phone can display the service information of the first application service when showing the interface of each target notification entry. The service information displayed by the mobile phone may include service status and service data, especially the key information in the service status and service data.

[0153] At the same time, the mobile phone will display the entry interface of a target notification entry, and the mobile phone can switch to the entry interface of another target notification entry in response to the user's operation. For example, the mobile phone can display the second interface corresponding to the first notification entry in response to the second operation, and display the service information of the first application service on the second interface. For another example, the mobile phone can also display the third interface corresponding to the third notification entry in response to the third operation, and display the service information of the first application service on the third interface.

[0154] In one example, the target notification entries matched by the mobile phone for the taxi service include the desktop, the negative first screen and the lock screen, the notification center, the status bar, the AOD interface, etc.

[0155] Such as Figure 3 and Figure 4 shown, it is the interface diagram of the mobile phone displaying the service information of the first application service on the entry interface of the target notification entry. As Figure 3 shown in (a), the mobile phone can display the service information of the taxi service in the form of a banner 301 on the desktop. As Figure 3 shown in (b), the mobile phone can also display the service information of the taxi service in the form of a capsule 302 on the status bar. As Figure 3 shown in (c), the mobile phone can display the service information of the taxi service in the form of a capsule 303 on the interface of the negative first screen. As Figure 3 shown in (d), the mobile phone can display the service information of the taxi service in the form of a card 304 on the interface of the negative first screen.

[0156] Such as Figure 4 shown in (a), the mobile phone can display the service information of the taxi service in the form of a card 401 on the lock screen interface. As Figure 4 shown in (b), the mobile phone can display the service information of the taxi service in the form of a card 402 on the interface of the notification center. As Figure 4 shown in (c), the mobile phone can display the service information of the taxi service in another form of capsule 403 on the status bar. Different from Figure 3 the capsule form 302 shown in (b), the capsule form 403 also adds a decorative design, decorates the installation area of the camera or other devices, and can use this area to display service information, improving the screen utilization rate. As Figure 4 shown in (d), the mobile phone can also display the service information of the taxi service in the form of a capsule 404 on the AOD interface.

[0157] During the operation of the first application service, the mobile phone can respond to multiple operations of the user, sequentially switch the entry interfaces of different target notification entries, and display the service information of the first application service on each entry interface.

[0158] The mobile phone can also, during the operation of the first application service, only display the entry interface of one target notification entry, and display the service information of the first application service on this one entry interface. For example, after the user places an order for a taxi service and then locks the screen, the mobile phone can continuously display the service information of the taxi service on the locked screen until the taxi service ends.

[0159] The mobile phone can select different target notification entries to display the service information, and can also select the display form of the service information on the interfaces of different notification entries. The display forms involved include cards, capsules, banners, etc.

[0160] Among them, the card is the main display form. Cards mainly include quick service cards, quick application cards (JavaScript TM , JS), Android TM application cards (Widget), and content interface cards, and support presenting in the form of cards or icons.

[0161] Quick service (Shortcut) refers to a service presented in the form of an icon, and the relevant service can be used on the mobile phone without installing the corresponding application program. Content interface card (Software Development Kit, SDK), and the service is presented in the form of a card or voice.

[0162] The quick application card is the JS card, which is carried by the quick application and presented in the form of a card, intuitively displaying the service content. The JS card is mainly displayed on the negative first screen interface and the quick application center interface.

[0163] Android TM The application card is the Widget card. The service follows the application and is presented in the form of a card, intuitively displaying the service content. The Widget card is displayed on multiple types of notification entries such as the desktop, negative first screen, notification center, and multi-device.

[0164] The Widget card can be displayed on notification entries such as the desktop, status bar interface, locked screen, notification center, and multi-device.

[0165] The above Figure 2 display control method provided in this embodiment, the mobile phone matches a target notification entry for displaying the service information of the first application service for the first application service. On the Figure 2 basis, the mobile phone can also match a solution for the target display form for the first application service.

[0166] Such asFigure 5 As shown, it is another schematic diagram of the display control method. The provided display control method mainly includes the following processes:

[0167] S501: In response to a first operation on a first interface of a first application, display indication information of a first application service of the first application.

[0168] The mobile phone can respond to the user's first operation and generate a first application service. The specific implementation of S501 can refer to the specific implementation of the aforementioned S201 and will not be elaborated here.

[0169] S502: Determine a target notification entry corresponding to the first application service.

[0170] S503: Determine a target display form corresponding to the first application service.

[0171] The mobile phone determines a corresponding target notification entry for the first application service and determines a corresponding target display form. For example, the mobile phone can first determine the target notification entry corresponding to the first application service. For another example, the mobile phone can also first determine the first type of display notification corresponding to the first application service.

[0172] In one example, the target display form determined by the mobile phone for the first application service can include a first display form and a second display form. Among them, the first display form corresponds to a second interface of a first notification entry, and the first display form is the display form of the service information of the first application service on the second interface. The second display form corresponds to a third interface of a second notification entry, and the second display form is the display form of the service information of the first application service on the third interface. The second display form and the third display form determined by the mobile phone for the first application service can be the same or different.

[0173] For example, during the operation of the taxi-hailing service, the target notification entries determined by the mobile phone for the taxi-hailing service include the negative first screen and the lock screen interface.

[0174] At a first moment, the mobile phone displays the entry interface of the negative first screen and displays the service information of the taxi-hailing service in a card form on the negative first screen interface.

[0175] At a second moment, the mobile phone displays the lock screen interface and displays the service information of the taxi-hailing service in a capsule form on the lock screen interface.

[0176] There can also be multiple schemes for the mobile phone to select a corresponding first display form for the first application service.

[0177] The first scheme is that the mobile phone can determine a corresponding target display form for the first application service based on the first application.

[0178] In one example, the mobile phone obtains the display form pre-registered by the first application as the target display form corresponding to the first application service.

[0179] When the mobile phone installs each application, the application registers the supported display forms. When the mobile phone generates the first application service, it searches for the display form pre-registered by the first application that generates the first application service, and uses the pre-registered display form as the target display form corresponding to the first application service.

[0180] For example, when the mobile phone installs a taxi-hailing application, the second type of display forms pre-registered by the taxi-hailing application include JS cards, Widget cards, capsules, etc. When the mobile phone generates a taxi-hailing service, it uses the second type of display forms pre-registered by the taxi-hailing application as the target display form of the taxi-hailing service.

[0181] For another example, for the mobile phone express application, the second type of display forms pre-registered by the express application include JS cards and capsules, etc. When the mobile phone generates an express service, it uses the second type of display forms pre-registered by the express application as the second type of display form of the express service.

[0182] In the second solution, the mobile phone can determine the corresponding target display form for the first application service based on the importance and urgency levels of the first application and the first application service.

[0183] In this case, the mobile phone first determines the target notification entry of the first application service, and then determines the target display form of the first application service. The mobile phone determines the target notification entry of the first application service by searching in the pre-stored entry mapping table (such as Table 1) according to the importance and urgency levels of the first application service. For the specific implementation of how the mobile phone determines the target notification entry of the first application service, reference can be made to the specific implementation of S202 described above, and details will not be elaborated here.

[0184] In one example, the mobile phone obtains the second type of display forms pre-registered by the first application, and the third type of display forms pre-registered by the target notification entry. The mobile phone uses the same display forms among the second type of display forms and the third type of display forms as the target display form of the first application service.

[0185] When the mobile phone starts up each time, some or all of the notification entries initiate a registration application to apply for display service information. In addition, the notification entry also registers the supported display forms, and the notification entry provides the function of displaying service information in the registered display forms. The mobile phone can store the display forms supported by the notification entry into the entry mapping table (such as Table 1).

[0186] When the mobile phone generates the first application service, according to the importance and urgency levels of the first application service, it searches in the entry mapping table for the target notification entry associated with the first application service and the display forms supported by each target notification entry.

[0187] The mobile phone takes the display form that exists in common between the previously registered display form of the first application and the display form supported by the target notification entry as the target display form of the first application service.

[0188] Furthermore, the target display form determined by the mobile phone has a corresponding relationship with the target notification entry. Taking the target notification entry including the first notification entry and the second notification entry as an example.

[0189] For example, the mobile phone takes the display form that exists in common between the display form previously registered by the first application and the display form previously registered by the first notification entry as the first display form corresponding to the first notification entry. When the mobile phone displays the second interface of the first notification entry, it displays the service information of the first application service in the first display form.

[0190] For another example, the mobile phone takes the display form that exists in common between the display form previously registered by the first application and the display form previously registered by the second notification entry as the second display form corresponding to the second notification entry. When the mobile phone displays the third interface of the second notification entry, it displays the service information of the first application service in the second display form.

[0191] The second display form and the third display form determined by the mobile phone can be one display form or multiple display forms, without limitation.

[0192] S504: On the entry interface of the target notification entry, display the service information of the first application service in the target display form.

[0193] The mobile phone determines at least two target notification entries of the first application service and the target display forms corresponding to different target notification entries, and then can perform the operation of displaying the service information of the first application service. The specific implementation manner of S504 can refer to the specific implementation processes of the foregoing S203 and S204, and will not be elaborated here.

[0194] As Figure 6 shown, it is a schematic diagram of the process of the display control method provided by the mobile phone for implementing the above implementation manner. The mobile phone has an intention perception function and can obtain the important and urgent level of the generated service.

[0195] When the mobile phone generates the first application service, it determines the important and urgent level of the first application service through intention perception. The mobile phone encapsulates the service information and the important and urgent level of the first application service to achieve service reach.

[0196] The mobile phone realizes service reach mainly including two stages: device reach and notification entry matching. The mobile phone first determines the device to be reached, such as the mobile phone itself or other devices (computer, tablet, watch, car machine, etc.).

[0197] The mobile phone determines the notification entry that provides the display function on the device that needs to be reached. Referring to the specific implementation process of the aforementioned S202, the mobile phone searches for the corresponding target notification entry in the entry mapping table according to the importance and urgency level of the first application service. The mobile phone displays the service information of the first application service on the entry interface of the target notification entry to complete the service reach.

[0198] The mobile phone executes the display control method provided in this embodiment, which mainly includes four processes: registering a notification entry, matching a notification entry for an application service and displaying service information, updating and displaying service information, and stopping displaying service information. These four processes will be explained in turn below.

[0199] Process 1: Notification portal registration.

[0200] Every time the phone is turned on, the notification portal initiates a registration application to apply for permission to display business information.

[0201] The target notification portal sends a registration application to the service interaction display framework. After the target notification portal successfully registers with the service interaction display framework, the service interaction display framework is allowed to send the service information of the first application service to the target notification portal.

[0202] Process 2: The mobile phone matches the notification entrance for the application service and displays the service information.

[0203] When the mobile phone generates the first application service, the mobile phone determines the importance and urgency level of the current service state of the first application service, and searches the entry mapping table for the second type notification entry corresponding to the importance and urgency level of the current service state.

[0204] The mobile phone verifies whether the second-type notification entrance has initiated the registration application first, and determines the second-type notification entrance that initiated the registration application first as the target notification entrance for the first application service.

[0205] The mobile phone also obtains the second display form pre-registered by the first application and the third display form pre-registered by the target notification portal. The mobile phone determines the target display form corresponding to the first application service based on the same form in the second display form and the third display form.

[0206] When the mobile phone displays the entry interface of each target notification entry, the service information of the first application service is displayed in the corresponding target display form.

[0207] Process 3: The mobile phone updates and displays the business information.

[0208] The mobile phone can obtain the updated service information of the first application service, and display the updated service information when displaying the entry interface of each target notification entry.

[0209] During the operation of the first application service on the mobile phone, the mobile phone will also re-determine the important and urgent level corresponding to the current service state according to the update of the service state of the first application service, and search for the current target notification entry corresponding to the important and urgent level of the current service state in the entry mapping table.

[0210] The mobile phone will determine a new target notification entry according to the update of the service state, and display the updated service information on the entry interface of the new target notification entry.

[0211] Process 4: The mobile phone stops displaying service information.

[0212] The mobile phone can also obtain a notification that the first application service has ended, and when the first application service ends, stop displaying the service information of the first application service on the target notification entry.

[0213] The above content mainly introduces the specific implementation process of the display control method provided by the embodiments of the present application from the perspective of the mobile phone. Next, the specific implementation process of the provided display control method will be explained in combination with the software and hardware framework of the mobile phone.

[0214] The framework of the mobile phone is a layered architecture. The layered architecture divides software and hardware into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the electronic device may include, for example, an application layer (Application, APP), a framework layer (FrameWorK, FWK), a hardware abstraction layer (Hardware AbstractionLayer, HAL), a kernel layer, and a hardware layer. Of course, in addition to the above several main layered architectures, it may also include a runtime and system libraries, etc., which will not be elaborated.

[0215] As Figure 7 shown, it is a schematic diagram of the software framework of the mobile phone. For ease of understanding, Figure 7 only some function modules related to the display control method provided by the embodiments of the present application are schematically shown, and it is not limited that the software framework of the mobile phone only includes these function modules.

[0216] Exemplarily, the application layer may include a series of application programs. The application programs included in the application layer may include system application programs and third-party application programs, such as a taxi-hailing application and a food delivery application.

[0217] In addition to including various application programs, the application layer may also include various notification entries and a display service module for supporting the display of corresponding entry interfaces for various notification entries, etc.

[0218] As Figure 7As shown in the figure, the application layer includes a first application, a notification entry module, and a host module HOST ARR. HOST ARR includes an entry initialization module, a view creation module, and a service channel.

[0219] Among them, the first application is the application that generates the first application service in the foregoing embodiment. The first application may include various types of applications, such as food delivery applications, taxi-hailing applications, etc.

[0220] This example does not focus on the implementation logic of the functions of various first applications themselves. For example, how the first application specifically generates the first application service and completes the first application service. This example mainly focuses on the process of calling each target notification entry to display the service information of the first application service on the entry interface when the mobile phone generates the first application service.

[0221] The notification entry module includes various notification entries supported by the mobile phone itself to display service information, such as the desktop, negative first screen, notification center, control center, quick application center, lock screen, status bar, AOD, etc.

[0222] In other cases, the notification entries provided on the mobile phone may also include multi-device entries. The multi-device entry may be other devices in communication connection with the mobile phone, such as a bracelet, a watch, a tablet, a car machine, etc. The multi-device notification entry set in the notification entry module refers to the communication module on the mobile phone used to communicate with the multi-device. The mobile phone can transmit the service information to the notification entry of the multi-device through the communication module for display, so that the service of the first application service can reach the user as much as possible.

[0223] The view creation module can support the creation and rendering of views for the notification entry to display the corresponding entry interface. Specifically, the view creation module may include view creation sub-modules for creating corresponding views for various operating systems, programming languages, or services. These sub-modules can be called by various notification entries in the notification entry module to create views.

[0224] The view creation module may include: a JS card view creation sub-module, an SDK card view creation sub-module, a notification (Notification) view creation sub-module, a Widget card view creation sub-module, a shortcut service (Shortcut) view creation sub-module, and a Remote Views view creation sub-module.

[0225] The notification entry initialization module includes a notification entry registration sub-module and a notification entry callback sub-module. Among them, the notification entry registration sub-module is used to receive the registration of various notification entries within the notification entry module. After registration, the notification entry has the permission to display business information and can display the business information of the generated application service on the corresponding entry interface. When the notification entry is registered in the notification entry registration sub-module, it may also register the display forms, display specifications, etc. that it supports at the same time.

[0226] After each boot of the mobile phone, various notification entries that support touch display within the notification entry module can register with the notification entry registration sub-module, and the notification entry that initiates the registration application first can be called to display business information.

[0227] The notification entry callback sub-module is used to monitor the called status of various notification entries. When the first application generates the first application service, in response to the notification entry call instruction of the framework layer, it calls the corresponding notification entry for interface display.

[0228] The service channel includes a card implementation type, a card ID, and service reception and processing, and is used to cooperate with the implementation of channel calls, card ID transmission, and service distribution.

[0229] The framework layer provides application programming interfaces (Application Programming Interface, API) and programming frameworks for the applications in the application layer. The framework layer can receive the instructions sent from the application layer and feedback relevant data to the application layer so that the application layer can display the relevant data. The application program framework layer also includes some predefined functions.

[0230] Continue as Figure 7 shown, the framework layer includes a wisdom module and a service interaction and display framework.

[0231] Among them, the wisdom module is used to manage the application services generated by the application program. Specifically, the wisdom module may include relevant functional modules that provide wisdom services in the mobile phone and manage the application services of each application program in the mobile phone.

[0232] When the wisdom module monitors that the first application generates the first application service, it notifies the service interaction and display framework to trigger the execution of the display control operation for the first application service.

[0233] In one example, when the wisdom module monitors that the first application generates the first application service, it also assigns a business identity (Identity Document, ID) to the first application service, and the subsequent display control method process can identify and match the first application service according to the business ID.

[0234] In another example, the intelligent module can also send the service information of the first application service to the service interaction and display framework. The service interaction and display framework assigns a service ID to the first application service and then passes the service ID to the intelligent module.

[0235] In addition, the intelligent module can also determine the importance and urgency level of the first application service. The intelligent module can determine the importance and urgency level of the first application service based on a pre-stored prediction algorithm or prediction model for predicting the importance and urgency level.

[0236] Furthermore, the intelligent module can also obtain the service information of the first application service and pass the service information of the first application service to the service interaction and display framework. The service information of the first application service obtained by the intelligent module is provided by the first application program. The intelligent module can directly pass the service information of the first application service to the service interaction and display framework. The intelligent module can also obtain, according to the target display forms supported by the first application program pre-registered, the view files in specific formats required for displaying the service information of the first application service in the target display forms, and pass the view files corresponding to each target display form to the service interaction and display framework.

[0237] The intelligent module can directly pass the encapsulated view files to the service interaction and display framework. Or, the intelligent module can also store the encapsulated view files in a specified shared storage space and notify the service interaction and display framework. The service interaction and display framework can go to the specified shared storage space to obtain the encapsulated view files.

[0238] As Figure 7 shown, the service interaction and display framework includes an interaction specification query module, a service parsing module, a parsing and implementation module, and an interaction notification entry management module.

[0239] Among them, the interaction specification query module receives the service ID and the importance and urgency level of the first application service sent by the intelligent module. The interaction specification query module queries, based on a pre-stored entry mapping table (such as Table 1), the target notification entry and the target display form corresponding to the importance and urgency level of the first application service. The interaction specification query module uploads the queried target notification entry and target display form associated with the first application service, together with the service ID, to the interaction notification entry management module.

[0240] The service parsing module receives the service ID and the service information of the first application service sent by the intelligent module. The service information mentioned here can be the encapsulated view files corresponding to each target display form. The parsing service module passes various types of service information to the parsing and implementation module.

[0241] The parsing and implementation module includes parsing and implementation function modules for various forms, specifically including:

[0242] Dynamic card framework, which realizes the dynamic card framework Surface View of the desktop view; Widget framework, where the Widget framework realizes the Widget Management Service; JS framework, which realizes the quick service View; Desktop application Launcher Apps service, which realizes the shortcut info; Notification framework, which realizes RemoteViews, etc.

[0243] These frameworks can obtain view files of corresponding types, parse to obtain the View files for corresponding view displays, and original business information, etc. And upload this information to each notification entry through the channels of each notification entry, so that the notification entry can display the corresponding business information.

[0244] The interactive notification entry management module includes ID allocation, interface callback processing, and service binding modules. ID allocation is used to allocate business IDs for the first application business, and interface callback processing is used to call the create interface, update interface, and stop interface, and listen for the start, update, and stop operations of the display control process.

[0245] In addition, continue as Figure 7 shown, the application layer also includes a status update interface and a lifecycle monitoring module. The lifecycle monitoring module is used to monitor the business process of the first application business. During the existence of the process of the first application business, the status update interface can be called to update the business status of the first application business.

[0246] In addition, the framework layer can also include some general functional modules, such as window manager, content provider, view system, resource manager, notification manager, etc. These functional modules can cooperate to support the application layer to implement various display functions.

[0247] The hardware abstraction layer can encapsulate the driver program in the kernel layer and provide an interface for the application framework layer to call, shielding the implementation details of the underlying hardware.

[0248] Combined with Figure 7 the provided software framework, the mobile phone responds to the first application business generated by the first application program and displays the business information of the first application business on multiple first-class entry interfaces. As Figure 8 shown, it is a schematic flowchart of the display control method implemented by the software framework of the mobile phone. As Figure 8 shown, the mobile phone executing the display control method mainly includes: Process 1, notification entry registration; Process 2, the mobile phone matches a notification entry for the application business and displays the business information; Process 3, the mobile phone updates the displayed business information; Process 4, the mobile phone stops displaying the business information.

[0249] Figure 8 The processes 1, 2, 3, and 4 shown respectively correspond to the processes 1, 2, 3, and 4 of the foregoing example. Below, in combination with the specific execution modules of the software framework, a detailed description will be given for these 4 main processes in sequence.

[0250] It should be noted that the business provider here can be understood as a data providing module within the first application that generates the first application service and can provide service information. The intelligent module can be understood as the intelligent module bound to the first application, or the intelligent module integrated on the intelligent side and bound to multiple application programs to manage the multiple application services they generate. The target notification entry can be the target notification entry among the multiple notification entries of the notification entry module that is associated with the first application service.

[0251] Process 1, notification entry registration.

[0252] S801: The target notification entry registers with the service interaction and display framework.

[0253] Process 1 mainly realizes the registration of the notification entry with the service interaction and display framework, and at the same time registers the display forms and specifications that it can implement.

[0254] Process 2, the mobile phone matches the notification entry for the application service and displays the service information.

[0255] S802: The business provider notifies the intelligent module that the first application generates the first application service.

[0256] S803: The intelligent module determines the importance and urgency level of the first application service.

[0257] S804: The intelligent module sends the service ID and the importance and urgency level of the first application service to the service interaction and display framework.

[0258] S805: The service interaction and display framework queries the entry mapping table to determine the target notification entry.

[0259] S806: The service interaction and display framework requests service information from the intelligent module.

[0260] S807: The business provider sends service information to the intelligent module.

[0261] S808: The intelligent module sends a view file containing service information to the service interaction and display framework.

[0262] S809: The service interaction and display framework distributes the view file containing service information to the target notification entry.

[0263] S810: The target notification entry displays service information.

[0264] In process 3, the mobile phone updates the display of service information.

[0265] S811: The service provider (Provider) sends the updated service information to the intelligent module.

[0266] S812: The intelligent module sends a view file containing the updated service information to the service interaction and display framework.

[0267] S813: The service interaction and display framework monitors the life cycle, regularly obtains the updated service information, and distributes the view file containing the updated service information to the target notification entry.

[0268] S814: The target notification entry displays the updated service information.

[0269] In process 4, the mobile phone stops displaying service information.

[0270] S815: The service provider (Provider) notifies the intelligent module that the first application has ended the first application service.

[0271] S816: The intelligent module notifies the service interaction and display framework of the service ID of the first application service and the stop of the entry display.

[0272] S817: The service interaction and display framework notifies the target notification entry to stop the entry display.

[0273] S818: The target notification entry stops displaying service information.

[0274] Based on the user's behavior of ending an order or other reasons for ending, the first application notifies the intelligent module that the first application has ended the first application service. The intelligent module sends the service ID of the first application service and an instruction to stop the notification entry display to the service interaction and display framework. The service interaction and display framework instructs the notification entry to stop the entry display, and the notification entry then stops displaying service information.

[0275] In addition, considering that the visible states of each target notification entry are different under different usage states, it will affect the display ability of the entry interface.

[0276] If the current entry interface is invisible, the service interaction and display framework may not send service information to the corresponding invisible notification entry. Or, the service interaction and display framework can also send the service information to the system cabinet entry. After the notification entry receives the service information, if the entry interface is currently invisible, it can not generate or display the view of the corresponding service information. When the entry interface of the notification entry switches to the visible state, the notification entry will display the view of the service information.

[0277] For example, when a ride-hailing application generates a ride-hailing service, the determined associated notification entrances include the negative first screen, the notification center, and the desktop. Then, if the mobile phone is currently displaying the desktop interface, the interface states of the negative first screen and the notification center are invisible. The service interaction and display framework may not send service information to the negative first screen and the notification center, and only send service information to the negative first screen or the notification center for display when the mobile phone switches to the negative first screen or the notification center. Alternatively, the service interaction and display framework may also send service information to the negative first screen and the notification center according to the specification, and the negative first screen or the notification center renders a view on the corresponding interface and displays the service information. Then, when the negative first screen is visible, the service information displayed on the negative first screen can reach the user.

[0278] Corresponding to the above Figure 8 As shown in the detailed example Figure 9 As shown, it is a schematic overview diagram of the software framework for implementing the display control method. The display control process may mainly include three stages: intent prediction, service management, and service reach.

[0279] The intelligent side in the mobile phone performs intent prediction based on the application services generated by the application program. The intelligent side includes a multi-modal multi-dimensional trigger and a multi-modal intent framework. The multi-modal multi-dimensional trigger framework includes a low-power voice module and a low-power vision model. The low-power voice model collects voices within a preset range and performs speech recognition. The low-power vision model collects images within a preset range and performs visual recognition. The recognition results of the low-power voice model and the recognition results of the low-power vision model are sent to the multi-modal intent framework after fusion perception.

[0280] The multi-modal intent framework performs speech recognition and natural language processing (NLP), as well as visual recognition and understanding respectively. Finally, the prediction result of the user intent is obtained through multi-modal intent prediction. The predicted intents involved here may include the intent to generate and display an order indicated by the user, and the intent for the user to hope that relevant service information is displayed. The multi-modal intent framework sends the predicted intent to the service management framework based on the intent slot.

[0281] The service management framework can perform fuzzy matching (Intent) or exact matching (ID) on the intent predicted by the multi-modal intent module, and perform service recommendation. One predicted intent may correspond to multiple services. After that, the service management framework will also perform service orchestration, such as service composition or batch processing. The service management framework also provides capabilities such as service query, permission management, ID management, classification and storage, installation, uninstallation, registration, and deregistration. Finally, the service management framework generates the display service for the application service, which can be mainly divided into system atomic services, third-party atomic services, and real-time data services, and reaches the service interaction and display framework.

[0282] The service interaction and display framework includes a system interaction notification entry, a service execution adapter, and a human-computer interaction specification. Among them, the system interaction notification entry mainly displays various notification entries. The service execution adapter is used to match the notification entry, display form, display method, etc., and query the importance and urgency level of the application service according to the human-computer interaction specification to determine the display method of the service information, the position of the notification entry, the display form, etc. Among them, the human-computer interaction specification includes a service interaction specification and a barrier-free scenario specification.

[0283] In this way, the system service and the third-party service are registered and managed in the service management framework. The intelligent side makes an intention prediction and then sends an intent service to the service display and interaction framework. The service display and interaction framework parses the intent and service, and finally the service interaction specification determines the display notification entry and the card size, and calls the notification entry for display to reach the user.

[0284] The foregoing solution describes the process of the electronic device from generating an application service to calling the notification entry to display the service information of the application service. Next, several main refinement solutions related to the display data transmission during the execution of the above display control method will be described through different embodiments. It should be noted that the subsequent Embodiments 2-4 are technical solutions implemented on the basis of the foregoing Embodiment 1.

[0285] Embodiment 2

[0286] Before the mobile phone executes step S504, that is, before the mobile phone displays the service information of the first application service in the target display form on the entry interface of the target notification entry, it is also necessary to first obtain the view file corresponding to the target display form.

[0287] The electronic device uses the Widget architecture. When the application is installed on the electronic device, the display form supported by the generated service information is a Widget card. Under the Widget architecture, when the notification entry displays the service information in the form of a Widget card, it is necessary to use the view file corresponding to the Widget card, such as a serialized file in the Remote Views format.

[0288] In one example, the notification entry has the ability to generate a view file corresponding to the Widget card. The notification entry can obtain the service information and generate a view file corresponding to the Widget card according to the service information. The notification entry then renders the view file corresponding to the Widget card and displays the service information in the form of a Widget card.

[0289] In another example, the notification entry does not have the ability to generate the view file corresponding to the Widget card. The notification entry needs to obtain the first application or other modules in the electronic device to generate the view file corresponding to the Widget card and pass it to the notification entry. This embodiment mainly explains the specific implementation of this example.

[0290] In other examples, other architectures may also be used in the electronic device in addition to the Widget architecture. Multiple types of notification entries of the electronic device will also support other types of card protocols in addition to the Widget card, such as the JS card corresponding to the JS architecture, etc., which will not be elaborated.

[0291] As in the foregoing embodiments Figure 7 and Figure 8 shown, the service information of the first application service is generated by the first application and provided by the service provider (Provider) of the business side to the service interaction and display framework, and distributed by the service interaction and display framework to the associated target notification entry for display. The service provider (Provider) of the business side can be the data providing component of the first application or the data providing component of the intelligent module. It should be noted that the service providers (Providers) of different application services are different.

[0292] In a specific implementation, the intelligent module monitors the application services generated by each application. When it monitors that the first application generates the first application service, it determines whether the first application has previously registered the display form of the Widget card. If the intelligent module determines that the first application has previously registered the display form of the Widget card, it determines that the first application service is specified to be displayed in the Widget card.

[0293] The intelligent module notifies the service interaction and display framework and provides the identification information of the service provider (Provider) corresponding to the first application service to the service interaction and display framework. The service interaction and display framework can request the service information of the first application service from the service provider (Provider) according to the identification information of the service provider (Provider).

[0294] As Figure 10 shown, it is another software framework schematic diagram of the electronic device corresponding to the Widget architecture. The framework layer includes a service interaction and display framework, a native Widget framework (Android TM Open Source Project", AOSP FWK) and an intelligent module. The intelligent module can obtain the service information of each application service, such as a taxi service, a food delivery service, a high-speed rail itinerary service, a flight itinerary service, etc.

[0295] The service interaction and display framework executes operations on the host side, i.e., the Host side, of the native Widget framework, and requests business information from the intelligent module through the Widget service of the native Widget framework. The business provider of the intelligent module provides the business information of the first application service to the native Widget framework, and the native Widget framework generates a view file corresponding to the Widget card according to the business information. The service interaction and display framework obtains the view file corresponding to the Widget card generated by the native Widget framework and distributes it to each associated target notification entry. The target notification entry obtains the view file corresponding to the Widget card, and then calls the relevant interfaces provided by the service interaction and display framework to render the view file corresponding to the Widget card into a view (View) and display the business information of the first application service in the format of the Widget card.

[0296] The mobile phone creates a corresponding process for each service, and there is process isolation between the processes of different services.

[0297] For example, the first application program of the mobile phone generates the first application service and creates a corresponding first process for the first application service. The interaction and display framework of the mobile phone displays the business information of the first application service through multiple target notification entries. This is a separate display control service, different from the first application service. The mobile phone also creates a corresponding second process for this display control service. There is process isolation between the first process and the second process, and the process isolation causes the second process to be unable to directly obtain accurate business information in the physical storage space of the first process. The mobile phone can enable the Inter Process Communication (IPC) technology to obtain the business information of the first application service.

[0298] The intelligent module can encapsulate the business information of the first application service into a file in a specific format that supports cross-process transmission and provide it to the interaction and display framework. The file in a specific format that supports cross-process transmission can be a serialized file in the Remote Views format applicable to the Widget card, or a serialized file in the JSON Views format that may be adopted for the JS card.

[0299] The intelligent module transmits the encapsulated view file across processes to ensure that the view file transmitted to the notification entry is an accurate and renderable view file, and the notification entry can display the business information of the first application service in the corresponding display form.

[0300] As Figure 11 shown, it is a schematic flowchart of the display control method executed based on the Widget architecture. As Figure 11 shown, the provided display control method mainly includes the following steps:

[0301] S1101: The target notification portal initiates a registration application to the service interaction and presentation framework.

[0302] S1102: In response to a first application service generated by a first application program, the service interaction and presentation framework determines a target notification entry and a target display form corresponding to the first application service.

[0303] S1103: The service interaction and presentation framework distributes the view file corresponding to the business information of the first application business to the target notification entry;

[0304] S1104: The target notification portal displays the service information of the first application service in a target form according to the view file corresponding to the service information of the first application service.

[0305] In an example, the target display form corresponding to the first application service includes a Widget card, and the view file corresponding to the service information of the first application service includes a view file in a Remote Views format.

[0306] The service interaction and display framework determines that the first application service supports display in the form of a Widget card, and first calls the native Widget framework to process the service information of the first application service into a view file in the Remote Views format. The native Widget framework uses the Remote Views channel to transmit the view file in the Remote Views format to the service interaction and display framework across processes, and the service interaction and display framework then distributes the view file in the Remote Views format to the target notification entry.

[0307] There are multiple target notification entrances determined by the service interaction and display framework. The service interaction and display framework can distribute view files in Remote Views format to multiple target notification entrances that support Widget card display. These target notification entrances can display business information of the first application business in the form of Widget cards.

[0308] like Figure 12 As shown, it is an interactive schematic diagram of executing the display control method based on the Widget architecture.

[0309] S1201: The smart module on the smart side instructs the interactive display management module to start displaying.

[0310] S1202: The interactive display management module instructs the interactive display service module to start displaying.

[0311] The intelligent module detects that the first application generates the first application service, and instructs the Interaction Display Manager to start displaying. The interaction display module instructs the Interaction Display Service of the service interaction and display framework to start displaying, and the input interaction information carried includes App Clip Info.

[0312] S1203: The interaction display service module performs callback verification to check whether the caller has the permission to call the notification entry for display.

[0313] S1204: The interaction display service module performs information verification to check whether the interaction information is compliant. If the verification fails, the callback returns an error code -2. S1204 includes:

[0314] S12041: Whether the important and urgent level is legal;

[0315] S12042: Whether the card type is supported;

[0316] S12043: Verify whether the software development kit (SDK) version corresponding to the installation package in the App Clip Info meets the minimum version required by the card.

[0317] The callback verification mainly checks whether the caller has the permission to call the notification entry for display.

[0318] The information verification mainly checks whether the interaction information is qualified. If the verification fails, the callback returns an error code. For example, the error code can be -2.

[0319] The main content of the information verification includes: whether the important and urgent level is legal, and verify whether the software development kit (SDK) version corresponding to the installation package in the App Clip Info meets the minimum version required by the card.

[0320] S1205: The interaction display service module queries the specification information of the target notification entry to be sent to the notification entry management module according to the important and urgent level. If there is no corresponding notification entry, the callback returns an error code -3.

[0321] S1206: The notification entry management module sends the specification information of the target notification entry to the interaction display service module.

[0322] S1207: The interaction display service module instructs the interaction scheduling control module to create an Interaction Display Record Locked.

[0323] S1208: The interactive scheduling control module instructs the interactive display service module to lock the interactive display record.

[0324] S1209: The interactive display service module instructs the card display interaction module to create a Widget card.

[0325] S1210: The card display interaction module instructs the Widget management service module to enter the card service process.

[0326] S1211: The Widget management service module instructs the application Widget host to apply for a Widget ID.

[0327] S1212: The application Widget host returns the Widget ID to the Widget management service module.

[0328] S1213: The Widget management service module instructs the Widget management service module to bind the business-side Provider and the Widget ID to the native Widget service.

[0329] S1214: The Widget management service module returns a binding instruction to the Widget management service module.

[0330] S1215: The Widget management service module instructs the application Widget host to start listening for Widget changes.

[0331] S1216: The Widget management service module instructs the Widget listening module to create a Widget listener.

[0332] S1217: The Widget listening module returns the Widget listener to the Widget management service module.

[0333] S1218: The Widget management service module instructs the application Widget host to set a listener for the current Widget.

[0334] S1219: The application Widget host applies to the intelligent module for business information.

[0335] S1220: The intelligent module instructs the native Widget framework to update the application Widget and process it into a Remote Views file.

[0336] S1221: The native Widget framework instructs the application Widget host to update the application Widget and send the Remote Views file using the Remote Views channel.

[0337] S1222: The Widget host is applied to instruct the Widget listening module to update the Widget.

[0338] S1223: The Widget listening module sends a message indicating successful creation to the Widget management service.

[0339] S1224: The Widget management service notifies the interactive display service module to perform a card display callback, indicating successful creation.

[0340] S1225: The interactive display service module instructs the interactive scheduling control module to call start display lock, obtain the RemoteViews, and extract the quick application data bound to it.

[0341] S1226: The interactive scheduling control module calls start display lock.

[0342] S1227: The interactive scheduling control module instructs the application Widget host to call start display lock.

[0343] S1228: The application Widget host calls start display lock.

[0344] S1229: The application Widget host sends display data.

[0345] S1230: The application Widget host instructs the target notification entry to register a creation callback.

[0346] S1231: The application Widget host ends the call to start display lock.

[0347] Next, the solutions for implementing the foregoing Processes 1-3 in the Widget architecture will be described in detail.

[0348] For the notification entry registration operation corresponding to the foregoing Process 1, the notification entry needs to register with the service interaction and display framework and provide the forms and specifications it supports for display. After a service is created, when the expected notification entry is queried from the interaction rule engine, it is also necessary to compare it with the registration information of the notification entry. The service can be truly displayed only when the registration information of the notification entry supports the corresponding forms and specifications.

[0349] Specifically, as Figure 13 shown, it mainly includes:

[0350] S1301: Registration application.

[0351] The target notification entry registers the notification entry Register Entrance with the Interactive Display Manager and validates the input parameters. If it is empty, -2 is returned.

[0352] S1302: Add a registration listener.

[0353] The interactive display management module adds a registration listener (Add Register Listener). Verify the server. If the service return cannot be obtained, return -1. Verify the registration information. If it has been registered, return -2.

[0354] S1303: Registration application.

[0355] The interactive display management module initiates a registration application to the interactive display service module and registers a notification entry lock with the interactive scheduling control module. The interactive scheduling control will verify the caller's permissions. If there are no permissions, return -2. Verify the input parameters. If they are empty, return -2.

[0356] S1304: Registration entry lock.

[0357] S1305: Registration entry lock.

[0358] S1306: New entry registration information.

[0359] The interactive scheduling control traverses the list of notification entry registration information passed in and registers each notification entry in turn until all the notification entries on the notification entry registration information list have been registered. If the passed-in notification entry does not exist on the local machine during the traversal, it will be skipped.

[0360] Corresponding to the aforementioned process 2, the notification entry displays the Widget card. As Figure 14 shown, it mainly includes the following steps:

[0361] S1401: Create a host view.

[0362] S1402: Create a host view.

[0363] S1403: Indicate to create a host view.

[0364] The host instructs the interactive Widget management to create a host view, and the interactive Widget management instructs the interactive Widget host view module to create a host view.

[0365] S1404: Apply Remote Views.

[0366] S1405: Generate a rendering asynchronous task.

[0367] S1406: Indicate to start executing the rendering task.

[0368] The Interactive Widget Host View Module applies Remote Views and renders an asynchronous task (inflateAsync), indicating that the asynchronous application task starts to execute the task (Start Task On Executor).

[0369] S1407: Process the background.

[0370] S1408: Render the view.

[0371] S1409: Start the transfer and execution.

[0372] S1410: Indicate view application listening.

[0373] S1411: Listen to the application container.

[0374] S1412: View callback.

[0375] The asynchronous task application processes the background (doLn Background), renders the view (inflate View), starts the transfer and execution (On Post Execute), then triggers the Interactive Widget Host View to listen to the view application (OnView Applied, View Apply Listener), and sends it to the host for view callback (View Callback.onView Created).

[0376] Corresponding to the aforementioned process 3, notify the entry to display the updated business information.

[0377] Business updates include two cases. One is that the business party actively updates, and the other is that the service interaction and display framework automatically updates. As Figure 15 shown, the service interaction and display framework provides an update interface (Update Display Data()), and the business party can actively call the interface to complete data updates. The main steps are as follows:

[0378] S1501: The business party instructs the interactive display management module to update the display data.

[0379] S1502: The interactive display management module instructs the interactive display service module to update the display data.

[0380] S1503: The interactive display service module updates the display data lock.

[0381] The business party notifies the Interaction Display Manager of the business party to update the display data, obtains the latest Remote Views from the business party Provider, writes them into the quick application data App Clip Data, and passes in the quick application data.

[0382] S1504: The Interaction Display Service Module notifies the Interaction Display Record to update the Remote Views.

[0383] S1505: The Interaction Display Service Module notifies the Interaction Dispatch Control Module to call the display data update lock.

[0384] S1506: The Interaction Dispatch Control Module calls the display lock.

[0385] The Interaction Display Service of the Service Interaction and Display Framework updates the display data lock and updates the Remote Views into the Interaction Message. The Interaction Display Service calls the display data update lock, and the Interaction Dispatch Controller calls the display lock Dispatch Display Locked.

[0386] S1507: The Interaction Dispatch Control Module notifies the Entry Call Module to call the entry lock.

[0387] S1508: The Entry Call Module calls the display lock.

[0388] S1509: The Entry Call Module calls the lock.

[0389] S1510: The Entry Call Module calls the display.

[0390] S1511: The Entry Call Module creates the display information.

[0391] S1512: The Entry Call Module sends the display data.

[0392] S1513: The Entry Call Module notifies the entry call update.

[0393] S1514: The Interaction Dispatch Control Module ends the call to the display lock.

[0394] The interactive scheduling control traverses all notification entries corresponding to the interactive display records in sequence to complete the data update of each notification entry. During each traversal, the notification entry lock is called and the display information is sent to repackage the Remote Views into the interactive display information. When the notification entry receives the application update callback, it obtains the Remote Views from the input interactive display information and ends the call to the display information.

[0395] As Figure 16 It is a schematic diagram of the process for the interactive display framework to automatically update the Widget card display. It mainly includes:

[0396] S1601: The notification entry instructs the interactive display management module to display.

[0397] S1602: The interactive display management module notifies the interactive display service module that the notification entry is to be displayed.

[0398] S1603: The interactive display service module notifies the display mode.

[0399] S1604: The interactive display service module applies to the card display management service module for a card.

[0400] S1605: The card display management service module applies to the Widget management service module for Widget display.

[0401] S1606: The Widget management service module starts to lock the main update of the Widget.

[0402] S1607: The Widget management service module sends a message delay to the main threader.

[0403] S1608: The main threader instructs the Widget management service module to process the main update Widget lock.

[0404] S1609: The Widget management service module updates the Widget.

[0405] S1610: The Widget management service module sends an application Widget update broadcast to the application Widget host extension module.

[0406] S1611: The application Widget host extension module applies to the application Widget Provider for an update.

[0407] The service interaction and display framework also provides the interfaces of Notify Display Showed() and Notify Display Hidden(). When the notification entry side needs to call Notify Display Showed() when the card (capsule) is visible to the user, and call Notify Display Hidden() when the card (capsule) is not visible to the user, so as to inform the service interaction and display framework of the visibility of the card (capsule).

[0408] When the notification entry side calls Notify Display Showed() to inform the service interaction and display framework that a certain card (capsule) is visible to the user, the service interaction and display framework will set the automatic update period according to the importance and urgency level of the corresponding business of this card, and regularly (send an update broadcast through the native Widget mechanism) notify the service provider Provider to update the data.

[0409] In the Widget card scenario, the service provider Provider inherits from the native App Widget Provider. After receiving the update broadcast, the Provider will create Remote Views based on the latest business data, call the native application Widget management (AppWidget Manager) and update the application Widget (Update App Widget) and pass in the Remote Views. The subsequent process is similar to the business creation process: as the Host side in the native Widget system, after getting the RemoteViews, the display framework queries the expected notification entry in the interaction rule engine according to the importance and urgency level of this business, then matches it with the notification entry registration information, distributes the Remote Views to the corresponding notification entry, and finally the notification entry side uses the RemoteViews to complete the update process of the Widget card.

[0410] The display control method provided in this embodiment provides the display control process of Widget cards under the Widget architecture. As the host Host side, the service interaction and display framework obtains the Remote Views transmitted from the Provider side through the native Widget framework, distributes the Remote Views to the corresponding notification entries, and then each notification entry performs the display.

[0411] Embodiment 3

[0412] When the mobile phone executes the step of S503, the determined target of the mobile phone may include capsules and cards. The mobile phone needs to obtain the view files corresponding to the capsules and the view files corresponding to the cards.

[0413] In one example, the mobile phone supports the display of two display forms, namely Widget cards and capsules, and can simultaneously transmit the view files corresponding to the cards and the view files corresponding to the capsules. Under the Widget framework, the mobile phone is based on the Widget card data and can also implement data transmission in other display forms.

[0414] The notification entry displays Widget cards, and can obtain the view data directly transmitted through the Remote Views channel. By calling the Remote ViewsEx extension interface of the service interaction and display framework, the Widget cards can be displayed. The solution for the notification entry to display capsules is different from that for displaying Widget cards. The notification entry needs to obtain the business information that has not been serialized and display it according to the display rules of each notification entry. The display rules of the notification entry can be determined by each notification entry customarily, including hole avoidance display, black background display, etc., and can be specifically determined according to the preset rules for each notification entry of the electronic device to display capsules.

[0415] Continue to refer to the software framework such as Figure 10 The service interaction and display framework adds two function modules, Remote ViewsEx and APPClip Data. Remote ViewsEx is used to display Widget cards, and APP Clip Data is used to display capsules and multi-devices.

[0416] 1. Each business party Provider provides Remote Views of cards in multiple sizes by inheriting the application Widget provider, HnApp Widget Provider.

[0417] 2. Each business party Provider passes the capsules and multi-devices (such as watches) (App Clip Data) into the extended fields of Remote Views through the Remote ViewsEx extension interface.

[0418] 3. Each business party Provider passes the Remote Views to the interaction display service (Interaction DisplayService) of the service interaction and display framework through the relevant interfaces of the application Widget service, App Widget Service.

[0419] 4. The service interaction and display framework passes the card view data Remote Views or the quick application data App ClipData to the host.

[0420] 5. If the host gets the Remote Views, it can be converted into a normal card view through the Interaction Widget Manager.

[0421] 6. If the host gets the App Clip Data, it can parse its fields and display them according to the user experience (UX) design of the electronic device. The App Clip Data contains important business data, such as business icon logo, business progress, business brand color, etc.

[0422] If the first application business is a taxi-hailing business, the App Clip Data includes data such as the taxi-hailing business icon, license plate number, distance between the car and the passenger, estimated arrival time, current travel distance, total trip distance, car body color, and total types of taxis.

[0423] like Figure 17 As shown in FIG. 1 , it is a flow chart of the display control method provided in this embodiment, which illustrates the specific process of the display control method for simultaneously displaying cards and capsules. Figure 17 As shown, the provided display control method mainly includes the following steps:

[0424] S1701: The target notification portal initiates a registration application to the service interaction and presentation framework.

[0425] S1702: In response to a first application service generated by a first application program, the service interaction and presentation framework determines a target notification entry and a target display form corresponding to the first application service, where the target display form includes a card form and a capsule form.

[0426] S1703: The service interaction and presentation framework obtains the view files in the card form and capsule form corresponding to the business information of the first application business, and distributes them to the target notification portal.

[0427] S1704: The target notification portal displays the service information of the first application service in a card form and / or a capsule form according to the view file corresponding to the service information of the first application service.

[0428] The service interaction and display framework simultaneously obtains the view file corresponding to the card form and the view file corresponding to the capsule form, and transmits them to the target notification portal. The target notification portal can display the business information of the first application service only in the card form, or in the capsule form.

[0429] In one example, if Figure 18As shown, the target notification entry is the negative first screen. The negative first screen can display the service information of the first application service in the capsule form 1801 and the card form 1802 at the same time.

[0430] The mobile phone supports Widget cards, and the view file corresponding to the card form can be a view file in the RemoteViews format that supports Widget cards. The view file supported by the mobile phone for capsule display can be a view file in the App Clip Data format of the instant app. When performing data transmission, the mobile phone can transmit the view file in the Remote Views format and the App Clip Data format that supports capsule display to the target notification entry across processes through the Remote Views channel.

[0431] The mobile phone determines the target notification entry associated with the first application service, which can include at least two notification entries among the desktop, negative first screen, instant app center, notification center, control center, status bar, lock screen interface, and persistent display AOD interface. The mobile phone can display the entry interfaces of different notification entries in response to different user operations. When the mobile phone switches the entry interfaces of different notification entries, if the switched display notification entry belongs to the target notification entry, the service information of the first application service will be displayed in the notification entry.

[0432] The display control method provided in this embodiment can display the service information of the first application on multiple notification entries after the first application generates the first application service to reach the user. During the operation of the first application service, even if the user switches to multiple different entry interfaces through multiple operations, the mobile phone can continuously display the service information of the taxi service through different notification entries.

[0433] In one example, for the mobile phone to execute the steps of S1704, reference can be made to the steps of S203 and S204 in the foregoing embodiment. The mobile phone switches different target notification entries to display the service information of the first application service in response to the second operation and the third operation respectively.

[0434] It should be noted that the above-mentioned second operation and third operation are both used to refer to the operation of switching the entry interface of the notification entry input by the user. The second operation can be a voice input operation or a touch operation. The second operation and the third operation can be the same operation or different operations.

[0435] The second operation and the third operation are the same operation, indicating that the first notification entry and the second notification entry entered by the mobile phone are the same notification entry. That is to say, the mobile phone enters the entry interface of a notification entry in response to a user operation, and the mobile phone simultaneously displays the service information of the first application service in the form of a card and a capsule in the entry interface of the notification entry.

[0436] The second operation and the third operation are different operations. The first notification entry and the second notification entry that the mobile phone enters are different notification entries. However, both of these notification entries belong to the target notification entries associated with the first application service. Both of these notification entries can display the service information of the first application service, but only the display forms of the entry interfaces of these two types of notification entries are different. In response to the second operation, the mobile phone enters the entry interface of the first notification entry and displays the service information of the first application service in the form of a card. In response to the third operation, the mobile phone enters the entry interface of the second notification entry and displays the service information of the first application service in the form of a capsule.

[0437] As Figure 19 shown, it is a schematic flow diagram of the display control method executed by the software framework of the mobile phone. The electronic device simultaneously transmits card and capsule data, mainly including the following processes:

[0438] S1901: The target notification entry registers the card size and whether capsule data is required with the interaction display service module.

[0439] Corresponding to the notification entry registration operation in Process 1 above.

[0440] The notification entry registers the notification entry display function with the Interaction Display Service. At the same time, the notification entry also registers the specification size of the card it supports for display. The specification sizes of the card usually include 4*2, 4*2, 2*2, etc. The notification entry will select one of the specification sizes as the default specification size for its displayed card.

[0441] In addition, considering that some notification entries can display both cards and capsules, and some notification entries only support displaying cards and do not support displaying capsules. When the notification entry registers with the service interaction and display framework, it will also register whether it supports the capsule display function. Registering whether it supports the capsule display function means whether it requires the service provider to provide the data required for capsule display. S1902: The interaction display service module notifies the service provider Provider to generate the first application service (carrying the service ID and the identification information of the service provider Provider).

[0442] S1903: The interaction display service module notifies the application Widget service module to bind the application Widget.

[0443] S1904: The application Widget service module requests an update from the service provider Provider.

[0444] S1905: The service provider Provider creates card display files Remote Views of different specification sizes (4*2, 4*1, 2*2).

[0445] S1906: The service provider creates data for quick applications to be displayed on capsules, multiple devices, watches, etc.

[0446] S1907: The service provider notifies the Remote ViewsEx extension module to extend data (Remote Views, App Clip Data).

[0447] S1908: The Remote ViewsEx extension module sends the extended data to the Remote Views channel.

[0448] S1909: Via the Remote Views channel, the service provider notifies the application Widget service module to update the application Widget data.

[0449] S1910: The application Widget service module notifies the interactive display service module to update the application Widget.

[0450] S1911: The interactive display service module distributes Remote Views and App Clip Data to the target notification entry.

[0451] S1912: The target notification entry notifies the interactive Widget management module to create a host view (Create Host View).

[0452] S1913: The interactive Widget management module returns a card view to the target notification entry.

[0453] S1914: The target notification entry displays the View.

[0454] S1915: The target notification entry parses the App Clip Data and displays the capsule.

[0455] In one example, the service provider can create Remote Views corresponding to the registered specification dimensions according to the specification dimensions registered by the notification entry.

[0456] In another example, the service provider can also directly generate view files for cards corresponding to all specification dimensions, so that it is not necessary to distinguish the specification dimensions registered by each notification entry.

[0457] The service provider creates the files required for capsule display and inserts the service information into the quick application data (App ClipData). It should be noted that the data required for capsule, multiple device, or watch display are all service information that does not need to be serialized and can be transmitted through App Clip Data.

[0458] The business party Provider calls the extended interface Remote ViewsEX within the service interaction and display framework, and inserts the card view file Remote Views and the capsule view file App Clip Data as extended data (Set Hn ExaData) into the Remote Views channel within the native Widget framework, and updates them to the application Widget service (Update APP Widget Remote Views) within the service interaction and display framework in the form of application Widget data.

[0459] The application Widget service transfers the files received from the Remote Views channel within the native Widget framework to the interaction display service, and the interaction display service parses out the card view file Remote Views and the capsule view file App ClipData. The interaction display service distributes the parsed Remote Views and App Clip Data to the associated notification entry.

[0460] The notification entry can call the interactive Widget management module to create a Widget view, and then call the interactive Widget host view module to display the card. The notification entry can also parse the App Clip Data and display the capsule.

[0461] For the scenario where the notification entry needs to display both the Widget card and the capsule, the display control method provided in the embodiment of the present application inserts the card view file Remote Views and the capsule view file App Clip Data as extended data into the Remote Views channel, so as to realize the cross-process transmission of the service information required for capsule display to the service interaction and display framework in synchronization. After the service interaction and display framework receives the data transmitted by the intelligent module, it respectively parses out the serialized data and the basic service information, and displays the Widget card and the capsule respectively. The service interaction and display framework can also provide the basic service information to the multi-device notification entry, and the multi-device notification entry displays the service information in other display forms.

[0462] Embodiment 4

[0463] When the mobile phone executes S202 in the foregoing Embodiment 1, the target notification entry determined for the first application service by the mobile phone may also include the notification entry provided by other devices outside the mobile phone itself. When the mobile phone executes the display operation of S203 or S204 in the foregoing Embodiment 2, it is the display operation of the notification entry of another device in Haikou City.

[0464] For example, the service information of an order generated by a ride-hailing application on a mobile phone can be transferred to and displayed on a watch or a car stereo connected to the mobile phone. For ease of description, in this embodiment, an external device refers to one or more devices connected to the mobile phone that support the display function of a notification entry.

[0465] As Figure 20 shown, it is a schematic diagram of the interaction between a mobile phone and a watch. The service information of the first application service that has been generated can be displayed on the mobile phone 2001 through a card. The mobile phone 2001 can also transfer the service information to the watch 2002 communicatively connected to the mobile phone 2001 for display. The watch can provide notification entries such as a desktop and a notification center, and each notification entry can choose a display form such as a card and / or a capsule to display the service information.

[0466] As Figure 21 shown, it is a schematic diagram of the interaction between a mobile phone, a watch, and a car stereo. The service information of the first application service that has been generated can be displayed on the mobile phone 2101 through a card. The mobile phone 2101 can also transfer the service information to the watch 2102 communicatively connected to the mobile phone 2101 for display, or transfer it to the car stereo 2103 communicatively connected to the mobile phone 2101 for display. External devices such as the watch and the car stereo can provide notification entries such as a desktop and a notification center, and each notification entry can choose a display form such as a card and / or a capsule to display the service information.

[0467] In one example, the mobile phone can use the external device as a notification entry. In this case, the mobile phone does not need to distinguish the number and type of notification entries supported on the external device. Regardless of the number of notification entries supported by the external device, the mobile phone can only use the external device as a notification entry, provide the service information corresponding to one notification entry to the watch, and then the watch distributes the received service information to each notification entry for display according to this one piece of service information. The data transmission scheme of using the external device as a notification entry by the mobile phone can reduce the communication frequency and the total amount of data transmission between the mobile phone and the watch, and improve the data transmission efficiency across devices.

[0468] In another example, the mobile phone can also distinguish each notification entry that can be provided on the external device, and when providing service information to the external device, distinguish different notification entries to provide the corresponding service information. For example, if the external device supports three notification entries, namely a desktop, a control center, and a notification center, then the watch can provide the service information corresponding to these three notification entries to the external device respectively. In this way, the operation of the external device generating and distributing service information for multiple notification entries can be omitted, reducing the related work of the external device.

[0469] As Figure 22As shown in the figure, it is a schematic diagram of the connection between a mobile phone and an external device. The mobile phone includes a smart side, a service interaction and display framework, a notification entry, and a cross-device communication module. Among them, the smart side includes a smart module, which is used to notify the service interaction and display framework to generate the first application service and the service information that needs to be called to the notification entry for display. The service interaction and display framework distributes the service information to the notification entry associated with the first application service, and the notification entry displays it. It should be noted that the notification entry here refers to the notification entry of the mobile phone itself, such as the desktop, the negative first screen, etc.

[0470] The mobile phone also includes a cross-device communication module, and a corresponding cross-device communication serialization interface (Android ARchive, AAR) is also included in the service interaction and display framework. The service interaction and display framework transmits data to the cross-device communication module through the cross-device communication serialization interface, and transmits the service information to the external device through the cross-device communication module. In a specific example, the external device can be a watch, and the cross-device communication module can be Synergy TM , then the cross-device communication serialization interface in the interaction display module can be Synergy TM AAR. The cross-device communication module can implement data transmission through communication methods such as Bluetooth, Wi-Fi, and cellular networks.

[0471] The cross-device communication module can provide the mobile phone with the ability to perform cross-device communication with external devices such as watches. In addition, the cross-device communication module can also monitor the connection status between the mobile phone and the external device to ensure the transmission and reach efficiency of information. In addition, the cross-device communication module can also receive instructions sent by the external device to the mobile phone to implement functions such as entry registration, information acquisition, and information update.

[0472] When the mobile phone executes the display control method provided in this embodiment, in response to the first application service generated by the first application program, it transmits the service information across devices to the external device, and the service information is displayed on the external device. The cross-device transmission process between the mobile phone and the external device mainly includes an active trigger operation initiated by the mobile phone and a push request actively applied by the external device. The scenarios where the mobile phone actively initiates an active trigger request can include scenarios such as service creation, update, and deletion. The scenarios where the external device actively applies for a push request can include scenarios such as when the watch is disconnected and reconnected, and it applies to send service information.

[0473] The service interaction and display framework of the mobile phone integrates the AAR package provided by the cross-device communication module. Through the serialization interface provided by the AAR package, the service information provided by the service interaction and display framework can be serialized and sent to the cross-device communication module, and then the cross-device communication module sends it to the external device. The external device can parse the original service information according to the pre-stored protocol and render the service information into forms such as cards and capsules for display.

[0474] In the solution where the mobile phone displays service information at the notification entry on the mobile phone itself, the service interaction and display framework only needs to set up notification entry distributors, and each notification entry distributor corresponds to a notification entry. After the interaction display module obtains the service information provided by the service provider (Provider), it calls each notification entry distributor to distribute the service information to each notification entry.

[0475] As Figure 23 shown, it is a schematic flowchart of the display control method provided by the embodiment of the present application, which involves the process of the mobile phone transmitting service information to an external device. The display control method provided by this embodiment adds a solution for sending service information on the mobile phone side to multiple devices such as watches for display. The provided display control method mainly includes the following processes:

[0476] S2301: In response to a first operation on the display interface of the first application, display the indication information of the first application service of the first application.

[0477] S2302: Determine the target notification entry and the target external device corresponding to the first application service.

[0478] S2303: During the operation of the first application service, in response to a second operation, send the service information of the first application service to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service.

[0479] S2304: In response to a third operation, display the service information of the first application service on the entry interface of the target notification entry.

[0480] This embodiment involves information interaction between two electronic devices. For ease of description, the external device that establishes a communication connection with the mobile phone is defined as the target device. The target device can be a wearable device such as a watch, or the target device can also be a car machine. The target device can also provide one or more notification entries to display the service information of the application service generated by the first electronic device.

[0481] After the mobile phone generates a taxi-hailing service, it sends the service information of the taxi-hailing service to the watch, and the watch can display the service information of the taxi-hailing service in the form of a card or a capsule at entrances such as the desktop and the notification center.

[0482] The mobile phone can, in response to a second operation, send the service information of the first application service to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service. The mobile phone can also, in response to a third operation, display the service information of the first application service on the entry interface of the target notification entry. The second operation and the third operation can be the same operation or different operations.

[0483] The display control method provided in this embodiment can display the service information of the first application at multiple notification entrances after the first application generates the first application service. It can not only include the target notification entrances on the mobile phone itself, but also be transferred to the second type of notification entrances of external devices such as watches for display, so as to reach users more comprehensively.

[0484] The above embodiment describes the specific implementation process of the display control method from the perspective of the first electronic device, i.e., the mobile phone. This embodiment can also provide the specific real-time process of the display control method from the perspective of the target device, i.e., the watch. The specific process is as follows:

[0485] The target device receives the service information of the first application service from the first electronic device; wherein, the first application service is generated by the first application program of the first electronic device;

[0486] In response to the fourth operation, the service information of the first application service is displayed on the entrance interface of the notification entrance provided by the target device;

[0487] Among them, the third notification entrance is one of the second type of notification entrances associated with the first application service in the target device; the second type of notification entrances all include at least one of the notification entrances on the desktop, the negative first screen, the quick application center, the notification center, the control center, the status bar, the lock screen interface, and the continuously displayed AOD interface.

[0488] As Figure 24 shown, it is a schematic diagram of a mobile phone supporting multi-device transmission and display. In the solution where the mobile phone transmits service information across devices to the entrance interface of other external devices for display, the notification entrances distributed by the service interaction and display framework include not only the notification entrances on the mobile phone itself, but also the notification entrances of external devices. Then, the distributor for distributing service information by the service interaction and display framework can include a device-level distributor. Each device-level distributor corresponds to an external device of the mobile phone, and the device-level distributor is used to distribute the service information obtained by the service interaction and display framework to the external devices of the mobile phone.

[0489] A mobile phone can set a virtual notification entry for an external device to reduce the data transmission volume from the mobile phone to the external device. For example, if the external device is a watch, the mobile phone uses Watch Dispatcher as the abstraction of the virtual notification entry for the watch. Watch Dispatcher is similar to the Entrance Dispatcher for the native entry of the mobile phone. It should be noted that the virtual notification entry abstracted for the watch may not be exactly the same as the notification entry of the mobile phone itself. Since the watch itself will pre-register the display function through the cross-device communication module, the watch does not need to register its display function with the service interaction and display framework like a notification entry. When the cross-device communication module between the mobile phone and the watch detects that they are in a communication connection state, the mobile phone can transmit service information to the watch through the cross-device communication module for display. If the cross-device communication module detects that the communication connection state between them is disconnected, the mobile phone cannot currently transmit service information to the watch through the cross-device communication module for display.

[0490] Continue as Figure 24 As shown, the watch data is first passed into the app clip data and then provided to the service interaction and display framework through the interaction message. The app clip data includes card data, capsule data, and watch data. The interaction message includes various types of data, including service type, service name, service ID, service state, etc.

[0491] The scope hierarchy of the objects called by the electronic device successively includes the display form, notification entry, and device. The corresponding display records in the electronic device also include display records, entry display records, device display records, and interaction display records. Among them, the display record is an atomic-level record and can be uniquely determined by the device + entry + form. The display record includes the entry display record transmitted upward and multiple parameter fields, such as Enable, Delete, Show On Top, Update Time, Create Time, and Cur State, which are the display record states.

[0492] The Entrance Display Record is an entrance-level service record that may need to be sent to multiple forms. The Entrance Display Record includes device display records transmitted upward, notification entrances, display records, etc. The corresponding display record can be found through the Array Map function according to the Shape.

[0493] The Device Display Record is a device-level service record that may need to be sent to multiple entrances. The Device Display Record includes the Device Type, Interaction Display Record transmitted upward, and Entrance Display Record transmitted downward. The corresponding Entrance Display Record of the notification entrance can be found through the Array Map function according to the Device Display Record.

[0494] The Interaction Display Record is an atomic service record that needs to be sent to multiple devices. The interaction display information includes interaction information, Interaction Display Record, and Device Display Record. The corresponding Device Display Record can be found through the Array Map function according to the Device Type.

[0495] The notification entrances of the mobile phone include AOD, Lock Screen, Launcher, Nagative Screen, Notification Center, Control Center, Global, Magic Gate, Multiple Device, etc. The Multiple Device includes the external watch as a notification entrance.

[0496] When the mobile phone performs Entrance Dispatcher, it will verify the EntranceRegistration Info and Registered status, and call the display record to find the corresponding Entrance Display Record. When the watch is called, it will call the entrance.

[0497] When the mobile phone performs Device Dispatcher, it will verify the device type and entrance call, find the entrance calls corresponding to each notification entrance included in the device, and hand them over to the interaction scheduling control.

[0498] Such as Figure 25As shown in the figure, it is a schematic flow chart of a display control method provided by an embodiment of the present application for transmitting service information to an external device. The intelligent side includes an intelligent module and an interaction display management module (Interaction Display Manager), and the service interaction and display framework includes an interaction display service module (Interaction Display Service), a card display implementation module (Card Display Internal), an interaction scheduling control module (Interaction Dispatcher Controller), a Widget management service module (Widget Manage Service), a watch call module (Watch Dispatcher), a channel unit module (Channel Client), and a channel listener (ChannelListener). The cross-device communication module includes a channel service providing module (Channel server Provider). In this embodiment, the transmission of the watch data Watch Data required by the watch depends on the solution of the Widget service for transmitting RemoteViews and the quick application data App Clip Data.

[0499] S2501: The intelligent module notifies the interaction display management module to start displaying.

[0500] S2502: The interaction display management module notifies the interaction display service module to start displaying.

[0501] S2503: The interaction display service module notifies the interaction scheduling control module to create an interaction display record lock.

[0502] S2504: The interaction scheduling control module returns the interaction display record lock to the interaction display service module.

[0503] S2505: The interaction display service module notifies the card display implementation module to create a card.

[0504] S2506: The card display implementation module notifies the Widget management service module to create a Widget card.

[0505] S2507: The Widget management service module returns a card display call to the interaction display service module.

[0506] S2508: The interaction display service module notifies the interaction scheduling control module to call the display start lock.

[0507] S2509: The interaction scheduling control module calls the display start lock.

[0508] S2510: The Interactive Scheduling Control Module notifies the Watch Invocation Module to invoke display locking.

[0509] S2511: The Watch Invocation Module sends information to the Channel Unit.

[0510] S2512: The Channel Unit confirms the call to the Service Provider.

[0511] S2513: The Channel Unit calls the Service Provider.

[0512] S2514: The Channel Service Provision Module binds to the Service Provider.

[0513] S2515: The Channel Unit obtains the notification information result.

[0514] S2516: The Channel Unit applies to the Channel Information Provision Module for the information result.

[0515] S2517: The Channel Information Provision Module returns the information result to the Channel Unit.

[0516] S2518: The Channel Unit sends the information result to the Watch Invocation Module.

[0517] S2519: The Watch Invocation Module sends the information result to the Interactive Scheduling Control Module.

[0518] S2520: The Interactive Scheduling Control Module ends the invocation of display locking.

[0519] The service provider will pre-determine whether the notification entry through which the service information of the application service it generates flows includes an external device, such as a watch. Then when the intelligent service starts to display the notification, the input parameters at this time need to include the watch data Watch Data, which is encapsulated and serialized by the service provider according to the communication protocol between the service provider and the watch.

[0520] When the service provider Provider constructs the App Clip Data, if it is determined that the service information needs to flow to the watch for display, then when transmitting the Remote Views, the Watch Data will be added to the App Clip Data. If the importance and urgency level of the service matches the watch notification entry, the multi-device transfer process will be followed when the service is issued. The overall interaction process specifically includes:

[0521] The intelligent service notifies the interactive display management to start displaying, and the interactive information (Interaction Message) in the input parameters contains the quick application data App Clip Data, which is transmitted to the service interaction and display framework.

[0522] Within the service interaction and display framework, the interaction display service creates an interaction display record locked (CreateInteraction Display Record Locked) to the interaction scheduling control. The interaction display service starts to create a card. Depending on the card type, it enters different service processes. The Widget will use the Widget management service to handle the creation process of the Widget card.

[0523] The service interaction and display framework first obtains the Remote Views object through the Widget framework, and then enters the distribution process. If the switch of this notification entry for the external device is turned on and the business-side Provider provides watch data, it enters the watch transfer process.

[0524] Considering that the Watch Data required for watch display depends on the Remote Views required for card display, at this distribution node on the mobile phone, usually to ensure that the watch data can be displayed normally, it will first refer to whether the card data can be displayed normally. After the card display on the mobile phone is implemented to create a card, it will further trigger the notification to the Widget management service to generate the operation of creating a Widget and enter the watch transfer process.

[0525] Of course, if the normal display of the watch data is not considered, the mobile phone can also not refer to the display status of the card data and enter the watch transfer process after obtaining the watch data.

[0526] After entering the watch transfer process, the interaction scheduling control calls the dispatch display start locked (Dispatch DisplayStart Locked) watch call, sends service information to the cross-device communication module through the channel unit, and realizes the transfer of service information from the mobile phone to the watch. After the watch receives the service information, it renders and displays according to its own view display logic.

[0527] Under normal circumstances, the way the service interaction and display framework of the mobile phone transmits service information to the watch through the cross-device communication module is single-item push. That is to say, even if there are multiple application service information on the mobile phone that need to be transferred to the same watch, the mobile phone will perform single-item push for the service information of each application service respectively, and distinguish that the creation, update, deletion and other service status changes of the service information of each application service will be pushed item by item. Generally speaking, the service from the mobile phone to the watch is one-way push service, mainly for the mobile phone to notify the watch to create display, update display, and delete display.

[0528] Then, if the mobile phone and the watch are disconnected and then reconnected, during this process, the business status of some application services may have changed, such as the end, status update, and addition of application services. If the mobile phone only notifies the watch of the newly generated service information after reconnection, there may be abnormal display of some service information. For example, the service information of an ended application service cannot be deleted, the service information of a newly added application service cannot be displayed, and the service information of an existing application service cannot be accurately updated. This will be illustrated by examples below.

[0529] For example, before the mobile phone and the watch are disconnected, there is a taxi service 1 (the driver has accepted the order and is 2 kilometers away from the passenger) and a food delivery service 2 (waiting for the merchant to accept the order). The mobile phone pushes the service information of taxi service 1 and food delivery service 2 to the watch separately in single items, and the watch will display the service information of taxi service 1 and the service information of food delivery service 2 respectively.

[0530] The mobile phone and the watch are disconnected. For taxi service 1, the service status changes from the driver has accepted the order to the driver has cancelled the order, and taxi service 1 ends. For food delivery service 2, the service status changes from waiting for the merchant to accept the order to the rider is delivering.

[0531] The mobile phone and the watch are reconnected. At this time, since taxi service 1 has ended, according to the single-item push rule, the service interaction and display framework will no longer notify the watch to delete the service information of taxi service 1 displayed. One possible situation is that the watch continuously displays the service information of taxi service 1 and stays in the service status where the driver has accepted the order or the service abnormal status. Or, the watch may also automatically clear the service information in the abnormal status according to the pre-set automatic clearing rule. Both of these processing solutions may cause abnormal display of service information on the watch and give wrong guidance to users.

[0532] The solution provided in the embodiment of the present application, when the mobile phone and the watch are reconnected after each disconnection, executes a full-volume push solution instead of a single-item push solution. The full-volume push solution can be understood as pushing the service information of all current application services to the watch in single items at the same time. As Figure 26 shown, the watch sends a full-volume push request to the service interaction and display framework of the mobile phone through the cross-device communication module. After the channel listener of the service interaction and display framework receives the full-volume push request sent by the watch, it calls all business records (Dispatch All Records) and sends them to the watch in full volume (Dispatch ToWatch).

[0533] S2601: The channel service providing module sends a full-volume push request to the channel listener.

[0534] S2602: The channel listener notifies the watch call module to call all records.

[0535] S2603: The watch calling module calls the watch.

[0536] S2604: The watch calling module sends full information to the channel unit.

[0537] When the watch is disconnected from the mobile phone and then reconnected, the watch can send a full push request of the watch to the mobile phone, requesting the mobile phone to push all the service information of all the current existing services to the watch in full. In this case, after the watch receives the service information pushed in full by the mobile phone, it checks the currently displayed service information. It deletes and displays the service information of the application services that have ended, updates the service information whose service status has changed, and creates and displays the service information of the newly added application services.

[0538] In specific implementation, after the mobile phone is disconnected from and then reconnected to the watch, it can be the watch that sends a full push request to the mobile phone. In this way, the watch side actively initiates a full push request according to the display requirements, minimizing unnecessary data transmission on the premise of ensuring comprehensive data. Of course, in other implementation manners, the mobile phone can also actively send full service information to the watch, enabling the watch to check and update the displayed service information according to the full service information.

[0539] The message sent by the mobile phone to the watch can include two bytes Byte[]: the file header Header and the file body Data.

[0540] Among them, the format of the file header can be as shown in Table 3 below, and the types and descriptions of each field in the file header can be as shown in Table 4.

[0541] Table 3

[0542]

[0543] Table 4

[0544]

[0545] Most of the data provided by the mobile phone to the watch is the service information provided by the service provider Provider. The service interaction and display framework calls Watch Data.getData() to obtain data from the service provider Provider. In some cases, the watch data needs to be created by the service interaction and display framework and then sent to the watch. For example, the watch has created the display of the corresponding application service, the important and urgent level of the application service has changed, and the virtual notification entry of the associated watch is no longer used as the notification entry for displaying service information, that is, the transfer plan from the mobile phone to the watch is closed. Or, the application service ends, and the display of the corresponding application service created by the watch needs to be deleted.

[0546] As shown in Table 5, it is a mapping table of the importance and urgency levels of application services and the interaction specifications of the watch. It should be noted that this is just an example here and does not limit the specific transfer scheme between the mobile phone and the watch.

[0547] Table 5

[0548]

[0549]

[0550] As shown in Table 5, when waiting for the driver to accept the order for the taxi-hailing service, the importance and urgency level is L21, and at this time, the taxi-hailing service does not need to be displayed on the watch. When a driver accepts the order, the importance and urgency level becomes L24. At this time, the service interaction and display framework needs to send information about creating a service to the watch so that the watch can display the taxi-hailing information. If the driver cancels the order, it may cause the importance and urgency level to drop back to L21, and the current importance and urgency level does not require the watch to display. Then, based on the information about creating a service sent by the service interaction and display framework to the watch before, the mobile phone needs to call the service interaction and display framework to send a notice to the watch to delete the service information, so as to end the display process of the taxi-hailing service on the watch.

[0551] The messages sent from the mobile phone to the watch include a file header and a file body. The mobile phone usually stores instructions and data in the file body to ensure the security of the instructions and data. For the notice sent from the mobile phone to the watch to delete the display of service information, it can be directly stored in the file header. In this way, the watch only needs to parse the file header to obtain the notice to delete the display of service information, saving the file parsing operation.

[0552] In summary, the display control method provided by the embodiment of the present application enables the electronic device to present the service information of application services generated by each application program in the form of notifications on the entry interfaces of each notification entry based on the notification framework of the native system, and can match different entry display schemes according to the importance and urgency levels of different application services, facilitating users to receive messages and make corresponding processing in various scenarios. Users can see the latest service information on each entry interface such as the desktop, notifications, AOD, the negative first screen, the lock screen, and even wearable devices, etc., without having to find the corresponding application interface to obtain the service information. It breaks the traditional situation of "people looking for services" and truly realizes "services looking for people", greatly improving the user experience.

[0553] In addition, an embodiment of the present application further provides an electronic device, which may be the aforementioned first electronic device or a target device. The electronic device includes a display, a memory, and a processor, and both the display and the memory are coupled to the processor. The memory stores computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the display control method provided in the foregoing embodiment. In addition to these main components, the electronic device further includes components for implementing basic functions, which will be described in detail below in combination with Figure 27 for specific illustration.

[0554] As Figure 27 shown is a schematic structural diagram of an electronic device 2700 provided by an embodiment of the present application. Among them, the electronic device 2700 may include a processor 2710, a memory 2720, a display 2750, a USB interface 2730, a charging management module 2740, a power management module 2741, a battery chip 2742, an antenna, a communication module 2760, an audio module 2770, a speaker 2770A, a receiver 2770B, a microphone 2770C, a headphone jack 2770D, a camera 2780, etc.

[0555] The structure schematically shown in the embodiment of the present invention does not limit the electronic device 2700. It may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0556] The processor 2710 may include one or more processing units. For example, the processor 2710 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), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0557] The above-mentioned controller may be a decision maker that commands the various components of the electronic device 2700 to work in coordination according to instructions. It is the nerve center and command center of the electronic device 2700. The controller generates operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

[0558] A memory can also be set in the processor 2710 for storing instructions and data. In some embodiments, the memory in the processor 2710 is a cache memory that can save the instructions or data just used or recycled by the processor 2710. If the processor 2710 needs to use the instructions or data again, it can directly call them from the memory. This avoids repeated accesses, reduces the waiting time of the processor 2710, and thus improves the efficiency of the system.

[0559] In some embodiments, the processor 2710 may include interfaces. The interfaces may include an Inter-Integrated Circuit (I2C) interface, an Inter-Integrated Circuit Sound (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a General-Purpose Input / Output (GPIO) interface, a SIM interface, and / or a USB interface, etc.

[0560] The interface connection relationships between the modules illustrated in the embodiments of the present invention are only illustrative and do not constitute a structural limitation on the electronic device 2700. The electronic device 2700 may adopt different interface connection methods in the embodiments of the present invention, or a combination of multiple interface connection methods.

[0561] The charging management module 2740 can be a rechargeable battery or a disposable battery. When it is a rechargeable battery, it can receive charging input through a charger. Herein, the charger can be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 2740 can receive the charging input of the wired charger through the USB interface 2730. In some embodiments of wireless charging, the charging management module 2740 can receive the wireless charging input through the wireless charging coil of the electronic device 2700. While charging the battery chip 2742, the charging management module 2740 can also supply power to the electronic device 2700 through the power management module 2741.

[0562] The power management module 2741 is used to connect the battery chip 2742, the charging management module 2740, and the processor 2710. The power management module 2741 receives inputs from the battery chip 2742 and / or the charging management module 2740 and supplies power to the processor 2710, the memory 2720, the display 2750, the camera 2780, the communication module 2760, etc. The power management module 2741 can also be used to monitor parameters such as the capacity of the charging management module, the number of charge-discharge cycles of the charging management module, and the health status (leakage, impedance) of the charging management module. In some embodiments, the power management module 2741 can also be disposed in the processor 2710. In some embodiments, the power management module 2741 and the battery chip 2742 can also be disposed in the same device.

[0563] The wireless communication function of the electronic device 2700 can be implemented by an antenna, a radio frequency module, the communication module 2760, a modem, and a baseband processor, etc.

[0564] The antenna is used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 2700 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the cellular network antenna can be multiplexed as the wireless local area network diversity antenna. In some embodiments, the antenna can be used in combination with a tuning switch. The radio frequency module can provide a communication processing module for wireless communication solutions including 2G / 3G / 4G / 5G, etc. applied to the electronic device 2700.

[0565] The communication module 2760 can provide a communication processing module for wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. applied to the electronic device 2700. The communication module 2760 can be one or more devices integrating at least one communication processing module. The communication module 2760 receives electromagnetic waves via the antenna, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 2710. The communication module 2760 can also receive the signals to be sent from the processor 2710, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna for radiation.

[0566] In some embodiments, the antenna of the electronic device 2700 is coupled to the radio frequency module, and the antenna is coupled to the communication module 2760, such that the electronic device 2700 can communicate with the network and other devices through wireless communication technologies. The wireless communication technologies may include Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. GNSS may include Satellite Based Augmentation Systems (SBAS), Global Navigation Satellite System (GLONASS), BeiDou navigation Satellite system (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0567] The electronic device 2700 implements the display function through the GPU, the display screen 2750, and the application processor, etc. The GPU is a microprocessor for image processing, which is connected to the display 2750 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 2710 may include one or more GPUs, which execute program instructions to generate or change the display information.

[0568] The display screen 2750 is used to display images, videos, etc. The display 2750 includes a display panel. The display panel can adopt 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 Micro LED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 2700 may include one or N displays 2750, where N is a positive integer greater than 1.

[0569] The electronic device 2700 can implement the shooting function through the ISP, the camera 2780, the video codec, the GPU, the display screen, and the application processor, etc.

[0570] The electronic device 2700 can implement the audio function through the audio module 2770, the speaker 2770A, the receiver 2770B, the microphone 2770C, the headphone jack 2770D, and the application processor, etc. For example, music playback, recording, etc.

[0571] The keys 2790 include a power-on key, a lock screen key, a volume key, etc. The keys 2790 can be mechanical keys or touch keys. The electronic device 2700 receives the input of the keys 2790 and generates a key signal input related to the user settings and function control of the electronic device 2700.

[0572] The motor 2791 can generate a vibration prompt. The motor 2791 can be used for incoming call vibration prompts and can also be used for touch vibration feedback. For example, touch operations on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. Touch operations on different areas of the display screen 2750 can also correspond to different vibration feedback effects. Different application scenarios (such as time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0573] The display control methods in the foregoing embodiments can all be implemented in the electronic device 2700 with the above hardware structure.

[0574] Based on the above embodiments, an embodiment of the present application further provides a display control device, which includes a processor for executing the display control method provided in the above embodiments.

[0575] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, which, when running on a computer, causes the computer to execute the display control method provided in the above embodiments.

[0576] An embodiment of the present application further provides a computer program product containing instructions, which, when running on a computer, enables the computer to execute the display control method provided in the above embodiments.

[0577] For the specific implementation manners of the electronic device, display control device, computer-readable storage medium, and computer program product containing instructions provided in the embodiments of the present application, and the technical effects brought thereby, reference may be made to the specific implementation process of the display control method provided in the foregoing embodiments and the technical effects brought thereby, which will not be elaborated herein.

[0578] In some embodiments, through the description of the above implementation manners, those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0579] In each embodiment of the embodiments of the present application, each functional unit can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0580] 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.

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

Claims

1. A display control method, characterized in that Applied to an electronic device, the method includes: In response to a first operation on a first interface of a first application, display indication information of a first application service of the first application; wherein, the indication information indicates that the first application service has been enabled; Determine a target notification entry and a target device corresponding to the first application service; During the running of the first application service, in response to a second operation, send service information of the first application service to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service; In response to a third operation, display the service information of the first application service on the entry interface of the target notification entry.

2. The display control method according to claim 1, wherein The target notification entry includes at least one of a desktop, a negative first screen, a notification center, a control center, a status bar, a lock screen interface, an AOD interface, and a quick application center.

3. The display control method according to claim 1, wherein The step of determining the target notification entry and the target external device corresponding to the first application service includes: During the running of the first application service, determine the corresponding first importance and urgency level according to the first service state where the first application service is currently located; Determine the target notification entry and the target external device currently corresponding to the first application service according to the first importance and urgency level.

4. The display control method according to any one of claims 1 to 3, characterized in that, Before the step of sending the service information of the first application service to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service, the method further includes: Determine the target display form corresponding to the first application service; wherein, the target display form includes a first display form and / or a second display form; The step of, during the running of the first application service, in response to a second operation, send the service information of the first application service to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service includes: In response to the second operation, send the service information of the first application service and a view file corresponding to the first display form to the target device, so that the entry interface of the notification entry of the target device displays the service information of the first application service in the first display form; The step of, in response to a third operation, display the service information of the first application service on the entry interface of the target notification entry includes: In response to the third operation, display the service information of the first application service on the entry interface of the target notification entry in the second display form.

5. The display control method according to claim 4, wherein The first display form and the second display form include at least one of a card, a capsule, and a banner.

6. The display control method according to claim 4 or 5, characterized in that The step of determining the target display form corresponding to the first application service includes: Obtain one or more display forms corresponding to the first application, one or more display forms corresponding to the target notification entry, and one or more display forms corresponding to the target device; Regarding the same display forms among one or more display forms corresponding to the first application and one or more display forms corresponding to the target device, use them as the first display form; and, regarding the same display forms among one or more display forms corresponding to the first application and one or more display forms corresponding to the target notification entry, use them as the second display form.

7. The display control method according to any one of claims 1 to 6, characterized in that The method further includes: In response to the electronic device reconnecting after disconnecting from the target device, send full-volume service information to the target device; Wherein, the full-volume service information is used for the target device to adjust the service information displayed on the entry interface of the target device's notification entry; the full-volume service information includes the service information of all application services currently enabled in the electronic device.

8. The display control method according to claim 7, wherein The step of sending the full-volume service information to the target device includes: In response to receiving a full-volume push request from the target device, send the full-volume service information to the target device.

9. The display control method according to claim 3, wherein The step of determining the current target notification entry corresponding to the first application service according to the first importance and urgency level includes: From the pre-stored entry mapping table, find the notification entry corresponding to the first importance and urgency level as the current target notification entry and target device corresponding to the first application service; wherein, the entry mapping table stores different notification entries and different target devices corresponding to different importance and urgency levels.

10. The display control method according to any one of claims 1 to 9, characterized in that, The step of, during the operation of the first application service, in response to a second operation, send the service information of the first application service to the target device so that the entry interface of the target device's notification entry displays the service information of the first application service further includes: In response to the update of the service information of the first application service, send the updated service information of the first application service to the target device so that the entry interface of the target device's notification entry displays the updated service information of the first application service; The step of, in response to a third operation, display the service information of the first application service on the entry interface of the target notification entry further includes: In response to the update of the service information of the first application service, display the updated service information of the first application service on the entry interface of the target notification entry.

11. The display control method according to claim 9, wherein, The step of determining the current target notification entry corresponding to the first application service according to the first importance and urgency level further includes: In response to the update of the service state of the first application service, determine the second importance and urgency level corresponding to the updated second service state according to the updated second service state of the first application service; According to the second importance and urgency level corresponding to the second service state, update the target notification entry and target device corresponding to the first application service.

12. The display control method according to any one of claims 1 to 11, characterized in that, After the step of, during the operation of the first application service, in response to a second operation, send the service information of the first application service to the target device so that the entry interface of the target device's notification entry displays the service information of the first application service, the method further includes: In response to the end of the operation of the first application service, send an indication message to stop displaying to the target device, so that the entry interface of the notification entry of the target device stops displaying the service information of the first application service; After the step of displaying the service information of the first application service on the entry interface of the target notification entry in response to the third operation, the method further includes: In response to the end of the operation of the first application service, stop displaying the service information of the first application service at the target notification entry.

13. The display control method according to any one of claims 1 to 12, characterized in that, The step of sending the service information of the first application service to the target device includes: Sending a view file in the App Clip Data format corresponding to the service information of the first application service to the target device; Before the step of displaying the service information of the first application service on the entry interface of the target notification entry, the method further includes: Sending a view file in the Remote Views format to the target notification entry.

14. A display control method, characterized in that, Applied to a first device, the first device is connected to an electronic device; the display control method includes: Receiving the service information of the first application service sent by the first device; wherein, the first application service is generated by a first application program of the electronic device; In response to a fourth operation, display the service information of the first application service on the entry interface of the notification entry of the first device.

15. The display control method according to claim 14, characterized in that, The notification entry of the first device includes at least one of a desktop, a negative first screen, a quick application center, a notification center, a control center, a global, a lock screen interface, and a persistent display AOD interface.

16. The display control method according to claim 14 or 15, characterized in that The step of displaying the service information of the first application service includes: In response to the updated service information of the first application service sent by the electronic device, display the updated service information of the first application service.

17. The display control method according to any one of claims 14 to 16, characterized in that, The method further includes: Receiving the indication message to stop displaying sent by the electronic device, and stopping displaying the service information of the first application service on the entry interface of the notification entry of the first device.

18. The display control method according to any one of claims 14-17, characterized in that, The method further includes: In response to the restoration of the connection after the first device is disconnected from the electronic device, send a full-volume service push request to the electronic device; Receiving the full-volume service information sent by the electronic device, and updating the service information displayed on the entry interface of the notification entry of the first device entry according to the full-volume service information; wherein, the full-volume service information is the service information of all the application services currently enabled in the electronic device.

19. The display control method according to claim 18, characterized in that, The step of updating the service information displayed on the entry interface of the notification entry of the first device entry according to the full-volume service information includes: If the full-volume service information includes the service information of the first application service, update the service information of the first application service displayed on the entry interface of the notification entry of the first device; If the full-volume service information does not include the service information of the first application service, stop displaying the service information of the first application service on the entry interface of the notification entry of the first device.

20. The display control method according to any one of claims 14-19, characterized in that, The first device is a wearable device, and the wearable device includes a smart watch.

21. An electronic device, characterized in that, The electronic device includes a display, a memory, and a processor, and both the display and the memory are coupled to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the display control method according to any one of claims 1 to 20.

22. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and when it runs on a computer, it causes the computer to execute the display control method according to any one of claims 1 to 20.

Images