Multi-window implementation method, device, equipment and storage medium

By receiving the file path of the target application, generating the application directory and creating hard links, the problem of not being able to fully implement multiple applications is solved, and disk space usage is reduced.

CN116932069BActive Publication Date: 2026-06-26SHUPENG INFORMATION TECH (SHENZHEN) CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
SHUPENG INFORMATION TECH (SHENZHEN) CO LTD
Filing Date
2022-04-12
Publication Date
2026-06-26

AI Technical Summary

Technical Problem

In existing technologies, the application multi-instance method cannot achieve complete multi-instance, and copying the application package to different locations will lead to excessive disk space pressure.

Method used

By receiving the original file path and copy path of the target application, the file type is obtained, and an application directory is generated according to the type. Files of the first preset type are stored in the copy path, and files of the second preset type are created as hard links or copied to the copy path, ensuring that the application can be fully opened without occupying too much disk space.

Benefits of technology

It enables full multi-instance of applications, reduces disk space usage, and avoids disk pressure caused by copying copies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116932069B_ABST
    Figure CN116932069B_ABST
Patent Text Reader

Abstract

The application discloses an application multi-opening implementation method and device, equipment and storage medium, and the application multi-opening implementation method comprises the following steps: receiving an original file path and a copy path of a target application program; acquiring file types of a plurality of files under a storage address of the original file path; generating a corresponding application program directory according to the file type of a file of a first preset type, and creating the application program directory under a storage address corresponding to the copy path; and copying the file of a second preset type to the storage address corresponding to the copy path. According to the application, the file of the second preset type is copied to the storage address corresponding to the copy path, so that all original files under the original file path do not need to be copied to the storage address corresponding to the copy path, application complete multi-opening can be realized, disk space can be highly reused, and disk pressure caused by copying of the copy is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the technical field of terminal applications, and in particular to a method, apparatus, device, and storage medium for implementing multiple applications. Background Technology

[0002] When launching an application, the terminal's system platform typically starts the application by clicking the selected application icon in the application directory of the file explorer. However, if an application is already running, clicking the corresponding application icon again will not launch a new application by default, but will instead place the already running application in the screen window.

[0003] In related technologies, there are two main ways to run multiple instances of an application. One method is to launch the application by entering the executable file path of the target application through separate software, thus opening multiple instances. However, launching the application through File Explorer does not achieve the same result. The other method is to copy the application package to a new file directory and then launch it. However, copying the application package to different locations puts significant pressure on disk space. Summary of the Invention

[0004] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention proposes a method for implementing multiple applications, which enables dual-instance operation of applications while saving disk space.

[0005] The present invention also proposes an application multi-open implementation device.

[0006] The present invention also proposes an electronic device.

[0007] The present invention also proposes a computer-readable storage medium.

[0008] In a first aspect, one embodiment of the present invention provides a method for implementing multiple instances of an application, including:

[0009] Receive the original file path and copy path of the target application;

[0010] Obtain the file types of multiple files under the storage address of the original file path;

[0011] Generate a corresponding application directory based on the file type of the first preset type, and create the application directory at the storage address corresponding to the copy path;

[0012] Copy the file of the second preset file type to the storage address corresponding to the copy path.

[0013] The application multi-instance implementation method of the present invention has at least the following beneficial effects: the application directory is generated from files of the first preset file type and the application directory is stored in the storage address corresponding to the copy path, while the files of the second preset file type are copied to the storage address corresponding to the copy path. Thus, it is not necessary to copy all the original files under the original file path to the storage address corresponding to the copy path. Moreover, it can realize full application multi-instance, and can highly reuse disk space, reducing the disk pressure caused by copying copies.

[0014] According to other embodiments of the present invention, the method for implementing multiple instances of an application includes obtaining the file types of multiple files under the storage address of the original file path, which includes:

[0015] The files at the storage address corresponding to the original file path are recursively traversed to obtain the file types of multiple files.

[0016] According to other embodiments of the present invention, the application multi-instance implementation method includes the following file types: directory files, symbolic link files, and ordinary files, wherein the ordinary files include any one of the following: executable files and resource files.

[0017] According to other embodiments of the present invention, in the method for implementing multiple instances of an application, the first preset type is a directory file and a symbolic link file. The step of generating a corresponding application directory based on the file of the first preset type and creating the application directory at the storage address corresponding to the copy path includes:

[0018] Obtain file information for files of the type described, such as directory files or symbolic link files;

[0019] Based on the file information, create an application directory corresponding to the file information at the storage address corresponding to the copy path.

[0020] According to other embodiments of the present invention, in the method for implementing multiple instances of an application, the second preset type is an executable file that is the primary startup file, and the step of copying the file of the second preset type to the storage address corresponding to the copy path includes:

[0021] Obtain the file of the type described above, which is the main executable file, located at the storage address corresponding to the original file path, to obtain the program file;

[0022] Copy the program file to the storage address corresponding to the copy path.

[0023] According to other embodiments of the present invention, the application multi-instance implementation method further includes:

[0024] Create corresponding hard links for files whose file type is resource file and / or executable files that are not primary boot files, and store the hard links in the storage address corresponding to the copy path.

[0025] According to other embodiments of the present invention, the application multi-instance implementation method includes any one of the following resource files: image files, language files, configuration files, and signature files.

[0026] Secondly, one embodiment of the present invention provides an application multi-opening implementation apparatus, including:

[0027] The receiving module is used to receive the original file path and copy path of the target application;

[0028] The acquisition module is used to acquire the file types of multiple files under the storage address of the original file path;

[0029] The directory creation module is used to generate a corresponding application directory based on the file type being a first preset type, and to create the application directory at the storage address corresponding to the copy path.

[0030] The copy module is used to copy files of the second preset file type to the storage address corresponding to the copy path.

[0031] The application multi-instance implementation device of the present invention has at least the following beneficial effects: it generates an application directory from files of the first preset file type and stores the application directory in the storage address corresponding to the copy path, while copies files of the second preset file type to the storage address corresponding to the copy path. This eliminates the need to copy all original files under the original file path to the storage address corresponding to the copy path, and enables full application multi-instance while highly reusing disk space and reducing the disk pressure caused by copying copies.

[0032] Thirdly, one embodiment of the present invention provides an electronic device, comprising:

[0033] At least one processor, and,

[0034] A memory communicatively connected to the at least one processor; wherein,

[0035] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the application multi-instance implementation method as described in the first aspect.

[0036] Fourthly, one embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the application multiplication implementation method as described in the first aspect.

[0037] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the description and the accompanying drawings. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating a specific embodiment of the multi-open implementation method in this invention.

[0039] Figure 2 yes Figure 1 A schematic diagram of a specific embodiment of step S200;

[0040] Figure 3 yes Figure 1 A schematic diagram of a specific embodiment of step S300;

[0041] Figure 4 yes Figure 1 A schematic diagram of a specific embodiment of step S400;

[0042] Figure 5 This is a flowchart illustrating another specific embodiment of the multi-open implementation method in this invention.

[0043] Figure 6 This is a module block diagram of a specific embodiment of the electronic device in this invention.

[0044] Reference numerals: 100, processor; 200, memory. Detailed Implementation

[0045] The following will describe the concept and technical effects of the present invention clearly and completely with reference to embodiments, so as to fully understand the purpose, features and effects of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are all within the scope of protection of the present invention.

[0046] In the description of this invention, if directional descriptions are involved, such as "up," "down," "front," "back," "left," "right," etc., indicating the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, it is only for the convenience of describing the invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. If a feature is referred to as "set," "fixed," "connected," or "installed" on another feature, it can be directly set, fixed, or connected to the other feature, or it can be indirectly set, fixed, connected, or installed on the other feature.

[0047] In the description of the embodiments of the present invention, the term "several" means one or more, and the term "multiple" means two or more. The terms "greater than," "less than," and "exceeding" should be understood as excluding the stated number, while the terms "above," "below," and "within" should be understood as including the stated number. The terms "first" and "second" should be understood as distinguishing technical features, and not as indicating or implying relative importance, the number of indicated technical features, or the order of the indicated technical features.

[0048] Traditional terminal platforms require clicking the application icon in the application manager's program directory to launch an application. Once an application is already running, clicking its icon again won't launch a new application; instead, it will bring the already launched application window to the front of the screen. macOS, on the other hand, launches applications by clicking their icons in Launchpad or Finder. Clicking the icon twice in Launchpad or Finder won't launch two separate applications. Currently, there are two ways to run multiple instances of an application. One is using system software, such as Terminal.app, to launch the application by entering the executable file path or using a command-line tool to specify the application path. Theoretically, opening multiple Terminal windows and performing the same operation can open multiple instances of the same application. However, if the user clicks the application again in Finder or Launchpad after launching an application this way, the existing instance will still be launched, failing to achieve true application multi-instance functionality. The other method is to copy the application package to a new file directory and then launch it. Since the system determines whether an application should start by detecting the file system path where the executable file (also known as a mach-o file) of the application package is located, this method can achieve full multi-instance operation of the application because it creates copies in different locations in the file system. However, the drawback is that having multiple copies of the application package on the disk can put a lot of pressure on the disk space.

[0049] Based on this, this application discloses a method for implementing multiple application instances, which can support multiple application instances and reduce the disk pressure caused by copying copies.

[0050] The following technical terms need to be explained:

[0051] A hard link, also known as a link, is one or more filenames associated with a single file. Its function is to link a filename to an inode number used by the computer's file system. Therefore, we can link multiple filenames to the same file; for the same file, only the link relationship needs to be maintained, eliminating the need for multiple copies, thus saving hard drive space.

[0052] File types: The file system defines a variety of file types for different purposes.

[0053] Executable file: The core module of an application. When we say that an application is running, it is essentially the operating system loading its executable file and executing it.

[0054] Firstly, referring to Figure 1 This invention discloses a method for implementing multiple applications, including but not limited to steps S100 to S400.

[0055] S100, Receive the original file path and copy path of the target application;

[0056] S200: Obtain the file types of multiple files at the storage address corresponding to the original file path;

[0057] S300: Generate the corresponding application directory based on the file type of the first preset type, and create the application directory at the storage address corresponding to the copy path;

[0058] S400: Copy the file of the second preset type to the storage address corresponding to the copy path.

[0059] In step S100, the original files of the target application are stored in the storage address corresponding to the original file path, while the copy files of the target application are stored in the storage address corresponding to the copy path. Thus, by obtaining the original file path and the copy path, it is further determined which files in the original file need to be stored in the copy path.

[0060] For example, if the target application for achieving dual-app functionality is "Calculator", then the original file path of "Calculator" is " / System / Applications / Calculator.app", and then a location to store the copy needs to be specified, that is, the copy path is determined to be " / Users / xxx / Documents / Calculator.app".

[0061] Through steps S200 to S400, an application directory is generated for files of the first preset file type, and the application directory is stored in the storage address corresponding to the copy path. Files of the second preset file type are copied to the storage address corresponding to the copy path. This eliminates the need to copy all original files under the original file path to the storage address corresponding to the copy path, and enables full multi-instance of applications while highly reusing disk space, reducing the disk pressure caused by copying copies.

[0062] Reference Figure 2 In some embodiments, step S200 includes, but is not limited to, step S210.

[0063] S210. Recursively traverse the files at the storage address corresponding to the original file path to obtain the file types of multiple files.

[0064] After obtaining the original file path, recursively traverse the files at the storage address corresponding to the original file path, and recursively traverse the files to obtain the file type.

[0065] For example, if the original file path is " / System / Applications / Calculator.app", then " / System / Applications / Calculator.app" will be recursively traversed to obtain the file type of the file at the storage address corresponding to " / System / Applications / Calculator.app".

[0066] In some embodiments, the file types include: directory files, symbolic link files, and ordinary files, where ordinary files include any one of the following: executable files and resource files.

[0067] The executable file is the core module of the target application. When we say that an application is running, it is essentially the operating system loading its executable file and executing it.

[0068] Reference Figure 3 In some embodiments, the first preset type is a directory file and a symbolic link file, and step S300 includes, but is not limited to, steps S310 and S320.

[0069] S310. Obtain file information for files of type directory file or symbolic link file;

[0070] S320. Based on the file information, create the application directory corresponding to the file information at the storage address corresponding to the copy path.

[0071] If the file type is a directory file or a symbolic link file, the corresponding relationship needs to be restored to ensure that the file organization hierarchy is consistent with the original program package. Therefore, the file information of the file type is obtained, and then the application directory corresponding to the file information is created under the storage address corresponding to the copy path to ensure that the structure of the application directory under the copy path and the original file path is the same.

[0072] For example, if there is a Contents directory under the " / System / Applications / Calculator.app" directory, and the Contents directory contains directories named MacOS, Resources, etc., then we need to create the same directory under the copy path " / Users / xxx / Documents / Calculator.app" to keep the directory structure of the copy path consistent, and the parent location of the file storage can be specified arbitrarily.

[0073] Reference Figure 4 In some embodiments, the second preset type is the executable file that is started by the master, and step S400 includes, but is not limited to, steps S410 and S420.

[0074] S410. Obtain the program file of the main executable file type under the storage address corresponding to the original file path, so as to obtain the program file;

[0075] S420. Copy the program file to the storage address corresponding to the copy path.

[0076] Since the primary executable file is the core module of the target application, and the operating system essentially loads and executes its primary executable file, copying the program file (which is the primary executable file) from the storage address corresponding to the original file path to the storage address corresponding to the copy path ensures that both the original and copy paths contain executable files, enabling dual-instance application execution. Furthermore, only the primary executable file needs to be copied to the storage address corresponding to the copy path; no other files need to be copied, thus saving disk space while achieving dual-instance application execution.

[0077] For example, to copy the executable file to the copy path for "calculator.app", you only need to copy " / System / Applications / Calculator.app / Contents / MacOS / Calculator" to " / Users / xxx / Documents / Calculator.app / Contents / MacOS / Calculator".

[0078] In this application, a copy operation is only performed on a complete original file if the file type is executable. In the application package structure of macOS, executable files often account for less than 10% of the total package file size. For example, the file size of "calculator.app" above is 5.6MB, while the executable file size is 214KB, accounting for 3.7%. The resource files in the package actually occupy most of the disk space. Therefore, this application enables multiple applications to be run while saving disk space.

[0079] Reference Figure 5 In some embodiments, the application of the multiple-open implementation method also includes, but is not limited to, step S500.

[0080] S500: Create corresponding hard links for files whose file type is resource file and / or executable files that are not primary startup files, and store the hard links to the storage address corresponding to the copy path.

[0081] Resource files include: image files, language files, configuration files, and signature files. In addition, any file that is not an executable file in the application is also a resource file. Therefore, resource files are not limited to: image files, language files, configuration files, and signature files.

[0082] It's important to note that hard links should be created for resource files, specifically image files, language files, configuration files, and signature files. These hard links should then be stored in the storage address corresponding to the copy path. Additionally, while an application may have multiple executable files, only one is designated as the primary executable. Therefore, the primary executable is copied to the storage address corresponding to the copy path, while hard links to non-primary executables are created to save storage space. Since the primary executable file is the one that truly affects the ability to run multiple instances of an application, meaning the system determines whether a program is running based on the file system path where the primary executable file resides, it's crucial that multiple copies of the executable file exist in different file system paths when the target application needs to run multiple instances. If a hard link is created to reference the original executable file, the operating system will treat it as the same file. Therefore, this application completely copies the files of the primary executable file to the storage address corresponding to the copy path. For resource files, hard links are created to reference the original file, which does not affect the ability to run multiple instances of the target application and does not consume additional disk space. Thus, hard links to reference the original file are used to save disk space. Therefore, this application can achieve multiple application instances while saving disk space.

[0083] The following is for reference. Figures 1 to 5 The following describes in detail an application multi-instance implementation method according to an embodiment of the present invention, using a specific example. It is to be understood that the following description is merely illustrative and not intended to limit the invention in any specific way.

[0084] If the target application for implementing dual-opening is "Calculator", the original file path of "Calculator" is obtained as " / System / Applications / Calculator.app". Then, a location to store the copy needs to be specified, i.e., the copy path is determined as " / Users / xxx / Documents / Calculator.app". The path " / System / Applications / Calculator.app" is recursively traversed to obtain the file types of the files at the corresponding storage address. The executable file of the main application is copied to the copy path; only " / System / Applications / Calculator.app / Contents / MacOS / Calculator" needs to be copied to " / Users / xxx / Documents / Calculator.app / Contents / MacOS / Calculator". If the " / System / Applications / Calculator.app" directory contains a "Contents" directory, and the "Contents" directory contains directories named "MacOS", "Resources", etc., then we need to create the same directories under the copy path " / Users / xxx / Documents / Calculator.app" to ensure that the file directory structure of both is consistent. If the file type is a resource file, then create a hard link to the resource file and / or the non-main executable file and store it in the storage address corresponding to the copy path.

[0085] Secondly, referring to Figure 6 The present invention also discloses an application multi-open implementation device, comprising:

[0086] The receiving module 100 is used to receive the original file path and the copy path of the target application;

[0087] Module 200 is used to obtain the file types of multiple files under the storage address of the original file path;

[0088] The directory creation module 300 is used to generate the corresponding application directory based on the file type of the first preset type, and to create the application directory at the storage address corresponding to the copy path.

[0089] The copy module 400 is used to copy files of the second preset file type to the storage address corresponding to the copy path.

[0090] The application directory is generated for files of the first preset file type, and the application directory is stored at the storage address corresponding to the copy path. Files of the second preset file type are copied to the storage address corresponding to the copy path. This eliminates the need to copy all original files under the original file path to the storage address corresponding to the copy path. It can achieve full application multi-instance and high disk space reuse, reducing the disk pressure caused by copying copies.

[0091] The specific operation process of one application multi-open implementation device is the same as that of the application multi-open implementation method in the first aspect, and will not be repeated here.

[0092] Thirdly, an electronic device includes: at least one processor 100, and a memory 200 communicatively connected to the at least one processor 100; wherein the memory 200 stores instructions executable by the at least one processor 100, the instructions being executed by the at least one processor 100 to enable the at least one processor 100 to perform the application multi-opening implementation method as described in the first aspect.

[0093] The electronic device can be a mobile terminal device or a non-mobile terminal device. Mobile terminal devices can be mobile phones, tablets, laptops, PDAs, in-vehicle terminal devices, wearable devices, super mobile personal computers, netbooks, personal digital assistants, CPEs, UFIs (wireless hotspot devices), etc.; non-mobile terminal devices can be personal computers, televisions, ATMs, or self-service machines, etc. The embodiments of this invention are not specifically limited.

[0094] The memory 200 can be either external or internal memory. External memory can be an external memory card, such as a Micro SD card. The external memory card communicates with the processor through an external memory interface to perform data storage functions. For example, music, video, and other files can be saved on the external memory card. Internal memory can be used to store executable program code, which includes instructions.

[0095] Processor 100 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0096] Fourthly, embodiments of the present invention also disclose a computer-readable storage medium storing computer-executable instructions for causing a computer to execute the application multi-instance implementation method as described in the first aspect.

[0097] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0098] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0099] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the present invention is not limited to the above embodiments, and various changes can be made within the scope of knowledge possessed by those skilled in the art without departing from the spirit of the present invention. Furthermore, the embodiments of the present invention and the features thereof can be combined with each other unless otherwise specified.

Claims

1. A method for implementing multiple instances of an application, characterized in that, include: Receive the original file path and copy path of the target application; Obtain the file types of multiple files under the storage address corresponding to the original file path; wherein, the file types include: directory files, symbolic link files, and ordinary files, and the ordinary files include any one of the following: executable files and resource files; Generate a corresponding application directory based on the file type of the first preset type, and create the application directory at the storage address corresponding to the copy path; Copy the file whose file type is the second preset type to the storage address corresponding to the copy path; The first preset type is directory files and symbolic link files. The step of generating a corresponding application directory based on files of the first preset type and creating the application directory at the storage address corresponding to the copy path includes: Obtain file information for files of the type described, such as directory files or symbolic link files; Based on the file information, create an application directory corresponding to the file information at the storage address corresponding to the copy path; The second preset type is an executable file for primary startup. The step of copying the file of the second preset type to the storage address corresponding to the copy path includes: Obtain the file of the type described above, which is the main executable file, located at the storage address corresponding to the original file path, to obtain the program file; Copy the program file to the storage address corresponding to the copy path; Create corresponding hard links for files whose file type is resource file and / or executable files that are not primary startup files, and store the hard links in the storage address corresponding to the copy path.

2. The application multi-instance implementation method according to claim 1, characterized in that, The step of obtaining the file types of multiple files under the storage address of the original file path includes: The files at the storage address corresponding to the original file path are recursively traversed to obtain the file types of multiple files.

3. The application multi-instance implementation method according to claim 1, characterized in that, The resource files include any of the following: image files, language files, configuration files, and signature files.

4. A device for implementing multiple applications, characterized in that, The device includes: The receiving module is used to receive the original file path and copy path of the target application; The acquisition module is used to acquire the file types of multiple files under the storage address corresponding to the original file path; wherein, the file types include: directory files, symbolic link files and ordinary files, and the ordinary files include any one of the following: executable files and resource files; The directory creation module is used to generate a corresponding application directory based on the file type being a first preset type, and to create the application directory at the storage address corresponding to the copy path. The copy module is used to copy the file of the second preset type to the storage address corresponding to the copy path; The first preset type is directory files and symbolic link files. The step of generating a corresponding application directory based on files of the first preset type and creating the application directory at the storage address corresponding to the copy path includes: Obtain file information for files of the type described, such as directory files or symbolic link files; Based on the file information, create an application directory corresponding to the file information at the storage address corresponding to the copy path; The second preset type is an executable file for primary startup. The step of copying the file of the second preset type to the storage address corresponding to the copy path includes: Obtain the file of the type described above, which is the main executable file, located at the storage address corresponding to the original file path, to obtain the program file; Copy the program file to the storage address corresponding to the copy path; Create corresponding hard links for files whose file type is resource file and / or executable files that are not primary startup files, and store the hard links in the storage address corresponding to the copy path.

5. An electronic device, characterized in that, include: At least one processor, and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the application multi-opening implementation method as described in any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the application multi-instance implementation method as described in any one of claims 1 to 3.