Display control method, electronic device, and computer readable storage medium

Abstract

The present application relates to the technical field of terminals, and provides a display control method, an electronic device, and a computer readable storage medium. In order to solve the technical problem that operation of viewing related data of application services is tedious, the electronic device calls multiple notification entrances to display application services such as a desktop, a minus one screen, a quick application center, a notification center, a control center, a status bar, a lock screen interface, and an always on display (AOD) interface. The electronic device determines target notification entrances for displaying service information for the application services, and in response to different operations, displays the service information of a first application service when different target notification entrances display corresponding entrance interfaces. The electronic device displays the service information of the ongoing application services on the entrance interfaces of the multiple notification entrances, so as to form a prompt effect of reaching a user on multiple interfaces. The electronic device simplifies the operation of a user viewing order information and improves the user experience.

Description

Display control method, electronic device, and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 10, 2024, with application number 202410045615.X and invention name “Display control method, electronic device and computer-readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] Smartphones are becoming increasingly powerful, offering users access to services such as hailing taxis, ordering food delivery, booking bus and flight tickets, and watching movies. Different apps are installed on mobile phones, each providing a different service. When a taxi-hailing app initiates a taxi order, the app's interface displays the order's progress. Similarly, when a food delivery app initiates a food delivery order, the app's interface displays the order's progress.

[0004] Mobile phones offer a wide variety of services, and each type of application provides a wide range of services. Different services may have different service states. The service state of each service is only displayed within the corresponding application interface, which results in poor visibility. Summary of the Invention

[0005] 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 of poor progress display accessibility of application services provided by existing mobile phones.

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

[0007] In a first aspect, a display control method is provided for use in an electronic device. The electronic device includes multiple notification portals, such as a desktop, a negative first screen, a quick application center, a notification center, a control center, a status bar, a lock screen interface, and an AOD interface. The electronic device has a first application installed. On a first interface of the first application, the electronic device can receive a first operation from a user and generate a first application service. The electronic device can also display an indication that the first application has been opened.

[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 one screen, and the second notification entry can be the lock screen interface.

[0009] The electronic device can receive user operations and switch to different notification portals. During the operation of the first application service, if the switched notification portal is the target notification portal corresponding to the first application service, the service information of the first application service will be displayed on the portal interface of this target notification portal. The service information displayed by the electronic device may include corresponding service data and service status.

[0010] In one case, the electronic device receives a second operation from the user and switches to the first notification portal, displays a second interface of the first notification portal, and displays service information of the first application service on the second interface.

[0011] In another case, the electronic device receives a third operation from the user and switches to the second channel entrance. The electronic device displays a third interface of the second notification entrance and displays service information of the second application service on the third interface.

[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 in different target notification entrances in sequence, which does not limit the electronic device to displaying the service information of the first application service in different target notification entrances.

[0013] For example, during the operation of the first application service, the electronic device may only display the second interface corresponding to the first notification entry. Alternatively, the electronic device may only display the third interface corresponding to the second notification entry. Alternatively, the electronic device may first display the second interface corresponding to the first notification entry, and then display the third interface corresponding to the second notification entry. Alternatively, the electronic device may 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] The display control method provided in this embodiment enables an electronic device to display business information of ongoing application services on multiple notification portal interfaces, thereby creating a prompt effect that reaches users across multiple interfaces. The electronic device simplifies the user's operation of viewing order information and improves the user experience.

[0015] In a specific embodiment of the first aspect, the electronic device matches a corresponding target notification portal based on the importance and urgency level of the first application service. Different application services have different importance and urgency levels and corresponding display access requirements. The electronic device can display service information of different application services through different notification portals.

[0016] After generating a first application service, the electronic device can obtain the importance and urgency level of the first application service. The importance and urgency level can be used to indicate the importance and / or urgency of the first application service. The electronic device can rely on the intent prediction model on the intelligent side to obtain the importance and urgency level of the first application service, or it 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 a target notification entry corresponding to the first application service from all notification entries that the electronic device can provide, and then displays service information of the first application service through the selected target notification entries.

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

[0019] In a specific embodiment, the electronic device can adjust the corresponding display control scheme according to the business status update. The first application business has multiple business states, and the importance and urgency levels corresponding to different business states may be different. During the operation of the first application business, the business state will change, and the importance and urgency level of the first application business will also change. The electronic device can determine the current importance and urgency level corresponding to the current business state according to the current business state at different time periods when the first application business is running, and then determine the current corresponding target notification entrance according to the importance and urgency level of the current business state.

[0020] During the operation of the first application service, the service status of the first application service obtained by the electronic device may include a first service status and a second service status in sequence. The first service status is the service status of the first time period, and the second service status is the service status of 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 important emergency level corresponding to the first service state according to the first service state of the first application service, and determines the target notification entrance currently corresponding to the first application service according to the first important emergency level.

[0022] During the second period, the electronic device responds to the updated service status of the first application service and determines a second urgency level corresponding to the second service status based on the updated second service status of the first application service. Based on the second urgency level corresponding to the second service status, the target notification entry corresponding to the first application service is updated. The target notification entry corresponding to the first service status may be the same as or different from 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 notification portal corresponding to the importance and urgency level each time the first application service updates its service status, and display the current service information of the first application service on the entry interface of the current corresponding target notification portal. In this way, the electronic device can switch to a matching display control scheme based on the display access requirements of different service states, further optimizing the display access effect and improving the user experience.

[0024] In another specific embodiment, 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 updating 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 the information according to a preset update frequency.

[0025] In response to the service information update of the first application service, the electronic device displays the updated service information of the first application service on the entry interface of the target notification entry corresponding to the current service state. For example, the electronic device may display the updated service information when displaying the second interface of the first notification entry. For another example, the electronic device may also display the updated service information when displaying the third interface of the second notification entry.

[0026] In this way, the electronic device displays the latest business information on the entry interface of the target notification entry, making it convenient for the user to grasp the latest business status of the order in a timely manner.

[0027] In a specific embodiment of the first aspect, the electronic device displays the service information of the first application service on the entry interface of the target notification entry, 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 after determining each target notification entry, display the service information of the first application service in the target display form on the entry interface of each target notification entry.

[0028] The electronic device determines multiple target notification portals for the first application service and can match different display modes to different notification portals. For example, the electronic device determines a first display mode corresponding to the first notification portal and a second display mode corresponding to the second notification portal.

[0029] When the electronic device displays the second interface of the first notification portal, the service information of the first application service is displayed in the first display mode. When the electronic device displays the third interface of the second notification portal, the service information of the first application service is displayed in the second display mode.

[0030] Electronic devices have added various display forms such as cards, capsules, and banners 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 a target display form. In this implementation, the electronic device determines a target display form corresponding to the first application service based on a first application program that generates the first application service, and then displays service information of the first application service in the target display form.

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

[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 method 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 an electronic device can also pre-register supported display formats. For example, each time the electronic device is powered on, the notification portal initiates a registration request, requesting permission to obtain service information and display it on the portal interface. Each notification portal can correspond to one or more display formats.

[0036] Specifically, the electronic device obtains the display mode corresponding to the first application and the display mode corresponding to the target notification portal. The electronic device intersects the display mode corresponding to the first application and the display mode corresponding to the target notification portal, and obtains the display mode that contains the same lock as the target display mode. The target display mode determined by this scheme can not only obtain the view file corresponding to the target display mode processed by the first application, but also enable the target notification portal to support the display of business information in the target display mode.

[0037] In another specific implementation of the first aspect, the electronic device may also determine the target display form corresponding to the first application service according to the display form corresponding to the target notification entrance.

[0038] For example, the electronic device determines the importance and urgency level of the first application service, determines the corresponding target notification entry based on the importance and urgency level, and determines the previously registered display form of the target notification entry as the target display form corresponding to the first application service.

[0039] In one specific embodiment of the first aspect, the electronic device further provides a pre-registration scheme for notification portals. This allows for a registration procedure for notification portals, taking into account that different device models support different notification portals or have different display functions. The notification portal initiates a registration request, requesting permission to obtain and display service information. The electronic device can then invoke a pre-registered notification portal to display service information for the application.

[0040] In a specific example, the electronic device may include a service interaction and display framework, which may be used to execute the main process of the display control method. For example, the service interaction and display framework may receive a registration application from a notification portal, and after a target notification portal successfully registers with the service interaction and display framework, allow the service interaction and display framework to send service information of the first application service to the target notification portal.

[0041] The electronic device can trigger the notification entry registration operation each time it is turned on. The electronic device can also add a user manual operation to trigger the notification entry registration operation, without limitation.

[0042] In a specific implementation of the first aspect, the electronic device searches for a target notification entry corresponding to the importance and urgency level of the first application service based on an entry mapping table. The electronic device pre-maintains an entry mapping table including different mapping relationships between the importance and urgency levels of application services and notification entries.

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

[0044] The electronic device determines the current importance and urgency level corresponding to the current service state of the first application service, and searches for the notification entry corresponding to the current importance and urgency level of the first application service from a predefined entry mapping table as the current corresponding target notification entry.

[0045] For example, the urgency level of the first application service is very important or very urgent, and the target notification entrances include the desktop, negative one screen, quick application center, notification center, control center, status bar, lock screen interface, and AOD interface.

[0046] For another example, the urgency level of the first application service is important or urgent, and the target notification entrances include the negative one screen, the quick application center, the notification center, the control center, the lock screen interface, and the continuous display interface.

[0047] For another example, the importance and urgency levels of the first application service are generally important and generally urgent, and the target notification entrances include the negative one screen, the quick application center, the notification center, and the control center.

[0048] Generally speaking, the higher the importance and urgency level, the more targeted notification portals are identified, and the stronger the display reach. Electronic devices select notification portals to display service information based on the importance and urgency level of the application service, resulting in a more adaptable display effect that better meets user needs.

[0049] In another specific implementation of the first aspect, when the electronic device finds the notification entry corresponding to the current important urgency level in the entry mapping table based on the important urgency level of the first application service, it will also determine whether the notification entry corresponding to the important urgency level of the first application service has been registered in advance to verify whether the notification entry corresponding to the current important urgency level has the ability to display service information.

[0050] If the electronic device determines that the notification entry corresponding to the important urgency level of the first application service has initiated a registration application, the notification entry corresponding to the important urgency level of the first application service is used as the target notification entry, and the target notification entry is called to display the service information of the first application service.

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

[0052] In a specific implementation of the first aspect, the electronic device further includes a method for stopping displaying service information. The electronic device can obtain an indication of the termination of the first application service. The indication of the termination of the first application service can be proactively sent by the first application program that generated the first application service, or can be proactively obtained by the electronic device based on a preset update frequency.

[0053] In response to the termination of the first application service, the electronic device stops displaying the service information of the first application service at the target notification portal, so as to promptly remind the user that the first application service has terminated.

[0054] In summary, the display control method provided in the embodiments of the present application enables an electronic device to display the latest service information of a first application service in different display formats on the entry interfaces of multiple notification portals during the process of a first application service being generated by a first application. The electronic device promptly displays the latest service information on each entry interface of the electronic device to ensure that the service information reaches the user as much as possible, simplifying the user's tedious operation of viewing information and greatly improving the user experience.

[0055] In a second aspect, the present application provides an electronic device, the electronic device comprising a display, a memory, and a processor, wherein the display and the memory are both coupled to the processor;

[0056] Memory stores computer-executable instructions;

[0057] The processor executes the computer-executable instructions stored in the memory, so that the electronic device executes the display control method as described in any one of the first aspects.

[0058] In a third aspect, a control device is provided, which can execute any display control method as described in the first aspect.

[0059] In a fourth aspect, an electronic device is provided, which has the function of implementing the display control method of the first aspect. The function can be implemented through hardware or through hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0060] In a fifth aspect, an electronic device is provided, comprising: a processor and a memory; the memory is used to store computer execution instructions, and when the electronic device is running, the processor executes the computer execution instructions stored in the memory to enable the electronic device to execute a display control method as described in any one of the first aspects above.

[0061] In a sixth aspect, an electronic device is provided, comprising: a processor; the processor is configured to be coupled to a memory, and after reading instructions in the memory, execute the display control method as described in any one of the first aspects above according to the instructions.

[0062] In a seventh aspect, a computer-readable storage medium is provided, in which instructions are stored. When the computer-readable storage medium is run on a computer, the computer can execute the display control method of any one of the above-mentioned first aspects.

[0063] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the display control method of any one of the above-mentioned first aspects.

[0064] In a ninth aspect, a control device (for example, the control device may be a chip system) is provided, the device including a processor for supporting the control device to implement the functions involved in the first aspect above. In one possible design, the device also includes a memory for storing program instructions and data necessary for the control device. When the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0065] Among them, the technical effects brought about by any design method in the second to ninth aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0067] FIG2 is a flow chart of a display control method according to an embodiment of the present application;

[0068] FIG3 is a diagram showing a portion of an interface of a mobile phone displaying service information on multiple target notification portals according to an embodiment of the present application;

[0069] FIG4 is another partial interface diagram of a mobile phone displaying service information on multiple target notification portals according to an embodiment of the present application;

[0070] FIG5 is another schematic flow chart of a display control method according to an embodiment of the present application;

[0071] FIG6 is a schematic diagram of a process of executing a display control method by a mobile phone according to an embodiment of the present application;

[0072] FIG7 is a schematic diagram of the software framework of a mobile phone provided in an embodiment of the present application;

[0073] FIG8 is a flow chart of a method for executing a display control method based on a software framework according to an embodiment of the present application;

[0074] FIG9 is a schematic diagram showing a software framework for implementing a display control method according to an embodiment of the present application;

[0075] FIG10 is a schematic diagram of a software framework corresponding to a Widget architecture of an electronic device provided in an embodiment of the present application;

[0076] FIG11 is a schematic diagram of a flow chart of a display control method executed by an electronic device based on a Widget architecture according to an embodiment of the present application;

[0077] FIG12 is another flowchart of a method for executing a display control method based on a Widget architecture in an electronic device according to an embodiment of the present application;

[0078] FIG13 is a flow chart of a notification entry registration operation involved in a display control method according to an embodiment of the present application;

[0079] FIG14 is a schematic diagram of a process of displaying a widget card on a notification portal according to a display control method provided in an embodiment of the present application;

[0080] FIG15 is a flow chart showing the process of displaying updated service information on a notification portal according to a display control method provided in an embodiment of the present application;

[0081] FIG16 is a schematic diagram of a process of automatically updating a Widget card display in an interactive display framework according to a display control method provided in an embodiment of the present application;

[0082] FIG17 is a schematic diagram of a flow chart of simultaneously transmitting capsule and card view files involved in a display control method provided in an embodiment of the present application;

[0083] FIG18 is a schematic diagram of an interface involving a capsule and a card in a display control method provided in an embodiment of the present application;

[0084] FIG19 is a schematic diagram of a process flow of an electronic device simultaneously transmitting a view file of capsule and card data according to an embodiment of the present application;

[0085] FIG20 is a schematic diagram of the interaction between a mobile phone and a watch involved in the display control method provided in an embodiment of the present application;

[0086] FIG21 is a schematic diagram of the interaction between a mobile phone, a watch, and a vehicle computer according to the display control method provided in an embodiment of the present application;

[0087] FIG22 is a schematic diagram of the connection between a mobile phone and a watch involved in the display control method provided in an embodiment of the present application;

[0088] FIG23 is a schematic diagram of a flow chart of a display control method provided in an embodiment of the present application involving a mobile phone transmitting business information to an external device;

[0089] FIG24 is a schematic diagram of a mobile phone supporting multi-device transmission and display according to a display control method provided in an embodiment of the present application;

[0090] FIG25 is a flow chart showing a display control method according to an embodiment of the present application involving transmitting service information to an external device;

[0091] FIG26 is a schematic diagram of a process of pushing full information in a display control method provided in an embodiment of the present application;

[0092] Figure 27 is a hardware structure diagram of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0093] The following description of exemplary embodiments of the present application is made in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0094] To facilitate understanding, some technical common sense involved in the embodiments of this application is first introduced.

[0095] Electronic devices (such as mobile phones) can install various applications to implement different services. These applications can include system applications and third-party applications. System applications include call and alarm clock applications, while third-party applications include ride-hailing and shopping applications. The mobile phone's desktop interface displays icons for various applications. When a user clicks an application icon on the desktop, the phone launches the corresponding application and displays the application interface to the user.

[0096] As shown in Figure 1, a schematic diagram of the mobile phone interface is shown. As shown in Figure 1 (a), the mobile phone can display icons corresponding to various applications on the desktop, such as the icon of the taxi application (101 shown in Figure 1 (a)). If the taxi application icon on the desktop receives a click operation from the user, it enters the taxi application interface shown in Figure 1 (b). The taxi application interface displays a taxi request input box. The user can enter or select taxi requirements, such as the departure point, destination, car type, etc., and click the "Confirm Taxi" control (102 shown in Figure 1 (b)) to initiate a taxi order. The taxi application will enter the taxi application interface shown in Figure 1 (c), which will display the order status of the taxi order and continuously update the order status, including the order acceptance status, driver arrival status, and trip status.

[0097] During the entire process of the taxi order, the user can exit the taxi application interface and click to enter the application interface of other applications on the phone, or the user can lock the phone screen. As shown in (d) in Figure 1, during the process of the taxi order, the user exits the taxi application interface and locks the screen. The phone does not display the order status of the taxi application on the lock screen interface, so that the user cannot obtain the real-time status of the taxi order in time. If the user wants to obtain the real-time status of the taxi order, he needs to unlock the phone and enter the taxi application interface again to view the real-time status and progress of the taxi order. In other words, the existing display control solution requires the user to perform relatively cumbersome operations, and the user experience is poor.

[0098] Based on this, an embodiment of the present application provides a display control method, which is applied to electronic devices. The electronic device provides a display solution for displaying relevant data of application services on the entry interface of multiple notification entrances for application services generated by various application programs. Compared with the solution of displaying business data only through the application interface, the display control method provided by the embodiment of the present application realizes the synchronous display of business data on the interface of multiple notification entrances. The display effect is more intuitive, and business data can be displayed to users without receiving a large number of user operations, which simplifies the operation of users viewing application services and improves user experience.

[0099] The electronic devices used in the embodiments of the present application may include personal computers (PCs), tablet computers, laptop computers, portable computers (such as mobile phones), wearable electronic devices (such as smart watches), augmented reality (AR) and virtual reality (VR) devices, in-vehicle computers, and other electronic devices with touch screens. The following embodiments do not impose any special restrictions on the specific form of the electronic devices. For ease of description, the embodiments of the present application mainly use mobile phones as an example to explain the specific implementation method of the electronic device executing the display control method.

[0100] Example 1

[0101] As shown in Figure 2, it is a flow chart of the display control method provided in the embodiment of the present application. The provided display control method mainly includes the following process:

[0102] S201: 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.

[0103] A first application is installed on the mobile phone. The first application can receive a first operation from the user and generate a first application service. The mobile phone can display instruction information for generating the first application service.

[0104] The first application involved in this embodiment can be a system application, a third-party application, a quick application, a mini-program application installed on a third-party application, etc.

[0105] The first application service involved in this embodiment can be understood as an application order initiated by the first application on the mobile phone, which needs to run continuously for a period of time to be completed. The application order can be a consumption order involving a payment transaction or a task order not involving a payment transaction.

[0106] In one example, the first application may be a taxi-hailing application, and the first interface of the first application may be the application interface of the taxi-hailing application. Upon receiving the user's first operation, the mobile phone generates a consumption order for the taxi-hailing service. This consumption order for the taxi-hailing service is an application order that takes a certain period of time to complete and can be considered a first application service. Similarly, the first application may also be a food delivery application, a courier application, or the like.

[0107] In another example, the first application can be an alarm clock or stopwatch. Upon receiving a user click, the alarm clock or stopwatch generates an alarm reminder or countdown timer. While this timer service doesn't involve a payment transaction, it still requires a certain period of time to complete and can be considered an application service. The first application can also be an application for sports results broadcasting, flight status notifications, smart home control, flight schedules, or train schedules.

[0108] An application can initiate multiple different application services at the same time. For example, a taxi application can initiate two different taxi services at the same time, one taxi service is to take a taxi from place A to place B, and the other taxi service is to take a taxi from place C to place D. Taking into account that different application services correspond to different user needs, that is to say, different application services are usually unrelated to each other, and have their own display access requirements. In order 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 initiates two application services respectively, the mobile phone can execute the corresponding display control methods for these two application services respectively.

[0109] 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 that 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.

[0110] In one example, the first application service is a ride-hailing service. Information provided by the mobile phone, such as the current number of people in the queue, driver and vehicle information, personal information, the distance between the vehicle's current location and the passenger's boarding point, navigation routes, distance to the destination, estimated arrival time, and estimated fare, constitutes service data. Information provided by the mobile phone regarding the order status of the ride-hailing service, such as "in queue," "waiting for the driver to arrive," "driver has arrived," "passenger has boarded," and "arrived at the destination," constitutes service status.

[0111] When each first application opens 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 the business data or business status and other related information of the first application service in the application interface of the first application. 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 in the first application interface of the first application until the first application service ends, and the business process will also end.

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

[0113] In one case, the application process of the taxi-hailing business is created when the taxi-hailing business is generated, and continues to follow up on several business states such as the driver accepting the order, the driver arriving, heading to the destination, and arriving at the destination. When the taxi-hailing business arrives at the destination, the taxi-hailing business ends, and the corresponding application process of the taxi-hailing business also ends.

[0114] 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 time limit, the user actively cancels the taxi-hailing, or other abnormal circumstances occur, the taxi-hailing service ends and the taxi-hailing process also ends.

[0115] That is to say, the first application service processed by the embodiment of the present application can be an application service that is started and created normally and ends normally, or an application service that is started and created normally and ends abnormally, without limitation.

[0116] As shown in Figure 1(b), the first application is a ride-hailing application, and the first application service is a ride-hailing service. The mobile phone displays the ride-hailing application interface. In response to a user clicking the "Confirm Ride Request" control (102 in Figure 1(b)), a ride order is placed. As shown in Figure 1(c), the mobile phone displays an indication within the ride-hailing application interface that a ride-hailing service has been generated.

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

[0118] The phone provides multiple notification portals, each of which can display notification messages. These portals can include: the desktop, the negative first screen, the notification center, the control center, the lock screen, the status bar, the always on display (AOD), and the quick app center.

[0119] The mobile phone may match multiple target notification portals for the first application service, and the mobile phone may display the service information of the first application service on the portal interface when the portal interface is displayed at the target notification portal.

[0120] There are many solutions for the mobile phone to determine the corresponding target notification entrance for the first application service.

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

[0122] In one example, when a mobile phone installs a first application, it can register a notification portal supported by the first application.

[0123] When detecting that the first application generates a new first application service, the mobile phone determines the notification entry pre-registered by the first application as a target notification entry matching the first application service.

[0124] For example, when a ride-hailing app is installed on a mobile phone, the notification portals supported by the ride-hailing app include the desktop, negative one screen, lock screen, status bar, and AOD interface. When the ride-hailing app generates a new ride-hailing service, the target notification portals matched for the ride-hailing service may include the desktop, negative one screen, lock screen, status bar, and AOD interface.

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

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

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

[0128] The notification portals provided by mobile phones enable device access, such as mobile phone access or tablet access. The access method provided by mobile phones in each notification portal can be visual access.

[0129] In another example, the phone can also display business information in different display formats in different notification portals. For example, the display formats can include capsules, cards, and banners. The cards provided by the phone can be divided into card sets and card collapse states, corresponding to cards of different sizes.

[0130] Table 1 below shows 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 importance and urgency level of application services and notification entry points, and can also store device access and access mode.

[0131] Table 1

[0132] As shown in Table 1, the mobile phone can also store identifiers corresponding to different importance and urgency levels of application services in the entry mapping table. The mobile phone can first determine the importance and urgency level of the first application service, search for the identifier corresponding to the importance and urgency level of the first application service in Table 2 below (L11, L21, etc.), and then search Table 1 for the target notification entry and display mode corresponding to the first application service based on the identifier.

[0133] Table 2

[0134] The above example provides a solution for the mobile phone to determine the corresponding target notification entry for the first application service based on 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.

[0135] In another example, during the operation of the first application service, the mobile phone may have different service states, each of which has different urgency levels. The mobile phone may also determine different target notification entrances based on the different service states of the first application service.

[0136] For example, during the operation of the first application service, the service status of the first application service obtained by the electronic device may include a first service status and a second service status in sequence, where the first service status is the service status of the first time period, and the second service status is the service status of the second time period, where the second time period is a time period after the first time period.

[0137] In the first time period, the electronic device determines the first important emergency level corresponding to the first service state according to the first service state of the first application service, and determines the target notification entrance currently corresponding to the first application service according to the first important emergency level.

[0138] During the second period, the electronic device responds to the updated service status of the first application service and determines a second urgency level corresponding to the second service status based on the updated second service status of the first application service. Based on the second urgency level corresponding to the second service status, the target notification entry corresponding to the first application service is updated. The target notification entry corresponding to the first service status may be the same as or different from the target notification entry corresponding to the second service status.

[0139] For example, during the first period, the mobile phone receives a taxi service with a service status of "Queued" and an urgency level of "General, Important, Urgent." The mobile phone finds the corresponding identifier L23 in Table 2 and the corresponding target notification portals in Table 1: AOD interface, lock screen, negative one screen, desktop, and notification center.

[0140] During the second period, the phone receives a taxi service status indicating that the driver has accepted the order and the urgency level is set to General, Important, or Urgent. The phone finds the corresponding identifier L23 in Table 2 and the corresponding target notification portals in Table 1: AOD, lock screen, negative one screen, desktop, and notification center.

[0141] During the third period, the mobile phone receives the taxi service status "Passenger Boarded" and the importance level is "Generally Important, General Urgent." The mobile phone finds the corresponding identifier L22 in Table 2 and the corresponding target notification portals in Table 1: -1 screen, desktop, and notification center.

[0142] In this example, the phone displays notifications on the AOD, lock screen, negative one screen, desktop, and notification center when the ride-hailing service is in the queue and the driver has accepted the order. When the ride-hailing service switches to the passenger boarding the vehicle, the phone displays notifications on the negative one screen, desktop, and notification center, but stops displaying them on the AOD and lock screen.

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

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

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

[0146] The phone will display one target notification entry interface at a time. In response to a user operation, the phone can switch to another target notification entry interface. For example, in response to a second operation, the phone can display a second interface corresponding to the first notification entry, displaying service information for the first application service on the second interface. For another example, in response to a third operation, the phone can display a third interface corresponding to a third notification entry, displaying service information for the first application service on the third interface.

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

[0148] As shown in Figures 3 and 4, the mobile phone displays the business information of the first application service on the entry interface of the target notification entrance. As shown in Figure 3 (a), the mobile phone can display the business information of the taxi service in the form of a banner 301 on the desktop. As shown in Figure 3 (b), the mobile phone can also display the business information of the taxi service in the form of a capsule 302 on the status bar. As shown in Figure 3 (c), the mobile phone can display the business information of the taxi service in the form of a capsule 303 on the interface of the negative one screen.

[0149] As shown in (d) of FIG. 3 , the mobile phone may display the business information of the taxi-hailing service in the form of a card 304 on the interface of the negative one screen.

[0150] As shown in (a) of FIG4 , the mobile phone can display the business information of the taxi-hailing service in the form of a card 401 on the lock screen interface. As shown in (b) of FIG4 , the mobile phone can display the business information of the taxi-hailing service in the form of a card 402 on the interface of the notification center. As shown in (c) of FIG4 , the mobile phone can display the business information of the taxi-hailing service in another form of a capsule 403 on the status bar. Different from the capsule form 302 shown in (b) of FIG3 , the capsule form 403 also adds a decorative design to decorate the installation area of ​​the camera or other devices, and can use this area to display business information, thereby improving screen utilization.

[0151] As shown in (d) of FIG. 4 , the mobile phone may also display the service information of the taxi service in the form of a capsule 404 on the AOD interface.

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

[0153] The mobile phone may also display only one target notification entry interface during the operation of the first application service, and display the service information of the first application service on this single entry interface. For example, after the user places an order for a taxi service and then locks the screen, the mobile phone may continue to display the service information of the taxi service on the lock screen until the taxi service is completed.

[0154] The phone can select different target notification portals to display business information, and can also choose the display format of business information on the interface of different notification portals. The display formats involved include cards, capsules, and banners.

[0155] Among them, cards are the main display form. Cards mainly include quick service cards, quick application cards (Java Script TM , JS), Android TM Application cards (Widgets) and content interface cards can be presented in the form of cards or icons.

[0156] Shortcuts are services presented as icons, allowing users to use them without installing the corresponding app on their phone. Software Development Kit (SDK) content interface cards present services as cards or voice commands.

[0157] Quick app cards, also known as JS cards, are hosted by quick apps and presented as cards, visually displaying service content. JS cards are primarily displayed on the negative one screen and the quick app center interface.

[0158] Android TM App cards are widget cards. Services are presented as cards alongside apps, visually displaying their content. Widget cards appear on various notification portals, including the desktop, the negative first screen, the notification center, and multiple devices.

[0159] Widget cards can be displayed on the desktop, status bar interface, lock screen interface, notification center, multiple devices and other notification portals.

[0160] In the display control method provided by the embodiment shown in FIG2 , the mobile phone matches a target notification portal for displaying service information of the first application service for the first application service.

[0161] FIG5 is another flow chart of the display control method. The provided display control method mainly includes the following process:

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

[0163] 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 S201 above and will not be repeated here.

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

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

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

[0167] In one example, the target display form determined by the mobile phone for the first application service may include a first display form and a second display form. The first display form corresponds to the second interface of the first notification portal, 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 the third interface of the second notification portal, 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 may be the same or different.

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

[0169] At the first moment, the mobile phone displays the entrance interface of the negative one screen, and displays the business information of the taxi service in the form of a card on the negative one screen interface.

[0170] At the second moment, the mobile phone displays the lock screen interface, and the business information of the taxi service is displayed in the form of a capsule on the lock screen interface.

[0171] There may be multiple solutions for the mobile phone to select the first display form corresponding to the first application service.

[0172] In a first solution, the mobile phone can determine a corresponding target display form for the first application service based on the first application.

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

[0174] When installing each application, the mobile phone registers the display modes it supports. When generating a first application service, the mobile phone searches for the display mode previously registered by the first application that generated the first application service and uses the previously registered display mode as the target display mode corresponding to the first application service.

[0175] For example, a mobile phone installs a taxi-hailing app. The second type of display form pre-registered by the taxi-hailing app includes JS cards, widget cards, capsules, etc. When the mobile phone generates a taxi-hailing service, the second type of display form pre-registered by the taxi-hailing app is used as the target display form for the taxi-hailing service.

[0176] For another example, the second display form pre-registered by the mobile phone express application includes JS cards and capsules, etc. When the mobile phone generates an express service, the second display form pre-registered by the express application is used as the second display form of the express service.

[0177] In a second solution, the mobile phone may determine a corresponding target display form for the first application service based on the importance and urgency level of the first application service.

[0178] In this case, the mobile phone will first determine the target notification entry for the first application service, and then determine the target display format for the first application service. The mobile phone determines the target notification entry for the first application service by searching a pre-stored entry mapping table (such as Table 1) based on the importance and urgency level of the first application service. The specific implementation method for the mobile phone to determine the target notification entry for the first application service can be found in the specific implementation method of S202 above and will not be repeated here.

[0179] In one example, the mobile phone obtains the second display mode pre-registered by the first application and the third display mode pre-registered by the target notification portal. The mobile phone uses the same display mode in the second and third display modes as the target display mode for the first application service.

[0180] Each time the phone is powered on, some or all notification portals initiate a registration request to display service information. Furthermore, the notification portals register supported display formats, providing the ability to display service information in these registered formats. The phone can store the supported display formats in a portal mapping table (see Table 1).

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

[0182] The mobile phone uses the display mode previously registered by the first application and the same display mode that exists in the display modes supported by the target notification portal as the target display mode of the first application service.

[0183] Furthermore, the target display mode determined by the mobile phone corresponds to the target notification entry. For example, the target notification entry includes the first notification entry and the second notification entry.

[0184] For example, the mobile phone uses the display mode pre-registered by the first application and the same display mode as the first notification portal's pre-registered display mode as the first display mode corresponding to the first notification portal. When the mobile phone displays the second interface of the first notification portal, it displays the service information of the first application service in the first display mode.

[0185] For another example, the mobile phone uses the display mode pre-registered for the first application and the display mode pre-registered for the second notification portal as the second display mode corresponding to the second notification portal. When the mobile phone displays the third interface of the second notification portal, the service information of the first application service is displayed in the second display mode.

[0186] The second display mode and the third display mode determined by the mobile phone may be one display mode or multiple display modes, without limitation.

[0187] S504: Displaying the service information of the first application service in a target display form on the entry interface of the target notification entry.

[0188] The mobile phone determines at least two target notification entrances of the first application service and the target display forms corresponding to the different target notification entrances, and then performs the operation of displaying the service information of the first application service. The specific implementation of S504 can refer to the specific implementation process of S203 and S204 above, which will not be repeated here.

[0189] As shown in Figure 6, it is a schematic diagram of the process of a mobile phone executing the display control method provided in the above embodiment. The mobile phone has an intention perception function and can obtain the important urgency level of the generated business.

[0190] When generating a first application service, the mobile phone determines the importance and urgency level of the first application service through intent perception. The mobile phone encapsulates the service information and importance and urgency level of the first application service into a service package to achieve service delivery.

[0191] Mobile service delivery mainly involves two stages: device delivery and notification entry matching. The mobile phone first determines the device to be reached, such as the mobile phone itself or other devices (computers, tablets, watches, car computers, etc.).

[0192] The mobile phone determines a notification portal that provides a display function on the device to be reached. Referring to the specific implementation process of S202 described above, the mobile phone searches the portal mapping table for the corresponding target notification portal based on the importance and urgency level of the first application service. The mobile phone displays the service information of the first application service on the portal interface of the target notification portal to complete the service reach.

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

[0194] Process 1: Notification portal registration.

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

[0196] 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 service information of the first application service to the target notification portal.

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

[0198] When generating 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.

[0199] The mobile phone verifies whether the second-type notification entrance has initiated a 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.

[0200] The phone also obtains the second display mode pre-registered by the first application and the third display mode pre-registered by the target notification portal. Based on the same display mode in the second and third display modes, the phone determines the target display mode corresponding to the first application service.

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

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

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

[0204] During the operation of the first application service, the mobile phone will also re-determine the importance and urgency level corresponding to the current service status according to the update of the service status of the first application service, and search the current target notification entry corresponding to the importance and urgency level of the current service status in the entry mapping table.

[0205] The mobile phone will determine a new target notification portal based on the updated service status and display the updated service information on the portal interface of the new target notification portal.

[0206] Step 4: The phone stops displaying service information.

[0207] The mobile phone may also obtain a notification of the end of the operation of the first application service, and when the operation of the first application service ends, the mobile phone stops displaying the service information of the first application service at the target notification entrance.

[0208] The above content mainly introduces the specific implementation process of the display control method provided by the embodiment of the present application from the mobile phone level. The specific implementation process of the display control method provided will be explained below in combination with the software and hardware framework of the mobile phone.

[0209] The framework of a mobile phone is a layered architecture that divides software and hardware into several layers, each with 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 (HAL), a kernel layer, and a hardware layer. Of course, in addition to the above-mentioned main layered architectures, it may also include a runtime (Runtime) and a system library, which will not be described in detail.

[0210] As shown in Figure 7, a schematic diagram of the software framework of a mobile phone is shown. For ease of understanding, Figure 7 only illustrates some functional modules associated with the display control method provided in the embodiment of the present application, and does not limit the software framework of the mobile phone to only include these functional modules.

[0211] For example, the application layer may include a series of applications. The applications included in the application layer may include system applications and third-party applications, such as taxi applications and food delivery applications.

[0212] In addition to various applications, the application layer may also include various notification portals and a display service module for supporting various notification portals to display corresponding portal interfaces.

[0213] As shown in FIG7 , the application layer includes a first application, a notification entry module and a host module HOST ARR. The HOST ARR includes an entry initialization module, a view creation module and a service channel.

[0214] The first application is the application that generates the first application service in the aforementioned embodiment. The first application may include various applications, such as a food delivery application, a taxi-hailing application, and the like.

[0215] This example does not focus on the implementation logic of various first application programs, such as how the first application program generates and completes the first application service. This example focuses on the process of calling various target notification portals to display the service information of the first application service on the portal interface when the mobile phone generates the first application service.

[0216] The notification entry module includes various notification entries that the mobile phone supports for displaying business information, such as the desktop, negative one screen, notification center, control center, quick application center, lock screen, status bar, AOD, etc.

[0217] In other cases, the notification portal provided on the mobile phone may also include a multi-device portal, which can be other devices that have a communication connection with the mobile phone, such as a bracelet, watch, tablet, car computer, etc. The multi-device notification portal set in the notification portal module refers to the communication module on the mobile phone used to communicate with multiple devices. The mobile phone can transmit service information to the notification portals of multiple devices through the communication module for display, so that the services of the first application service can reach users as much as possible.

[0218] The view creation module can support notification portal creation and rendering of views to display the corresponding portal interface. Specifically, the view creation module can include view creation submodules for creating corresponding operating systems, programming languages, or services. These submodules can be called by various notification portals of the notification portal module to create views.

[0219] The view creation module may include: JS card view creation sub-module, SDK card view creation sub-module, notification view creation sub-module, widget card view creation sub-module, shortcut view creation sub-module, and Remote Views view creation sub-module.

[0220] The notification portal initialization module includes a notification portal registration submodule and a notification portal callback submodule. The notification portal registration submodule is used to receive registrations from various notification portals within the notification portal module. Registered notification portals are authorized to display business information and can display generated application business information on the corresponding portal interface. When registering with the notification portal registration submodule, notification portals may also register their supported display formats and specifications.

[0221] After each phone is turned on, various notification portals in the notification portal module that support touch display can register with the notification portal registration submodule, and the notification portal that initiates the registration application first can be called to display business information.

[0222] The notification entry callback submodule is used to monitor the calling status of various notification entries. When the first application generates the first application service, it responds to the notification entry calling instruction of the framework layer and calls the corresponding notification entry for interface display.

[0223] The service channel includes the card implementation type, card ID and service reception processing, which are used to coordinate the implementation of channel calling, card ID transmission and service distribution.

[0224] The framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The framework layer receives instructions from the application layer and feeds back relevant data so that the application layer can display it. The application framework layer also includes some predefined functions.

[0225] Continuing as shown in Figure 7, the framework layer includes the smart module and the service interaction and display framework.

[0226] The smart module is used to manage the application services generated by the application. Specifically, the smart module may include relevant functional modules that provide smart services in the mobile phone and manage the application services of various applications in the mobile phone.

[0227] When monitoring that the first application program generates the first application service, the smart module notifies the service interaction and presentation framework to trigger the execution of a display control operation for the first application service.

[0228] In one example, when the smart module monitors that the first application generates a first application service, it will also allocate a service identifier (Identity Document, ID) for the first application service. In the subsequent display control method process, the first application service can be identified and matched according to the service ID.

[0229] In another example, the smart module may also send the business information of the first application business to the service interaction and presentation framework, which will assign a business ID to the first application business and then pass the business ID to the smart module.

[0230] In addition, the smart module can also determine the importance and urgency level for the first application service. The smart 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.

[0231] In addition, the smart module can also obtain business information of the first application business and pass the business information of the first application business to the service interaction and display framework. The business information of the first application business obtained by the smart module is provided by the first application, and the smart module can directly pass the business information of the first application business to the service interaction and display framework. The smart module can also obtain the business information of the first application business based on the target display form pre-registered by the first application and display the view file in the specific format required for the target display form, and pass the view file corresponding to each target display form to the service interaction and display framework.

[0232] The smart module can directly pass the packaged view file to the service interaction and presentation framework. Alternatively, the smart module can store the packaged view file in a designated shared storage space and notify the service interaction and presentation framework, which can then retrieve the packaged view file from the designated shared storage space.

[0233] As shown in FIG7 , 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.

[0234] The interaction specification query module receives the service ID and importance / urgency level of the first application service from the smart module. Based on a pre-stored entry mapping table (such as Table 1), the interaction specification query module searches for the target notification entry and target display format corresponding to the importance / urgency level of the first application service. The interaction specification query module uploads the target notification entry and target display format associated with the first application service, along with the service ID, to the interaction notification entry management module.

[0235] The service parsing module receives the service ID and service information of the first application service sent by the smart module. The service information here can be a packaged view file corresponding to each target display form. The parsing service module passes various types of service information to the parsing and implementation module.

[0236] The parsing and implementation modules include parsing and implementation function modules for various forms, including:

[0237] Dynamic card framework, implementing the dynamic card framework Surface View of the desktop view; Widget framework, among which the Widget framework implements the Widget Manager Service; JS framework, implementing the quick service View; desktop application Launcher Apps service, implementing Shortcut Info; Notification framework, implementing Remote Views, etc.

[0238] These frameworks can obtain the corresponding type of view files, parse them to obtain the View files displayed by the corresponding views, and the original business information, etc. They then upload this information to each notification portal through the channels of each notification portal so that the notification portal can display the corresponding business information.

[0239] The interactive notification entry management module includes ID allocation, interface callback processing, and service binding modules. ID allocation is used to assign a service ID to the first application service. Interface callback processing is used to call the create interface, update interface, and stop interface, and monitor the start, update, and stop operations of the display control process.

[0240] Continuing with FIG7 , the application layer also includes a state update interface and a lifecycle monitoring module. The lifecycle monitoring module is used to monitor the service process of the first application service. While the first application service process is active, the state update interface can be called to update the service state of the first application service.

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

[0242] The hardware abstraction layer can encapsulate the drivers in the kernel layer and provide a calling interface to the application framework layer, shielding the implementation details of the underlying hardware.

[0243] In conjunction with the software framework provided in Figure 7, the mobile phone displays service information for the first application service generated by the first application program on multiple first-category entry interfaces. Figure 8 is a flow chart illustrating the implementation of the display control method by the mobile phone's software framework. As shown in Figure 8, the mobile phone's execution of the display control method primarily includes: Step 1, registering a notification entry; Step 2, matching the notification entry with the application service and displaying the service information; Step 3, updating the displayed service information; and Step 4, stopping the display of the service information.

[0244] Process 1, process 2, process 3 and process 4 shown in Figure 8 correspond to process 1, process 2, process 3 and process 4 of the aforementioned example respectively. The following will describe these four main processes in detail in conjunction with the specific execution modules of the software framework.

[0245] It should be noted that the "business provider" here can be understood as the data provision module within the first application that generates the first application service, capable of providing service information. The "smart module" can be understood as the smart module bound to the first application, or as a smart module integrated on the smart side that is bound to multiple applications to manage the multiple application services generated by them. The "target notification entry" can be the target notification entry associated with the first application service among the multiple notification entries of the notification entry module.

[0246] Process 1, notification entrance registration.

[0247] S801: The target notification portal registers with the service interaction and presentation framework.

[0248] Process 1 mainly implements the registration of the notification portal to the service interaction and display framework, and at the same time registers the display forms and specifications that can be achieved.

[0249] In process 2, the mobile phone matches the notification entrance for the application service and displays the service information.

[0250] S802: The business provider notifies the smart module that the first application generates a first application service.

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

[0252] S804: The smart module sends the service ID and importance and urgency level of the first application service to the service interaction and presentation framework.

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

[0254] S806: The service interaction and presentation framework requests business information from the smart module.

[0255] S807: The business provider sends business information to the smart module.

[0256] S808: The smart module sends a view file containing business information to the service interaction and presentation framework.

[0257] S809: The service interaction and presentation framework distributes the view file containing the business information to the target notification portal.

[0258] S810: The target notification portal displays business information.

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

[0260] S811: The business provider sends updated business information to the smart module.

[0261] S812: The smart module sends a view file containing updated business information to the service interaction and presentation framework.

[0262] S813: The service interaction and presentation framework monitors the life cycle, obtains updated business information regularly, and distributes view files containing updated business information to the target notification entry.

[0263] S814: The target notification portal displays updated business information.

[0264] Process 4: The mobile phone stops displaying business information.

[0265] S815: The service provider notifies the smart module that the first application ends the first application service.

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

[0267] S817: The service interaction and presentation framework notifies the target notification portal to stop portal display.

[0268] S818: The target notification portal stops displaying business information.

[0269] Based on the user's order termination or other reasons, the first application notifies the smart module to terminate the first application service. The smart module sends the service ID of the first application service and an instruction to stop displaying the notification portal to the service interaction and presentation framework. The service interaction and presentation framework instructs the notification portal to stop displaying the notification portal, and the notification portal stops displaying service information.

[0270] In addition, considering that the visibility status of each target notification portal is different under different usage conditions, it will affect the display capability of the portal interface.

[0271] If the current portal interface is not visible, the service interaction and display framework may not send business information to the corresponding invisible notification portal. Alternatively, the service interaction and display framework may send business information to the system cabinet portal. After the notification portal receives the business information, if the portal interface is not currently visible, it may not generate or display the corresponding business information view. The notification portal will only display the business information view when the portal interface of the notification portal switches to a visible state.

[0272] For example, when a taxi-hailing app generates a taxi-hailing service, the associated notification entrances determined include the negative one screen, the notification center, and the desktop. Then, if the phone currently displays the desktop interface, the interface status of the negative one screen and the notification center will not be visible. The service interaction and display framework may not send business information to the negative one screen and the notification center, and only send business information to the negative one screen or the notification center for display when the phone switches to the negative one screen or the notification center. Alternatively, the service interaction and display framework may also send business information to the negative one screen and the notification center in accordance with the specifications, and the negative one screen or the notification center will render the view and display the business information on the corresponding interface. Then when the negative one screen is visible, the business information displayed on the negative one screen can reach the user.

[0273] Corresponding to the detailed example shown in Figure 8, Figure 9 is a schematic diagram of a software framework implementing a display control method. The display control process can mainly include three stages: intent prediction, service management, and service access.

[0274] The smart side of the phone predicts intent based on the application services generated by the app. This side includes multimodal, multidimensional triggering and a multimodal intent framework. The multimodal, multidimensional triggering framework includes a low-power voice module and a low-power vision model. The low-power voice model collects speech within a preset range for speech recognition. The low-power vision model collects images within a preset range for visual recognition. The recognition results of the low-power voice and low-power vision models are fused and sent to the multimodal intent framework.

[0275] The multimodal intent framework performs speech recognition and natural language processing (NLP), as well as visual recognition and understanding, ultimately predicting the user's intent through multimodal intent prediction. This predicted intent can include the user's intent to generate and display an order, as well as the user's intent to display related business information. Based on the intent slot, the multimodal intent framework sends the predicted intent to the service management framework.

[0276] The service management framework can perform fuzzy matching (Intent) or exact matching (ID) on the intents predicted by the multimodal intent module and make service recommendations. A predicted intent may correspond to multiple services. The service management framework will then perform service orchestration, such as service composition or batch processing. The service management framework also provides service query, permission management, ID management, classification and storage, installation, uninstallation, registration, and deregistration capabilities. Ultimately, the service management framework generates display services for application businesses, which can be mainly divided into system atomic services, third-party atomic services, and real-time data services, connecting services to the service interaction and display framework.

[0277] The service interaction and display framework includes a system interaction notification portal, a service execution adapter, and human-computer interaction specifications. The system interaction notification portal primarily displays various notification portals. The service execution adapter matches notification portals, display formats, and display methods. Based on the human-computer interaction specifications, it queries the importance and urgency level of the application service and determines the display method, notification portal location, and display format for service information. The human-computer interaction specifications include service interaction specifications and accessibility scenario specifications.

[0278] In this way, system services and third-party services are registered and managed in the service management framework, the intelligent side predicts intent, and then sends the intent service to the service display and interaction framework. The service display and interaction framework performs intent and service analysis, and finally the service interaction specification determines the display notification entrance and card size, and calls the notification entrance for display to reach the user.

[0279] The above solution illustrates the process from generating an application service to calling a notification portal to display the service information of the application service. The following describes several major detailed solutions involving display data transmission during the execution of the above display control method through different embodiments. It should be noted that subsequent embodiments 2-4 are technical solutions implemented based on the above embodiment 1.

[0280] Example 2

[0281] 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 also needs to obtain the view file corresponding to the target display form.

[0282] Electronic devices use the Widget architecture. Applications installed on these devices support displaying generated business information as widget cards. In this architecture, notification portals display business information as widget cards, requiring the use of view files corresponding to the widget cards, such as serialized files in the Remote Views format.

[0283] In one example, a notification portal can generate a view file corresponding to a widget card. The notification portal can obtain business information and generate a view file corresponding to the widget card based on the business information. The notification portal then renders the view file corresponding to the widget card, displaying the business information as a widget card.

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

[0285] In other examples, other architectures besides the Widget architecture may be used in electronic devices, and multiple notification entrances of electronic devices may also support other types of card protocols besides Widget cards, such as JS cards corresponding to the JS architecture, etc., which will not be elaborated on.

[0286] As shown in Figures 7 and 8 of the aforementioned embodiment, the business information for the first application service is generated by the first application, provided by the service provider to the service interaction and presentation framework, and then distributed by the service interaction and presentation framework to the associated target notification portal for display. The service provider can be the data provider component of the first application or the data provider component of the smart module. It should be noted that the service provider for different application services is different.

[0287] In one specific embodiment, the intelligent module monitors application services generated by various applications. Upon monitoring the generation of a first application service by a first application, the intelligent module determines whether the first application has previously registered a widget card display format. If the intelligent module determines that the first application has previously registered a widget card display format, the intelligent module determines that the first application service is designated for display as a widget card.

[0288] The smart module notifies the service interaction and display framework and provides the service interaction and display framework with the identification information of the business provider corresponding to the first application service. The service interaction and display framework can request the business information of the first application service from the business provider based on the identification information of the business provider.

[0289] As shown in Figure 10, it is another software framework diagram of the electronic device corresponding to the Widget architecture. The framework layer includes the service interaction and display framework, the native Widget framework (Android TM The smart module can obtain business information of various application services, such as taxi-hailing, food delivery, high-speed rail itinerary, flight itinerary, etc.

[0290] The service interaction and display framework executes the operations of the host side in the native Widget framework, and requests business information from the smart module through the Widget service of the native Widget framework. The business side Provider of the smart module provides the business information of the first application business to the native Widget framework, and the native Widget framework generates the view file corresponding to the Widget card based on 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 interface 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 business in the Widget card format.

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

[0292] For example, a mobile phone's first application generates a first application service and creates a corresponding first process for the first application service. The mobile phone's interactive display framework displays the service information of the first application service through multiple target notification portals. 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 and second processes. Process isolation prevents the second process from directly obtaining accurate service information from the physical storage space of the first process. The mobile phone can enable inter-process communication (IPC) technology to obtain service information of the first application service.

[0293] The smart module can encapsulate the business information of the first application into a file formatted for cross-process transmission and provide it to the interactive display framework. This file format can be a serialized file in the Remote Views format for Widget cards or a serialized file in the JSON Views format for JS cards.

[0294] The smart module transmits the encapsulated view file across processes to ensure that the view file transmitted to the notification entry is accurate and can be rendered and displayed. The notification entry can then display the business information of the first application business in the corresponding display format.

[0295] As shown in Figure 11, it is a flow chart of executing the display control method based on the Widget architecture. As shown in Figure 11, the provided display control method mainly includes the following steps:

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

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

[0298] 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 portal;

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

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

[0301] The Service Interaction and Presentation Framework determines that the first application service supports display as a widget card. It first calls the native widget framework to process the first application service's business information into a view file in Remote Views format. The native widget framework uses the Remote Views channel to transmit the view file in Remote Views format across processes to the Service Interaction and Presentation Framework. The Service Interaction and Presentation Framework then distributes the view file in Remote Views format to the target notification portal.

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

[0303] FIG12 is a schematic diagram showing an interaction of executing a display control method based on a Widget architecture.

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

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

[0306] The smart module detects that the first application generates a first application service, instructs the interaction display management module (Interaction Display Manager) to start display, and the interaction display module instructs the interaction display service module (Interaction Display Service) of the service interaction and display framework to start display. The input interaction information carried includes quick application information (App Clip Info).

[0307] S1203: The interactive display service module performs callback verification to verify whether the caller has the authority to call the notification entry display.

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

[0309] S12041: Whether the important emergency level is legal;

[0310] S12042: Is the card type supported?

[0311] S12043: Verify the software development kit version corresponding to the installation package in the quick application information to see if it meets the minimum version required by the card.

[0312] The callback check mainly verifies whether the caller has the permission to call the notification entry display.

[0313] Information verification mainly verifies whether the interactive information is qualified. If the verification fails, the callback returns an error code, for example, the error code can be -2.

[0314] The main contents of information verification include: whether the importance and urgency level are legal, and whether the software development kit (SDK) version corresponding to the installation package in the quick application information meets the minimum version required by the card.

[0315] S1205: The interactive display service module queries the notification entry management module for the specification information of the target notification entry to be issued according to the importance and urgency level. If there is no corresponding notification entry, the callback returns an error code -3.

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

[0317] S1207: The interactive display service module instructs the interactive scheduling control module to create an interactive display record lock (Create Interaction Display Record Locked).

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

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

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

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

[0322] S1212: The application widget host returns the widget ID to the widget management service module.

[0323] S1213: The Widget management service module instructs the Widget management service module to bind the business party Provider and Widget ID to the native Widget service.

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

[0325] S1215: The Widget management service module instructs the application Widget host to start monitoring Widget changes.

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

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

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

[0329] S1219: The Widget host applies for business information from the smart module.

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

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

[0332] S1222: The Widget host is used to instruct the Widget monitoring module to update the Widget.

[0333] S1223: The Widget monitoring module sends a creation success message to the Widget management service.

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

[0335] S1225: The interactive display service module instructs the interactive scheduling control module to call to start display locking, obtain Remote Views and retrieve its bound quick application data.

[0336] S1226: The interactive scheduling control module calls to start display locking.

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

[0338] S1228: The application Widget host calls to start display locking.

[0339] S1229: Apply the Widget host to send display data.

[0340] S1230: The Widget host instructs the target notification entry to register and create a callback.

[0341] S1231: The application Widget host ends calling display locking.

[0342] The following describes in detail the solutions for implementing the aforementioned processes 1 to 3 under the Widget architecture.

[0343] Corresponding to the notification portal registration operation in step 1 above, the notification portal must register with the service interaction and presentation framework and provide the supported formats and specifications. After a service is created, the interaction rules engine retrieves the desired notification portal and compares it with the registered information. Only if the registered information supports the corresponding format and specifications can the service be presented.

[0344] As shown in Figure 13, it mainly includes:

[0345] S1301: Registration application.

[0346] The target notification entry registers the notification entry with the Interaction Display Manager and verifies the input parameters. If the parameters are empty, -2 is returned.

[0347] S1302: Add a registration listener.

[0348] Add Register Listener in the interactive display management module. Verify the server. If the service cannot be obtained, return -1. Verify the registration information. If it is already registered, return -2.

[0349] S1303: Registration application.

[0350] The interactive display management module initiates a registration request with the interactive display service module and registers with the interactive scheduling control module to notify the entry lock. The interactive scheduling control module verifies the caller's permissions and returns -2 if the caller does not have permissions. It also verifies the input parameters and returns -2 if they are empty.

[0351] S1304: The registration entry is locked.

[0352] S1305: The registration entry is locked.

[0353] S1306: New entry registration information.

[0354] The interactive scheduling control traverses the incoming notification entry registration information list and registers each notification entry in turn until all notification entries in the notification entry registration information list are registered. If the incoming notification entry does not exist in the local machine during the traversal process, it will be skipped.

[0355] Corresponding to the above process 2, the notification portal displays a Widget card. As shown in Figure 14, it mainly includes the following steps:

[0356] S1401: Create a host view.

[0357] S1402: Create a host view.

[0358] S1403: Instruct to create a host view.

[0359] The host instructs the interactive widget manager to create a host view, and the interactive widget manager instructs the interactive widget host view module to create a host view.

[0360] S1404: Apply Remote Views.

[0361] S1405: Generate a rendering asynchronous task.

[0362] S1406: Instruct to start executing the rendering task.

[0363] The interactive widget host view module applies Remote Views, renders asynchronous tasks (inflate Async), and instructs the asynchronous application task to start executing the task (Start Task On Executor).

[0364] S1407: Processing background.

[0365] S1408: Rendering view.

[0366] S1409: Start transmission execution.

[0367] S1410: Instruct the view application to monitor.

[0368] S1411: Monitor application container.

[0369] S1412: View callback.

[0370] The asynchronous task application processes the background (doLn Background), renders the view (inflate View), starts the transmission execution (On Post Execute), and 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).

[0371] Corresponding to the aforementioned process 3, the notification portal displays updated business information.

[0372] Business updates can be done in two ways: proactively by the business side, and automatically by the service interaction and display framework. As shown in Figure 15, the service interaction and display framework provides an update interface (Update Display Data()), which the business side can proactively call to update data. This mainly involves the following steps:

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

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

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

[0376] The business side notifies the business side's Interaction Display Manager to update the display data, obtain the latest Remote Views from the business side's Provider, write them into the quick app data App Clip Data, and pass the quick app data in.

[0377] S1504: The interactive display service module notifies the interactive display record to update Remote Views.

[0378] S1505: The interactive display service module notifies the interactive scheduling control module to call the display data update lock.

[0379] S1506: The interactive scheduling control module calls display locking.

[0380] The Interaction Display Service of the service interaction framework updates the display data lock and updates the Remote Views to the interaction message. The Interaction Display Service calls the Display Data Update Lock function, and the Interaction Dispatch Controller calls the Display Lock function.

[0381] S1507: The interactive scheduling control module notifies the entry calling module to call entry lock.

[0382] S1508: The entry calling module calls the display lock.

[0383] S1509: The entry calling module calls the lock.

[0384] S1510: Entry calling module calling display.

[0385] S1511: The entry calls the module to create display information.

[0386] S1512: The entry calls the module to send display data.

[0387] S1513: The entry call module notifies the entry call update.

[0388] S1514: The interactive scheduling control module ends calling the display lock.

[0389] The interactive scheduling control sequentially traverses all notification entries corresponding to the interactive display record to complete the data update of each notification entry. During each traversal process, the notification entry is locked and the display information is sent to repackage the Remote Views into the interactive display information. When the notification entry receives the update request callback, it obtains the Remote Views from the input interactive display information and ends the call to display information.

[0390] Figure 16 shows the process flow of the interactive display framework automatically updating the widget card display. It mainly includes:

[0391] S1601: Notification entry indicates interactive display management module display.

[0392] S1602: The interactive display management module notifies the interactive display service module to notify the portal display.

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

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

[0395] S1605: The card display management service module applies to the widget management service module for widget display.

[0396] S1606: The Widget management service module starts locking the main update widget.

[0397] S1607: The Widget management service module sends information delay to the main thread.

[0398] S1608: The main thread instructs the Widget management service module to handle the main update Widget lock.

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

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

[0401] S1611: The application widget host extension module applies to the application widget provider for an update.

[0402] The service interaction and display framework also provides the Notify Display Showed() and Notify Display Hidden() interfaces. 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, to inform the service interaction and display framework of the visibility of the card (capsule).

[0403] When the notification entry side calls Notify Display Showed() to inform the service interaction and display framework that a card (capsule) is visible to the user, the service interaction and display framework will set an automatic update cycle based on the importance and urgency of the business corresponding to this card, and regularly notify the business provider (through the native widget mechanism to send update broadcasts) to update the data.

[0404] In the widget card scenario, the business provider inherits from the native app widget provider. After receiving an update broadcast, the provider creates remote views based on the latest business data, calls the native app widget manager and updates the app widget, and passes the remote views in. The subsequent process is similar to the business creation process: the presentation framework acts as the host in the native widget system. After obtaining the remote views, it queries the interaction rule engine for the expected notification entry based on the urgency of the business, matches it with the notification entry registration information, and distributes the remote views to the corresponding notification entry. Finally, the notification entry uses the remote views to complete the widget card update process.

[0405] This embodiment provides a display control method for widget cards within the widget architecture. The service interaction and display framework, acting as the host, retrieves Remote Views from the provider through the native widget framework and distributes them to the corresponding notification portals, which then display them.

[0406] Example 3

[0407] The mobile phone executes step S503, and the target determined by the mobile phone may include a capsule and a card. The mobile phone needs to obtain the view file corresponding to the capsule and the view file corresponding to the card.

[0408] In one example, a mobile phone supports both widget card and capsule display formats, and can simultaneously transmit view files corresponding to both cards and capsules. Under the widget framework, the mobile phone uses widget card data as the basis while also enabling data transmission in other display formats.

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

[0410] Continuing to refer to the software framework as shown in Figure 10, the service interaction and display framework has added two functional modules: Remote ViewsEx and APP Clip Data. Remote ViewsEx is used to display Widget cards, and APP Clip Data is used to display capsules and multiple devices.

[0411] 1. Each business provider inherits the HnApp Widget Provider to provide card Remote Views of various sizes.

[0412] 2. Each business provider passes capsules and multiple devices (such as watches) (App Clip Data) to the Remote Views extension field through the Remote ViewsEx extension interface.

[0413] 3. Each business provider passes Remote Views to the Interaction Display Service of the service interaction and display framework through the App Widget Service related interface.

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

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

[0416] 6. Once the host receives the App Clip Data, it can analyze its fields and display it based on the device's pre-defined user experience (UX). App Clip Data includes important business data, such as the business logo, business progress, and business brand colors.

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

[0418] As shown in Figure 17, the flow chart of the display control method provided in this embodiment illustrates the specific process of the display control method for displaying cards and capsules at the same time. As shown in Figure 17, the display control method provided mainly includes the following steps:

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

[0420] 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. The target display forms include a card form and a capsule form.

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

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

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

[0424] In one example, as shown in FIG18 , the target notification entry is the negative one screen, which can display the service information of the first application service in both capsule form 1801 and card form 1802 .

[0425] If the phone supports Widget cards, the view files corresponding to the card form can be in the Remote Views format for Widget cards. If the phone supports capsule display, the view files can be in the App Clip Data format for quick apps. During data transfer, the phone can use the Remote Views channel to transfer both Remote Views and capsule display view files to the target notification portal across processes.

[0426] The mobile phone determines the target notification portal associated with the first application service, which may include at least two notification portals from the desktop, negative one screen, quick application center, notification center, control center, status bar, lock screen interface, and continuous display AOD interface. The mobile phone can respond to different user operations and display different entry interfaces of notification portals. When the mobile phone switches the entry interface of different notification portals, if the notification portal displayed by the switch belongs to the target notification portal, the service information of the first application service will be displayed in the notification portal.

[0427] The display control method provided in this embodiment displays the service information of the first application in multiple notification portals after the first application generates the first application service, thereby reaching the user. While the first application service is running, even if the user switches to multiple different portal interfaces through multiple operations, the mobile phone can continue to display the service information of the taxi service through different notification portals.

[0428] In one example, the mobile phone executes step S1704, which can refer to steps S203 and S204 in the aforementioned embodiment. The mobile phone responds to the second operation and the third operation respectively, switching different target notification entrances to display the service information of the first application service.

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

[0430] The second and third operations are identical, indicating that the first and second notification portals entered by the mobile phone are the same. In other words, in response to a user operation, the mobile phone enters a notification portal interface, where the mobile phone displays service information for the first application service in both a card and a capsule.

[0431] The second and third operations are different operations, indicating that the first and second notification portals entered by the mobile phone are different notification portals. However, both notification portals are target notification portals associated with the first application service. Both notification portals can display the service information of the first application service. However, the display format of the entry interface of these two types of notification portals is different. In response to the second operation, the mobile phone enters the entry interface of the first notification portal, displaying the service information of the first application service as a card. In response to the third operation, the mobile phone enters the entry interface of the second notification portal, displaying the service information of the first application service as a capsule.

[0432] Figure 19 shows a flowchart of the mobile phone's software framework executing the display control method. The electronic device transmits card and capsule data simultaneously, which mainly includes the following processes:

[0433] S1901: The target notification portal registers the card size and whether capsule data is required with the interactive display service module.

[0434] Corresponding to the notification entry registration operation in the aforementioned process 1.

[0435] The notification portal registers its display capabilities with the Interaction Display Service. It also registers the card sizes it supports. Card sizes typically include 4*2, 4*2, and 2*2, and the notification portal selects one of these sizes as the default size for displaying cards.

[0436] Furthermore, considering that some notification portals can display both cards and capsules, while others only support cards and not capsules, when a notification portal registers with the service interaction and presentation framework, it also registers whether it supports capsule display. Registering for capsule display indicates whether the business party needs to provide the data required for capsule display. S1902: The interactive display service module notifies the business party provider to generate the first application service (carrying the service ID and the business party provider's identification information).

[0437] S1903: The interactive display service module notifies the application widget service module to bind the application widget.

[0438] S1904: The application widget service module requests an update from the business provider.

[0439] S1905: The business provider creates card display files of different sizes (4*2, 4*1, 2*2).

[0440] S1906: The business provider creates capsules, multiple devices, and watches to display quick app data.

[0441] S1907: The business side Provider notifies the Remote ViewsEx extension module of the extended data (Remote Views, App Clip Data).

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

[0443] S1909: Through the Remote Views channel, the business provider notifies the application widget service module to update the application widget data.

[0444] S1910: The application widget service module notifies the interactive display service module to update the application widget.

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

[0446] S1912: The target notification portal notifies the interactive Widget management module to create a host view Create Host View.

[0447] S1913: The interactive widget management module returns the card view to the target notification portal.

[0448] S1914: The target notification portal displays the View.

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

[0450] In one example, the business provider can create Remote Views corresponding to the registered specifications and sizes based on the specifications and sizes registered by the notification portal.

[0451] In another example, the business side can also directly generate view files corresponding to cards of all sizes, so there is no need to distinguish the sizes registered for each notification entry.

[0452] The business provider creates the files required for capsule display and inserts the business information into the quick app data App ClipData. It should be noted that the data required for capsule, multi-device, or watch display does not require serialization and can be transmitted through App Clip Data.

[0453] The business provider calls the extended interface Remote ViewsEX in the service interaction and presentation framework, inserts the card view file Remote Views and the capsule view file App Clip Data as extended data (Set Hn ExaData), and inserts them into the Remote Views channel in the native widget framework. The data is then updated to the application widget service of the service interaction and presentation framework (Update APP Widget Remote Views) in the form of application widget data.

[0454] The App Widget service passes the files received from the Remote Views channel within the native widget framework to the Interactive Display service, which parses them into card view files (Remote Views) and capsule view files (App Clip Data). The Interactive Display service then distributes the parsed Remote Views and App Clip Data to the associated notification portal.

[0455] The notification portal 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 portal can also parse App Clip data to display capsules.

[0456] The display control method provided in the above embodiment of the present application targets scenarios where the notification portal needs to display both Widget cards and capsules at the same time. The card view file Remote Views and the capsule view file App Clip Data are inserted into the Remote Views channel as extended data to achieve synchronous cross-process transmission of the business information required for capsule display to the service interaction and display framework. After receiving the data transmitted by the smart module, the service interaction and display framework parses the data to obtain serialized data and basic business information, and displays the Widget card and capsule respectively. The service interaction and display framework can also provide basic business information to the multi-device notification portal, which will display business information in other display forms.

[0457] Example 4

[0458] The mobile phone executes S202 in the aforementioned embodiment 1, which is the target notification entry determined by the mobile phone for the first application service, and may also include notification entries provided by other devices other than the mobile phone. The mobile phone executes the display operation of S203 or S204 in the aforementioned embodiment 2, which is the display operation of the notification entry of other devices.

[0459] For example, the business information of an order generated by a taxi app on a mobile phone can be transferred to a watch or car computer connected to the mobile phone for display. For ease of description, this embodiment uses the term "external device" to refer to one or more devices connected to the mobile phone that can support the notification portal display function.

[0460] Figure 20 shows the interaction between a mobile phone and a watch. Mobile phone 2001 can display the generated first application service information via a card. Mobile phone 2001 can also transmit the service information to watch 2002, which is connected to mobile phone 2001, for display. The watch can provide notification portals such as a desktop and a notification center, each of which can display service information in a card and / or capsule format.

[0461] Figure 21 shows a schematic diagram of the interaction between a mobile phone, a watch, and a vehicle computer. Mobile phone 2101 can display the generated business information of the first application business via a card. Mobile phone 2101 can also transmit the business information to a watch 2102 connected to mobile phone 2101 for display, or to a vehicle computer 2103 connected to mobile phone 2101 for display. External devices such as watches and vehicle computers can provide notification portals such as desktops and notification centers. Each notification portal can display business information in a display format such as cards and / or capsules.

[0462] In one example, the mobile phone can use the external device as a notification portal. In this case, the mobile phone does not need to distinguish the number and type of notification portals supported by the external device. Regardless of how many notification portals the external device supports, the mobile phone can only use the external device as a notification portal and provide the business information of the corresponding notification portal to the watch. The watch then distributes the received business information to each notification portal for display. The data transmission solution in which the mobile phone uses the external device as a notification portal can reduce the communication frequency and total data transmission between the mobile phone and the watch, and improve the efficiency of data transmission across devices.

[0463] In another example, the phone can also distinguish between the various notification portals available on the external device. When providing service information to the external device, it can distinguish different notification portals and provide corresponding service information. For example, if the external device supports three notification portals: desktop, control center, and notification center, then the watch can provide service information corresponding to these three notification portals to the external device. This can eliminate the need for the external device to regenerate and distribute service information for multiple notification portals, reducing the related work of the external device.

[0464] As shown in Figure 22, it is a schematic diagram of the connection between the mobile phone and the external device. The mobile phone includes a smart side, a service interaction and display framework, a notification portal 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 business and the business information that needs to be displayed by calling the notification portal. The service interaction and display framework distributes the business information to the notification portal associated with the first application business, and the notification portal displays it. It should be noted that the notification portal here refers to the notification portal of the mobile phone, such as the desktop, the negative one screen, etc.

[0465] The mobile phone also includes a cross-device communication module, and the service interaction and display framework also includes a corresponding cross-device communication serialization interface (Android ARchive, AAR). The service interaction and display framework transmits data with the cross-device communication module through the cross-device communication serialization interface, and transmits business 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 interactive display module can be Synergy TM AAR. The cross-device communication module can realize data transmission through communication methods such as Bluetooth, Wi-Fi, and cellular networks.

[0466] The cross-device communication module enables the phone to communicate with external devices such as watches. Furthermore, the module monitors the connection status between the phone and the external device to ensure efficient information transmission and reach. Furthermore, the module can also receive commands sent from the external device to the phone, enabling functions such as portal registration, information acquisition, and information updates.

[0467] The mobile phone executes the display control method provided in this embodiment, responds to the first application service generated by the first application, transmits the service information across devices to the external device, and displays the service information on the external device. The cross-device transmission process between the mobile phone and the external device mainly includes active triggering operations initiated by the mobile phone and push requests actively applied for by the external device. Scenarios in which the mobile phone actively initiates active triggering requests may include scenarios such as service creation, update, and deletion. Scenarios in which the external device actively applies for push requests may include scenarios in which the watch is disconnected and reconnected and then applies for sending service information.

[0468] 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 business information provided by the service interaction and display framework can be serialized and sent to the cross-device communication module. The cross-device communication module then sends it to the external device. The external device can parse the original business information according to the pre-stored protocol and render the business information into cards, capsules, etc. for display.

[0469] In a solution where a mobile phone displays business information in the notification portal, the service interaction and display framework only needs to configure a notification portal distributor, with each notification portal distributor corresponding to a notification portal. After the interactive display module obtains the business information from the service provider, it calls each notification portal distributor to distribute the business information to each notification portal.

[0470] As shown in Figure 23, the display control method provided in the embodiment of the present application involves a flow chart of a mobile phone transmitting business information to an external device. The display control method provided in this embodiment adds a solution for sending business information on the mobile phone side to multiple devices such as watches for display. The provided display control method mainly includes the following process:

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

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

[0473] S2303: During the operation of the first application service, in response to the second operation, the service information of the first application service is sent 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.

[0474] S2304: In response to the third operation, the service information of the first application service is displayed on the entry interface of the target notification entry.

[0475] This embodiment involves information exchange between two electronic devices. For ease of description, an external device that establishes a communication connection with a mobile phone is defined as a target device. The target device can be a wearable device such as a watch, or it can be a vehicle computer. The target device can also provide one or more notification portals to display service information of application services generated by the first electronic device.

[0476] After the mobile phone generates a taxi service, the business information of the taxi service is sent to the watch. The watch can display the business information of the taxi service in the form of cards or capsules on the desktop, notification center and other entrances.

[0477] In response to the second operation, the mobile phone may send 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 entry interface of the notification portal of the target device. The mobile phone may also respond to the third operation by displaying the service information of the first application service on the entry interface of the target notification portal. The second and third operations may be the same operation or different operations.

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

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

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

[0481] In response to the fourth operation, displaying the service information of the first application service on the entry interface of the notification entry provided by the target device;

[0482] Among them, the third notification entrance is a notification entrance of the second type of notification entrance associated with the first application service in the target device; the second type of notification entrance includes at least one notification entrance of the desktop, negative one screen, quick application center, notification center, control center, status bar, lock screen interface and continuous display AOD interface.

[0483] Figure 24 shows a schematic diagram of a mobile phone supporting multi-device transmission and display. In a scenario where a mobile phone transmits business information across devices to display on the portal interface of another external device, the service interaction and display framework distributes notification portals not only for the mobile phone itself but also for external devices. Therefore, the service interaction and display framework's business information distributor can include device-level distributors, each corresponding to an external device connected to the mobile phone. The device-level distributor is used to distribute business information obtained by the service interaction and display framework to the external device connected to the mobile phone.

[0484] A mobile phone can set up a virtual notification portal for an external device to reduce data transmission between the phone and the external device. For example, if the external device is a watch, the phone will call the Watch Dispatcher as an abstraction of this virtual notification portal. The Watch Dispatcher is similar to the Entrance Dispatcher on the phone's native portal. It should be noted that this abstract virtual notification portal may not be identical to the phone's native notification portal. Because the watch already registers its display function through the cross-device communication module, it does not need to register its display function with the service interaction and presentation framework as a notification portal. When the cross-device communication module between the phone and watch detects a communication connection between the two, the phone can transmit service information to the watch for display. If the cross-device communication module detects a disconnection, the phone cannot transmit service information to the watch for display.

[0485] Continuing with Figure 24, watch data is first passed to the quick app data (APP Clip Data), and then provided to the service interaction and display framework via interaction messages. Quick app data includes card data (Remote Views), capsule data (Capsule Data), and watch data. Interaction messages include various types of data, including service type (mService Type), service name (mService Name), service ID (mService ID), and service status (mService State).

[0486] The scope hierarchy of the electronic device calling object includes display form, notification entry and device in sequence. The corresponding display records in the electronic device also include display records, entry display records, device display records and interactive display records. Among them, the display record is an atomic record and can be uniquely determined by device + entry + form. The display record includes the entry display record transmitted upward and multiple parameter fields, such as visible (Enable), delete (Delete), top (Show On Top), update event (Update Time), creation time (Create Time), current state (Cur State) is the display record state (Display Record State), etc.

[0487] Entrance Display Records are entry-level service records that may need to be distributed to multiple shapes. They include device display records, notification entries, and display records that are transmitted upstream. You can use the lookup function (Array Map) to find the display record corresponding to a shape.

[0488] A Device Display Record is a device-level service record that may need to be distributed to multiple portals. It includes the device type, the interaction display record (transmitted upward), and the portal display record (transmitted downward). A device display record can be found by using the search function to find the portal display record corresponding to the notification portal.

[0489] Interaction display records are atomic service records and need to be distributed to multiple devices. Interaction display information includes interaction information, interaction display records, and device display records. Interaction display records can be searched for device display records corresponding to device types using the search function.

[0490] The notification portals of the mobile phone include AOD, Lock Screen, Launcher, Nagative Screen, Notification Center, Control Center, Global Status Bar, Magic Gate, Multiple Devices, etc. Among them, Multiple Devices includes the notification portal of the external watch.

[0491] When the phone calls the Entrance Dispatcher, it verifies the Entrance Registration Info and Registration Status, and searches for the corresponding Entrance Display Record. When the watch calls the Entrance Dispatcher, it calls the Entrance.

[0492] When the mobile phone makes a device call (Device Dispatcher), it verifies the device type and entry call, searches for the entry call corresponding to each notification entry included in the device, and hands it over to the interactive dispatcher for control.

[0493] As shown in Figure 25, the display control method provided for the embodiment of the present application involves a flow chart of transmitting business information to an external device. The smart side includes a smart module and an interactive display management module (Interaction Display Manager), and the service interaction and display framework includes an interactive display service module (Interaction Display Service), a card display implementation module (Card Display Internal), an interactive 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 (Channel Listener). The cross-device communication module includes a channel service provider module (Channelserver Provider). In this embodiment, the transmission of the watch data Watch Data required by the watch needs to rely on the solution of the Widget service to transmit Remote Views and quick application data App Clip Data.

[0494] S2501: The smart module notifies the interactive display management module to start displaying.

[0495] S2502: The interactive display management module notifies the interactive display service module to start displaying.

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

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

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

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

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

[0501] S2508: The interactive display service module notifies the interactive scheduling control module to call the display start locking.

[0502] S2509: The interactive scheduling control module calls the display start locking.

[0503] S2510: The interactive scheduling control module notifies the watch calling module to call display lock.

[0504] S2511: The watch calling module sends information to the channel unit.

[0505] S2512: The channel unit confirms the calling service provider Provider.

[0506] S2513: The channel unit calls the service provider Provider.

[0507] S2514: The channel service provider module is bound to the business provider.

[0508] S2515: The channel unit obtains the notification information result.

[0509] S2516: The channel unit applies for information results from the channel information providing module.

[0510] S2517: The channel information providing module returns the information result to the channel unit.

[0511] S2518: The channel unit sends the information result to the watch calling module.

[0512] S2519: The watch calling module sends the information result to the interactive scheduling control module.

[0513] S2520: The interactive scheduling control module ends calling the display lock.

[0514] The business side will predetermine whether the notification entry point for the business information generated by its application business will include external devices, such as watches. When the smart service starts displaying the notification, the incoming parameters must include watch data. This data is encapsulated and serialized by the business side according to the communication protocol between the business side and the watch.

[0515] When building App Clip Data, the business provider determines that the business information needs to be transferred to the watch display. It will add Watch Data to the App Clip Data when transmitting Remote Views. If the importance and urgency of the business matches the watch notification entry, the multi-device flow process will be used when the business is delivered. The overall interaction process specifically includes:

[0516] Smart service notification interaction display management starts displaying. The input interaction message (Interaction Message) contains quick application data App Clip Data, which is transmitted to the service interaction and display framework.

[0517] Within the service interaction and display framework, the Interaction Display Service creates an Interaction Display Record Locked to the Interaction Scheduling Control. The Interaction Display Service begins creating cards. Depending on the card type, different service processes are followed. The widget uses the Widget Management Service to handle the widget card creation process.

[0518] The service interaction and presentation framework first obtains the Remote Views object through the Widget framework and then enters the distribution process. If the switch for the external device notification entry is turned on and the business provider provides watch data, the watch flow process begins.

[0519] Because the Watch Data required for watch display depends on the Remote Views required for card display, the phone, at this distribution point, typically checks the card data to ensure proper display of the watch data. Once the card display is created on the phone, it triggers a notification to the Widget Management Service to generate a widget creation operation, thus entering the watch flow.

[0520] Of course, if you don't consider whether the watch data can be displayed normally, the mobile phone can also not refer to the display status of the card data. After obtaining the watch data, it will enter the watch circulation process.

[0521] After entering the watch flow, the interactive dispatch control calls the Dispatch Display Start Locked watch call, sending business information to the cross-device communication module through the channel unit, realizing the flow of business information from the phone to the watch. After receiving the business information, the watch renders the display according to its own view display logic.

[0522] Normally, the service interaction and display framework of the mobile phone transmits business information to the watch through the cross-device communication module in the form of a single push. In other words, even if there are business information of multiple application businesses on the mobile phone that need to be transferred to the same watch, the mobile phone will push a single message for the business information of each application business separately, and distinguish the business status changes such as creation, update, and deletion of the business information of each application business. In general, the push service from the mobile phone to the watch is a one-way service, mainly the mobile phone notifies the watch to create, update, and delete the display.

[0523] If the phone and watch are disconnected and then reconnected, the service status of some apps may have changed during this process, such as ending, updating, or adding new apps. If the phone only notifies the watch of newly generated service information after reconnection, some service information may be displayed abnormally. For example, service information for terminated apps cannot be deleted, service information for newly added apps cannot be displayed, and service information for existing apps cannot be accurately updated. The following example illustrates this.

[0524] For example, before the phone and watch are disconnected, there are two services: taxi service 1 (the driver has accepted the order and is 2 kilometers away from the passenger) and food delivery service 2 (waiting for the merchant to accept the order). The phone pushes the service information of taxi service 1 and food delivery service 2 to the watch separately, and the watch displays the service information of taxi service 1 and food delivery service 2 respectively.

[0525] The phone and watch are disconnected. For taxi service 1, the service status changes from driver accepted to driver canceled, ending taxi service 1. For food delivery service 2, the service status changes from waiting for the merchant to accept the order to the rider delivering the food.

[0526] The phone and watch reconnect. At this point, since Taxi Service 1 has ended, the Service Interaction and Display Framework will no longer notify the watch to delete the displayed information for Taxi Service 1, according to the single push rule. A possible scenario is that the watch will continue to display information for Taxi Service 1, remaining in the driver-accepted state or in an abnormal state. Alternatively, the watch may automatically clear abnormal information according to pre-set automatic clearing rules. Both of these solutions may result in the watch displaying abnormal information and misleading the user.

[0527] The solution provided by the embodiment of the present application executes a full push solution instead of a single push solution each time the mobile phone and the watch are disconnected and reconnected. The full push solution can be understood as pushing the business information of all current application services to the watch at the same time. As shown in Figure 26, the watch sends a full 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 push request from the watch, it calls all business records (Dispatch All Records) and sends them in full to the watch (Dispatch To Watch).

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

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

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

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

[0532] When the watch is disconnected and then reconnected to the phone, it can send a full push request to the phone, requesting that the phone push all service information for all currently available services to the watch. In this case, after receiving the full push, the watch verifies the currently displayed service information, deletes information for completed services, updates information for services with changed status, and creates information for newly added services.

[0533] In specific implementations, after the phone and watch are disconnected and then reconnected, the watch can send a full push request to the phone. In this way, the watch side actively initiates a full push request based on display requirements, ensuring comprehensive data while minimizing unnecessary data transmission. Of course, in other implementations, the phone can also actively send full service information to the watch, allowing the watch to verify and update the displayed service information based on the full service information.

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

[0535] The format of the file header may be as shown in Table 3 below, and the type and description of each field in the file header may be as shown in Table 4.

[0536] Table 3

[0537] Table 4

[0538] Most of the data provided by the phone to the watch is business information provided by the business provider. The Service Interaction and Display Framework calls WatchData.getData() to retrieve this data from the business provider. In some cases, the watch data must be created by the Service Interaction and Display Framework and then sent to the watch. For example, if the watch has already created a display for the corresponding application service and the urgency level of the application service changes, the associated watch virtual notification portal will no longer serve as the notification portal for displaying business information, effectively shutting down the phone-to-watch flow. Alternatively, if the application service ends, the watch display created for the corresponding application service needs to be deleted.

[0539] Table 5 shows a mapping table of the interaction specifications between the important emergency levels of application services and watches. It should be noted that this is only an example and is not limited to a specific flow scheme between mobile phones and watches.

[0540] Table 5

[0541] As shown in Table 5, when the taxi service is waiting for the driver to accept the order, the importance and urgency level is L21, and the taxi service does not need to be displayed on the watch at this time. 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 a service creation information to the watch, so that the watch can display the taxi information. If the driver cancels the order, the importance and urgency level may be reduced back to L21, and the current importance and urgency level does not need to be displayed on the watch. Therefore, based on the service creation information previously sent by the service interaction and display framework to the watch, the phone needs to call the service interaction and display framework to send a notification to delete the service information to end the display process of the taxi service on the watch.

[0542] Messages sent from the phone to the watch consist of a file header and a file body. Phones typically store instructions and data in the file body to ensure security. Notifications sent from the phone to the watch regarding the deletion of service information can be stored directly in the file header. This allows the watch to retrieve the notification by simply parsing the file header, saving file parsing.

[0543] In summary, the display control method provided in the embodiment of the present application is based on the notification framework of the native system. The electronic device presents the business information of the application business generated by each application in the form of a notification on the entry interface of each notification entry, and can match different entry display schemes according to the importance and urgency level of different application businesses, so that users can receive messages and take corresponding actions in various scenarios. Users can see the latest service information on various entry interfaces such as the desktop, notification, AOD, negative one screen, lock screen, and even wearable devices without having to find the corresponding application interface to obtain service information. It breaks the traditional status quo of "people looking for services" and truly realizes "services looking for people", greatly improving the user experience.

[0544] 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 the display and the memory are both 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 above embodiment. In addition to these main components, the electronic device also includes components for implementing basic functions, which will be specifically described below in conjunction with Figure 27.

[0545] FIG27 is a schematic diagram of the structure of an electronic device 2700 provided in an embodiment of the present application. 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, and the like.

[0546] The structure shown in the embodiment of the present invention does not limit the electronic device 2700. The electronic device 2700 may include more or fewer components than shown, or some components may be combined or separated, or arranged differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0547] 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). The different processing units may be independent devices or integrated into one or more processors.

[0548] The controller is the decision-maker that directs the various components of electronic device 2700 to coordinate operations according to instructions. It serves as the nerve center and command center of electronic device 2700. Based on instruction opcodes and timing signals, the controller generates operational control signals to control instruction fetching and execution.

[0549] Processor 2710 may also include memory for storing instructions and data. In some embodiments, the memory in processor 2710 is a high-speed cache memory that can store instructions or data that have just been used or are being recycled by processor 2710. If processor 2710 needs to use an instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces processor 2710's waiting time, and thus improves system efficiency.

[0550] In some embodiments, the processor 2710 may include an interface. The interface 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.

[0551] The interface connection relationship between the modules shown in the embodiment of the present invention is for illustrative purposes only and does not limit the structure of the electronic device 2700. The electronic device 2700 may adopt different interface connection methods or a combination of multiple interface connection methods in the embodiment of the present invention.

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

[0553] 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 input from the battery chip 2742 and / or the charging management module 2740 and provides power to the processor 2710, the memory 2720, the display 2750, the camera 2780, and the communication module 2760. The power management module 2741 can also be used to monitor parameters such as the charging management module capacity, the number of charging management module cycles, and the health status (leakage, impedance) of the charging management module. In some embodiments, the power management module 2741 can also be provided in the processor 2710. In some embodiments, the power management module 2741 and the battery chip 2742 can also be provided in the same device.

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

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

[0556] 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) network), Bluetooth (Blue Tooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), etc., which are applied to the electronic device 2700. The communication module 2760 can be one or more devices that integrate at least one communication processing module. The communication module 2760 receives electromagnetic waves via an antenna, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 2710. The communication module 2760 can also receive the signal to be sent from the processor 2710, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna.

[0557] 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, so 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 technology. GNSS may include the Global Positioning System (Satellite Based Augmentation Systems, SBAS), the Global Navigation Satellite System (GLONASS), the BeiDou navigation Satellite system (BDS), the Quasi-Zenith Satellite System (QZSS) and / or the Satellite Based Augmentation System (SBAS).

[0558] Electronic device 2700 implements display functionality through a GPU, display screen 2730, and an application processor. The GPU is a microprocessor for image processing that connects display screen 2750 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 2710 may include one or more GPUs that execute program instructions to generate or modify display information.

[0559] Display screen 2730 is used to display images, videos, etc. Display 2750 includes a display panel. The display panel can be a liquid crystal display (LCD), organic light-emitting diode (OLED), active-matrix organic light-emitting diode or active-matrix organic light-emitting diode (AMOLED), flexible light-emitting diode (FLED), mini-LED, micro LED, micro-OLED, quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 2700 may include one or N displays 2750, where N is a positive integer greater than 1.

[0560] The electronic device 2700 can implement a shooting function through an ISP, a camera 2780, a video codec, a GPU, a display, and an application processor.

[0561] The electronic device 2700 can implement audio functions such as music playback and recording through the audio module 2770, the speaker 2770A, the receiver 2770B, the microphone 2770C, the headphone jack 2770D, and the application processor.

[0562] Keys 2790 include a power button, a lock screen button, a volume button, and the like. Keys 2790 may be mechanical keys or touch-sensitive keys. Electronic device 2700 receives input from keys 2790 and generates key signal input related to user settings and function control of electronic device 2700.

[0563] Motor 2791 can generate vibration prompts. Motor 2791 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. Touch operations acting on different areas of the display 2750 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0564] The display control methods in the aforementioned embodiments can all be implemented in the electronic device 2700 having the aforementioned hardware structure.

[0565] On the basis of the above embodiments, an embodiment of the present application further provides a display control device, which includes a processor, and the processor is used to execute the display control method provided by the above embodiments.

[0566] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the display control method provided in the above embodiment.

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

[0568] The specific implementation methods 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 about by them can be found in the specific implementation process of the display control method provided in the aforementioned embodiments and the technical effects brought about by them, which will not be repeated here.

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

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

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

[0572] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited to this. Any changes or replacements within the technical scope disclosed in the embodiment of the present application should be included in the protection scope of the embodiment of the present application. Therefore, the protection scope of the embodiment of the present application should be based on 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 corresponding to the first application service; wherein, the target notification entry includes a first notification entry and a second notification entry; During the operation of the first application service, in response to a second operation, display a second interface corresponding to the first notification entry, wherein the second interface includes service information of the first application service; and / or In response to a third operation, display a third interface corresponding to the second notification entry, wherein the third interface includes service information of the first application service; Wherein, the first notification entry is different from the second notification entry.

2. The display control method according to claim 1, wherein The notification entries of the electronic device include: desktop, negative first screen, notification center, control center, status bar, lock screen interface, AOD interface, and quick application center.

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

4. The display control method according to any one of claims 1 to 3, characterized in that, Before the step of, during the operation of the first application service, in response to a second operation, display the second interface corresponding to the first notification entry, the method further includes: Determine a 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, in response to a second operation, display the second interface corresponding to the first notification entry includes: In response to the second operation, display the service information of the first application service on the second interface in the first display form; And / or, The step of, in response to a third operation, display the third interface corresponding to the second notification entry includes: In response to the third operation, display the service information of the first application service on the third interface 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, and one or more display forms corresponding to the target notification entry; Use 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 target display form of the first application service.

7. The display control method according to any one of claims 1 to 6, characterized in that, The electronic device includes a service interaction display framework. Before the step of determining the target notification entry corresponding to the first application service, the method further includes: In response to the startup of the electronic device, a target notification entry of the electronic device sends a registration application to the service interaction display framework. After the target notification entry successfully registers with the service interaction display framework, the service interaction display framework is allowed to send service information of the first application service to the target notification entry.

8. 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: Searching, from a pre-stored entry mapping table, for a notification entry corresponding to the first importance and urgency level as the current target notification entry corresponding to the first application service; wherein the entry mapping table stores different notification entries corresponding to different importance and urgency levels.

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: Searching, from a pre-stored entry mapping table, for a notification entry corresponding to the first importance and urgency level; Detecting whether a registration application has been initiated for the notification entry corresponding to the first importance and urgency level; Taking the notification entry that has initiated the registration application among the notification entries corresponding to the first importance and urgency level as the target notification entry.

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, displaying a second interface corresponding to the first notification entry further includes: In response to an update of the service information of the first application service, displaying the updated service information of the first application service on the second interface; and / or The step of, in response to a third operation, displaying a third interface corresponding to the second notification entry further includes: In response to an update of the service information of the first application service, displaying the updated service information of the first application service on the third interface.

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 an update of the service state of the first application service, determining a second importance and urgency level corresponding to the second service state according to the updated second service state of the first application service; Updating the target notification entry corresponding to the first application service according to the second importance and urgency level corresponding to the second service state.

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, displaying a second interface corresponding to the first notification entry, and / or, in response to a third operation, displaying a third interface corresponding to the second notification entry, the method further includes: In response to the end of the operation of the first application service, stopping the display of the service information of the first application service on the target notification entry.

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

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program which, when running on a computer, causes the computer to execute the display control method according to any one of claims 1 to 12.

Images