Android application packaging and installing system, method and device, medium and product

Abstract

The invention discloses an Android application packaging and installing system, method and device, a medium and a product, and relates to the technical field of computer operating systems, and the system comprises a cloud and an application installing terminal; the cloud end obtains an externally uploaded Android application, analyzes the Android application, generates a shell application, generates a configuration file, packages the shell application and the configuration file into an application package in a preset format, and issues the application package to the cloud end; if the application installation terminal receives an installation request for installing the application package, the application package is downloaded from the cloud through the application market according to the installation request, and a first Android compatible subsystem in the OpenHarmony system analyzes the application package to obtain a shell application, an Android application and a configuration file; the second Android compatible subsystem in the Android system installs the Android application according to the configuration file, and the first Android compatible subsystem installs the shell application according to the configuration file, so that automatic packaging and uploading of the Android application and installation of the Android application by the OpenHarmony system are realized.

Description

Technical Field

[0001] The present application relates to the technical field of computer operating systems, and in particular to Android application packaging and installation systems, methods, devices, media and products. Background Art

[0002] With the rapid development of information technology and the widespread popularity of smart terminal devices, the compatibility and scalability of operating systems as the core software of devices have become the focus of users. As an open source project incubated and operated by the OpenAtom Foundation, OpenHarmony aims to promote the development of the full-scenario, full-connection, and full-intelligence era, and provides a unified operating system framework and platform for smart terminal devices. The project supports a variety of device types, including mobile phones, tablets, smart homes, wearable devices, etc., and is committed to realizing the vision of the Internet of Everything. However, in the current operating system environment, the Android system still occupies an important position with its extensive application ecology and huge user base. In order to make full use of the application resources of the Android system and give full play to the advantages of OpenHarmony in full-scenario and full-connection, how to achieve the compatible operation of the OpenHarmony operating system with Android applications has become a technical problem that needs to be solved urgently. Traditional solutions often require manual packaging and installation of Android applications in the OpenHarmony system, which not only increases the complexity of user operations, but also limits the compatibility and scalability of the system. Summary of the invention

[0003] The main purpose of this application is to provide an Android application packaging and installation system, method, device, medium and product, aiming to realize automatic packaging and uploading of Android applications, and direct installation of Android applications by the OpenHarmony system.

[0004] To achieve the above-mentioned purpose, the present application proposes an Android application packaging and installation system, the Android application packaging and installation system includes a cloud and an application installation terminal that are communicatively connected to each other, the application installation terminal includes an Android system and an OpenHarmony system that are communicatively connected to each other, the OpenHarmony system includes a first Android compatible subsystem and an application market module, the Android system includes a second Android compatible subsystem, and the first Android compatible subsystem is communicatively connected to the second Android compatible subsystem;

[0005] The cloud is used to obtain externally uploaded Android applications, parse the Android applications, generate shell applications, generate configuration files based on the Android applications and shell applications, and package the Android applications, shell applications and configuration files into an application package in a preset format;

[0006] The application market module is used to download the application package from the cloud according to the installation request if an installation request for installing the application package is received;

[0007] The first Android compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the second Android compatible subsystem;

[0008] A second Android compatible subsystem, used for installing Android applications according to the configuration file;

[0009] The first Android compatible subsystem is used to install the shell application according to the configuration file when monitoring that the Android application is installed.

[0010] In one embodiment, the Android system further includes an Everestd subsystem, and the OpenHarmony system further includes an Everest_service subsystem, and the Everestd subsystem is communicatively connected with the Everest_service subsystem;

[0011] Everest_service subsystem, used to create sockets;

[0012] Everestd subsystem, used to create a client socket and use the client socket to establish a connection with the socket of the Everest_service subsystem;

[0013] The first Android compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the Everestd subsystem;

[0014] The Everestd subsystem is used to receive the Android application and configuration file sent by the first Android compatible subsystem, encode the Android application and configuration file, and send the encoded Android application and configuration file to the Everest_service subsystem through the client socket;

[0015] The Everest_service subsystem is used to receive the encoded Android application through the socket, decode the encoded Android application, obtain the Android application and the configuration file, and send the Android application and the configuration file to the second Android compatible subsystem;

[0016] The second Android compatible subsystem is used to receive the Android application and configuration file of the Everest_service subsystem, and install the Android application according to the configuration file.

[0017] In one embodiment, the Android application packaging and installation method is applied to the cloud in the Android application packaging and installation system, and includes:

[0018] Get externally uploaded Android applications, parse the Android applications, and generate shell applications;

[0019] A configuration file is generated based on the Android application and the shell application, and the Android application, the shell application and the configuration file are packaged into an application package in a preset format, wherein if the application installation terminal receives an installation request for installing the application package, the application package is downloaded from the cloud through the application market module in the application installation terminal according to the installation request, and the application package is parsed through the first Android compatible subsystem in the OpenHarmony system of the application installation terminal to obtain the shell application, the Android application and the configuration file; the Android application is installed according to the configuration file through the second Android compatible subsystem in the Android system of the application installation terminal; and when it is monitored that the installation of the Android application is completed, the shell application is installed according to the configuration file through the first Android compatible subsystem.

[0020] In one embodiment, the Android application packaging and installation method is applied to an application installation terminal connected to the cloud in an Android application packaging and installation system, and includes:

[0021] If an installation request for installing an application package is received, the application package is downloaded from the cloud according to the installation request, wherein the cloud obtains an externally uploaded Android application, parses the Android application, generates a shell application, generates a configuration file according to the Android application and the shell application, and packages the Android application, the shell application and the configuration file into an application package in a preset format;

[0022] Calling the first Android compatible subsystem in the OpenHarmony system of the application installation terminal to parse the application package and obtain the shell application, the Android application and the configuration file;

[0023] Invoke a second Android compatible subsystem in the Android system of the application installation terminal to install the Android application according to the configuration file;

[0024] When it is detected that the Android application is installed, the first Android compatible subsystem is called to install the shell application according to the configuration file.

[0025] In one embodiment, before the step of calling the second Android compatible subsystem in the Android system to install the Android application according to the configuration file, the following steps are included:

[0026] Encode the Android application and configuration file through the Everestd subsystem in the Android system, and transmit the encoded Android application and configuration file to the Everest_service subsystem in the OpenHarmony system through the client socket preset in the Everestd subsystem;

[0027] The encoded Android application and configuration file are received and decoded through the socket preset in the Everest_service subsystem to obtain the Android application and configuration file.

[0028] In one embodiment, the step of calling the first Android compatible subsystem to install the shell application according to the configuration file includes:

[0029] Detecting the life cycle of Android applications through a second Android compatible subsystem;

[0030] If the lifecycle is updated, the lifecycle update is transmitted to the socket in the Everest_service subsystem through the client socket;

[0031] The lifecycle updates are synchronized to the shell application through the first Android compatible subsystem.

[0032] In one embodiment, the step of transmitting the encoded Android application to the Everest_service subsystem in the OpenHarmony system through the client socket preset in the Everestd subsystem includes:

[0033] Create a socket in the Everest_service subsystem;

[0034] Create a client socket in the Everestd subsystem and use the client socket to establish a connection with the socket of the Everest_service subsystem.

[0035] In addition, to achieve the above-mentioned purpose, the present application also proposes a medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the Android application packaging and installation method as described above are implemented.

[0036] In addition, to achieve the above-mentioned purpose, the present application also provides a product, which is a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps of the Android application packaging and installation method as described above.

[0037] One or more technical solutions proposed in this application have at least the following technical effects:

[0038] The present application provides an Android application packaging and installation system, including a cloud and an application installation terminal that are communicatively connected to each other, the application installation terminal includes an Android system and an OpenHarmony system that are communicatively connected to each other, the OpenHarmony system includes a first Android compatible subsystem and an application market module, the Android system includes a second Android compatible subsystem, and the first Android compatible subsystem is communicatively connected to the second Android compatible subsystem, thereby greatly improving the compatibility and deployment efficiency of Android applications on the OpenHarmony system; the cloud is used to obtain externally uploaded Android applications, parse the Android applications, generate shell applications, generate configuration files according to the Android applications and the shell applications, and package the Android applications, the shell applications and the configuration files into an application package in a preset format, thereby realizing an automated packaging process for Android applications and reducing Less manual intervention improves packaging efficiency and accuracy, and also facilitates the distribution and management of applications; if the application market module in the application installation terminal receives an installation request for an application package, it downloads the application package from the cloud according to the installation request; the first Android compatible subsystem parses the application package to obtain the shell application, the Android application and the configuration file, and sends the Android application and the configuration file to the second Android compatible subsystem; the second Android compatible subsystem installs the Android application according to the configuration file; when it is detected that the Android application is installed, the first Android compatible subsystem installs the shell application according to the configuration file, realizing the direct installation and operation of the Android application by the OpenHarmony system, without the need for users to perform complex settings or operations, improving the user experience, and also introducing more application resources to the OpenHarmony system. In summary, this application realizes the automatic packaging and uploading of Android applications, as well as the direct installation and operation of Android applications by the OpenHarmony system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0041] Figure 1 A schematic diagram of the process of packaging and installing the Android application system for this application;

[0042] Figure 2 This is a flowchart of Embodiment 2 of the Android application packaging and installation method of this application;

[0043] Figure 3A schematic diagram of the structure of the application package for the Android application packaging and installation method of this application;

[0044] Figure 4 This is a flowchart of Embodiment 3 of the Android application packaging and installation method of this application;

[0045] Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the Android application packaging and installation method in the embodiment of the present application.

[0046] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0047] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0048] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0049] Based on this, an embodiment of the present application provides an Android application packaging and installation system.

[0050] In this embodiment, the Android application packaging and installation system includes a cloud and an application installation terminal that are communicatively connected to each other, the application installation terminal includes an Android system and an OpenHarmony system that are communicatively connected to each other, the OpenHarmony system includes a first Android compatible subsystem and an application market module, the Android system includes a second Android compatible subsystem, and the first Android compatible subsystem is communicatively connected to the second Android compatible subsystem;

[0051] The cloud is used to obtain externally uploaded Android applications, parse the Android applications, generate shell applications, generate configuration files based on the Android applications and shell applications, and package the Android applications, shell applications and configuration files into an application package in a preset format;

[0052] The application market module is used to download the application package from the cloud according to the installation request if an installation request for installing the application package is received;

[0053] The first Android compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the second Android compatible subsystem;

[0054] A second Android compatible subsystem, used for installing Android applications according to the configuration file;

[0055] The first Android compatible subsystem is used to install the shell application according to the configuration file when monitoring that the Android application is installed.

[0056] In this embodiment, the cloud is a highly integrated and automated server-side solution, which is specially designed to handle the packaging process of Android applications. The system specifically includes an application receiving and verification module, which is responsible for obtaining externally uploaded Android applications and performing preliminary verification; an application parsing module, which deeply analyzes the internal structure, dependency library and permission requirements of Android applications; a shell application generator, which intelligently generates a shell application that matches the Android application based on the parsing results to provide the necessary operating environment support; a configuration file creation tool, which generates a configuration file containing key information such as installation parameters, operating permissions, and dependencies based on the specific information of the Android application and the shell application; and an application packaging and publishing module, which packages the Android application, the shell application and the configuration file into a single application package in a preset format and automatically publishes it to the cloud. The cloud serves as a data storage and distribution center, providing a wide range of access and distribution channels for applications. Users can download and install this application package through the cloud, so as to enjoy the same application experience on different devices. The main function of the cloud is to automatically process Android applications so that they can be smoothly migrated and run on the OpenHarmony system, thereby reducing the cost and complexity of application migration.

[0057] The application installation terminal is a smart device or software environment that integrates the Android system and the OpenHarmony system, which provides users with a rich selection of applications and a convenient installation experience. The terminal specifically includes an Android system module, which provides an operating environment for native Android applications; an OpenHarmony system module, which embeds a compatible subsystem designed specifically for Android applications to support the smooth synchronization of life cycles and message transmission between shell applications on the OpenHarmony system and Android applications; and an application market module, which serves as an entry point for users to download and install applications, and provides a one-stop service for application search, download, installation and update. The main function of the application installation terminal is to serve as a bridge between users and applications, receive and process user installation requests, download and install the application packages required by users from the application market, and ensure the stable operation of applications and continuous optimization of user experience.

[0058] The application market module (hereinafter referred to as the application market) in the application installation terminal is a functional component, which includes a download function for downloading application packages from the cloud and a user interface for displaying application packages and receiving user installation requests. The main purpose of the application market is to download the corresponding application package from the cloud according to the request after receiving the user's installation request.

[0059] The first Android compatible subsystem in the application installation terminal is a subsystem for processing an Android application package, which includes a parser for parsing the application package to extract a shell application, an Android application, and a configuration file, and a communication interface for communicating with the second Android compatible subsystem. The main purpose of the first Android compatible subsystem is to parse the application package and send the parsed Android application and configuration file to the second Android compatible subsystem for installation, and after the Android application is installed, install the shell application according to the configuration file.

[0060] The second Android-compatible subsystem in the application installation terminal is a subsystem for installing Android applications, which includes an installer for installing Android applications according to a configuration file and a security management module for ensuring the security of the installation process. The main purpose of the second Android-compatible subsystem is to safely install the corresponding Android application according to the configuration file received from the first Android-compatible subsystem.

[0061] The entire Android application packaging and installation system realizes the automatic packaging and uploading of Android applications and the intelligent process of application installation through the close cooperation between the cloud and the application installation terminal. Specifically, the system first uses the application receiving and verification module in the cloud to receive the externally uploaded Android application, and performs in-depth analysis through the application analysis module. Then, the shell application generator generates the shell application according to the analysis results, and the configuration file making tool generates the configuration file containing key information. Then, the application packaging and publishing module packages the Android application, the shell application and the configuration file into an application package and publishes it to the specified cloud. When the user issues an installation request through the application installation terminal, the system will connect to the specified cloud through the application market, thereby downloading the corresponding application package from the cloud, and using the first Android compatible subsystem in the OpenHarmony system to parse the application package to obtain the shell application, Android application and configuration file. Then, the second Android compatible subsystem in the Android system automatically installs the Android application according to the installation parameters and dependencies in the configuration file. After the Android application is installed, the first Android compatible subsystem in the OpenHarmony system installs the shell application according to the configuration file, thereby ensuring that the Android application can run smoothly on the OpenHarmony system.

[0062] This embodiment provides an Android application packaging and installation system, including a cloud and an application installation terminal that are communicatively connected to each other, the application installation terminal includes an Android system and an OpenHarmony system that are communicatively connected to each other, the OpenHarmony system includes a first Android compatible subsystem and an application market module, the Android system includes a second Android compatible subsystem, and the first Android compatible subsystem is communicatively connected to the second Android compatible subsystem, thereby greatly improving the compatibility and deployment efficiency of Android applications on the OpenHarmony system; the cloud is used to obtain externally uploaded Android applications, parse the Android applications, generate shell applications, generate configuration files according to the Android applications and the shell applications, and package the Android applications, the shell applications and the configuration files into an application package in a preset format, thereby realizing an automated packaging process for Android applications and reducing Less manual intervention improves packaging efficiency and accuracy, and also facilitates application distribution and management; if the application market module in the application installation terminal receives an installation request for an application package, it downloads the application package from the cloud according to the installation request; the first Android compatible subsystem parses the application package to obtain a shell application, an Android application, and a configuration file, and sends the Android application and the configuration file to the second Android compatible subsystem; the second Android compatible subsystem installs the Android application according to the configuration file; when it is detected that the Android application has been installed, the first Android compatible subsystem installs the shell application according to the configuration file, realizing the direct installation and operation of the Android application by the OpenHarmony system, without the need for users to perform complex settings or operations, improving the user experience, and also introducing more application resources to the OpenHarmony system. In summary, this embodiment realizes the automatic packaging and uploading of Android applications, as well as the direct installation and operation of Android applications by the OpenHarmony system.

[0063] In a feasible implementation, the Android system further includes an Everestd subsystem, and the OpenHarmony system further includes an Everest_service subsystem, and the Everestd subsystem is communicatively connected with the Everest_service subsystem;

[0064] Everest_service subsystem, used to create sockets;

[0065] Everestd subsystem, used to create a client socket and use the client socket to establish a connection with the socket of the Everest_service subsystem;

[0066] The first Android compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the Everestd subsystem;

[0067] The Everestd subsystem is used to receive the Android application and configuration file sent by the first Android compatible subsystem, encode the Android application and configuration file, and send the encoded Android application and configuration file to the Everest_service subsystem through the client socket;

[0068] The Everest_service subsystem is used to receive the encoded Android application through the socket, decode the encoded Android application, obtain the Android application and the configuration file, and send the Android application and the configuration file to the second Android compatible subsystem;

[0069] The second Android compatible subsystem is used to receive the Android application and configuration file of the Everest_service subsystem, and install the Android application according to the configuration file.

[0070] In this embodiment, the Everest_service subsystem is a service module in the OpenHarmony system that is specially designed for cross-system communication. It specifically includes a socket creation module, which is responsible for creating a socket for receiving data within the OpenHarmony system; a data receiving module, which is used to monitor and receive data sent from other systems (such as the Android system) through the socket; a data decoding module, which decodes the received encoded data to restore the original application data; and an application forwarding module, which forwards the decoded application data to other subsystems in the OpenHarmony system (such as the second Android compatible subsystem) for processing. The main function of the Everest_service subsystem is to serve as a communication bridge between the OpenHarmony system and the Android system, ensuring that application data can be transmitted safely and efficiently between the two systems.

[0071] The Everestd subsystem is a client module in the Android system that cooperates with the Everest_service subsystem. It specifically includes a client socket creation module, which is responsible for creating a client socket for sending data within the Android system; a data encoding module, which encodes the application data to be sent to ensure the security and integrity of the data during transmission; a data sending module, which sends the encoded application data to the socket of the Everest_service subsystem through the client socket; and a communication status monitoring module, which monitors the communication status in real time to ensure smooth data transmission. The main function of the Everestd subsystem is to serve as a communication client between the Android system and the OpenHarmony system, responsible for sending Android application data to the Everest_service subsystem and receiving its feedback.

[0072] The first Android compatibility subsystem is a module in the Android system that is specifically used to parse and process application packages from the OpenHarmony system. It specifically includes an application package parsing module, which is used to parse the application package to extract the shell application, Android application and configuration file; an application data forwarding module, which forwards the parsed Android application data to the Everestd subsystem for processing; and a configuration file management module, which is used to manage and maintain the integrity and validity of the configuration file. The main function of the first Android compatibility subsystem is to ensure that the application package can be correctly parsed and processed, and to provide necessary support for the installation of Android applications across systems.

[0073] The second Android compatibility subsystem is a module in the OpenHarmony system that is specifically used to install and run Android applications. It specifically includes an application installation module, which is used to receive Android application data forwarded by the Everest_service subsystem and install it according to the configuration file; an application running module, which provides operating environment support for installed Android applications; and an application management module, which is used to manage the life cycle and permissions of installed Android applications. The main function of the second Android compatibility subsystem is to ensure that Android applications can run smoothly on the OpenHarmony system and provide users with a good application experience.

[0074] With the assistance of the added Everest_service subsystem and Everestd subsystem, communication between systems becomes more convenient and efficient. Specifically, when the Android system needs to send Android application data to the OpenHarmony system, the Everestd subsystem creates a client socket and sends the encoded Android application data to the socket of the Everest_service subsystem through the socket. After receiving the data, the Everest_service subsystem decodes it and forwards the decoded Android application data to the second Android compatible subsystem for installation. In this process, the Everest_service subsystem and the Everestd subsystem realize cross-system data transmission through sockets, ensuring the integrity and security of the data.

[0075] When the application package is installed, the data flow between the Android system and the OpenHarmony system mainly includes the steps of application package parsing, application data encoding and sending, data decoding and receiving, and application installation. These steps are successfully completed with the assistance of the Everest_service subsystem and the Everestd subsystem, ensuring that the Android application can be smoothly installed and run on the OpenHarmony system. After the application package is installed, the data flow between the Android system and the OpenHarmony system mainly focuses on the operation and management of the application. The second Android compatible subsystem will be responsible for the operating environment support and management of Android applications, while the Everest_service subsystem and the Everestd subsystem may continue to provide communication support in the background to ensure that data synchronization and interaction between the two systems can proceed smoothly. In addition, the system can also provide real-time data synchronization mechanisms, application status monitoring and feedback mechanisms, etc. to further improve the stability of the system and user experience.

[0076] Exemplary, reference Figure 1 First, the developer uploads the Android application to the cloud, which parses the Android application, generates a shell application, and creates a configuration file. Subsequently, the Android application, the shell application, and the configuration file are packaged into an application package and put on the shelf. After being put on the shelf, other developers can see the application package information, and the application market can also display the application package information for users to download. On the application installation terminal side, the OpenHarmony system downloads the application package from the application market through the first Android compatible subsystem. Then, the first Android compatible subsystem is responsible for parsing the application package, generating Android applications and shell applications, and transmitting the Android application to the second Android compatible subsystem on the Android system through the Everest_service subsystem and the Everestd subsystem. The second Android compatible subsystem receives and installs the Android application. After the Android application is installed, the second Android compatible subsystem Everestd subsystem and the Everest_service subsystem notify the first Android compatible subsystem to install the shell application. During the installation process, the two Android compatible subsystems synchronize the shell application and Android application life cycle and transmit messages through the Everest_service subsystem and the Everestd subsystem. When the shell application is installed, the first Android compatible subsystem notifies the application market that the installation is complete, and subsequent steps can be performed, such as sending a message to notify the user.

[0077] This embodiment realizes efficient and secure communication between the Android system and the OpenHarmony system by introducing the Everest_service subsystem and the Everestd subsystem. This innovative design not only simplifies the parsing, encoding, transmission and installation process of the application package, but also significantly improves the compatibility and stability of cross-system application deployment. The Everest_service subsystem acts as a communication bridge to ensure the seamless transmission of application data between the two systems, while the Everestd subsystem acts as a client and is responsible for encoding and sending data. The two subsystems work together to enable Android applications to be smoothly installed and run on the OpenHarmony system, providing users with richer and more diverse application choices. At the same time, the solution also has mechanisms such as real-time data synchronization, application status monitoring and feedback, which further improves the overall performance of the system and user experience.

[0078] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the first embodiment can be referred to the above introduction and will not be repeated later.

[0079] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a terminal system, etc. that can realize the above functions. The following takes the Android application packaging and installation system (hereinafter referred to as the system) as an example to illustrate this embodiment and the following embodiments.

[0080] This embodiment also provides an Android application packaging and installation method, which is applied to the cloud in the Android application packaging and installation system. Figure 2 The method comprises steps S11 to S12:

[0081] Step S11, obtaining an externally uploaded Android application, parsing the Android application, and generating a shell application;

[0082] Step S12, generate a configuration file based on the Android application and the shell application, and package the Android application, the shell application and the configuration file into an application package in a preset format, wherein, if the application installation terminal receives an installation request for installing the application package, the application package is downloaded from the cloud through the application market module in the application installation terminal according to the installation request, and the application package is parsed by the first Android compatible subsystem in the OpenHarmony system of the application installation terminal to obtain the shell application, the Android application and the configuration file; the Android application is installed according to the configuration file through the second Android compatible subsystem in the Android system of the application installation terminal; when it is monitored that the installation of the Android application is completed, the shell application is installed according to the configuration file through the first Android compatible subsystem.

[0083] It should be noted that the shell application is a lightweight application framework that provides the compatibility layer and environment required for Android applications to run on non-native Android systems (OpenHarmony systems in this embodiment). Configuration files are files that contain various parameters and settings required for application installation and operation, such as permission declarations, dependencies, etc. The application package is a single file that packages the Android application, shell application, and configuration file. It has a specific format for easy distribution and installation. In this embodiment, it is the .acs file format.

[0084] First, the Android application is uploaded to the cloud. In this step, the developer or user uploads the developed Android application file to the specified location of the cloud. Then, the cloud parses the Android application to generate a shell application. A parser will run inside the system, which will deeply analyze the code, resource files and configuration files of the Android application, and then generate a matching shell application based on this information. The main function of the shell application is to provide a compatibility layer so that the Android application can be used in the OpenHarmony system. Then, a configuration file is generated based on the Android application and the shell application, and the three are packaged into an application package. The configuration file contains all the key information required for the installation and operation of the application, such as permission declarations, dependencies, etc. The cloud will integrate this information into a configuration file and package it with the Android application and the shell application into an application package with a specific format. Subsequently, the cloud will publish the application package to the cloud. The application installation terminal can be a device with an operating system such as a smartphone or tablet, or a software environment such as an emulator. The application market is a platform on the application installation terminal for displaying, downloading and installing application packages. The cloud will upload the packaged application package to a designated cloud (such as the server of the application market) for users to download and install.

[0085] When the user receives an installation request to install the application package through the application installation terminal, the system will start downloading and parsing the application package. In the OpenHarmony system, the first Android compatible subsystem will be responsible for parsing the application package and extracting the shell application, Android application and configuration file. Then, the second Android compatible subsystem (located in the Android system) will start installing the Android application according to the information in the configuration file. In this step, the second Android compatible subsystem will read the installation parameters and dependencies in the configuration file, and then install the Android application to the specified location of the Android system according to these parameters and relationships. Finally, when the Android application is installed, the first Android compatible subsystem will start installing the shell application according to the information in the configuration file. The installation process of the shell application is similar to that of the Android application, but it should be noted that the main function of the shell application is to provide a compatibility layer so that the installed Android application can run smoothly on the OpenHarmony system.

[0086] Exemplary, reference Figure 3 , Figure 3 It is a schematic diagram of the structure of the application package, including an Android application (in the .apk file format in this embodiment), a shell application (i.e., an OpenHarmony application, which corresponds one-to-one to the Android application in the application installation terminal, in the .hap file format in this embodiment), and a configuration file (in the json file format in this embodiment).

[0087] In this embodiment, the cloud, the application installation terminal and their internal subsystems work together to realize the packaging, distribution and installation of Android applications on non-native Android systems. This embodiment not only improves the portability and compatibility of applications, but also provides users with more convenient and rich application choices.

[0088] Based on the first or second embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those in the first or second embodiment can be referred to the above description, and will not be repeated in the following. This embodiment also provides an Android application packaging and installation method, which is applied to an application installation terminal in an Android application packaging and installation system, referring to Figure 4 The method comprises steps S21 to S24:

[0089] Step S21, if an installation request for installing an application package is received, the application package is downloaded from the cloud according to the installation request, wherein the cloud obtains an externally uploaded Android application, parses the Android application, generates a shell application, generates a configuration file according to the Android application and the shell application, and packages the Android application, the shell application and the configuration file into an application package in a preset format;

[0090] As the front end of the entire process, the cloud is responsible for receiving and processing Android applications uploaded from the outside. Inside the system, an automated parser will deeply analyze the composition of the Android application, including its code, resource files, and configuration files. Based on this information, the parser will generate a shell application that matches it. The shell application is a lightweight application framework that aims to provide a compatibility layer for Android applications to run in non-native Android environments (such as OpenHarmony). Next, the cloud will integrate the Android application, the shell application, and a configuration file containing key information required for installation and operation. These elements are packaged into an application package with a specific format and then published to the cloud for users to download and install.

[0091] Step S22, calling the first Android compatible subsystem in the OpenHarmony system of the application installation terminal to parse the application package and obtain the shell application, the Android application and the configuration file;

[0092] Step S23, calling a second Android compatible subsystem in the Android system of the application installation terminal to install the Android application according to the configuration file;

[0093] Step S24, when it is detected that the Android application is installed, the first Android compatible subsystem is called to install the shell application according to the configuration file.

[0094] When an application installation terminal (such as a smartphone, tablet, etc.) receives a request to install a preset application package, the entire installation process is immediately initiated. The application installation terminal will download the corresponding application package from the cloud through the application market according to the installation request. This process involves the application of network communication protocols (such as HTTP / HTTPS) to ensure accurate data transmission. After the download is completed, the application installation terminal will call the first Android compatible subsystem in its internal OpenHarmony system to parse the application package. This subsystem has the ability to parse application packages in a specific format and can extract shell applications, Android applications and configuration files from them. Subsequently, the application installation terminal will call the second Android compatible subsystem in its Android system. This subsystem starts to install the Android application based on the information in the configuration file. This step involves decompressing the Android application code, verifying and granting permissions, and registering and starting the application. When the Android application is installed, the first Android compatible subsystem will start to install the shell application based on the information in the configuration file. The installation process of the shell application is similar to that of the Android application, but it focuses more on providing a compatibility layer to ensure that the Android application can run smoothly on the OpenHarmony system.

[0095] This embodiment realizes an efficient and secure Android application packaging and installation process through close cooperation between the cloud and the application installation terminal. This process not only improves the portability and compatibility of the application, but also provides users with more convenient and rich application selection.

[0096] In a feasible implementation manner, before step S23, steps A10 to A20 are included:

[0097] Step A10, encoding the Android application and configuration file through the Everestd subsystem in the Android system, and transmitting the encoded Android application and configuration file to the Everest_service subsystem in the OpenHarmony system through the client socket preset in the Everestd subsystem;

[0098] It should be noted that encoding is the process of converting information from one form or format to another. Here, it refers to compressing, encrypting or otherwise converting the data of the Android application for safe and efficient transmission. The client socket is an endpoint for sending and receiving data in network communications. In this embodiment, it is the communication channel used by the Everestd subsystem to transmit the encoded Android application to the Everest_service subsystem in the OpenHarmony system.

[0099] Step A20, receiving and decoding the encoded Android application and configuration file through the socket preset in the Everest_service subsystem to obtain the Android application and configuration file.

[0100] It should be noted that in network programming, a socket is an endpoint of network communication that supports the TCP / IP protocol. In this embodiment, it refers to the communication channel used by the Everest_service subsystem to receive data from the Everestd subsystem. Decoding is the reverse process of encoding, that is, restoring the encoded information to its original form or format. Here, it refers to decompressing, decrypting, or otherwise restoring the received encoded Android application data to obtain the original Android application.

[0101] First, in the Android system, the Everestd subsystem encodes the Android application. In this step, the Everestd subsystem reads the data of the Android application, and then processes the data using a specific encoding algorithm (such as compression, encryption, etc.) to generate the encoded Android application data. The purpose of encoding is to improve the efficiency and security of data transmission. Next, the Everestd subsystem transmits the encoded Android application data to the Everest_service subsystem in the OpenHarmony system through its internal preset client socket. In this step, the Everestd subsystem establishes a network connection with the Everest_service subsystem and sends the encoded data through the connection. The client socket serves as a channel for data transmission, ensuring accurate data transmission. Then, in the OpenHarmony system, the Everest_service subsystem receives the encoded Android application data from the Everestd subsystem through its internal preset socket. In this step, the Everest_service subsystem listens to the network connection from the Everestd subsystem and processes the data when it is received. Finally, the Everest_service subsystem decodes the received encoded Android application data. In this step, the Everest_service subsystem will apply the same decoding algorithm (such as decompression, decryption, etc.) as the Everestd subsystem to process the received data to restore the original Android application data. After the decoding is completed, the Everest_service subsystem can perform subsequent processing or installation on the Android application.

[0102] In this embodiment, Everestd subsystem and Everest_service subsystem act as a bridge for data transmission, and ensure the safe and efficient transmission of Android applications between different systems through encoding and decoding technology. This process not only improves the efficiency and security of data transmission, but also facilitates the distribution and deployment of cross-system applications.

[0103] In a feasible implementation manner, step S24 includes steps B10 to B30:

[0104] Step B10, detecting the life cycle of the Android application through the second Android compatible subsystem;

[0105] It should be noted that the life cycle refers to a series of state changes that an Android application goes through from startup to stop, including creation, startup, resumption, pause, stop, and destruction.

[0106] According to the information in the configuration file, the first Android compatible subsystem installs a shell application on the OpenHarmony system. This shell application provides a compatible operating environment for the Android application to be run. At the same time, on the Android system, the second Android compatible subsystem continuously monitors the life cycle status of the Android application. Whenever the state of the Android application changes (such as from a suspended state to a running state), the second Android compatible subsystem detects this change.

[0107] Step B20, if the life cycle is updated, the update of the life cycle is transmitted to the socket in the Everest_service subsystem through the client socket;

[0108] When an update is detected in the life cycle of an Android application, the second Android compatible subsystem will encapsulate the update information into a specific data packet and send it to the Everest_service subsystem in the OpenHarmony system through the client socket. This step involves the application of network communication protocols to ensure accurate data transmission.

[0109] Step B30: Synchronize the life cycle update to the shell application through the first Android compatible subsystem.

[0110] The Everest_service subsystem receives the lifecycle update data packet from the Android system through its internal socket. Then, it parses the data packet and extracts the lifecycle update information. Finally, the first Android compatible subsystem updates the status of the shell application based on the lifecycle update information received from the Everest_service subsystem. Furthermore, not only can the lifecycles of applications be synchronized according to the Everestd subsystem and the Everest_service subsystem during the installation process, but after the application is installed, the lifecycles of applications can also be synchronized and messages can be transmitted transparently. In this way, the shell application can maintain synchronized lifecycle status and messages with the Android application, thereby ensuring the stable operation of the Android application on the OpenHarmony system.

[0111] This embodiment embodies the close collaboration between the Android system and the OpenHarmony system, and ensures the compatibility and stability of Android applications on non-native Android systems through synchronized updates during the life cycle.

[0112] In a feasible implementation manner, step A10 includes steps C10 to C20:

[0113] Step C10, creating a socket in the Everest_service subsystem;

[0114] The Everest_service subsystem creates a socket in the operating system it runs on. This socket will act as a server-side socket, waiting for connection requests from the Everestd subsystem. The creation of a socket involves assigning a unique port number and setting related network parameters (such as IP address, protocol type, etc.).

[0115] Step C20, create a client socket in the Everestd subsystem, and use the client socket to establish a connection with the socket of the Everest_service subsystem.

[0116] The Everestd subsystem creates a client socket in the operating system it is running on. This socket will be used to initiate a connection request to the socket of the Everest_service subsystem. The creation process of the client socket is similar to that of the server socket, but usually there is no need to specify a port number (because the port number will be dynamically assigned by the operating system in the connection request). The Everestd subsystem sends a connection request to the server socket of the Everest_service subsystem through its client socket. This request contains information such as the IP address and port number of the Everest_service subsystem socket.

[0117] After receiving the connection request, the Everest_service subsystem verifies the validity of the request (for example, checking whether the IP address and port number match, and whether there are sufficient resources to handle the connection). If the verification is successful, the Everest_service subsystem accepts the connection request and establishes a network connection with the client socket of the Everestd subsystem. Once the connection is established, the Everestd subsystem and the Everest_service subsystem can send and receive data through their respective sockets. This network connection can be persistent (that is, until one party actively disconnects) or temporary (that is, it is used for one-time data transmission and then disconnected).

[0118] In this embodiment, the Everestd subsystem and the Everest_service subsystem implement cross-system data communication through a socket connection, providing a basis for subsequent operations such as application installation and life cycle synchronization.

[0119] It should be noted that, under the condition that the technology is feasible and the logic is clear, the above embodiments can be combined in pairs or in multiple combinations.

[0120] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the Android application packaging and installation method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0121] The present application provides an Android application packaging and installation device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the Android application packaging and installation method in the above-mentioned embodiment 1.

[0122] Reference below Figure 5 , which shows a schematic diagram of the structure of an Android application packaging and installation device suitable for implementing the embodiment of the present application. The Android application packaging and installation device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5The Android application packaging and installation device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0123] like Figure 5 As shown, the Android application packaging and installation device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the Android application packaging and installation device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the Android application packaging and installation device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows an Android application packaging and installation device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or have instead.

[0124] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0125] The Android application packaging and installation device provided by the present application adopts the Android application packaging and installation method in the above embodiment, and can realize the automatic packaging and uploading of Android applications, as well as the direct installation of Android applications by the OpenHarmony system. Compared with the prior art, the beneficial effects of the Android application packaging and installation device provided by the present application are the same as the beneficial effects of the Android application packaging and installation method provided by the above embodiment, and other technical features in the Android application packaging and installation device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0126] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0127] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0128] The present application provides a medium, which is a computer-readable storage medium having computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the Android application packaging and installation method in the above-mentioned embodiment.

[0129] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0130] The computer-readable storage medium may be included in the Android application packaging and installation device; or may exist independently without being assembled into the Android application packaging and installation device.

[0131] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the Android application packaging and installation device, the Android application packaging and installation device:

[0132] Get Android apps uploaded to the cloud;

[0133] Generate a shell application by parsing the Android application through the cloud;

[0134] Generate a configuration file according to the Android application and the shell application, and package the Android application, the shell application and the configuration file into an application package in a preset format;

[0135] The application package is published to the preset cloud through the cloud, wherein if the application installation terminal receives an installation request for installing the application package, the application package is downloaded from the cloud through the application market according to the installation request, and the first Android-compatible subsystem in the OpenHarmony system of the application installation terminal parses the application package to obtain the shell application, the Android application and the configuration file; the second Android-compatible subsystem in the Android system of the application installation terminal installs the Android application according to the configuration file; when the Android application is installed, the first Android-compatible subsystem installs the shell application according to the configuration file.

[0136] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0137] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0138] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0139] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned Android application packaging and installation method, and can realize automatic packaging and uploading of Android applications, as well as direct installation of Android applications by the OpenHarmony system. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the Android application packaging and installation method provided in the above-mentioned embodiment, and will not be repeated here.

[0140] The present application also provides a product, which is a computer program product, including a computer program, which implements the steps of the Android application packaging and installation method as described above when the computer program is executed by a processor.

[0141] The computer program product provided by this application can realize automatic packaging and uploading of Android applications, as well as direct installation of Android applications by the OpenHarmony system. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the Android application packaging and installation method provided by the above embodiment, and will not be repeated here.

[0142] The above are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. An Android application packaging and installation system, characterized in that: The Android application packaging and installation system includes a cloud and an application installation terminal that are communicatively connected to each other, the application installation terminal includes an Android system and an OpenHarmony system that are communicatively connected to each other, the OpenHarmony system includes a first Android compatible subsystem and an application market module, the Android system includes a second Android compatible subsystem, and the first Android compatible subsystem is communicatively connected to the second Android compatible subsystem; The cloud is used to obtain an externally uploaded Android application, parse the Android application, generate a shell application, generate a configuration file according to the Android application and the shell application, and package the Android application, the shell application and the configuration file into an application package in a preset format; The application market module is configured to download the application package from the cloud according to the installation request if an installation request for installing the application package is received; The first Android-compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the second Android-compatible subsystem; The second Android compatible subsystem is used to install the Android application according to the configuration file; The first Android compatible subsystem is used to install the shell application according to the configuration file after monitoring that the Android application is installed.

2. The Android application packaging and installation system according to claim 1, characterized in that: The Android system further includes an Everestd subsystem, and the OpenHarmony system further includes an Everest_service subsystem, and the Everestd subsystem is communicatively connected with the Everest_service subsystem; The Everest_service subsystem is used to create a socket; The Everestd subsystem is used to create a client socket and use the client socket to establish a connection with the socket of the Everest_service subsystem; The first Android compatible subsystem is used to parse the application package, obtain the shell application, the Android application and the configuration file, and send the Android application and the configuration file to the Everestd subsystem; The Everestd subsystem is used to receive the Android application and configuration file sent by the first Android compatible subsystem, encode the Android application and configuration file, and send the encoded Android application and configuration file to the Everest_service subsystem through the client socket; The Everest_service subsystem is used to receive the encoded Android application through the socket, decode the encoded Android application, obtain the Android application and the configuration file, and send the Android application and the configuration file to the second Android compatible subsystem; The second Android compatible subsystem is used to receive the Android application and configuration file of the Everest_service subsystem, and install the Android application according to the configuration file.

3. An Android application packaging and installation method, characterized in that: Applied to the cloud in the Android application packaging and installation system according to any one of claims 1 to 2, the Android application packaging and installation method comprises: Obtain an externally uploaded Android application, parse the Android application, and generate a shell application; A configuration file is generated based on the Android application and the shell application, and the Android application, the shell application and the configuration file are packaged into an application package in a preset format, wherein if the application installation terminal receives an installation request for installing the application package, the application package is downloaded from the cloud through the application market module in the application installation terminal according to the installation request, and the application package is parsed by a first Android-compatible subsystem in the OpenHarmony system of the application installation terminal to obtain the shell application, the Android application and the configuration file; the Android application is installed according to the configuration file through a second Android-compatible subsystem in the Android system of the application installation terminal; and when it is monitored that the installation of the Android application is complete, the shell application is installed according to the configuration file through the first Android-compatible subsystem.

4. An Android application packaging and installation method, characterized in that: Applied to an application installation terminal connected to the cloud in the Android application packaging and installation system according to any one of claims 1 to 2, the Android application packaging and installation method comprising: If an installation request for installing an application package is received, the application package is downloaded from the cloud according to the installation request, wherein the cloud obtains an externally uploaded Android application, parses the Android application, generates a shell application, generates a configuration file according to the Android application and the shell application, and packages the Android application, the shell application and the configuration file into the application package in a preset format; Calling the first Android compatible subsystem in the OpenHarmony system of the application installation terminal to parse the application package to obtain the shell application, the Android application and the configuration file; Calling a second Android compatible subsystem in the Android system of the application installation terminal to install the Android application according to the configuration file; When it is detected that the Android application is installed completely, the first Android compatible subsystem is called to install the shell application according to the configuration file.

5. The Android application packaging and installation method according to claim 4, characterized in that: Before the step of calling the second Android compatible subsystem in the Android system to install the Android application according to the configuration file, the following steps are included: Encode the Android application and configuration file through the Everestd subsystem in the Android system, and transmit the encoded Android application and configuration file to the Everest_service subsystem in the OpenHarmony system through the client socket preset in the Everestd subsystem; The encoded Android application and configuration file are received and decoded through a socket preset in the Everest_service subsystem to obtain the Android application and configuration file.

6. The Android application packaging and installation method according to claim 5, characterized in that: The step of calling the first Android compatible subsystem to install the shell application according to the configuration file includes: detecting the life cycle of the Android application by the second Android compatible subsystem; If the life cycle is updated, the update of the life cycle is transmitted to the socket in the Everest_service subsystem through the client socket; The update of the life cycle is synchronized to the shell application through the first Android compatible subsystem.

7. The Android application packaging and installation method according to claim 5, characterized in that: The step of transmitting the encoded Android application to the Everest_service subsystem in the OpenHarmony system through the client socket preset in the Everestd subsystem includes: Create the socket in the Everest_service subsystem; Create the client socket in the Everestd subsystem, and use the client socket to establish a connection with the socket of the Everest_service subsystem.

8. An Android application packaging and installation device, characterized in that: The Android application packaging and installation device comprises: the Android application packaging and installation system as described in claims 1 to 2, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the Android application packaging and installation method as described in any one of claims 3 to 7.

9. A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the Android application packaging and installation method as described in any one of claims 3 to 7.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the steps of the Android application packaging and installation method according to any one of claims 3 to 7 are implemented.

Images