An application processing method and related apparatus

Abstract

This application discloses an application processing method and related apparatus. An electronic device displays a first link. If the electronic device determines that the first link is a lightweight application short link, it displays a first interface through the first lightweight application. If the electronic device determines that the first link is not a lightweight application short link, it displays a second interface through a browser application. In this way, after receiving a link from another device, the electronic device can detect whether the link is a lightweight application short link. When the electronic device determines that the link is a lightweight application short link, it can quickly jump to and display the interface corresponding to the lightweight application short link without going through a browser, allowing the electronic device to display the content of different applications more quickly.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an application processing method and related apparatus. Background Technology

[0002] Currently, with the diversification of applications (APPs), more and more users are accustomed to using APPs for online activities, such as shopping and social networking. To promote their applications, APP administrators often embed links to target interfaces within messages sent to electronic devices (e.g., SMS, emails). Upon receiving the link, the electronic device needs to parse it through a browser application to display a webpage introducing the target application. Only then can the user be redirected to and run the target application—a cumbersome and complex process. Therefore, how to enable electronic devices to quickly display content from different applications has become a pressing issue. Summary of the Invention

[0003] This application provides an application processing method and related apparatus, enabling electronic devices to quickly display content from different applications.

[0004] Firstly, this application provides an application processing method, including: displaying a first link; receiving a first input for the first link; if it is determined that the first link is a lightweight application short link, displaying a first interface through a first lightweight application; if it is determined that the first link is not a lightweight application short link, displaying a second interface through a browser application. In this way, the electronic device can determine whether the first link is a lightweight application short link, allowing it to quickly jump to and display the interface corresponding to the lightweight application short link without going through a browser when the first link is determined to be a lightweight application short link. This enables the electronic device to display the content of different applications more quickly, resulting in a better user experience. When the first link is not a lightweight application short link, the webpage corresponding to the first link can be displayed through a browser application.

[0005] In one possible implementation, displaying the first interface through a first lightweight application specifically includes: sending a first link to a server; receiving first information sent by the server, the first information including the package name of the first lightweight application and parameters of the first interface; running the first lightweight application based on its package name, and displaying the first interface through the first lightweight application based on the parameters of the first interface. In this way, when the electronic device determines that the first link is a short link to a lightweight application, it can obtain the first information corresponding to the first link from the server, enabling the electronic device to determine whether to run the first lightweight application based on its package name, and to determine whether to display the first interface based on its parameters. This achieves a better display effect, avoids displaying the browser's redirection interface used to display the first interface, and makes the operation smoother.

[0006] In one possible implementation, the electronic device does not have the first application installed. The first lightweight application is then run based on its package name. Specifically, this includes: installing the first lightweight application based on its package name; and running the first lightweight application after successful installation. In this way, even when the first lightweight application is not installed, the electronic device can directly install it based on its package name, achieving a silent installation effect. That is, the electronic device automatically installs the first lightweight application without user intervention, reducing redundant user operations.

[0007] In one possible implementation, before determining that the first link is a lightweight application short link, the method further includes: detecting that the first link includes a first domain name from the short link feature information; before determining that the first link is not a lightweight application short link, the method further includes: detecting that the first link does not include a first domain name. In this way, the electronic device can determine whether the first link is a lightweight application short link more quickly based on the domain name in the first link, without needing to send the first link to a server, thus saving processing time and displaying the first interface faster.

[0008] In one possible implementation, determining that the first link is a lightweight application short link specifically includes: detecting that the first link includes the first domain name in the short link feature information, and that the length of the first path in the first link is less than a preset length indicated by the short link feature information, thus determining that the first link is a lightweight application short link; determining that the first link is not a lightweight application short link specifically includes: detecting that the first link does not include the first domain name, or that the length of the first path in the first link is greater than a preset length, thus determining that the first link is not a lightweight application short link. In this way, the electronic device can determine whether the first link is another link provided by the server that is not a lightweight application short link based on the length of the first path.

[0009] In one possible implementation, before displaying the first interface through the first lightweight application after determining that the first link is a lightweight application short link, the method further includes: receiving short link feature information sent by the server. In this way, the server sends the short link feature information to the electronic device in advance, enabling the electronic device to determine whether the first link is a lightweight application short link based on the short link feature information.

[0010] In one possible implementation, if it is determined that the first link is not a lightweight application short link, a second interface is displayed through a browser application. Specifically, this includes: running the browser application; and displaying the second interface through the browser application based on the first link. The second interface includes a first control used to open a third interface of the second application. Thus, after the electronic device determines that the first link is not a lightweight application short link, it determines that the electronic device cannot directly display the corresponding interface based on the first link, runs the browser application, and displays the second interface used to open the third interface through the browser application.

[0011] In one possible implementation, the electronic device has a second application installed; the method further includes: receiving a second input to a first control; responding to the second input, running the second application based on a second link corresponding to the first control, and displaying a third interface through the second application based on the second link. Thus, when the first link is a short application link, the electronic device can jump to and display the third interface through the first control. If the electronic device does not have a second application installed, since the electronic device cannot silently install the second application and the user needs to install it manually, the electronic device displays the first control to help the user determine whether to perform subsequent jump operations, which is more in line with user habits.

[0012] In one possible implementation, before running a second application based on a second link corresponding to a first control in response to a second input, and before displaying a third interface through the second application based on the second link, the method further includes: sending a first link to a server via a browser application; receiving a second link sent by the server, the second link being used to display the third interface of the second application. In this way, the electronic device can obtain the second link from the server.

[0013] Secondly, this application provides an electronic device, including: a messaging application, an application runtime management module, and a short link parsing engine; wherein, the messaging application is used to display a first link; the messaging application is also used to send the first link to the application runtime management module after receiving a user's first input on the first link; the application runtime management module is used to send the first link to the short link parsing engine; the short link parsing engine is used to obtain first information corresponding to the first link from a server when it identifies the first link as a lightweight application short link, the first information being used to indicate the first interface of the first lightweight application; the short link parsing engine is used to send the first information to the application runtime management module; the application runtime management module is used to run the first lightweight application based on the first information; the first lightweight application is used to display the first interface based on the first information. In this way, the electronic device can receive and display the first link through the messaging application, run the application corresponding to the first link through the application runtime management module, and obtain the first information corresponding to the first link based on the short link parsing engine, thereby achieving the effect of determining whether the first link is a lightweight application short link and displaying the interface corresponding to the lightweight application short link. This allows the electronic device to quickly display the content of different applications, helping users see the first interface faster and providing users with a better display effect.

[0014] One possible implementation also includes a silent installation engine; specifically, an application runtime management module is used to send the first information to the silent installation engine; the silent installation engine is used to install the first lightweight application based on the first information; and the application runtime management module is used to run the first lightweight application after it is successfully installed and send the first information to the first lightweight application. In this way, even when the electronic device does not have the first lightweight application installed, it can install it through the silent installation engine, reducing user operations and providing a smoother user experience.

[0015] In one possible implementation, a browser application is also included. The short link parsing engine is further configured to notify the application runtime management module that the first link is not a lightweight application short link when it is identified that the first link is not a lightweight application short link. The application runtime management module then sends the first link to the browser application. The browser application displays a second interface based on the first link. Thus, when the electronic device determines that the first link is not a lightweight application short link through the short link parsing engine, it can display the second interface indicated by the first link through the browser application.

[0016] Thirdly, this application provides an electronic device, including: one or more processors and one or more memories and a transceiver; the transceiver, the one or more memories are coupled to one or more processors, the one or more memories are used to store a computer program, and when the one or more processors execute the computer program, they execute the application processing method in any of the possible implementations of the first aspect above.

[0017] Fourthly, embodiments of this application provide a computer storage medium for storing a computer program, which, when executed by a processor, implements the application processing method in any of the possible implementations of the first aspect described above.

[0018] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the application processing method in any of the possible implementations of the first aspect described above. Attached Figure Description

[0019] Figures 1A-1J A set of interface schematic diagrams provided for embodiments of this application;

[0020] Figure 2 A flowchart is provided for an embodiment of this application;

[0021] Figures 3A-3F Another set of interface schematic diagrams provided for embodiments of this application;

[0022] Figure 4 A flowchart illustrating an application processing method provided in an embodiment of this application;

[0023] Figure 5 A flowchart illustrating another application processing method provided in an embodiment of this application;

[0024] Figure 6 A schematic diagram of an interface provided for an embodiment of this application;

[0025] Figure 7 A schematic diagram of a hardware structure provided for an embodiment of this application;

[0026] Figure 8 This is a schematic diagram of a software architecture provided for an embodiment of this application. Detailed Implementation

[0027] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0028] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0029] In this embodiment, a lightweight application is a program that is installed and run by an electronic device after receiving input of an icon for a lightweight application. The size of a lightweight application is typically smaller than a preset size (e.g., 10MB).

[0030] An application is typically a program installed by an electronic device through an app store. An electronic device can install an application after receiving input from the user. After successful installation, the application's icon will appear on the desktop. The electronic device can also run the application after receiving input from the user for the application's icon. Alternatively, the electronic device can download the application's installation package after receiving input from the user for the installation package.

[0031] It's important to note that, compared to applications that require user installation, lightweight applications can be used without installation. They are more lightweight, occupy less storage space, open faster on first use, and typically do not consume excessive memory resources on electronic devices during operation. Lightweight applications are usually composed of a series of components and functional modules, providing different services and functions, such as online shopping, social entertainment, and lifestyle services. For example, electronic devices can display multiple lightweight applications on the negative one screen. Since electronic devices do not require user installation, they can provide users with the ability to directly trigger check-in functionality by clicking card components, tapping, or scanning, offering a smooth and seamless "use and go" experience. Some lightweight applications can also display key information such as flights, express deliveries, and schedules directly on the desktop and / or negative one screen in card form.

[0032] A deep link is a link used to trigger an electronic device to navigate from a redirecting webpage to a specified interface. Deep links include redirect deep links and install deep links. When the target application is already installed on the electronic device, a redirect deep link can be used to redirect the device to the target application's interface. When the target application is not installed on the electronic device, an install deep link can be used to redirect the device to the application's installation interface.

[0033] Short links are links shorter than a preset length (e.g., 200 bytes). Short links can be divided into application short links and lightweight application short links. Application short links are links generated by the short link server 200 that correspond to the target interface of the target application. The short link server 200 stores the correspondence between application short links, deep redirect links, and installation deep links. Application short links can serve as the URL of a redirected webpage, triggering the electronic device to display the redirected webpage through a browser application. The redirected webpage includes controls corresponding to the deep links, allowing the electronic device to display the interface corresponding to the deep link after receiving user input to the controls.

[0034] The lightweight application short link is generated by the short link server 200 and corresponds to the target interface of the target lightweight application. When an electronic device displays an interface including the lightweight application short link, the electronic device can be triggered to jump from the interface including the lightweight application short link to the target interface of the target lightweight application through the lightweight application short link.

[0035] In one possible implementation, the short link server 200 can be used to generate application short links corresponding to the target interface of the target application. After generating the application short links, the short link server 200 can store the correspondence between application short links, deep links, and installation deep links. The application short link can serve as the URL of a redirected webpage, used to trigger the electronic device to display the redirected webpage. The deep link can be used to trigger the electronic device to display the target interface. The installation deep link can be used to trigger the electronic device to display the installation interface, which can then be used to install the target application.

[0036] The short link server 200 can send application short links to multiple electronic devices (e.g., electronic device 100) through one or more applications. These applications may include, but are not limited to, communication applications such as messaging and email, instant messaging applications such as Wi-Fi, social networking applications such as microblogs, news and information applications, and so on.

[0037] After receiving and displaying an application short link through one or more applications, the electronic device 100 can receive user input for the application short link and obtain a deep redirect link and an installation deep link from the short link server 200 based on the application short link. The electronic device 100 can also display a redirect interface based on the application short link, the deep redirect link, and the installation deep link. The redirect interface may include, but is not limited to, a redirect webpage. The redirect webpage may include, but is not limited to, an open control and an install control. The redirect webpage can be used to prompt the user to jump to the interface displaying the target application. The open control can be used to trigger the electronic device 100 to display the target interface based on the deep redirect link if the application corresponding to the application short link is already installed on the electronic device 100. The install control can be used to trigger the electronic device 100 to display the installation interface based on the installation deep link if the application corresponding to the application short link is not installed on the electronic device 100. The installation interface can be an interface provided by an application used by the electronic device 100 to download and install new applications (e.g., an application gallery, AG), or an interface provided by the browser application of the electronic device 100, etc.

[0038] It should be noted that the method is not limited to the short link server 200 sending application short links to multiple electronic devices (including electronic device 100) through one or more applications. After the short link server 200 generates the application short link, users can share the application short link through different applications. For example, the application short link can be included in published comments, articles, microblogs, WeChat Moments, blogs, etc., and this application embodiment does not limit this. In this way, when users of electronic device 100 browse content such as comments carrying application short links, they can trigger electronic device 100 to jump to display the target interface through the application short link. Alternatively, after the short link server 200 generates the application short link, the administrator of the target application can send the application short link to multiple electronic devices through one or more applications (e.g., a messaging application). Alternatively, the server of the target application can send the application short link to multiple electronic devices through one or more applications, etc., and this application embodiment does not limit this.

[0039] In other examples, the redirect interface may include an open control. When the application corresponding to the application link is already installed, the electronic device 100 can receive user input for the open control and display the target interface based on a deep redirect link. When the application corresponding to the application link is not installed, the electronic device 100 can receive user input for the open control and display the installation interface described above based on an installation deep redirect link.

[0040] In this way, developers can configure a specific interface of their application through the short link server 200 to generate a corresponding application short link. When the application short link is delivered to the electronic device 100 through one or more channels, and the electronic device 100 receives user input for the application short link, its application for displaying web pages (e.g., a browser application) can display a redirect interface introducing the target application. Subsequently, if the target application is installed on the electronic device 100, the user can trigger the electronic device 100 to redirect and display the target interface using the open control on the redirect interface.

[0041] The following section uses an e-commerce application as an example to illustrate the interface diagrams provided in the embodiments of this application.

[0042] For example, such as Figure 1A As shown, the electronic device 100 displays a desktop 11. The desktop 11 may include multiple application icons (e.g., an app store icon, a browser icon, etc.). The app store icon can be used to trigger the display of the app store application interface. The browser icon can be used to trigger the display of the browser application interface. Optionally, a status bar including icons such as a time indicator icon may be displayed at the top of the desktop 11. Optionally, multiple tray icons (e.g., a dialer icon, a messaging icon, a contacts icon, and a camera icon) may be displayed below the multiple application icons.

[0043] Short link server 200 generates the interface 47 of e-commerce application 15 (not shown in the figure) (e.g.) Figure 1J The application short link 16 corresponds to the one shown. The short link server 200 stores the correspondence between the application short link 16, the installation deep link 17, and the jump deep link 18. The short link server 200 can send the application short link 16 to one or more electronic devices through the information application's server. These one or more electronic devices include electronic device 100. It is understood that the short link server 200 sending the application short link 16 through the information application is merely an example and should not constitute a specific limitation.

[0044] After receiving a short message including the application short link 16 through the information application, the electronic device 100 can display as follows: Figure 1B Window 12 is shown. (As shown) Figure 1BAs shown, window 12 can be used to notify the user that the information application has received a new message. For example, window 12 may include, but is not limited to, identification information 12A and summary information 12B. Identification information 12A can be used to indicate the source of the new message to the user. This identification information 12A may include, but is not limited to, the identifier of the e-commerce application 15. For example, identification information 12A could be: "E-commerce". Summary information 12B can be used to indicate the specific content of the new message to the user. This summary information 12B may include, but is not limited to, part or all of the content of a short message. For example, summary information 12B could be: "[E-commerce] Today's milk special..."

[0045] The electronic device 100 can, in response to user input (e.g., a click) to the window 12, display something like... Figure 1C Interface 21 is shown. (As shown) Figure 1C As shown, interface 21 may include, but is not limited to, message box 22, which contains the entire content of the short message. Message box 22 includes application short link 16.

[0046] The electronic device 100 can, upon receiving user input (e.g., a click) to the application link 16, respond to that input by displaying, as shown below. Figure 1D Window 24 is shown. (As shown) Figure 1D As shown, window 24 may include one or more options. These options may include, but are not limited to, the "Open URL" option 25.

[0047] The electronic device 100 can, upon receiving user input (e.g., a click) for the "Open URL" option 25, respond to that input by displaying, as shown below. Figure 1E The interface 31 shown is as follows. In this interface 31, the electronic device 100 can run a browser application in response to the user's input of the "Open URL" option 25. The browser application of the electronic device 100 can display interface 31 based on the application link 16.

[0048] like Figure 1E As shown, interface 31 may include webpage 33. Webpage 33 includes an open control 32. Optionally, interface 31 may also include, but is not limited to, an address bar, which can be used to display the URL of webpage 33. Electronic device 100 can use application short link 16 as the URL, so that browser application can obtain and display webpage 33 based on the URL. Optionally, webpage 33 may also include, but is not limited to, the logo, icon, and / or content of interface 47 of the e-commerce application corresponding to application short link 16.

[0049] Upon receiving user input to open control 32, electronic device 100 can respond to the input by running the e-commerce application 15 via deep link 18. However, since e-commerce application 15 is not installed on electronic device 100, running e-commerce application 15 fails. Electronic device 100 can then use deep link 17 to access the application market and display applications as shown below. Figure 1F The interface shown is 41.

[0050] like Figure 1F As shown, interface 41 can be used to install the e-commerce application 15. Interface 41 may include, but is not limited to, the installation control 42. Optionally, interface 41 may also include, but is not limited to, content used to introduce the e-commerce application 15, etc.

[0051] After receiving user input on the installation control 42, the electronic device 100 can respond to the input by displaying, as shown in the image. Figure 1G Control 43 is shown. (Example) Figure 1G As shown, control 43 can be used to trigger electronic device 100 to stop installing the store application 15. Optionally, control 43 can also be used to prompt the user about the progress of electronic device 100 installing the store application 15.

[0052] After successfully installing the e-commerce application 15, electronic device 100 can display the following: Figure 1H The open control 44 is shown. Upon receiving user input to the open control 44, the electronic device 100 can respond to the input by displaying, as shown... Figure 1I The interface shown is 45.

[0053] like Figure 1I As shown, interface 45 is the interface provided by the e-commerce application 15 (which can be called the homepage of e-commerce application 15). Interface 45 is different from interface 47 corresponding to application short link 16. Interface 45 includes "Smart Office" control 46.

[0054] After receiving input from the user into the "Smart Office" control 46, the electronic device 100 can respond to the input by displaying, as shown below. Figure 1J Interface 47 is shown. Interface 47 is the interface corresponding to application short link 16. It should be noted that the above interface description is only an example and should not constitute a specific limitation on the interface of the embodiments of this application. It can be understood that if the electronic device 100 has installed the e-commerce application 15, the electronic device 100 can respond to the user's request. Figure 1E The input of the open control 32 shown above, based on the deep link 18, runs the e-commerce application 15, and through the e-commerce application 15, based on the deep link 18, displays as shown above. Figure 1J The interface shown is 47.

[0055] In this way, after receiving the user's input for the application shortcut 16, the operating system of the electronic device 100 can run a browser application and display the redirect interface 31 through the browser application. The electronic device 100 can also receive the user's input for the open control 32 and redirect to display the interface 41 for installing the e-commerce application 15. Afterwards, the user needs to manually operate the electronic device 100 to install the e-commerce application 15 and manually open the interface 47 corresponding to the application shortcut 16, which is very cumbersome, and the user is highly likely to abandon browsing interface 47.

[0056] The following is a flowchart provided by an embodiment of this application.

[0057] For example, such as Figure 2 As shown, the electronic device 100 may include, but is not limited to, an information application 51, an application operation management module 52, a browser application 53, and an application market application 55. The application operation management module 52 can be used to launch applications. The application market application 55 can be used to download and install applications. The short link server 200 generates an application short link 262 corresponding to the interface 261 of a specified application 54. The electronic device 100 processes the application short link 262 including the following steps:

[0058] S201. Short link server 200 receives the input configuration information.

[0059] S202. Based on the configuration information, the short link server 200 generates an application short link 262 corresponding to the interface 261 of the specified application 54, and stores the correspondence between the application short link 262, the deep link 264, and the deep link 265.

[0060] The short link server 200 can receive configuration information from the administrator of the specified application 54 and generate an application short link 262. The domain names of the application short links generated by the short link server 200 are the same, and they can point to the short link server 200. The configuration information may include, but is not limited to, a deep link 264 pointing to interface 261 and an installation deep link 265 pointing to the specified application 54. After generating the application short link 262, the short link server 200 can store the correspondence between the application short link 262, the deep link 264, and the installation deep link 265. Here, the target application corresponding to the application short link 262 is the specified application 54, and the target interface corresponding to the application short link 262 is interface 261. In some examples, interface 261 may include a webpage in Hypertext Markup Language (HTML) 5 format, and the application short link 262 is the URL of that webpage.

[0061] S203. The short link server 200 sends the application short link 262 to the information application 51 of the electronic device 100.

[0062] After the short link server 200 generates the application short link 262, the short link server 200, the server of the designated application 54, or the server of one or more applications can receive input and send the application short link 262 to multiple electronic devices, including electronic device 100, through various channels. Specifically, please refer to the above embodiments, which will not be repeated here. In this embodiment, the information carrying the application short link 262 can be called a link carrier, such as a text message or a webpage. Electronic devices receiving the application short link 262 can use a browser application to parse the application link and redirect to the display interface 261, etc. For example, the short link server 200 can send the application short link 262 to electronic device 100 through the server of information application 51.

[0063] S204. Information Application 51 Display Application Short Link 262.

[0064] Specifically, after receiving the application short link 262, the information application 51 of the electronic device 100 can display the application short link 262. For details, please refer to... Figure 1B and Figure 1C The embodiments shown are not described in detail here.

[0065] S205. Information application 51 receives input to application short link 262.

[0066] S206. Information application 51 sends application short link 262 to application operation management module 52.

[0067] S207. In response to the application short link 262, the application runtime management module 52 runs the browser application 53 and sends the application short link 262 to the browser application 53.

[0068] S208. Browser application 53 sends application short link 262 to short link server 200.

[0069] After receiving the application short link 262, the browser application 53 can send the application short link 262 to the short link server 200.

[0070] S209. The short link server 200, based on the application short link 262, determines the deep link to jump to 264 and the deep link to install 265.

[0071] After receiving the application short link 262, the short link server 200 can determine the corresponding deep link 264 and the installation deep link 265 based on the application short link 262.

[0072] S210. Short link server 200 sends deep link 264 and deep link installation 265 to browser application 53.

[0073] S211. Browser application 53 displays a redirect interface based on application short link 262, deep redirect link 264, and installation deep link 265. The redirect interface includes an open control.

[0074] In this way, when the user of the electronic device 100 clicks on the application short link 262 in the link carrier, the application operation management module 52 of the electronic device 100 can run the browser application 53 and load the application short link 262 through the browser application 53 to display the jump interface.

[0075] S212. Browser application 53 receives input for opening the control.

[0076] For example, using short chains 262 Figure 1C When the application short link 16 is shown, the control can be opened. Figure 1E The open control 32 is shown.

[0077] In other examples, information application 51 may display a jump interface based on application short link 16. For details, please refer to the embodiment of browser application 53 displaying a jump interface, which will not be repeated here.

[0078] S213. Browser application 53 sends the deep link 264 and the deep link 265 to application runtime management module 52.

[0079] The browser application 53 can respond to input to the open control by sending the deep link 264 to the deep link 265 to the application runtime management module 52.

[0080] Case 1: After the browser application 53 sends the deep link 264 and the deep link 265 to the application runtime management module 52, when the electronic device 100 has the specified application 54 installed, the electronic device 100 can execute steps S214 and S215.

[0081] Scenario 2: After the browser application 53 sends the deep link 264 and the deep link 265 to the application runtime management module 52, if the electronic device 100 has not installed the specified application 54, the electronic device 100 can execute steps S216 to S218.

[0082] S214. The application operation management module 52 opens the specified application 54 based on the jump deep link 264 and sends the jump deep link 264 to the specified application 54.

[0083] The application runtime management module 52 can run a specified application 54 based on the jump depth link 264. After successfully running the specified application 54, the application runtime management module 52 can send the jump depth link 264 to the specified application 54.

[0084] S215. The specified application 54 displays the interface 261 based on the deep link 264.

[0085] After receiving the deep link 264, the specified application 54 can parse the deep link 264 and determine the interface 261 corresponding to the deep link 264. The specified application 54 can then display the interface 261. For example, the application short link 262 is... Figure 1C When the application short link 16 is shown, the specified application 54 can be the aforementioned e-commerce application 16. Interface 261 can be... Figure 1J The interface shown is 47.

[0086] S216. Application runtime management module 52 failed to open the specified application 54 based on deep link 264.

[0087] S217. The application operation management module 52, based on the installation of Deep Link 265, opens the application market application 55 and sends the installation of Deep Link 265 to the application market application 55.

[0088] The application runtime management module 52 can run the application market application 55 based on the installed DeepLink 265. After successfully running the application market application 55, the application runtime management module 52 can send the installed DeepLink 265 to the application market application 55.

[0089] S218. Application Market Application 55 is based on installation depth link 265, displaying the installation interface for installing the specified application 54.

[0090] After receiving the installation deep link 265, application market application 55 can parse the installation deep link 265 and determine the corresponding installation interface. Application market application 55 can then display the installation interface. For example, application short link 262 is... Figure 1C When the application is short link 16 as shown, the installation interface can be... Figure 1F The interface shown is 41.

[0091] In this system, after the electronic device 100 displays the installation interface, it can receive input from the user to install a specified application 54 and install the specified application 54. After the electronic device 100 successfully installs the specified application 54, it can receive input from the user to open the specified application 54 and display the interface of the specified application 54 in response to the input. Subsequently, the electronic device 100 can receive input from the user to switch interfaces 261 and display interface 261 in response to the input. Alternatively, after the electronic device 100 successfully installs the specified application 54, it can receive input from the user regarding the application link 262 and display interface 51 in response to the input. For details, please refer to the above embodiments.

[0092] It should also be noted that, not limited to application market application 55, electronic device 100 can also download the installation package of specified application 54 through browser application 53. After that, electronic device 100 can install specified application 54 based on the installation package. This application embodiment does not limit this.

[0093] In the above example, the steps required for electronic device 100 to receive user input for the application link and redirect to display the target interface are cumbersome, and it also needs to go through a browser application / web page in between to display the target interface, resulting in a choppy experience.

[0094] Furthermore, if the electronic device 100 does not have the target application corresponding to the application link installed, after displaying the installation interface, the electronic device 100 needs to receive input from the user to install the target application and then install it. Afterwards, upon receiving input from the user for the application link, the electronic device 100 displays a redirect interface, and only after receiving input from the user for the open control can it display the target interface. Alternatively, the electronic device 100 may require the user to manually open the target application and trigger the display of the target interface; it cannot directly redirect to the target interface, and there is a high probability that the user will abandon triggering the display of the target interface midway.

[0095] This application provides an application processing method. A short link server 200 can generate a short link corresponding to the interface of a lightweight application (also known as a quick app, meta-service application, etc.) based on received lightweight application information. The lightweight application is smaller than a preset size (e.g., 10MB). When the electronic device 100 receives input from a user to open the lightweight application, it automatically installs and opens the lightweight application. The lightweight application information may include, but is not limited to, the package name of the lightweight application, parameters indicating the interface of the lightweight application (e.g., the storage path of the interface), etc. The short link server 200 can store the correspondence between the lightweight application short links and the lightweight application information. One or more electronic devices (including electronic device 100) can receive lightweight application short links through one or more applications.

[0096] After receiving a lightweight application short link, electronic device 100 can display the lightweight application short link. Upon receiving input for a lightweight application short link, electronic device 100 can retrieve the corresponding lightweight application information from the short link server 200 based on the lightweight application short link. When electronic device 100 has not installed the lightweight application corresponding to the lightweight application short link, it can install the lightweight application based on the lightweight application information, and after successful installation, display the interface corresponding to the lightweight application short link through that lightweight application.

[0097] It should be noted that after receiving user input (e.g., a click) for a link other than a lightweight application short link, electronic device 100 can send the link to short link server 200. Short link server 200 can notify electronic device 100 that the link is not a lightweight application short link if it determines that no lightweight application information corresponding to the link exists. Electronic device 100 can run a browser application and display the webpage corresponding to the link through the browser application.

[0098] In this way, after receiving a link from another device, the electronic device 100 can detect whether the link is a lightweight application short link through the short link server 200. When the electronic device 100 determines that the link is a lightweight application short link, it can quickly jump to and display the interface corresponding to the lightweight application short link without going through a browser / web page.

[0099] In some examples, the lightweight application short link generated by the short link server 200 includes domain name information and path information. The domain name information is used to indicate the short link server 200, and the path information is used to indicate the storage path of the redirected webpage. The short link server 200 can generate short link feature information and send the short link feature information to one or more electronic devices (including electronic device 100). The short link feature information includes domain name information and path matching rules. The domain name information is the domain name of the lightweight application short link generated by the short link server 200. The path matching rules may include, but are not limited to, the path length of the lightweight application short link not exceeding a preset length (e.g., 200 bytes), and / or, the lightweight application short link not including specified characters (e.g., specified characters may include characters other than numbers, letters, and forward slashes). After receiving a link sent by another device, electronic device 100 can determine whether the link is a lightweight application short link based on the short link feature information. When electronic device 100 determines that a link is a lightweight application short link, it can display the interface corresponding to the lightweight application short link based on the lightweight application information corresponding to the short link server 200. When electronic device 100 determines that the link is not a lightweight application short link, it can display the webpage indicated by the link through a browser application. The short link server 200 can receive and store specified input characters. Since the domain names of the lightweight application short links generated by the short link server 200 are all the same, electronic device 100 can automatically determine whether a link clicked by a user is a lightweight application short link based on the short link characteristic information, facilitating faster execution of the corresponding operation.

[0100] It should be noted that electronic devices that lack the ability to access lightweight application information can display a redirect interface via a browser application based on a short link to the lightweight application. Therefore, when users use electronic devices without this capability, they can only access the interface corresponding to the short link to the lightweight application through a redirect interface, which is cumbersome.

[0101] The following section presents a set of interface diagrams provided in the embodiments of this application.

[0102] For example, after receiving the lightweight application information 302 of the target lightweight application, the short link server 200 can generate a link 301 corresponding to the target interface of the target lightweight application. The short link server 200 can store the correspondence between the link 301 and the lightweight application information 302. The short link server 200 or the server of the target lightweight application can receive input and send the link 301 to one or more electronic devices.

[0103] Electronic device 100 displays such as Figure 1A Interface 11 is shown. Electronic device 100 can display, after receiving an application link via an information application, the following interface... Figure 3A Window 305 is shown. (As shown) Figure 3A As shown, window 305 can be used to notify the user that an information application has received a new message. For example, window 305 may include, but is not limited to, identification information 305A and summary information 305B. Identification information 305A can be used to indicate the source of the new message to the user. This identification information 305A may include, but is not limited to, the identifier of the target lightweight application. For example, identification information 305A could be: "XX Health". Summary information 305B can be used to indicate the specific content of the new message to the user. This summary information 305B may include, but is not limited to, part or all of the content of a short message. For example, summary information 305B could be: "[XX Health] Get a 50 yuan exclusive offer..."

[0104] The electronic device 100 can, in response to user input (e.g., a click) to the window 305, display something like... Figure 3B The interface shown is 311. (As shown) Figure 3B As shown, interface 311 may include, but is not limited to, information box 312, which includes the entire content of the short message. Information box 312 includes link 301. Interface 311 may also include information box 313, which includes link 314. It should be noted that the link 301 is not limited to being displayed in text form; the electronic device 100 may also display the link 301 in the form of images, videos, etc. This application embodiment does not limit this.

[0105] The electronic device 100 can, upon receiving user input (e.g., a click) on the link 301, respond to that input by displaying, as shown below. Figure 3C Window 321 is shown. (As shown) Figure 3C As shown, window 321 may include one or more options. These options may include, but are not limited to, the "Open URL" option 322.

[0106] Upon receiving user input (e.g., a click) for the "Open URL" option 322, electronic device 100, in response to this input, determines whether link 301 is a lightweight application short link based on short link feature information. For example, short link feature information includes the domain name "short.link" and path matching rules: the path length of a lightweight short link application is less than a preset length and does not include specified characters. Electronic device 100 detects that the domain name of link 301 is the same as the domain name in the short link feature information, and link 301 meets the path matching rules, thus determining that link 301 is a lightweight application short link. Electronic device 100 can then obtain the corresponding lightweight application information 302 from the short link server 200 based on link 301. Based on the lightweight application information 302, electronic device 100 can display, for example... Figure 3D The interface shown is 341.

[0107] It should be noted that when the electronic device displays 100, such as Figure 3D Before the interface 341 shown, if the electronic device 100 does not have the target lightweight application installed, the electronic device 100 can install the target lightweight application based on the lightweight application information 302, and run the target lightweight application upon successful installation. The electronic device 100 can then display the following based on the lightweight application information 302: Figure 3D The interface shown is 341.

[0108] In other examples, electronic device 100 may, upon receiving user input (e.g., a click) on link 301, display, in response to that input, such as... Figure 3D The interface 341 is shown. For details, please refer to the above embodiments, which will not be repeated here. In this way, when the electronic device 100 detects that a user has clicked link 301, it tends to assume that the user wants to trigger the electronic device 100 to display the target interface corresponding to link 301, eliminating the need for the user to select the "Open URL" option 322, thus simplifying the operation steps.

[0109] In this way, when the electronic device 100 displays a lightweight application link, it can directly display the corresponding interface based on the lightweight application information without needing to access a browser or other applications to redirect to a separate interface, making the operation simpler. Furthermore, even if the lightweight application corresponding to the lightweight application link is not installed, the electronic device 100 can install the lightweight application without requiring manual user intervention, and then redirect to display the interface corresponding to the lightweight application link through the installed application, providing a more convenient user experience and reducing the probability of users abandoning access to the interface corresponding to the lightweight application link.

[0110] For example, electronic device 100 displays as follows Figure 3B The interface 311 is shown. Upon receiving user input on link 314, the electronic device 100 can, in response to that input, display as shown... Figure 3E Window 351 is shown. (As shown) Figure 3E As shown, window 351 may include one or more options. These options may include, but are not limited to, the "Open URL" option 352.

[0111] Electronic device 100 can receive user input Figure 3E Upon input (e.g., clicking) of the "Open URL" option 352, the system responds to this input and determines whether link 314 is a lightweight application short link based on short link feature information. For example, short link feature information includes the domain name "short.link" and path matching rules: the path length of a lightweight short link application is less than a preset length and does not include specified characters. The electronic device 100 detects that the domain name of link 314 is different from the domain name in the short link feature information and determines that link 314 is not a lightweight application short link. The electronic device 100 can run a browser application. The electronic device 100 can display, based on link 314, the following information through the browser application: Figure 3F The interface shown is 361.

[0112] In this way, when the electronic device 100 determines that the link clicked by the user is not a lightweight application short link, it can run a browser application and access the webpage indicated by the link through the browser application.

[0113] For example, such as Figure 4 As shown, the application processing method provided in this application embodiment includes the following steps:

[0114] S401. Electronic device 100 displays that there is a first link, and electronic device 100 receives input for the first link.

[0115] The electronic device 100 can display the first link after receiving it. Upon receiving user input for the first link, the electronic device 100 can execute step S402 in response to that input. The application used to display the first link can be referred to as a messaging application (e.g., the aforementioned information application). It should be noted that when the first link is a lightweight application short link, the electronic device 100 can receive the lightweight application short link through one or more applications. For details, please refer to the description of the electronic device 100 receiving application short links above, which will not be repeated here.

[0116] S402. Electronic device 100 detects whether the first link is a lightweight application short link.

[0117] After receiving input from the user for the first link, the electronic device 100 can, in response to the input, execute step S403 if it detects that the first link is a lightweight application short link. If the electronic device 100 detects that the first link is not a lightweight application short link, it can execute step S406.

[0118] The electronic device 100 can receive short link feature information sent by the short link server 200 and determine whether the first link is a lightweight application short link based on the short link feature information. The short link feature information may include, but is not limited to, domain name information, where the domain name is the domain name of the lightweight application short link generated by the short link server 200. The electronic device 100 can determine that the first link is a lightweight application link when it detects that the first link includes domain name information. The electronic device 100 can determine that the first link is not a lightweight application link when it detects that the first link does not include domain name information. In this way, the electronic device 100 can determine whether the first link is a lightweight application link more quickly in most cases.

[0119] In some examples, short link characteristic information may include, but is not limited to, domain name information and path matching rules. Path matching rules may include, but are not limited to, the path length of a lightweight application short link not exceeding a preset length. Electronic device 100 can determine that the first link is a lightweight application short link when it detects that the first link includes domain name information and that the first link conforms to the path matching rules (i.e., the path length of the first link does not exceed the preset length). Electronic device 100 can determine that the first link is not a lightweight application short link when it detects that the first link does not include domain name information, or that the first link does not conform to the path matching rules (i.e., the path length of the first link does not exceed the preset length). In this way, electronic device 100 can avoid identifying a link generated by short link server 200 for accessing a webpage as a lightweight application short link.

[0120] Optionally, the path matching rules may also include rules that lightweight application short links do not include specified characters. Electronic device 100 may determine that the first link conforms to the path matching rules when it detects that the path length of the first link does not exceed a preset length and the first link does not include the specified characters. Electronic device 100 may determine that the first link does not conform to the path matching rules when it detects that the path length of the first link exceeds a preset length or the first link includes the specified characters.

[0121] For example, if the short link feature information includes domain name 1 and path matching rules, the electronic device 100 can determine that the first link is a lightweight application short link when it detects that domain name 1 exists in the first link and the path of the first link matches the path matching rules. The electronic device 100 can also determine that the first link is not a lightweight application short link when it detects that domain name 1 does not exist in the first link, or when the path of the first link matches the path matching rules.

[0122] It should be noted that after detecting that the first link is a lightweight application short link, if the electronic device 100 fails to obtain the corresponding lightweight application information through the short link server 200, the electronic device 100 can run a browser application and display the corresponding webpage based on the first link through the browser application.

[0123] In some examples, the short link server 200 can update at preset intervals (e.g., every day), or it can update the short link feature information after updating it, or it can send the short link feature information to one or more electronic devices. In this way, the short link server 200 can update the stored short link feature information, making it easier for one or more electronic devices to determine whether a link is a lightweight application short link based on the short link feature information.

[0124] It should be noted that, not limited to the aforementioned short link feature information, the short link server 200 can also determine short link feature information based on one or more lightweight application short links. The short link server 200 can send the short link feature information to one or more electronic devices (including electronic device 100). For example, the short link server 200 can obtain the feature information of a lightweight application short link when generating it. The short link server 200 can determine whether the stored short link feature information includes the feature information of the lightweight application short link. If the short link server 200 determines that the stored short link feature information does not include the feature information of the lightweight application short link, it can store the feature information of the lightweight application short link as short link feature information; this embodiment does not limit this.

[0125] In other examples, the lightweight application short links generated by the short link server 200 include domain name information and identification information. The domain name information can be used to identify the short link server 200, and the identification information can be used to distinguish different lightweight application short links. The identification information for different lightweight application short links generated by the short link server 200 is different. For example, the identification information can be a random string of a preset length. Optionally, the random string does not include specified characters. Thus, the electronic device 100 can determine whether a link is a lightweight application short link based on the short link feature information, domain name information, and identification information. The description of identifying whether a link is a lightweight application short link based on the identification information can be found in the above description of identifying whether a link is a lightweight application short link through path information, and will not be repeated here.

[0126] S403. Electronic device 100 determines the first lightweight application information corresponding to the first link.

[0127] When the electronic device 100 determines that the first link is a lightweight application short link, it sends the first link to the short link server 200. The short link server 200 can determine the first lightweight application information corresponding to the first link from the stored correspondence between lightweight application short links and lightweight application information, and send the first lightweight application information to the electronic device 100.

[0128] In other examples, the short link server 200 can send the mapping between lightweight application short links and lightweight application information to one or more electronic devices (including electronic device 100). Electronic device 100 can determine the first lightweight application information corresponding to the first link based on the mapping between the lightweight application short links and the lightweight application information. In this way, electronic device 100 can determine the corresponding lightweight application information more quickly without going through the short link server 200.

[0129] S404. If the electronic device 100 does not have the first lightweight application corresponding to the first link installed, the electronic device 100 installs the first lightweight application based on the first lightweight application information.

[0130] S405. After the electronic device 100 successfully installs the first lightweight application, it displays the first interface of the first lightweight application based on the information of the first lightweight application.

[0131] After receiving the first lightweight application information, the electronic device 100 can install the first lightweight application based on the first lightweight application information. After determining that the electronic device 100 has already installed the first lightweight application or after the electronic device 100 has successfully installed the first lightweight application, the first interface can be displayed through the first lightweight application based on the first lightweight application information.

[0132] For example, after receiving the first lightweight application information, the electronic device 100 can attempt to install the first lightweight application based on the package name of the lightweight application in the first lightweight application information. When the electronic device 100 has already installed the first lightweight application, the electronic device 100 determines that the first lightweight application is installed and runs the first lightweight application based on the first lightweight application information. The electronic device 100 can display the first interface of the first lightweight application based on the parameters in the first lightweight application information. When the electronic device 100 has not installed the first lightweight application, the electronic device 100 installs the first lightweight application. After successfully installing the first lightweight application, the electronic device 100 can run the first lightweight application and then display the first interface of the first lightweight application based on the parameters in the first lightweight application information.

[0133] In other examples, electronic device 100 may attempt to run a first lightweight application. If electronic device 100 successfully runs the first lightweight application, it may display the first interface of the first lightweight application. If electronic device 100 fails to run the first lightweight application, it may install the first lightweight application. In this way, electronic device 100 can run the first lightweight application faster even if it is already installed.

[0134] S406. Electronic device 100 displays a second interface indicated by a first link via a browser application.

[0135] When the electronic device 100 determines that the first link is not a lightweight application short link, it can run a browser application and parse the first link through the browser application to display the second interface indicated by the first link.

[0136] In this way, after receiving the user's input to select the first link, the electronic device 100 intercepts the first link before sending it to the browser application. The electronic device 100 can then... Figure 4 The steps shown complete the processing of different links, allowing the electronic device 100 to directly display the interface corresponding to the lightweight application short link without displaying a jump interface. This makes the jump process smoother, displays the interface that the user wants to view faster, and makes it easier to see the content of different applications.

[0137] The following is a flowchart illustrating the application processing method provided in the embodiments of this application.

[0138] For example, such as Figure 5As shown, the electronic device 100 may include, but is not limited to, an information application 51, an application runtime management module 52, a short link parsing engine 57, and a silent installation engine 58. The information application 51 can be used to receive and display links. The application runtime management module 52 can be used to launch applications. The short link parsing engine 57 can be used to determine whether a link is a lightweight application short link, and can also be used to obtain lightweight application information corresponding to the lightweight application short link. The silent installation engine 58 can be used to install lightweight applications. The application processing method includes the following steps:

[0139] S501. Short Link Server 200 generates short link feature information.

[0140] S502. The short link server 200 sends the short link feature information to the short link parsing engine 57.

[0141] The short link server 200 can send short link feature information to the short link parsing engine 57 of one or more electronic devices, including electronic device 100.

[0142] S503. Electronic device 100 receives input lightweight application information 61, which points to the interface 62 of lightweight application 56.

[0143] S504. The short link server 200 generates a link 63 based on the lightweight application information 61, and stores the correspondence between the link 63 and the lightweight application information 61.

[0144] The short link server 200 can receive lightweight application information 61 input by the administrator of the lightweight application and generate a link 63. The lightweight application information 61 is used to trigger the electronic device to display the interface 62 of the lightweight application 56. After generating the link 63, the short link server 200 can save the correspondence between the link 63 and the lightweight application information 61.

[0145] S505. Short link server 200 sends link 63 to information application 51.

[0146] The short link server 200 can send link 63 to one or more electronic devices, including electronic device 100, via messaging application 51. It is understood that the electronic device 100 receiving link 63 via messaging application 51 is merely an example; electronic device 100 can also receive link 63 via other applications. For details, please refer to the description of receiving application short links above, which will not be repeated here.

[0147] S506. Information Application 51 Display Link 63.

[0148] Information application 51 can display link 63 after receiving it; for example, see [link to example]. Figure 3B The illustrated embodiment.

[0149] S507. Information application 51 receives input to link 63.

[0150] S508. Information application 51 sends link 63 to application operation management module 52.

[0151] After receiving input for link 63, information application 51 can respond to the input by sending link 63 to application operation management module 52.

[0152] S509. The application runtime management module 52 can send link 63 to the short link parsing engine 57.

[0153] After receiving the link 63 sent by the information application 51, the application operation management module 52 can send the link 63 to the short link parsing engine 57.

[0154] The S510 short link parsing engine 57 can determine that link 63 is a lightweight application short link based on short link feature information.

[0155] After receiving link 63 from application runtime management module 52, short link parsing engine 57 can determine whether link 63 is a lightweight application short link based on short link feature information. When short link parsing engine 57 determines that link 63 is a lightweight application short link, it can execute step S511.

[0156] Understandably, when the short link parsing engine 57 determines, based on short link characteristic information, that link 63 is not a lightweight application short link, it can notify the application runtime management module 52 that link 63 is not a lightweight application short link. Upon determining that link 63 is not a lightweight application short link, the application runtime management module 52 can run the browser application and send link 63 to the browser application. The browser application can then parse link 63 and display the webpage indicated by link 63.

[0157] S511. The short link parsing engine 57 can send link 63 to the short link server 200.

[0158] The short link parsing engine 57 determines that link 63 is a lightweight application short link and can send link 63 to the short link server 200.

[0159] S512. The short link server 200 can determine the corresponding lightweight application information 61 based on the link 63.

[0160] The short link server 200 can determine the lightweight application information 61 corresponding to link 63 from the stored correspondence between lightweight application short links and lightweight application information.

[0161] S513. The short link server 200 can send lightweight application information 61 to the short link parsing engine 57.

[0162] After determining the lightweight application information 61, the short link server 200 can send the lightweight application information 61 to the short link parsing engine 57.

[0163] S514. The short link parsing engine 57 sends lightweight application information 61 to the application runtime management module 52.

[0164] After receiving the lightweight application information 61 sent by the short link server 200, the short link parsing engine 57 can send the lightweight application information 61 to the application runtime management module 52.

[0165] S515. The application runtime management module 52 can send lightweight application information 61 to the silent installation engine 58.

[0166] After receiving the lightweight application information 61 sent by the short link parsing engine 57, the application runtime management module 52 can send the lightweight application information 61 to the silent installation engine 58.

[0167] S516. Silently install engine 58 based on lightweight application information 61, install lightweight application 56.

[0168] After receiving the lightweight application information 61, the silent installation engine 58 can download the data of the lightweight application 56 from the server that manages the lightweight applications based on the lightweight application information 61, and then install the lightweight application 56.

[0169] In this embodiment, the silent installation engine 58 can be used to silently install lightweight applications. "Silent installation" can be understood as an installation behavior that is imperceptible to the user. That is, the silent installation engine 58 can automatically install lightweight applications without receiving user input. During the installation process, the electronic device 100 will not display any prompts indicating that the electronic device 100 is installing a lightweight application. Thus, the lightweight application is small in size, the installation time is short, no prompts are displayed, and no user intervention is required. The entire installation process is silent and seamless, reducing the number of user operations and providing a simpler installation experience.

[0170] It should be noted that when the electronic device 100 already has a lightweight application installed, the silent installation engine 58 can send a message to the application runtime management module 52 indicating that the lightweight application has been installed after receiving the lightweight application information 61. In some examples, this message can be an installation success message. In this way, the electronic device 100 can install the lightweight application 56 faster through the silent installation engine 58 even when the lightweight application is not installed, and display the interface 62 of the unused lightweight application 56 faster.

[0171] In other examples, the application runtime management module 52 of electronic device 100 can run the lightweight application 56 based on the lightweight application information 61 received. If the lightweight application 56 is already installed on electronic device 100, the application runtime management module 52 runs the lightweight application 56 successfully and sends the lightweight application information 61 to the lightweight application 56. If the lightweight application 56 is not installed on electronic device 100, the application runtime management module 52 fails to run the lightweight application 56 and sends the lightweight application information 61 to the silent installation engine 58. Thus, if the user has already opened the lightweight application 56 on electronic device 100 before electronic device 100 receives input for link 63, and the lightweight application 56 is already installed on electronic device 100, the application runtime management module 52 can run the lightweight application 56 faster without going through the silent installation engine 58.

[0172] S517. The silent installation engine 56 sends an installation success message to the application runtime management module 52 to indicate that the silent installation engine 58 has successfully installed the lightweight application 56.

[0173] After the silent installation engine 56 successfully installs the lightweight application 56, it can send an installation success message to the application operation management module 52 to notify the application operation management module 52 that the electronic device 100 has installed the lightweight application 56.

[0174] S518. The application operation management module 52 triggers the lightweight application 56 to display the interface 62 based on the lightweight application information 61.

[0175] The application operation management module 52 determines that the electronic device 100 has installed a lightweight application 56, and can trigger the display interface 62 of the lightweight application 56 based on the lightweight application information 61.

[0176] In some examples, the operating system of electronic device 100 can be HarmonyOS (operating system), and the lightweight application can be a meta-service application. The application runtime management module 52 can be a meta-capability module. The short link parsing engine 57 can be a lightweight application short link parsing engine. The silent installation engine 56 can be a meta-service silent installation engine. The lightweight application short link can be a meta-service short link.

[0177] In this way, when the electronic device 100 receives user input for link 63, the information application 51 can send link 63 to the application operation management module 52. The application operation management module 52 can then send link 63 to the short link parsing engine 57. The electronic device 100 can use the short link parsing engine 57 to determine whether link 63 is a lightweight application short link. When the electronic device 100 identifies link 63 as a lightweight application short link, it can interact with the short link server 200 to obtain lightweight application information 61. Based on the lightweight application information 61, the electronic device 100 can silently install the lightweight application. After successful silent installation, the electronic device 100 can directly open the lightweight application, enabling users to jump directly to the lightweight application interface 62 without intermediate steps when clicking link 63, reducing cumbersome operation steps and providing a more convenient user experience.

[0178] In one possible implementation, the short link server 200 can generate a short link to the lightweight application corresponding to the interface of the lightweight application. After generating the short link, the short link server 200 can store the correspondence between the short link and the deep link. After displaying the short link corresponding to the interface of the lightweight application, the electronic device 100 can receive user input on the short link and display a redirect interface in response to the input. The redirect interface includes an open control; for details, please refer to the above embodiments. Subsequently, when the electronic device 100 does not have the lightweight application installed, it can install the lightweight application based on the deep link after receiving user input on the open control, and after successful installation, display the interface of the lightweight application corresponding to the short link.

[0179] In this way, because lightweight applications are small in size, electronic devices 100 can quickly install lightweight applications without the user's awareness. After successfully installing the lightweight application, the device will jump to and display the interface corresponding to the lightweight application's short link, without requiring the user to install the application themselves, thus reducing the probability that the user will give up opening the interface corresponding to the application's short link midway.

[0180] Understandably, when the lightweight application is installed on the electronic device 100, the electronic device 100 can display the interface of the lightweight application corresponding to the application short link based on the deep link after receiving the user's input for the open control.

[0181] For example, after receiving the configuration information of the target lightweight application, the short link server 200 can generate a link 301 corresponding to the target interface of the target lightweight application. The short link server 200 can store the correspondence between the link 301 and the jump depth link 71. The short link server 200, the server of the target lightweight application, or the server of one or more applications can receive input and send the link 301 to one or more electronic devices.

[0182] Electronic device 100 displays such as Figure 1A Interface 11 is shown. Electronic device 100 can display the following after receiving link 301 via an information application: Figure 3A The window 305 is shown. Upon receiving user input (e.g., a click) to the window 305, the electronic device 100 can, in response to that input, display something like... Figure 3B The interface shown is 311. (As shown) Figure 3B As shown, interface 311 may include, but is not limited to, message box 312, which contains the entire content of the short message. Message box 312 includes link 301.

[0183] The electronic device 100 can, upon receiving user input (e.g., a click) on the link 301, respond to that input by displaying, as shown below. Figure 3C Window 321 is shown. (As shown) Figure 3C As shown, window 321 may include one or more options. These options may include, but are not limited to, the "Open URL" option 322.

[0184] The electronic device 100 can, upon receiving user input (e.g., a click) for the "Open URL" option 322, respond to that input by displaying, as shown below. Figure 6 The interface 601 is shown. The electronic device 100 can run a browser application in response to the user's input of the "Open URL" option 322. The browser application of the electronic device 100 can display interface 601 based on link 301.

[0185] like Figure 6As shown, interface 601 may include, but is not limited to, redirecting to webpage 602. Webpage 602 may include, but is not limited to, opening control 603. Electronic device 100 can use link 301 as the URL of webpage 602, allowing a browser application to obtain and display webpage 602 based on link 301. Optionally, webpage 602 may also include, but is not limited to, the identifier of an application used to manage lightweight applications (e.g., a meta-service center application or a lightweight application center application), etc. The application used to manage lightweight applications is also a lightweight application.

[0186] Here, if the electronic device 100 has not yet installed the target lightweight application when displaying interface 601, the electronic device 100 can, upon receiving user input to open control 603, respond to that input by using a deep link 71 to install the target lightweight application. After successfully installing the target lightweight application, it can then display the application as shown in the image. Figure 3D The interface shown is 341. Here, interface 341 is the target interface.

[0187] In this way, when the target lightweight application corresponding to the application shortcut is not installed, the electronic device 100 can jump to and display the target interface of the application shortcut without requiring manual operation by the user, which is more convenient. However, the electronic device 100 still needs to jump to and display the target interface through a browser application / web page, which is a cumbersome process.

[0188] In one possible implementation, the short link server 200 can generate application short links based on the application's configuration information. The short link server 200 can store the correspondence between application short links, deep links, and deep installation links. After receiving user input for a link, the electronic device 100 can obtain the corresponding deep link and deep installation link through the short link server 200. The electronic device 100 can run the application corresponding to the link based on the deep link. If the electronic device 100 successfully runs the application corresponding to the application short link based on the deep link, it can send the deep link to the corresponding application. The electronic device 100 can then display the interface corresponding to the deep link through this application. If running the application corresponding to the link fails, the electronic device 100 can run an application market application and send the deep installation link to the application market application. The electronic device 100 can then display the installation interface for installing the application corresponding to the deep installation link through the application market application.

[0189] It should be noted that when electronic device 100 successfully retrieves the corresponding deep link from the short link server 200 and successfully installs the deep link, it can be determined that the link is an application short link. When electronic device 100 fails to retrieve the corresponding data from the short link server 200, it can be determined that the link is neither an application short link nor a lightweight application short link. Electronic device 100 can run a browser application and display the interface corresponding to the link through the browser application.

[0190] In this way, electronic device 100 can directly trigger the display of the application's short link interface even when the application is already installed, without needing to go through a redirect interface. Electronic device 100 can also display the installation interface for the application corresponding to the short link even when it is not installed, improving the user experience. Since electronic device 100 does not need to display a redirect interface, the probability of users abandoning the triggering of the application's short link interface is reduced, enhancing the promotional effect of the application short link.

[0191] In other examples, the short link server 200 can parse deep links to obtain redirect information, which may include the package name of the target application and the path to the target interface. The short link server 200 can also parse deep installation links to obtain installation information, which may include the package name of the app store application and the path to the interface used to install the target application. The short link server 200 can store the mapping between application short links, redirect information, and installation information. In this way, the electronic device 100 can display the corresponding interface more quickly based on the redirect information or installation information, without needing to parse deep links and deep installation links itself.

[0192] The electronic device provided in the embodiments of this application is described below.

[0193] Electronic device 100 may be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device and / or smart city device. The embodiments of this application do not impose any special restrictions on the specific type of electronic device.

[0194] Figure 7 A schematic diagram of the structure of the electronic device 100 is shown.

[0195] The following description uses electronic device 100 as an example to illustrate the embodiment. It should be understood that... Figure 7 The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 7 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0196] Electronic device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0197] It is understood that the structures illustrated in the embodiments of the present invention 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.

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

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

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

[0201] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0202] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0203] It is understood that the interface link relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface linking methods or combinations of multiple interface linking methods as described in the above embodiments.

[0204] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0205] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0206] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0207] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0208] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0209] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0210] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0211] 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, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0212] 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, linking 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.

[0213] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD). The display panel can also be manufactured using organic light-emitting diodes (OLEDs), active-matrix organic light-emitting diodes (AMOLEDs), flexible light-emitting diodes (FLEDs), miniled, microled, micro-OLEDs, quantum dot light-emitting diodes (QLEDs), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0214] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0215] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimizations on image noise, brightness, etc. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0216] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0217] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0218] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0219] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0220] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0221] 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, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0222] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0223] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0224] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.

[0225] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

[0226] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In some embodiments, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0227] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0228] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0229] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0230] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0231] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to establish contact with and disconnect from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to achieve functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from it.

[0232] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses a layered architecture system as an example to illustrate the software structure of electronic device 100.

[0233] Figure 8 This is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0234] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into four layers, from top to bottom: the application layer, the application framework layer, the runtime and system libraries, and the kernel layer.

[0235] The application layer can include a series of application packages.

[0236] like Figure 8As shown, the application layer may include applications such as camera, browser, calendar, call, WLAN, Bluetooth, messaging application 51, and lightweight application 56. Messaging application 51 can be used to receive and display the aforementioned lightweight application links. Lightweight application 56 can be used to display the interface corresponding to the lightweight application link based on the aforementioned lightweight application information.

[0237] Optionally, the application layer may also include the specified application 54 mentioned above. Figure 8 (Not shown in the image) and the application market application 55. The designated application 54 can be used to redirect to the interface corresponding to the application's short link based on the aforementioned deep link or redirection information. The application market application 55 can be used to display the installation interface for installing the designated application 54 based on the installation deep link or installation information.

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

[0239] like Figure 8 As shown, the application framework layer may include a window manager, content provider, view system, resource manager, notification manager, application runtime management module 52, short link parsing engine 57, and silent installation engine 58, etc.

[0240] The application runtime management module 52 can be used to run applications, such as lightweight applications 56.

[0241] The short link parsing engine 57 can be used to identify lightweight application short links and obtain the lightweight application information corresponding to the lightweight application short links.

[0242] Silent Install Engine 58 can be used to install lightweight applications.

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

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

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

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

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

[0248] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0249] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

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

[0251] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

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

[0253] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0257] The following example, using a scene of capturing a photograph, illustrates the workflow of the software and hardware of the electronic device 100.

[0258] When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, etc.). The raw input event is stored in the kernel layer. The application framework layer retrieves the raw input event from the kernel layer and identifies the control corresponding to the input event. Taking a touch click as an example, where the corresponding control is the camera application icon, the camera application calls the application framework layer's interface to launch the camera application, and then calls the kernel layer to launch the camera driver, capturing still images or videos through camera 193.

[0259] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.

[0260] This application also provides a computer program product, including a computing program, which, when run on a processor, can implement the steps in the various method embodiments described above.

[0261] This application also provides a chip system, which includes a processing circuit and an interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0262] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. An application processing method, applied to electronic devices, characterized in that, include: Show the first link; Receive the first input to the first link; If it is determined that the first link is a short link for a lightweight application, the first interface is displayed through the first lightweight application; If it is determined that the first link is not the short link of the lightweight application, the second interface is displayed through the browser application.

2. The method according to claim 1, characterized in that, The step of displaying the first interface through a first lightweight application specifically includes: Send the first link to the server; The system receives first information sent by the server, the first information including the package name of the first lightweight application and the parameters of the first interface; Based on the package name of the first lightweight application, the first lightweight application is run, and the first interface is displayed through the first lightweight application based on the parameters of the first interface.

3. The method according to claim 2, characterized in that, The electronic device does not have the first application installed; running the first lightweight application based on its package name specifically includes: Install the first lightweight application based on its package name. After successfully installing the first lightweight application, run the first lightweight application.

4. The method according to any one of claims 1-3, characterized in that, Before determining that the first link is a lightweight application short link, the method further includes: The first link was detected to include the first domain name in the short link feature information; Before determining that the first link is not a lightweight application short link, the method further includes: The first link was detected to not include the first domain name.

5. The method according to any one of claims 1-3, characterized in that, The determination that the first link is a lightweight application short link specifically includes: If the first link is detected to include the first domain name in the short link feature information, and the length of the first path in the first link is less than the preset length indicated by the short link feature information, then the first link is determined to be the lightweight application short link. The determination that the first link is not a short link for a lightweight application specifically includes: If the first link is found to not include the first domain name, or the length of the first path in the first link is greater than the preset length, it is determined that the first link is not the lightweight application short link.

6. The method according to claim 4 or 5, characterized in that, Before determining that the first link is a lightweight application short link and displaying the first interface through the first lightweight application, the method further includes: The short chain feature information sent by the receiving server.

7. The method according to any one of claims 1-6, characterized in that, If it is determined that the first link is not the lightweight application's short link, displaying the second interface through a browser application specifically includes: Run the browser application; The browser application displays the second interface based on the first link. The second interface includes a first control, which is used to open a third interface of the second application.

8. The method according to claim 7, characterized in that, The electronic device is equipped with the second application; the method further includes: Receive a second input to the first control; In response to the second input, the second application is run based on the second link corresponding to the first control, and the third interface is displayed through the second application based on the second link.

9. The method according to claim 8, characterized in that, Before the second application is run based on the second link corresponding to the first control in response to the second input, and the third interface is displayed through the second application based on the second link, the method further includes: The first link is sent to the server through the browser application; The server sends the second link, which is used to display the third interface of the second application.

10. An electronic device, characterized in that, include: The system includes a messaging application, an application runtime management module, and a short link parsing engine; among these, The messaging application is used to display the first link; The messaging application is also used to send the first link to the application operation management module after receiving the user's first input on the first link. The application operation management module is used to send the first link to the short link parsing engine; The short link parsing engine is used to obtain first information corresponding to the first link from the server when it is identified that the first link is a short link of a lightweight application. The first information is used to indicate the first interface of the first lightweight application. The short link parsing engine is used to send the first information to the application runtime management module; The application operation management module is used to run the first lightweight application based on the first information; The first lightweight application is used to display the first interface based on the first information.

11. The electronic device according to claim 10, characterized in that, This also includes silent engine installation; among which, The application operation management module is specifically used to send the first information to the silent installation engine; The silent installation engine is used to install the first lightweight application based on the first information; The application operation management module is specifically used to run the first lightweight application after it is successfully installed, and to send the first information to the first lightweight application.

12. The electronic device according to claim 10 or 11, characterized in that, It also includes browser applications; among which, The short link parsing engine is also used to notify the application runtime management module that the first link is not the short link of the lightweight application when it is identified that the first link is not the short link of the lightweight application. The application operation management module is used to send the first link to the browser application; The browser application is used to display a second interface based on the first link.

13. An electronic device, characterized in that, include: One or more processors and one or more memories, wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program that, when the one or more processors execute the computer program, performs the application processing method as described in any one of claims 1-9.

14. A computer-readable storage medium, characterized in that, The system contains a computer program that, when executed by a processor, implements the application processing method as described in any one of claims 1-9.

15. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, performs the application processing method as described in any one of claims 1-9.

Images