Desktop shortcut processing method and device, equipment, storage medium and computer program product

Abstract

The invention relates to a desktop shortcut processing method and device, equipment, a storage medium and a computer program product. The method comprises the steps of displaying an application program list matched with a logged-in target account in an application page of a simulator in response to an account login operation triggered by a first terminal for the simulator; the simulator is installed on the first terminal, and an application program simulated by the simulator is matched with the second terminal; displaying the shortcut of the target application program represented by the target application identifier on the desktop of the first terminal; the target application identifier is an application identifier which exists in an application program list and represents that the target application program does not display a shortcut on a desktop; and in response to an account logout event for the target account, cancelling displaying the shortcut of the target application program on the desktop of the first terminal. By adopting the method, the security and flexibility of desktop shortcut processing can be ensured.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a desktop shortcut processing method, apparatus, device, storage medium, and computer program product. Background Art

[0002] With the development of personal computers (PCs), the PC and mobile applications can be further integrated, that is, the mobile application (APP) can be run on the PC through an emulator. The emulator is a tool that simulates the operating system of the mobile phone on the PC, so that the application adapted for the mobile phone can be run on the PC. For example, game application 1 is only adapted for the mobile phone. If you need to use game application 1 on a computer, you can open the emulator on the computer and run game application 1 in the emulator on the computer. Currently, in order to quickly access the application, you can use shortcuts to access the application, that is, you can display the shortcut of the mobile application running in the emulator on the PC. However, when the terminal user logs in to the same PC, the same shortcut on the PC will be displayed, which may cause the terminal user who does not have access rights to the application to access the application through the shortcut, thereby affecting the security and flexibility of desktop shortcut processing. Therefore, how to ensure the security and flexibility of desktop shortcut processing is an urgent problem to be solved. Summary of the Invention

[0003] Based on this, it is necessary to provide a desktop shortcut processing method, device, equipment, storage medium and computer program product that ensure the security and flexibility of desktop shortcut processing in order to address the above technical problems.

[0004] In a first aspect, the present application provides a method for processing desktop shortcuts. The method comprises:

[0005] In response to an account login operation triggered on the simulator at the first terminal, a list of applications matching the logged-in target account is displayed on an application page of the simulator; the application list includes at least one application identifier, the application identifier representing an application that has been triggered by the target account at the second terminal, the simulator being installed on the first terminal, and the application simulated by the simulator being compatible with the second terminal;

[0006] Displaying a shortcut of a target application represented by the target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and for which no shortcut is displayed on the desktop;

[0007] In response to an account logout event for the target account, the shortcut of the target application is canceled from being displayed on the desktop of the first terminal.

[0008] In a second aspect, the present application further provides a desktop shortcut processing device. The device comprises:

[0009] An application display module, configured to, in response to an account login operation triggered on the simulator at the first terminal, display a list of applications matching the logged-in target account on the simulator's application page; the application list including at least one application identifier representing an application that has been triggered by the target account at the second terminal, the simulator being installed on the first terminal, and the applications simulated by the simulator being compatible with the second terminal;

[0010] The shortcut display module is used to display the shortcut of the target application represented by the target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and the target application represented by it does not display a shortcut on the desktop

[0011] The shortcut display cancellation module is used to cancel the display of the shortcut of the target application on the desktop of the first terminal in response to an account logout event for the target account.

[0012] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above methods when executing the computer program.

[0013] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the above methods when executed by a processor.

[0014] In a fifth aspect, the present application further provides a computer program product, which includes a computer program that implements the steps of the above methods when executed by a processor.

[0015] The above-mentioned desktop shortcut processing method, apparatus, computer equipment, storage medium and computer program product, for a simulator installed on a first terminal, can, in response to an account login operation triggered for the simulator, display the application that has been triggered on the second terminal and matched with the logged-in target account on the application page of the simulator without the target account actively triggering the operation, and further display a shortcut of the target application represented by the application identifier that does not display a shortcut on the desktop on the desktop of the first terminal, that is, the shortcut can be displayed without the target account actively triggering it, and because the displayed shortcut is a shortcut to an application that is not displayed on the desktop of the first terminal but corresponds to the target account, it is ensured that the displayed shortcut is a shortcut to the application that the target account can access, thereby ensuring the security and flexibility of desktop shortcut processing. And when an account logout event is triggered for the target account, it indicates that the target account has exited the account login of the simulator, and at this time, the shortcut of the target application is canceled from the desktop of the first terminal to prevent accounts that do not have access rights to the target application from accessing the program through the desktop shortcut, further ensuring the security and flexibility of desktop shortcut processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A diagram illustrating an application environment of a desktop shortcut processing method according to an embodiment;

[0017] Figure 2 This is a schematic diagram of a display interface of a mobile client in one embodiment;

[0018] Figure 3 A schematic diagram of a display interface of a PC client in one embodiment;

[0019] Figure 4 A schematic diagram of the display interface of the mobile phone simulator Guest terminal in one embodiment;

[0020] Figure 5 A schematic diagram of a process for displaying and canceling a shortcut on a first terminal in one embodiment;

[0021] Figure 6 1 is a flowchart of a desktop shortcut processing method according to an embodiment;

[0022] Figure 7 A schematic diagram of an account login operation in one embodiment;

[0023] Figure 8 This is a schematic diagram of an interface showing a list of applications matching a logged-in target account on an application page of a simulator in one embodiment;

[0024] Figure 9A schematic diagram of an interface showing an application icon and an application name of an application on an application page of a simulator in one embodiment;

[0025] Figure 10 This is a schematic diagram of an interface for displaying shortcuts to an application on the desktop of a first terminal in one embodiment;

[0026] Figure 11 A schematic diagram of an interface for canceling the display of an existing shortcut of an existing application on the desktop of a first terminal in one embodiment;

[0027] Figure 12 A schematic diagram of an interface for canceling the display of shortcuts in one embodiment;

[0028] Figure 13 A schematic diagram of an interface for canceling the display of a shortcut in another embodiment;

[0029] Figure 14 A schematic diagram of a process for displaying a shortcut of a target application program represented by a target application identifier in one embodiment;

[0030] Figure 15 is a schematic diagram of a movement trajectory in one embodiment;

[0031] Figure 16 A schematic diagram of an interface for adding a shortcut to a target application to the desktop of a first terminal in one embodiment;

[0032] Figure 17 A schematic diagram of a flow chart of displaying a shortcut of a target application program represented by a target application identifier in another embodiment;

[0033] Figure 18 A schematic diagram of a flow chart of displaying a shortcut of a target application program represented by a target application identifier in another embodiment;

[0034] Figure 19 A schematic diagram of an interface showing a shortcut to a target application in one embodiment;

[0035] Figure 20 A schematic diagram of an interface for adjusting and displaying shortcuts of a target application in one embodiment;

[0036] Figure 21 A schematic diagram of a flow chart of displaying a shortcut of a target application program represented by a target application identifier in yet another embodiment;

[0037] Figure 22 A schematic diagram of an interface showing a placeholder shortcut and shortcuts in one embodiment;

[0038] Figure 23A schematic diagram of a process for canceling the display of a shortcut to a target application in one embodiment;

[0039] Figure 24 A schematic diagram of an interface for canceling the display of a shortcut of a target application in response to a shortcut deletion operation in one embodiment;

[0040] Figure 25 A schematic diagram of an interface for canceling the display of a shortcut of a target application in response to a shortcut deletion operation in another embodiment;

[0041] Figure 26 A flowchart of a desktop shortcut process performed by a PC client, a Windows system, and a cloud server in one embodiment;

[0042] Figure 27 This is a sequential flow chart of interaction among a PC client, a Windows system, and a cloud server in one embodiment;

[0043] Figure 28 A schematic diagram of a complete process of a desktop shortcut processing method according to one embodiment;

[0044] Figure 29 is a structural block diagram of a desktop shortcut processing device in one embodiment;

[0045] Figure 30 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0047] With the development of PCs, it is possible to further integrate PC and mobile applications, that is, to run mobile APPs on the PC through an emulator. An emulator is a tool that simulates the operating system of a mobile phone on the PC, making it possible to run applications adapted for the mobile phone on the PC. For example, game application 1 is only adapted for mobile phones. If you need to use game application 1 on a computer, you can open the emulator on the computer and run game application 1 in the emulator on the computer. Currently, in order to quickly access applications, shortcuts can be used to access applications, that is, shortcuts to mobile applications running in the emulator can be displayed on the PC. However, when the terminal user logs in to the same PC, the same shortcut on the PC will be displayed, which may cause terminal users who do not have access rights to the application to access the application through the shortcut, thereby affecting the security and flexibility of desktop shortcut processing. Therefore, how to ensure the security and flexibility of desktop shortcut processing is an urgent problem to be solved.

[0048] To solve the above problems, the present invention provides a desktop shortcut processing method that can ensure the security and flexibility of desktop shortcut processing. The desktop shortcut processing method provided by the present invention can be applied to Figure 1 In the application environment shown, the first terminal 102 is a terminal with a simulator installed, and the application simulated by the simulator is adapted to the second terminal 104, that is, the second terminal 104 can run the application simulated by the simulator, and the first terminal 102 and the second terminal 104 can be connected to each other through a network.

[0049] Specifically, the desktop shortcut processing method provided in an embodiment of the present application is applied to a first terminal 102 installed with an emulator as an example. Specifically, in response to an account login operation triggered on the first terminal for the emulator, the first terminal 102 displays a list of applications matching the logged-in target account on the emulator's application page 106. The aforementioned application list includes at least one application identifier, which represents an application that has been triggered by the target account on the second terminal 104. Furthermore, a shortcut to the target application represented by the target application identifier can also be displayed on the first terminal's desktop 108. The aforementioned target application identifier is an application identifier that exists in the application list and represents a target application for which a shortcut is not displayed on the desktop. After displaying the target application shortcut, the target application shortcut can be removed from the first terminal's desktop 108 in response to an account logout event for the target account. This ensures that the displayed shortcut is a shortcut to the application that the target account can access, and prevents accounts that do not have access rights to the target application from accessing the program through the desktop shortcut, thereby ensuring the security and flexibility of desktop shortcut processing.

[0050] The first terminal 102 may be, but is not limited to, various desktop computers, laptop computers, and tablet computers, and the second terminal 104 may be a smartphone, etc. The desktop shortcut processing method provided in the embodiment of the present application can be applied to various scenarios, including but not limited to cloud technology, and scenarios where simulators are run and managed on a PC.

[0051] Since the desktop shortcut processing method provided in the embodiment of the present application can be applied to the scenario of running and managing the simulator on the PC side, the relevant technical terms are explained below:

[0052] 1. Mobile client. The mobile client can be called Client or user terminal. The mobile client refers to the program that corresponds to the server and provides local services to customers. Therefore, in addition to some applications that only run on the mobile client, the mobile client is generally installed on an ordinary user terminal, so it needs to cooperate with the server to run. The mobile version of the mobile client includes but is not limited to the version running on iOS, Android, and Hongmeng system mobile devices. For ease of understanding, the specific example is Figure 2 The display interface of the mobile client is shown.

[0053] 2. PC client is used to describe the client running on a personal computer. For ease of understanding, the specific Figure 3 The display interface of the PC client is shown.

[0054] 3. Software Development Kit (SDK) can simply provide the development files of Application Programming Interface (API) for a certain programming language.

[0055] 4. Cloud gaming is the use of cloud services deployed in data centers to render game images.

[0056] 5. A cloud application is software that is primarily accessed through the Internet, so this means that at least part of it is managed by a server (rather than by the user's local computer).

[0057] 6. Android is an open-source operating system based on the Linux kernel, primarily used for mobile devices (such as smartphones and tablets) and other embedded devices. Therefore, the Android system provides an application framework that allows developers to build various applications and games.

[0058] 7. The Android System Server is a core component of the Android operating system, responsible for launching and managing system-level services. These services support various system functions, such as application management, window management, and resource management. The System Server is created by the Zygote process during system startup and runs as the system user.

[0059] 8. Mobile applications generally refer to mobile apps. In this embodiment, mobile applications specifically refer to apps in the Android system. In the Android system, the package name of a mobile application is a string that uniquely identifies the application. The package name is typically expressed in reverse domain name notation, for example, com.example.myapp. The package name is important in the Android system because it not only distinguishes different applications but also generates the application's internal file and directory structure.

[0060] 9. Executable (EXE) programs. An EXE program under the Windows operating system is a special file format used to store programs that run on the Windows operating system. An EXE file contains the program's machine code, resources (such as icons, strings, images, etc.), and other metadata. When a user double-clicks an EXE file or runs it from the command line, the Windows operating system starts a new process to execute the program. In this embodiment, the application market and the mobile phone simulator host are both EXE programs.

[0061] 10. A virtual disk image (VDI) file is a virtual disk image file format, mainly used in virtual machine software. A VDI file can be regarded as a digital copy of a physical disk. It contains all the data of a virtual disk, including partitions, file systems, files, and directories.

[0062] 11. Mobile Simulator Application: A software tool used to simulate the operating environment of a mobile device on a computer. It allows users to experience mobile applications without actually owning a mobile device. It mainly includes an application market program, a mobile simulator host, and a mobile simulator guest. In this embodiment, the scenario is that a user runs the Android system on a Windows computer, downloads an Android application, installs it, and opens it for normal use.

[0063] 12. The application market program refers to the software program protected in this embodiment. Users can search and download software. At the same time, in this application market program, the running status of the mobile phone simulator Host and the mobile phone simulator Guest can be managed.

[0064] 13. The mobile phone simulator host refers to the simulator software itself, along with its supporting hardware abstraction layer, operating system, and user interface components, running on a computer. The host is responsible for creating and managing the virtual phone environment (the guest) and provides a series of tools and interfaces for users to interact with the virtual phone. The host described in this embodiment is a Windows-based PC software.

[0065] 14. The Guest end of the mobile phone simulator refers to the virtual mobile phone environment created by the simulator software on the computer. In this environment, you can install and run mobile phone applications, perform various operations and experiences, just like using a real mobile phone. The Guest end described in this embodiment is an Android system based on the vbox virtualization solution, which is expressed as a virtual desktop infrastructure (VDI) file. It complies with the VDI file format specification. The Host end loads this VDI file to load and run this VDI file, hereinafter referred to as the Guest end. For ease of understanding, specifically as follows Figure 4 The display interface of the mobile phone simulator Guest side is shown.

[0066] 15. Cross-platform application distribution refers to distributing applications to different platforms and devices, such as distributing mobile applications to PCs.

[0067] 16. Single package: A ready-to-use program package. This refers to packaging an Android application into an executable file so that it can run on different platforms, such as a PC client.

[0068] The following describes the process of displaying and canceling shortcuts for the target account on the first terminal. Figure 5As shown, after the target account triggers an account login operation for the simulator on the first terminal, the target account's account login request is sent to the cloud server via the first terminal, so that the cloud server, in response to the account login request, returns a list of applications matching the target account and is able to obtain the installed applications that have been installed for the simulator on the first terminal through local information. After the target account completes the account login operation, the first terminal compares the installed applications with the applications represented by the application identifiers in the application list. The following describes different situations: 1. If the target application identifier representing the target application is included in the application list and the list of installed applications adapted for the simulator includes the target application, a shortcut to the target application is displayed on the desktop of the first terminal. 2. If the target application identifier representing the target application is included in the application list but the list of installed applications adapted for the simulator does not include the target application, the target application adapted for the simulator is first installed on the first terminal and a shortcut to the target application is displayed on the desktop of the first terminal. 3. If the application list does not include the existing application, the existing shortcut to the existing application is removed from the desktop.

[0069] The following will describe in detail how to process desktop shortcuts, specifically through the following examples: In one embodiment, Figure 6 As shown, a desktop shortcut processing method is provided, which is applied to Figure 1 The first terminal 102 in the example is used for explanation. The first terminal 102 is a terminal with an emulator installed, and the application simulated by the emulator is adapted to the second terminal 104. It is understood that the method can also be applied to a system including the first terminal 102 and the second terminal 104, and is implemented through interaction between the first terminal 102, the second terminal 104 and the cloud server. In this embodiment, the method includes the following steps:

[0070] Step 602: In response to an account login operation triggered on the simulator at the first terminal, a list of applications matching the logged-in target account is displayed on the application page of the simulator; the application list includes at least one application identifier, which represents an application triggered on the second terminal by the target account. The simulator is installed on the first terminal, and the application simulated by the simulator is adapted to the second terminal.

[0071] The "account login operation" describes logging into an account on the simulator, so that the simulator runs applications compatible with the second terminal 104 on the first terminal 102. Thus, the application lists are associated and matched with the accounts. For example, application list A1 is associated and matched with account B1, application list A2 is associated and matched with account B2, and application list A3 is associated and matched with account B3. In other words, if the account login operation specifically involves logging into account B1, account B1 can be determined to be the target account, and application list A1 associated and matched with account B1 is the application list that matches the target account.

[0072] Based on this, since an application refers to a computer program for completing one or more specific tasks, and an application runs in user mode and can interact with the user, the application list cannot directly include the application, that is, the application list includes at least one application identifier, and the application identifier in the application list can be in the form of text, picture, or any combination thereof, and the specific application identifier represents the program function of the application running on the second terminal, then the application identifier specifically represents the program function of the application on the mobile phone, and the application in the embodiment of the present application can be an application running directly on the second terminal, or a light application running through an application installed on the second terminal, such as a mini-program. Since the application list is associated with an account in the embodiment of the present application, the application identifier included in the application list that matches the target account at least represents the application triggered by the target account in the second terminal, that is, the mobile phone application that the target account has triggered to interact. For example, the application list A1 associated with account B1 in the above example is further introduced as the application list matching the target account. If the application list A1 includes application identifier C1, application identifier C2 and application identifier C3, and application identifier C1 is used to represent application 1, application identifier C2 is used to represent application 2, and application identifier C3 is used to represent application 3.

[0073] Specifically, when the target user needs to run an application adapted to the second terminal (i.e., a mobile application) on the first terminal, the target user needs to trigger the account login operation of the target account for the simulator on the first terminal. The following describes how to trigger the account login operation of the target account for the simulator. In a specific embodiment, the account login operation triggered for the simulator includes one of the following: when the first terminal is started, starting the simulator and synchronously triggering the account login operation for the simulator; or, in response to the start operation of the simulator in the first terminal, triggering the account login operation for the simulator.

[0074] Specifically, before the target account was closed for the last time on the first terminal, an account login operation for the simulator had been performed. That is, based on the fact that the account login for the target account has been completed on the first terminal, when the first terminal is started, the simulator can be started and the account login operation for the simulator can be triggered synchronously, thereby completing the account login operation for the target account on the simulator. That is, when the first terminal is started, the simulator is started by default and the target account is automatically logged in.

[0075] Alternatively, in response to the start-up operation of the simulator in the first terminal, the account login operation for the simulator is triggered, that is, the first terminal first needs to display the application page of the simulator on the desktop of the first terminal, and trigger the account login control displayed on the application page of the simulator to display the account login interface on the application page of the simulator. At this time, after the target user enters and confirms the login information of the target account on the account login interface, the account login operation for the target account is triggered. The aforementioned login information can be the account number and password of the target account, or other account information associated with the target account, which is not limited here. For ease of understanding, Figure 7 The account login operation shown is used as an example to illustrate. Figure 7 In the figure (A), the application page 702 of the simulator is displayed on the desktop 701 of the first terminal, and the account login control 703 is displayed on the application page 702. After the account login control 703 is triggered, Figure 7 In Figure (B), an account login interface 704 is displayed on the application page 702 of the simulator displayed on the desktop 701 of the first terminal. After the login information of the target account is input and confirmed in the account login interface 704, the account login operation of the target account is triggered. That is, the account name and password of the target account can be input in the account login interface 704 to trigger the account login operation, or the account login operation can be triggered by other login methods in the account login interface 704, which is not limited here.

[0076] Furthermore, in response to the account login operation triggered on the simulator at the first terminal in the aforementioned manner, the first terminal will display a list of applications matching the logged-in target account on the simulator's application page, and specifically, display an application icon of the application represented by the application identifier in the list of applications matching the logged-in target account on the simulator's application page. That is, by performing an interactive operation (such as a click operation, a double-click operation, etc.) on the application icon of the application in the simulator, the application can be opened and run through the simulator. The following details the process of determining the application represented by the application identifier in the list of applications matching the target account, and the triggering of the target account on the second terminal can be: the target account is running on the second terminal, the target account is logged in on the second terminal, and the target account performs an interactive operation on the second terminal, etc., which are not limited here.

[0077] Because application lists are associated with accounts, the application identifiers in the application lists matching different accounts can be different, although they can also be the same in actual applications. Therefore, after logging in with different accounts, the application icons representing the applications represented by the application identifiers in the application lists matching the logged-in target account will also be different on the simulator's application page. For example, application list A1 includes application identifiers C1, C2, and C3, while application list A1 includes application identifiers C1, C3, C4, and C5.

[0078] For ease of understanding, Figure 8 The interface diagram of the application list matching the logged-in target account in the application page of the simulator is shown. If the target account is account B1 matching the application list A1, then when the account login operation is specifically for logging in to account B1, as shown in FIG. Figure 8 As shown in FIG. 8A , the simulator's application page 800 displays an application list A1 matching account B1, in which application icon 801 for application 1 represented by application identifier C1, application icon 802 for application 2 represented by application identifier C2, and application icon 803 for application 3 represented by application identifier C3. If the target account is account B2 matching application list A2, then when the account login operation is specifically for account B2, as shown in FIG. Figure 8 As shown in the figure (B), in the application page 800 of the simulator, the application list A2 matching the account B2 displays the application icon 801 of application 1 represented by application identifier C1, the application icon 803 of application 3 represented by application identifier C3, the application icon 804 of application 4 represented by application identifier C4, and the application icon 805 of application 5 represented by application identifier C5.

[0079] And in actual application, on the basis of displaying the application icon of the application, the application name of the application can also be displayed, that is, in the application page of the simulator, the application list matching the logged-in target account is displayed, the application icon and application name of the application represented by the application identifier are displayed. Figure 8 The interface example shown in Figure (A) is further introduced. Figure 9As shown, in the application list A1 matching the account B1 displayed on the application page 900 of the simulator, the application identifier C1 represents the application icon 901 and the application name "Application 1" of application 1, the application identifier C2 represents the application icon 902 and the application name "Application 2" of application 2, and the application identifier C3 represents the application icon 903 and the application name "Application 3" of application 3.

[0080] Since the application list includes at least one application identifier, and the application identifier represents an application that has been triggered on the second terminal through the target account, the following details the process of determining the application represented by the application identifier in the application list that matches the target account. In a specific embodiment, the application represented by the application identifier in the application list includes at least one of the following: at least one application that was last triggered by the target account on the second terminal; or, the application that meets the first filtering condition and is triggered the most times by the target account on the second terminal within a preset time interval; or, the application that meets the second filtering condition and is triggered the most times within a preset time interval.

[0081] Specifically, as can be seen from the above introduction, the triggering of the target account on the second terminal can be the target account running on the second terminal, the target account logging in on the second terminal, and the target account performing interactive operations on the second terminal, etc., so before the target account logs in to the simulator installed in the first terminal, it determines at least one application that was last triggered on the second terminal, and then adds the application identifier representing the aforementioned application to the list of applications that match the target account. In other words, the applications run by the target account in the second terminal, the applications logged in by the target account, and the applications interactively operated by the target account can all be matched with the target account. For example, if the target account last logged in to application 1 on the second terminal and ran application 2, then the application identifier C1 representing application 1 and the application identifier C2 representing application 2 can be added to the list of applications that match the target account.

[0082] Furthermore, the applications that meet the first screening condition and are triggered the most times by the target account on the second terminal within a preset time interval and meet the first screening condition are added to the applications represented by the application identifier in the application list matching the target account. The aforementioned preset time interval can be 1 day, 3 days, 1 week, etc., and the first screening condition can be the maximum value of the most triggered times, or the top N values of the most triggered times, etc., wherein N is a positive integer greater than or equal to 2, which is not limited here. Therefore, the applications that meet the first screening condition can be single or multiple. For ease of understanding, taking the preset time interval of 1 week as an example, that is, the maximum number of times application 1 is triggered by the target account on the second terminal (here the triggering can be login, running, interactive operation, etc.) within 1 week is 10 times, the maximum number of times application 2 is triggered by the target account on the second terminal within 1 week is 8 times, the maximum number of times application 3 is triggered by the target account on the second terminal within 1 week is 12 times, and the maximum number of times application 4 is triggered by the target account on the second terminal within 1 week is 2 times.

[0083] If the first filtering condition is the maximum value of the most triggered times, then it can be determined that the maximum value of the most triggered times is 12 times, that is, application 3 is determined to be the application that matches the target account, and application identifier C3 representing application 3 is added to the list of applications that match the target account. If the first filtering condition is the first two values of the most triggered times, applications 1 to 4 are sorted by the maximum number of triggered times, and the first two values in the sorting result, namely 10 times and 12 times, are selected. In other words, both application 1 and application 3 are determined to be applications that match the target account, and application identifier C1 representing application 1 and application identifier C3 representing application 3 are added to the list of applications that match the target account.

[0084] Secondly, it is also possible to consider applications that have been triggered on the mobile phone, such as adding applications that have been triggered a number of times within a preset time interval that meet the second filtering condition to the application list matched with the target account, represented by the application identifier. The aforementioned preset time interval can be 1 day, 3 days, 1 week, etc., and the second filtering condition can be the maximum value of the number of triggers, or the first N values of the number of triggers, etc., where N is a positive integer greater than or equal to 2, which is not limited here. Therefore, the application that meets the second filtering condition can be single or multiple. For ease of understanding, taking the preset time interval of 1 week as an example, that is, the number of times application 1 is triggered within 1 week is 150, the number of times application 2 is triggered by the target account on the second terminal within 1 week is 80, the number of times application 3 is triggered by the target account on the second terminal within 1 week is 200, the number of times application 4 is triggered by the target account on the second terminal within 1 week is 30, and the number of times application 5 is triggered by the target account on the second terminal within 1 week is 210.

[0085] If the second filtering condition is the maximum value of the number of times triggered, then the maximum value of the number of times triggered can be determined to be 210. In other words, Application 5 can also be determined as the application that matches the target account, and Application ID C5 representing Application 5 is added to the list of applications that match the target account. If the second filtering condition is the top 3 values of the number of times triggered, the number of times triggered for Applications 1 to 5 is sorted, and the top 3 values in the sorted results, namely 210, 200, and 150, are selected. In other words, Applications 1, 3, and 5 are all determined to be applications that match the target account, and Application ID C1 representing Application 1, Application ID C3 representing Application 3, and Application ID C5 representing Application 5 are added to the list of applications that match the target account.

[0086] It is understood that the application represented by the application identifier in the list of applications matching the target account may also be at least one application triggered by the second terminal through the target account within a preset time interval. For example, if the target account logged into application 1 and clicked on application 3 through the second terminal within one day, application identifier C1 representing application 1 and application identifier C3 representing application 3 may also be added to the list of applications matching the target account.

[0087] In actual applications, the list of applications matching the target account is constructed by a cloud server that has a communication connection with the first terminal and the second terminal. In the event that there are duplicate applications identified by the aforementioned multiple application identification methods, the cloud server can merge the same applications, or compare the version numbers of applications with the same application identifier to retain the application with the latest version number under the same application identifier. The application list can also be set with a quantity threshold, which represents the maximum number of application identifiers that can be included in the application list. If the number of added application identifiers exceeds the quantity threshold, the application identifiers can be deleted according to the addition time of each application identifier in the application list. That is, if the number of application identifiers in the application list exceeds the quantity threshold, the application identifier with the longest addition time is deleted to avoid repeated push display and historical push display to the target account.

[0088] It is understood that in actual applications, application icons matching applications represented by application identifiers that are not in the list of applications matching the target account can also be displayed on the simulator's application page. In other words, the simulator's application page can include an account page corresponding to the target account, that is, the account page specifically displays the list of applications matching the logged-in target account. The application page can also include an application discovery page and an application recommendation page, and the application discovery page and application recommendation page can display recommended applications based on the simulator's application recommendation method.

[0089] Step 604 : Displaying a shortcut of the target application represented by the target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and for which no shortcut is displayed on the desktop.

[0090] An application shortcut is a method for quickly launching applications provided in the Windows system; that is, a shortcut is a quick link to an application. A target application identifier is an application identifier that exists in the application list and represents a target application for which a shortcut is not displayed on the desktop. In other words, if an application identifier for an application that displays a shortcut exists on the desktop of the first terminal and is in the application list, it is not a target application identifier. For example, if application list A1 matching the target account includes application identifier C1, application identifier C2, and application identifier C3, then if a shortcut for application 1 is displayed on the desktop of the first terminal, that is, application 1 represented by application identifier C1 is displayed on the desktop, application identifier C2 and application identifier C3 are determined as target application identifiers. If a shortcut for application 4 is displayed on the desktop of the first terminal, that is, application 4 represented by application identifier C4 is displayed on the desktop, and application identifier C4 is not in the application list A1 matching the target account, then application identifier C1, application identifier C2, and application identifier C3 are determined as target application identifiers.

[0091] Specifically, on the desktop of the first terminal, a shortcut of the target application represented by the target application identifier is displayed, that is, the shortcut of the application represented by the application identifier that exists in the application list and does not display a shortcut on the desktop is displayed on the desktop of the first terminal, so as to ensure that the shortcuts of the application represented by the application identifier in the application list can be displayed on the desktop of the first terminal. For ease of understanding, the example of the first terminal desktop not displaying any application shortcut is used for explanation. Figure 8 The examples given are further described, such as Figure 10 As shown in the interface diagram of displaying the shortcut of the application on the desktop of the first terminal, if the target account is the account B1 that matches the application list A1, then when the account login operation is specifically to log in to the account B1, as shown in FIG. Figure 10 As shown in Figure (A), on the simulator's application page 1001, application icon 10011 representing application 1 with application identifier C1, application icon 10012 representing application 2 with application identifier C2, and application icon 10013 representing application 3 with application identifier C3 are displayed. Simultaneously, on the first terminal's desktop 1002, shortcut 10021 representing application 1 with application identifier C1, shortcut 10022 representing application 2 with application identifier C2, and shortcut 10023 representing application 3 with application identifier C3 are displayed.

[0092] Similarly, if the target account is account B2 that matches application list A2, then when the account login operation is specifically for account B2, such as Figure 10 As shown in FIG. 2B , in the application list A2 matching account B2, application page 1001 of the simulator displays application icon 10011 representing application 1 with application identifier C1, application icon 10013 representing application 3 with application identifier C3, application icon 10014 representing application 4 with application identifier C4, and application icon 10015 representing application 5 with application identifier C5. Simultaneously, a shortcut 10021 representing application 1 with application identifier C1, a shortcut 10023 representing application 3 with application identifier C3, a shortcut 10024 representing application 4 with application identifier C4, and a shortcut 10025 representing application 5 with application identifier C5 are displayed on the desktop 1002 of the first terminal.

[0093] Similar to displaying the application icon, in addition to displaying the application shortcut, the application name of the application can also be displayed. That is, the shortcut and application name of the target application represented by the target application identifier are displayed on the desktop of the first terminal. The specific display is similar to the previous embodiment and will not be repeated here.

[0094] Considering the need to ensure that shortcuts to applications represented by application identifiers in the application list are displayed on the desktop of the first terminal, if an existing application represented by an existing shortcut on the desktop does not exist in the application represented by the application identifier in the application list, the existing shortcut may be canceled to prevent quick access to applications without account login authorization. This is described in detail below: In an optional embodiment, the desktop shortcut processing method further includes: for an existing application represented by an existing shortcut on the desktop, if the application identifier of the existing application does not exist in the application list, canceling the display of the existing shortcut for the existing application on the desktop.

[0095] Specifically, the first terminal should determine the existing shortcuts displayed on the desktop, and determine the existing applications represented by the existing shortcuts, and then determine whether there is an application identifier of the existing application in the application list matched by the target account logged in by the simulator. If it exists, it is consistent with the above-mentioned embodiment example, and there is no need to adjust the existing shortcuts. If it does not exist, it means that the existing application of the existing shortcut displayed for the target account is an unauthorized application. Therefore, it is necessary to cancel the display of the existing shortcut of the existing application on the desktop of the first terminal. It can be understood that at this time, it is still necessary to display the shortcut of the target application represented by the target application identifier on the desktop of the first terminal. That is, in actual application, the first terminal calls the IShellLink interface to delete the .lnk file of the existing application, and then the first terminal updates the local cache database (such as SQLite) to mark the deleted existing application as "hidden", thereby canceling the display of the existing shortcut of the existing application on the desktop.

[0096] For ease of understanding, Figure 11 The interface diagram shown is a diagram of canceling the display of existing shortcuts of existing applications on the desktop of the first terminal, as shown in FIG. Figure 11 As shown in Figure (A), the desktop 1101 of the first terminal displays the application page 1102 of the simulator, and the desktop 1101 of the first terminal displays a shortcut 11024 of the application 4, that is, the shortcut 11024 is an existing shortcut. If the target account is the account B1 that matches the application list A1, then when the account login operation is specifically for logging in to the account B1, as shown in FIG. Figure 11 As shown in Figure (B), on the simulator's application page 1102, application icon 11011 representing application 1 with application identifier C1, application icon 11012 representing application 2 with application identifier C2, and application icon 11013 representing application 3 with application identifier C3 are displayed. Since application identifier C4 representing shortcut 11024 (i.e., an existing shortcut) for application 4 does not exist in program list A1 matching the target account, shortcut 11024 needs to be canceled on the first terminal's desktop 1101, and shortcut 11021 representing application 1 with application identifier C1, shortcut 11022 representing application 2 with application identifier C2, and shortcut 11023 representing application 3 with application identifier C3 need to be displayed.

[0097] Step 606 : In response to the account logout event for the target account, the shortcut of the target application is canceled from the desktop of the first terminal.

[0098] Among them, the account logout event is used to indicate that the target account has logged out of the simulator account at the first terminal. Specifically, when the first terminal detects the account logout event for the target account, in response to the account logout event for the target account, the shortcut of the target application is canceled from the desktop of the first terminal. That is, the shortcut of the target application displayed on the desktop of the first terminal can be canceled, but the installation package of the target application is not deleted at this time. For ease of understanding, as Figure 12 The shortcut shown is a schematic diagram of the interface for canceling the display, as shown in Figure 12 As shown in Figure (A), the desktop 1201 of the first terminal displays the application page 1202 of the simulator, and the desktop 1201 of the first terminal displays a shortcut 12021 of the application 1. At this time, the shortcut 12021 is an existing shortcut. If the target account is the account B1 that matches the application list A1, then when the account login operation is specifically for logging in to the account B1, as shown in FIG. Figure 12 As shown in FIG. (B), an application icon 12011 representing application 1 with application identifier C1, an application icon 12012 representing application 2 with application identifier C2, and an application icon 12013 representing application 3 with application identifier C3 are displayed on the application page 1201 of the simulator. Since the application identifier C1 representing the shortcut 12021 of application 1 exists in the program list A1 matching the target account, the shortcut 12022 representing application 2 with application identifier C2 and the shortcut 12023 representing application 3 with application identifier C3 are directly displayed on the desktop 1201 of the first terminal. Then, after responding to the account logout event for the target account, as shown in FIG. Figure 12 As shown in the figure (C), the desktop of the first terminal cancels the display Figure 12 In the middle (B) figure, shortcuts 12022 and 12023 are displayed, while shortcut 12021 remains displayed on the desktop of the first terminal.

[0099] In actual applications, considering that the target application is an application whose application identifier exists in the application list and whose shortcut is not displayed on the desktop, the application whose application identifier exists in the application list and whose shortcut is displayed on the desktop can also be canceled in response to an account logout event for the target account. That is, after responding to the account logout event for the target account, the first terminal can cancel the display of the shortcut of the application represented by the application identifier in the application list on the desktop of the first terminal.

[0100] For ease of understanding, Figure 13 The shortcut shown cancels the displayed interface diagram, and then Figure 12The examples given are introduced as follows: Figure 13 As shown in Figure (A), the desktop 1301 of the first terminal displays the application page 1302 of the simulator, and the desktop 1301 of the first terminal displays a shortcut 13021 of the application 1. If the target account is the account B1 that matches the application list A1, then when the account login operation is specifically for logging in to the account B1, as shown in FIG. Figure 13 As shown in FIG. 2(B), an application icon 13011 representing application 1 with application identifier C1, an application icon 13012 representing application 2 with application identifier C2, and an application icon 13013 representing application 3 with application identifier C3 are displayed on the application page 1301 of the simulator. A shortcut 13022 representing application 2 with application identifier C2, and a shortcut 13023 representing application 3 with application identifier C3 are displayed on the desktop 1301 of the first terminal. At this time, after responding to the account logout event for the target account, as shown in FIG. Figure 13 As shown in the middle (C) figure, the shortcut 13021 of application 1 represented by application identifier C1, the shortcut 13022 of application 2 represented by application identifier C2, and the shortcut 13023 of application 3 represented by application identifier C3 belonging to application list A1 will be cancelled.

[0101] The following describes how to determine the method for triggering an account logout event for the target account. In a specific embodiment, the account logout event for the target account includes one of the following: triggering an account logout operation for the target account in the application page of the simulator; or triggering an account logout event when it is detected that the account login information meets the account logout conditions.

[0102] Specifically, as can be seen from the above-mentioned embodiments, an account login control is displayed on the application interface of the simulator. After the account login control is triggered, an account login interface is displayed on the application page of the simulator. After the login information of the target account is input and confirmed in the account login interface, the account login operation for the target account is triggered. Similarly, when it is necessary to log out of the target account, an account logout operation for the target account can be triggered in the application page of the simulator to trigger an account logout event for the target account. That is, an account logout control can be displayed in the application page of the simulator. After the account logout control is operated, an account logout confirmation interface will be displayed on the application page of the simulator. After completing the confirmation operation on the account logout confirmation interface, it can be determined that the account logout operation has been triggered, thereby triggering the account logout operation for the target account. At this time, the account logout event actively triggered by the target account is completed.

[0103] In actual applications, the account logout event can also be triggered in other ways, such as when the first terminal detects that the account login information meets the account logout condition, the account logout event is triggered. The aforementioned account logout condition can be that the first terminal performs a shutdown operation. That is, when the first terminal detects the shutdown operation, the simulator's account logout event is triggered to log out the target account in the simulator. Then, the first terminal can also actively trigger the target account's account login operation for the simulator when it is turned on next time. Or, the account logout condition can also be: the duration of no operation on the simulator's application interface reaches the operation duration threshold. The operation duration threshold can be 1 hour, 90 minutes, and 2 hours, etc., which are not limited here. That is, after the target user logs in to the simulator through the target account, the simulator's application interface has not been operated for a long time. At this time, the duration of no operation on the simulator's application interface is counted. After reaching the operation duration threshold (such as 1 hour), the account logout event is triggered to log out the target account from the simulator. It is understandable that the aforementioned account logout condition can also be that the first terminal's desktop screen is off for a duration that reaches the screen off duration threshold, etc., and the account logout conditions are not exhaustive here.

[0104] It is understandable that the above examples are used to understand the present solution and should not be understood as specific limitations of the present solution.

[0105] In the above desktop shortcut processing method, for the simulator installed on the first terminal, by responding to the account login operation triggered for the simulator, it is possible to display the application that has been triggered on the second terminal and matched by the logged-in target account on the application page of the simulator without the target account actively triggering the operation, and further display the shortcut of the target application represented by the application identifier that does not display the shortcut on the desktop on the desktop on the desktop of the first terminal, that is, the shortcut can be displayed without the target account actively triggering it, and because the displayed shortcut is a shortcut to the application that is not displayed on the desktop of the first terminal but corresponds to the target account, it is ensured that the displayed shortcut is a shortcut to the application that the target account can access, thereby ensuring the security and flexibility of desktop shortcut processing. And when the account logout event for the target account is triggered, it indicates that the target account has exited the account login of the simulator. At this time, the shortcut of the target application is canceled on the desktop of the first terminal to prevent accounts that do not have access rights to the target application from accessing the program through the desktop shortcut, further ensuring the security and flexibility of desktop shortcut processing.

[0106] In actual applications, shortcuts can also be actively generated and displayed for applications, which is described in detail below: In one embodiment, Figure 14 As shown, on the desktop of the first terminal, the shortcut of the target application represented by the target application identifier is displayed, including:

[0107] Step 1402 : In response to a drag operation on at least one application identifier in the application list, display a moving track of the dragged target application identifier.

[0108] The drag operation is specifically performed on the application icon of the application represented by the application identifier, and the movement trajectory is used to describe the movement trajectory of the target application icon of the target application represented by the target application identifier on the display page of the first terminal. Specifically, the target user can drag the application icon of the application represented by any application identifier in the application list, and the application identifier of the application of the dragged application icon is the target application identifier. The first terminal responds to the drag operation on the target application identifier and displays the movement trajectory of the dragged target application identifier on the display page of the first terminal. The dragged target application identifier belongs to the application list, that is, the starting point of the drag operation is the application page of the simulator, and specifically is the target application icon of the target application indicated by the dragged target application identifier displayed on the application page of the simulator. Then the movement trajectory of the dragged target application identifier can be: from the application page of the simulator (that is, the display area of the target application icon on the application page of the simulator) to the desktop area of the first terminal, or, from the application page of the simulator (that is, the display area of the target application icon on the application page of the simulator) to other areas of the application page of the simulator.

[0109] For ease of understanding, Figure 15 The schematic diagram of the movement trajectory shown, Figure 15 (A) shows the moving track 1503 of dragging the target application icon 15011 from the application page 1501 of the simulator to the desktop 1502 of the first terminal. Figure 15 The diagram (B) shows a moving track 1504 of dragging the target application icon 15011 from the application page 1501 of the simulator to another area of the application page 1501 of the simulator.

[0110] Step 1404: In response to a drag-and-release operation on the target application identifier, if the drag-and-release location of the target application identifier is the area where the desktop of the first terminal is located and there is no shortcut of the target application represented by the target application identifier on the desktop, a shortcut of the target application is added to the desktop of the first terminal.

[0111] Among them, the drag operation is a drag start operation, that is, the drag start operation has a drag start position. The drag start position in this embodiment is the application page of the simulator, and specifically the location of the target application icon of the target application identifier being dragged in the application page of the simulator. The drag release operation is used to indicate the end of dragging the target application icon of the target application identifier. Therefore, the drag release position in this embodiment can be the area where the desktop of the first terminal is located, or other areas in the application page of the simulator. Specifically, in response to the drag release operation for the target application identifier, it is determined that the dragging of the target application icon of the target application identifier is completed. At this time, the first terminal needs to identify the drag release position of the target application icon of the target application identifier. For ease of understanding, please refer to again. Figure 15 , Figure 15 The diagram (A) shows the moving track 1503 of dragging the target application icon 15011 from the application page 1501 of the simulator to the desktop 1502 of the first terminal. That is, the moving track 1503 can indicate the drag-release position of the target application icon 15011, which is the area where the desktop of the first terminal is located. Figure 15 The figure (B) shows the movement trajectory 1504 of dragging the target application icon 15011 from the application page 1501 of the simulator to other areas of the application page 1501 of the simulator, that is, the movement trajectory 1504 now indicates that the drag-and-release position of the target application icon 15011 is other areas of the application page of the simulator.

[0112] Based on this, when the drag-and-drop location is the area where the desktop of the first terminal is located, it is also necessary to determine whether there is a shortcut to the target application represented by the target application identifier on the desktop of the first terminal. If so, there is no need to add a shortcut. On the contrary, if not, a shortcut to the target application is added to the desktop of the first terminal. Figure 15 The figure (A) shows the movement trajectory for further introduction, such as Figure 16 The interface diagram of adding a shortcut of a target application to the desktop of the first terminal is shown as follows: Figure 16 As shown in Figure (A), the target application icon 16011 is dragged from the application page 1601 of the simulator to the desktop 1602 of the first terminal. At this time, the drag-and-drop position of the target application icon 16011 represented by the target application identifier is determined to be the area where the desktop 1602 of the first terminal is located. Since the desktop 1602 of the first terminal does not display any shortcuts, as shown in FIG. Figure 16 As shown in the middle (B) figure, a shortcut 16021 of the target application is added to the desktop of the first terminal 1602.

[0113] As described in the aforementioned embodiments, in actual applications, application icons that match the application represented by the application identifier that is not in the application list matching the target account can also be displayed on the simulator's application page. That is, the application page can also include an application discovery page and an application recommendation page, etc., and the application discovery page and application recommendation page can display recommended applications based on the simulator's application recommendation method. The target user can then drag and drop the application icons displayed on the application discovery page and application recommendation page to display shortcuts to the recommended applications on the desktop of the first terminal.

[0114] Based on this, the following describes in detail how the first terminal creates a shortcut and displays the shortcut on the desktop in response to the drag operation and the drag-and-release operation. Figure 17 The schematic diagram of the sequential flow of creating a shortcut by dragging shows that, first, the target user initiates a drag operation on the target application through the service module. The drag event processing submodule in the client module detects the user's drag operation on the first terminal to capture the drag event and obtain program information of the application targeted by the drag operation (such as the application identifier "app_id", application icon, and program installation status). After capturing the drag event, the Windows API in the Windows system module is called to verify whether the drag target is the desktop. Specifically, it detects the window handle. Based on this, if the target user performs a drag-and-release operation through the service module and the drag target is the desktop, the client module calls the Windows system module to perform a local cache query, that is, to determine whether the target application indicated by the drag operation is installed for the simulator. The installation status of the target application is obtained from the Windows system module. The installation status is used to indicate whether the target application is installed or not installed. If the target application is installed, the client module generates a standard shortcut by calling the Windows API of the Windows system module to create a .lnk file. Based on the shortcut creation result returned by the Windows system module, a shortcut for the target application is displayed on the desktop of the first terminal.

[0115] Conversely, if the target application is not installed, the client module generates a placeholder shortcut for the target application and specifically calls the Windows system module to create a .lnk file pointed to by the agent program. The client module then retrieves the creation result of the placeholder shortcut for the target application from the Windows system module. After the placeholder shortcut is created, the placeholder shortcut for the target application is displayed on the desktop of the first terminal. Then, when the user clicks on the placeholder shortcut, the Windows system module is called to trigger an installation request from the simulator module, at which point the application identifier and callback interface of the target application are passed. In response to the installation request, the simulator module downloads the Android application package (APK) installation package of the target application from the cloud server and installs the target application to a specified path based on the installation package APK. It then sends back an installation completion notification to the Windows system module. The Windows system module then calls back the client module to update the shortcut path. At this point, the Windows system module still calls the Windows API of the Windows system module to update the .lnk file, that is, to update the placeholder shortcut .lnk file of the target application to the shortcut .lnk file of the target application. After the update is complete, an update completion notification is sent back, and the shortcut of the target application is displayed on the desktop of the first terminal.

[0116] It is understandable that the above examples are used to understand the present solution and should not be understood as specific limitations of the present solution.

[0117] In this embodiment, by dragging the application icon of the application from the application list to the desktop through a drag operation, a shortcut of the dragged application is displayed on the desktop in a manner that the target user actively drags it, so as to provide a more flexible and practical shortcut display method, thereby further improving the flexibility and practicality of desktop shortcut processing.

[0118] As can be seen from the above embodiments, multiple dimensions need to be considered in the process of displaying shortcuts on the desktop of the first terminal, namely, whether the shortcut of the application has been displayed on the desktop of the first terminal, whether the application is completely consistent locally and in the cloud, etc., that is, possible scenarios as shown in Table 1:

[0119] Scenario 1 (the first terminal is installed and compatible with the simulator logged in by the target account) Scenario 2 (The first terminal is already installed and is not compatible with the simulator logged in by the target account) Scenario 3 (the first terminal is not installed and is adapted to the simulator logged in by the target account)

[0120] Table 1

[0121] For scenario 2, that is, the first terminal has been installed and is not compatible with the simulator logged in by the target account, that is, the existing application represented by the existing shortcut on the desktop introduced in the aforementioned embodiment, there is no application identifier of the existing application in the application list. At this time, the existing shortcut of the existing application is cancelled on the desktop.

[0122] The following describes how to display shortcuts in other scenarios. First, the following describes how to display shortcuts in scenario 1 where the first terminal is installed and the simulator that is compatible with the target account logged in is used: In one embodiment, Figure 18 As shown, on the desktop of the first terminal, a shortcut of the target application represented by the target application identifier is displayed, including:

[0123] Step 1802 : For each target application represented by the target application identifier, if the target application has been installed on the first terminal and is compatible with the simulator, a shortcut of the target application is displayed on the desktop of the first terminal.

[0124] Specifically, the target application represented by the target application identifier, that is, the target application, does not display a shortcut on the desktop of the first terminal. In this case, the target application may not be installed, or it may be installed but a shortcut is not displayed on the desktop of the first terminal. Based on this, if for each target application, if the target application has been installed on the first terminal and the target application is adapted to the simulator, the target application being adapted to the simulator means that the target account can directly access and run the target application through the simulator. Therefore, when the target account can directly access and run the target application through the simulator and the first terminal has installed the target application, a shortcut to the target application is displayed on the desktop of the first terminal, that is, by interactively operating the shortcut to the target application displayed on the desktop, the target application can be run through the simulator logged in by the target account.

[0125] Considering that in actual applications, the first terminal specifically needs to compare the application that the first terminal completes the application installation for the simulator to see whether there is a consistent application among the related applications authorized by the target account. The following is a detailed introduction to this: In a specific embodiment, the first terminal has installed the target application and the target application is adapted to the simulator: the application list includes the target application, and the installed application list adapted to the simulator includes the target application; wherein the installed application list is the installed application that completes the application installation for the simulator on the first terminal.

[0126] Specifically, when the first terminal responds to the account login operation triggered by the simulator on the first terminal, it will also send an account authentication request for the target account to the cloud server to request synchronization of the target account's account application information. The cloud server will then feedback a list of applications to the first terminal. The aforementioned application list is the application that the target account is authorized to run through the simulator. Therefore, the first terminal can obtain the application list and cache the application list in the local cache of the first terminal. For ease of understanding, the following example uses the cloud server feedback of authorization information for application 1 to the first terminal as an example:

[0127]

[0128] The aforementioned code information indicates that the cloud server has determined that the target account has been authorized to run the application through the simulator.

[0129] Based on this, the first terminal can obtain the installed applications that have been installed on the first terminal for the simulator, that is, obtain a list of installed applications that includes at least one installed application identifier that represents the installed application. In other words, when an application adapted for the second terminal is installed through the simulator, the application identifier of the installed application is added to the list of installed applications. Therefore, the list of installed applications includes multi-dimensional local installation information of the application, and the local installation information includes at least the application identifier of the installed application and the version number of the installed application. The application identifier is used to uniquely indicate an application, and the version number is used to describe the application version of the application.

[0130] From this, it can be seen that the first terminal specifically compares the target application identifier representing the target application included in the application list cached by the cloud server, and the installed application identifier representing the installed application in the installed application list of the adaptation simulator. If the target application identifier is consistent with the installed application identifier, it means that the target application in the application list matching the target account has completed the application installation for the simulator on the first terminal, so there is no need to install the target application again. At this time, it is determined that a shortcut to the target application is displayed on the desktop of the first terminal.

[0131] As mentioned above, local installation information includes at least the application ID and version number of the installed application. Therefore, each target application in the application list also includes the application ID and version number of the target application. In actual applications, different version numbers may result in different application functions supported during runtime, and even different shortcut display methods. For example, different version numbers may have different shortcut icons or different application names. The following details how to display shortcuts when the version numbers are different, even if the application IDs are the same:

[0132] In an optional embodiment, the target application has different version numbers, and the different version numbers are usually obtained after the version is updated. For example, the target application is Game 1, and the game has version number D1, version number D2 which is an update of version number D1, version number D3 which is an update of version number D2, etc. Different version numbers can indicate at least one of different application names and application icons. For example, version number D1 can indicate application name E1 and application icon F1, version number D2 can indicate application name E1 and application icon F2, and version number D3 can indicate application name E2 and application icon F3. That is, after the application is updated from the application version indicated by version number D1 to the application version indicated by version number D2, the application name remains unchanged but the application icon changes, and after the application is updated to the application version indicated by version number D3, both the application name and application icon change.

[0133] Based on this, the desktop shortcut processing method further includes: when the first version number of the target application represented by the target application identifier is different from the second version number of the target application installed on the first terminal, updating the installed target application to a version corresponding to the first version number.

[0134] Specifically, considering that the first terminal has installed the target application and the target application is adapted to the simulator, the target application is included in the application list, and the list of installed applications adapted to the simulator includes the target application, that is, the application identifier of the target application at this time is consistent with the application identifier of the target application installed by the first terminal. Based on this, it is necessary to further extract the first version number of the target application represented by the target application identifier in the application list, and extract the second version number of the target application installed by the first terminal, and determine whether the first version number is consistent with the second version number. If they are consistent, it means that the metadata of the target application represented by the target application identifier in the application list is consistent with the metadata of the target application installed by the first terminal. At this time, the shortcut of the target application is directly displayed on the desktop of the first terminal, and the shortcut of the target application displayed on the desktop is consistent with the application name and application icon indicated by the first version number.

[0135] On the contrary, if there is inconsistency, it means that the metadata of the target application represented by the target application identifier in the application list is inconsistent with the metadata of the target application installed on the first terminal. Since the application list is associated with the target account, that is, the target application represented by the target application identifier in the application list is the application authorized by the target account, it is necessary to determine whether the application name and application icon indicated by the first version number are consistent with the application name and application icon indicated by the second version number. If one of the application name and application icon is updated, the installed target application is updated to the version corresponding to the first version number, that is, a version update is performed on the installed target application in the first terminal to update the target application to the version corresponding to the first version number.

[0136] For example, the target application identifier in the application list is application identifier C1, and the application identifier of the target application installed on the first terminal is application identifier C1. If the first version number of the target application identifier in the application list is version number D2 in the aforementioned example, and the second version number of the target application installed on the first terminal is version number D1 in the aforementioned example, that is, the first version number and the second version number are inconsistent, therefore, it is necessary to further determine whether the application name E1 and application icon F1 indicated by version number D1, and the application name E1 and application icon F2 indicated by version number D2 are consistent. At this time, it can also be determined that the application icon F1 and the application icon F2 have changed. Therefore, it is necessary to update the target application installed on the first terminal from the application version indicated by version number D1 to the application version indicated by version number D2.

[0137] It is understandable that in actual applications, it is also possible to calculate and compare the first hash value of the target application represented by the target application identifier and the second hash value of the target application installed on the first terminal. Similar to the aforementioned embodiment, different target applications have different hash values, and different hash values can indicate different application names and at least one of the application icons. Therefore, in the case where the first hash value and the second hash value are inconsistent, it is necessary to determine whether the application name and application icon matched by the first hash value are consistent with the application name and application icon indicated by the second hash value. If one of the application name and application icon is updated, the installed target application is updated to the application corresponding to the first hash value. The specific implementation method is similar to the aforementioned introduction and will not be repeated here.

[0138] Based on the foregoing, in a specific embodiment, displaying a shortcut of a target application includes: displaying a shortcut of the target application according to the application name and the application icon indicated by the first version number.

[0139] Specifically, as can be seen from the above introduction, different version numbers can indicate different application names and at least one of the application icons. Since the installed target application has been updated to the version corresponding to the first version number in this embodiment, considering that the shortcut display method of the target application will change at least one of the application name and the application icon, the first terminal specifically calls the Update Shortcut method to refresh the .lnk file of the target application. Then, the first terminal displays the shortcut of the target application on the desktop of the first terminal according to the application name and application icon indicated by the first version number. For ease of understanding, as Figure 19 The schematic diagram of the interface for displaying a shortcut of a target application shows that a shortcut 1904 of the target application is displayed on a desktop 1901 of the first terminal according to an application name 1902 and an application icon 1903 indicated by a first version number.

[0140] In actual applications, there must be an application identifier that belongs to the application list and the application represented by it has a shortcut displayed on the desktop. The application identifier that exists in the application list and the application represented by it has a shortcut displayed on the desktop is determined to be an existing application identifier. At this time, it is necessary to use a similar method to the above-mentioned embodiment. For the existing application identifier, it is also necessary to extract the third version number of the existing application represented by the existing application identifier in the application list, and extract the fourth version number of the existing application installed on the first terminal, and determine whether the third version number is consistent with the fourth version number. If they are consistent, it means that the metadata of the existing application represented by the existing application identifier in the application list is consistent with the metadata of the existing application installed on the first terminal. At this time, the shortcut to the existing application is directly retained on the desktop of the first terminal.

[0141] On the contrary, if there is inconsistency, it means that the metadata of the existing application represented by the existing application identifier in the application list is inconsistent with the metadata of the existing application installed on the first terminal. Since the application list is associated with the existing account, that is, the existing application represented by the existing application identifier in the application list is the application authorized by the existing account, it is necessary to determine whether the application name and application icon indicated by the third version number are consistent with the application name and application icon indicated by the fourth version number. If one of the application name and application icon is updated, the installed existing application is updated to the version corresponding to the third version number, that is, the version of the installed existing application is updated in the first terminal to update the existing application to the version corresponding to the third version number. Then, the shortcut of the existing application displayed on the desktop of the first terminal is adjusted and updated to the shortcut displayed according to the application name and application icon indicated by the third version number. And instead of using the version number for comparison, it can also be compared by hash value in a similar way as described above, which will not be repeated here.

[0142] For ease of understanding, Figure 20 The diagram of the interface for adjusting the shortcuts to the target application is shown as follows: Figure 20 As shown in Figure (A), a shortcut 2002 of an existing application installed on the first terminal is displayed on the desktop 2001 of the first terminal. At this time, the application name displayed corresponding to the shortcut 2002 is "Game", and the application icon is as shown. If the third version number of the existing application represented by the application identifier in the application list is different from the fourth version number of the existing application installed on the first terminal, it is necessary to update the installed existing application to the version corresponding to the third version number, as shown in the figure. Figure 20As shown in FIG. 5(B), the shortcut 2002 on the desktop 2001 of the first terminal is adjusted to a shortcut 2005 that matches the application name 2003 (specifically, an online game) indicated by the third version number and the application icon 2004.

[0143] It is understandable that the above examples are used to understand the present solution and should not be understood as specific limitations of the present solution.

[0144] In this embodiment, by determining whether the target application has been installed for the simulator on the first terminal, the target application's shortcut is accurately displayed, ensuring that the target application can be quickly accessed and run through the simulator via the shortcut. Secondly, if the target application's application identifier is consistent, the version number is further considered to ensure that the shortcut matching the version number associated with the target account is more accurately displayed. This also ensures that the program version running on the first terminal for the simulator is authorized by the target account, further ensuring the reliability and accuracy of desktop shortcut processing.

[0145] The following describes how to display shortcuts in scenario 3 when the first terminal is not installed and the simulator that the target account is logged in is adapted. In one embodiment, Figure 21 As shown, on the desktop of the first terminal, a shortcut of the target application represented by the target application identifier is displayed, including:

[0146] Step 2102 : for each target application represented by the target application identifier, if the target application is not installed on the first terminal, the target application adapted to the simulator is installed on the first terminal, and a shortcut of the target application is displayed on the desktop of the first terminal.

[0147] Among them, the situation in which the first terminal does not install the target application is: the target application is included in the application list, and the simulator's installed application list does not include the target application. That is, the application list includes a target application identifier representing the target application, and the first terminal's installed application list for the simulator does not include the target application identifier representing the target application. For example, the application list includes application identifier C1, application identifier C2, and application identifier C3. If the first terminal includes application identifier C4 in the simulator's installed application list, it can be determined that application identifier C1, application identifier C2, and application identifier C3 are all target application identifiers, and the simulator's installed application list does not include the target application (i.e., application 1 represented by application identifier C1, application 2 represented by application identifier C2, and application 3 represented by application identifier C3). That is, the first terminal has not installed application 1, application 2, and application 3 for the simulator.

[0148] Specifically, for each target application represented by the target application identifier, if the target application is not installed on the first terminal, simply displaying a shortcut to the target application cannot achieve the purpose of quickly accessing the target application through the shortcut. Therefore, the target application adapted for the simulator is installed on the first terminal, that is, the program adapted for the simulator is installed on the first terminal according to the installation information of the target application. After the target application adapted for the simulator is installed, a shortcut to the target application is displayed on the desktop of the first terminal.

[0149] It is understandable that, when the target application is not installed on the first terminal, it is possible to consider operating through the target user to determine the creation and display of a shortcut for the target application, that is, it is necessary to authorize the target application to be adapted and installed on the first terminal with the simulator. This is described in detail below: In a specific embodiment, when the target application is not installed on the first terminal, the target application adapted to the simulator is installed on the first terminal, and a shortcut to the target application is displayed on the desktop of the first terminal, including: displaying a placeholder shortcut on the desktop of the first terminal; in response to a trigger operation for the placeholder shortcut, installing the target application adapted to the simulator on the first terminal; and replacing the placeholder shortcut with a shortcut to the target application on the desktop of the first terminal.

[0150] Specifically, if you want to display a placeholder shortcut on the desktop of the first terminal, you need to call the shortcut control engine in the Windows system through the simulator to generate a shortcut creation instruction. The shortcut creation instruction includes the installation path of the shortcut. File operations are performed through the shortcut control engine in the Windows system. At this time, a placeholder shortcut is first generated and displayed on the desktop of the first terminal.

[0151] Based on this, if the target user determines to install the target application and display a shortcut, a trigger operation can be performed to display a placeholder shortcut on the first terminal's desktop. The trigger operation can be a single-click operation, a double-click operation, or other similar operation, which is not limited here. Therefore, in response to the trigger operation for the placeholder shortcut, the first terminal installs the target application adapted for the simulator on the first terminal. Specifically, the shortcut control engine in the Windows system generates a .lnk file for the shortcut and points it to the installer agent program via TargetPath. Specifically, TargetPath can point to a unified installation agent program (such as AppInstaller.exe), so that the agent parameter carries the application identifier (app_id) and callback API. The installation agent program then starts and downloads the APK installation package of the target application. Based on the target application's APK installation package, the target application is installed on the simulator, thereby completing the installation of the target application adapted for the simulator. During the installation of the target application, the displayed icon of the placeholder shortcut can also be adjusted to a "downloading" icon or an "installing" icon to indicate to the target user that the target application's installation progress is confirmed by the aforementioned icon.

[0152] Furthermore, after the target application is installed, the placeholder shortcut is replaced with the target application shortcut on the first terminal's desktop, displaying the target application shortcut. That is, after the target application is installed, the target application shortcut path is reset to the actual application path (e.g., C:\Emulator\game1.exe), and the target application shortcut is displayed on the first terminal's desktop. At this point, the target application status can also be fed back to the cloud server as "installed."

[0153] For ease of understanding, Figure 22 The interface diagram of the display placeholder shortcut and shortcut is shown as follows: Figure 22 As shown in FIG. 10A , a placeholder shortcut 2202 for a target application is displayed on the desktop 2201 of the first terminal. After the placeholder shortcut 2202 is triggered, Figure 22 As shown in FIG. 22 (B), during the installation of the target application, an "installing" icon 2203 for the target application is displayed on the desktop 2201 of the first terminal. After the installation of the target application is completed, Figure 22 As shown in FIG. 2 (C), on the desktop 2201 of the first terminal, the placeholder shortcut 2202 is replaced with a shortcut 2204 of the target application for display.

[0154] It is understandable that the above examples are used to understand the present solution and should not be understood as specific limitations of the present solution.

[0155] In this embodiment, since the first terminal installs the target application in the simulator and then displays a shortcut to the target application on the desktop of the first terminal, it is ensured that the installed target application can be accurately run in the simulator through the shortcut, thereby ensuring the reliability and accuracy of desktop shortcut processing.

[0156] Considering that the account logout event is used to indicate that the target account has logged out of the simulator at the first terminal, the shortcut of the target application should be canceled on the desktop of the first terminal when the target account logs out. In actual application, the selection requirements of the target user can be considered to retain the display of some shortcuts, or more shortcuts to be canceled can be selected according to the selection requirements of the target user. This is described in detail below: In one embodiment, if Figure 23 As shown, in response to an account logout event for a target account, canceling the display of a shortcut of a target application on the desktop of the first terminal includes:

[0157] Step 2302: In response to an account logout event for the target account, a shortcut operation control for the target application is displayed.

[0158] The shortcut operation control is used to operate the shortcut of the target application, and the aforementioned operation may be a selection operation. Specifically, when the first terminal detects an account logout event for the target account, a shortcut operation control for the target application is displayed on the first terminal's desktop in response to the account logout event. It is understood that in actual applications, considering that the shortcut to the target application is a displayed shortcut, when the target account logs out, the first terminal's desktop may also display a shortcut operation control corresponding to the application represented by the application identifier in the application list. Alternatively, since the first terminal's desktop may also display shortcuts for applications that are not in the application list, shortcut operation controls for applications with shortcuts displayed on the first terminal's desktop may also be displayed. That is, shortcut operation controls may correspond one-to-one with applications. For example, shortcut operation control G1 corresponds to application 1, shortcut operation control G2 corresponds to application 2, shortcut operation control G3 corresponds to application 3, and shortcut operation control G4 corresponds to application 4.

[0159] Step 2304 : In response to the shortcut deletion operation triggered by the shortcut operation control, the shortcut of the target application is undisplayed on the desktop of the first terminal.

[0160] Among them, the shortcut deletion operation is used to delete the shortcut matched by the shortcut operation control, that is, to cancel the display of the shortcut matched by the shortcut operation control on the desktop of the first terminal. Specifically, when the target user needs to cancel the display of the shortcut of the application displayed on the desktop, the target user triggers the shortcut deletion operation for the shortcut operation control, so that the first terminal responds to the shortcut deletion operation triggered for the shortcut operation control, and determines the target application for which the shortcut needs to be canceled through the shortcut deletion operation, and then cancels the display of the shortcut of the determined target application on the desktop of the first terminal. The following will introduce in detail how to determine the target application for which the shortcut needs to be canceled:

[0161] In a specific embodiment, in response to a shortcut deletion operation triggered by a shortcut operation control, the shortcut of the target application is canceled from the desktop of the first terminal, including: in response to a shortcut selection operation triggered by the shortcut operation control, displaying a selection box corresponding to each shortcut of the target application; in response to a selection operation on at least a part of the selection boxes, displaying the selected shortcut; in response to a shortcut deletion operation triggered by the selected shortcut, canceling the display of the shortcut of the target application on the desktop of the first terminal.

[0162] Specifically, when the target user needs to cancel the display of the shortcut of the application displayed on the desktop, the target user triggers the shortcut deletion operation on the shortcut operation control, so that the first terminal responds to the shortcut deletion operation triggered by the shortcut operation control and displays a selection box corresponding to each shortcut of the target application. At this time, the selection box corresponding to each shortcut of the target application can be displayed on the application interface of the simulator, or on the desktop, and the selection box corresponding to each shortcut of the target application can also be displayed. At this time, a text description such as "Please select the application to be canceled" can also be displayed in the associated position of the selection box to enable the target user to confirm that the shortcut of the selected application is to be canceled.

[0163] Therefore, when the target user needs to cancel the display of some of the shortcuts of the target application, the target user selects the selection box of at least some of the shortcuts to display the selected shortcuts. At this time, the selected shortcuts can still be displayed on the application interface of the simulator or on the desktop, without limitation. Based on this, after the target user confirms the cancellation of the display of the selected shortcuts, a shortcut deletion operation is initiated for the selected shortcuts. The first terminal will respond to the aforementioned shortcut deletion operation and cancel the display of the shortcuts of the target application on the desktop of the first terminal.

[0164] To facilitate understanding of the aforementioned related display interfaces, Figure 24 The interface diagram shown is a diagram of canceling the display of the shortcut of the target application in response to the shortcut deletion operation. Figure 24 Figure (A) shows that the application page 2401 of the simulator displays the application icons corresponding to application 1, application 2, and application 3, respectively, and the desktop of the first terminal displays a shortcut 24021 of application 1, a shortcut 24022 of application 2, and a shortcut 24023 of application 3. After the account logout event is triggered, shortcut operation controls for shortcuts 24021, 24022, and 24023 may be displayed, and after selecting an operation for the shortcut triggered by the shortcut operation control, as shown in FIG. Figure 24 The middle (B) diagram shows the selection boxes corresponding to the shortcuts of each target application, namely, the selection box 24031 corresponding to the shortcut 24021, the selection box 24032 corresponding to the shortcut 24022, and the selection box 24033 corresponding to the shortcut 24023. If the target user selects the selection box 24031, as shown in FIG. Figure 24 Figure (C) shows the selected shortcut 24021 and the selection box 24031 corresponding to the shortcut 24021. After the target user determines to cancel the display of the shortcut 24021, the first terminal responds to the shortcut deletion operation triggered for the selected shortcut, and Figure 24 The middle figure (D) shows that the selected shortcut 24021 is canceled from the desktop 2401 of the first terminal. At this time, the unselected shortcut 24022 and the unselected shortcut 24023 are still displayed on the desktop 2401 of the first terminal.

[0165] In a specific embodiment, in response to a shortcut deletion operation triggered by a shortcut operation control, the shortcut of the target application is canceled on the desktop of the first terminal, including: in response to a shortcut selection operation triggered by the shortcut operation control, displaying the selection boxes corresponding to the shortcuts of each target application; in response to a selection operation on at least a part of the selection boxes, displaying the selected shortcuts; in response to the shortcut deletion operation, canceling the display of the shortcuts corresponding to the unselected selection boxes on the desktop of the first terminal.

[0166] Specifically, when the target user needs to cancel the display of the shortcut of the application displayed on the desktop, the target user triggers the shortcut deletion operation on the shortcut operation control, so that the first terminal responds to the shortcut deletion operation triggered by the shortcut operation control and displays a selection box corresponding to each shortcut of the target application. At this time, the selection box corresponding to each shortcut of the target application can be displayed on the application interface of the simulator, or on the desktop, and the selection box corresponding to each shortcut of the target application can also be displayed. At this time, a text description such as "Please select the application to be retained" can also be displayed in the associated position of the selection box to enable the target user to confirm that the shortcut of the selected application is retained.

[0167] Therefore, when the target user needs to cancel the display of shortcuts for some target applications, at this time, the selection box of at least some shortcuts is selected to display the selected shortcuts. At this time, the selected shortcuts can still be displayed in the application interface of the simulator, or the selected shortcuts can be displayed on the desktop, without limitation here. Based on this, since "Please select the application to be displayed", the shortcuts of the selected applications will be retained and displayed on the desktop. Therefore, after the target user determines to retain the display of the selected shortcuts, a shortcut deletion operation is initiated for the selected shortcuts. The first terminal will respond to the aforementioned shortcut deletion operation and cancel the display of the shortcuts corresponding to the unselected selection boxes on the desktop of the first terminal.

[0168] To facilitate understanding of the aforementioned related display interfaces, Figure 25 The interface diagram shown is a diagram of canceling the display of the shortcut of the target application in response to the shortcut deletion operation. Figure 25 (A) shows that the application page 2501 of the simulator displays the application icons corresponding to application 1, application 2, and application 3, respectively, and the desktop of the first terminal displays a shortcut 25021 of application 1, a shortcut 25022 of application 2, and a shortcut 25023 of application 3. After the account logout event is triggered, shortcut operation controls for shortcuts 25021, 25022, and 25023 may be displayed, and after selecting an operation on the shortcut triggered by the shortcut operation control, as shown in FIG. Figure 25 (B) shows the selection boxes corresponding to the shortcuts of each target application, namely, selection box 25031 corresponding to shortcut 25021, selection box 25032 corresponding to shortcut 25022, and selection box 25033 corresponding to shortcut 25023. If the target user selects selection box 25031, as shown in FIG. Figure 25Figure (C) shows the selected shortcut 25021 and the selection box 25031 corresponding to the shortcut 25021. After the target user determines to keep the displayed shortcut 25021, the first terminal responds to the shortcut deletion operation triggered for the selected shortcut, and Figure 25 The middle figure (D) shows that the unselected shortcut 25022 and the unselected shortcut 25023 are cancelled on the desktop 2501 of the first terminal, and the selected shortcut 25021 remains displayed on the desktop 2501 of the first terminal.

[0169] It is understandable that the above examples are used to understand the present solution and should not be understood as specific limitations of the present solution.

[0170] In this embodiment, in response to an account logout event for the target account, the user is instructed to make a shortcut display selection through the shortcut operation control, that is, the user can choose to keep the displayed shortcut or cancel the displayed shortcut through user operation, so as to improve the flexibility of desktop shortcut processing and better meet the user's needs for shortcut processing.

[0171] Based on the detailed description of the above embodiments, the following describes the complete process of completing desktop shortcut processing through the PC client, Windows system and cloud server in the embodiment of the present application. Figure 26 The flowchart shown is a process flow chart for processing desktop shortcuts through a PC client, Windows system, and cloud server. The PC client 2602 is used for account management, local caching, and shortcut control engine. Among them, account management is to respond to the account login operation and account logout event of the target account through the PC client 2602, and to perform token verification on the target account and synchronize the account information of the target account with the cloud server 2604. The local cache is a list of installed applications of the simulator installed applications stored by the PC client 2602, and can store temporary data such as shortcut configuration information and application installation status. The shortcut control engine is the core logic processing unit of the PC client 2602, which is used to compare the installed application list in the local cache with the program installation information between the application list for the target account fed back by the cloud server 2604, and the PC client 2602 can trigger shortcut operation instructions through the shortcut control engine.

[0172] Secondly, simulator 2606 is a PC client and is primarily used to download and install applications. Specifically, simulator 2606 communicates with cloud server 2604 via a connection between PC client 2602 and cloud server 2604, retrieves the application's APK installation package from cloud server 2604's application database, and installs the application into the local simulator environment based on the APK installation package. Simulator 2606 can also send operation requests to the shortcut control engine of PC client 2602 (e.g., triggering shortcut generation after installation is complete).

[0173] Among them, in this embodiment, Windows system 2608 specifically performs file operations and permission control. File operations are to create, delete, and update shortcuts (.lnk files), and permission control specifically limits shortcut directory access rights through Access Control List (ACL) to prevent unauthorized access across accounts. In other words, each account can only access and run authorized applications through the simulator. Finally, cloud server 2602 specifically performs account information synchronization and provides an application database in this embodiment. Account information synchronization is used to provide a list of authorized applications for the target account and the configuration of the application list on the first terminal (such as whether to display shortcuts on the first terminal). The application database is used to store the APK installation package of each application adapted to the second terminal, as well as the application's metadata (version number, application icon, program description, etc.).

[0174] Based on the aforementioned processing flow through the PC client, Windows system and cloud server, it is known that the desktop shortcut processing needs to be completed through communication and interaction between the PC client, Windows system and cloud server, such as Figure 27 The timing flow chart shown is for the interaction among the PC client, Windows system and cloud server. First, the user logs in, that is, the target user initiates an account login request for the target account. The PC client sends an authentication request for the target account to the cloud server through account management. The cloud server feeds back a list of applications authorized by the target account and the configuration information of each application to the PC client. Then, the PC client stores the application list and the configuration information of each application in the local cache.

[0175] Based on this, data comparison and processing begins. The PC client first reads the application list and each application's configuration information from the local cache, then obtains the list of locally installed applications from the simulator. The installed application list is then compared with the list of authorized applications, specifically comparing each application's installation information. Comparison dimensions include at least the application identifier (app_id), the application installation path, and the shortcut configuration. This involves comparing the application installation path to avoid duplicate installations, and comparing the shortcut configuration to see if the application name and icon have changed, as well as whether the shortcut is displayed on the desktop.

[0176] Based on this, if you need to cancel a shortcut that is already displayed on the desktop, the PC client sends a shortcut deletion command to the simulator, and the simulator deletes the displayed shortcut (.lnk) through the Windows system. Similarly, if the application you want to display is not installed, the PC client needs to send a download and installation request for the aforementioned application to the simulator, so that the simulator can install the application and feedback the installation completion notification to the PC client. At this time, it sends a create shortcut command to the simulator, and the simulator generates a shortcut (.lnk) through the Windows system and displays the newly added shortcut on the desktop.

[0177] Based on the detailed description of the above embodiment, the complete process of the desktop shortcut processing method in the embodiment of the present application will be described below. In one embodiment, Figure 28 As shown, a desktop shortcut processing method is provided, which is applied to Figure 1 The first terminal 102 in the example is used for explanation. The first terminal 102 is a terminal with an emulator installed, and the application simulated by the emulator is adapted to the second terminal 104. It is understood that the method can also be applied to a system including the first terminal 102 and the second terminal 104, and is implemented through interaction between the first terminal 102, the second terminal 104 and the cloud server. In this embodiment, the method includes the following steps:

[0178] Step 2801 : In response to an account login operation triggered on a simulator at a first terminal, a list of application programs matching the logged-in target account is displayed on an application page of the simulator.

[0179] Step 2802: In response to a drag operation on at least one application identifier in the application list, a moving trajectory of the dragged target application identifier is displayed; in response to a drag-and-release operation on the target application identifier, when the drag-and-release position of the target application identifier is the area where the desktop of the first terminal is located and there is no shortcut to the target application represented by the target application identifier on the desktop, a shortcut to the target application is added to the desktop of the first terminal.

[0180] Step 2803 : For each target application represented by the target application identifier, if the target application has been installed on the first terminal and is compatible with the simulator, a shortcut of the target application is displayed on the desktop of the first terminal.

[0181] Step 2804: Display a placeholder shortcut on the desktop of the first terminal for each target application represented by the target application identifier; install a target application adapted for the simulator on the first terminal in response to a triggering operation on the placeholder shortcut; and replace the placeholder shortcut with a shortcut to the target application on the desktop of the first terminal.

[0182] Step 2805 : For an existing application represented by an existing shortcut on the desktop, if the application identifier of the existing application does not exist in the application list, the existing shortcut of the existing application is undisplayed on the desktop.

[0183] Step 2806 : In response to the account logout event for the target account, the shortcut of the target application is canceled from the desktop of the first terminal.

[0184] It should be understood that the specific implementation of steps 2801 to 2806 are similar to those in the aforementioned embodiment and will not be repeated here.

[0185] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0186] Based on the same inventive concept, embodiments of the present application also provide a desktop shortcut processing device for implementing the aforementioned desktop shortcut processing method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations of one or more desktop shortcut processing device embodiments provided below can be found in the above-mentioned limitations of the desktop shortcut processing method and will not be repeated here.

[0187] In one embodiment, Figure 29As shown, a desktop shortcut processing device is provided. The device is applied to a first terminal installed with an emulator, and the application simulated by the emulator is adapted to a second terminal. The device includes: an application display module 2902, a shortcut display module 2904, and a shortcut cancellation display module 2906, wherein:

[0188] Application display module 2902 is configured to, in response to an account login operation triggered on the simulator at the first terminal, display a list of applications matching the logged-in target account on the simulator's application page; the application list includes at least one application identifier, the application identifier representing an application that has been triggered by the target account at the second terminal, the simulator being installed on the first terminal, and the applications simulated by the simulator being compatible with the second terminal;

[0189] The shortcut display module 2904 is configured to display a shortcut of a target application represented by a target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and for which a shortcut is not displayed on the desktop.

[0190] The shortcut display cancellation module 2906 is configured to cancel the display of the shortcut of the target application on the desktop of the first terminal in response to an account logout event for the target account.

[0191] In one embodiment, the shortcut display module is specifically used to display the movement trajectory of the dragged target application identifier in response to a drag operation on at least one application identifier in the application list; in response to a drag-and-release operation on the target application identifier, when the drag-and-release position of the target application identifier is the area where the desktop of the first terminal is located and there is no shortcut to the target application represented by the target application identifier on the desktop, a shortcut to the target application is added to the desktop of the first terminal.

[0192] In one embodiment, the shortcut display module is specifically configured to display a shortcut of the target application represented by each target application identifier on the desktop of the first terminal if the target application has been installed on the first terminal and is adapted to the simulator.

[0193] In one embodiment, the desktop shortcut processing device further includes a version update module;

[0194] The target applications have different version numbers;

[0195] The version update module is configured to update the installed target application to a version corresponding to the first version number when the first version number of the target application represented by the target application identifier is different from the second version number of the target application installed on the first terminal.

[0196] In one embodiment, the shortcut display module is specifically configured to display a shortcut of the target application according to the application name and application icon indicated by the first version number.

[0197] In one embodiment, the first terminal has installed the target application and the target application is adapted to the simulator as follows: the target application is included in the application list, and the installed application list adapted to the simulator includes the target application; wherein the installed application list is the installed application for which the application installation is completed on the first terminal for the simulator.

[0198] In one embodiment, the shortcut display module is specifically used to install the target application adapted for the simulator on the first terminal for each target application represented by the target application identifier, if the target application is not installed on the first terminal, and display a shortcut to the target application on the desktop of the first terminal.

[0199] In one embodiment, the shortcut display module is specifically configured to display a placeholder shortcut on the desktop of the first terminal; in response to a triggering operation on the placeholder shortcut, install a target application adapted for the simulator on the first terminal; and replace the placeholder shortcut with a shortcut of the target application on the desktop of the first terminal.

[0200] In one embodiment, the case where the first terminal does not have the target application installed is that the target application is included in the application list, and the installed application list of the simulator does not include the target application.

[0201] In one embodiment, the shortcut display cancellation module is further configured to cancel the display of an existing shortcut of an existing application represented by an existing shortcut on the desktop if the application identifier of the existing application does not exist in the application list.

[0202] In one embodiment, the shortcut cancellation display module is specifically used to display a shortcut operation control for a target application in response to an account logout event for a target account; and to cancel the display of the shortcut of the target application on the desktop of the first terminal in response to a shortcut deletion operation triggered by the shortcut operation control.

[0203] In one embodiment, the shortcut cancellation display module is specifically used to display the selection boxes corresponding to the shortcuts of each target application in response to a shortcut selection operation triggered by a shortcut operation control; display the selected shortcuts in response to a selection operation on at least a part of the selection boxes; and cancel the display of the shortcuts of the target application on the desktop of the first terminal in response to a shortcut deletion operation triggered by the selected shortcut.

[0204] In one embodiment, the shortcut cancellation display module is specifically used to display the selection boxes corresponding to the shortcuts of each target application in response to a shortcut selection operation triggered by a shortcut operation control; display the selected shortcuts in response to a selection operation on at least a part of the selection boxes; and cancel the display of the shortcuts corresponding to the unselected selection boxes on the desktop of the first terminal in response to a shortcut deletion operation.

[0205] In one embodiment, the application represented by the application identifier in the application list includes at least one of the following: at least one application that was last triggered by the target account on the second terminal; or, the application that meets the first filtering condition and is triggered the most times by the target account on the second terminal within a preset time interval; or, the application that is triggered the most times within a preset time interval and meets the second filtering condition.

[0206] In one embodiment, the account login operation triggered for the simulator includes one of the following: when the first terminal is started, starting the simulator and synchronously triggering the account login operation for the simulator; or, in response to the startup operation of the simulator in the first terminal, triggering the account login operation for the simulator.

[0207] In one embodiment, the account logout event for the target account includes one of the following: triggering an account logout operation for the target account in the application page of the simulator; or triggering an account logout event when it is detected that the account login information meets the account logout condition.

[0208] In one embodiment, a computer device is provided. The computer device can be a server or a terminal. In this embodiment, the computer device is used as a terminal as an example. The internal structure diagram thereof can be shown as follows: Figure 30As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface, the display unit and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a desktop shortcut processing method is implemented. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0209] Those skilled in the art will understand that Figure 30 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0210] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0211] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0212] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0213] It should be noted that the desktop shortcut processing (including but not limited to the object device information, object personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the object or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0214] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, and the like.

[0215] The technical feature information of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical feature information in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical feature information, they should be considered to be within the scope of this specification.

[0216] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A desktop shortcut processing method, characterized in that: The method comprises: In response to an account login operation triggered on the simulator at the first terminal, a list of applications matching the logged-in target account is displayed on an application page of the simulator; the list of applications includes at least one application identifier, the application identifier representing an application that has been triggered by the target account on the second terminal, the simulator is installed on the first terminal, and the application simulated by the simulator is compatible with the second terminal; Displaying a shortcut of a target application represented by a target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and for which a shortcut of the target application is not displayed on the desktop; In response to an account logout event for the target account, the shortcut of the target application is undisplayed on the desktop of the first terminal.

2. The method according to claim 1, characterized in that Displaying a shortcut of the target application program represented by the target application identifier on the desktop of the first terminal includes: In response to a drag operation on at least one application identifier in the application list, displaying a moving track of the dragged target application identifier; In response to a drag-and-release operation on the target application identifier, when the drag-and-release position of the target application identifier is the area where the desktop of the first terminal is located and there is no shortcut of the target application represented by the target application identifier on the desktop, a shortcut of the target application is added to the desktop of the first terminal.

3. The method according to claim 1, characterized in that The step of displaying a shortcut of the target application program represented by the target application identifier on the desktop of the first terminal includes: For each target application represented by the target application identifier, if the first terminal has installed the target application and the target application is adapted to the simulator, a shortcut of the target application is displayed on the desktop of the first terminal.

4. The method according to claim 3, characterized in that The target application has a different version number; the method further includes: When the first version number of the target application program represented by the target application identifier is different from the second version number of the target application program installed on the first terminal, the installed target application program is updated to a version corresponding to the first version number.

5. The method according to claim 4, characterized in that The displaying of the shortcut of the target application comprises: Display a shortcut of the target application according to the application name and application icon indicated by the first version number.

6. The method according to claim 3, characterized in that The case where the target application has been installed on the first terminal and the target application is adapted to the simulator is: the target application is included in the application list, and the list of installed applications adapted to the simulator includes the target application; wherein, the installed application list is the installed applications for which the application installation is completed on the first terminal for the simulator.

7. The method according to claim 1, characterized in that The step of displaying a shortcut of the target application program represented by the target application identifier on the desktop of the first terminal includes: For each target application represented by the target application identifier, if the target application is not installed on the first terminal, the target application adapted to the simulator is installed on the first terminal, and a shortcut of the target application is displayed on the desktop of the first terminal.

8. The method according to claim 7, characterized in that In a case where the target application is not installed on the first terminal, installing the target application adapted to the simulator on the first terminal and displaying a shortcut of the target application on the desktop of the first terminal includes: Displaying a placeholder shortcut on the desktop of the first terminal; In response to a triggering operation on the placeholder shortcut, installing a target application adapted to the simulator on the first terminal; On the desktop of the first terminal, the placeholder shortcut is replaced with a shortcut of the target application.

9. The method according to claim 7, characterized in that The case where the target application is not installed on the first terminal is that the target application is included in the application list, and the installed application list of the simulator does not include the target application.

10. The method according to claim 1, characterized in that The method further comprises: For an existing application represented by an existing shortcut on the desktop, if the application identifier of the existing application does not exist in the application list, the existing shortcut of the existing application is canceled from being displayed on the desktop.

11. The method according to claim 1, wherein In response to the account logout event for the target account, canceling the display of the shortcut of the target application on the desktop of the first terminal includes: In response to an account logout event for the target account, displaying a shortcut operation control for the target application; In response to the shortcut deletion operation triggered by the shortcut operation control, the shortcut of the target application is undisplayed on the desktop of the first terminal.

12. The method according to claim 11, characterized in that In response to the shortcut deletion operation triggered by the shortcut operation control, canceling the display of the shortcut of the target application on the desktop of the first terminal includes: In response to the shortcut selection operation triggered by the shortcut operation control, displaying a selection box corresponding to each shortcut of the target application; In response to a selection operation on at least a portion of the selection box, displaying the selected shortcut; In response to a shortcut deletion operation triggered for the selected shortcut, the shortcut of the target application is undisplayed on the desktop of the first terminal.

13. The method according to claim 11, characterized in that In response to the shortcut deletion operation triggered by the shortcut operation control, canceling the display of the shortcut of the target application on the desktop of the first terminal includes: In response to the shortcut selection operation triggered by the shortcut operation control, displaying a selection box corresponding to each shortcut of the target application; In response to a selection operation on at least a portion of the selection box, displaying the selected shortcut; In response to the shortcut deletion operation, the shortcuts corresponding to the unselected selection boxes are undisplayed on the desktop of the first terminal.

14. The method according to any one of claims 1 to 13, characterized in that The application represented by the application identifier in the application list includes at least one of the following: at least one application last triggered on the second terminal by the target account; or, triggering the application satisfying the first screening condition the most times through the target account on the second terminal within a preset time interval; Or, an application that is triggered a number of times within a preset time interval that meets the second screening condition.

15. The method according to any one of claims 1 to 13, characterized in that The account login operation triggered on the simulator includes one of the following: When the first terminal is started, starting the simulator and synchronously triggering an account login operation for the simulator; Or, in response to a startup operation on the simulator in the first terminal, an account login operation on the simulator is triggered.

16. The method according to any one of claims 1 to 13, characterized in that The account logout event for the target account includes the following: Triggering an account logout operation for the target account in the application page of the simulator; Or, the account logout event is triggered when it is detected that the account login information meets the account logout condition.

17. A desktop shortcut processing device, characterized in that: The device comprises: an application display module, configured to, in response to an account login operation triggered on a first terminal for a simulator, display, on an application page of the simulator, a list of applications matching the logged-in target account; the list of applications including at least one application identifier representing an application that has been triggered by the target account on a second terminal, the simulator being installed on the first terminal, and the applications simulated by the simulator being compatible with the second terminal; A shortcut display module is used to display a shortcut of the target application represented by the target application identifier on the desktop of the first terminal; the target application identifier is an application identifier that exists in the application list and the target application represented by the target application does not display a shortcut on the desktop The shortcut display cancellation module is configured to cancel display of the shortcut of the target application on the desktop of the first terminal in response to an account logout event for the target account.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 16 are implemented.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

20. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

Images