Installation method, electronic equipment and readable storage medium

Abstract

The invention relates to the technical field of computers, in particular to an installation method, electronic equipment and a readable storage medium. The method comprises the steps that when terminal equipment installs an application program A for the first time through an application market, a server can determine that the application program A and an application program B are in a strong association relationship through a pre-established association relationship of the application program A; for example, for different terminal devices, such as mobile phones and smart watches, the navigation application G of the smart watches and the navigation application G of the mobile phones are in a strong association relationship. For the same terminal device, for the smart watch in dual-system operation, the payment application F of the smart watch in an ultra-long endurance mode and the payment application F of the smart watch in an intelligent mode are in a strong association relationship. Thus, the server can enable the terminal device to display the prompt information based on the association relationship between different application programs, a user is prompted to determine to install the application program B on the terminal device or other terminal devices, and the installation efficiency of the application programs and the use experience of the user are improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to an installation method, an electronic device, and a readable storage medium. Background Art

[0002] Due to the limitations in hardware capabilities of smart wearable devices such as smart watches, some application programs on smart wearable devices often need to be linked with relevant application programs on terminal devices such as mobile phones to be used. For example, the navigation application on a smart watch needs to be linked with the corresponding navigation application on a mobile phone to implement functions such as displaying a navigation interface on the smart watch for navigation.

[0003] For example, Figure 1A shows an interface 110 of a smart watch 10. When a user clicks on the application icon 111 of the installed AutoNavi Map TM on the interface 110, the smart watch 10 can display an interface 120 as shown. Figure 1B This interface 120 may include a QR code 121 and a prompt message 122 such as "Scan the QR code on your phone to install AutoNavi Map" to prompt the user to install AutoNavi Map on the mobile phone 20 side. TM . When the user installs AutoNavi Map on the mobile phone 20 based on the prompt message 122 TM and starts navigation, the navigation interface 210 of the mobile phone 20 as shown is displayed on the mobile phone 20 side. This navigation interface 210 may include navigation prompt messages 211 such as "Go straight along Wuyi Road for 50 meters" and prompt messages 212 such as "Whether to synchronize the walking navigation actions to the watch side for display". At this time, if the user clicks on the operation control 2120 that prompts "Synchronize", the smart watch 10 can display an interface 220 as shown. Figure 2A The interface 220 displays a navigation direction control 221 and a prompt message 222 "Go straight along Wuyi Road for 50 meters", so that the user can perform navigation through the smart watch 10. Figure 2B

[0004] However, since some users are not aware that some application programs on the smart watch side need to rely on the corresponding application programs on the mobile phone side, when the user is about to use the application programs downloaded on the smart watch, it is suddenly found that the corresponding application programs also need to be downloaded and installed on the mobile phone side before they can be used, resulting in a poor user experience. Summary of the Invention

[0005] To solve the above problems, embodiments of this application provide an installation method, an electronic device, and a readable storage medium.

[0006] In a first aspect, the present application provides an installation method, applied to a first terminal device, the method comprising: detecting a first installation instruction of a first application; in response to the first installation instruction, downloading the installation package of the first application, and displaying a prompt message for installing a second application associated with the first application.

[0007] It is understood that the first application mentioned above may refer to the navigation application G, payment application F, and other applications on the smartwatch 10 side mentioned in the embodiment of the present application, and is not limited here. The prompt information may refer to the prompt information displayed by the first terminal device in response to the instruction to display the prompt information sent by the server mentioned in the embodiment of the present application, wherein the prompt information can be used to instruct the user to confirm the installation of the second application on the first terminal device or the second terminal device.

[0008] Through the above solution, when an application is first installed on a terminal device, it is possible to determine other applications with strong associations with the application based on the association relationships pre-established by the terminal device's application market service. A prompt message is then displayed on the terminal device, prompting the user to confirm the simultaneous installation of other applications with strong associations with the application on the current terminal device or other terminal devices. This allows the coordinated installation of multiple applications with strong associations, eliminating the need for the user to wait until the application is installed and ready to use before installing other applications with strong associations with the application. This saves application installation time and improves the user's application installation experience.

[0009] In a possible implementation of the first aspect above, the prompt information includes a confirmation control; and the method also includes: corresponding to detecting a first operation of the user on the confirmation control, installing the second application on the first terminal device; or corresponding to detecting a first operation of the user on the confirmation control, sending a confirmation message, wherein the confirmation information is used to indicate the installation of the second application to the second terminal device associated with the first terminal device.

[0010] It can be understood that the confirmation control may refer to the control 432 and the control 632 mentioned in the embodiment of the present application; the second application may refer to the navigation application G, payment application F and other applications on the mobile phone 20 side mentioned in the embodiment of the present application, or the navigation application G, payment application F and other applications on the smart watch 10 side in smart mode.

[0011] In a possible implementation of the first aspect above, corresponding to detecting a first operation of a user on a confirmation control, sending confirmation information includes: sending confirmation information to a server, wherein the confirmation information is used to instruct the server to send an instruction to install a second application and an installation package of the second application to a second terminal device.

[0012] In a possible implementation of the first aspect described above, displaying a prompt message for installing a second application associated with the first application includes: corresponding to detecting that the second application is not installed on the first terminal device, controlling the first terminal device to display a first prompt message for installing the second application.

[0013] It can be understood that when the server receives the installation information of the first application installed on the first terminal device, the server can further determine that the second application that has a strong association relationship with the first application is not installed. Then the server can send a prompt message to the first terminal device to prompt the installation of the second application. In this way, after receiving the installation information of the first application, the server can quickly determine whether the second application is installed. If not installed, it can quickly send an instruction to the first terminal device to display a prompt message to guide the installation of the second application.

[0014] In a possible implementation of the first aspect described above, the first terminal device includes a first processor and a second processor. The computing power of the first processor is greater than that of the second processor, and the terminal device includes a first operating mode corresponding to the first processor and a second operating mode corresponding to the second processor.

[0015] It can be understood that the first processor may be the application processor (AP) mentioned in the embodiments of the present application, and the second processor may be the micro - controller unit (MCU) mentioned in the embodiments of the present application; the first operating mode may refer to the intelligent mode of the smart watch 10 mentioned in the embodiments of the present application, and the second operating mode may refer to the ultra - long battery life mode of the smart watch 10 mentioned in the embodiments of the present application.

[0016] In a possible implementation of the first aspect described above, detecting a first installation instruction for the first application includes: detecting a first installation instruction for the first application in the second operating mode; and displaying a prompt message for installing a second application associated with the first application includes: corresponding to detecting a first installation instruction for the first application in the second operating mode, confirming whether the second application has been installed on the first terminal device; corresponding to confirming that the second application is not installed, displaying a second prompt message for installing the second application.

[0017] In a possible implementation of the first aspect described above, it further includes: corresponding to detecting a second operation by the user to confirm the installation of the second application in the second operating mode, switching the operating mode of the first terminal device to the first operating mode; and installing the second application in the first operating mode.

[0018] It can be understood that in some other embodiments, it is also possible to install the second application in the first operating mode, which is not limited herein.

[0019] In a possible implementation of the above first aspect, in response to the first installation instruction, downloading the installation package of the first application, including: sending an installation request for the first application to the server; and the method further includes: receiving association information from the server, where the association information is sent by the server after determining that there is a second application associated with the first application in response to the installation request for the first application; and displaying a prompt message for installing the second application associated with the first application, including: corresponding to receiving the association information, displaying the prompt message.

[0020] It can be understood that the association information is the association information pre-established by the server based on the first application or the second application, and the association relationship can represent the dependence of the first application on the second application, that is, if the second application is not installed, the first application cannot use the corresponding function. The server can determine that the second application with a strong association relationship with the first application is not installed based on the association information, and then the server can send an instruction to display the prompt message to the first terminal device to prompt the user to install the second application.

[0021] In a possible implementation of the above first aspect, detecting the first installation instruction of the first application includes: detecting a third operation of the user, and the third operation is used to send an installation request for the first application to the server.

[0022] In a second aspect, the application provides an installation method applied to a server. The method includes: receiving an installation request for a first application sent by a first terminal device; in response to the installation request, determining that there is a second application associated with the first application; sending association information to the first terminal device, where the association information indicates that the second application needs to be installed to install the first application; and in response to the confirmation information sent by the first terminal device, sending the installation package of the second application.

[0023] It can be understood that the association information may refer to the instruction for the server to send a prompt message to the first terminal device mentioned in the embodiments of the present application; the server may refer to the server 30 mentioned in the embodiments of the present application, that is, the application market service.

[0024] Through the above solution, when an application is first installed on a terminal device, it is possible to determine other applications with strong associations with the application based on the association relationships pre-established with the application by the terminal device's application market service, and display a prompt on the terminal device, prompting the user to confirm the simultaneous installation of other applications with strong associations with the application on the current terminal device or other terminal devices. This allows the coordinated installation of multiple applications with strong associations, eliminating the need for the user to wait until the application is installed and ready to use before installing other applications with strong associations with the application. This saves application installation time and improves the user's application installation experience.

[0025] In a possible implementation of the second aspect above, sending an installation package of the second application in response to a confirmation message sent by the first terminal device includes: sending an instruction to install the second application and the installation package of the second application to the second terminal device associated with the first terminal device in response to the confirmation message.

[0026] In a possible implementation of the second aspect above, in response to the confirmation information, an installation package of the second application is sent to the first terminal device.

[0027] In a possible implementation of the second aspect above, the method further includes establishing an association relationship between the first application and the second application.

[0028] In a possible implementation of the second aspect above, the process of establishing an association relationship between the first application and the second application includes: obtaining the binary file of the first application, and determining the permission application information, distributed component type or distributed interface type of the second application based on the binary file of the first application; determining that the first application and the second application have an association relationship based on the fact that the permission application information and distributed component type of the first application and the second application are the same; or, determining that the first application and the second application have an association relationship based on the fact that the permission application information and distributed interface type of the first application and the second application are the same.

[0029] It can be understood that the permission application information may be the support for Bluetooth communication or near field communication (NFC) mentioned in the embodiments of this application, the distributed component type may be the "wear engine", "android wear", "watch kit", "CommuX" mentioned in the embodiments of this application, and the distributed interface type may be the "p2pClient", "Init" mentioned in the embodiments of this application, etc., which are not limited here.

[0030] In a possible implementation of the second aspect above, determining the permission application information, distributed component type, or distributed interface type of the second application based on the binary file of the first application includes: determining the first distributed interface and the first distributed component applied by the first application based on the binary file of the first application, and obtaining the installation package name of the second application through the permission application of the first application corresponding to the first distributed interface or the first distributed component; obtaining the permission application information, distributed component type, or distributed interface type of the second application based on the installation package name of the second application.

[0031] In a third aspect, an embodiment of the present application provides a terminal device, including: a memory, which includes physical memory and external memory and is used to store instructions executed by one or more processors of the terminal device; and a processor, which is used to execute the instructions to enable the terminal device to implement the installation method provided in the first aspect and various possible implementations of the first aspect above.

[0032] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which instructions are stored, and when the instructions are executed on the terminal device, the installation method provided in the first aspect and various possible implementations of the first aspect above is implemented.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instructions, and when the computer program / instructions run on the terminal device, the terminal device is enabled to implement the installation method provided in the first aspect and various possible implementations of the first aspect above.

[0034] For the beneficial effects of the second aspect to the fifth aspect above, reference may be made to the relevant descriptions in the first aspect and various possible implementations of the first aspect above, and details are not described herein again. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1A A schematic diagram of an interface 110 of a smart watch 10 is shown;

[0036] Figure 1B A schematic diagram of an interface 120 of a smart watch 10 is shown;

[0037] Figure 2A According to the method provided by the embodiment of the present application, a schematic diagram of a navigation interface 210 of a mobile phone 20 is shown;

[0038] Figure 2B According to the method provided by the embodiment of the present application, a schematic diagram of an interface 220 of a smart watch 10 is shown;

[0039] Figure 2CThe method provided by the embodiments of the present application shows a schematic diagram of an interface 230 of a mobile phone;

[0040] Figure 2D The method provided by the embodiments of the present application shows a scenario diagram of an application market service for collaboratively installing application programs on multiple terminal devices based on the distribution ability;

[0041] Figure 2E The method provided by the embodiments of the present application shows a schematic diagram of a dual-system structure in which a dual-core device operates;

[0042] Figure 3 According to the embodiments of the present application, an interaction flowchart of an installation method is shown;

[0043] Figure 4A The method provided by the embodiments of the present application shows a schematic diagram of an interface 410 of a smart watch 10;

[0044] Figure 4B The method provided by the embodiments of the present application shows a schematic diagram of an application market interface 420 of a smart watch 10;

[0045] Figure 4C The method provided by the embodiments of the present application shows a schematic diagram of an interface 430 of a smart watch 10 displaying a first prompt message;

[0046] Figure 4D The method provided by the embodiments of the present application shows a schematic diagram of a scenario for collaboratively installing application programs between a smart watch 10 and a mobile phone 20;

[0047] Figure 5 According to the embodiments of the present application, an interaction flowchart of another installation method is shown;

[0048] Figure 6A The method provided by the embodiments of the present application shows a schematic diagram of an interface 610 of a smart watch 10;

[0049] Figure 6B The method provided by the embodiments of the present application shows a schematic diagram of an interface 620 of a smart watch 10 in an ultra-long battery life mode;

[0050] Figure 6C The method provided by the embodiments of the present application shows a schematic diagram of an interface 630 of a smart watch 10 displaying a second prompt message in an ultra-long battery life mode;

[0051] Figure 6D The method provided by the embodiments of the present application shows a schematic diagram of a pull-up interface 640 of a smart watch 10 in an ultra-long battery life mode;

[0052] Figure 6E The method provided by an embodiment of the present application shows a schematic diagram of a pull-up interface 650 when a smart watch 10 is in the smart mode;

[0053] Figure 6F The method provided by an embodiment of the present application shows a schematic diagram of a scenario for collaborative installation of a payment application F between the ultra-long battery life mode and the smart mode of the smart watch 10;

[0054] Figure 6G The method provided by an embodiment of the present application shows another schematic diagram of a scenario for collaborative installation of a payment application F between the ultra-long battery life mode and the smart mode of the smart watch 10;

[0055] Figure 7 The method provided by an embodiment of the present application shows a flowchart of establishing an application association relationship by an application market service;

[0056] Figure 8A The method provided by an embodiment of the present application shows a HarmonyOS TM schematic diagram of code information in an application binary file;

[0057] Figure 8B The method provided by an embodiment of the present application shows an Android TM schematic diagram of code information in an application binary file;

[0058] Figure 8C The method provided by an embodiment of the present application shows an iOS TM schematic diagram of code information in an application binary file;

[0059] Figure 8D The method provided by an embodiment of the present application shows a schematic diagram of a scenario;

[0060] Figure 8E The method provided by an embodiment of the present application shows an Android TM schematic diagram of code information of an application in the Info.plist of an application binary file;

[0061] Figure 9A The method provided by an embodiment of the present application shows a scenario diagram of establishing an application association update by an application market service;

[0062] Figure 9B The method provided by an embodiment of the present application shows a scenario diagram for prompting coordinated installation of different applications based on Figure 9A the established application association relationship;

[0063] Figure 9C The method provided by the embodiments of the present application shows a Figure 9A and Figure 9B schematic diagram of a combined macro scenario;

[0064] [[ID=⑨]] Figure 10 The method provided by the embodiments of the present application shows a schematic diagram of the structure of a terminal device 100. Detailed implementation manners

[0065] The illustrative embodiments of the present application include, but are not limited to, an installation method, an electronic device, and a readable storage medium.

[0066] It can be understood that the electronic device in the embodiments of the present application can also be referred to as a terminal, user terminal, mobile terminal, user equipment (UE), terminal device, mobile station (MS), mobile terminal (MT), etc. The terminal device can be a mobile phone, smart TV, wearable device, tablet computer (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The following will take a smart watch and a mobile phone as examples for illustration. However, it can be understood that the technical solutions described in the present application are applicable to various electronic devices with mobile communication functions as described above, not limited to mobile phones or smart watches.

[0067] The technical solutions of the present application will be introduced below with reference to the accompanying drawings.

[0068] As mentioned above, since some users are not aware that some application programs on the terminal device need to rely on the corresponding application programs on other terminal devices, when the user is about to use the application programs downloaded on the terminal device, it is temporarily found that the corresponding application programs also need to be downloaded and installed on other terminal devices before they can be used, resulting in a poor user experience. For example, application program A is the navigation application G on the smart watch side, application program B is the navigation application G on the mobile phone side, and application program A must rely on application program B to be used.

[0069] In some solutions, if the operating system of the terminal device is iOS TM system, the distribution capability of the application market service under the iOS TM system can be used to achieve collaborative installation of related application programs among multiple terminal devices. Among them, the distribution capability of the application market service means that if an application program is installed on one of the different terminal devices logged in with the same user account, the other terminal devices logged in with this user account can synchronously install this application program. For example, when a mobile phone logged in with the same account installs a navigation application through the application market, other devices logged in with this account, such as smart watches, tablets, etc., can synchronously install this navigation application.

[0070] For example, Figure 2C shows a schematic diagram of the interface 230 of a mobile phone under an operating system. In the interface 230, there is an icon 232 of the navigation application G, an operation control 231 indicating the installation of the navigation application G, and other terminal devices supported for installation by the navigation application G are prompted to the user. When the user clicks the operation control 231, the application program can be collaboratively installed on multiple terminal devices based on the distribution capability of the application market service under this operating system.

[0071] For example, Figure 2D shows a scenario diagram of the application market service under an operating system collaboratively installing application programs on multiple terminal devices based on the distribution capability.

[0072] As Figure 2D shown, the same user account can be logged in on a mobile phone, a smart watch, a tablet, and a laptop. The application programs 201 to 204 can be different application programs deployed on different terminal devices. For example, 201 is an application program for the mobile phone, 202 is an application program for the smart watch, 203 is an application program for the tablet, and 204 is an application program for the laptop. When the mobile phone installs the application program 201 through the application market, the application market service can push the installation package of the application program 201 to the application market on the mobile phone side for downloading and installation. At the same time, based on the application distribution capability, the application market service can also synchronously push the installation package of the application program 202 to the application market of the smart watch for installation, push the application program 203 to the application market of the tablet for installation synchronously, and push the application program 204 to the application market of the laptop for installation synchronously.

[0073] It can be understood that the installation package names of the above-mentioned applications that support cross-device collaborative installation must be the same in the application markets of each terminal device. That is, for the application installation packages uploaded by the developer to the application market of this operating system, each application installation package needs to have a unique installation package name (bundle identity document, Bundle ID) according to the relevant regulations of this operating system for the uploaded application installation packages, and the naming formats of the installation package names are the same. For example, the installation package name format can be "com.xx1.xx2", where xx1 represents the developer name of the application, and xx2 can represent the application name. That is, the installation package names of the applications of the same application on different types of electronic devices under this operating system need to be the same.

[0074] However, in actual scenarios, the installation package names of applications on different electronic devices are not the same. For example, the installation package name of the navigation application G on the smartwatch side is "GForWatch.xx", while the installation package name of the navigation application G on the mobile phone side is "GForPhone.xx". In this way, when installing the navigation application G on one device, it is impossible to synchronously install the navigation application G on other electronic devices collaboratively based on the distribution capabilities of the above-mentioned application market, which affects the user experience.

[0075] To solve the above problems, an installation method is provided in the embodiments of the present application. The method includes: when the terminal device first installs the application A through the application market, the application market service can determine that the application A and the application B are in a strong association relationship through the pre-established association relationship of the application A. For example, for different terminal devices, assuming the terminal devices are a mobile phone and a smartwatch respectively, the navigation application G on the smartwatch and the navigation application G on the mobile phone are in a strong association relationship. In some other embodiments, for the same terminal device, assuming the terminal device is a smartwatch with dual-system operation, the payment application F in the ultra-long battery life mode and the payment application F in its smart mode corresponding to different systems are in a strong association relationship. In this way, the application market service of the terminal device can cause a prompt message to be displayed on the terminal device, prompting the user to determine to synchronously install the application B on this terminal device or other terminal devices, so as to realize the linked installation of the application A and the application B.

[0076] Based on the above, when the user uses the application A installed on one side of the terminal device, there is no need to wait for the application B on which the application A depends to be downloaded and installed on the other side of the terminal device, saving the application installation time and improving the user experience.

[0077] In another scenario, when the smartwatch is a terminal device with dual-core and dual-system, reference can be made to Figure 2ESchematic diagram of a dual - system structure for the operation of a dual - core device. In the embodiments of the present application, the smart watch 10 can be a dual - core device, for example, including a first processor 01 (not shown) and a second processor 02 (not shown). The above - mentioned first processor 01 can correspond to the main processor of the smart watch 10 in the intelligent mode, having relatively high computing power, such as an application processor (AP), etc. The above - mentioned second processor 02 can correspond to the coprocessor used by the smart watch 10 in the ultra - long battery life mode, with lower power consumption during operation, such as a micro - controller unit (MCU), etc.

[0078] Taking the first system and the second system as examples, combined with Figure 2E Exemplarily illustrate the software structure of the dual - system running on a dual - core device such as the smart watch 10.

[0079] As Figure 2E shown, the dual - system running on a dual - core device such as the smart watch 10 can include a first system 240 and a second system 250. It can be understood that in some embodiments, the first system 240 and the second system 250 can be two different systems, or two identical systems. In other embodiments, the first system 240 and the second system 250 can also be two - part system architectures of the same system, which is not limited here.

[0080] It can be understood that the operating system of a dual - core device such as the smart watch 10 can adopt a layered architecture, an event - driven architecture, a micro - kernel architecture, a microservices architecture, or a cloud architecture. Among them, the layered architecture divides software into several layers, and each layer has a clear role and division of labor. The layers communicate through software interfaces. In some embodiments, as Figure 2E shown, the first system 240 from top to bottom is respectively an application layer 241, a framework layer 242, a system service layer 243, and a kernel layer 244.

[0081] Among them, the application layer 241 can run the first - type applications adapted to the first system 240 and the system user interface (SystemUI). Among them, SystemUI can be used to call the display framework 2421 of the framework layer 242 to negotiate the drawing and rendering of relevant interface elements, and call the scheduling module 2431 of the system service layer 243 to negotiate the composition and display of the rendered interface elements, that is, SystemUI is used to provide an interaction interface with the user and trigger the display process of relevant interfaces.

[0082] The framework layer 242 may include a display framework 2421 for communicating with the display framework 2521 of the second system 250 to negotiate and decide which interface elements of the relevant interface are to be drawn and rendered by the first processor 110 or the second processor 120.

[0083] The system service layer 243 may include a scheduling module 2431 for communicating with the scheduling module 2531 of the second system 250 to negotiate the composition of the relevant interface elements by the first processor 01 or the second processor 02 and send them for display.

[0084] In some embodiments, the above-mentioned scheduling module 2431 may be, for example, a hybrid scheduling module based on a hybrid interface, where the hybrid interface can be used to schedule the graphics synthesizers connected or run by the first processor 01 or the second processor 02 to synthesize the interface elements of each part after rendering, and then send the interface-related data after synthesis to the display screen of the terminal device for display, that is, send for display.

[0085] The kernel layer 244 is the layer between hardware and software. The kernel layer of the distributed operating system may include: a kernel subsystem and a driver subsystem. Among them, the kernel subsystem can adopt a multi-kernel design for the distributed operating system, so the kernel subsystem supports selecting a suitable OS kernel for different resource-constrained devices. The kernel abstract layer (KAL) on the kernel subsystem provides basic kernel capabilities to the upper layer by shielding the multi-kernel differences, including process / thread management, memory management, file system, network management, and peripheral management, etc. The driver framework provided by the driver subsystem is the basis for the opening of the distributed system hardware ecosystem, providing a unified peripheral access capability and a driver development and management framework. In some embodiments, the driver subsystem may include device drivers such as display drivers and audio drivers for driving the corresponding devices to work and providing corresponding hardware capabilities, etc.

[0086] Continuing to refer to Figure 2E , similarly, the second system 250 from top to bottom is respectively an application layer 251, a framework layer 252, a system service layer 253, and a kernel layer 254.

[0087] Among them, the application layer 251 may run a second type of application adapted to the second system 250 and SystemUI. Among them, SystemUI can be used to call the display framework 2521 of the framework layer 252 to negotiate the drawing and rendering of the relevant interface elements, and call the scheduling module 2531 of the system service layer 253 to negotiate the composition of the rendered interface elements and send them for display, etc.

[0088] It can be understood that the above-mentioned second type of application can be a simpler application program than the first type of application. Among them, the above-mentioned first type of application can be an application program deployed on the main processor, and the above-mentioned second type of application can be an application program deployed and running on the coprocessor.

[0089] The framework layer 252 may include a display framework 2521 for communicating with the display framework 2421 of the first system 240 to negotiate and decide which interface elements of the relevant interface are to be drawn and rendered by the first processor 01 or the second processor 02.

[0090] The system service layer 253 may include a scheduling module 2531 for communicating with the scheduling module 2431 of the first system 240 to negotiate which interface elements of the relevant interface are to be synthesized by the first processor 240 or the second processor 250 and sent for display.

[0091] The kernel layer 254 is the layer between hardware and software, and its specific structure and functions can refer to the relevant description of the above-mentioned kernel layer 244. In some embodiments, the kernel subsystems and driver subsystems of the kernel layer 254 may have fewer kernel capabilities and driver structures, etc. than those of the kernel layer 244, which is not limited herein.

[0092] It can be understood that the process of pre-establishing a strong association relationship between application program A and application program B by the above-mentioned application market service can be summarized as the following process: The application market service can read the binary file of application program A uploaded by the developer. The binary file can be understood as an executable file, and the code level corresponding to the binary file may include application program information such as the distributed capabilities, distributed components or distributed interfaces possessed by the application program. Furthermore, the application market service can determine the application programming interface (API) or distributed components used by application program A based on the binary file, and determine the installation package name of application program B associated with application program A based on the API or distributed components. Among them, the installation package name of application program B associated with application program A can be described at the code level corresponding to the binary file of application program A. Then, according to the installation package names of application program A and application program B respectively, determine the types of terminal devices on which application program A and application program B are respectively deployed, the permission information applied for by each, the types of distributed components or APIs. If the permission information and distributed component types applied for by the two application programs are the same, or the permission information and API types applied for by each are the same, then the two application programs can be set as a strong association relationship.

[0093] It can be understood that the specific process of the association relationship of each application program pre-established by the application market service will be based on Figure 7The following elaborates on the specific process shown.

[0094] It can be understood that for the installation package name of the application B that has an association with the application A, the developer can explicitly specify it at the code level of the binary file of the application A uploaded to the application market. That is, in the uploaded binary file, the developer can write relevant code to describe the relevant information of the application B that has an association with the application A, such as the installation package name of the application B, etc.

[0095] It can be understood that the types of terminal devices deployed above can include smart watches or mobile phones, etc., the permission information can include Bluetooth access permissions, and the types of distributed components can include distributed components of the HarmonyOS TM system, such as the wearable ability component (wear engine), or Android TM system's distributed component: Android wearable ability component (android wearable), or iOS TM system's distributed component: watch development framework component (watch kit), etc., which are not limited here.

[0096] The following will illustrate the installation method provided by the embodiments of the present application based on the relevant process schematic diagram.

[0097] For example, Figure 3 According to the embodiments of the present application, an interaction flowchart of an installation method is shown. It can be understood that the interaction entities involved in this interaction process include the smart watch 10, the mobile phone 20, and the server 30. Among them, the application A can be, for example, the navigation application G in the smart watch 10, and the application B can be, for example, the navigation application G in the mobile phone 20. The server 30 can refer to the application market service mentioned above, which is not limited here.

[0098] Specifically, the interaction process can include the following steps:

[0099] S301: The smart watch 10 detects the first operation instruction and downloads and installs the application A.

[0100] In some embodiments, as Figure 4A shown, when the user clicks on the icon 411 of the application market in the interface 410 of the smart watch 10, the application A that needs to be installed on the smart watch 10 can be found based on the application market. For example, the application A is the navigation application G. It can be understood that the first operation instruction refers to the operation instruction generated by the user clicking on the operation control 422.

[0101] Figure 4B shows a schematic diagram of the application market interface of the smart watch 10.

[0102] For example,Figure 4B As shown, the application name 421 of the navigation application G can be displayed in the application market interface 420, and an operation control 422 for instructing the user to click to install the navigation application G. Based on the user clicking the operation control 422, the smart watch 10 can detect the first operation instruction generated corresponding to the user clicking the operation control 422, and download and install the navigation application G.

[0103] S302: The smart watch 10 reports the installation information of the application program A to the server 30.

[0104] In some embodiments, through the first operation instruction generated corresponding to the user clicking the operation control 433 in S301, after the smart watch 10 detects the first operation instruction, the application market of the smart watch 10 can install the navigation application G, and report the information of installing the navigation application G on the smart watch 10 to the server 30.

[0105] S303: The server 30 determines that the application program B having a strong association relationship with the application program A is not installed on the mobile phone 20 side.

[0106] In some embodiments, as can be seen from the above S302, the application market of the smart watch 10 reports the information of installing the navigation application G on the smart watch 10 to the server 30. After receiving the installation information of installing the navigation application G on the smart watch 10, the server 30 can, based on the pre-established association relationships of each application program, determine that the application program having a strong association relationship with the navigation application G on the smart watch 10 is the navigation application G on the mobile phone 20 side. And it can detect that the navigation application G on the mobile phone 20 is not installed.

[0107] It can be understood that the pre-established association relationships of each application program by the server 30 may include: the navigation application G on the smart watch 10 and the navigation application G on the mobile phone 20 side have a strong association relationship. This strong association relationship means that the navigation application G on the smart watch 10 must rely on the navigation application G on the mobile phone 20 when in use.

[0108] It can be understood that the specific process of the pre-established association relationships of each application program for the application market service will be specifically described below based on Figure 7 the flow shown.

[0109] S304: The server 30 sends an instruction to the smart watch 10 to display a first prompt message.

[0110] In some embodiments, through S303, the server 30 determines that the navigation application G on the mobile phone 20 having a strong association relationship with the navigation application G on the smart watch 10 is not installed, and the server 30 can send an instruction to the smart watch 10 to display a first prompt message. Among them, the first prompt message can be used to prompt the user to install the navigation application G on the mobile phone 20 side.

[0111] S305: The smartwatch 10 displays a first prompt message.

[0112] In some embodiments, in S304, the server 30 sends an instruction to the smartwatch 10 to display a first prompt message. After the application program of the smartwatch 10 receives the instruction sent by the server 30 to display the first prompt message, it can cause the first prompt message to be displayed on the user interface (UI) of the smartwatch 10. For example, Figure 4C An interface 430 for the smartwatch 10 to display a first prompt message is shown. The first prompt message 431 "It is detected that this application needs to rely on the navigation application G installed on the mobile phone side, otherwise this application cannot be used normally. Do you want to install the navigation application G on the mobile phone side?" is displayed in the interface 430 to prompt the user to install the navigation application G on the mobile phone 20. The user can click the confirmation control 432 "Yes" for indicating installation to confirm installing the navigation application G on the mobile phone 20, or can click the control 433 "No" for indicating not to install, and then the navigation application G will not be installed in the mobile phone 20.

[0113] S306: The smartwatch 10 detects a second operation instruction.

[0114] In some embodiments, when the smartwatch 10 displays the first prompt message, when the user clicks the above Figure 4C operation control 432 "Yes" for indicating installation, the UI interface of the smartwatch 10 can detect the second operation instruction generated by the user clicking the operation control 432.

[0115] S307: In response to the second operation instruction, the server 30 sends an installation package of the application program B and an installation instruction for the application program B to the mobile phone 20.

[0116] In some embodiments, when the server 30 recognizes the second operation instruction in S306 above, that is, the user determines to install the navigation application G on the mobile phone 20, then the server 30 can, in response to the second operation instruction, send an installation package of the navigation application G for installation on the mobile phone 20 to the application market of the mobile phone 20, as well as an installation instruction to install the navigation application G on the mobile phone 20.

[0117] S308: The mobile phone 20 installs the application program B in response to the installation instruction.

[0118] In some embodiments, when the application market of the mobile phone 20 receives the installation package of the navigation application G for installation on the mobile phone 20 and the installation instruction sent by the server 30, the application market of the mobile phone 20 can install the navigation application G in the mobile phone 20 based on the installation package of the navigation application G.

[0119] Figure 4D Based on the above Figure 3 The described solution shows a schematic diagram of a scenario for collaborative installation of application programs between the smartwatch 10 and the mobile phone 20. As Figure 4D shown, when the user clicks on the operation control 422 in the interface 420 of the application market of the smartwatch 10, the application market of the smartwatch 10 can report the installation information of the navigation application G to the server 30, and control the display of a first prompt message 431 on the interface 430 of the smartwatch 10 to prompt the user to also install the navigation application G on the mobile phone 20 side. Then, the server 30 can send the installation package and installation instructions of the navigation application G to the application market on the mobile phone 20 side for installation. In this way, the user can directly open the already installed navigation application G by clicking on the operation control 441 in the interface 440 of the mobile phone. Finally, when the user needs to use navigation on the smartwatch 10, a prompt message 451 "Please initiate walking / cycling / bus navigation or hail a taxi in the navigation application G on the mobile phone side, and the information will be synchronously displayed on the watch side" can be displayed in the interface 450 of the smartwatch 10. When the user sets up the relevant navigation route on the mobile phone 20 side, navigation can be carried out through the smartwatch 10.

[0120] Through the above solution, when installing an application program for the first time on a terminal device, it is possible to establish, based on the association relationship of the application program pre-established by the application market service of the terminal device, the other application programs that have a strong association relationship with the application program, and display a prompt message on the terminal device to prompt the user to determine to synchronously install on other terminal devices the other application programs that have a strong association relationship with the application program. It is possible to realize the linked installation of multiple application programs with a strong association relationship, without waiting for the installation of the other application programs that have a strong association relationship with the application program when the user has installed the application program and is ready to use it, saving the application installation time and improving the user experience of installing and using application programs.

[0121] In some other embodiments, when collaboratively installing different application programs in different modes of the same terminal device, such as in the smart mode of the smartwatch or the ultra-long battery life mode of the smartwatch, collaboratively install the payment application F in the smart mode of the smartwatch and the payment application F in the ultra-long battery life mode of the smartwatch.

[0122] It can be understood that different modes of the smartwatch in the embodiments of the present application correspond to the use of different processors, and the smartwatch has dual-core communication capabilities. Dual-core communication means that it runs based on an application processor (AP) in the smart mode of the smartwatch; and it runs based on a microcontroller unit (MCU) in the ultra-long battery life mode of the smartwatch.

[0123] Figure 5An interaction flowchart showing another installation method according to an embodiment of the present application is illustrated. It can be understood that the interaction entities involved in this interaction process include the smartwatch 10 and the server 30. Among them, the application A can be, for example, the payment application F in the ultra-long battery life mode of the smartwatch 10, and the application B can be, for example, the payment application F in the smart mode of the smartwatch 10, which is not limited herein.

[0124] Specifically, the interaction process may include the following steps:

[0125] S501: The smartwatch 10 detects a third operation instruction in the ultra-long battery life mode, and downloads and installs the application A.

[0126] In some embodiments, as Figure 6A shown, the user can click on the icon 611 of the app market in the interface 610 of the smartwatch 10 in the ultra-long battery life mode. Then, the user can find the application A that needs to be installed in the smartwatch 10 in the ultra-long battery life mode through this app market. For example, the application A can be the payment application F for the smartwatch 10 in the ultra-long battery life mode.

[0127] Figure 6B A schematic diagram of the app market interface of the smartwatch 10 in the ultra-long battery life mode is shown.

[0128] As Figure 6B shown, the app market interface 620 can display the app name 621 of the payment application F, and the operation control 622 indicating that the user clicks to install the payment application F. Based on the user's click on the operation control 622. The smartwatch 10 in the ultra-long battery life mode can detect the third operation instruction corresponding to the user's click on the operation control 622, and download and install the payment application F.

[0129] It can be understood that in some other embodiments, the user can also install the applications supported by the ultra-long battery life mode of the smartwatch 10 through the application settings of other terminal devices with the same account as the smartwatch 10, which is not limited herein.

[0130] S502: The smartwatch 10 reports the installation information of the application A to the server 30.

[0131] In some embodiments, through the third operation instruction generated by the user's click on the operation control 622 in S501. After the smartwatch 10 detects the third operation instruction, the app market of the smartwatch 10 can install the application A, and report the information of installing the payment application F in the ultra-long battery life mode of the smartwatch 10 to the server 30.

[0132] S503: The server 30 determines that application B, which has a strong association with application A, is not installed in the intelligent mode of the smartwatch 10.

[0133] In some embodiments, in the above S502, the smartwatch 10 in the ultra-long battery life mode reported to the server 30 the information that the payment application F was installed in the smartwatch 10 in the ultra-long battery life mode. After receiving the information that the payment application F was installed in the smartwatch 10 in the ultra-long battery life mode, the server 30 can, based on the pre-established association relationships of each application program in the server 30, determine that the application program that has a strong association with the payment application F in the ultra-long battery life mode of the smartwatch 10 is the payment application F in the intelligent mode of the smartwatch 10. And the server 30 can detect that the payment application F in the intelligent mode of the smartwatch 10 is not installed.

[0134] It can be understood that the pre-established association relationships of each application program in the server 30 may include: the payment application F in the ultra-long battery life mode of the smartwatch 10 and the payment application F in the intelligent mode of the smartwatch 10 have a strong association relationship. This strong association relationship means that the prerequisite for using the payment application F in the ultra-long battery life mode of the smartwatch 10 is that the payment application F has been installed in the intelligent mode of the smartwatch 10.

[0135] It can be understood that the specific process of the pre-established association relationships of each application program for the application market service will be specifically described below based on Figure 7 the process shown.

[0136] S504: The server 30 sends an instruction to the smartwatch 10 to display a second prompt message.

[0137] In some embodiments, in S503, the server 30 determines that the payment application F in the intelligent mode, which has a strong association with the payment application F in the ultra-long battery life mode of the smartwatch 10, is not installed. Based on this, the server 30 can send an instruction to the smartwatch 10 in the ultra-long battery life mode to display a second prompt message. Among them, the second prompt message can be used to prompt the user to install the payment application F in the intelligent mode of the smartwatch 10.

[0138] S505: The smartwatch 10 displays the second prompt message.

[0139] In some embodiments, as can be seen from S504, the server 30 sends an instruction to the smartwatch 10 in the ultra-long battery life mode to display a second prompt message. After receiving the instruction sent by the server 30 to display the second prompt message, the smartwatch 10 in the ultra-long battery life mode can display the second prompt message on the UI interface of the smartwatch 10 in the ultra-long battery life mode.

[0140] For example, Figure 6CAn interface 630 of the smartwatch 10 in an ultra-long battery life mode shows a second prompt message. In the interface 630, the second prompt message 631 is displayed: "It is detected that this application depends on other applications. Please install the payment application F in the ultra-long battery life mode. Otherwise, this application cannot be used normally. Do you want to install the payment application F in the smart mode?" to prompt the user that they need to install the payment application F in the smart mode of the smartwatch 10. The user can click on the operation control 632 "Yes" indicating installation to confirm installing the payment application F in the smart mode of the smartwatch 10, or can click on the operation control 633 "No" indicating not to install, and then not install the payment application F in the smart mode of the smartwatch 10.

[0141] S506: The smartwatch 10 detects a fourth operation instruction.

[0142] In some embodiments, in S505, the smartwatch 10 displays a second prompt message. When the user clicks on the operation control 632 "Yes" indicating installation in the second prompt message, the UI interface of the smartwatch 10 in the ultra-long battery life mode can detect the fourth operation instruction generated by the user clicking on the operation control 632.

[0143] S507: The smartwatch 10 switches from the ultra-long battery life mode to the smart mode.

[0144] In some embodiments, since the processors used in the ultra-long battery life mode and the smart mode of the smartwatch 10 are different, when the smartwatch 10 is in the ultra-long battery life mode, the smart mode of the smartwatch 10 is in a non-running state. Therefore, it is necessary to wait until the smartwatch 10 switches from the ultra-long battery life mode to the smart mode before further installing the payment application F corresponding to the smart mode in the smart mode.

[0145] For example, Figure 6D An upward pull interface 640 of the smartwatch 10 in the ultra-long battery life mode is shown. In the interface 640, there are an operation control "Smart Mode" 641 for indicating switching to the smart mode, an alarm control 642, a settings control 643, etc. The user can click on the operation control 641 to switch the smartwatch 10 from the ultra-long battery life mode to the smart mode. When the user clicks on the operation control 641, the application market service can detect that the smartwatch 10 switches from the ultra-long battery life mode to the smart mode. Then, the operations of sending the installation package and the application installation instruction in S507 can be executed.

[0146] In addition, Figure 6EThe figure shows a pull-up interface 650 of the smartwatch 10 in the smart mode. In the interface 650, there are operation controls such as "Ultra-long Battery Life Mode" 651 for indicating the switch to the ultra-long battery life mode, an alarm control 652, a settings control 653, etc. The user can click the operation control 651 to switch the smartwatch from the smart mode to the ultra-long battery life mode.

[0147] S508: The server 30 detects the switch to the smart mode and, in response to the fourth operation instruction, sends an installation instruction and an installation package for installing the application B in the smart mode.

[0148] In some embodiments, in S507, the smartwatch 10 switches from the ultra-long battery life mode to the smart mode. After the server 30 detects that the smartwatch 10 switches from the ultra-long battery life mode to the smart mode, the server 30 can respond to the fourth operation instruction sent by the server 30 in S506, that is, the user determines to install the payment application F in the smart mode of the smartwatch 10. The server 30 can send the installation package of the payment application F for installation in the smart mode to the application market of the smartwatch 10 in the smart mode, as well as an installation instruction for installing the payment application F in the smart mode of the smartwatch 10.

[0149] S509: The smartwatch 10 responds to the installation instruction and installs the application B in the smart mode.

[0150] In some embodiments, through the installation package and installation instruction of the payment application F sent by the server 30 in S508. The application market of the smartwatch 10 in the smart mode can respond to the installation instruction and install it through the installation package of the payment application F sent by the server 30 for installation in the smartwatch 10 in the smart mode.

[0151] In other embodiments, when the smartwatch 10 is in the ultra-long battery life mode, if the smartwatch 10 detects the fourth operation instruction, the server 30 can respond to the fourth operation instruction, send the installation package of the payment application F in the smart mode to the application market of the smartwatch 10, and install it in its application mode without waiting for the smartwatch 10 to switch from the ultra-long battery life mode to the smart mode for installation, which is not limited herein.

[0152] In some other embodiments, when the smartwatch 10 is in the smart mode, if the smartwatch 10 detects an operation instruction for the user to click to install the payment application F, it can directly send an instruction to install the payment application F for use in the ultra-long battery life mode and an instruction to install the payment application F for use in the smart mode to the server 30. Furthermore, the server 30 can send the installation package of the payment application F for use in the ultra-long battery life mode and the installation package of the payment application F for use in the smart mode to the application market of the smartwatch 10 in the smart mode. Then, the application market can install them based on the above two installation packages in their respective applicable modes, which is not limited herein.

[0153] Figure 6F Based on the above Figure 5 described solution, a schematic diagram of a scenario for collaborative installation of the payment application F between the ultra-long battery life mode and the smart mode of the smartwatch 10 is shown. As Figure 6F shown, when the user clicks the operation control 622 in the interface 620 of the application market in the ultra-long battery life mode of the smartwatch 10, the application market in the ultra-long battery life mode of the smartwatch 10 can report the installation information of the payment application F and control the display of a second prompt message 631 on the interface 630 of the smartwatch 10 to prompt the user to also install the payment application F in the smart mode of the smartwatch 10. Thus, when the smartwatch 10 clicks the operation control 641 indicating switching to the smart mode in the pull-up interface 641 in the ultra-long battery life mode, the smartwatch 10 switches to the smart mode. When the server 30 detects that the smartwatch 10 switches to the smart mode, it can determine to install the payment application F in the smart mode based on the user clicking the operation control 641 and send the installation package of the payment application F to the smartwatch 10. Furthermore, the user can search for the payment application F in the smart mode through the application market and can click the operation control 662 indicating installation of the payment application F in the interface 660. Then, the smartwatch 10 in the smart mode can install the payment application F based on the installation package of the payment application F.

[0154] In some other embodiments, after the smartwatch 10 switches to the smart mode, the user can search for the payment application F in the smart mode through the application market and can click the operation control 663 indicating opening the payment application F in the interface 660. Then, the payment application F has been installed in the smart mode of the smartwatch 10, and there is no need for the user to click to install.

[0155] Based on this, when the user uses the payment application F again in the ultra-long battery life mode, it can be directly used without waiting to install its corresponding payment application F in the smart mode.

[0156] Next, in conjunction with the accompanying drawings, the process of how the application market service pre-establishes the association relationship information including the association relationships of each application program in steps S303 and S503 will be specifically introduced.

[0157] Figure 7 A flowchart showing the establishment of an association relationship between application programs by an application market service is shown.

[0158] The specific process includes:

[0159] S701: The application market service receives the binary files of each application program uploaded by the developer.

[0160] The prerequisite for installing an application program is that there is an application program installation package in the application market, and the installation package of the application program installed by the application market is obtained through the application market service, that is, the server 30 mentioned above. Therefore, the developer can put the installation packages of each application program developed according to the development guidance document for distributed application collaboration on the application market service. Among them, the installation package of the application program uploaded by the developer is also a binary file of the application program, which can also be called an executable file. By installing and running the binary file of the application program, the application market can install the application program into the terminal device.

[0161] The following introduces the process in which the developer needs to configure relevant information in the application program binary file:

[0162] In some embodiments, if it is necessary to achieve the collaborative installation of different application programs on the same terminal device or different terminal devices, distributed components, or what can be called distributed middleware, need to be declared in the binary file of the application program. That is, a multi-device application communication support package needs to be integrated into the binary file of the application program, which includes the distributed components used by the application program, such as the "wear engine" communication support package.

[0163] Therefore, during the development stage of the application program, the developer can integrate a multi-device application communication support package into the binary file of the application program, that is, declare the distributed components used by the application program under the script file "build.gradle" in the binary file. For example, declare that the distributed component used by the application program under "build.gradle" in the application program binary file is the wearable ability component "wear engine", etc.

[0164] It can be understood that the distributed components used by application programs under different systems are different. When the system is the Android system, the distributed components used by application programs under the Android system can be: the Android Wear component "androidwearable", etc.; when the system is the HarmonyOS system, the distributed components used by application programs under the HarmonyOS system can be: the wearable ability component "wear engine", etc.; when the system is the iOS TM system, iOS TMThe distributed components used by the application under the system may include: development integration tool components such as "watch kit", etc. In addition, in the embodiments of the present application, the system applied by the application and the types of distributed components used by the application under each system are not limited.

[0165] In some embodiments, when different applications are collaboratively installed on the same terminal device or different terminal devices, the distributed API provided by each system platform can be utilized, that is, a communication interface. This distributed API can be used for communication between different applications on the same or different terminal devices. The distributed API can be integrated into the binary file of the application, that is, the installation package, in the form of a binary capability component. For example, the distributed API for application - to - application communication is "p2pClient".

[0166] In addition, information such as the installation package name of other applications that can communicate with the application in a peer - to - peer manner can be explicitly specified at the code level of the binary file of the application. Furthermore, the application market service of the terminal device can call information such as the installation package name of other applications that can communicate with it in a peer - to - peer manner based on its distributed API. It can be understood that if the distributed API is not integrated into the application binary file, the installation package name and other information of the application that can communicate with the application in a peer - to - peer manner can also be directly obtained through the code information of the binary file, which is not limited here.

[0167] For example, when application A and application B are collaboratively installed on the same terminal device or different terminal devices, the distributed API for application - to - application communication: "p2pClient" can be integrated into the binary file of application A, that is, the installation package; and the installation package name and other information of application B that can communicate with application A in a peer - to - peer manner are explicitly declared in the binary file of application A. Furthermore, the application market service of the terminal device can then call the installation package name and other information of application B through the distributed API "p2pClient".

[0168] Therefore, during the development stage of the application, developers can integrate the distributed API applied by the application into the binary file of the application in the form of a binary capability component, and explicitly specify information such as the installation package name of other applications that can communicate with the application in a peer - to - peer manner in the binary file of the application.

[0169] The following introduces the process of developers setting relevant application information in the binary file of the application before the application market service establishes the association relationship between different applications on different terminal devices (such as smart watches and mobile phones) based on each application uploaded by the developer.

[0170] In some embodiments, when the system applied by the application developed by the developer is HarmonyOS TM system, relevant information can be explicitly specified in the binary file of the application. For example, Figure 8A shows a schematic diagram of the code information in the binary file of an application under HarmonyOS TM system. The code information 810 in Figure 8A can indicate that the distributed component used by the application under HarmonyOS TM system is "wear engine". The code information 811 in Figure 8A can illustrate that the distributed API used by the application is "p2pClient". The code information 812 in Figure 8A can illustrate that the application can call the installation package name of the application that can communicate with the application through the distributed API "p2pClient", where "peerPkgName" refers to the installation package name of the application that can communicate with the application.

[0171] In other embodiments, when the system applied by the application developed by the developer is Android TM system, relevant information can be explicitly specified in the binary file of the application. For example, Figure 8B shows a schematic diagram of the code information in the manifest file of an Android application in the binary file of the application under Android TM system. The code information 813 in Figure 8B can indicate that the application is defined as a non-independent application in the manifest file of the Android TM application (android app).

[0172] When the application is depended on by other applications, the type of terminal device deployed by the application and the name of the distributed capability on which the application is depended on the terminal device can be explicitly declared in the binary file "res / values / wear.xml" of the application. And the type of terminal device deployed by other applications that can communicate with the application and the distributed capabilities, etc. can be explicitly specified. For example, Figure 8C shows a schematic diagram of the code information of a manifest file, Figure 8C the code information 814 in which indicates that the type of terminal device deployed by other applications that can communicate with the application is a smart wearable device; Figure 8C the code information 815 in which indicates that the name of the distributed capability on which the application is depended on the terminal device is "android wear", that is, it shows that the distributed component used by the application under the Android system is "android wear". ​​​​​​​​

[0173] When the application depends on other applications, the developer can declare the name of the distributed capabilities it depends on at the code level of the binary file of the application, and can query other applications that support the distributed capabilities it depends on through the getCapability method, that is, "getCapabilityClient(context)", where context can represent the name of the distributed capabilities to be queried. For example, the query code can be "getCapability(String capability, int nodeFilter)". It can be understood that the distributed capabilities (capability) of the application declared here can be consistent with the strings of the distributed capabilities declared in the binary file "res / values / wear.xml" of other applications that the application depends on. Refer to Figure 8D the schematic diagram of the scenario shown. Assuming that the application A in the terminal device A depends on the application B in the terminal device B, the distributed capabilities it depends on can be queried by explicitly calling the getCapability(capability name) method in the binary file of the application A, and the distributed capabilities that it has and can be depended on by the application A are declared under the "android_wear_capabilities" node in the binary file "res / values / wear.xml" of the application B. For example, the distributed capability is "android wear".

[0174] In some other embodiments, when the application developed by the developer needs to be applied to the ios TM system, relevant information can be explicitly specified in the binary file of the application. The binary file of the application under the ios TM system is Info.plist, and Info.plist can be used to store the xml file of the relevant configuration information of the application under the ios TM system. For example, Figure 8E shows a schematic diagram of the code information of the application in the binary file Info.plist of the application under the Android system. Figure 8E The code information 816 in it can represent that the distributed component used by the application under the ios TM system is "watch kit". Figure 8E The code information 817 in it can illustrate that the application on the mobile phone side that can communicate with the application in a peer-to-peer manner is also configured with "watch kit".

[0175] The following describes the process in which a developer sets relevant configuration information in the binary file of an application before the application market service of a smartwatch establishes the association relationship of each application based on the applications listed on the market in different modes of the same terminal device (such as the smart mode and the ultra-long battery life mode of the smartwatch).

[0176] It can be understood that the co-installation of applications in the two operating modes of the smartwatch can be based on the dual-core communication capability of the smartwatch. Therefore, a dual-core communication support package for supporting the smartwatch to perform dual-core communication can be integrated into the binary file of the smartwatch. It can also be called an android archive (AAR) package, simply referred to as an AAR package.

[0177] In some embodiments, when the application developed by the developer needs to be applied in different modes of the smartwatch, relevant information can be explicitly specified in the binary file of the application. For example, in the build.gradle file under the binary file of the application, the distributed component package name: "HwWatchSystemServerClient" is referenced to indicate that the application can support dual-core communication. The statement can be "implementation(\"com.huawei.watch.hws:HwsClient:100.x.x.x\")" and so on.

[0178] In addition, in the binary file of the application, it can also be declared that the installation package name of the application that can perform peer-to-peer communication with this application can be specified by calling the interface Init (peer package name) for dual-core communication. For example, the corresponding code information can be "static void init(Context context,java.lang.String...commuList)", where "commuList" can be defined as the installation package name of the peer application.

[0179] It can be understood that in the embodiments of the present application, the relevant information of the dependent or peer-to-peer communication application can be declared statically or dynamically in the binary file of the application, which is not limited herein. Furthermore, the application service can identify and establish the association relationship between these applications before the application is installed.

[0180] S702: The application market service reads the binary files of each application and extracts the key features of each application.

[0181] In S701, the application service has received the binary files of each application. Further, the application market service can read the binary files of each application and extract the key features of each application.

[0182] In some embodiments, the key features may refer to the distributed components mentioned in S701 above: "wearengine", "android wearable", "watch kit", etc., where different distributed components correspond to different distributed capabilities. Extracting the key features from the application installation package means obtaining the distributed components used by the application by reading the binary file of the application, where the distributed components can indicate the distributed capabilities that the application has or depends on.

[0183] In other embodiments, the key features may refer to the distributed communication interface APIs such as "p2pClient" and "Init" mentioned in S701 above, which may be applied in distributed communication.

[0184] S703: The application market service establishes associations between the applications based on key features of the applications and stores the associations.

[0185] In step S702, the application market service has obtained the key features of each application by reading the binary files of the application. Further, association relationships between the applications can be established based on the key features.

[0186] The specific process of establishing associations between applications in the App Market service is as follows:

[0187] The application market service reads the binary file of the application, that is, the installation package of the application, and determines whether the installation package of the application contains a distributed component (also known as distributed middleware). If it is determined that the installation package of the application contains a distributed component, the corresponding permission application or distributed communication API can be directly obtained based on the distributed component, and the installation package name of other applications that can communicate with the application through the permission application or distributed communication API corresponding to the distributed component can be obtained. Among them, the device type on which the application is deployed can be determined by information such as the installation package name, and the permission application corresponding to the distributed component refers to the name of the installation package of the application that can be obtained through the distributed component. Among them, the application's installation package name and permission application information are application information that developers will reserve when applying for application-related permissions in the process of listing the application.

[0188] Furthermore, based on the installation package name of the application and the installation package names of other applications that can communicate with the application in a peer-to-peer manner, determine the device types on which they are respectively deployed, the permission information they apply for, the types of distributed components, and set whether the two applications are in a strong association relationship. If the two applications are respectively deployed on two different terminal devices, or in different modes of the same terminal device, and their respective applied permission information is the same, for example, they support Bluetooth communication or near field communication (NFC) communication, and their respective distributed component types are both "wear engine", then it can be determined that they are in a strong association relationship based on the same permission information and distributed component types. If only one of the applied permission information and the distributed component types is the same item, then it can be set as a non-strong association relationship.

[0189] In addition, if there is no distributed middleware in the application installation package, the application binary file can be read to determine the system distributed communication API used by the application, and based on the information of the API calls, determine the installation package names of other applications that can communicate with the application in a peer-to-peer manner. Furthermore, based on the installation package name of the application and the installation package names of other applications that can communicate with the application in a peer-to-peer manner, determine the types of the terminal devices on which they are respectively deployed, the permission information they apply for, and the types of distributed interfaces. If their respective applied permission information and the types of distributed interfaces are the same, for example, their respective applied permission information both supports Bluetooth communication or NFC communication, and the types of the distributed communication APIs of their respective applications are both "p2pClient", then the two applications can be set as being in a strong association relationship. If only one of their applied permission information and the types of distributed components is the same item, then it can be set as a non-strong association relationship.

[0190] In some embodiments, the mobile-side application market service can determine that the distributed component declared in the binary file of the mobile-side application is "wear engine" by reading the binary file of the mobile-side application. If it is shown that the mobile-side application has distributed capabilities, then the corresponding permission application or distributed communication API can be determined based on the distributed component "wear engine", and based on the corresponding permission application or distributed communication API, the installation package name of the application that can communicate with the mobile-side application in a peer-to-peer manner can be obtained. For example, by calling the distributed communication API "p2pClient", the installation package names of the applications that can communicate with the mobile-side navigation application G in a peer-to-peer manner can be obtained as: "GForLiteWearable.hap", "GForWearable.hap", where G can refer to the name of the navigation application, LiteWearable can represent a lightweight wearable device, such as a sports watch; Wearable can represent a smart wearable device, such as a smart watch.

[0191] The installation package name of the mobile-side application is "GForPhone", indicating that the mobile-side application is the mobile-side navigation application G. When the application market service reads the binary file of the mobile-side navigation application G and obtains the installation package name of the peer application as "GForLiteWearable.hap" by calling the distributed communication API "p2pClient", it can be determined that the type of the terminal device on which the peer application is deployed is a sports watch, and the distributed component of the navigation application G on the sports watch side is "wear engine". In addition, the permission information applied for by the mobile-side navigation application G and the navigation application G on the sports watch side can be to support Bluetooth communication or NFC communication, that is, the distributed component types and the applied permission information of the two applications are the same. Also considering that the device capabilities of some current sports watches do not support an independent application market on the watch side and do not support networking, etc., it can be determined that the navigation application G on the sports watch side needs to rely on the mobile-side navigation application G to be used, that is, the navigation application G on the sports watch side and the mobile-side navigation application G have a strong dependency relationship.

[0192] When the application market service reads the binary file of the navigation application G on the mobile phone side and obtains the installation package name of the application on the peer side as "GForWearable.hap" by calling the distributed communication API "p2pClient", it can be determined that the type of the terminal device where the peer application is deployed is a smart watch. The distributed component of the navigation application G on the smart watch side is "wear engine". In addition, the permission information applied for by the navigation application G on the mobile phone side and the navigation application G on the smart watch side can support Bluetooth communication or NFC communication. Also considering that the current device capabilities of the smart watch are: not supporting independent navigation functions, etc., it can be determined that the navigation application G on the smart watch side needs to rely on the navigation application G on the mobile phone side to be used, that is, the navigation application G on the smart watch side and the navigation application G on the mobile phone side are in a strong association relationship, which can also be called a strong dependence relationship. In addition, the application market service can store this association relationship.

[0193] Based on the above, the application market services of different terminal devices can store the established association relationships of the navigation application G in different terminal devices. For example, as shown in Table 1, the installation package name of the navigation application G on the mobile phone side is "GForPhone", the installation package name of the navigation application G on the sports watch side is "GForLiteWearable.hap", and the installation package name of the navigation application G on the smart watch side is "GForWatch.hap". And the application program association relationships generated by the application market service can be: the navigation application G on the sports watch side strongly depends on the navigation application G on the mobile phone side; the navigation application G on the smart watch side strongly depends on the navigation application G on the mobile phone side.

[0194] Table 1

[0195]

[0196]

[0197] Based on this, the process based on the above can be executed based on the established association relationships of the application programs. Figure 3 In this way, the application market service can push the navigation application G on the mobile phone side to the mobile phone side for installation based on the cloud. Realize the linked installation, that is, the collaborative installation, of the navigation application G on the watch side and the navigation application G on the mobile phone side. Instead of prompting the user to install the navigation application G on the mobile phone side when the user opens the navigation application G on the watch side to prepare for use. Improve the installation efficiency of the application program and the user experience.

[0198] It can be understood that the above process of the application market service establishing the association relationship taking the navigation application G as an example is only an exemplary illustration. In other embodiments, the application market service can also establish the association relationships of other different application programs, which are not limited herein.

[0199] In some other embodiments, the application market service on the smartwatch side can read the binary file of payment application F in the smart mode of the smartwatch, determine that the distributed component declared in the binary file of payment application F in the smart mode of the smartwatch is the dual-core distributed communication component CommuX, indicating that it has dual-core distributed capabilities. Then, based on the dual-core distributed communication component CommuX, it can determine its corresponding permission application or dual-core distributed communication API, and based on the corresponding permission application or dual-core distributed communication API, obtain the installation package name of the application program that can communicate with payment application F in the smart mode in a peer-to-peer manner. For example, by calling the dual-core distributed communication API "Init", the installation package name of the application program that can communicate with payment application F in the smart mode in a peer-to-peer manner can be obtained as "FpayWearableforPSM.hap", where Fpay can represent the name of the application program, and WearableforPSM can represent the ultra-long battery life mode of the smartwatch.

[0200] The installation package name of the application program in the smart mode of the smartwatch is "FWearable.hap", indicating that the application program in the smart mode of the smartwatch is payment application F in the smart mode. When the application market service reads the binary file of payment application F in the smart mode of the smartwatch and, by calling the dual-core distributed communication API "Init", obtains the installation package name of the application program that can communicate with payment application F in the smart mode in a peer-to-peer manner as "FpayWearableforPSM.hap", it can then determine that the type of the terminal device where the peer application program is deployed is the ultra-long battery life mode of the smartwatch, and the distributed component of payment application F on the smartwatch side is CommuX. In addition, the permission applications corresponding to payment application F in the ultra-long battery life mode of the smartwatch and payment application F in the smart mode of the smartwatch can be to support Bluetooth communication or NFC communication, that is, the types of distributed components and the permission information applied for by the two application programs are the same. Also considering that the device capabilities in the ultra-long battery life mode of the smartwatch are not supporting independent installation of application programs, no network connection, etc., that is, the prerequisite for using payment application F in the ultra-long battery life mode of the smartwatch is to install payment application F in the smart mode of the smartwatch, it can be determined that payment application F in the ultra-long battery life mode of the smartwatch and payment application F in the smart mode of the smartwatch have a strong association relationship, which can also be called a strong dependency relationship. In addition, the application market service on the smartwatch side can store this association relationship.

[0201] Based on the above, the app market service for the same terminal device can store the established associations between payment applications F in different modes of the same terminal device. For example, as shown in Table 2, the installation package name of payment application F in the smartwatch's ultra-long battery life mode is "FpayWearableforPSM.hap," while the installation package name of payment application F in the smartwatch's smart mode is "FpayWearable.hap." Furthermore, the application association generated by the app market service may indicate that payment application F in the smartwatch's ultra-long battery life mode is strongly dependent on payment application F in the smartwatch's smart mode.

[0202] Table 2

[0203]

[0204] Based on this, the above-mentioned Figure 5 For example. When a user installs the installation package of the payment application F in the ultra-long battery life mode of a smartwatch, the application market service can determine that the payment application F has not been installed in the smart mode of the smartwatch. In this case, a prompt message will be displayed in the UI interface in the ultra-long battery life mode of the smartwatch to prompt the user to confirm the linkage installation of the payment application F in the two modes in the smart mode of the smartwatch, otherwise the payment application F in the ultra-long battery life mode will not be able to operate normally. The user can then confirm the linkage installation of the payment application F in the two modes in the smart mode of the smartwatch by clicking the operation control. In this way, the application market service can install the payment application F in the smart mode and the payment application F in the ultra-long battery life mode based on the cloud push in the smart mode of the smartwatch, that is, collaborative installation. This improves the installation efficiency of the application and the user experience.

[0205] The following is based on Figures 9A to 9B , briefly summarizes the process from the stage of pre-establishing application association relationships in the embodiment of the present application to implementing the installation method provided in the embodiment of the present application by utilizing the pre-established application association relationships.

[0206] refer to Figure 9AThe application market service shown establishes a scenario diagram for associated updates of application programs. After a developer uploads the binary file (which can also be called a binary package or an installation package) of application program A that can perform peer-to-peer communication and the binary file of application program B to the application market of a terminal device, the application market service can extract the key features of application program A or application program B by reading the binary file of application program A or the binary file of application program B. The key features can be, for example, the distributed components or distributed communication interfaces (APIs) applied by application program A or application program B. Furthermore, the installation package name of application program B can be obtained based on the distributed components or distributed communication interfaces (APIs) of application program A, or the installation package name of application program A can be obtained based on the distributed components or distributed communication interfaces (APIs) of application program B. In this way, the device types deployed by each of application program A and application program B, the permission information applied for by each, and the types of distributed components or distributed interface types applied by each can be determined through the installation package names of application program A and application program B. If the permission information applied for by application program A and application program B is the same, and the types of distributed components or distributed interface types applied by each are the same, then it can be determined that application program A and application program B have a strong association relationship and are stored.

[0207] Reference Figure 9B The application market service shown is based on Figure 9A The established association relationship of application programs in the figure prompts a scenario diagram for coordinating the installation of different application programs. When a user downloads and installs application program A on terminal device A, the application market service recognizes this information, and then determines based on the pre-established association relationship of application programs that application program B on terminal device B, which is relied on by application program A, is not installed. The application market service then prompts the user on the UI interface of terminal device A to install application program B on terminal device B in an associated manner. Otherwise, the function of application program A on terminal device A will not be available. Based on the user's confirmation of coordinated installation, the coordinated installation of application program A and application program B can be achieved, improving the application installation efficiency and enhancing the user experience.

[0208] Reference Figure 9C The macro scenario diagram shown Figure 9C Combines Figure 9A And Figure 9B Combines to cover the process provided in the embodiments of the present application: from the application market service pre-establishing the association relationship of application programs to using the pre-established association relationship of application programs to implement the installation method provided in the embodiments of the present application.

[0209] Through the above solution, when an application is first installed on a terminal device, the association relationship of the application established in advance by the application market service based on the terminal device can be realized, other applications that have a strong association relationship with the application can be determined, and a prompt message can be displayed on the terminal device to prompt the user to determine whether to synchronize and install other applications that have a strong association relationship with the application on this terminal device or other terminal devices. It can be realized that multiple applications with a strong association relationship can be installed in a linked manner, without waiting for other applications that have a strong association relationship with the application to be installed when the user has installed the application and is ready to use, saving the application installation time and improving the user experience of installing and using applications.

[0210] In addition, based on the installation method provided in the embodiments of the present application, it can be realized that the association relationship between different applications is established by scanning and extracting features such as distributed components and distributed interfaces of the applications in the binary files of the applications, without the need for manual operation intervention; moreover, the features related to the applications identified based on the binary files of the applications are more accurate, the applicable range is wider, and it involves the collaborative installation of applications in a distributed scenario.

[0211] Furthermore, Figure 10 According to some embodiments of the present application, a schematic structural diagram of a terminal device 100 is shown. Based on the terminal device 100, the installation method mentioned in the embodiments of the present application can be realized.

[0212] As Figure 10 shown, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, a communication device 196, 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 acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, a color temperature sensor 180N, etc. Among them:

[0213] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a microcontroller unit (MCU), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors. In some embodiments, the application processor (AP) and the microcontroller unit (MCU) may be applied to the smart watch 10 in the embodiments of the present application, and the AP may run the smart mode of the smart watch 10, and the MCU may run the ultra-long battery life mode of the smart watch 10.

[0214] The controller may generate operation control signals according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0215] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 may save the stored data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0216] In some embodiments, the processor 110 may be used to execute the installation method provided in the embodiments of the present application. After establishing the association relationship of the application program by reading the relevant information in the binary file of the application program, the association relationship of each application program may be stored in the memory. Furthermore, when installing the application program in the terminal device, the association relationship of the application program may be obtained. It can be understood that the processor 110 may include cloud processing, and the memory may include cloud storage.

[0217] The USB interface 130 is an interface that complies with the USB standard specifications. Specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type-C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used to transfer data between the terminal device 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0218] The charging management module 140 is used to receive charging input from a charger. While charging the battery 142, the charging management module 140 can also supply power to the terminal device 100 through the power management module 141.

[0219] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives inputs from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, etc.

[0220] The wireless communication function of the terminal device 100 can be implemented through antenna 1, antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, and the baseband processor, etc.

[0221] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals, that is, wireless carrier information.

[0222] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc. applied to the terminal device 100. The mobile communication module 150 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by antenna 1, filter, amplify, etc. the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through antenna 1 and radiate it out.

[0223] The wireless communication module 160 may provide solutions for wireless communications applied to the terminal device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), near field communication (NFC), global navigation satellite system (GNSS), frequency modulation (FM), infrared (IR), ultra wide band (UWB), etc. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 may receive electromagnetic waves through the antenna 2, filter, amplify, and perform other processing on the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The wireless communication module 160 may also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through the antenna 2 for radiation.

[0224] The terminal device 100 realizes the interface display function through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to execute mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or change the display information.

[0225] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel may adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the first prompt information, the second prompt information, etc. provided in the embodiments of the present application may be displayed based on the display screen 194.

[0226] The camera 193 is used to capture static images or videos.

[0227] The external memory interface 120 can be used to connect to an external memory card, such as a Micro SD card, to implement the storage capacity expansion of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. For example, resource files of system theme elements are saved in the external memory card.

[0228] The internal memory 121 can be used to store computer-executable program codes. The executable program codes include instructions, such as the aforementioned memory 103. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function, etc. The data storage area can store data created during the use of the terminal device 100, such as the control identifier of the security control, the screenshot redrawing policy identifier corresponding to the security control, the patterns, images, texts, etc. corresponding to the screenshot redrawing policy. In addition, the internal memory 121 can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications of the terminal device 100 by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor 110.

[0229] The terminal device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor, etc.

[0230] The touch sensor 180K, also called a "touch control device". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting thereon or nearby. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the terminal device 100, at a different position from the display screen 194. In some embodiments, when the touch screen detects an operation by the user on the touch screen, it can be sent to the processor 110 to trigger the co-installation application program provided by the embodiments of the present application.

[0231] The motor 191 can generate a vibration prompt.

[0232] The indicator 192 can be an indicator light, which can be used to indicate the charging state, the change in battery power, and can also be used to indicate messages, missed calls, notifications, etc.

[0233] The SIM card interface 195 is used to connect the SIM card.

[0234] It can be understood that the structure of the terminal device 100 shown in the embodiments of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0235] The embodiments disclosed in the present application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memories and / or storage elements), at least one input device, and at least one output device.

[0236] The program code can be applied to the input instructions to perform the various functions described in the present application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of the present application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor. The program code can be implemented in a high-level procedural language or an object-oriented programming language in order to communicate with the processing system.

[0237] When needed, the program code can also be implemented in assembly language or machine language. In fact, the mechanisms described in the present application are not limited to the scope of any specific programming language. In any case, the language can be a compiled language or an interpreted language.

[0238] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may be implemented as instructions carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable media. Thus, machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, floppy disks, optical disks, optical discs, compact disc read-only memories (CD-ROMs), magneto-optical discs, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or tangible machine-readable memories for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0239] In the drawings, some structural or method features are shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or ordering may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Additionally, the inclusion of a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0240] It should be noted that each unit / module mentioned in the device embodiments of the present application is a logical unit / module. Physically, a logical unit / module may be a physical unit / module, a part of a physical unit / module, or may be implemented as a combination of multiple physical units / module. The physical implementation manner of these logical units / module themselves is not the most important. The combination of the functions implemented by these logical units / module is the key to solving the technical problems proposed by the present application. In addition, in order to highlight the innovative part of the present application, the above device embodiments of the present application do not introduce units / modules that are not closely related to solving the technical problems proposed by the present application. This does not mean that there are no other units / modules in the above device embodiments.

[0241] It should be noted that in the examples and the specification of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one" does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element. Although this application has been illustrated and described by reference to certain preferred embodiments of the present application, those of ordinary skill in the art should understand that various changes can be made in form and detail without departing from the scope of this application.

Claims

1. An installation method, characterized in that, Applied to a first terminal device, the method includes: Detecting a first installation instruction for a first application; In response to the first installation instruction, downloading an installation package of the first application, and Displaying a prompt message for installing a second application associated with the first application.

2. The method according to claim 1, wherein The prompt message includes a confirmation control; and The method further includes: Corresponding to detecting a first operation of the user on the confirmation control, installing the second application on the first terminal device; or Corresponding to detecting a first operation of the user on the confirmation control, sending a confirmation message, where the confirmation message is used to indicate installing the second application on a second terminal device associated with the first terminal device.

3. The method according to claim 2, wherein Corresponding to detecting a first operation of the user on the confirmation control, sending a confirmation message includes: Sending the confirmation message to a server, where the confirmation message is used to instruct the server to send an instruction for installing the second application and the installation package of the second application to the second terminal device.

4. The method according to claim 1, wherein The displaying a prompt message for installing a second application associated with the first application includes: Corresponding to detecting that the second application is not installed on the first terminal device, controlling the first terminal device to display a first prompt message for installing the second application.

5. The method according to claim 1, characterized in that The first terminal device includes a first processor and a second processor, the computing power of the first processor is greater than that of the second processor, and the terminal device includes a first operating mode corresponding to the first processor and a second operating mode corresponding to the second processor.

6. The method according to claim 1, characterized in that The detecting a first installation instruction for a first application includes: In the second operating mode, detecting a first installation instruction for a first application; and The displaying a prompt message for installing a second application associated with the first application includes: Corresponding to being in the second operating mode: Detecting a first installation instruction for a first application, and confirming whether the second application has been installed on the first terminal device; Corresponding to confirming that the second application is not installed, displaying a second prompt message for installing the second application.

7. The method according to claim 6, wherein It further includes: Corresponding to detecting a second operation of the user confirming to install the second application in the second operating mode, switching the operating mode of the first terminal device to the first operating mode; In the first operating mode, installing the second application.

8. The method according to claim 1, characterized in that The downloading an installation package of the first application in response to the first installation instruction includes: Sending an installation request for the first application to a server; And the method further includes: Receiving display association information from the server, where the association information is sent by the server after determining that there is a second application associated with the first application in response to the installation request for the first application; and The displaying a prompt message for installing a second application associated with the first application includes: In response to receiving the association information, display the prompt information.

9. The method according to claim 8, characterized in that The detecting of the first installation instruction of the first application program includes: Detecting a third operation of the user, where the third operation is used to send an installation request for the first application program to the server.

10. An installation method, characterized in that, Applied to the server, the method includes: Receiving an installation request for a first application program sent by a first terminal device; In response to the installation request, determining that there is a second application program associated with the first application program; Sending association information to the first terminal device, where the association information indicates that installing the second application program is required to install the first application program; In response to the confirmation information sent by the first terminal device, sending an installation package of the second application program.

11. The method according to claim 10, characterized in that, The sending the installation package of the second application program in response to the confirmation information sent by the first terminal device includes: In response to the confirmation information, sending an instruction to install the second application program and the installation package of the second application program to a second terminal device associated with the first terminal device.

12. The method according to claim 11, wherein It further includes: In response to the confirmation information, sending the installation package of the second application program to the first terminal device.

13. The method according to claim 10, characterized in that, It further includes: Establishing an association relationship between the first application program and the second application program.

14. The method according to claim 13, wherein The process of establishing the association relationship between the first application program and the second application program includes: Obtaining a binary file of the first application program, and determining permission application information, distributed component type, or distributed interface type of the second application program based on the binary file of the first application program; Based on the same permission application information and distributed component type of the first application program and the second application program, determining that there is an association relationship between the first application program and the second application program; or, Based on the same permission application information and distributed interface type of the first application program and the second application program, determining that there is an association relationship between the first application program and the second application program.

15. The method according to claim 14, wherein The determining the permission application information, distributed component type, or distributed interface type of the second application program based on the binary file of the first application program includes: Determining a first distributed interface and a first distributed component applied by the first application program based on the binary file of the first application program, and obtaining the installation package name of the second application program through the first distributed interface or the permission application for the first application program corresponding to the first distributed component; Obtaining the permission application information, distributed component type, or distributed interface type of the second application program based on the installation package name of the second application program.

16. A terminal device, characterized in that, It includes: A memory, where the memory includes physical memory and external storage, and is used to store instructions executed by one or more processors of the terminal device; And a processor, which is used to execute the instructions to enable the terminal device to implement the installation method according to any one of claims 1 to 15.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is run by the terminal device, it enables the terminal device to implement the installation method according to any one of claims 1 to 15.

18. A computer program product, characterized in that, Comprising computer programs / instructions which, when the computer program product runs on a terminal device, cause the terminal device to implement the installation method described in any one of claims 1 to 15.

Images