Cross-application interface display method and electronic device

Abstract

The present application provides a cross-application interface display method and an electronic device. The method comprises: displaying a user interface of a first application, wherein the user interface comprises first shared content of a second application; receiving a first operation of the user on the first shared content; and in response to the first operation, running a vertical domain service independent process of the second application, and displaying a first interface of a vertical domain service of the second application; and when a main process of the second application is running, displaying a second interface of the main process of the second application, wherein the vertical domain service independent process is different from the main process. According to the method provided by the present invention, a user can quickly use, in a first application, a service provided by a second application, thereby solving the problems of long interaction path, tedious operation, and poor user experience caused by the need of starting a main process of a second application when a service provided by the second application is used in a first application.

Description

Cross-application interface display method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 5, 2023, with application number 2023111410992 and application name “A cross-application interface display method and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of image processing and display technology, and more specifically, to a cross-application interface display method and electronic device. Background Art

[0003] With the rapid development of electronic technology, there are more and more types of applications on electronic devices. When a user is using an application, he or she may need to use the service provided by application B in application A.

[0004] Currently, when a user needs to access a service provided by application B within application A, they are typically directed to open application B from a browser after multiple redirects within application A, or they are required to open the corresponding mini-program within application A and launch application B before they can use the service. Both of these implementations require long interaction paths between applications, preventing users from quickly redirecting to and using the service provided by application B, which increases the power consumption of electronic devices.

[0005] Therefore, how users can achieve service jumps and direct access between applications is a problem that needs to be solved at present.

[0006] Summary of the Invention

[0007] The present application provides a cross-application interface display method and electronic device, which solves the problem of long interaction path and increased power consumption of the device electronic device caused by the need to start application B when using the service provided by application B in application A, thereby improving the user experience.

[0008] In the first aspect, the present application provides a cross-application interface display method. The method provided in the first aspect can be executed by an electronic device, or by a module applied in the electronic device (such as a processor, chip, or chip system, etc.), or by a logical node, logical module or software that can realize all or part of the functions of the electronic device. The present application does not limit this.

[0009] Specifically, the method includes: displaying the user interface of the first application, which includes the first shared content of the second application; receiving a first operation of the user on the first shared content; in response to the first operation, running the independent process of the vertical domain service of the second application, and displaying the first interface of the vertical domain service of the second application; when running the main process of the second application, displaying the second interface of the main process of the second application, the independent process of the vertical domain service is different from the main process.

[0010] The method provided in the first aspect is that when the electronic device receives the first operation of the user to share content of the second application in the user interface of the first application, the electronic device displays the first interface provided by the vertical domain service of the second application by running the independent process of the vertical domain service of the second application in the first application, and the second application does not need to pull up the main process to display the first interface. This method allows the user to quickly use the services provided by the second application (for example, preview, share, etc.) in the first application without starting the main process of the second application, thereby avoiding the problems of long interaction path, cumbersome operation, and waste of electronic device power consumption caused by starting the main process of the second application, thereby improving the user experience.

[0011] For example, the first operation may be a preview (open) operation, a share operation, or an edit operation on the first shared content of the second application. Of course, the first operation may also be other operations.

[0012] It should be understood that the first shared content of the second application may refer to generating a link related to the shared content in the second application and sending the link to the first application, or it may refer to generating a QR code related to the shared content in the second application and sending the QR code to the first application. Of course, the shared content of the second application may also be in other forms, which is not limited in the embodiments of the present application.

[0013] In a possible implementation of the first aspect, running the vertical domain service independent process of the second application includes: creating a vertical domain service independent process, the vertical domain service independent process is used to run the vertical domain service of the second application, the vertical domain service is used to represent: a display interface when the second application is run in response to a first operation; when the vertical domain service is started, drawing a first interface based on the vertical domain service; loading the first interface into the first application. In addition, when the vertical domain service independent process is already running, in response to a user operation, the vertical domain service independent process can add a corresponding instance to display the corresponding interface through the instance. The instance can be a window instance newly added in the original thread of the vertical domain service independent process.

[0014] In this implementation, the electronic device creates an independent vertical domain service process for the second application based on the user's first operation. The independent vertical domain service process can load independent resources required by the application and does not rely on the second application main process and resources. Therefore, this method can make the power consumption of the electronic device lower. When the vertical domain service is started, the first interface is drawn based on the vertical domain service, and then the first interface is loaded into the first application to realize the display of the interface set by the second application in the first application.

[0015] In some examples, the vertical domain service of the second application can be developed by developers based on a vertical domain service template during the application development phase. It can also be understood that the developer can set the display interface to be loaded based on the vertical domain service template.

[0016] In a possible implementation of the first aspect, before displaying the first interface of the vertical service of the second application, the method also includes: determining a vertical service control in the first application, the vertical service control being used to limit the display area of ​​the first interface, and the first interface being displayed in the vertical service control.

[0017] In this implementation, the electronic device creates a vertical service control in the first application, and displays the first interface in the vertical service control. The vertical service control can determine the display position or display area of ​​the first interface.

[0018] In a possible implementation of the first aspect, the first application corresponds to a graphic node tree, the graphic node tree includes a graphic node tree identifier, the graphic node tree identifier includes an identifier of a vertical domain service control, and the first interface is loaded in the first application, including: mounting the node of the first interface on the graphic node tree of the first application based on the identifier of the vertical domain service control, and loading the first interface in the first application according to the graphic node tree of the node on which the first interface is mounted.

[0019] In this implementation, the mounting position of the first interface of the second application on the first application interface can be determined by using the identifier of the vertical domain service control on the graphic node tree.

[0020] In a possible implementation of the first aspect, the vertical domain service independent process can run a first vertical domain service and a second vertical domain service, the first vertical domain service includes a control corresponding to the second vertical domain service, and the first vertical domain service and the second vertical domain service are different.

[0021] It should be understood that the first vertical domain service and the second vertical domain service run in the same vertical domain service independent process.

[0022] In this implementation, the independent vertical domain service process can load multiple vertical domain services, and the first vertical domain service among the multiple vertical domain services includes controls corresponding to the second vertical domain service. Then, when the user is using the first vertical domain service, he can quickly switch to the second vertical domain service as needed, thereby improving the user experience.

[0023] For example, when the second application is a document application, in response to a user's operation of previewing the document, the electronic device may create an independent vertical service process that runs multiple vertical services, such as a preview vertical service and an edit vertical service. The preview vertical service includes a control for the edit vertical service. When the user needs to edit the document after previewing it, they can directly switch from the preview vertical service to the edit vertical service, thereby improving the user's office efficiency.

[0024] In a possible implementation of the first aspect, the method also includes: displaying a user interface of a third application, the user interface of the third application including the second shared content of the second application; receiving a second operation of the user on the second shared content of the second application; in response to the second operation on the second shared content, running an independent process of the vertical domain service of the second application, and displaying a third interface of the vertical domain service of the second application, the vertical domain service of the second application including a display window of the third application, and the display window of the third application is different from the display window of the first application.

[0025] In this implementation, when the first application and the second application both launch independent processes of the second application's vertical domain service, the electronic device creates multiple window instances in the vertical domain service provided by the second application, and sets the first interface according to the multiple window instances, thereby ensuring that each vertical domain service control corresponds to a window, each displaying an interface, and does not affect the interaction with each other.

[0026] It should be noted that the first operation and the second operation can be the same type of operation, for example, they can both be operations to open shared content. The independent vertical domain service process of the second application launched by the third application and the independent vertical domain service process of the second application launched by the first application are the same independent vertical domain service process. The vertical domain service provided to the first application or the third application when the independent vertical domain service process is run based on the second application is related to the user's operation.

[0027] For example, when the user's operation in the user interface of the first application is to open the first shared content, the vertical service provided to the first application when the second application runs an independent process of the vertical service is to open the vertical service. When the user's operation in the user interface of the third application is also to open the second shared content, the vertical service provided to the third application when the second application runs an independent process of the vertical service is also to open the vertical service.

[0028] For another example, if a user operation in the user interface of a first application is to share first shared content, the vertical service provided to the first application when the second application runs an independent vertical service process is to share the vertical service. If a user operation in the user interface of a third application is to open second shared content, the vertical service provided to the third application when the second application runs an independent vertical service process is to open the vertical service. In this case, although both the first application and the third application have launched the independent vertical service process of the second application, the vertical services provided by the second applications are different, and the interface displayed by the vertical service is also determined based on the shared content in the first application or the third application.

[0029] In a possible implementation of the first aspect, when at least one of the first application and the third application is running in the foreground, the vertical domain service independent process of the second application is running in the foreground.

[0030] It should be noted that when the first application is running in the foreground, the first interface is displayed in the foreground; when the third application is running in the foreground, the first interface is displayed in the foreground; or, when the first application is running in the background, the first interface runs in the background; or, when the third application is running in the background, the first interface runs in the background.

[0031] In a possible implementation of the first aspect, when the first application and the third application are running in the background, the vertical domain service independent process of the second application is running in the background.

[0032] In one possible implementation of the first aspect or the second aspect, the first interface of the vertical domain service of the second application is displayed using at least one of full screen, floating window, or control embedding. In addition, the vertical domain service can also display the interface in a full modal or semi-modal manner.

[0033] On the second aspect, the present application provides another cross-application interface display method. The method provided in the second aspect can be executed by an electronic device, or by a module applied in the electronic device (such as a processor, chip, or chip system, etc.), or by a logical node, logical module or software that can realize all or part of the functions of the electronic device. This application does not limit this.

[0034] Specifically, the method includes: displaying a user interface of a first application, which user interface includes first shared content of a second application; receiving a first operation of a user on the first shared content; in response to the first operation, determining at least one target application, and registering a configuration file for the first operation in at least one target application; displaying at least one target application to the user on the display interface of the first application; receiving a third operation of the user on at least one target application, the third operation being used to select a fourth application in at least one target application; in response to the third operation, running an independent process of a vertical domain service of the fourth application, and displaying a first interface of the vertical domain service of the fourth application; when running the main process of the second application, displaying a second interface of the main process of the fourth application, and the independent process of the vertical domain service is different from the main process.

[0035] The method provided by the second aspect is that when the electronic device receives the first operation of the user to share content of the second application in the user interface of the first application, the electronic device can determine multiple target applications corresponding to the first operation, and the electronic device can display the application selection boxes of the multiple target applications to the user for the user to select. Finally, based on the user's own needs, the electronic device runs the fourth application's vertical domain service independent process in the first application, and displays the first interface provided by the fourth application's vertical domain service. The fourth application does not need to pull up the main process to display the first interface. This method allows the user to quickly use the services provided by the fourth application (for example, sharing services, etc.) in the first application without starting the fourth application's main process, thereby avoiding the problems of long interaction paths, cumbersome operations, and waste of electronic device power consumption caused by starting the fourth application's main process, thereby improving the user experience.

[0036] For example, when the first operation is a sharing operation, multiple applications that support sharing operations are displayed to the user, such as application A, application B, and application C. The user can select application C for sharing based on his or her own needs, then the first interface displayed in the first interface is the first interface corresponding to application C.

[0037] In a third aspect, a communication device is provided, which includes a unit for executing each step in the above first aspect or any possible implementation of the first aspect, or a unit for executing each step in the above second aspect or any possible implementation of the second aspect.

[0038] In a fourth aspect, an electronic device is provided, which includes a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program from the memory, so that the electronic device executes the method in the above first aspect or any possible implementation of the first aspect, or is used to execute the above second aspect or any possible implementation of the second aspect.

[0039] In a fifth aspect, a computer program product is provided, which includes a computer program. When the computer program is executed by a processor, it is used to execute the method in the above first aspect or any possible implementation of the first aspect, or to execute the above second aspect or any possible implementation of the second aspect.

[0040] In the sixth aspect, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed, it is used to execute the method in the above first aspect or any possible implementation of the first aspect, or to execute the above second aspect or any possible implementation of the second aspect.

[0041] In the seventh aspect, a chip is provided, which includes: a processor for calling and running a computer program from a memory, so that a communication device equipped with the chip executes a method for executing the above first aspect or any possible implementation of the first aspect, or for executing the above second aspect or any possible implementation of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] FIG1 is a schematic diagram showing a related art method of previewing content shared by application B in application A;

[0043] FIG2 shows a schematic structural diagram of an electronic device 100;

[0044] FIG3 shows a schematic diagram of the software structure of the electronic device 100 according to an embodiment of the present application;

[0045] FIG4 shows a schematic diagram of a cross-application interface display provided by an embodiment of the present application;

[0046] FIG5 shows a schematic diagram of the vertical domain service startup process provided by an embodiment of the present application;

[0047] FIG6 shows another cross-application interface display diagram provided by an embodiment of the present application;

[0048] FIG7 shows another cross-application interface display diagram provided by an embodiment of the present application;

[0049] FIG8 shows a schematic diagram of the voice taxi service process provided by an embodiment of the present application;

[0050] FIG9 shows another cross-application interface display diagram provided in an embodiment of the present application;

[0051] FIG10 is a schematic diagram showing a multi-window instance corresponding to a vertical domain service template provided in an embodiment of the present application;

[0052] FIG11 is a schematic flowchart of a cross-application interface display method 1100 provided in an embodiment of the present application;

[0053] FIG12 shows a schematic flowchart of another cross-application interface display method 1200 provided in an embodiment of the present application.

[0054] FIG13 shows a schematic structural diagram of an electronic device provided by the present application. DETAILED DESCRIPTION

[0055] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

[0056] The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to be limiting of the present application. As used in the specification and appended claims of this application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the embodiments of the present application, "one or more" refers to one or more (including two); "and / or" describes the association relationship of associated objects, indicating that three relationships may exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship.

[0057] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0058] The "multiple" involved in the embodiments of the present application means greater than or equal to two. It should be noted that in the description of the embodiments of the present application, the words "first" and "second" are only used for the purpose of distinguishing the description and cannot be understood as indicating or implying relative importance or order.

[0059] In some examples, when a user receives content shared by other users in application B in application (app) (hereinafter referred to as application) A currently being used, and the user wants to preview the shared content from application B, the electronic device will jump to the interface of application A and guide the user to choose to open the shared content from application B from the browser for preview, based on the user's operation.

[0060] For example, FIG1 shows a schematic diagram of a related art preview of content shared by application B in application A. As shown in FIG1(a), the display interface is a chat interface 110 of application A (for example, application A can be a Changlian application). When a user receives a message from another user in application B (for example, application B can be a blog), When the user clicks on the shared content 120 of application B, the user can click on the shared content 120 of application B to preview the related content. When the user clicks on the shared content of application B, the display interface jumps to the interface shown in Figure 1 (b). As can be seen from the interface shown in Figure 1 (b), the user can see the partial content of application B on application A. If the user wants to browse all the content shared from application B and the comments related to the content, the user can click "Open APP" to browse more content. After the user clicks "Open APP", the display interface jumps to the interface shown in Figure 1 (c). As can be seen from the interface shown in Figure 1 (c), the user cannot open the APP directly, but can only click on the menu bar in the upper right corner. The menu bar in the upper right corner includes the option to open from the browser, as shown in Figure 1 (d), the menu bar also includes options such as forwarding and favorites. When the user clicks to open in the browser, application A can jump in the browser and finally preview all the content shared from application B in the browser.

[0061] It can be seen that when a user wants to open the content shared from application B in application A and browse all the content, it needs to be done through the browser after multiple jumps. The operation is cumbersome and the interaction path is long. The user cannot browse the shared content directly in one step, which reduces the user experience and increases the power consumption of the electronic device to a certain extent.

[0062] In another related technology example, some large applications utilize a whitelist mechanism. When a user requests to open a specific application, the target application is not opened, but instead redirected to a whitelisted application. These whitelisted applications require the application developer to develop a corresponding mini-program. For example, let's say the large application is Application A, and Application B is included in Application A's whitelist. To enable users to open Application B within Application A, the developer needs to develop a corresponding mini-program. When Application A receives content shared by Application B, it needs to run the corresponding mini-program to open the details of the shared content. This approach, which requires the development of additional mini-programs, increases developer workload and maintenance costs. Even if Application A includes a mini-program corresponding to Application B, it may still lead users to download and install Application B, impacting the user experience. It should be understood that large applications can be considered applications with good reputation and influence, that is, applications with high rankings. Alternatively, applications larger than 50MB, 60MB, or 100MB in size may be used.

[0063] In combination with the above content, the services provided by application B (for example, preview, sharing, editing, etc.) cannot be directly used on application A. In view of this, the following embodiments of this application provide a cross-application interface display method, which includes: an electronic device receives a first operation of a user to share content with a second application in a user interface of a first application, and the first application is the application currently being used by the user; in response to the user's first operation, a first interface is displayed in the first application, and the first interface is the same as the interface displayed when responding to the first operation when running a third application. The third application and the second application can be the same application or different applications. The method provided by this application can enable users to quickly use the services provided by the second application in the first application, thereby avoiding the problem of long interaction paths caused by multiple jumps between applications, which increases the power consumption of electronic devices, and improves the user experience on the basis of reducing application development costs.

[0064] In one possible application scenario, when a user wants to quickly preview the content shared by application B without launching application B in application A, the cross-application interface display method provided in this application can be used.

[0065] In another possible application scenario, when a user wants to quickly share the content shared by application B to application C without launching application B in application A, the cross-application interface display method provided in this application can be used.

[0066] In another possible application scenario, when a user wants to quickly use a taxi service without launching a taxi application on the desktop, the cross-application interface display method provided in this application can be used.

[0067] The following describes electronic devices to which the cross-application interface display method provided in this application is applicable.

[0068] The electronic devices involved in the embodiments of the present application may include, but are not limited to, at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, or a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the electronic device.

[0069] As shown in FIG2 , FIG2 shows a schematic structural diagram of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) connector 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor 180, a button 190, an indicator 191, a subscriber identification module (SIM) card interface 192, a positioning device 193, and a display screen 194.

[0070] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than those shown in FIG1 , or may combine or separate certain components, or may have different component arrangements. The components shown in FIG1 may be implemented in hardware, software, or a combination of software and hardware.

[0071] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a 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.

[0072] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 may be a cache memory. This memory can store instructions or data that have been used or are frequently used by processor 110. When processor 110 needs to use the instruction or data, it can directly access it from this memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0073] Exemplarily, the memory is used to execute the application code of the solution of the present application, and the execution is controlled by the processor 110. The processor 110 is used to execute the application code stored in the memory to control the electronic device 100 to implement the cross-application interface display method provided by the embodiment of the present application.

[0074] Electronic device 100 can implement display functions using a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0075] The sensor 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., which is used to convert various signals from the outside world into electrical signals or other required forms of information output.

[0076] The touch sensor is also called a "touch panel." The touch sensor can be disposed on the display screen 194. The touch sensor and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to a processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor can also be disposed on the surface of the electronic device 100, at a location different from that of the display screen 194.

[0077] Illustratively, in an embodiment of the present application, the touch sensor may detect a drag operation of the user and transmit the detected drag operation to the processor to determine the drag event type.

[0078] Display screen 194 is used to display data such as images, text, and videos. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or more display screens 194.

[0079] Illustratively, in an embodiment of the present application, the display screen 194 is used to display the display interface of application B on application A based on the cross-system interface display method provided by the present application.

[0080] The electronic device 100 may also adopt other architectures. The embodiment of the present invention takes the Harmony system as an example to exemplarily illustrate the software architecture of the electronic device 100. FIG3 is a schematic diagram of the software structure of the electronic device 100 in the embodiment of the present application.

[0081] In some implementations, the Harmony system comprises four layers. The layered architecture divides the software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. From top to bottom, these layers are the application layer, the application framework layer, the Harmony graphics stack, and the kernel layer. The Harmony graphics stack comprises the interface layer, the framework layer, and the engine layer.

[0082] The application layer includes system applications and third-party applications. Applications on electronic devices can be system applications (such as applications installed in electronic devices when the operating system is installed before the electronic device leaves the factory) or third-party applications (such as applications downloaded and installed by users through the application store), which is not limited in the embodiments of this application. For example, applications may include: camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, game, shopping, travel, instant messaging (such as short message), Xiaoyi suggestion and other system applications (not shown in Figure 3), and applications may also include In the Harmony system, applications are built based on the stage model or the fa model.

[0083] The application framework layer provides Harmony system applications with a user program framework and meta-capability framework in multiple languages, such as Java, C, C++, JavaScript, and TS. It also provides a multi-language framework application programming interface (API) for various software and hardware services. For example, the application framework layer can be the ArkUI application framework.

[0084] The interface layer of the Harmony graphics stack provides native graphics API capabilities, including WebGL, Native Drawing drawing capabilities, and OpenGL instruction-level drawing support.

[0085] The framework layer of the Harmony graphics stack is divided into five modules: rendering service, drawing, animation, effects, and display and memory management. Among them, the rendering service module provides the drawing capabilities of the UI framework. Its core responsibility is to convert the control description of ArkUI into drawing tree information and perform optimal path rendering according to the corresponding rendering strategy. At the same time, it is responsible for the core underlying mechanism of multi-window smoothness and UI sharing in spatial state. The drawing module provides a standardized interface within the image subsystem, mainly completing basic functions such as 2D rendering, 3D rendering, and rendering engine management. The animation module provides related capabilities of the animation engine. The effect module mainly completes the ability to process effects such as image effects and rendering effects, including: serial and parallel processing of multiple effects, adding rendering effects and control interaction effects during layout, and other related capabilities. The display and memory management module is the main module that decouples the graphics stack from the hardware and mainly defines the display and memory management capabilities of Harmony.

[0086] Exemplarily, in an embodiment of the present application, the drawing module of the framework layer is used to draw the first interface according to the vertical domain service template provided by the second application, and the rendering tree management in the rendering service module of the framework layer is used to load the drawn first interface onto the graphic node tree of the first application so that the first interface can be displayed in the first application.

[0087] The engine layer of the Harmony graphics stack consists of two modules: the 2D graphics library and the 3D graphics engine. The 2D graphics library provides the underlying API for 2D graphics drawing, supporting the underlying capabilities of graphics and text drawing.

[0088] Kernel layer: The Harmony system uses a multi-kernel design, optionally including the Linux kernel, Hongmeng microkernel, and LiteOS. This design allows devices with different capabilities to select the appropriate system kernel. The kernel layer also includes the Kernel Abstraction Layer, which provides basic kernel capabilities for other Harmony layers, such as process management, thread management, memory management, file system management, network management, and peripheral management.

[0089] It should be noted that Figure 3 only takes the layered architecture Harmony system as an example to introduce the interface display process in a cross-application interface display scenario. This application does not limit the specific architecture of the electronic device software system. For the specific introduction of software systems with other architectures, reference can be made to conventional technologies. For example, the software system may also include but is not limited to Symbian etc. operating systems, and this application is not limited.

[0090] For ease of understanding, the following embodiments of this application will take an electronic device having the structure shown in Figures 2 and 3 as an example, and combine the accompanying drawings and application scenarios to specifically explain the cross-application interface display method provided in the embodiments of this application.

[0091] The following uses a mobile phone as an example of an electronic device to specifically describe the cross-application display interface provided by this application.

[0092] FIG4 shows a schematic diagram of an example of a cross-application interface display provided by an embodiment of the present application, wherein FIG4 (a) shows a display interface 410 of application A (for example, application A can be a Changlian application). As can be seen from FIG4 (a), application A receives a message from application B (for example, application B can be a blog). Application A generates a link related to the shared content, and sends the link to Application B. Application B can also generate a QR code related to the shared content and send the QR code to Application A. Of course, the shared content of Application B can also be shared in other forms. In the embodiment of the present application, the generation of relevant links is used as an example. In response to the user's preview operation on the shared content of Application B (the preview operation can also be understood as an open operation), the display interface switches from the interface shown in Figure 4 (a) to the interface shown in Figure 4 (b), that is, in response to the user's preview operation on the shared content of Application B, the electronic device can directly display the preview interface 430 of the shared content of Application B in Application A, thereby avoiding multiple jumps between applications and improving the user experience.

[0093] 5 , an exemplary description will be given below of how the electronic device switches from the interface shown in FIG. 4 (a) to the interface shown in FIG. 4 (b).

[0094] Figure 5 shows a schematic diagram of the vertical domain service startup process provided by an embodiment of the present application. As shown in Figure 5, in response to the user's preview operation of the shared content of application B on the display interface of application A (the preview operation can also be understood as an open operation), application A triggers an interface call, and the system of the electronic device creates a vertical domain service control (440 as shown in Figure (b) in Figure 4). It should be understood that the vertical domain service control is used to display the preview display interface. After application A completes the creation of the vertical domain service control 440, it sends a first request to the system of the electronic device, which is used to request a preview of the vertical domain service.

[0095] It should be noted that the systems of the electronic devices mentioned in the embodiments of the present application may include but are not limited to Harmony, Symbian, And other operating systems.

[0096] For example, functions related to vertical domain services can be started through the interface created by the system service of the electronic device. For example, a vertical domain service control can be created using the interface of the system service of the electronic device, or an application initiates a first request to the interface of the system service of the electronic device, or a jump between applications can be achieved through the interface of the system service of the electronic device.

[0097] It should be understood that vertical services correspond to user operations. When the user operation is to preview the shared content of application B, the vertical service corresponds to the preview vertical service. When the user operation is to edit the shared content of application B, the vertical service corresponds to the edit vertical service. When the user operation is to share the shared content of application B, the vertical service corresponds to the share vertical service. Of course, the user operation can also be other operations, then the vertical service corresponds to other vertical services, such as a vertical service that combines editing and sharing, or corresponds to a save vertical service. Examples are not given here one by one.

[0098] In one possible implementation, when application A sends a first request to the system of the electronic device, the first request includes a graphical node tree identifier of the vertical domain service control. It should be understood that application A corresponds to a graphical node tree, which includes graphical node tree identifiers of multiple controls on the display interface of application A, that is, the graphical node tree identifier includes the identifier of the vertical domain service control, and the identifier of the vertical domain service control is used to identify the mounting location of the display interface of application B on the interface of application A.

[0099] When the system of the electronic device receives the first request, it verifies the security of the first request. After the verification is passed, it matches at least one target application according to the first request, and the target application includes the vertical domain service corresponding to the first request. In the example shown in Figure 4, the user wants to preview the shared content 420 of application B, so the vertical domain service is the preview vertical domain service provided by application B. It should be understood that when the system of the electronic device matches the target application according to the first request, it matches based on the information of the application and the type of vertical domain service. Register the preview function for the shared content of application B in the configuration file of application B.

[0100] In some examples, when a user wants to share content from application B, the electronic device's system matches it based on the type of vertical service. A vertical service sharing service may correspond to multiple target applications. For example, a vertical service sharing service may correspond to application C, application D, and application E. It should be noted that the sharing function must be registered in the configuration files of application C, application D, and application E.

[0101] In the example shown in Figure 4, after the electronic device's system matches the target application, it creates and launches an independent vertical domain service process based on the matching result. This independent vertical domain service process is used to load the preview display interface of application B. In related technologies, the preview display interface of application B requires the launch of the main process of application B. The independent vertical domain service process in the embodiment of the present application can load the necessary independent resources and does not rely on the main application process and its resources. Compared with the method of launching the main process, this method of creating an independent vertical domain service process by the electronic device's system consumes less power.

[0102] The electronic device's system starts an independent process for application B's vertical domain service, and then starts a preview vertical domain service for application B. After application B's preview service starts, the electronic device's system renders, loads, and constructs a graphic node tree based on the configured preview display interface. Finally, it mounts the rendered display interface on the graphic node tree corresponding to application A's vertical domain service control. Finally, the preview display interface of application B is displayed in application A.

[0103] In some examples, the preview vertical domain service of application B can be developed by developers according to a preview vertical domain service template during the application development phase. That is, the developer can set the preview display interface to be loaded based on the preview vertical domain service template.

[0104] In the example of Figure 4, based on the user's preview operation, the electronic device can accurately match the target application. If the user's operation corresponds to a sharing operation, the electronic device will perform a fuzzy match on the target application and finally determine the target application based on the user's operation. The following is a detailed description of another cross-application interface display provided by an embodiment of the present application, taking the vertical domain service startup process of Figure 5 and the user's sharing operation shown in Figure 6 as examples.

[0105] Figure 6 shows another cross-application interface display diagram provided by an embodiment of the present application. Figure (a) in Figure 6 shows a display interface 610 of application A. It can be seen from Figure (a) in Figure 6 that after receiving shared content 620 from application B in application A, in response to the user's sharing operation on the shared content of application B, the electronic device creates a vertical domain service control in application A. It should be understood that the vertical domain service control is used to display the sharing display interface. When the vertical domain service control of application A is created, a first request message is sent to the system of the electronic device, and the first request message is used to request the sharing of the vertical domain service.

[0106] When the electronic device's system receives the first request, it verifies the security of the first request and matches the target application based on the first request. In the example shown in Figure 6, the user wants to share content from application B. Among the multiple applications on the electronic device, at least one application supports the sharing function. In this case, the sharing vertical domain service corresponds to multiple target applications.

[0107] In one possible implementation, the electronic device's system can scan application configuration files to detect which configuration files have registered the sharing function. The electronic device then displays the applications registered for the sharing function as target applications on the interface. That is, the target applications for the sharing operation include multiple applications registered for the sharing function.

[0108] In some examples, when a shared vertical domain service corresponds to multiple target applications, the electronic device can pop up application selection boxes corresponding to the multiple target applications and display a list of applications that support the shared vertical domain service for the user to select. After the user selects the target application he wants to use based on the multiple application selection boxes displayed, the electronic device's system creates and pulls up an independent process of the vertical domain service corresponding to the target application, and then starts the shared vertical domain service of the target application. When the shared vertical domain service of the target application is started, the electronic device's system renders, loads, and constructs a graphic node tree based on the set sharing display interface, and finally mounts the drawn display interface on the graphic node tree corresponding to the vertical domain service control of application A. Finally, the shared display interface of the target application can be displayed in application A.

[0109] In some examples, the target application's shared vertical domain service can be developed by developers during the application development phase based on a shared vertical domain template. That is, the developer can set the sharing display interface to be loaded based on the shared vertical domain service template.

[0110] For example, as shown in FIG6 (b), assuming that application A, application B, application C, application D, application E, and application F have all registered the sharing function, the electronic device will pop up an application selection box, i.e., a sharing service list 630, and display these applications in the sharing service list 630, and the user can select them. For example, the user can select application C for sharing operation, and the electronic device system will create and pull up an independent process of the vertical domain service of application C, and then start the sharing vertical domain service of application C. When the sharing vertical domain service of application C is started, the electronic device system renders, loads, and constructs the number of graphic nodes according to the set sharing display interface of application C, and finally mounts the drawn sharing display interface of application C on the graphic node tree corresponding to the vertical domain service control of application A. That is, when the user clicks the control of application C in the interface shown in FIG6 (b), the display interface of the electronic device switches to the interface shown in FIG6 (c), that is, in response to the user's sharing operation on the shared content of application B, the electronic device can directly display the sharing display interface 640 based on the sharing of application C in application A.

[0111] It should be understood that the sharing vertical domain service of application C can be developed by the developer according to the sharing vertical domain service template of application C during the development stage of application C. That is, the developer sets the sharing display interface to be loaded based on the sharing vertical domain service template of application C.

[0112] It should be noted that the interface switched from the interface shown in Figure 6 (b) to the interface shown in Figure 6 (c) is displayed in the vertical domain service control created in the interface of application A, without the need for a jump effect across applications, thereby reducing the energy consumption of electronic devices. When the user completes the sharing operation, click the close control on the interface as shown in Figure 6 (c), and the vertical domain service exits on the interface of application A. At the same time, application A destroys the corresponding vertical domain service control and returns to the main interface of application A, as shown in the interface in Figure 6 (d). This method also does not require a jump effect across applications, reducing the energy consumption of electronic devices.

[0113] The examples in Figures 4 and 6 above are specifically introduced using a vertical domain service with a single function provided by an electronic device as an example. In the embodiment of the present application, the electronic device can also create multiple vertical domain services related to the application based on the application's request to enhance the user experience. The following takes the vertical domain service startup process in Figure 5 and the cross-application interface display shown in Figure 7 as examples to specifically describe another cross-application interface display method provided in the embodiment of the present application.

[0114] Figure 7 shows another example of a cross-application interface display diagram provided by an embodiment of the present application, as shown in Figure 7 (a) shows the display interface 710 of application A, as shown in Figure 7 (a), the content 720 shared from application B is received in application A, and in response to the user's preview operation on the shared content of application B, the system of the electronic device creates a vertical domain service control in application A. It should be understood that the vertical domain service control is used to display the display interface of application B. When the vertical domain service control in application A is created, application A sends a first request message to the system of the electronic device, and the first request message is used to request a vertical domain service. In the example shown in Figure 7, the vertical domain service is not limited to the preview vertical domain service, and the vertical domain service can be multiple vertical domain services related to application B. For example, if application B is a document-type application, then the vertical domain service may include preview, editing, sharing, etc. related to the document. The embodiment of the present application does not limit the specific category of the vertical domain service.

[0115] When the electronic device's system receives the first request, it verifies the security of the first request and, if the verification passes, matches the target application based on the first request. For example, the target application may be a document-related application. Based on the target application selected by the user, the electronic device creates and starts an independent vertical domain service process. The independent vertical domain service process is used to load all vertical domain service templates for the application.

[0116] The electronic device's system creates an independent vertical service process and launches multiple vertical services of Application B. The electronic device's system renders, loads, and constructs a graphical node tree based on the configured interface. Ultimately, based on user input, the rendered display interface is mounted on the graphical node tree corresponding to the vertical service control of Application A. When the electronic device's system launches Application B's vertical service within Application A, the display interface corresponding to Application B's vertical service appears within Application A.

[0117] In some examples, application B may have multiple vertical services during the development phase of the application. Developers develop multiple vertical services for application B based on multiple vertical service templates, that is, developers can set the interfaces that need to be loaded based on multiple vertical service templates.

[0118] It should be understood that when the user clicks on the preview operation, the system of the electronic device will mount the drawn preview interface of application B on the graphic node tree corresponding to the vertical domain service control of application A, and finally display it. For example, as shown in Figure (a) in Figure 7, when the user clicks on the link of the content 720 shared by application B, the electronic device responds to the user's preview operation (the preview operation can also be understood as an open operation), and the display interface of the electronic device switches from the interface shown in Figure (a) in Figure 7 to the interface shown in Figure (b) in Figure 7, that is, the preview interface 730 of application B is displayed in application A. It should be understood that the preview interface of application B is displayed in the form of a vertical domain service template. Therefore, when switching from the interface shown in Figure (a) in Figure 7 to the interface shown in Figure (b) in Figure 7, there is no need to jump between applications. Compared with the prior art, multiple jumps between applications are avoided, thereby reducing the power consumption of the electronic device and improving the user experience.

[0119] As can be seen from Figure 7 (b), the preview display interface 730 includes an edit control 740 and a return control 750. When the user completes the preview of the document content and does not need to edit, he can click the return control 750 to exit the preview vertical domain service and return to the application A interface 710. If the user still needs to edit the document after previewing the document content, the user can directly click the edit control 740. The electronic device's system will start and draw the editing interface of application B, and mount the drawn editing interface on the graphical node tree corresponding to the vertical domain service control of application A, and finally display the editing interface. Referring to Figure 7, after the user clicks the edit control 740 in Figure 7 (b), the display interface switches to the interface shown in Figure 7 (c). That is, switching from the preview vertical domain service to the edit vertical domain service, the user completes the editing in the interface shown in Figure 7 (c), clicks the completion control 760, exits the edit vertical domain service, and destroys the corresponding vertical domain service control, as shown in Figure 7 (d), and returns to the display interface 710 of application A.

[0120] It can be seen that based on the example of Figure 7, the electronic device can provide multiple vertical services based on the user's request, allowing the user to use the preview vertical service to browse the document content without jumping out of application A. If further editing is required, switch to the editing vertical service in the preview vertical service, thereby improving the user experience and office efficiency.

[0121] In the examples in Figures 4, 6, and 7 above, the method provided in the embodiments of the present application can be applied to scenarios where application A is a system application or a third-party application; correspondingly, application B can also be a system application or a third-party application. For example, the user experience can be improved by combining system applications with vertical domain service templates. For example, the system application can be Xiaoyi Suggestions, and the vertical domain service template can be a taxi-hailing vertical domain service template.

[0122] Below, in conjunction with Figures 8 and 9, another example of a cross-application interface display method provided by an embodiment of the present application is illustrated. Figure 8 shows a schematic diagram of the voice taxi service process provided by an embodiment of the present application, and Figure 9 shows a schematic diagram of another cross-application interface display provided by an embodiment of the present application. As shown in Figure 8, after the user issues a voice command of "Xiaoyi Xiaoyi, I want to take a taxi", the system of the electronic device matches the target application based on the taxi voice command. As shown in Figure 9 (a), it is a desktop interface 910 of the electronic device. When the user issues a voice command of "Xiaoyi Xiaoyi, I want to take a taxi", the "Xiaoyi Suggestion" application of the electronic device creates a vertical domain service control. The vertical domain service control is used to display the taxi display interface. After the vertical domain service control is created, the system of the electronic device matches multiple target applications. As shown in Figure 9 (b), the taxi service list 920 includes target applications including application A, application B and application C. It should be understood that application A, application B and application C are all registered for taxi services.

[0123] Because the vertical domain service corresponds to multiple target applications, the electronic device pops up application selection boxes corresponding to the multiple target applications and displays a list of applications that support the vertical domain service for the user to select. After the user selects the target application they want to use based on the multiple application selection boxes displayed, the electronic device's system creates and launches an independent vertical domain service process for the target application, and then starts the vertical domain service of the target application. The electronic device's system renders, loads, and constructs a graphic node tree based on the set taxi display interface, and finally mounts the constructed display interface on the graphic node tree corresponding to the vertical domain service control. When the taxi vertical domain service of the target application is started based on the electronic device's system, the taxi display interface of the target application can be displayed on the electronic device.

[0124] In some examples, the target application's ride-hailing vertical service can be developed by a developer during the application's development phase based on a ride-hailing vertical service template. That is, the developer can set the ride-hailing display interface to be loaded based on the ride-hailing vertical service template.

[0125] For example, as shown in Figure 9 (b), after the user selects the taxi application A, the system of the electronic device creates an independent process of the vertical domain service of application A, and then starts the taxi vertical domain service of application A. When the taxi vertical domain service of application A is started, the system of the electronic device draws the taxi display interface according to the taxi display interface set by application A, and then mounts the drawn taxi display interface under the graphic node tree of the Xiaoyi suggestion application for display. Finally, the taxi display interface of application A is displayed on the electronic device. That is, after the user selects the taxi application A, the display interface switches from the interface shown in Figure 9 (b) to the interface shown in Figure 9 (c), and the electronic device can directly display the taxi display interface 930 of application A in Xiaoyi suggestion. The user can enter the destination in the interface shown in Figure 9 (c), and application A completes the taxi order operation in the interface shown in Figure 9 (c). The user can click the return control 940, and the display interface switches to the interface shown in Figure 9 (d). That is, users can exit or minimize the taxi service, return to the main interface of the electronic device or operate other applications without having to keep the taxi service open. When the vehicle arrives, an arrival notification will be displayed on the electronic device.

[0126] In some examples, the taxi-hailing vertical service of application A can be developed by developers based on a taxi-hailing vertical service template during the application development phase. That is, the developer can set the taxi-hailing display interface to be loaded based on the taxi-hailing vertical service template.

[0127] It can be seen that in the example shown in Figure 9, the user combines the system application (Xiaoyi's suggestion) with the taxi vertical service. The user can quickly experience the taxi service without launching the main process of the taxi application, thereby reducing the power consumption of the electronic device and not affecting the user's current operation on the display interface, thereby improving the user experience.

[0128] In the examples of Figures 4, 6, 7 and 9 above, the service user is an application as an example for illustration. In an embodiment of the present application, the user of the same service can also be multiple applications. When the service user is multiple applications, the multiple applications respectively send a first request to the system of the electronic device to request the vertical domain service. The system of the electronic device creates multiple window instances in the vertical domain service template based on the multiple first requests, and the vertical domain service provider sets the display interface according to the multiple window instances, thereby ensuring that each vertical domain service control corresponds to a window, each displaying an interface, and does not affect the interaction with each other. It should be understood that the service user is the application currently being used by the user (for example, application A in the example of Figure 4), and the vertical domain service provider is the application that provides the service (for example, application B in the example of Figure 4).

[0129] Exemplarily, Figure 10 shows a schematic diagram of a multi-window instance corresponding to the vertical domain service template provided in an embodiment of the present application. As shown in Figure 10, assuming that application A and application B request a preview of the vertical domain service from the system of the electronic device, the system of the electronic device creates an independent process for the vertical domain service, and then starts the preview vertical domain service of application C. Application C sets the interface displayed in application A based on the requests of application A and application B, and the display interface is displayed in window A, and sets the interface displayed in application B, and the display interface is displayed in window B. Finally, the system of the electronic device renders and loads window A and window B set by application C respectively, and finally mounts the interface corresponding to the rendered window A in the vertical domain service control of application A for displaying the interface in application A, and mounts the interface corresponding to the rendered window B in the vertical domain service control of application B for displaying the interface in application B.

[0130] In some embodiments, when the service user is a plurality of applications, the state of the independent process of the vertical domain service is switched according to the process state of the plurality of applications. When the plurality of applications are in the background state, the state of the independent process of the vertical domain service is switched to the background state. For example, referring to Figure 10, when both application A and application B are running in the background, the independent process of the vertical domain service of application C is running in the background. When at least one application among the plurality of applications is in the foreground state, although the other applications are in the background state, the state of the independent process of the vertical domain service is still in the foreground state. For example, when application A or application B is displayed in the foreground, the independent process of the vertical domain service of application C is running in the background.

[0131] The following will describe in detail an example of a cross-application interface display method provided by an embodiment of the present application in combination with the above interface display schematic diagram.

[0132] Figure 11 shows a schematic flow chart of a cross-application interface display method 1100 provided in an embodiment of the present application. As shown in Figure 11, the method 1100 shown in Figure 11 may include steps S1110 to S1130. The steps in the method 1100 are described in detail below in conjunction with Figure 11.

[0133] It should be understood that in the embodiments of the present application, the electronic device is used as an example to illustrate the method 1100. As an example and not a limitation, the execution body of the method 1100 may also be a chip used in the electronic device.

[0134] S1110. The electronic device displays a user interface of the first application, where the user interface includes first shared content of the second application.

[0135] It should be noted that the application involved in the embodiments of the present application refers to application software; the first application or the second application can be a system application or a third-party application running on the terminal; for example, the first application can be an application software that comes with the system (for example, Xiaoyi Suggestions, etc.), or it can be an application software downloaded and installed by the user (social application, shopping application or taxi application, etc.), and this application does not limit this.

[0136] The user interface refers to the interface for interaction between the first application and the user, and the user can perform a series of operations on the user interface. Accordingly, the electronic device receives the user's first operation instruction through the user interface, determines the operation intention corresponding to the first operation based on the first operation, and finally responds to the user operation based on the operation intention.

[0137] It should also be noted that the applications referred to in this application can be World Wide Web (Web) applications or native applications. Web applications refer to web applications that run in a browser. Native applications refer to applications that can run directly on the current operating system. Web applications include, but are not limited to, ticket purchasing applications, message boards, and forums that run in a browser; native applications include, but are not limited to, music applications, shopping applications, graphic editing applications, and sports applications.

[0138] In an embodiment of the present application, the first shared content of the second application included in the user interface of the first application can be a link related to the shared content generated in the second application, which is sent to the first application; the first shared content of the second application can also be a QR code generated in the second application, which is sent to the first application. Of course, the first shared content of the second application can also be in other forms, which are not limited in this embodiment of the present application.

[0139] For example, as shown in FIG4 (a), the first application and the second application are both social applications (third-party applications) currently being used by the user, and the first shared content of the second application is sent in the form of a link.

[0140] For another example, as shown in FIG6 (a), the first application and the second application are both social applications currently in use, and the shared content of the second application is sent in the form of a link.

[0141] For another example, as shown in Figure 7 (a), the first application is a social application (third-party application) that the user is currently using, the second application is an office application (third-party application), and the first shared content of the second application is sent in the form of a link.

[0142] For another example, as shown in Figure 9 (a), the first application is a system-provided application (Xiaoyi's suggestion), and the second application is a taxi-hailing application.

[0143] S1120: The electronic device receives a first operation of a user on first shared content.

[0144] In some examples, the user's first operation on the first shared content of the second application in the user interface of the first application can be understood as: when the user is currently using the first application, the first shared content from the second application is received, and the user performs a preview operation, a share operation, or an edit operation on the first shared content in the user interface of the first application.

[0145] It should be noted that the first shared content of the second application may be a message sent by other users, or a message sent between the first application and the second application on the same electronic device currently used by the user.

[0146] For example, as shown in FIG. 4( a ) and FIG. 7( a ), the first operation based on the user is a preview operation (opening operation) of the user.

[0147] For another example, as shown in FIG6( a ), the first operation based on the user is a sharing operation of the user.

[0148] For another example, as shown in FIG9 (a), the first operation based on the user is a voice operation (“Xiaoyi Xiaoyi, I want to take a taxi”).

[0149] S1130. In response to the user's first operation, run the independent process of the vertical domain service of the second application, and display the first interface of the vertical domain service of the second application. When running the main process of the second application, display the second interface of the main process of the second application. The vertical domain service process is different from the main process.

[0150] After the electronic device receives the first operation of the user on the first shared content of the second application in the first application, in response to the first operation, the electronic device runs the vertical service process of the second application without starting the main process of the second application, and displays the first interface of the vertical service of the second application in the first application, thereby reducing the power consumption of the electronic device and improving the user experience.

[0151] In the embodiment of the present application, the first interface of the vertical domain service of the second application can be displayed using at least one of full screen, floating window, or control embedding. In addition, the vertical domain service can also display the interface in full modality or semi-modality. Alternatively, the first interface can be displayed in other ways, which are not limited in the embodiment of the present application.

[0152] For example, as shown in Figure 4 (a), after the electronic device responds to the user's preview operation on the first shared content of the second application in the first application, as shown in Figure 4 (b), the preview display interface of the second application is displayed on the first application. The preview display interface is the first interface. It should be noted that, assuming that the electronic device clicks the preview operation on the content when running the main process of the second application, the second interface of the main process of the second application is displayed. The display interface in the second application (second interface) and the display interface in the first application (first interface) can be the same or different.

[0153] For another example, as shown in Figure 7 (a), after the electronic device responds to the user's preview operation on the first shared content of the second application in the first application, as shown in Figure 7 (b), the preview display interface of the second application is displayed on the first application, and the preview display interface is the first interface. It should be noted that, assuming that the electronic device clicks the preview operation on the document when running the main process of the second application, the second interface of the main process of the second application is displayed. The display interface in the second application (second interface) and the display interface shown in Figure 7 (b) (first interface) can be the same or different.

[0154] For another example, as shown in Figure 9 (a), in response to a user's voice operation on a second application (a taxi-hailing application) in a first application (Xiaoyi's suggestion), the electronic device displays the taxi-hailing display interface of the second application on the first application, as shown in Figure 9 (c). This taxi-hailing display interface is the first interface. It should be noted that, assuming that the electronic device is running the main process of the second application and the user performs a taxi-hailing operation, the electronic device displays the taxi-hailing display interface of the main process of the second application. This taxi-hailing display interface (second interface) and the display interface shown in Figure 9 (c) can be the same or different.

[0155] In step S1130, in response to the user's first operation, the independent process of the vertical domain service of the second application is run, and the specific process of displaying the first interface of the vertical domain service of the second application can be referred to the description in Figures 4 to 9 above, which will not be repeated here.

[0156] The method provided in the embodiment of the present application is that when the electronic device receives the first operation of the user to share content of the second application in the user interface of the first application, the electronic device displays the first interface provided by the vertical domain service of the second application by running the independent process of the vertical domain service of the second application in the first application, and the second application does not need to pull up the main process to display the first interface. This method allows the user to quickly use the services provided by the second application (for example, preview, share, etc.) in the first application without starting the main process of the second application, thereby avoiding the problems of long interaction path, cumbersome operation, and waste of electronic device power consumption caused by starting the main process of the second application, thereby improving the user experience.

[0157] In some possible implementations, running the second application's vertical domain service independent process includes: creating a vertical domain service independent process, the vertical domain service independent process is used to run the second application's vertical domain service, the vertical domain service is used to represent: the display interface when the second application is run in response to the first operation; when the vertical domain service is started, drawing the first interface based on the vertical domain service; loading the first interface into the first application.

[0158] In this implementation, the electronic device creates an independent vertical domain service process for the second application based on the user's first operation. The independent vertical domain service process can load independent resources required by the application and does not rely on the second application main process and resources. Therefore, this method can make the power consumption of the electronic device lower. When the vertical domain service is started, the first interface is drawn based on the vertical domain service, and then the first interface is loaded into the first application to realize the interface set by the second application displayed in the first application. The process of displaying the first interface through this implementation method can refer to the description of Figures 4 to 9 above, which will not be repeated here.

[0159] For example, as shown in Figure 4, in response to the user's preview operation, the electronic device creates an independent process of the vertical domain service of the second application. The independent process of the vertical domain service is used to run the preview vertical domain service of the second application. When the preview vertical domain service is started, the electronic device draws the preview display interface (first interface) based on the set preview vertical domain service, and finally loads the preview display interface into the first application.

[0160] It should be noted that the preview vertical domain service of the first application can be developed by the developer based on the vertical domain service template during the application development phase. It can also be understood that the developer can set the preview display interface to be loaded based on the preview vertical domain service template.

[0161] In some possible implementations, before displaying the first interface of the vertical service of the second application, the method also includes: determining a vertical service control in the first application, the vertical service control being used to limit the display area of ​​the first interface, and the first interface being displayed in the vertical service control.

[0162] In this implementation, the electronic device creates a vertical service control in the first application, and displays the first interface in the vertical service control. The vertical service control can determine the display position or display area of ​​the first interface.

[0163] For example, as shown in Figure 4, the electronic device creates a vertical service control 440 in the first application, and finally displays the loaded preview display interface 430 in the vertical service control 440. Referring to Figure 4, it can be seen that the vertical service control 440 can determine the display position and display area of ​​the preview display interface 430.

[0164] In some possible implementations, the first application corresponds to a graphic node tree, the graphic node tree includes a graphic node tree identifier, the graphic node tree identifier includes an identifier of a vertical domain service control, and the first interface is loaded in the first application, including: mounting the node of the first interface on the graphic node tree of the first application based on the identifier of the vertical domain service control, and loading the first interface in the first application according to the graphic node tree of the node on which the first interface is mounted.

[0165] In this implementation, the mounting position of the first interface of the second application on the first application interface can be determined by using the identifier of the vertical domain service control on the graphic node tree.

[0166] In some possible implementations, the vertical domain service independent process can run the first vertical domain service and the second vertical domain service, the first vertical domain service includes a control corresponding to the second vertical domain service, and the first vertical domain service and the second vertical domain service are different.

[0167] It should be understood that the first vertical domain service and the second vertical domain service run in the same vertical domain service independent process.

[0168] In this implementation, the independent vertical domain service process can load multiple vertical domain services, and the first vertical domain service among the multiple vertical domain services includes controls corresponding to the second vertical domain service. Then, when the user is using the first vertical domain service, he can quickly switch to the second vertical domain service as needed, thereby improving the user experience.

[0169] For example, referring to Figure 7 (b), the first vertical domain service is a preview vertical domain service, and the second vertical domain service is an edit vertical domain service. The preview vertical domain service includes a control for editing the vertical domain service, such as the interface shown in Figure 7 (b). When the preview vertical domain service includes a control for editing the vertical domain service, the preview display interface includes an edit control. Then, when the user needs to edit, he directly clicks the edit button in the preview display interface, and the display interface of the electronic device switches to the interface shown in Figure 7 (c), thereby realizing rapid switching of vertical domain service templates within the application.

[0170] In some possible implementations, the method also includes: displaying a user interface of a third application, the user interface of the third application including the second shared content of the second application; receiving a second operation of the user on the second shared content of the second application; in response to the second operation on the second shared content, running an independent process of the vertical domain service of the second application, and displaying a third interface of the vertical domain service of the second application, the vertical domain service of the second application including a display window of the third application, and the display window of the third application is different from the display window of the first application.

[0171] It should be noted that the first operation and the second operation may be operations of the same type, for example, both may be operations of opening shared content.

[0172] In this implementation, when the first application and the second application both launch independent processes of the second application's vertical domain service, the electronic device creates multiple window instances in the vertical domain service provided by the second application, and sets the first interface according to the multiple window instances, thereby ensuring that each vertical domain service control corresponds to a window, each displaying an interface, and does not affect the interaction with each other.

[0173] It should be noted that the independent vertical domain service process of the second application launched by the third application and the independent vertical domain service process of the second application launched by the first application are the same independent vertical domain service process. The vertical domain service provided to the first application or the third application when the independent vertical domain service process is run based on the second application is related to the user's operation.

[0174] For example, as shown in Figure 10, the first application is application A, and the third application is application B. Application B includes the second shared content of the second application. After the electronic device receives the user's preview operation on the second shared content of the second application, the electronic device responds to the preview operation, runs the second application's independent vertical domain service process, and displays the interface of the preview vertical domain service of the second application. The preview vertical domain service includes the display window of the third application. When application A also pulls up the preview vertical domain service of the second application, the preview vertical domain service also includes the display window of the first application. In order to avoid confusion in display, the display window of the third application and the display window of the first application are different.

[0175] It should also be noted that application A launches the preview vertical domain service of the second application, and application B also launches the preview vertical domain service of the second application. The independent vertical domain service process corresponding to the preview vertical domain service of the second application launched by application A and the independent vertical domain service process corresponding to the preview vertical domain service of the second application launched by application B are the same process.

[0176] In some possible implementations, when at least one of the first application and the third application is running in the foreground, the vertical domain service independent process of the second application is running in the foreground.

[0177] For example, as shown in Figure 10, when either application A or application B is running in the foreground, or when both application A and application B are running in the foreground, the preview vertical domain service independent process runs in the foreground. When application A is displayed in the foreground, the preview display interface is displayed in the foreground; when application A is displayed in the background, the preview display interface runs in the background. Similarly, when application B is displayed in the foreground, the preview display interface is displayed in the foreground; when application B is displayed in the background, the preview display interface runs in the background.

[0178] In a possible implementation of the first aspect, when the first application and the third application are running in the background, the vertical domain service independent process of the second application is running in the background.

[0179] For example, as shown in FIG10 , when application A and application B are running in the background, the preview vertical domain service independent process is running in the background.

[0180] The above method specifically describes the vertical domain service provided by the second application. The following will describe another cross-application interface display method provided in an embodiment of the present application in combination with the above interface display schematic diagram.

[0181] Figure 12 shows a schematic flow chart of another example of a cross-application interface display method 1200 provided in an embodiment of the present application. As shown in Figure 12, the method 1200 shown in Figure 12 may include steps S1210 to S1260. The steps in the method 1200 are described in detail below in conjunction with Figure 12.

[0182] It should be understood that in the embodiments of the present application, the electronic device is used as an example to illustrate the method 1200. As an example and not a limitation, the execution body of the method 1200 may also be a chip used in the electronic device.

[0183] S1210: The electronic device displays a user interface of the first application, where the user interface includes first shared content of the second application.

[0184] S1220: The electronic device receives a first operation of the user on the first shared content.

[0185] The description of step S1210 and step S1220 can refer to step S1110 and step S1120, and will not be repeated here.

[0186] S1230: In response to the first operation, the electronic device determines at least one target application, and registers a configuration file of the first operation in the at least one target application.

[0187] S1240: Display at least one target application to the user on the display interface of the first application.

[0188] S1250: Receive a third operation on at least one target application, where the third operation is used to select a fourth application from the at least one target application.

[0189] In an embodiment of the present application, based on the user's first operation, the electronic device can determine at least one target application corresponding to the first operation, that is, the configuration file of the first operation is registered in the at least one target application, and the electronic device can display the application selection box of the multiple target applications to the user for the user to select.

[0190] For example, as shown in Figure 6 (a), after the electronic device responds to the user's sharing operation of the first shared content of the second application in the first application, the electronic device determines multiple target applications corresponding to the operation based on the sharing operation. As shown in Figure 6 (b), the multiple target applications include application A, application B, application C, application D, application E, and application F. The user can select an application from the multiple target applications for sharing. The third operation is the operation of selecting the application to be shared from application A, application B, application C, application D, application E, and application F. As shown in Figure 6 (b), the third operation is the operation of the user clicking on application C.

[0191] S1260. In response to the third operation, the independent process of the vertical domain service of the fourth application is run, and the first interface of the vertical domain service of the fourth application is displayed. When the main process of the fourth application is run, the second interface of the main process of the fourth application is displayed. The independent process of the vertical domain service is different from the main process.

[0192] In response to the third operation, the electronic device runs the vertical domain service process of the fourth application without starting the main process of the fourth application, and displays the first interface of the vertical domain service of the fourth application in the first application, thereby reducing the power consumption of the electronic device and improving the user experience.

[0193] For example, as shown in Figure 6 (b), the user selects application C for sharing. Then, after the electronic device receives the third operation of the user clicking on application C, as shown in Figure 6 (c), the sharing display interface of application C (the fourth application) is displayed on the first application. This sharing display interface is the first interface. It should be noted that, assuming that the electronic device clicks the sharing operation on the content when running the fourth application, the display interface in the fourth application (the second interface) and the display interface shown in Figure 6 (c) (the first interface) can be the same or different.

[0194] In another example of a cross-application interface display method provided by an embodiment of the present application, when an electronic device receives a first operation of a user on sharing content of a second application in the user interface of a first application, the electronic device can determine multiple target applications corresponding to the first operation, and the electronic device can display application selection boxes of the multiple target applications to the user for the user to select. Finally, based on the user's own needs, the electronic device runs an independent process of the vertical domain service of the fourth application in the first application, and displays the first interface provided by the vertical domain service of the fourth application. The fourth application does not need to start the main process to display the first interface. This method allows the user to quickly use the services provided by the fourth application (for example, sharing services, etc.) in the first application without starting the main process of the fourth application, thereby avoiding the problems of long interaction paths, cumbersome operations, and waste of electronic device power consumption caused by starting the main process of the fourth application, thereby improving the user experience.

[0195] The above describes in detail an example of the cross-application interface method provided by the present application. It is understandable that, in order to implement the above functions, the electronic device includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0196] This application can divide the cross-application interface display method into functional units based on the above method examples. For example, each function can be divided into various functional units, or two or more functions can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in this application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0197] Figure 13 shows a schematic diagram of the structure of an electronic device provided by the present application. The dotted line in Figure 13 indicates that the unit or module is optional. The electronic device 1300 can be used to implement the method described in the above method embodiment. The electronic device 1300 can be a terminal device or a server, or a module (such as a processor, a chip, or a chip system, etc.) applied to a terminal device or a server, or a logical node, a logical module or software that can implement all or part of the terminal functions, or a logical node, a logical module or software that can implement all or part of the server functions.

[0198] The electronic device 1300 includes one or more processors 1301, which can support the electronic device 1300 to implement the methods in the method embodiments corresponding to Figures 11 and 12. The processor 1301 can be a general-purpose processor or a dedicated processor. For example, the processor 1301 can be a central processing unit (CPU). The CPU can be used to control the electronic device 1300, execute software programs, and process data of software programs. The electronic device 1300 can also include a communication unit 1305 to implement signal input (reception) and output (transmission).

[0199] The electronic device 1300 may be a chip (system) including a memory and a processor, wherein the processor is configured to execute a computer program stored in the memory to implement the methods shown in the above embodiments.

[0200] The communication unit 1305 may be an input and / or output circuit of the chip (system), or the communication unit 1305 may be a communication interface of the chip (system), and the chip (system) may be a component of the electronic device 1300 .

[0201] For another example, the communication unit 1305 may be a transceiver of the electronic device 1300 , or the communication unit 1305 may be a transceiver circuit of the electronic device 1300 .

[0202] The electronic device 1300 may include one or more memories 1302, on which a program 1304 is stored. The program 1304 can be executed by the processor 1301 to generate instructions 1303, so that the processor 1301 performs the method described in the above method embodiment according to the instructions 1303. Optionally, data may also be stored in the memory 1302. Optionally, the processor 1301 may also read the data stored in the memory 1302. The data may be stored at the same storage address as the program 1304, or the data may be stored at a different storage address than the program 1304.

[0203] The processor 1301 and the memory 1302 may be provided separately or integrated together, for example, integrated on a system on chip (SOC) of an electronic device.

[0204] The specific manner in which the processor 1301 executes the cross-application interface display method can be found in the relevant description in the method embodiment.

[0205] It should be understood that each step of the above method embodiment can be completed by hardware logic circuits or software instructions in the processor 1301. The processor 1301 can be a CPU, a digital signal processor (DSP), a field programmable gate array (FPGA), or other programmable logic devices, such as discrete gates, transistor logic devices, or discrete hardware components.

[0206] The present application also provides a computer program product, which, when executed by the processor 1301, implements the method of any method embodiment in the present application.

[0207] The computer program product may be stored in the memory 1302 . For example, the computer program product is a program 1304 . The program 1304 is converted into an executable target file that can be executed by the processor 1301 after undergoing preprocessing, compilation, assembly, and linking.

[0208] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements any method embodiment of the present application. The computer program may be a high-level language program or an executable target program.

[0209] The computer-readable storage medium is, for example, memory 1302. Memory 1302 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SynchLink DRAM, SLDRAM) and direct RAM bus random access memory (Direct Rambus RAM, DRRAM).

[0210] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and equipment and the technical effects produced can refer to the corresponding processes and technical effects in the aforementioned method embodiments, and will not be repeated here.

[0211] In several embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, some features of the method embodiments described above can be ignored or not executed. The device embodiments described above are merely schematic, and the splitting of units is only a logical function splitting. There may be other splitting methods in actual implementation, and multiple units or components may be combined or integrated into another system. In addition, the coupling between the units or the coupling between the components may be direct coupling or indirect coupling, and the above coupling includes electrical, mechanical or other forms of connection.

[0212] The above embodiments are intended only to illustrate the technical solutions of the present application and are not intended to limit the same. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they may still modify the technical solutions described in the above embodiments or replace some of the technical features therein with equivalents, and that such modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application and are therefore intended to be included within the scope of protection of the present application.

[0213] Finally, the above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the scope of protection of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection of the claims.

Claims

1. A cross-application interface display method, applied to an electronic device, characterized in that: The method comprises: Displaying a user interface of the first application, wherein the user interface includes first shared content of the second application; receiving a first operation of a user on the first shared content; In response to the first operation, the independent process of the vertical domain service of the second application is run, and the first interface of the vertical domain service of the second application is displayed; when the main process of the second application is run, the second interface of the main process of the second application is displayed, and the independent process of the vertical domain service is different from the main process.

2. The method according to claim 1, characterized in that The vertical domain service independent process running the second application includes: creating the vertical domain service independent process, the vertical domain service independent process being used to run the vertical domain service of the second application, the vertical domain service being used to represent: a display interface when the second application is run in response to the first operation; When the vertical domain service is started, drawing the first interface based on the vertical domain service; The first interface is loaded into the first application.

3. The method according to claim 2, characterized in that Before displaying the first interface of the vertical domain service of the second application, the method further includes: Determining a vertical domain service control in the first application, where the vertical domain service control is used to limit a display area of ​​the first interface; The first interface is displayed in the vertical domain service control.

4. The method according to claim 3, characterized in that The first application corresponds to a graphic node tree, the graphic node tree includes a graphic node tree identifier, the graphic node tree identifier includes an identifier of the vertical domain service control, and loading the first interface into the first application includes: Mounting the node of the first interface on the graphic node tree of the first application based on the identifier of the vertical domain service control; The first interface is loaded into the first application according to the graphic node tree of the node on which the first interface is mounted.

5. The method according to any one of claims 2 to 4, characterized in that: The vertical domain service independent process is used to run the first vertical domain service and the second vertical domain service. The first vertical domain service includes a control corresponding to the second vertical domain service. The first vertical domain service and the second vertical domain service run in the same vertical domain service independent process. The first vertical domain service and the second vertical domain service are different.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: displaying a user interface of a third application, wherein the user interface of the third application includes the second shared content of the second application; Receiving a second operation of the user on the second shared content of the second application; In response to a second operation on the second shared content, an independent process of the vertical service of the second application is run, and a third interface of the vertical service of the second application is displayed. The vertical service of the second application includes a display window of a third application, and the display window of the third application is different from the display window of the first application.

7. The method according to claim 6, characterized in that When at least one of the first application and the third application is running in the foreground, the vertical domain service independent process of the second application is running in the foreground.

8. The method according to claim 6, characterized in that When the first application and the third application are both running in the background, the vertical domain service independent process of the second application runs in the background.

9. The method according to any one of claims 6 to 8, characterized in that: The independent vertical domain service process of the second application launched by the first application and the independent vertical domain service process of the second application launched by the third application are the same process.

10. The method according to any one of claims 1 to 9, characterized in that The first interface of the vertical domain service of the second application is displayed using at least one of full screen, floating window, or control embedding.

11. A cross-application interface display method, applied to an electronic device, characterized in that: The method comprises: Displaying a user interface of the first application, wherein the user interface includes first shared content of the second application; receiving a first operation of a user on the first shared content; In response to the first operation, determining at least one target application, in which a configuration file of the first operation is registered; Displaying the at least one target application to the user on a display interface of the first application; receiving a third operation on the at least one target application, wherein the third operation is used to select a fourth application from the at least one target application; In response to the third operation, the independent process of the vertical domain service of the fourth application is run, and the first interface of the vertical domain service of the fourth application is displayed. When the main process of the fourth application is run, the second interface of the main process of the fourth application is displayed. The independent process of the vertical domain service is different from the main process.

12. The method according to any one of claims 1 to 11, characterized in that The first operation includes: any one of a preview operation, a sharing operation or an editing operation.

13. An electronic device, characterized in that: The electronic device comprises at least one processor coupled to at least one memory: The at least one processor is configured to execute a computer program or instruction in the at least one memory, so that the electronic device executes the method as claimed in 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 or instruction. When a computer reads and executes the computer program or instruction, the computer executes the method according to any one of claims 1 to 12.

15. A chip, characterized in that: include: A processor, configured to execute the method according to any one of claims 1 to 12.

Images