Method for jumping to display interface, and electronic device

Abstract

Provided in the present application are a method for jumping to a display interface, and an electronic device. The method comprises: a first electronic device displaying a first link; and when the first link is a link of a target application program and the target application program is not installed on the first electronic device, in response to a click operation of a user on the first link, the first electronic device displaying a first display interface, wherein the first display interface is a display interface in an application market that is used for downloading the target application program. In the technical solution, when a user clicks on a link of an application program that is not installed on an electronic device, a detailed display interface of the application program may be directly displayed in an application market, thereby improving the efficiency of jumping to the display interface by means of the link.

Description

Methods and electronic devices for switching display interfaces

[0001] This application claims priority to Chinese Patent Application No. 202510107160.4, filed on January 22, 2025, entitled "Method and Electronic Device for Jumping to Display Interface", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of electronic technology, and more specifically, to a method and electronic device for switching display interfaces. Background Technology

[0003] During user interaction with an electronic device, links may be used to navigate to different interfaces. For example, when an electronic device detects that a user has clicked a link to an application (Application 1) within a messaging application, and if Application 1 is not installed on the device, the device will navigate to the application's Hypertext Markup Language 5 (H5) interface via a browser or the world wide area network (web). This H5 interface may include a download control for Application 1. When the electronic device detects that the user has clicked the download control, it can navigate to the application and then download and install Application 1 according to the user's request.

[0004] However, this redirection method has a long path and requires multiple user operations, resulting in low redirection efficiency. Summary of the Invention

[0005] This application provides a method and electronic device for jumping to a display interface, so as to improve the efficiency of electronic devices jumping to a display interface via links.

[0006] In a first aspect, a method for jumping to a display interface is provided, applied to a first electronic device, comprising: displaying a first link; and, if the first link is a link to a target application and the target application is not installed on the first electronic device, displaying a first display interface in response to a user clicking the first link, wherein the first display interface is a display interface in an application market used for downloading the target application.

[0007] For example, the first link can be carried in a link carrier such as a text message, email, or memo.

[0008] The display interface used for downloading the target application can be a details display interface for the target application, which may include information such as the target application's download control, description, icon, and download count. Alternatively, the display interface can be any other display interface that includes the target application's download control.

[0009] Based on the embodiments of this application, when a user clicks on a link to a target application that is not installed on the first electronic device, the details display interface of the target application can be directly displayed in the application market, thereby improving the efficiency of the electronic device jumping to the display interface via the link.

[0010] In some implementations, the method further includes: displaying a second link; and, in response to a user clicking the second link when the second link is not a link in the application, displaying a second display interface, which is the display interface corresponding to the second link displayed in a browser or on a global wide area network web application.

[0011] Based on the embodiments of this application, when a user clicks a link that does not belong to an application, the first electronic device can directly display the corresponding display interface through a browser or a global wide area network web interface, thereby improving the speed at which the electronic device jumps to the display interface.

[0012] In some implementations, before the first electronic device displays the first display interface, the method further includes: determining that the target application is not installed in the first electronic device based on first information and a first link of an application already installed in the first electronic device.

[0013] For example, the initial information of the installed application may include the domain name of the installed application. Alternatively, it may include information such as the package name, name, and organization to which the installed application belongs.

[0014] Based on the embodiments of this application, the first electronic device can determine that the target application corresponding to the first link is not installed in the first electronic device.

[0015] In some implementations, the first link includes a first domain name, and the first information includes the domain name of an installed application. Determining that the target application is not installed in the first electronic device based on the information of the installed application in the first electronic device and the first link includes: determining that the target application is not installed in the first electronic device when the first domain name does not match the domain name of an installed application.

[0016] Based on the embodiments of this application, by matching the first domain name in the first link with the domain name of the application already installed in the first electronic device, it can be determined whether the target application is installed in the first electronic device.

[0017] In some implementations, the first link includes a first domain name. Before displaying the first display interface, the method further includes: determining that the first link belongs to the target application based on the first domain name and a first correspondence, wherein the first correspondence is the correspondence between the application's second information and the domain name.

[0018] For example, the second information of the application may include information such as the application's package name, name, version number, and organization.

[0019] Based on the embodiments of this application, the first electronic device can determine that the first link belongs to an application based on the domain name in the first link and the first correspondence, which is beneficial for subsequently calling the application market to display the details display interface of the application corresponding to the first link.

[0020] In some implementations, determining that a first link belongs to a target application based on a first domain name and a first correspondence includes: determining that a first link belongs to a target application when a target application is matched from the first correspondence based on the first domain name.

[0021] Based on the embodiments of this application, the first electronic device can easily determine that the first link belongs to the target application, which is beneficial for subsequently calling the application market to display the details display interface of the application corresponding to the first link.

[0022] In some implementations, the method further includes: determining whether a second link does not belong to the application based on the correspondence between the second domain name and the first domain name.

[0023] In some implementations, determining that a second link does not belong to an application based on the second domain name and the first correspondence includes: determining that a second link does not belong to an application when no application is matched from the first correspondence based on the second domain name.

[0024] Based on the embodiments of this application, the first electronic device can easily determine that the second link does not belong to the application, which is beneficial for subsequently calling the browser or web to display the display interface corresponding to the second link.

[0025] In some implementations, before determining that the first link belongs to the application based on the first domain name and the first correspondence, the method further includes: sending a first request message to a second electronic device, the first request message being used to obtain the first correspondence; and receiving the first correspondence sent by the second electronic device.

[0026] For example, the second electronic device can be a server or a cloud server. Alternatively, the second electronic device can also be a smart host, etc.

[0027] Based on the embodiments of this application, the correspondence between application information and domain name can be obtained from the cloud in advance. During subsequent matching, it can be quickly determined from the local machine whether the first link belongs to the application, thereby improving the page redirection speed.

[0028] In other examples, the first electronic device may also periodically send a first request message to the second electronic device to obtain the latest first correspondence.

[0029] In this way, the first electronic device can obtain the latest application information and the correspondence between the domain name, thereby expanding the scope of applicability of the technical solution.

[0030] It should be understood that the embodiments of this application do not limit the above-mentioned period. For example, the period can be 1 day, 3 days, or 1 week, etc.

[0031] In some implementations, the second information of the application includes at least one of the following: the application's domain name, the application's package name, the application's name, or the application's version number.

[0032] In some implementations, the first link includes a first domain name. Before displaying the first display interface, the method further includes: sending the first domain name to a third electronic device; and receiving second information of the target application corresponding to the first domain name sent by the third electronic device.

[0033] For example, the third electronic device can be a server or a cloud server. Alternatively, the third electronic device can also be a smart host, etc.

[0034] Based on the embodiments of this application, the first electronic device can query in real time from the cloud whether the first link corresponds to the target application, thereby eliminating the need for the electronic device to download the correspondence between the domain name and the application's second information, thus saving the memory space of the first electronic device.

[0035] In a second aspect, a method for jumping to a display interface is provided, including modules for implementing the method for jumping to a display interface as described in the first aspect and any possible implementation thereof.

[0036] Thirdly, an electronic device is provided, comprising: one or more processors; one or more memories; said one or more memories storing one or more programs that, when executed by said one or more processors, cause a method for jumping to a display interface as described in the first aspect and any possible implementation thereof to be executed.

[0037] Fourthly, a chip is provided, the chip including a processor and a communication interface, the communication interface being used to receive signals and transmit the signals to the processor, the processor processing the signals such that a method for jumping to a display interface as described in the first aspect and any possible implementation thereof is executed.

[0038] Fifthly, a readable storage medium is provided, wherein instructions are stored therein, which, when executed on an electronic device, cause a method for switching display interfaces as described in the first aspect and any possible implementation thereof to be performed.

[0039] In a sixth aspect, a program product is provided, the program product including program code, which, when run on an electronic device, causes a method for jumping to a display interface as described in the first aspect and any possible implementation thereof to be executed. Attached Figure Description

[0040] Figure 1 is a schematic structural diagram of an electronic device provided in an embodiment of this application.

[0041] Figure 2 is an architecture diagram of the electronic device provided in an embodiment of this application.

[0042] Figure 3 is a schematic framework diagram of an electronic device provided in an embodiment of this application.

[0043] Figure 4 is a schematic diagram of a set of graphical user interfaces (GUIs) provided in an embodiment of this application.

[0044] Figure 5 is a schematic diagram of another set of GUIs provided in an embodiment of this application.

[0045] Figure 6 is a schematic flowchart of a method for jumping to a display interface provided in an embodiment of this application.

[0046] Figure 7 is a schematic flowchart of a method for jumping to a display interface provided in an embodiment of this application.

[0047] Figure 8 is a schematic flowchart of a method for jumping to a display interface provided in an embodiment of this application.

[0048] Figure 9 is a schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0049] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0050] The display method in this application embodiment can be applied to smartphones, wearable devices, smart TVs, tablets, laptops, personal computers (PCs), ultra-mobile personal computers (UMPCs), netbooks, in-vehicle devices, foldable devices, Internet of Things (IoT) devices, augmented reality devices, virtual reality devices, etc.

[0051] Figure 1 shows a schematic diagram of the structure of electronic device 100. Electronic device 100 may include processor 110, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, display screen 194, external memory interface 120, internal memory 121, and touch sensor 180K, etc.

[0052] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0053] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0054] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0055] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0056] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Bluetooth low energy (BLE), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0057] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0058] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0059] The display screen 194 is used to display images, videos, etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1. In this embodiment, the display screen 194 can be used to display various display interfaces and application switching entries, etc.

[0060] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.

[0061] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of electronic device 100 (such as the correspondence between domain names and application installation package names, audio data, etc.).

[0062] For example, the internal memory 121 can also be used to store data, such as the mapping between link domain names and application installation package names.

[0063] Touch sensor 180K can be disposed on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen". Touch sensor 180K is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be disposed on the surface of electronic device 100, in a different location than display screen 194.

[0064] Figure 2 is a software structure block diagram of an electronic device 100 according to an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces.

[0065] For example, the system is divided into four layers, from top to bottom: the application layer, the application framework layer, the system library layer, and the kernel layer. The application layer may include a series of application packages.

[0066] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0067] As shown in Figure 2, the application framework layer may include a window manager, content provider, phone manager, resource manager, notification manager, view system (not shown in the figure), application runtime management service, package management service, application domain management service, etc.

[0068] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0069] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0070] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0071] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0072] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0073] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0074] The application runtime management service can be used to manage application startup, interface navigation, and other functions. This application runtime management server can also interact with the package management service to identify applications installed on the electronic device 100. Furthermore, the application runtime management service can interact with the application domain name management service to determine whether a link belongs to an application.

[0075] Package management services can be used to manage information about applications installed within an application. For example, it can determine whether an electronic device has an application corresponding to a domain name installed based on the domain name in a link.

[0076] Application domain management services can be used to match application information (such as the application's package name) with domain names. This service can also interact with servers to obtain these matching relationships.

[0077] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part is the core library itself.

[0078] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0079] The system library can include multiple functional modules. For example: surface manager, media library, 3D graphics processing library, 2D graphics engine, etc.

[0080] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0081] The media library supports playback and recording of various common audio and video formats, as well as still image files. It also supports multiple audio and video encoding formats.

[0082] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0083] A 2D graphics engine is a graphics engine for 2D drawing.

[0084] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0085] It should be understood that the embodiments in this application are illustrated using the Android system as an example. In other examples, this technical solution can also be applied to the HarmonyOS operating system or other operating systems.

[0086] Before introducing the technical solutions of the embodiments of this application, some technical terms that may be involved in this application will be introduced as follows.

[0087] Domain name: The name of a website, which is the unique identifier of the website on the Internet.

[0088] Application link: refers to a URL that allows direct access to specific content within an application.

[0089] Link carrier: The medium that carries the link, such as text messages, memos, emails, web pages, etc.

[0090] During user interaction with electronic devices, links may be used to navigate to different interfaces. For example, when an electronic device detects that a user has clicked a link to an application (Application 1) within a messaging application, and if Application 1 is not installed on the device, the device will redirect to an H5 (HTML5) page for Application 1 via a browser or the world wide area network (web). This H5 page may include a download control for Application 1. When the electronic device detects that the user has clicked the download control, it can navigate to the application and then download and install Application 1 according to the user's request.

[0091] However, this redirection method has a long path and requires multiple user operations, resulting in low redirection efficiency.

[0092] In view of this, embodiments of this application provide a method and electronic device for jumping to a display interface. In this technical solution, when a user clicks a link to an application not installed on the electronic device, the application's details interface can be directly displayed in the application market, thereby improving the efficiency of page jumping.

[0093] The following section will describe the technical solution of the jump display interface provided in the embodiments of this application with reference to Figures 3 to 8.

[0094] For example, Figure 3 is a schematic diagram of the interaction between an electronic device and a cloud server according to an embodiment of this application. As shown in Figure 3, the application layer of the electronic device 200 may include application 1, application 2, browser, ..., application market, etc. The application framework layer may at least include application runtime management service, package management service, and application domain name management service.

[0095] It should be understood that application 1 can serve as a carrier of the link; for example, application 1 can be a text message, memo, email, etc. In this embodiment of the application, a text message is used as an example to illustrate the link, but this should not limit the scenarios to which this application can be applied.

[0096] For example, electronic device 200 receives a text message that may include a link A. Link A may or may not belong to an application, and may include a domain name A. When electronic device 200 detects that a user has clicked on link A, the text message can transmit the link to the application runtime management service.

[0097] In some implementations, the application runtime management service may interact with the package management service to determine whether a link to an application installed in the electronic device 200 matches link A.

[0098] For example, the application runtime management service can send query request A to the package management service and receive query result A from the package management service.

[0099] The first possible outcome is that the application runtime management service determines, based on query result A, that link A is not matched among the links to the installed applications. In this case, if link A is a link to an application, then the electronic device 200 does not have that application installed. Alternatively, link A is not a link to an application.

[0100] The second outcome is that the application runtime management service determines, based on query result A, that a link A has been successfully matched among the links of the installed applications. For example, if link A belongs to application A, then the electronic device 200 has already installed the application corresponding to link A. In this case, the application runtime management service can directly call application A, enabling the electronic device 200 to display the interface of link A.

[0101] For the first outcome, the application runtime management service also needs to interact with the application domain management service to determine whether link A belongs to the application.

[0102] For example, the application runtime management service can send a query request B to the application domain name management service and receive the query result B sent by the application domain name management service.

[0103] In one scenario, query result B might indicate that link A belongs to application A. Since application A is not installed on electronic device 200, the application management service can access the application market and cause electronic device 200 to directly display the details interface of application A from the application market. This details interface can include information such as the icon, name, description, rating, and number of installations of application A. It can also include a download control, allowing users to easily learn about and download application A.

[0104] In one scenario, if query result B indicates that link A does not belong to the application, the application runtime management service can directly call a browser or web browser to open link A.

[0105] In some implementations, the application runtime management service can interact with the application domain name management service to determine whether link A is a link of the application; for specific implementations, please refer to the description above.

[0106] When the application runtime management service determines that link A does not belong to the application, link A can be opened directly in a browser or on the web.

[0107] When the application runtime management service determines that link A belongs to application A, it further interacts with the package management service to determine whether application A corresponding to link A is installed in electronic device 200. For specific implementation details, please refer to the description above.

[0108] When the application runtime management service determines that application A has been installed on electronic device 200, it directly invokes application A to open link A.

[0109] When the application management service determines that application A is not installed on electronic device 200, it can call the application market and make electronic device 200 directly display the details display interface of application A in the application market.

[0110] The application domain name management service can interact with the application domain name management microservice in cloud server 210 to obtain the correspondence between application information and domain names.

[0111] For example, the mapping relationship could be the mapping relationship between the application's package name and the domain name. Alternatively, the mapping relationship could also be the mapping relationship between other information of the application (such as the application name, the organization to which it belongs, or other information that identifies the application) and the domain name, which is not limited in this embodiment of the application.

[0112] It should be understood that an application may correspond to one or more domain names, and this application embodiment does not limit this.

[0113] The application's domain name management service can periodically interact with the cloud server 210 to obtain the latest application information and its correspondence with the domain name. For example, this period can be one day, one week, one month, etc., and the specific value of this period is not limited in this embodiment.

[0114] The application's domain management service can also store the above-mentioned correspondences in the database of electronic devices for quick retrieval later.

[0115] Understandably, after receiving the above query request B, the application domain management service can search the database for information about the application corresponding to domain A in link A. If no result is found, then link A does not belong to an application; if application A is found, then link A belongs to application A.

[0116] Alternatively, after receiving the aforementioned query request B, the application domain name management server can also interact with the cloud server 210 in real time to determine whether link A belongs to the application. Alternatively, the electronic device 200 can also query from websites that include the aforementioned correspondence to determine whether link A belongs to the application.

[0117] In other examples, the electronic device 200 has pre-stored the correspondence between application information and domain names, thus eliminating the need to interact with the cloud server 210.

[0118] The cloud server 210 may include an application domain name management microservice, which can be used to manage the mapping between application information and domain names. For example, application developers need to register the mapping between their application information and domain names on the cloud server 210.

[0119] The following section will use the graphical user interfaces (GUIs) shown in Figures 4-5 to illustrate the process by which electronic devices can directly jump to the details display interface of applications in the app store via links.

[0120] For example, Figure 4 is a schematic diagram of a set of GUIs provided in an embodiment of this application. In Figure 4(a) to (b), the process by which the electronic device 300 jumps directly to the details display interface of the application via a link is shown.

[0121] Referring to Figure 4(a), the GUI can be the SMS display interface 310 of an electronic device. This display interface 310 may include the time the SMS was received, the SMS content, the SMS source, and an editing display box. The SMS content may include a link 311. This link 311 may include a domain name; for example, if the link 311 is http: / / app2.X / XXX, then the domain name is "app2.X". It can be understood that the domain name "app2.X" can be the domain name of an application.

[0122] For example, when the electronic device 300 detects that the user has clicked the link 311, it can display the GUI shown in Figure 4(b).

[0123] Understandably, when electronic device 300 detects that a user clicks on link 311, it can determine whether link 311 (or the domain name in link 311) belongs to an application, and determine from the installed applications whether there is an application that matches link 311. If it is determined that link 311 belongs to an application and the electronic device does not have that application installed, the GUI shown in Figure 4(b) can be displayed.

[0124] This application embodiment does not limit the specific order in which the electronic device determines whether link 311 belongs to an application and determines from the installed applications whether there is an application that can match link 311.

[0125] Referring to Figure 4(b), this GUI can be the details display interface 320 of App2 in the app store. This display interface 320 may include a search control 321, a share control 322, an app icon 323 for App2, the name, rating, number of installations, recommended age for use of App2, a description of App2, promotional cards 324 and 325, and a download or installation control 326, etc.

[0126] It should be understood that after the electronic device 300 detects the user's click on the control 326, it can download and install the App 2. After installation, the electronic device 300 can run the App 2 and redirect to the display interface corresponding to link 311. Alternatively, the electronic device 300 can run the App 2 and redirect to the display interface corresponding to link 311 based on the user's operation.

[0127] In other examples, the GUI shown in Figure 4(b) can also be a download display interface for App2. For example, the download display interface can include a list of multiple applications, in which App2 can be at the top of the list, and the user can download App2 through the download control of App2 in the download display interface.

[0128] In this way, when a user clicks a link belonging to an application, and even if the application is not installed on the electronic device, the electronic device can directly display the details of the application in the app store. This eliminates the need for the electronic device to display the application's H5 interface through a browser or web, thus improving the efficiency of the electronic device's interface redirection.

[0129] In some cases, the aforementioned link may not be an application link; in such cases, the electronic device can directly open the link through a browser. This technical solution will be described below with reference to Figure 5.

[0130] For example, Figure 5 is a schematic diagram of another set of GUIs provided in an embodiment of this application. In Figure 5(a) to (b), the process of electronic device 300 jumping to browser via a link is shown.

[0131] It should be understood that the description of (a) in Figure 5 can be found in the description of (a) in Figure 4, and for the sake of brevity, it will not be repeated here.

[0132] It is understood that, in this embodiment, the domain name "test.com" included in link 331 does not belong to the application. For example, link 331 could be a URL that does not belong to any application.

[0133] For example, when the electronic device 300 detects that the user has clicked the link 331, it can display the GUI shown in Figure 5(b).

[0134] Understandably, when electronic device 300 detects that a user has clicked on link 331, it can determine from the installed applications whether there is an application that matches link 331, and whether link 331 (or the domain name in link 331) belongs to an application. If it is determined that link 331 does not belong to an application, the GUI shown in Figure 5(b) can be displayed.

[0135] In other examples, if the electronic device first determines whether link 331 (or the domain name in link 331) belongs to an application, and then determines that link 311 (or the domain name in link 331) does not belong to an application, the process of determining from the installed applications whether there is an application that can match link 331 may not be performed.

[0136] Referring to Figure 5(b), the GUI can be the display interface 340 of link 331 opened in the browser.

[0137] In this way, when an electronic device determines that a user has clicked a link that does not belong to an application, it can directly display the corresponding interface through a browser or web, thus allowing the user to quickly jump to the corresponding interface.

[0138] The following section, in conjunction with Figure 6, describes the interaction process between various modules in the electronic device during the process of switching to the display interface in this application embodiment.

[0139] For example, FIG6 is a schematic flowchart of a method for jumping to a display interface provided in an embodiment of this application. As shown in FIG6, the method 400 may include steps 401 to 412.

[0140] The electronic device may include application runtime management services, package management services, application domain name management services, application marketplace, database, and App1. For example, the electronic device may be electronic device 200, electronic device 300, etc. mentioned above.

[0141] 401. The application domain management service sends a data synchronization request to the cloud server. The cloud server then receives this data synchronization request.

[0142] A 402 error occurs when the cloud server sends the mapping between the application's target information and its domain name to the application domain name management service. The application domain name management service then receives this mapping.

[0143] For example, the target information may be one or more of the following: the application's package name, name, organization, version, or other information that can identify the application.

[0144] This cloud server may include an application domain name management microservice, which can be used to manage the mapping between application information and domain names. For example, application developers need to register the mapping between their application's target information and domain names on this cloud server. This cloud server can be cloud server 210 mentioned above.

[0145] 403, Application Domain Management Service stores the mapping between application target information and domain names in a database.

[0146] It should be understood that steps 401 to 403 are optional steps, and in some examples, steps 401 to 403 may not be performed. In this case, the correspondence can be pre-stored in the electronic device.

[0147] 404 error, App1 displays the first link.

[0148] For example, App1 can be a text message. When an electronic device receives a text message that includes a first link and detects that the user has opened the text message, the first link can be displayed.

[0149] Alternatively, App1 can also be a carrier that can hold links, such as emails or memos.

[0150] It should be understood that the first link may include a domain name. For example, referring to Figure 4(a), the first link may be link 311.

[0151] 405, In response to detecting that a user has clicked the first link, App1 sends the first link to the application runtime management service. Accordingly, the application runtime management service receives the first link.

[0152] 406. The application runtime management service sends query request 1 to the package management service. Query request 1 is used to query whether the first link corresponds to an installed application. Accordingly, the package management service receives query request 1.

[0153] The query request 1 may include the first link or domain name, which can be used to match applications already installed on the electronic device to determine whether an application is matched.

[0154] 407, Package Management Service sends query result 1 to Application Runtime Management Service.

[0155] For example, the package management service may include information about installed applications, such as the application's package name, domain name, name, installation time, and installation directory. After receiving query request 1, the package management service can match the domain name included in query request 1 with the domain name of the installed applications and send the matching result to the application runtime management service.

[0156] In one example, if the package management service does not match any results, then query result 1 can be used to indicate that no application was matched. In this case, step 408 can be continued.

[0157] In one example, if the package management service matches an application, then query result 1 can include the application's target information. In this case, the application runtime management service can directly call that application to open the first link. Thus, if the electronic device already has the application corresponding to the first link installed, the first application can be quickly invoked and the corresponding display interface can be displayed.

[0158] For example, an application installed on an electronic device may include a configuration file, which may contain the domain name corresponding to the application. Thus, when the package management service receives query request 1, it can match the request based on the corresponding domain name.

[0159] 408, The application runtime management service sends query request 2 to the application domain name management service. Query request 2 is used to query whether the first link corresponds to the application.

[0160] For example, the query request 2 may include the first link or the domain name in the first link.

[0161] Depending on the results returned by query request 2, this section may include Scheme 1 and Scheme 2. Scheme 1 includes steps 409 to 411, and Scheme 2 includes steps 409a to 410a.

[0162] Option 1

[0163] 409. The application domain management service sends the target information of the target application to the application runtime management service.

[0164] For example, after receiving query request 2, the application domain name management service can match the domain name in query request 2 from the database to determine whether the domain name corresponds to an application. Once a target application is matched, the target information of the target application can be sent to the application runtime management service.

[0165] For example, if query request 2 includes domain name 2, and the database stores the correspondence between domain name 2 and target information (such as package name) of the target application, then the first link corresponds to the target application.

[0166] For example, the application domain name management service can also send the query request 2 to the cloud server to query whether it corresponds to the application.

[0167] For example, the application domain name management service receives information from the cloud server indicating that no corresponding target application was found, thereby determining that the first link is not for the target application.

[0168] It should be understood that steps 406 to 407 can also be executed after step 409. That is, the electronic device can first determine whether the first link belongs to an application, and after determining that the first link corresponds to the target application, it can then determine whether the target application is installed on the electronic device. In this case, when the electronic device determines that the first link does not belong to an application, it can directly call a browser or web browser to open the first link without matching it with an installed application, thereby improving the speed of opening the first link.

[0169] 410. The application runtime management service sends the target information of the target application to the application market. The application market then accepts this target information.

[0170] 411, The app store displays the details of the target application.

[0171] The app store can identify the target application based on this target information and display a detailed display interface for that target application. For example, referring to Figure 4(b), this detailed display interface can be display interface 320.

[0172] In this technical solution, when the first link corresponds to the target application, the details display interface of the target application can be opened directly through the application market, thereby avoiding the need to open the H5 display interface of the target application through a browser or web, shortening the jump path and improving the efficiency of electronic devices jumping to display interfaces.

[0173] Option 2

[0174] 409a, The Application Domain Name Management Service sends Instruction Message A to the Application Runtime Management Service, Instruction Message A indicating that the first link does not correspond to an application. Accordingly, the Application Runtime Management Service receives Instruction Message A.

[0175] For example, after receiving the above query request 2, the application domain name management service can match the domain name in the query request 2 from the database to determine whether the domain name corresponds to an application. If no target application is matched, the service can send the instruction information A to the application runtime management service.

[0176] For example, if query request 2 includes domain name 2, and the database does not store a correspondence between domain name 2 and target information (such as package name) of the target application, then the first link does not correspond to the target application.

[0177] Alternatively, the application domain management service can send the query request 2 to the cloud server to check if it corresponds to the application.

[0178] For example, the application domain name management service receives information from the cloud server indicating that no corresponding target application was found, thereby determining that the first link is not for the target application.

[0179] 410a, The application runtime management service calls a browser or web browser to open the first link.

[0180] After receiving instruction information A, the application runtime management service can determine that the first link does not belong to the application, and can then directly call a browser or web application to open the first link.

[0181] For example, referring to Figure 5(b), the application running management service calls a browser or web to open the first link, at which point the electronic device can display the display interface 340.

[0182] In this technical solution, when it is determined that the first link does not correspond to the target application, the display interface corresponding to the first link can be directly displayed through a browser or web, thereby allowing for quick navigation to the corresponding display interface.

[0183] For example, FIG7 is a schematic flowchart of a method for switching display interfaces provided in an embodiment of this application. As shown in FIG7, the method 500 can be applied to an electronic device, and the method 500 may include steps 510 to 560.

[0184] For example, the electronic device can be electronic device 200, electronic device 300, etc. mentioned above.

[0185] 510, the electronic device displays the first link.

[0186] The first link may include a domain name.

[0187] For example, referring to Figure 4, the first link can be link 331.

[0188] 520, In response to the user clicking the first link, the electronic device determines whether the first link belongs to the application.

[0189] For example, an electronic device can match a domain name from a database based on the domain name in the first link to determine whether the domain name corresponds to an application.

[0190] For example, the electronic device can also query the cloud server to see if the domain name in the first link corresponds to the application.

[0191] When the electronic device determines that the first link belongs to an application, it may proceed to step 530. When the electronic device determines that the first link does not belong to an application, it may proceed to step 540.

[0192] 530, The electronic device determines whether to install the target application corresponding to the first link.

[0193] For example, the electronic device may include information about all installed applications, such as package name, domain name, organization, installation time, and installation path. The electronic device can compare the domain name in the first link with the domain names of the installed applications to determine whether to install the target application corresponding to the first link.

[0194] It should be understood that the specific order of steps 520 and 530 is not limited in the embodiments of this application. In some examples, step 520 may also be located after step 530.

[0195] When the electronic device determines that the target application corresponding to the first link has been installed, step 550 can be executed. When the electronic device determines that the target application corresponding to the first link has not been installed, step 560 can be executed.

[0196] 540. The electronic device displays the interface corresponding to the first link in a browser or web.

[0197] Once the electronic device determines that the first link does not belong to the application, it can directly open the first link in a browser or web browser and display the corresponding interface.

[0198] 550, Electronic devices display the details of the target application in the application market.

[0199] When the electronic device determines that the target application corresponding to the first link is not installed, the app store can be directly accessed to display the details of the target application.

[0200] This details display interface can also be understood as a display interface used for downloading or installing the target application.

[0201] In this way, electronic devices can be redirected to the details display interface of the target electronic device in the app store in one step, allowing users to easily download the target application from the details display interface, thus improving the efficiency of redirecting to the display interface via a link.

[0202] 560, the electronic device calls the target application to display the display interface corresponding to the first link.

[0203] When the electronic device determines that the target application has been installed, it can invoke the target application to open the first link and display the corresponding display interface.

[0204] Based on the embodiments of this application, when a user clicks the first link belonging to the target application, and the electronic device does not have the target application installed, the electronic device does not need to jump to the H5 display interface displayed in the browser or web, but can directly jump to the details display interface of the target application in the application market, thereby improving the efficiency of jumping to the display interface through the link.

[0205] It is understood that the technical solutions or parts thereof in the various embodiments of this application described above may be combined with each other to form new technical solutions if there is no logical conflict. Such technical solutions should not be considered to be outside the scope of protection of this application.

[0206] For example, FIG8 is a schematic flowchart of a jump display interface provided in an embodiment of this application. As shown in FIG8, the method 800 can be applied to a first electronic device, and the method 800 may include steps 810 to 820.

[0207] 810, the first electronic device displays the first link.

[0208] For example, the first electronic device may display the first link via a link carrier. For instance, the link carrier may include a text message, email, memo, webpage, etc.

[0209] For example, referring to Figure 4(a), the link carrier can be a text message, the first link can be link 311, and after receiving a text message including the first link, the first electronic device can display the first link in response to the user's operation.

[0210] 820, if the first electronic device is connected to a target application and the target application is not installed on the first electronic device, the first electronic device displays a first display interface in response to the user clicking the first link. The first display interface is a display interface in the application market used to download the target application.

[0211] It should be understood that the display interface used to download the target application can be a details display interface for the target application, which may include information such as the download control, description, icon, and download count of the target application. The display interface used to download the target application may also be other display interfaces that include the download control for the target application.

[0212] For example, referring to Figure 4(b), the first display interface can be display interface 320, and the target application can be App2. In this display interface 320, the user can download the target application.

[0213] In other examples, the first display interface may include a list of multiple applications, where App2 may be at the top of the list, and the user can download App2 through the download control of App2 in the download display interface.

[0214] Based on the embodiments of this application, when a user clicks on a link to a target application that is not installed on the first electronic device, the details display interface of the target application can be directly displayed in the application market, thereby improving the efficiency of the electronic device jumping to the display interface via the link.

[0215] In some embodiments, the method 800 further includes:

[0216] The first electronic device displays the second link;

[0217] When the second link is not a link in the application, the first electronic device displays a second display interface in response to the user clicking the second link. The second display interface is the display interface corresponding to the second link displayed in a browser or on a global wide area network web application.

[0218] For example, referring to (a) in Figure 5, the second link can be link 331.

[0219] Referring to Figure 5(b), the second display interface can be display interface 340.

[0220] Based on the embodiments of this application, when a user clicks a link that does not belong to an application, the first electronic device can directly display the corresponding display interface through a browser or a global wide area network web interface, thereby improving the speed at which the electronic device jumps to the display interface.

[0221] In some embodiments, before the first electronic device displays the first display interface, the method 800 further includes:

[0222] Based on the first information and first link of the application already installed in the first electronic device, it is determined that the target application is not installed in the first electronic device.

[0223] For example, the initial information of the installed application may include the domain name of the installed application. Alternatively, it may include information such as the package name, name, and organization to which the installed application belongs.

[0224] Based on the embodiments of this application, the first electronic device can determine that the target application corresponding to the first link is not installed in the first electronic device.

[0225] In some embodiments, the first link includes a first domain name, and the first information includes the domain name of an installed application. Determining that the target application is not installed in the first electronic device based on the first information of the applications installed in the first electronic device and the first link includes:

[0226] When the first electronic device does not find a matching domain name for the installed application in the first domain name, it determines that the target application is not installed in the first electronic device.

[0227] For example, referring to Figure 4, the first domain name can be "app2.X".

[0228] For example, if "app2.X" is not found in the domain name of the installed application, it can be determined that the target application is not installed on the first electronic device, or that the first link corresponding to the first domain name is not a link of the application.

[0229] Based on the embodiments of this application, by matching the first domain name in the first link with the domain name of the application already installed in the first electronic device, it can be determined whether the target application is installed in the first electronic device.

[0230] In some embodiments, the first link includes a first domain name, and before displaying the first display interface, the method 800 further includes:

[0231] The first electronic device determines that the first link belongs to the target application based on the first domain name and the first correspondence relationship, wherein the first correspondence relationship is the correspondence between the application's second information and the domain name.

[0232] For example, the second information of the application includes information such as the application's package name, name, and organization.

[0233] Based on the embodiments of this application, the first electronic device can determine that the first link belongs to the target application based on the domain name in the first link and the first correspondence, which is beneficial for subsequently calling the application market to display the details display interface of the application corresponding to the first link.

[0234] In some embodiments, determining that a first link belongs to a target application based on a first domain name and a first correspondence includes:

[0235] When the first electronic device matches the target application from the first correspondence based on the first domain name, it determines that the first link belongs to the target application.

[0236] Based on the embodiments of this application, the first electronic device can easily determine that the first link belongs to an application, which is beneficial for subsequently calling the application market to display the details display interface of the application corresponding to the first link.

[0237] In some implementations, the method further includes: determining whether a second link does not belong to the application based on the correspondence between the second domain name and the first domain name.

[0238] In some implementations, determining that a second link does not belong to an application based on the second domain name and the first correspondence includes: determining that a second link does not belong to an application when no application is matched from the first correspondence based on the second domain name.

[0239] Based on the embodiments of this application, the first electronic device can easily determine that the second link does not belong to the application, which is beneficial for subsequently calling the browser or web to display the display interface corresponding to the second link.

[0240] In some embodiments, before determining that the first link belongs to the target application based on the first domain name and the first correspondence, the method 800 further includes:

[0241] The first electronic device sends a first request message to the second electronic device, the first request message being used to obtain a first correspondence;

[0242] The first electronic device receives the first correspondence sent by the second electronic device.

[0243] For example, the second electronic device can be a server or a cloud server. Alternatively, the second electronic device can also be a smart host, etc.

[0244] Based on the embodiments of this application, the correspondence between application information and domain name can be obtained from the cloud in advance. During subsequent matching, it can be quickly determined from the local machine whether the first link belongs to the application, thereby improving the page redirection speed.

[0245] In other examples, the first electronic device may also periodically send a first request message to the second electronic device to obtain the latest first correspondence.

[0246] In this way, the first electronic device can obtain the latest application information and the correspondence between the domain name, thereby expanding the scope of applicability of the technical solution.

[0247] It should be understood that the embodiments of this application do not limit the above-mentioned period. For example, the period can be 1 day, 3 days, or 1 week, etc.

[0248] In some embodiments, the application information includes at least one of the following: the application's domain name, the application's package name, the application's name, or the application's version number.

[0249] In some implementations, the first link includes the first domain name, and before displaying the first display interface, the method 800 also includes:

[0250] The first electronic device sends the first domain name to the third electronic device;

[0251] The first electronic device receives the second information of the target application corresponding to the first domain name sent by the third electronic device.

[0252] The second information may include at least one of the following: the target application's package name, name, version number, and organization.

[0253] For example, the third electronic device can be a server or a cloud server. Alternatively, the third electronic device can also be a smart host, etc.

[0254] It should be understood that the third electronic device and the aforementioned second electronic device may be the same electronic device or different electronic devices.

[0255] Based on the embodiments of this application, the first electronic device can query in real time from the cloud whether the first link corresponds to the target application, thereby eliminating the need for the electronic device to download the correspondence between the domain name and the application information, thus saving the memory space of the first electronic device.

[0256] For example, FIG9 is a schematic block diagram of an electronic device provided in an embodiment of the present application. As shown in FIG9, the electronic device 900 includes one or more processors 910; one or more memories 920; the one or more memories 920 store one or more instructions, which, when executed by one or more processors 910, cause the method described in any of the possible implementations above to be executed.

[0257] For example, the electronic device 900 can be the electronic device 100, electronic device 200, electronic device 300, cloud server 210, electronic device in the embodiment, first electronic device, second electronic device, cloud server, etc. mentioned above.

[0258] The electronic device 900 can be used to execute methods 400, 500 and 800 mentioned above.

[0259] This application also provides an electronic device, including a processor, a memory, and a communication interface, wherein the communication interface is used to receive signals, the memory is used to store signals, the communication interface is also used to transmit signals to the processor, and the processor processes the signals so that the method of jumping to the display interface as described in any of the possible implementations above is executed.

[0260] This application also provides an apparatus for jumping to a display interface, including a processor and a communication interface. The communication interface is used to receive signals and transmit the signals to the processor. The processor processes the signals so that the method for jumping to a display interface as described in any of the possible implementations above is executed.

[0261] The device can be a chip. For example, the chip can be a chip system or a standalone chip.

[0262] This application also provides a readable storage medium (also known as a computer-readable storage medium) storing instructions that, when executed on an electronic device, cause the electronic device to perform the aforementioned method steps to implement the method for jumping to the display interface in the above embodiments.

[0263] This application also provides a program product (also known as a computer program product) that, when run on an electronic device, causes the electronic device to perform the aforementioned steps to implement the method for jumping to the display interface in the above embodiments.

[0264] This application also provides an apparatus including a module for implementing the method of jumping to a display interface as described in any of the preceding embodiments.

[0265] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store instructions, and when the apparatus is running, the processor may execute the instructions stored in the memory to cause the apparatus to perform the method of jumping to the display interface in the above method embodiments.

[0266] In this embodiment, the device, readable storage medium, program product or apparatus are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0267] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0268] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0269] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0270] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0271] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0272] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0273] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for switching to a display interface, characterized in that, The method is applied to a first electronic device, and the method includes: Show the first link; If the first link is a link to the target application and the target application is not installed on the first electronic device, in response to the user clicking the first link, a first display interface is displayed, which is a display interface in the application market used to download the target application.

2. The method according to claim 1, characterized in that, The method further includes: Show the second link; When the second link does not belong to the application, in response to the user clicking the second link, a second display interface is displayed, which is the display interface corresponding to the second link displayed in a browser or on a global wide area network web.

3. The method according to claim 1 or 2, characterized in that, Before displaying the first display interface, the method further includes: Based on the first information of the applications already installed in the first electronic device and the first link, it is determined that the target application is not installed in the first electronic device.

4. The method according to claim 3, characterized in that, The first link includes a first domain name, the first information includes the domain name of the installed application, and the step of determining that the target application is not installed in the first electronic device based on the first information of the application installed in the first electronic device and the first link includes: If the first domain name does not match the domain name of the installed application, it is determined that the target application is not installed in the first electronic device.

5. The method according to any one of claims 1-3, characterized in that, The first link includes a first domain name, and before displaying the first display interface, the method further includes: The first link is determined to belong to the target application based on the first domain name and the first correspondence relationship, wherein the first correspondence relationship is the correspondence between the application's second information and the domain name.

6. The method according to claim 5, characterized in that, The step of determining that the first link belongs to the target application based on the first domain name and the first correspondence includes: When the target application is matched from the first correspondence based on the first domain name, it is determined that the first link belongs to the target application.

7. The method according to claim 5 or 6, characterized in that, Before determining that the first link belongs to the target application based on the first domain name and the first correspondence, the method further includes: Send a first request message to the second electronic device, the first request message being used to obtain the first correspondence; Receive the first correspondence sent by the second electronic device.

8. The method according to any one of claims 5-7, characterized in that, The second information includes at least one of the following: the application's package name, the application's name, or the application's version number.

9. The method according to any one of claims 1-3, characterized in that, The first link includes a first domain name, and before displaying the first display interface, the method further includes: Send the first domain name to the third electronic device; Receive the second information of the target application corresponding to the first domain name sent by the third electronic device.

10. An electronic device, characterized in that, include: One or more processors; One or more memories; the one or more memories storing one or more programs that, when executed by one or more processors, cause the method as described in any one of claims 1-9 to be performed.

11. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface being used to receive signals and transmit the signals to the processor, the processor processing the signals such that the method as described in any one of claims 1-9 is executed.

12. A readable storage medium, characterized in that, The readable storage medium stores instructions that, when executed on an electronic device, cause the method as described in any one of claims 1-9 to be performed.

13. A program product, characterized in that, The program product includes program code that, when run on an electronic device, causes the method as described in any one of claims 1-9 to be performed.

Images