Multi-runtime container capable of integrating any application, and application management method

Abstract

The present invention relates to the technical fields of computers and mobile ends. Provided are a multi-runtime container capable of integrating any application, and an application management method. An overall service architecture uses a hierarchical model. A presentation layer is divided into web-end users and mobile-end users; a transmission layer uses a web server; an application layer provides a user service, an organization service, a permission service, a role service, a host application service, a light application service, a template service, a code packet service, a security detection service, a version service, a canary release service, a hot update service, a release / retirement service, an access policy service, a classification label service and a statistical analysis service; and a data layer includes a cache service and a data persistence service. Management users and subscribers of a service layer are divided into web-end users and mobile-end users, so as to also adapt to the development requirements of the current mobile-end electronic devices to a greater extent; and the design of a hierarchical structure enables a system to have higher flexibility, and enables flexible service-oriented division of layers and modules.

Description

A multi-runtime container capable of integrating any application and an application management method Technical Field

[0001] The present invention relates to the field of computer and mobile terminal technologies, and in particular to a multi-runtime container capable of integrating any application and an application management method. Background Art

[0002] In recent years, the rapid development of the mobile internet and the continuous increase in user base have made it increasingly competitive. Internet giants like WeChat, Baidu, Alipay, and Toutiao have matured in the development of "super apps" and "light apps." After years of development, these "super apps" have formed their own ecosystems, becoming new entry points that can precisely connect with the needs of hundreds of millions of mobile search users and expand their user base.

[0003] However, the "light apps" offered by these internet giants' "super apps" can only run within specific "super apps." For example, Baidu Light Apps, 360 Micro Apps, and WeChat Mini Programs can only run within their own apps and cannot be run in other apps. Furthermore, the ecosystems of these "super apps" each have distinct characteristics, primarily positioned based on the DNA of their own platforms, and do not cover all industry ecosystems. Summary of the Invention

[0004] Purpose of the invention: To propose a multi-runtime container and application management method that can integrate any application to solve the above-mentioned problems existing in the prior art.

[0005] First, a multi-runtime container that can integrate any application is proposed. The container includes four components: presentation layer, transport layer, application layer, and data layer.

[0006] The presentation layer includes the WEB side and the mobile side.

[0007] The transport layer includes a web server; the web server is used to transmit data between the presentation layer and the application layer.

[0008] The application layer provides user services, organizational services, permission services, role services, host application services, lightweight application services, template services, code package services, security testing services, version services, grayscale release services, hot update services, delisting and listing services, access policy services, classification label services, and statistical analysis services.

[0009] The data layer establishes communication with the application layer; the data layer provides cache services and data persistence services.

[0010] In a further embodiment of the first aspect, the mobile terminal provides a multi-runtime container SDK; the multi-runtime container SDK includes an H5 runtime container, a mini-program runtime container, and a native plug-in runtime container.

[0011] In a further embodiment of the first aspect, the H5 runtime container is extended based on WebView, and the resource files are downloaded to the APP in advance through hot update, so that the APP can directly read the resource files locally when loading the H5 application.

[0012] In a further embodiment of the first aspect, the mini-program runtime container provides a basic library of the runtime container that satisfies the dual-thread model and realizes the separation of the view layer and the logic layer.

[0013] In a further embodiment of the first aspect, the native plug-in runtime container adopts a ClassLoader-based plug-in approach and is implemented using a ClassLoader parent delegation model.

[0014] In a further embodiment of the first aspect, the native plug-in runtime container first uses the ClassLoader created by the Hook host application to deceive the system into completing component startup by occupying the pit replacement method, and then downloads the native APP plug-in package obtained in advance from the system to the APP through hot update. Then, through Java's reflection mechanism, it is replaced with a self-created PathClassLoader instance to realize dynamic loading of resource files.

[0015] In a further embodiment of the first aspect, when the native plug-in runtime container is running, the following process is performed:

[0016] First, you need to record the name of the Activity to be opened, which includes the application package name. Then, through a series of pre-defined processes, find an available slot and record it. Then, directly open this slot through the system's startActivity. Then, when the system calls the Hook's ClassLoader, intercept it, find the real Activity corresponding to this slot, and finally load and obtain the real Activity's Class object and return it to the system.

[0017] In a further embodiment of the first aspect, the mobile terminal regularly uploads data to the management platform by setting tracking points in the multi-runtime container SDK. The platform sets statistical indicators of the number of times the light application is opened, the opening time period and the opening duration, the number of times the light application is collected and the number of times the light application is uncollected, the basic information and network information of the device, and the template, classification, and label information of the light application to perform statistical analysis on the data to assist operators in making analysis and decisions.

[0018] In a second aspect, an application management method based on the multi-runtime container capable of integrating any application as described in the first aspect is proposed, comprising the following steps:

[0019] S1. The web user creates a host application through the host application management function and downloads the host application code framework that has integrated the SDK;

[0020] S2. Create a light application through the light application management function, and download the light application template code by selecting the category, tag, and template information maintained by the category management, tag management, and template management;

[0021] S3. Select the associated host application and the light application. After the user develops the light application, upload the developed code package through the code package management function and test the developed code package through the security detection function. The code package can only be packaged after passing the test;

[0022] S4. After packaging is completed, use the access policy management function to set the access policy and blacklist and whitelist of the light application, and use the grayscale release management function to set the grayscale release policy of the light application;

[0023] S5. Submit the version for review through the version management function. After passing the review, the light application can be put on the shelves through the shelf management function;

[0024] S6. The mobile terminal integrates the multi-runtime container SDK and first calls the light application authentication interface for authentication. After the authentication is passed, it calls the light application query interface to query the available light applications. Then, it downloads the updated light application through the hot update rule and calls the open light application interface to run the light application.

[0025] In a third aspect, an electronic device is proposed, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the application management method as described in the second aspect is implemented.

[0026] In a fourth aspect, a computer-readable storage medium is proposed, wherein the storage medium stores at least one executable instruction. When the executable instruction is executed on an electronic device, the electronic device executes the application management method as described in the second aspect.

[0027] Beneficial effects: The multi-runtime container SDK provided by this application can break down an APP into smaller parts, similar to microservices on the server side and micro-frontends on the WEB side, splitting business functions into several different types of "light applications" to achieve modular development and operation, so that each module runs in its own runtime container. The modules do not affect each other and can be updated and released independently, assembling business applications in a Lego-like manner, thereby improving APP development efficiency. This application provides templates for H5, mini-programs, and native plug-ins, as well as an SDK for runtime containers that can integrate any APP, so that these three types of light applications can run on any APP developed by oneself. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 is the business architecture diagram of the light application management platform.

[0029] Figure 2 is a diagram of the light application management model.

[0030] Figure 3 is a diagram of the multi-runtime container SDK architecture.

[0031] FIG4 is a schematic diagram of a monitoring statistical analysis model. DETAILED DESCRIPTION

[0032] In the following description, numerous specific details are provided to provide a more thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without one or more of these details. In other instances, certain technical features well known in the art have not been described to avoid confusion with the present invention.

[0033] This embodiment proposes a multi-runtime container that can integrate any application. In this era of terminal fragmentation, the APP is broken down into parts, similar to microservices on the server side and micro front-ends on the WEB side, and business functions are split into several "light applications" to achieve modular development and operation. Each module runs in its own runtime container. The modules do not affect each other and can be updated and released independently. Business applications are assembled in a way similar to Lego components, which ultimately gives enterprises the opportunity to build their own "super APP" and gradually form their own ecosystem and the industry ecosystem of the industry in which the enterprise is located.

[0034] The overall business architecture of the system described in the present invention adopts a layered model. The WEB end manages "super APP" and "light application", and the mobile end integrates multiple runtime containers to manage and control "light application". First, the present invention provides a "super APP" management function. When a new "super APP" is created, it will automatically generate an APP code framework with integrated multiple runtime containers. Combined with the publishing function of "light application", the published "light application" can be run in the "super APP"; Secondly, the interface provides help documentation for APP integration of multiple runtime containers, and supports the integration of multiple runtime containers into any APP managed by the present invention so that any APP can run the "light application" managed by the present invention. At the same time, the mobile end provides a multi-runtime container SDK, which can support the mobile end to run "light applications" such as H5, applets and native plug-ins. It has a unified entrance for users and does not focus on the technology and usage of specific applications.

[0035] Specifically, the multi-runtime container proposed in this invention, which can integrate any application, has the following features:

[0036] The overall business architecture adopts a layered model, in which the presentation layer is divided into WEB and mobile users, the transport layer uses a WEB server, the application layer provides user services, organizational services, permission services, role services, host application services, light application services, template services, code package services, security detection services, version services, grayscale release services, hot update services, delisting and listing services, access policy services, classification label services, and statistical analysis services. The data layer includes cache services and data persistence services. The management users and user users of the service layer are split into WEB and mobile terminals, which is more in line with the development needs of current mobile electronic devices. The layered structure design makes the system more flexible and enables flexible service-oriented splitting of each layer and module.

[0037] Light application management: It provides template management and light application management functions. Different types of "light applications" have their own templates, which allows users to create and download different types of "light applications" according to their needs. It provides code package management and security detection functions. Users upload developed code packages, and the system can perform security detection on the code packages. The code packages can be packaged only after passing the detection. It provides version management, access policy management, gray release management and delisting management functions. Users can submit the version of the packaged resource files for review. After the review is passed, they can be delisted and delisted. Users can also set access policies for "light applications", set access blacklists and whitelists, and set gray release policies for "light applications". Finally, the mobile terminal downloads the "light application" after it is put on the shelf and runs it according to the hot update rules.

[0038] The multi-runtime container SDK includes the H5 runtime container, the mini-program runtime container, and the native plug-in runtime container. The H5 runtime container is an extension of WebView. In order to improve the loading efficiency of the H5 application, the resource files are downloaded to the APP in advance through hot updates, so that the APP can directly read the resource files from the local when loading the H5 application, avoiding a large number of network resource requests, thereby eliminating the overhead of loading resources through the network. The mini-program runtime container complies with the requirements of the mini-program white paper and provides a basic library for runtime containers that meet the dual-thread model and realize the separation of the view layer and the logic layer, providing mini-programs with rich interface and functional support. The native plug-in runtime container is a plug-in based on ClassLoader. The Hook system creates a ClassLoader for the APP, and then replaces it with a self-created PathClassLoader instance through Java reflection to achieve dynamic loading of resource files.

[0039] Monitoring data collection and statistical analysis: By setting tracking points in the multi-runtime container SDK, data is regularly uploaded to the management platform. The platform sets statistical indicators for the number of times light applications are opened, the opening time period and the opening duration, the number of times light applications are collected and the number of times they are uncollected, the basic information of the device and the network information, etc., and cooperates with the template, classification and label information of the light application to conduct statistical analysis of the data, assist operators in analytical decision-making, and continuously improve the templates, classifications and labels of the management platform, and eventually gradually establish the company's own ecosystem and the industry ecosystem of the industry in which the company is located.

[0040] The specific implementation of the present invention is described in detail below with reference to specific embodiments.

[0041] Example 1:

[0042] As shown in Figure 1, the light application management platform adopts a layered model for its overall business architecture, in which the presentation layer is divided into WEB and mobile users, the transport layer adopts a WEB server, the application layer provides user services, organizational services, permission services, role services, host application services, light application services, template services, code package services, security detection services, version services, grayscale release services, hot update services, delisting services, access policy services, classification label services, and statistical analysis services. The data layer includes cache services and data persistence services; the service layer splits the management users and the use users into WEB and mobile terminals, and is more adapted to the development needs of current mobile electronic devices. The layered structure design makes the system more flexible. It not only performs flexible service splitting at various levels and modules, but more importantly, it can provide some basic support services for other related areas of the software, facilitating the rapid integration and expansion of other systems. For example, the user services, organizational services, permission services, role services, etc. of the application layer can be reused in other related fields.

[0043] The light application management platform system provided by the present invention is not only aimed at the model of a super APP, but also supports multi-tenant model splitting, so that the system can support multiple super APPs, so that all APPs on the system can open the light applications on this system through the integrated SDK.

[0044] Example 2:

[0045] The light application management model shown in Figure 2 provides the entire light application management process. First, the WEB user creates a host application through the host application management function and downloads the host application code framework with the SDK integrated. Then, the light application is created through the light application management function, and the light application template code is downloaded by selecting the category, label and template information maintained by the category management, label management and template management. Then, the user chooses to associate the host application and the light application. After the user develops the light application, he can upload the developed code package through the code package management function and test the developed code package through the security detection function. The code package can be packaged only after the detection passes. After the packaging is completed, the access policy management function is used to set the access policy and blacklist and whitelist of the light application, and the grayscale release management function is used to set the grayscale release policy of the light application. Then, the version is submitted for review through the version management function. After the review passes, the light application is put on the shelf through the delisting and listing management function. Finally, the mobile end integrates the multi-runtime container SDK, first calls the light application authentication interface for authentication, and after the authentication passes, calls the light application query interface to query the available light applications, and then downloads the updated light application after the hot update rule, and calls the open light application interface to run the light application.

[0046] Example 3:

[0047] As shown in Figure 3, the multi-runtime container SDK primarily includes three types of runtime containers: HTML5, mini-programs, and native plug-ins. The HTML5 container is a fundamental solution for hybrid mobile development. Its primary function is to load HTML5 pages, manage two-way communication between HTML5 and native applications, and encapsulate native system functionality for H5 access, such as photo gallery, camera, and Bluetooth. With the increasingly close integration between mobile and front-end platforms, HTML5 pages, with their low R&D costs and flexible publishing capabilities, are gaining popularity, enabling them to handle a growing number of applications on the app side. However, the most obvious drawback of HTML5 pages is that they open significantly slower than native applications, resulting in a poor user experience. To improve the loading efficiency of HTML5 applications and shorten the loading process, the HTML5 container presented in this article extends WebView. To improve the loading efficiency of HTML5 applications, resource files are pre-downloaded to the app via a hot update mechanism. This allows the app to directly access resource files locally when loading the HTML5 application, avoiding numerous network resource requests and eliminating the overhead associated with loading resources over the network. The mini-program runtime container is a hybrid solution that relies on web technologies (particularly CSS and JavaScript) and integrates with native application functionality. It is a specialized container capable of running mini-program applications, decoupling them from the underlying system, thereby improving their stability and compatibility. The mini-program runtime container presented in this article complies with the requirements of the mini-program white paper and provides a foundational library that implements a dual-threaded model to separate the view and logic layers. The view layer is responsible for rendering the mini-program page, including displaying web components and native components. The logic layer uses JavaScript to handle mini-program events, API calls, and lifecycle management. Furthermore, the mini-program container provides a rich set of native component and plugin call capabilities, providing rich interface and functional support for mini-program applications. The native plug-in runtime container offers a plug-in-based solution based on a ClassLoader and leveraging the ClassLoader parent delegation model. It first hooks the ClassLoader created by the host application, tricking the system into completing component startup through a plug-in replacement scheme. It then uses a hot update to download the native app plug-in package from the system and then replaces it with a self-created PathClassLoader instance, enabling dynamic resource file loading.This is achieved primarily through the following steps: First, the name of the Activity to be opened, including the application package name, is recorded. A predefined series of processes is then used to find an available slot and record it. The slot is then opened directly through the system's startActivity method. When the system calls the Hook's ClassLoader, it is intercepted to find the actual Activity corresponding to this slot. Finally, the Class object of the actual Activity is loaded and retrieved and returned to the system. Finally, the multi-runtime container SDK integration eliminates the differences between different light apps, encapsulating a unified light app component and management processing engine. This allows for unified authentication, querying, and management of light apps, while providing specific and unique processing for the differences between light apps.

[0048] Example 4:

[0049] As shown in the monitoring statistical analysis model in Figure 4, mobile users set tracking points in the multi-runtime container SDK to upload the number of times light applications are opened, the time period during which light applications are opened, the duration of light application openings, the number of times light applications are collected, the number of times light applications are uncollected, and the basic information and network information of the device used to the light application management platform. WEB users create light applications through the information of light application classification management, light application tag management, and template management, and record the classification, tag, and template information used. After that, data statistical analysis is performed through the indicator model set up in the system backend to assist operators in analytical decision-making, and continuously optimize and improve the information of light application classification management, light application tag management, and template management, and eventually gradually establish the company's own ecosystem and the industry ecology of the industry in which the company is located.

[0050] In summary, the multi-runtime container SDK provided by this application can break down an APP into parts, similar to microservices on the server side and micro-frontends on the WEB side, splitting business functions into several different types of "light applications" to achieve modular development and operation, so that each module runs in its own runtime container. The modules do not affect each other and can be updated and released independently, assembling business applications in a Lego-like manner, thereby improving the development efficiency of the APP. This application provides templates for H5, mini-programs, and native plug-ins, as well as an SDK for runtime containers that can integrate any APP, so that these three types of light applications can run on any APP developed by themselves.

[0051] Embodiment 5:

[0052] This embodiment proposes a computer-readable storage medium, in which at least one executable instruction is stored. When the executable instruction is executed on an electronic device, the electronic device performs the operation of the application management method described in the above embodiment 2. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it can be various devices including one or any combination of the above memories. The computer can be various computing devices including smart terminals and servers. The executable instruction can be in the form of a program, software, software module, script or code, written in any form of programming language (including compiled or interpreted language, or declarative or procedural language), and it can be deployed in any form, including being deployed as an independent program or being deployed as a module, component, subroutine or other unit suitable for use in a computing environment.

[0053] By way of example, executable instructions may, but need not necessarily, correspond to a file in a file system, may be stored as part of a file storing other programs or data, such as in one or more scripts in a Hypertext Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple coordinating files (e.g., files storing one or more modules, subroutines, or code portions). Executable instructions may be deployed for execution on one computing device, on multiple computing devices located at one site, or on multiple computing devices distributed across multiple sites and interconnected by a communication network.

[0054] As described above, although the present invention has been shown and described with reference to specific preferred embodiments, it should not be construed as limiting the present invention itself. Various changes may be made to it in form and detail without departing from the spirit and scope of the present invention as defined in the appended claims.

Claims

1. A multi-runtime container that can integrate any application, characterized in that: include: Display layer, including WEB and mobile terminals; The transport layer includes a web server; the web server is used to transmit data between the presentation layer and the application layer; Application layer; The application layer provides user services, organizational services, permission services, role services, host application services, light application services, template services, code package services, security detection services, version services, grayscale release services, hot update services, on-shelf and off-shelf services, access policy services, classification label services, and statistical analysis services; The data layer establishes communication with the application layer; the data layer provides cache services and data persistence services.

2. The multi-runtime container capable of integrating any application according to claim 1, characterized in that: The mobile terminal provides a multi-runtime container SDK; the multi-runtime container SDK includes an H5 runtime container, a mini-program runtime container, and a native plug-in runtime container.

3. The multi-runtime container capable of integrating any application according to claim 2, characterized in that: The H5 runtime container is extended based on WebView, and the resource files are downloaded to the APP in advance by hot update, so that the APP can directly read the resource files from the local when loading the H5 application.

4. The multi-runtime container capable of integrating any application according to claim 2, characterized in that: The mini-program runtime container provides a basic library of the runtime container that meets the dual-thread model and realizes the separation of the view layer and the logic layer.

5. The multi-runtime container capable of integrating any application according to claim 2, characterized in that: The native plug-in runtime container adopts a ClassLoader-based plug-in approach and is implemented using the ClassLoader parent delegation model; The native plug-in runtime container first hooks the ClassLoader created by the host application, deceives the system to complete component startup by occupying the pit replacement method, and then downloads the native APP plug-in package obtained in advance from the system to the APP through hot update. Then, through Java's reflection mechanism, it is replaced with a self-created PathClassLoader instance to realize dynamic resource file loading.

6. The multi-runtime container capable of integrating any application according to claim 5, characterized in that: When the native plug-in runtime container is running, the following process is executed: First, you need to record the name of the Activity to be opened, which includes the application package name. Then, through a series of pre-defined processes, find an available slot and record it. Then, open this slot directly through the system's startActivity. Then, when the system calls the Hook's ClassLoader, intercept it, find the real Activity corresponding to this slot, and finally load and obtain the real Activity's Class object and return it to the system.

7. The multi-runtime container capable of integrating any application according to claim 1, characterized in that: The mobile terminal sets tracking points in the multi-runtime container SDK and regularly uploads data to the management platform. The platform sets statistical indicators of the number of times the light application is opened, the opening time period and the opening duration, the number of times the light application is collected and the number of times the light application is uncollected, the basic information of the device and the network information, and cooperates with the template, classification and label information of the light application to perform statistical analysis on the data to assist operators in making analysis and decisions.

8. The application management method based on the multi-runtime container capable of integrating any application program according to any one of claims 1 to 7, characterized in that: The steps include: S1. The WEB user creates a host application through the host application management function and downloads the host application code framework that has integrated the SDK; S2. Create a light application through the light application management function, and download the light application template code by selecting the category, label and template information maintained by the category management, label management and template management; S3. Select to associate the host application and the light application. After the user develops the light application, upload the developed code package through the code package management function, and test the developed code package through the security detection function. The code package can be packaged only after passing the detection; S4. After packaging is completed, use the access policy management function to set the access policy and blacklist and whitelist of the light application, and use the grayscale release management function to set the grayscale release policy of the light application; S5. Submit the version for review through the version management function. After the review is passed, the light application is put on the shelves through the on-shelf and off-shelf management function; S6. The mobile terminal integrates the multi-runtime container SDK, first calls the light application authentication interface for authentication, and then calls the light application query interface to query the available light applications after the authentication is passed. Then, the light application that has been updated and put on the shelf is downloaded through the hot update rules, and the light application opening interface is called to run the light application.

9. An electronic device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the application management method according to claim 8 is implemented.

10. A computer-readable storage medium, characterized in that: The storage medium stores at least one executable instruction, and when the executable instruction is executed on the electronic device, the electronic device executes the application management method as claimed in claim 8.

Images