CN111796909A - Lightweight mobile application virtualization system - Google Patents
Lightweight mobile application virtualization system Download PDFInfo
- Publication number
- CN111796909A CN111796909A CN202010588083.6A CN202010588083A CN111796909A CN 111796909 A CN111796909 A CN 111796909A CN 202010588083 A CN202010588083 A CN 202010588083A CN 111796909 A CN111796909 A CN 111796909A
- Authority
- CN
- China
- Prior art keywords
- container
- application
- request
- service
- creating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 120
- 230000008569 process Effects 0.000 claims abstract description 114
- 230000000694 effects Effects 0.000 claims description 36
- 238000009434 installation Methods 0.000 claims description 12
- 239000011230 binding agent Substances 0.000 claims description 9
- 238000013507 mapping Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 238000004891 communication Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 102100038612 Calmodulin-regulated spectrin-associated protein 3 Human genes 0.000 description 1
- 101000741294 Homo sapiens Calmodulin-regulated spectrin-associated protein 3 Proteins 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000036316 preload Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45516—Runtime code conversion or optimisation
- G06F9/45525—Optimisation or modification within the same instruction set architecture, e.g. HP Dynamo
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a lightweight mobile application virtualization system which comprises a container starting auxiliary process and an AMS (automatic management system) process which are arranged in an Android system and are used for managing a container root process of a container; the container starts an auxiliary process to construct an Intent data packet, and creates and sends a request for creating a virtualized application to the AMS process according to the Intent data packet; the AMS process receives a request for creating a virtualized application, analyzes the received Intent data packet, and sends a request for creating a container process to the container root process according to the Intent data packet; and the container root process creates and initializes an application running environment, creates a container process after receiving a container process creation request, obtains package information of the container application from the AMS process according to the sent container application loading request, and starts the container application. To reduce the system resources that need to be occupied by application virtualization.
Description
Technical Field
The invention belongs to the technical field of virtualization, and particularly relates to a lightweight mobile application virtualization system.
Background
The advent and popularity of mobile smart devices has created a number of problems and challenges. The huge demand of the mobile application market guides the development threshold of the mobile application to be reduced, and in addition to the imperfect authority mechanism and security model of the intelligent device operating system, the mobile operating system becomes the most attractive target of the current virus software. Meanwhile, the dependence of the user on the mobile application is deepened, and a plurality of terminal devices are required to play different user roles to meet different application scene requirements, so that the personal privacy and the data security of the user are protected.
The virtualization technology has the characteristics of improving the application safety and meeting the requirement of solving the multi-scenario role, and the combination of the virtualization technology and the mobile operating system is an important direction of the current solution. Different from the application virtualization of the traditional operating system, the android operating system can be operated after the initialization of the kernel of the android device is completed, and a large amount of system services are operated in the android system for a user mode process to access system resources. Apps in the application marketplace need to be installed, loaded, and run in the android system framework, controlled and managed by the android system. In the existing solutions, a complete android operating system is operated in a virtual machine or a container through system-level virtualization, such as Cells, android, Nezha, and Gemini, so as to provide resource access services for user applications, and then target applications are operated in a virtualized operating system environment, which greatly increases the response time and resource consumption of application virtualization, and is not suitable for intelligent device terminals with limited resources.
Application publication No. CN106572014A discloses a virtualization network system, and application publication No. CN103207762A discloses a storage virtualization system, both of which are not suitable for the Android system.
Disclosure of Invention
The invention aims to provide a lightweight mobile application virtualization system so as to reduce system resources occupied by application virtualization and improve the usability of application virtualization on intelligent mobile equipment.
In order to achieve the purpose, the invention provides the following technical scheme:
a lightweight mobile application virtualization system comprises a container starting auxiliary process and an Activity Manager Service (AMS) process which are arranged in an Android system, and further comprises a container root process for managing containers;
the container starts an auxiliary process to construct an Intent data packet, and creates and sends a request for creating a virtualized application to the Activity Manager Service process according to the Intent data packet;
the Activity Manager Service process receives a request for creating a virtualized application, analyzes a received Intent data packet, and sends a request for creating a container process to a container root process according to the Intent data packet; sending package information of the container application to the container root process according to the received request for loading the container application;
the container root process creates and initializes an application running environment, creates a container process after receiving a request for creating the container process, and the container process obtains package information of the container application from the Activity Manager Service process according to the sent request for loading the container application and starts the container application.
When the Intent data packet is constructed, a FLAG _ ACTIVITY _ contact identifier for identifying the virtualized application which is requested to be started is added to the Intent data packet.
Preferably, before sending the request for starting and creating the container application, the container starting auxiliary process further performs application check, initiates a target component query request to the Package Manager Service, checks whether the target component to be started is installed, if the target component is not installed, initiates a target component installation request to the Package Manager Service, and installs the target application according to an installation Package address of the target application, which is transmitted by the target component installation request.
Preferably, after the Activity Manager Service analyzes the Intent data packet, whether a target application is installed in the current Android system is checked according to the packet name and the UID of the target application recorded in the Intent data, if the installation record exists, whether an application process of the target application exists is searched and judged, and if the application process does not exist, a new record is created according to the packet name and the UID of the target application for storing information of the application;
checking whether the Intent data contains a FLAG _ ACTIVITY _ CONTAINER FLAG, and sending a CONTAINER process creation request to the CONTAINER root process through a CONTAINER socket when the FLAG _ ACTIVITY _ CONTAINER FLAG is contained.
Preferably, the container root process creating and initializing the application execution environment includes:
creating a Java virtual machine, registering a jni function, loading a ZygoteInit class in the jni function and preloading Java classes and Android resources.
Preferably, the create container process comprises:
abi for checking uid, gid, gids, capabilities security authority and application program in the request for creating the container process, checking that a corresponding sub-process is created by calling a fork system after passing, and loading ActivityThread to initialize the container application;
the ActivityThread sets a system path required to be used in the application in an initialization process, sets a certificate storage position of the current application, sets a process name and creates a Binder thread pool for processing Binder communication of Android system services.
Preferably, after receiving the request for loading the container application, the activityManagerService searches the package information of the container application according to the uid of the sender of the Binder request, and transmits the package information to the container process;
and the container process loads and starts the target container application after receiving the packet information of the target container application.
In order to realize the application virtualization instance, the container root process sets a container identifier as a container application instance ID for each container, wherein the container identifier maps the matching relationship between the container application instance and the corresponding application process record;
through the container identifier and the application program ID, when the container identifier and the application program ID cannot be matched with the existing container identifier and application program ID, a new container process and a new Activity Stack are created for the container application, and the same-application multi-virtualization instance is realized.
Preferably, the container root process further creates an allowed access authority list for each container, and sets a name Namespace ID for each allowed access authority list;
when the container application needs to access the system service of the Android system through the service manager service of the Android system, the service manager service opens the corresponding system service to the container application according to the access service contained in the access permission list corresponding to the Namespace ID.
Compared with the prior art, the invention has the beneficial effects that:
the lightweight mobile application virtualization system provided by the invention realizes application-level virtualization by using a container technology under an android operating system environment, and one application can have a plurality of virtualization instances and simultaneously control the access limit of the virtualization application to system services. The system resources occupied by application virtualization are reduced, the usability of the application virtualization on the intelligent mobile device is improved, and great support is provided for improving the application safety and solving the multi-scenario role requirement.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a framework diagram of a lightweight mobile application virtualization system provided by an embodiment;
FIG. 2 is an exemplary diagram of an application virtualization multi-instance provided by an embodiment;
fig. 3 is a flow chart of system service access control provided by an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the detailed description and specific examples, while indicating the scope of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
In order to realize application-level virtualization in an android operating system environment, one application may have multiple virtualization instances to control access restrictions of virtualized applications to system services. As shown in fig. 1, the lightweight mobile application virtualization system includes a container startup auxiliary process container and an Activity Manager Service process, which are provided in an Android system, and a container root process container-init for managing a container. The contianertool sends a request for creating a virtualized application to an android system service ActivityManagerService process, and the contianer-init process initializes an application running environment and creates a process and loads a target application after receiving an ActivityManagerService starting application request. The operation flow of the whole system is shown in fig. 1.
The container starting auxiliary process containertool is arranged in an Android system host, and mainly realizes the functions of constructing Intent, checking applications and sending a request for creating virtualized applications to ActivityManagerservice.
Aiming at the construction of an Intent flow, a contenantertool constructs an Intent data packet according to a user identifier of an initiator and a target application component name, the Intent data packet is a data packet used by an android system for data transmission, and a FLAG _ ACTIVITY _ content identifier is added to the Intent data packet and used for identifying whether the initiation request is a normal application or a virtualized application.
Before sending a request for starting and creating the container application, the container starting auxiliary process also carries out application check, initiates a target component query request to the Package Manager Service, checks whether the target component to be started is installed, if the target component is not installed, initiates a target component installation request to the Package Manager Service, and installs the target application according to an installation Package address of the target application transmitted by the target component installation request.
After the application check is finished, the container starts a request for creating the virtualized application initiated by the auxiliary process to the activityManagerservice, transmits the previously created Intent data packet, and requests the android system on the host machine to create the virtualized application.
The ActivityManagerService process is a service process carried by the android system, the ActivityManagerService process is subjected to function modification, and the ActivityManagerService process is mainly used for processing a request for creating a virtualized application.
After receiving the request for creating the virtualized application, the ActivityManagerService process analyzes an Intent data packet contained in the request for creating the virtualized application, checks whether a target application is installed in the current Android system according to the packet name and UID of the target application recorded in Intent data, if the installation record exists, searches and judges whether the application process of the target application exists, and if the application process does not exist, creates a new record according to the packet name and UID of the target application for storing the information of the application;
checking whether the Intent data contains a FLAG _ ACTIVITY _ CONTAINER FLAG, and sending a CONTAINER process creation request to the CONTAINER root process through a CONTAINER socket when the FLAG _ ACTIVITY _ CONTAINER FLAG is contained.
The container root process container-init is a core for implementing a virtualized application, and is mainly used to create and initialize an application running environment, create a container process, and start a container application, and each part is described in detail below.
In the process of creating and initializing the application running environment, the container root process container-init mainly creates a Java virtual machine, registers a jni function, loads Zygoteinit class in the jni function and pre-loads Java class and Android resources.
The method comprises the steps that a container root process creates a container process after receiving a container process creation request, specifically, abi of uid, gid, gids, capabilities security authority and an application program in the container process creation request is checked, and a corresponding sub-process is created through later calling a fork system call and ActivityThread is loaded to initialize a container application;
the ActivityThread sets a system path required to be used in the application in an initialization process, sets a certificate storage position of the current application, sets a process name and creates a Binder thread pool for processing Binder communication of Android system services.
After receiving the container application loading request, the ActivityManagerservice searches the package information of the container application according to the uid of the sender of the Binder request and transmits the package information to the container process; and the container process loads and starts the target container application after receiving the package information of the target container application.
When the target application started by the container is not started in the host or other containers, the Activity manager service can create a new container process and Activity Stack for the target application because the application process record and the Activity Stack matched with the target application can not be found, so as to start and store the Activity of the target application. When the host or other container starts the target application with the same name, the Activity manager service does not create the corresponding container process and Activity Stack because the record ID exists, which results in the failure of starting the container process.
When the target application started by the container is not started in the host or other containers, because the Activity record can not be found in the Activity record and the Activity Stack matched with the target application record, the Activity manager service can create a new container process and Activity Stack for the target application record to start and store the Activity of the target application. When a host or other container starts multiple existing virtualized instances of the application, the Activity manager service does not create a corresponding container process and Activity Stack due to the existence of the record ID, which results in failure of starting the application virtualization.
FIG. 2 depicts an application virtualization multi-instance solution where the container root process sets a container identifier for each container as a container application instance ID, the container identifier mapping the matching relationship of the container application instance to the corresponding application process record;
in the embodiment, the IPC Namespace ID of the container is used as the identifier of the user ID, different containers have different IPC Namespace IDs, and application records of different containers are isolated from each other due to different identifiers of the user ID. When the ActivityManagerService searches records according to the UID + APPId as an index, only an application record list corresponding to the current container is searched, and when similar applications are started, because the UID + APPId cannot be matched, a new container process and a new Activity Stack can be created for the application container, so that a multi-virtualization instance with the same application is realized.
The android application virtualization instance and the user on the host machine share the android system service on the host machine, the application instance acquires the corresponding service address through the service manager service, and then the corresponding system resource can be acquired through the system service, so that the risk of data leakage on the host machine is increased, such as sensor data of equipment, network information and the like.
As shown in fig. 3, the lightweight mobile application virtualization system performs access authority control on the access authority of the system service of the android application virtualization instance. Specifically, the container root process also creates an allowed access authority list for each container, and sets a name Namespace ID for each allowed access authority list; when the container application needs to access the system service of the Android system through the service manager service of the Android system, the service manager service opens the corresponding system service to the container application according to the access service contained in the access permission list corresponding to the Namespace ID.
When a user application wants to acquire a service, the user application needs to send a service query request to a service manager, the service manager calls a do _ find _ service method after receiving the request, and a service address is queried according to a service name sent by a requester. And if the corresponding service address exists, checking whether the service requester meets the SELinux service access authority, and if so, returning the service address to the Binderleent. When creating an application container, we write the system service name that we allow the container to access into the configuration file. When the container runs, the name of the container, the IPCNamespace ID of the container and the system service which the container allows to access are mapped by analyzing the application container. When the virtualized application instance wants to acquire service, the IPC Namespace of the current process is sent to servicemanager through current- > nsproxy- > IPC _ ns. After receiving the service query request and checking that the SELinux service access authority of the request sender is satisfied, the servicemanager checks whether the current request caller can acquire the requested service name or not through mapping from the Namespace ID to the system service, and if the service name does not pass the mapping, the servicemanager refuses to acquire the system resource.
Compared with the existing system level virtualization, the lightweight mobile application virtualization system provided by the embodiment has the advantages that the consumption of system resources such as response time, memory occupation and disk occupation of application virtualization is reduced by sharing android system services through a plurality of application instances. Meanwhile, the android system source code is modified by the technology of the lightweight mobile application virtualization system, so that the transportability of the scheme is enhanced, and the method can be adapted to android systems customized by different versions and different manufacturers.
The above-mentioned embodiments are intended to illustrate the technical solutions and advantages of the present invention, and it should be understood that the above-mentioned embodiments are only the most preferred embodiments of the present invention, and are not intended to limit the present invention, and any modifications, additions, equivalents, etc. made within the scope of the principles of the present invention should be included in the scope of the present invention.
Claims (9)
1. A lightweight mobile application virtualization system is characterized by comprising a container starting auxiliary process and an Activity Manager Service process which are arranged in an Android system, and a container root process for managing containers;
the container starts an auxiliary process to construct an Intent data packet, and creates and sends a request for creating a virtualized application to the Activity Manager Service process according to the Intent data packet;
the Activity Manager Service process receives a request for creating a virtualized application, analyzes the received Intent data packet, and sends a request for creating a container process to a container root process according to the Intent data packet; sending package information of the container application to the container root process according to the received request for loading the container application;
the container root process creates and initializes an application running environment, creates a container process after receiving a request for creating the container process, and the container process obtains package information of the container application from the Activity Manager Service process according to the sent request for loading the container application and starts the container application.
2. The lightweight mobile application virtualization system of claim 1 wherein a FLAG _ ACTIVITY _ contact identification is added to the Intent packet to identify that the virtualized application is requested to launch when the Intent packet is constructed.
3. The lightweight mobile application virtualization system of claim 1 wherein the container start assist process, before sending the request to start creating the container application, further performs an application check, initiates a target component query request to the Package Manager Service to see if the target component to be started is installed, if the target component is not installed, initiates a target component installation request to the Package Manager Service, and installs the target application according to the installation Package address of the target application into which the target component installation request is passed.
4. The lightweight mobile application virtualization system of claim 1, wherein after parsing an Intent data packet, the activtymanagemager Service checks whether a target application is installed in the current Android system according to a packet name and a UID of the target application recorded in Intent data, if an installation record exists, searches and determines whether an application process of the target application exists, and if the application process does not exist, creates a new record according to the packet name and the UID of the target application for storing information of the application;
checking whether the Intent data contains a FLAG _ ACTIVITY _ CONTAINER FLAG, and sending a CONTAINER process creation request to the CONTAINER root process through a CONTAINER socket when the FLAG _ ACTIVITY _ CONTAINER FLAG is contained.
5. The lightweight mobile application virtualization system of claim 1 wherein the container root process creating and initializing an application execution environment comprises:
creating a Java virtual machine, registering a jni function, loading a ZygoteInit class in the jni function and preloading Java classes and Android resources.
6. The lightweight mobile application virtualization system of claim 1 wherein the create container process comprises:
abi for checking uid, gid, gids, capabilities security authority and application program in the request for creating the container process, checking that a corresponding sub-process is created by calling a fork system after passing, and loading ActivityThread to initialize the container application;
the ActivityThread sets a system path required to be used in the application in an initialization process, sets a certificate storage position of the current application, sets a process name and creates a Binder thread pool for processing Binder communication of Android system services.
7. The lightweight mobile application virtualization system of claim 1 wherein the activitymanageservice, upon receiving a load container application request, looks up package information for a container application according to a Binder request sender's uid and passes the package information to the container process;
and the container process loads and starts the target container application after receiving the packet information of the target container application.
8. The lightweight mobile application virtualization system according to any one of claims 1 to 7, wherein the container root process sets a container identifier as a container application instance ID for each container, the container identifier mapping a matching relationship between the container application instance and a corresponding application process record;
through the container identifier and the application program ID, when the container identifier and the application program ID cannot be matched with the existing container identifier and application program ID, a new container process and a new Activity Stack are created for the container application, and the same-application multi-virtualization instance is realized.
9. The lightweight mobile application virtualization system according to any one of claims 1 to 7, wherein the container root process further creates an allowed access permission list for each container, and sets a name Namespace ID for each allowed access permission list;
when the container application needs to access the system service of the Android system through the service manager service of the Android system, the service manager service opens the corresponding system service to the container application according to the access service contained in the access permission list corresponding to the Namespace ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010588083.6A CN111796909B (en) | 2020-06-24 | 2020-06-24 | Lightweight mobile application virtualization system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010588083.6A CN111796909B (en) | 2020-06-24 | 2020-06-24 | Lightweight mobile application virtualization system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111796909A true CN111796909A (en) | 2020-10-20 |
| CN111796909B CN111796909B (en) | 2024-04-02 |
Family
ID=72803178
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010588083.6A Active CN111796909B (en) | 2020-06-24 | 2020-06-24 | Lightweight mobile application virtualization system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111796909B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210152857A1 (en) * | 2019-11-19 | 2021-05-20 | Samsung Electronics Co., Ltd. | Method, system and device for sharing contents |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20130093804A (en) * | 2012-01-06 | 2013-08-23 | 한국전자통신연구원 | Apparatus and method for secure and consistent runtime based confidential execution of application services |
| CN103593225A (en) * | 2013-10-30 | 2014-02-19 | 浙江大学 | Method for multiplexing Binder IPC mechanism by multiple Android systems in mobile virtualization scene |
| CN106095530A (en) * | 2016-06-08 | 2016-11-09 | 电子科技大学 | The container of a kind of many android system automatically creates and startup method |
| GB201700073D0 (en) * | 2017-01-04 | 2017-02-15 | Cisco Tech Inc | Method and apparatus for container-based virtualisation |
| CN106471791A (en) * | 2015-04-07 | 2017-03-01 | 华为技术有限公司 | Method and apparatus for the PC cluster framework based on mobile device |
| CN106897611A (en) * | 2017-03-03 | 2017-06-27 | 金光 | Secure virtual mobile applications running environment system and method and application without root authority |
-
2020
- 2020-06-24 CN CN202010588083.6A patent/CN111796909B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20130093804A (en) * | 2012-01-06 | 2013-08-23 | 한국전자통신연구원 | Apparatus and method for secure and consistent runtime based confidential execution of application services |
| CN103593225A (en) * | 2013-10-30 | 2014-02-19 | 浙江大学 | Method for multiplexing Binder IPC mechanism by multiple Android systems in mobile virtualization scene |
| CN106471791A (en) * | 2015-04-07 | 2017-03-01 | 华为技术有限公司 | Method and apparatus for the PC cluster framework based on mobile device |
| CN106095530A (en) * | 2016-06-08 | 2016-11-09 | 电子科技大学 | The container of a kind of many android system automatically creates and startup method |
| GB201700073D0 (en) * | 2017-01-04 | 2017-02-15 | Cisco Tech Inc | Method and apparatus for container-based virtualisation |
| CN106897611A (en) * | 2017-03-03 | 2017-06-27 | 金光 | Secure virtual mobile applications running environment system and method and application without root authority |
Non-Patent Citations (1)
| Title |
|---|
| 王千;张激;高元钧: "一种基于组件的应用虚拟化方法", 计算机工程, vol. 39, no. 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20210152857A1 (en) * | 2019-11-19 | 2021-05-20 | Samsung Electronics Co., Ltd. | Method, system and device for sharing contents |
| US11936928B2 (en) * | 2019-11-19 | 2024-03-19 | Samsung Electronics Co., Ltd. | Method, system and device for sharing contents |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111796909B (en) | 2024-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108170503B (en) | Method, terminal and storage medium for cross-system android application running | |
| CN101755271A (en) | Method and apparatus for managing access privilege in cldc osgi environment | |
| US5566326A (en) | Copy file mechanism for transferring files between a host system and an emulated file system | |
| US20220004410A1 (en) | Method For Deploying Virtual Machine And Container, And Related Apparatus | |
| US10462228B2 (en) | Providing access to a smartcard within a remote session | |
| US20070124365A1 (en) | Method, apparatus and program storage device that provides a user mode device interface | |
| US20140033208A1 (en) | Method and device for loading application program | |
| US10411957B2 (en) | Method and device for integrating multiple virtual desktop architectures | |
| US7444624B2 (en) | Method for the secure interpretation of programs in electronic devices | |
| CN110532106B (en) | Inter-process communication method, device, equipment and storage medium | |
| WO2019062771A1 (en) | Method for enabling multiple instances of one android application to be opened, mobile terminal, and storage medium | |
| CN113010265A (en) | Pod scheduling method, scheduler, memory plug-in and system | |
| WO2022170946A1 (en) | Access control method and related apparatus | |
| CN111796909B (en) | Lightweight mobile application virtualization system | |
| US11411887B2 (en) | Method and device for performing traffic control on user equipment | |
| CN116467704A (en) | Resource calling method and device | |
| KR20130063399A (en) | Mobile terminal and cloud server for mobile cloud computing environment and method of mobile cloud computing using the same | |
| US10223178B2 (en) | Enabling WPD devices to be managed at the capability level | |
| CN115129250A (en) | Object storage method and device and readable storage medium | |
| TWI814877B (en) | Isolating a redirected biometric device to a remote session | |
| CN110502354B (en) | Java intelligent card and calling method of application program interface thereof | |
| US20200050781A1 (en) | Differentiating and managing identical usb devices | |
| CN111339173A (en) | Data sharing method, server and readable storage medium | |
| CN111737013B (en) | Chip resource management method and device, storage medium and system chip | |
| CN117235771B (en) | Permission management and control method of application program and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Wang Zonghui Inventor after: Zhang Xinhao Inventor after: Liu Peiyu Inventor after: Chen Wenzhi Inventor before: Wang Zonghui Inventor before: Zhang Xinhao Inventor before: Liu Peiyu Inventor before: Chen Wenzhi |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |