CN104598309B - The system of multi-mode OS based on OS virtualizations and its establishment, switching method - Google Patents
The system of multi-mode OS based on OS virtualizations and its establishment, switching method Download PDFInfo
- Publication number
- CN104598309B CN104598309B CN201410852021.6A CN201410852021A CN104598309B CN 104598309 B CN104598309 B CN 104598309B CN 201410852021 A CN201410852021 A CN 201410852021A CN 104598309 B CN104598309 B CN 104598309B
- Authority
- CN
- China
- Prior art keywords
- mode
- nativeservice
- service
- domainengine
- kernel
- 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.)
- Active
Links
Landscapes
- Telephone Function (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides it is a kind of based on OS virtualization multi-mode OS system, for Android device, including：Kernel, at least three User space environment started based on kernel, domain management；Wherein described at least three User spaces environment includes：For a User space environment of infrastructure service, it includes the local service of Android and domain engine；For each different mode OS other each User space environment, it includes respectively：Incubator, Java services and application；On kernel, each different mode OS is run on the management of domain the domain management operating.Further correspondingly provide system creation, the switching method of the multi-mode OS based on OS virtualizations.Android system EMS memory occupation amount can be reduced using the present invention.
Description
Technical field
The present invention relates to the security technology area of the mobile device of Android system, particularly relate to a kind of based on OS virtualizations
Multi-mode system and its establishment, switching method.
Background technology
In Android device, such as the mobile device such as mobile phone, flat board, based on security needs, at present using two kinds of work
The operating system (OS) of pattern：General mode OS and safe mode OS.
When Android device operation be general mode OS when, can perform the low application of security requirement, such as user is usual
Open network browsing, information send etc. daily use.When Android device operation be safe mode OS when, then can hold
The high special applications of row security requirement, such as personal device office (Bring Your Own Device) or individual privacy
Protection, and limit the application of some low-securities of user.Wherein, the running environment of above two pattern is entered from operating system layer
Row isolation so that a kind of pattern does not influence another pattern.
In order to which two kinds of different mode OS of operation can be achieved in Android device, there are three kinds of technical schemes at present：Based on virtual
The scheme of machine, this scheme committed memory is more, and efficiency is low, is less suitable for use in mobile device；Scheme based on application container, this
Kind scheme is not isolated from operating system layer completely, and security is low but committed memory is smaller；The scheme virtualized based on OS,
This scheme is in both upper intermediateness, and security is less than virtual machine but be higher than application container, internal memory be less than virtual machine but
It is approximately higher than application container twice of application container committed memory.From the point of view of security and EMS memory occupation amount, virtualized based on OS
Scheme be more suitable for mobile device.
As Fig. 1 show based on OS virtualize double mode OS system architecture, including kernel (Kernel), based on kernel
The two User space environment started.Two User space environment, an OS for being used to run general mode, another, which is used to run, pacifies
The OS of syntype.Each User space environment includes local service (NativeService), the incubator of a set of Android respectively
(Zygote), Java services (SystemServer) and applies (App).Wherein：
Using the various applications for referring to run in Android system, such as：Contact person, calendar, various social networking applications, game
Deng.
Java services are to provide the process of management and service in Android system for application, and it is included：Android assures reason, window
Management, using stack management etc..
Incubator is the Java Virtual Machine process of Android system, be responsible for creating all application process and Java service into
Journey.
Local service is the non-Java of Android system service processes, is primarily used to as description of each application to kernel
The access or calling of each hardware resource (such as corresponding driving port, or device file) are managed.Such as kernel is provided
Display service (SurfaceFlinger), voice service, Video service, video playback engine (NuPlayer) service, bluetooth
(BT) access of the service such as service, Wifi or calling are managed, and the content of management including being according to the access or calling of application
Certain above-mentioned service of the application distribution kernel, or connect or be disconnected to certain above-mentioned service of kernel etc..Such as according to certain application
Call request, control the voice service that kernel is provided (as corresponding driving interface, or sound device describe the interface of file)
Distribute to the application.
Name space and packeting controller (Namespace+Control Groups) be kernel provide a set of resource every
From mechanism and the mechanism that uses of limitation resource, each User space environment is based on characteristic startup, so as to realize the OS of different mode
Running environment isolated from operating system layer, do not influenced each other between the OS of different mode.
After Android device starts, start described two User space environment successively and enter a User space environment, that is, enter
A kind of OS of pattern, when handover is needed, then notifies kernel, switches into another User space environment by interior nuclear control, that is, switches
To the OS of another pattern.
Under this mode, two User space environment of startup all respectively the local service comprising a set of Android, incubator,
Java is serviced and application, therefore its shared internal memory needs is larger, is approximately start internal memory needed for a User space environment twice.Such as
What can reduce its EMS memory occupation amount, be the technical problem up for solution.
The content of the invention
In view of this, it is a primary object of the present invention to provide it is a kind of based on OS virtualization multi-mode OS system and its
Create, switching method, its EMS memory occupation amount is reduced to realize.
A kind of multi-mode OS based on OS virtualizations provided by the invention system, for Android device, including：Kernel
Kernel, at least three User space environment started based on kernel, domain management DomainManager；
Wherein described at least three User spaces environment include for infrastructure service a User space environment, for it is each not
With pattern OS other each User space environment；
User space environment for infrastructure service includes：The local service NativeService and domain engine of Android
DomainEngine；
The NativeService of the Android is used to be to carry out pipe using the access or calling of each service provided to kernel
Reason；
Each service that the DomainEngine is used to control the NativeService in Android device to provide allows a certain
Selected pattern OS access and calling；
Each User space environment for each different mode OS includes respectively：Incubator Zygote, Java are serviced
SystemServer and using App；
The DomainManager is used for the establishment and life cycle management for controlling each different mode OS；
The DomainManager is run on kernel, each different mode OS run on DomainManager it
On.
By upper, due to present invention employs the primary NativeService of a set of Android system, being total to by different mode OS
Enjoy, more set NativeService are employed rather than background technology description, so as to save a large amount of internal memories, so as to improve
The performance of system.
After tested, the present invention can keep security to remain unchanged, higher than application container scheme；Internal memory is using largely subtracting
It is small, maintain an equal level substantially with application container scheme；And execution efficiency is higher, higher than common OS virtualization schemes, virtual machine approach and
Application container scheme.
Optionally, described other each User space environment for each different mode OS include：It is respectively used to common mould
Formula OS and safe mode OS second and third User space environment.
By upper, the OS of different safety class can be arranged as required to.
Present invention also offers a kind of creation method based on system described above, including step：
A, bottom hardware initialization procedure is performed after start power-up；
B, the bootup process of linux kernel is performed, including starts first user level process init；
C, perform init process bootup process, including Android system initialization, start domain engine successively
DomainEngine processes, start local service NativeService processes, to complete the first User space for infrastructure service
The startup of environment；
D, init processes bootup process also starts domain management DomainManager processes；
E, each different mode OS is created by DomainManager processes successively, to complete to be used for each different mode
The startup of OS each User space environment；
Each pattern OS foundation step includes：Start incubator zygote processes, taken by zygote process initiations java
Business SystemServer processes, and apply app by SystemServer process initiations are each；
The connection status of each service of currently selected pattern OS and NativeService offers is provided by DomainEngine
It is visible for that can connect and be chosen pattern OS display layer.
By upper, because the present invention is in start-up course, the primary NativeService of a set of Android system is employed, by
Different mode OS shares, and more set NativeService is employed rather than background technology description, so as to save in a large amount of
Deposit, so as to improve the performance of system.
Optionally, also include after step E：
DomainManager records the current shape of each service that NativeService is provided under currently selected pattern OS
State.
By upper, due to carrying out the record, when can be chosen pattern OS in order to switch back into this, the shape of the fast each service of quick-recovery
State.
Optionally, include during the step for creating each different mode OS described in step E successively：In addition to the OS of first establishment,
Other each pattern OS create in backstage successively.
By upper, because other each pattern OS are in backstage establishment, therefore user, after first OS has been created, user can make
With the Android device, the normal startup and use of user are not influenceed.
Optionally, the OS of the first establishment is the OS of general mode.
By upper, which, normal startup and use of the user to general mode OS are not influenceed.
Present invention also offers a kind of switching method of the system based on described in claim 1, including step：
When DomainEngine receives handover request, the display management process in NativeService is controlled to set current
Pattern OS display layer is invisible, and the display layer for being chosen pattern OS is visible；
DomainEngine controls NativeService preserves the state for each service that present mode OS is provided；
The process that DomainEngine control present modes OS each application accesses NativeService is hung up；
DomainEngine according to the states of each services of NativeService under the selected pattern OS pre-saved,
Recover the state of each services of NativeService；
The selected pattern OS of DomainEngine controls each application may have access to NativeService.
By upper, the handoff procedure, provided by DomainEngine controls NativeService preserves present mode OS
Each service state；According to the state of each services of NativeService under the selected pattern OS pre-saved, recover
The state of each services of NativeService, it is possible to achieve when being switched to selected pattern OS, quickly recover to the selected pattern OS
Use state originally.
Optionally, DomainEngine controls present mode OS input service stopping to read input equipment node, control
Input equipment node is read in selected pattern OS input services.
Optionally, the handover request is that present mode OS switching is sent using when being triggered by the application.
By upper, user can be as needed, voluntarily selects the OS for the selected pattern to be switched.
Brief description of the drawings
Fig. 1 is the system architecture figure of the existing double mode based on OS virtualizations；
Fig. 2 is the system architecture figure of double mode of the present invention based on OS virtualizations；
Fig. 3 is the Booting sequence figure of dual mode system；
Fig. 4 is the switching flow figure of dual mode system.
Embodiment
Multi-mode OS of the present invention based on OS virtualizations system architecture figure as shown in Figure 2, it is with double in the embodiment
Illustrated exemplified by pattern OS system architecture, including kernel (Kernel), first, second and third User space based on kernel startup
Environment, domain management (DomainManager) module, wherein：
First User space environment is used for infrastructure service, including the local service (NativeService) of Android and a domain are drawn
Hold up (DomainEngine) module.NativeService effect is identical with described in background technology, be primarily used to be to kernel
It is managed using the access or calling of each service of offer.DomainEngine is mainly responsible in Android device
Current each service that NativeService is provided allows to be accessed by which pattern OS and called, and is responsible for Android device in other words
Which pattern OS is current controls give, so as to realize the application access to different mode OS or call device resource to be controlled
And management；The communication being also responsible between different mode OS, such as it is responsible for safe mode and shares partial information from general mode, for example contacts
People's information etc..
Second and third User space environment is all respectively comprising a set of incubator (Zygote), Java services (SystemServer)
General mode OS and safe mode OS are respectively used to using (App), second and third User space environment.
DomainManager is run on kernel, and general mode OS and safe mode OS run on DomainManager
On.DomainManager is responsible for general mode OS and safe mode OS establishment and life cycle management, including management is commonly
Pattern OS and safe mode OS file system.Wherein, general mode OS and safe mode OS can use different file systems
System and system image (img files), general mode OS and safe mode OS can also be the version of different Android systems.
In order to further lift the security of the present invention program, the safety enhancing module of kernel in this programme
(SELinux) it is enforced opening.It should be noted that safety enhancing module is the characteristic for having used kernel, non-invention
The module of creation, therefore repeated not to this.
By upper, due to the system architecture figure of the present invention as shown in Figure 2, it is primary to employ a set of Android system
NativeService, shared by different mode OS, more set NativeService are employed rather than background technology description, from
And a large amount of internal memories are saved, so as to improve the performance of system.Example shown in Fig. 2 further expands, and can also set and the
Two User space environment identical fourth user state environment, realize the three pattern OS based on OS virtualizations.
Present invention also offers the establishment of the system of the double mode OS based on Fig. 2 based on OS virtualizations and switching method,
It is described in detail referring to Fig. 3, Fig. 4.
As Fig. 3 shows the visioning procedure of double mode OS system, after Android device is started shooting, comprise the following steps：
Step 310：Start power-up, the bootloader write by assembler language carry out bottom hardware initialization, also
It is the initialization procedure for completing the related hardwares such as CPU, and loads kernel code, finally jumps to the startup program of kernel.This
Process is identical with existing Android device start-up course, repeats no more.
Step 320：The bootup process of linux kernel.
The process includes successively：Kernel Kernel Initializations, such as internal memory initialization, open and interrupt, initialization plan etc.
Deng；Driving initialization；Start kernel backstage (daemons) thread；Android root (root) file system；And start first use
Family level process init.This process is identical with existing Android device start-up course, repeats no more.
Step 330：Init process initiation processes, include the initialization program of Android system, also include in the present embodiment according to
Secondary startup domain engine (DomainEngine) process, start local service (NativeService) process.
For Android system mobile phone, the program of init processes is located in system/core/init/init.c files, this article
Part is the specific initialization program of Android system, can be created by the process or Android device file, process file and/or be
System file node, and start service or process that the script file specified in the configuration file is specified to start.In this example,
Specified by configuration file and start described DomainEngine, NativeService and domain described hereinafter management successively
(DomainManager)。
The NativeService that the function that the DomainEngine processes started provide mainly is responsible in Android device is carried
Each service supplied allows to be accessed by which pattern OS and called, the default configuration after start be allow to be accessed by general mode OS and
Each service for calling NativeService to provide.
The NativeService processes started include display service (SurfaceFlinger), the sound provided kernel
The access of the services such as sound service, Video service, video playback engine (NuPlayer) service, bluetooth (BT) service, Wifi and tune
With being managed, with existing local service contained by content it is identical, repeat no more.
After DomainEngine and NativeService process initiations, that is, complete and used for the first of infrastructure service
The startup of family state environment.
Step 340：Init process initiation DomainManager processes.
Wherein, general mode OS and safe mode OS establishment and life can be carried out by DomainManager processes
Cycle management, and the management to general mode OS and safe mode OS file system.
Step 350：DomainManager process creation general mode OS, general mode OS establishment process include：
Incubator (zygote) process of startup, (SystemServer) process is serviced by zygote process initiations java, and
By each application (app) of SystemServer process initiations.Start-up course in this process and background technology for starting successively
It is identical, repeat no more.
Wherein, after general mode OS starts, by DomainEngine controls (example in the data data fields of infrastructure service
Such as it is recorded in as under //data catalogues) recording interactive pattern is general mode OS, and is recorded under currently common pattern OS
The current state for each service that NativeService is provided, such as display service, sound, wifi, bt, sound and camera
Deng the state parameter of device resource.The state parameter includes whether to be opened, and is assigned to which application etc..
Step 360：The establishment process that DomainManager processes create safe mode OS, the OS on backstage is general with creating
Logical pattern OS process differences include：
It is invisible to set safe mode OS display layer, such as SafeOsFramelayer=invisible；
The connection status for making each service of each applications of safe mode OS and NativeService offers is off-state.
By upper, then the establishment process of double mode OS system is completed.As seen from the above, the inventive method only enables
One NativeService process, relative to the prior art shown in Fig. 1, substantially reduce system resource, the occupancy of such as internal memory
Amount.
It is further to note that above-mentioned steps 360 can perform simultaneously with step 350.But in order in Android system
System enters the enabled mode of access customer as soon as possible after starting, therefore postpones to perform step 360, enough to have when performing step 350
System resource.
It is logical when the application under present mode OS accesses NaitveService it should be noted that after starting
The Binder processes crossed in kernel realize interprocess communication, enter because Binder inter-process communication mechanisms are that Android system is primary
Communication mechanism between journey, is no longer repeated this.
The flow of double mode OS as shown in Figure 4 system switching method, the example is to be switched to peace from general mode OS
Syntype OS, is detailed below.
Before switching is introduced, carried out first to running on the content related to switching of the Android device under general mode OS
Illustrate, including：
1) there is multi-mode OS switching icons using desktop, the corresponding switching application of the icon, the switching application can be with
DomainEngine process communications；
2) interactive mode that DomainEngine is preserved is common OS patterns, i.e., current equipment control by
DomainEngine gives general mode OS；
3) DomainEngine controls in the data data fields of infrastructure service (such as being recorded in as under //data catalogues)
Recording interactive pattern is general mode OS, and records NativeService when having general mode OS and safe mode OS and carry respectively
The state of each service supplied, such as the state parameter of the device resource such as display service, voice service, wifi services, bt services.
Whether the state parameter is opened including resource corresponding to these services, is assigned to which application etc..
Referring to Fig. 4, specific handoff procedure, comprise the following steps：
Step 410：Android device is presently operating under general mode OS, detects it using the multi-mode on desktop
When OS switching icons are touched by user, switching application corresponding to multi-mode OS switching icons sends a switching to DomainEngine
Interactive mode is set to safe mode OS by request, request DomainEngine.
Step 420：DomainEngine receives the request, performs following step, safe mould is given equipment control
Formula OS：
Step 4201：DomainEngine control general modes OS input service (InputService, including touch screen prison
Control service) stop reading input equipment node, such as stop the monitoring to touch screen service；
Step 4202：Display management process in DomainEngine controls NativeService sets general mode OS
Display layer to be invisible, display layer NormalOsFramelayer=invisible is such as set；
Step 4203：DomainEngine control NativeService preservations are currently provided each by general mode OS
The state of individual local service, preserved by file mode in the data data fields to infrastructure service, under such as //data catalogues, such as
Current video, sound, the state parameter of camera；
Step 4204：The each applications of DomainEngine control NativeService access NativeService process
Hang up, that is, disconnect general mode OS and video, sound and camera connection；
Step 4205：DomainEngine is extensive according to the NativeService states under the safe mode OS pre-saved
Video, sound, the broadcast state of camera, wifi, bt (bloouetooth) unlatching/closed mode under multiple safe mode OS；
For example, according to the information preserved, recover accordingly to service certain to certain distribution applied etc..
Step 4206：DomainEngine controls show that NativeService management module sets safe mode OS's
Display layer is visible；Such as SafeOsFramelayer=visible；
Step 4207：Input equipment node is read in DomainEngine control safe mode OS input services；
Step 4208：DomainEngine makes safe mode OS each application may have access to NativeService, preserves and hands over
Mutual pattern is safe mode OS.
Now, switching is completed, and Android device is presently operating under safe mode OS, and certainly, it can also have using desktop
One pattern OS switches icon, and in order to switch back under general mode OS, its handoff procedure repeats no more.
In addition, above-mentioned is the description that the system of the double mode OS to be virtualized based on OS is carried out as embodiment, it is not difficult to manage
Solution, when for three patterns or more pattern OS when, it, which switched application, can increase the choosing selected from user to which pattern switching
, specifically create process, handoff procedure with it is upper identical, repeat no more.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all essences in the present invention
God any modification, equivalent substitution and improvements made etc., should be included in the scope of the protection with principle.
Claims (9)
- A kind of 1. system of the multi-mode OS based on OS virtualizations, for Android device, it is characterised in that including：Kernel Kernel, at least three User space environment started based on kernel, domain management DomainManager；Wherein described at least three User spaces environment includes a User space environment for infrastructure service, for each different moulds Formula OS other each User space environment；User space environment for infrastructure service includes：The local service NativeService and domain engine of Android DomainEngine；The NativeService of the Android is used to be to be managed using the access or calling of each service provided to kernel；Each service that the DomainEngine is used to control the NativeService in Android device to provide allows a certain selected Pattern OS access and calling；Each User space environment for each different mode OS includes respectively：Incubator Zygote, Java are serviced SystemServer and using App；The DomainManager is used for the establishment and life cycle management for controlling each different mode OS；The DomainManager is run on kernel, and each different mode OS is run on DomainManager.
- 2. system according to claim 1, it is characterised in that described other each users for each different mode OS State environment includes：It is respectively used to general mode OS and safe mode OS second and third User space environment.
- 3. a kind of creation method of the system based on described in claim 1, it is characterised in that including step：A, bottom hardware initialization procedure is performed after start power-up；B, the bootup process of linux kernel is performed, including starts first user level process init；C, perform init process bootup process, including Android system initialization, successively start domain engine DomainEngine enter Journey, start local service NativeService processes, to complete the startup of the first User space environment for infrastructure service；D, init processes bootup process also starts domain management DomainManager processes；E, each different mode OS is created by DomainManager processes successively, to complete for each different mode OS's The startup of each User space environment；Each pattern OS foundation step includes：Start incubator zygote processes, serviced by zygote process initiations java SystemServer processes, and apply app by SystemServer process initiations are each；The connection status that each service of currently selected pattern OS and NativeService offers is controlled by DomainEngine is can Connection and selected pattern OS display layer are visible.
- 4. according to the method for claim 3, it is characterised in that also include after step E：DomainManager records the current state of each service that NativeService is provided under currently selected pattern OS.
- 5. according to the method for claim 3, it is characterised in that create each different mode OS step described in step E successively Include when rapid：In addition to the OS of first establishment, other each pattern OS create in backstage successively.
- 6. according to the method for claim 5, it is characterised in that the OS of the first establishment is the OS of general mode.
- 7. a kind of switching method of the system based on described in claim 1, it is characterised in that including step：When DomainEngine receives handover request, control the display management process in NativeService that present mode is set OS display layer is invisible, and the display layer for being chosen pattern OS is visible；DomainEngine controls NativeService preserves the state for each service that present mode OS is provided；The process that DomainEngine control present modes OS each application accesses NativeService is hung up；DomainEngine recovers according to the state of each services of NativeService under the selected pattern OS pre-saved The state of each services of NativeService；The selected pattern OS of DomainEngine controls each application may have access to NativeService.
- 8. according to the method for claim 7, it is characterised in thatIt is defeated that DomainEngine control present modes OS input service stopping reads input equipment node, the selected pattern OS of control Enter service and read input equipment node.
- 9. according to the method for claim 7, it is characterised in that the handover request is present mode OS switching application quilt Sent during triggering by the application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410852021.6A CN104598309B (en) | 2014-12-31 | 2014-12-31 | The system of multi-mode OS based on OS virtualizations and its establishment, switching method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410852021.6A CN104598309B (en) | 2014-12-31 | 2014-12-31 | The system of multi-mode OS based on OS virtualizations and its establishment, switching method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104598309A CN104598309A (en) | 2015-05-06 |
| CN104598309B true CN104598309B (en) | 2017-12-22 |
Family
ID=53124124
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410852021.6A Active CN104598309B (en) | 2014-12-31 | 2014-12-31 | The system of multi-mode OS based on OS virtualizations and its establishment, switching method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104598309B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109726050A (en) * | 2018-12-28 | 2019-05-07 | 杭州迪普科技股份有限公司 | A kind of method and apparatus of process reparation |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105407218B (en) * | 2015-10-28 | 2018-08-24 | 东莞酷派软件技术有限公司 | A kind of SMS processing method and terminal |
| US10282210B2 (en) | 2016-06-13 | 2019-05-07 | Huawei Technologies Co., Ltd. | System and method for virtual hardware control |
| CN107515790A (en) * | 2016-06-16 | 2017-12-26 | 成都鼎桥通信技术有限公司 | The system of electronic equipment |
| CN106850928B (en) * | 2017-01-13 | 2019-08-06 | 北京安云世纪科技有限公司 | Incoming call and SMS processing method, device and mobile terminal |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101373441A (en) * | 2008-09-19 | 2009-02-25 | 苏州壹世通科技有限公司 | Virtual platform system based on firmware |
| CN101533434A (en) * | 2009-04-10 | 2009-09-16 | 武汉大学 | Leakage-proof credible virtual machine remote certification method facing sensitive data |
| CN101599022A (en) * | 2009-07-07 | 2009-12-09 | 武汉大学 | The Trustworthy computing base cutting method that is used for dummy machine system |
| US8270963B1 (en) * | 2010-10-01 | 2012-09-18 | Viasat, Inc. | Cross domain notification |
| CN103778389A (en) * | 2012-10-18 | 2014-05-07 | 美国博通公司 | Integration of untrusted framework component with secure operating system environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101651202B1 (en) * | 2009-12-21 | 2016-08-26 | 삼성전자주식회사 | Virtualization apparatus and method of operating thereof |
-
2014
- 2014-12-31 CN CN201410852021.6A patent/CN104598309B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101373441A (en) * | 2008-09-19 | 2009-02-25 | 苏州壹世通科技有限公司 | Virtual platform system based on firmware |
| CN101533434A (en) * | 2009-04-10 | 2009-09-16 | 武汉大学 | Leakage-proof credible virtual machine remote certification method facing sensitive data |
| CN101599022A (en) * | 2009-07-07 | 2009-12-09 | 武汉大学 | The Trustworthy computing base cutting method that is used for dummy machine system |
| US8270963B1 (en) * | 2010-10-01 | 2012-09-18 | Viasat, Inc. | Cross domain notification |
| CN103778389A (en) * | 2012-10-18 | 2014-05-07 | 美国博通公司 | Integration of untrusted framework component with secure operating system environment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109726050A (en) * | 2018-12-28 | 2019-05-07 | 杭州迪普科技股份有限公司 | A kind of method and apparatus of process reparation |
| CN109726050B (en) * | 2018-12-28 | 2021-01-26 | 杭州迪普科技股份有限公司 | Process repairing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104598309A (en) | 2015-05-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12001661B2 (en) | Bound based contextual zoom | |
| CN104598309B (en) | The system of multi-mode OS based on OS virtualizations and its establishment, switching method | |
| US20140380406A1 (en) | Polymorphic virtual appliance rule set | |
| EP2857967B1 (en) | User interface management method and system | |
| JP5865496B2 (en) | Lock screen for accessing work environment on personal portable device | |
| Andrus et al. | Cells: a virtual mobile smartphone architecture | |
| KR101530104B1 (en) | Multi-os(operating system) boot via mobile device | |
| US10459772B2 (en) | System, method and computer program product for capturing touch events for a virtual mobile device platform | |
| US7818559B2 (en) | Boot negotiation among multiple boot-capable devices | |
| JP4805238B2 (en) | Method, apparatus and system for enabling a secure location aware platform | |
| WO2016090702A1 (en) | Dual-card dual-standby call method, device and terminal | |
| CN103389900B (en) | A kind of control method and device that Android device camera uses | |
| CN105245523B (en) | Storage service platform and its implementation applied to desktop virtualization scene | |
| JP6466476B2 (en) | Access isolation for multi-operating system devices | |
| US20140331285A1 (en) | Mobile Device Locking with Context | |
| CN106020829A (en) | System and method for switching between environments in multi-environment operating system | |
| CN106155568B (en) | A kind of method and terminal of partition holding | |
| US20190020659A1 (en) | Role-based access control with feature-level granularity | |
| CN106776067A (en) | Method and device for managing system resources in multi-container system | |
| US20200175196A1 (en) | Multi-android system implementation method, storage medium, and terminal | |
| US20130332686A1 (en) | Information processing apparatus, information processing method, and program | |
| CN103257889B (en) | Application program management device and management method for hybrid architecture system | |
| CN108345490A (en) | The method and system of virtual machine is disposed in a kind of NFV | |
| CN106485113A (en) | Mobile terminal and the method for secret protection of mobile terminal | |
| CN109522111A (en) | Call method, device, electronic equipment and the storage medium of the isomery ecosystem |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP02 | Change in the address of a patent holder |
Address after: Room 101-105, floor 1, Chuangda building, No. 9, Qinghua East Road, Haidian District, Beijing 100083 (Dongsheng District) Patentee after: Thunder Software Technology Co., Ltd. Address before: 100191 Beijing Haidian District Lung Cheung Road No. 1 Tai Xiang 4 storey commercial building Patentee before: Thunder Software Technology Co., Ltd. |
|
| CP02 | Change in the address of a patent holder |