Android application method and system based on web mobile operating system

Abstract

The application provides an Android application method and system based on a Web mobile operating system, relates to the technical field of mobile operating systems, and comprises the following steps: in the case that the Web mobile operating system and the Android system are simultaneously running, bridging a Web mobile operating system graphic display framework to a graphic display service, uniformly performing allocation and read-write management of a graphic cache area through the graphic display service, and realizing related functions such as application installation and uninstallation, application startup and system display switching between the Web system and the Android system through the establishment of an agent access service. The application can improve the application diversity of the Web system, thereby meeting the diversified use scene requirements of different users.

Description

Technical Field

[0001] This invention relates to the field of mobile operating system technology, specifically to the implementation of a method for compatible operation of Android applications in a Web mobile operating system, and more particularly to an Android application method and system based on a Web mobile operating system. Background Technology

[0002] Galaxy Ruihua Mobile Operating System is a web-based mobile operating system based on Linux + HTML5 technology. It supports a variety of domestically produced low-power chips and is compatible with Android drivers. Under the premise of meeting the requirements of autonomy, personalization, real-time performance and high security of domestic mobile operating systems, it provides domestic mobile operating system solutions for mobile terminal devices such as smart handhelds, tablets and wearables.

[0003] In recent years, with the continuous improvement of mobile hardware performance, smartphones and tablets have shifted from a single-system model to multi-system support to meet users' needs in different application scenarios. Currently, multi-system application support for smart mobile devices mainly falls into two categories. The first involves deploying multiple operating system images on different partitions of the hardware device. A customized system boot loader selects the corresponding system image and enters the desired operating system. However, this technology cannot meet the requirements for hot-switching of systems, resulting in long waiting times and impacting user experience. The second approach uses container technology to create multiple virtual containers through the Linux kernel. Each container runs its own system image independently, but the data between containers is independent, making it impossible to perform related business logic operations between two systems, and it consumes significant system resources. Currently, mobile terminals running Android applications on non-Android systems are mainly achieved through multi-system image booting or container technology running multiple systems in parallel.

[0004] The invention patent with publication number CN107102853B discloses a method for a customized mobile operating system to be compatible with Android applications, including the following steps: (1) extracting the underlying layer shared by the native applications of the customized mobile operating system and Android applications to form a unified hardware adaptation layer; (2) adding a basic library that supports the operation of Android applications to the basic class library of the customized mobile operating system; (3) adding an Android application runtime environment based on the customized mobile operating system runtime environment using Dalvik virtual machine technology, so that the customized mobile operating system contains two sets of application runtime environments; (4) adding an Android application framework to the application framework layer of the customized mobile operating system, and adapting the Android basic components at the same time, so that the two environments use a window manager. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides an Android application method and system based on a web mobile operating system.

[0006] According to the present invention, an Android application method and system based on a Web mobile operating system are provided, the solution of which is as follows:

[0007] In a first aspect, an Android application method based on a Web mobile operating system is provided. The method includes: when the Web mobile operating system and the Android system are running simultaneously, bridging the Web mobile operating system's graphics display framework to a graphics display service, and uniformly allocating and managing the graphics cache through the graphics display service.

[0008] It also establishes a proxy access service to enable functions such as application installation and uninstallation, application startup, and system display switching between the Web system and the Android system.

[0009] Preferably, establishing the proxy access service includes: starting the process as a background service process first, initializing the Web communication service, and constructing application proxy service and graphics management service objects; at the same time, when the Android system starts, the remote access service is initialized, relevant service object references including application management, package management, and window management are stored, and the remote access service proxy object is registered with the proxy access service to create its own remote access service proxy object.

[0010] Preferably, the proxy access service further includes:

[0011] When a web application makes Android system function calls, it first loads the web communication client dynamic library through the JS / C++ compatibility layer, and then uses Binder to call the proxy access service to remotely call functions and register callback functions.

[0012] After receiving the relevant function call request, the proxy access obtains the remote access service proxy object to notify the Android system to perform relevant business operations, including application installation, application startup, and application uninstallation.

[0013] After the business operation is completed, the proxy access service, based on the business execution result returned by the Android system, notifies the Web system client to perform the relevant callback function callback and calls the graphics management service to switch the layer display.

[0014] Preferably, the proxy access service includes application management proxy and graphical display control;

[0015] The web system initiates application installation requests to the Android application management service through the application management module of the proxy access service, and is responsible for starting and closing the corresponding Android application; the graphics display control module is responsible for switching the system display after listening to the start and exit status of the Android application.

[0016] Preferably, the application management agent specifically includes:

[0017] Application installation steps: When the Web system installs an Android application, it first sends an application installation request to Android through a proxy access service. Once the package management service completes the application package parsing and installation, it returns the application package name to the Web system. The Web system then requests the application name and application icon bitmap data from the Android side based on the returned package name. After obtaining the application name and icon image data, the Web template application package updates the application configuration manifest file and application icon, thereby generating a Web application package with the same application name as the Android system application. This package is then handed over to the Web system for installation, and an application launch icon is generated on the desktop.

[0018] Application startup steps: After the Android application package is installed, a virtual application is generated on the web system side. This virtual application is mainly responsible for sending a startup application request to the Android system and registering an application stack listener callback function for display switching. On the Android side, based on the received application package name, an off-screen application is launched via an Intent. After the application starts successfully, the window manager application stack obtains the class name of the top-level display application page of the current application, notifies the proxy service to update the application stack list, and calls back the web application stack listener callback function.

[0019] Application exit steps: When a user exits an application on the Android device, the original top-level application page in the window manager is removed or replaced. After receiving the updated application stack list information, the proxy service calls back the stack listener function registered by the Web virtual application. When the Web virtual application detects that the application name at the top of the current application stack does not match its own, it closes the current virtual application web page, returns to the main interface, and notifies the proxy graphics service to switch the screen display.

[0020] Preferably, the graphics display control specifically includes: using a unified graphics display service management system to drive the display device, the two system runtime spaces to create drawable layers through client access, and passing each created layer (stacklayer) to the graphics display control module for storage, so as to perform layer management and switching processing.

[0021] Preferably, the application startup step further includes: after the application stack listener callback function within the Web application is triggered, notifying the proxy service graphics management service to draw the Android application page graphics cache area onto the screen;

[0022] When the application is accessed again, the application stack list in the proxy service is traversed to check if a running application page already exists. If it does, the page class name is obtained to update the proxy application service stack list and the screen display is switched.

[0023] Secondly, an Android application system based on a web-based mobile operating system is provided, the system comprising:

[0024] When the Web mobile operating system and the Android system are running simultaneously, the Web mobile operating system's graphics display framework is bridged to the graphics display service, and the graphics display service is used to uniformly allocate and manage the graphics cache.

[0025] It also establishes a proxy access service to enable functions such as application installation and uninstallation, application startup, and system display switching between the Web system and the Android system.

[0026] Preferably, the establishment of the proxy access service includes: starting the process as a background service process first, initializing the Web communication service, and constructing application proxy service and graphics management service objects; at the same time, when the Android system starts, the remote access service is initialized, relevant service object references including application management, package management, and window management are stored, and the remote access service proxy object is registered with the proxy access service to create its own remote access service proxy object;

[0027] The proxy access service also includes:

[0028] When a web application makes Android system function calls, it first loads the web communication client dynamic library through the JS / C++ compatibility layer, and then uses Binder to call the proxy access service to remotely call functions and register callback functions.

[0029] After receiving the relevant function call request, the proxy access obtains the remote access service proxy object to notify the Android system to perform relevant business operations, including application installation, application startup, and application uninstallation.

[0030] After the business operation is completed, the proxy access service, based on the business execution result returned by the Android system, notifies the Web system client to perform the relevant callback function callback and calls the graphics management service to switch the layer display.

[0031] Preferably, the proxy access service includes an application management proxy module and a graphics display control module;

[0032] The web system initiates application installation requests to the Android application management service through the application management module of the proxy access service, and is responsible for starting and closing the corresponding Android application; the graphics display control module is responsible for switching the system display after listening to the start and exit status of the Android application.

[0033] The application management agent module specifically includes:

[0034] Application Installation Module: When the Web system installs an Android application, it first sends an application installation request to Android through a proxy access service. Once the package management service completes the application package parsing and installation, it returns the application package name to the Web system. The Web system then requests the application name and application icon bitmap data from the Android side based on the returned package name. After obtaining the application name and icon image data, it updates the application configuration manifest file and application icon in the Web template application package, thereby generating a Web application package with the same application name as the Android system application. This package is then handed over to the Web system for installation, and an application launch icon is generated on the desktop.

[0035] Application Launch Module: After the Android application package is installed, a virtual application is generated on the Web system. This virtual application is mainly responsible for sending a launch application request to the Android system and registering an application stack listener callback function for display switching. On the Android side, based on the received application package name, an off-screen application is launched via an Intent. After the application launches successfully, the window manager application stack obtains the class name of the top-level display application page of the current application, notifies the proxy service to update the application stack list, and calls back the Web application stack listener callback function.

[0036] When the application stack listener callback function within the web application is triggered, the proxy service graphics management service is notified to draw the Android application page graphics cache area onto the screen. When the application is entered again, the application stack list in the proxy service is traversed to check if a running application page already exists. If it already exists, its page class name is obtained to update the proxy application service stack list and the screen display is switched.

[0037] Application Exit Module: When a user exits an application on the Android device, the original top-level application page in the window manager is removed or replaced. After receiving the updated application stack list information, the proxy service calls back the stack listener function registered by the Web virtual application. When the Web virtual application detects that the application name at the top of the current application stack does not match its own, it closes the current virtual application web page, returns to the main interface, and notifies the proxy graphics service to switch the screen display.

[0038] The graphics display control module specifically includes: using a unified graphics display service to manage and control the display device driver; two system running spaces to create drawable layers through client access; and passing each created layer (stacklayer) to the graphics display control module for storage, so as to perform layer management and switching.

[0039] Compared with the prior art, the present invention has the following beneficial effects:

[0040] This invention enables the installation and compatible operation of Android applications under a Web system, and realizes the hot-switching function between Web applications and Android applications through a customized graphical management service, which can enrich the application diversity of the Web mobile operating system and improve the ease of use of the Web mobile system. Attached Figure Description

[0041] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:

[0042] Figure 1 This is a general block diagram of the technical solution;

[0043] Figure 2 Methods for implementing proxy access services;

[0044] Figure 3 Application installation flowchart;

[0045] Figure 4 Application startup flowchart;

[0046] Figure 5 Flowchart for application exit;

[0047] Figure 6 This is a schematic diagram of the control module. Detailed Implementation

[0048] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0049] This invention provides a method for applying Android applications based on a Web mobile operating system. When the Web mobile operating system and the Android system are running simultaneously, the Web mobile operating system's graphics display framework is bridged to a graphics display service. The graphics display service then centrally manages the allocation and read / write operations of the graphics cache. Furthermore, a proxy access service is established to enable functions such as application installation and uninstallation, application startup, and system display switching between the Web system and the Android system. (Refer to...) Figure 1 As shown, the proxy access service in this invention mainly consists of an application management module and a graphics display control module. The Web system initiates an application installation request to the Android application management service through the application management module of the proxy access service, and is responsible for starting and closing the corresponding Android application; the graphics display control module is responsible for switching the system display after listening to the start and exit status of the Android application.

[0050] (1) Proxy access service:

[0051] This application establishes a proxy to access a backend service as a remote function call function between a web system and an Android system. For example... Figure 2 As shown, the proxy access service starts first as a background service process, initializes the Web communication service, and constructs application proxy service and graphics management service objects. Simultaneously, when the Android system starts, it initializes the remote access service, stores references to service objects such as application management, package management, and window management, and registers its own remote access service proxy object with the proxy access service. When the Web application makes a function call to the Android system, it first loads the Web communication client dynamic library through the JS / C++ compatibility layer and uses Binder to remotely call and register callback functions with the proxy access service. After receiving the relevant function call request, the proxy access service obtains the remote access service proxy object to notify the Android system to perform business operations such as application installation, application startup, and application uninstallation. After the business operation is completed, the proxy access service, based on the business execution result returned by the Android system, notifies the Web system client to perform relevant callback function callbacks and calls the graphics management service to switch layer displays.

[0052] (2) Application Management Module:

[0053] Typically, application installation package information is fixed at the time of generation in a web system. In the method of this application, the application management agent module constructs a virtual application mechanism and uses a unified template web application creation and dynamic information update mechanism to realize the installation and management of various Android applications on the web system.

[0054] a) Application Installation

[0055] When the web system installs an Android application, it first sends an application installation request to Android via a proxy access service. Once the package management service completes the application package parsing and installation, it returns the application package name to the web system. The web system then requests the application name and application icon bitmap data from the Android client based on the returned package name. After obtaining the application name and icon image data, it updates the application configuration manifest file and application icon within the web template application package, thereby generating a web application package with the same name as the Android system application. This package is then handed over to the web system for installation, and an application launch icon is generated on the desktop. The main application installation flowchart is as follows: Figure 3 As shown.

[0056] b) Application Launch

[0057] In this application, after the Android application package is installed, a virtual application is generated on the Web system side. This application is mainly responsible for sending a request to start the application to the Android system and registering an application stack listener callback function for display switching. On the Android side, based on the received application package name, an off-screen application is launched via an Intent. After successful application launch, the window manager application stack obtains the class name of the current top-level display application page, notifies the proxy service to update the application stack list, and calls back the Web application stack listener callback function. When the application stack listener callback function within the Web application is triggered, it notifies the proxy service graphics management service to draw the Android application page graphics cache onto the screen. When the application is re-entered, the proxy service traverses the application stack list to check if a running application page already exists. If it does, the page class name is retrieved, the proxy application service stack list is updated, and the screen display is switched. The application launch flowchart is as follows: Figure 4 As shown.

[0058] c) Exit the application

[0059] When a user exits an application on an Android device, the top-level application page in the window manager is removed or replaced. Upon receiving the updated application stack list information, the proxy service calls back the stack listener function registered by the web virtual application. When the web virtual application detects that the application name at the top of the current application stack does not match its own, it closes the current virtual application's web page, returns to the main interface, and notifies the proxy graphics service to switch screen displays. The application startup flowchart is as follows: Figure 5 As shown.

[0060] (3) Graphics display control module:

[0061] like Figure 6As shown, this application uses a unified graphics display service to manage and control the display device driver. The two system runtimes create drawable layers via client access and pass the stack stack of each created layer to the graphics display control module for storage and layer management switching. By default, upon system startup, the Web system requests a drawable Surface layer from the graphics display service and registers this Surface's layStack value with the proxy service's graphics display control module. When a Web page starts, the various web pages are arranged and stacked before being passed to the Web graphics compositor to generate the final image buffer, which is then copied into the Surface layer created by the Web system. Similarly, when the Web system starts an Android application, it creates a Surface layer to store the Android application window display buffer and passes the layer stack of this layer to the graphics display control module for storage. When the proxy service receives Android application startup and exit events, it reads the lay stack value of the corresponding Surface based on the page to be launched and passes it along with the screen display device operation object to the graphics display service, notifying it to perform display switching and screen delivery processing, thereby achieving hot-switching between the Web application and the Android application.

[0062] The present invention will now be described in more detail.

[0063] Implementation example:

[0064] (I) Application Installation and Startup

[0065] The web application accesses the application management interface through a proxy call via a JS / C++ compatibility layer, enabling the installation, startup, and event listening of Android application packages. The pseudocode for the application management interface is shown below:

[0066] (1) Application installation interface

[0067] Interface description: Request the installation package for the Android application.

[0068] Parameter description: The parameter packagePath is the path to the Android application package, and the returned value is the name of the installed application package.

[0069] std::string application_agent_insallAPK(std::string packagePath)

[0070] (2) Application Uninstallation Interface

[0071] Interface Description: Uninstalls an Android application that is already installed on the web platform.

[0072] Parameter description: The parameter packageName is the name of the Android application package that has been installed on the web. The return value is the uninstallation result.

[0073] status_t application_agent_uninsall(std::string packageName);

[0074] (3) Get application icon interface

[0075] Interface Description: Retrieves the Android application icon from the web interface.

[0076] Parameter description: The parameter packageName is the Android application package name, icon is a pointer to the icon bitmap container, and the return value is the result of whether the retrieval was successful.

[0077] status_t application_agent_getIcon(std::string packageName,std::vector<uint8_t> *icon);

[0078] (4) Application startup interface

[0079] Interface Description: Launch an installed Android application from the web interface.

[0080] Parameter description: The parameter packageName is the name of the Android application package that has been installed on the web. The return value is the uninstallation result.

[0081] status_t application_agent_launchApp(std::string packageName);

[0082] (5) Application status monitoring interface

[0083] Interface Description: Register the Android client's list of running applications listener callback function

[0084] Parameter description: The parameter listener_callback is the registered application list listener callback function, where event is the callback event type, packageName is the package name of the Android application installed on the web, activityClassName is the application page function name to which the current callback event belongs, list is the application stack list data pointer, and the return value is the ID number of the listener created.

[0085] int32_t application_agent_addEventLinstener(

[0086] void*(listener_callback)(int event,std::string packageName,

[0087] std::string activityClassName,void*list)));

[0088] (II) Display Control

[0089] The system implements layer data registration and switching control operations by calling the graphics display control module. The pseudocode of the display control interface is shown below:

[0090] (1) Layer registration interface

[0091] Interface Description: Registers the created Surface layer information with the Graphics Control Manager.

[0092] Parameter description: The parameter content is the handle of the Surface layer to be created, layerStack is the layerStack value corresponding to the layer, and the return value is the execution result.

[0093] status_t display_agent_setSurface(int32_t content,int32_tlayerStack);

[0094] (2) Layer switching interface

[0095] Interface Description: Toggles the display of the Surface layer on the current screen.

[0096] Parameter description: The parameter content is the handle of the Surface layer to be created, and the return value is the execution result.

[0097] status_t display_agent_showSurface(int32_t content);

[0098] (3) Get the currently displayed layer

[0099] Interface Description: Get the handle of the currently displayed Surface.

[0100] Parameter description: The parameter content is a pointer to the Surface handle to be obtained, and the return value is the execution result.

[0101] status_t display_agent_getCurrentSurface(int32_t*content);

[0102] This invention provides an Android application method and system based on a Web mobile operating system. By modifying the Web system application package installation management and display framework process, it enables the installation of Android application packages and displays their icons on the Web system's main interface for easy launch. This provides strong support for the Web OS platform to implement Android application package installation and launch functions. It also enables compatible operation and hot-switching of Android system applications in the Web mobile operating system environment, improving the diversity of Web system applications and meeting the diverse usage scenarios of different users.

[0103] Those skilled in the art will understand that, besides implementing the system and its various devices, modules, and units provided by this invention in the form of purely computer-readable program code, the same functions can be achieved entirely through logical programming of the method steps, making the system and its various devices, modules, and units of this invention function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, the system and its various devices, modules, and units provided by this invention can be considered as a hardware component, and the devices, modules, and units included therein for implementing various functions can also be considered as structures within the hardware component; alternatively, the devices, modules, and units for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0104] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A method for Android application based on Web mobile operating system, characterized in that, The application relates to a method for realizing the bridging of a Web mobile operating system graphic display framework to a graphic display service and the uniform allocation and read-write management of a graphic buffer area in the case of the simultaneous running of the Web mobile operating system and an Android system. The method comprises the following steps: The method further comprises the following steps: The method further comprises the following steps: When a Web application calls an Android system function, a Web communication client dynamic library is loaded through a Js / C++ compatible layer, and a remote function call and a callback function registration are realized through Binder calling and implementing to the proxy access service; After the proxy access receives a related function call request, a remote access service proxy object is obtained to notify the Android system to perform related business operations such as application installation, application startup and application uninstallation; After the business operation is completed, the proxy access service notifies the Web system client to perform related callback function callback according to the business execution result returned by the Android system, and calls a graphic management service to perform layer display switching. The proxy access service comprises an application management proxy and a graphic display control; 2.The Android application method based on a Web mobile operating system according to claim 1, wherein, The Web system initiates an application installation request to the Android application management service through the application management module of the proxy access service, and is responsible for the startup and shutdown of the corresponding Android application; The graphic display control module is responsible for system switching display processing after listening to the Android application startup and exit state. The application management proxy comprises the following steps:

3. The method of claim 2, wherein the Android application is executed on the Web-based mobile operating system. An application installation step: when the Web system installs an Android application, an application installation request is first initiated to the Android through the proxy access service; when the package management service completes application package analysis and installation, the application package name is returned to the Web system; the Web system applies to the Android end to obtain the application name and application icon bitmap data according to the returned package name; after the application name and icon picture data are obtained, the application configuration list file and the application icon in the Web template application package are updated, so that the Web application package consistent with the Android system application name is generated, the Web system is transferred for installation, and an application startup icon is generated on the desktop; ​ The application starting step comprises the following steps: after the installation of the Android application package, a virtual application is generated on the Web system side, which is mainly responsible for sending an application starting request to the Android system and registering a callback function of the application stack for display switching processing; the Android side starts the application off-screen through Intent according to the received application package name, and the window manager application stack obtains the class name of the current application top display application page after the application is started successfully, and notifies the proxy service application stack list operation and calls back the Web application stack listening callback function; The application exit step comprises the following steps: when the user performs an application exit operation on the Android side, the original top application page in the window manager is removed or replaced, the proxy service receives the application stack list update information and calls back the Web virtual application registered stack listening function, and when the Web virtual application detects that the application name at the top of the application stack does not match itself, the current virtual application Web page is closed, the main interface is returned, and the proxy graphics service is notified to perform screen display switching.

4. The method of claim 3, wherein the Android application is executed on the Web-based mobile operating system. The graphic display control specifically comprises the following steps: display device driver control is performed through the use of unified graphic display service management, the two system running spaces are created through the client access method, the created layers are saved to the graphic display control module for layer management switching processing.

5. The method of claim 4, wherein the Android application is executed on the Web-based mobile operating system. The application starting step further comprises the following steps: after the Web application application stack listening callback function is triggered, the proxy service graphics management service is notified to draw the Android application page graphic buffer to the screen. When the application enters again, it is queried through the application stack list in the proxy service whether there is an existing running application page, if there is, the page class name is obtained for proxy application service stack list update, and screen display switching is performed.

6. A Web-based mobile operating system Android application system, characterized in that, The application starting step further comprises the following steps: after the Web application application stack listening callback function is triggered, the proxy service graphics management service is notified to draw the Android application page graphic buffer to the screen. When the application enters again, it is queried through the application stack list in the proxy service whether there is an existing running application page, if there is, the page class name is obtained for proxy application service stack list update, and screen display switching is performed. The application starting step further comprises the following steps: after the Web application application stack listening callback function is triggered, the proxy service graphics management service is notified to draw the Android application page graphic buffer to the screen. When the application enters again, it is queried through the application stack list in the proxy service whether there is an existing running application page, if there is, the page class name is obtained for proxy application service stack list update, and screen display switching is performed. The application starting step further comprises the following steps: after the Web application application stack listening callback function is triggered, the proxy service graphics management service is notified to draw the Android application page graphic buffer to the screen. When the application enters again, it is queried through the application stack list in the proxy service whether there is an existing running application page, if there is, the page class name is obtained for proxy application service stack list update, and screen display switching is performed. The application starting step further comprises the following steps: after the Web application application stack listening callback function is triggered, the proxy service graphics management service is notified to draw the Android application page graphic buffer to the screen. When the application enters again, it is queried through the application stack list in the proxy service whether there is an existing running application page, if there is, the page class name is obtained for proxy application service stack list update, and screen display switching is performed. The agent access receives a related function call request, acquires a remote access service agent object to notify the Android system to perform related business operations such as application installation, application startup and application uninstallation; After the business operation is completed, the agent access service notifies the Web system client to perform related callback function callback according to the business execution result returned by the Android system, and calls the graphic management service to perform layer display switching. 7.The Android application system based on a Web mobile operating system according to claim 6, characterized in that, The agent access service includes an application management agent module and a graphic display control module; The Web system initiates an application installation request to the Android application management service through the application management module of the agent access service, and is responsible for starting and closing the corresponding Android application; The graphic display control module is responsible for system switching display processing after listening to the Android application startup and exit state; The application management agent module specifically includes: An application installation module: when the Web system installs an Android application, the application installation module initiates an application installation request to the Android system through the agent access service, and returns the application package name to the Web system when the package management service completes application package analysis and installation; the Web system applies to the Android end for application name and application icon bitmap data according to the returned package name; after obtaining the application name and icon picture data, the Web system updates the application configuration list file and the application icon in the Web template application package, thereby generating a Web application package consistent with the Android system application name, and transfers the Web application package to the Web system for installation and generates an application startup icon on the desktop; An application startup module: after the installation of the Android application package is completed, a virtual application is generated on the Web system side, which is mainly responsible for sending a startup application request to the Android system and registering an application stack listening callback function for display switching processing; the Android end performs off-screen application startup through Intent according to the received application package name; after the application startup is successful, the window manager application stack obtains the class name of the current application top display application page, notifies the proxy service application stack list operation, and calls back the Web application stack listening callback function; After the Web application inside the application stack listening callback function is triggered, the proxy service graphic management service is notified to draw the Android application page graphic buffer to the screen; when the application enters again, whether there is a running application page exists is queried by traversing the application stack list in the proxy service; if there is an existing running application page, the page class name is obtained to update the proxy application service stack list, and screen display switching is performed; An application exit module: when the user performs an application exit operation on the Android end, the original top application page in the window manager is removed or replaced; after the proxy service receives the application stack list update information, the Web virtual application registers the stack listening function; when the Web virtual application detects that the current application stack top application name does not match itself, the current virtual application Web page is closed, the main interface is returned, and the proxy graphic service is notified to perform screen display switching. The graphic display control module specifically includes: display device driver control through the use of unified graphic display service management, two system running spaces through client access mode for drawable layer creation processing, and each created layer stack layer is transmitted to the graphic display control module for saving, for layer management switching processing.

Images