CN105357256B - Manage the method and server of mobile device - Google Patents
Manage the method and server of mobile device Download PDFInfo
- Publication number
- CN105357256B CN105357256B CN201510626718.6A CN201510626718A CN105357256B CN 105357256 B CN105357256 B CN 105357256B CN 201510626718 A CN201510626718 A CN 201510626718A CN 105357256 B CN105357256 B CN 105357256B
- Authority
- CN
- China
- Prior art keywords
- container
- mobile device
- android
- server
- driving
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
Abstract
The invention discloses a kind of method and server of management mobile device, the method for the management mobile device includes the following steps：Multiple Android containers are built in container server；By the one-to-one access Android container of multiple mobile devices, the operating rights of the Android container is obtained, to carry out remote operation to the mobile device.Compatibility and isolation when present invention progress mobile device management is preferable, and resource occupation is low compared with virtual machine.
Description
Technical field
The present invention relates to the methods and service of mobile device management technical field more particularly to a kind of management mobile device
Device.
Background technology
With becoming stronger day by day for the terminal function based on operating systems such as iOS and Android, mobile Internet industry
It is developed rapidly.Originally smart mobile phone and tablet computer for designing for individual consumer etc. constantly be used to carry crucial
Business and core application allow users to the constraint for breaking away from office, are handled by mobile terminal devices such as smart mobile phones each
Kind affairs.
Mobile device management (Mobile Device Management, MDM) is corporate information technology to mobile Internet
The platform technology of transition helps enterprise that information technology management ability is extended to mobile device even movement from traditional computer and answers
With.
Current mobile device management scheme is essentially all to be used as management and control by correspondence, is encrypted to data and communication
Anti-leak protects data safety to prevent communication data from leaking, but there is a problem of poor compatibility and dispose inconvenience.Than
As common injection technique realizes network communication data encryption, landing number by automating injection technique modification application to application
According to encryption etc., versatility is higher, but since application code is changed, the problem of causing using poor compatibility；And it is all primary
Using be required for doing inject after just can guarantee safety, it is inconvenient to use.Peace is run by for another example long-range Android virtualization scheme, data center
Tall and erect virtual machine, mobile device pass through remote protocol access of virtual desktop.This technology versatility is good, supports Android and IOS behaviour
Make system, good compatibility, but running background is a complete virtual machine, and occupancy resource is more, and data center's cost is larger,
And virtual machine performance is low.
The above is only used to facilitate the understanding of the technical scheme, and is not represented and is recognized that the above is existing skill
Art.
Invention content
The main purpose of the present invention is to provide a kind of method and system of management mobile device, it is intended to solve mobile device
Managed Solution compatibility and safety it is poor, occupancy resource more than technical problem.
To achieve the above object, the present invention provides a kind of method of management mobile device, the side of the management mobile device
Method includes the following steps：
Multiple Android containers are built in container server；
By the one-to-one access Android container of multiple mobile devices, the operating rights of the Android container is obtained, with to institute
It states mobile device and carries out remote operation.
Preferably, described the step of multiple Android containers are built in container server, includes：
After starting linux kernel and cutting Android environment, start the control group service control of the container server
Groups and namespace service namespace adds name space branch to the specific driving of the bottom of the container server
It holds；
The multiple Android containers of upper layer building of container server after addition name space is supported.
Preferably, it is described it is specific be driven to binding driving, frame buffered-display driver and input and output driving.
Preferably, described by the one-to-one access Android container of multiple mobile devices, obtain the behaviour of the Android container
It weighs, to include the step of carrying out remote operation to the mobile device：
The mobile device is established with corresponding Android container by binding driving and is communicated；
The input and output event is given to by the input and output event that the mobile device is obtained by remote control protocol
The input and output of the corresponding Android container drive, and are delayed the frame of the corresponding Android container by remote control protocol
Punching is sent to the mobile device, to carry out remote operation to the mobile device.
Preferably, the step that the mobile device is established to communication by the binding driving with corresponding Android container
Suddenly include：
When receiving the request message of the mobile device, at binding driving acquisition and the binding driving
The information on services is sent to the mobile device by the information on services of the equipment manager in same Android container, for
The mobile device is established with corresponding Android container according to the information on services and is communicated.
In addition, to achieve the above object, the present invention also provides a kind of servers of mobile device management, including：
Module is built, for building multiple Android containers in container server；
AM access module, for by the one-to-one access Android container of multiple mobile devices, obtaining the Android container
Operating rights, to carry out remote operation to the mobile device.
Preferably, the structure module includes：
Adding device, for after starting linux kernel and cutting Android environment, starting the control of the container server
Group service control groups and namespace service namespace, the specific driving to the bottom of the container server
Name space is added to support；
Construction unit, the multiple Android containers of upper layer building for the container server after addition name space is supported.
Preferably, it is described it is specific be driven to binding driving, frame buffered-display driver and input and output driving.
Preferably, the AM access module includes：
Communication unit is communicated for being established the mobile device with corresponding Android container by binding driving；
Control unit, the input and output event for obtaining the mobile device by remote control protocol will be described defeated
Enter the input and output driving that outgoing event is given to the corresponding Android container, and will be described corresponding by remote control protocol
The frame buffering of Android container is sent to the mobile device, to carry out remote operation to the mobile device.
Preferably, the communication unit is specifically used for when receiving the request message of the mobile device, by described
Binding driving obtains the information on services of the equipment manager in same Android container with the binding driving, by the service
Information is sent to the mobile device, is established and is led to corresponding Android container according to the information on services for the mobile device
Letter.
The present invention a kind of method and server of management mobile device, transport mobile device and its application by container technique
In row to an individual Android container, i.e., run in data center.Skill is virtualized with existing injection technique and long-range Android
Art is compared, and what it is due to container server running background is an independent container, since container does not change application, operation
Environment is independent, so compatibility is preferably；And the isolation of container is preferable, thus it is safer, it is not easy to it divulges a secret；Additionally, due to
The light weight level characteristics of container, resource occupation are low compared with virtual machine.
Description of the drawings
Fig. 1 is the flow diagram of one embodiment of method of present invention management mobile device；
Fig. 2 is the refinement flow diagram of step S101 in Fig. 1；
Fig. 3 is to drive addition name space to support front and back comparison diagram binding in Fig. 2；
Fig. 4 is to add name space to frame buffered-display driver in Fig. 2 to support front and back comparison diagram；
Fig. 5 is to drive addition name space to support front and back comparison diagram input and output in Fig. 2；
Fig. 6 is the refinement flow diagram of step S102 in Fig. 1；
Fig. 7 is the high-level schematic functional block diagram of one embodiment of server of mobile device management of the present invention；
Fig. 8 is the refinement high-level schematic functional block diagram that module is built in Fig. 7；
Fig. 9 is the refinement high-level schematic functional block diagram of AM access module in Fig. 8.
The embodiments will be further described with reference to the accompanying drawings for the realization, the function and the advantages of the object of the present invention.
Specific implementation mode
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
The present invention provides a kind of method of management mobile device, referring to Fig.1, in one embodiment, the management mobile device
Method include：
Step S101 builds multiple Android containers in container server；
In the present embodiment, on the linux system of container server, multiple peaces are built by the container technique of linux
Tall and erect container.Container is a kind of lightweight virtualization technology of shared kernel, and the occupancy of resource is lower compared with virtual machine.
The one-to-one access Android container of multiple mobile devices is obtained the operation of the Android container by step S102
Power, to carry out remote operation to the mobile device.
In the present embodiment, when being operated to mobile device, the Android constructed by the one-to-one access of mobile device is held
Device obtains the operating rights of the Android container, to carry out remote operation.
By taking an enterprise is managed the mobile phone of employee as an example, employee needs to do by mobile device (mobile phone)
Public affairs, if with private mobile phone, relate to company to maintain secrecy, in terms of audit the problem of, then company is public to one the Taiwan Affairs Office of each employee
Mobile phone will do the Android container that the one-to-one access of common mobile phone is built in container server, then container server
The operating rights for obtaining Android container can carry out remote operation, that is, manipulate the permission for doing common mobile phone in employee's hand, allow it
Handle official business relevant operation and forbid the confidential information etc. of its enterprise of leaking, to realize to doing common mobile phone in employee's hand
Carry out remote management, the anti-operations such as divulge a secret.The present embodiment is by container technique mobile device and its application operation to a list
In only Android container, i.e., run in data center.Compared with existing injection technique and long-range Android virtualization technology, due to
Container server running background is an independent container, and since container does not change application, running environment is independent
, so compatibility is preferably；And the isolation of container is preferable, thus it is safer, it is not easy to it divulges a secret；Additionally, due to the light weight of container
Level characteristics, resource occupation are low compared with virtual machine.
The present embodiment, with common KVM virtual machine instances, it is left that KVM virtual machines generally decline 5% relative to physical machine performance
The right side, and the bigger of upper decline is frequently applied, and also KVM virtual machines cannot share video card.But these problems are not present in container,
Container is shared kernel, and it is directly to run on physical cpu to instruct, so performance will not decline, and can be shared aobvious
Card.
In the present embodiment, 2 virtual machines are enabled, it is respectively 105% and 7% that virtual machine process (qemu), which occupies CPU, memory
It is 11.8% and 14.2% to occupy, and full machine not hot spot when enabling 4 Android containers, and CPU and EMS memory occupation are than enabling 2
Virtual machine is much lower, more enables a container and opens as a process more, the speed of service is quickly.
In a preferred embodiment, as shown in Fig. 2, on the basis of the embodiment of above-mentioned Fig. 1, above-mentioned steps S101 packets
It includes：
Step S1011 starts the control group of the container server after starting linux kernel and cutting Android environment
Control groups and namespace service namespace are serviced, the specific driving of the bottom of the container server is added
Name space is added to support；
Step S1012, the multiple Android containers of upper layer building of the container server after addition name space is supported.
In the present embodiment, start the linux kernel of container server, initialization context, then by change root
Chroot cuts Android environment.Android environment itself is a complete chroot environment, is easy to be packaged entire framework, make
Container.
In the present embodiment, Android environment will support container technique, need opening control group service cgroup and name sky
Between on the basis of service namespace, change the specific driving of bottom, addition name space is supported, with to constructed Android
Different driving in container is identified.
It, can be in the multiple Android containers of upper layer building of container server after the support of layer with the end in the present embodiment.
Wherein, specific driving includes at least binding driving, frame buffered-display driver and input and output driving, these three drivings are structures
The basis of an Android container is built, constructed Android container may be considered virtual Android container.
As shown in figure 3, in figure (3a), there are one original binding drivings only, can only register an equipment manager.This
Implement for example shown in figure (3b), in binding drives, name space is added and supports, passes through the side of name space oil (gas) filling device manager
Formula identifies the equipment manager in different Android containers, achievees the effect that support more containers.
As shown in figure 4, in figure (4a), original frame buffered-display driver also only there are one, can only support a mobile device
Display.The present embodiment is as shown in figure (4b), in frame buffered-display driver, name space is added and supports, passes through name space plus frame
The mode of buffering area identifies the frame buffer zone in different Android containers, achievees the effect that support more containers.
As shown in figure 5, in figure (5a), original input and output drive in framework, all input and output of mobile device
Event is notified that the input and output drive.The present embodiment drives input and output as shown in figure (5b), and it is empty that name is added
Between support, different name spaces identifies the driving of the input and output in different Android containers, in this way simulation input
Output achievees the effect that support more containers.
In a preferred embodiment, as shown in fig. 6, on the basis of the embodiment of above-mentioned Fig. 1, above-mentioned steps S102 packets
It includes：
The mobile device is established with corresponding Android container by binding driving and is communicated by step S1021；
Step S1022 obtains the input and output event of the mobile device by remote control protocol, and the input is defeated
Outgoing event is given to the input and output driving of the corresponding Android container, and by remote control protocol by the corresponding Android
The frame buffering of container is sent to the mobile device, to carry out remote operation to the mobile device.
In the present embodiment, the service of itself is registered to by binding driving in equipment manager by container service end, mobile
When the application of equipment will use some service, the IP information on services of the service is obtained from equipment manager by binding driving,
It is sent to mobile device, then mobile device establishes communication according to the IP information on services of acquisition and container service end, to access
Corresponding Android container.Mobile device and container service end can carry out normal communication interaction by binding driving in this way.
When container server carries out remote operation to multiple mobile devices, a mobile device accesses an Android container and in the peace
It is run in tall and erect container, realizes and remote operation is carried out to multiple mobile devices.
In the present embodiment, after mobile device accesses corresponding Android container, movement is obtained by remote control protocol and is set
Standby input and output event, the input and output that input and output event is given to corresponding Android container drive, and by remotely controlling
The frame buffering of corresponding Android container is sent to the mobile device by agreement processed so that the runnable interface energy of multiple mobile devices
It is enough to be shown in the container server medium-long range, in this way, realizing that container server carries out remote operation to multiple mobile devices.
Preferably, include by binding driving and establishing to communicate with corresponding Android container by mobile device：Mobile device to
Container server sends request message, and after container server receives the request message of mobile device, the binding driving obtains
With the IP information on services of equipment manager of the binding driving in same Android container, IP information on services is sent to movement and is set
Standby, mobile device is established with corresponding Android container according to the IP information on services and is communicated.
The present invention also provides a kind of servers of mobile device management, as shown in fig. 7, in one embodiment, including：
Module 101 is built, for building multiple Android containers in container server；
In the present embodiment, the server of the mobile device management is container server.
On the linux system of container server, multiple Android containers are built by the container technique of linux.Container
It is a kind of lightweight virtualization technology of shared kernel, the occupancy of resource is lower compared with virtual machine.
AM access module 102 is used for the one-to-one access Android container of multiple mobile devices,
In the present embodiment, when being operated to mobile device, the Android constructed by the one-to-one access of mobile device is held
Device obtains the operating rights of the Android container, to carry out remote operation to the mobile device.
By taking an enterprise is managed the mobile phone of employee as an example, employee needs to do by mobile device (mobile phone)
Public affairs, if with private mobile phone, relate to company to maintain secrecy, in terms of audit the problem of, then company is public to one the Taiwan Affairs Office of each employee
Mobile phone will do the Android container that the one-to-one access of common mobile phone is built in container server, then container server
The operating rights for obtaining Android container can carry out remote operation, that is, manipulate the permission for doing common mobile phone in employee's hand, allow it
Handle official business relevant operation and forbid the confidential information etc. of its enterprise of leaking, to realize to doing common mobile phone in employee's hand
Carry out remote management, the anti-operations such as divulge a secret.
The present embodiment by container technique in mobile device and its application operation to an individual Android container, in number
It is run according to center.Compared with existing injection technique and long-range Android virtualization technology, due to container server running background
It is an independent container, since container does not change application, running environment is independent, so compatibility is preferably；And
The isolation of container is preferable, therefore safer, it is not easy to divulge a secret；Additionally, due to the light weight level characteristics of container, resource occupation is more empty
Quasi- machine is low.
The present embodiment, with common KVM virtual machine instances, it is left that KVM virtual machines generally decline 5% relative to physical machine performance
The right side, and the bigger of upper decline is frequently applied, and also KVM virtual machines cannot share video card.But these problems are not present in container,
Container is shared kernel, and it is directly to run on physical cpu to instruct, so performance will not decline, and can be shared aobvious
Card.
In the present embodiment, 2 virtual machines are enabled, it is respectively 105% and 7% that virtual machine process (qemu), which occupies CPU, memory
It is 11.8% and 14.2% to occupy, and full machine not hot spot when enabling 4 Android containers, and CPU and EMS memory occupation are than enabling 2
Virtual machine is much lower, more enables a container and opens as a process more, the speed of service is quickly.
In a preferred embodiment, as shown in figure 8, on the basis of the embodiment of above-mentioned Fig. 7, structure module 101 is wrapped
It includes：
Adding device 1011, for after starting linux kernel and cutting Android environment, starting the container server
Control group services control groups and namespace service namespace, to the specific of the bottom of the container server
Driving addition name space is supported；
Construction unit 1012, the multiple Androids of upper layer building for the container server after addition name space is supported are held
Device.
In the present embodiment, start the linux kernel of container server, initialization context, then by change root
Chroot cuts Android environment.Android environment itself is a complete chroot environment, is easy to be packaged entire framework, make
Container.
In the present embodiment, Android environment will support container technique, need opening control group service cgroup and name sky
Between on the basis of service namespace, change the specific driving of bottom, addition name space is supported, with to constructed Android
Different driving in container is identified.
It, can be in the multiple Android containers of upper layer building of container server after the support of layer with the end in the present embodiment.
Wherein, specific driving includes at least binding driving, frame buffered-display driver and input and output driving, these three drivings are structures
The basis of an Android container is built, constructed Android container may be considered virtual Android container.
As shown in Figure 3 above, in figure (3a), there are one original binding drivings only, can only register an equipment management
Device.The present embodiment is as shown in figure (3b), in binding drives, name space is added and supports, is managed by name space oil (gas) filling device
The mode of device identifies the equipment manager in different Android containers, achievees the effect that support more containers.
As shown in Figure 4 above, in figure (4a), original frame buffered-display driver also only there are one, can only support a movement
The display of equipment.The present embodiment is as shown in figure (4b), in frame buffered-display driver, name space is added and supports, passes through name space
Add the mode of frame buffer zone to identify the frame buffer zone in different Android containers, achievees the effect that support more containers.
As shown in Figure 5 above, in figure (5a), original input and output drive in framework, all inputs of mobile device
Outgoing event is notified that the input and output drive.The present embodiment drives input and output as shown in figure (5b), and name is added
Word space supports that different name spaces identifies the driving of the input and output in different Android containers, simulates in this way
Input and output achieve the effect that support more containers.
In a preferred embodiment, as shown in figure 9, on the basis of the embodiment of above-mentioned Fig. 7, AM access module 102 is wrapped
It includes：
Communication unit 1021 is logical for being established the mobile device with corresponding Android container by binding driving
Letter；
Control unit 1022, the input and output event for obtaining the mobile device by remote control protocol, by institute
The input and output driving that input and output event is given to the corresponding Android container is stated, and will be described right by remote control protocol
The frame buffering for the Android container answered is sent to the mobile device, to carry out remote operation to the mobile device.
In the present embodiment, the service of itself is registered to by binding driving in equipment manager by container service end, mobile
When the application of equipment will use some service, the IP information on services of the service is obtained from equipment manager by binding driving,
It is sent to mobile device, then mobile device establishes communication according to the IP information on services of acquisition and container service end, to access
Corresponding Android container.Mobile device and container service end can carry out normal communication interaction by binding driving in this way.
When container server carries out remote operation to multiple mobile devices, a mobile device accesses an Android container and in the peace
It is run in tall and erect container, realizes and remote operation is carried out to multiple mobile devices.
In the present embodiment, after mobile device accesses corresponding Android container, movement is obtained by remote control protocol and is set
Standby input and output event, the input and output that input and output event is given to corresponding Android container drive, and by remotely controlling
The frame buffering of corresponding Android container is sent to the mobile device by agreement processed so that the runnable interface energy of multiple mobile devices
It is enough to be shown in the container server medium-long range, in this way, realizing that container server carries out remote operation to multiple mobile devices.
Preferably, communication unit 1021 is specifically used for when receiving the request message of the mobile device, by described
Binding driving obtains the information on services of the equipment manager in same Android container with the binding driving, by the service
Information is sent to the mobile device, is established and is led to corresponding Android container according to the information on services for the mobile device
Letter.
It these are only the preferred embodiment of the present invention, be not intended to limit the scope of the invention, it is every to utilize this hair
Equivalent structure or equivalent flow shift made by bright specification and accompanying drawing content is applied directly or indirectly in other relevant skills
Art field, is included within the scope of the present invention.
Claims (10)
1. a kind of method of management mobile device, which is characterized in that the method for the management mobile device includes the following steps：
Multiple Android containers are built in container server；
By multiple mobile devices by binding the one-to-one access Android container of driving, the operation of the Android container is obtained
Power, to carry out remote operation to the mobile device, wherein the binding driving and the equipment manager in the Android container
It is associated with, service is registered in the equipment manager by the container service end in the Android container by binding driving.
2. the method for management mobile device as described in claim 1, which is characterized in that the structure in container server is more
The step of a Android container includes：
After starting linux kernel and cutting Android environment, start the control group service control of the container server
Groups and namespace service namespace adds name space branch to the specific driving of the bottom of the container server
It holds；
The multiple Android containers of upper layer building of container server after addition name space is supported.
3. the method for management mobile device as claimed in claim 2, which is characterized in that described specific to be driven to binding drive
Dynamic, frame buffered-display driver and input and output driving.
4. the method for management mobile device as claimed in claim 3, which is characterized in that described that multiple mobile devices are one-to-one
The Android container is accessed, the operating rights of the Android container is obtained, with the step of to mobile device progress remote operation
Including：
The mobile device is established with corresponding Android container by binding driving and is communicated；
The input and output event is given to described by the input and output event that the mobile device is obtained by remote control protocol
The input and output of corresponding Android container drive, and the frame of the corresponding Android container is buffered hair by remote control protocol
The mobile device is given, to carry out remote operation to the mobile device.
5. the method for management mobile device as claimed in claim 4, which is characterized in that described to be driven institute by the binding
Stating the step of mobile device establishes communication with corresponding Android container includes：
When receiving the request message of the mobile device, obtained with binding driving in same by binding driving
The information on services is sent to the mobile device by the information on services of the equipment manager in one Android container, for
The mobile device is established with corresponding Android container according to the information on services and is communicated.
6. a kind of server of mobile device management, which is characterized in that including：
Module is built, for building multiple Android containers in container server；
AM access module, for multiple mobile devices by binding the one-to-one access Android container of driving, to be obtained the peace
The operating rights of tall and erect container, to carry out remote operation to the mobile device, wherein in the binding driving and the Android container
Equipment manager association, container service end in the Android container will service by binding driving is registered in described in set
Standby manager.
7. the server of mobile device management as claimed in claim 6, which is characterized in that the structure module includes：
Adding device, the control group clothes for after starting linux kernel and cutting Android environment, starting the container server
Be engaged in control groups and namespace service namespace, is added to the specific driving of the bottom of the container server
Name space is supported；
Construction unit, the multiple Android containers of upper layer building for the container server after addition name space is supported.
8. the server of mobile device management as claimed in claim 7, which is characterized in that described specific to be driven to the binding
Driving, frame buffered-display driver and input and output driving.
9. the server of mobile device management as claimed in claim 8, which is characterized in that the AM access module includes：
Communication unit is communicated for being established the mobile device with corresponding Android container by binding driving；
Control unit, the input and output event for obtaining the mobile device by remote control protocol are defeated by the input
Outgoing event is given to the input and output driving of the corresponding Android container, and by remote control protocol by the corresponding Android
The frame buffering of container is sent to the mobile device, to carry out remote operation to the mobile device.
10. the server of mobile device management as claimed in claim 9, which is characterized in that the communication unit is specifically used for
When receiving the request message of the mobile device, is obtained by binding driving and be in same peace with binding driving
The information on services is sent to the mobile device, for described by the information on services of the equipment manager in tall and erect container
Mobile device is established with corresponding Android container according to the information on services and is communicated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510626718.6A CN105357256B (en) | 2015-09-28 | 2015-09-28 | Manage the method and server of mobile device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510626718.6A CN105357256B (en) | 2015-09-28 | 2015-09-28 | Manage the method and server of mobile device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105357256A CN105357256A (en) | 2016-02-24 |
| CN105357256B true CN105357256B (en) | 2018-10-30 |
Family
ID=55333115
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510626718.6A Active CN105357256B (en) | 2015-09-28 | 2015-09-28 | Manage the method and server of mobile device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105357256B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106020942B (en) * | 2016-05-05 | 2019-03-26 | 四川安嵌科技有限公司 | A kind of WiFi equipment multiplexing method and device based on multisystem |
| CN106095530B (en) * | 2016-06-08 | 2019-10-22 | 电子科技大学 | A kind of container of more android systems automatically creates and its starts method |
| US10405182B2 (en) * | 2016-06-30 | 2019-09-03 | Huawei Technologies Co., Ltd. | Systems devices and processes to support mobile device management of multiple containers in virtualization environment |
| CN106776067B (en) * | 2016-11-29 | 2020-10-23 | 北京元心科技有限公司 | Method and device for managing system resources in multi-container system |
| CN107179955A (en) * | 2017-05-08 | 2017-09-19 | 北京海杭通讯科技有限公司 | Equipment blocking method and its terminal based on Android containers |
| CN107517245A (en) * | 2017-07-10 | 2017-12-26 | 电子科技大学 | A kind of mobile security sandbox design based on static analysis |
| CN107682445A (en) * | 2017-10-24 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of building method of the mobile cloud desktop platform based on cloud framework |
| CN109922106B (en) * | 2017-12-13 | 2021-09-17 | 中标软件有限公司 | Cloud mobile phone system realized based on Docker container |
| CN109587118B (en) | 2018-11-11 | 2021-05-11 | 长沙摩智云计算机科技有限公司 | Distributed multi-terminal and multi-network supporting system for Android online game |
| CN112073448B (en) * | 2019-06-11 | 2022-10-11 | 成都鼎桥通信技术有限公司 | Service isolation method and device for dual-system terminal |
| CN112068968B (en) * | 2019-06-11 | 2022-10-18 | 成都鼎桥通信技术有限公司 | Service access method and device for dual-system terminal |
| CN114047933A (en) * | 2021-10-20 | 2022-02-15 | 北京鲸鲮信息系统技术有限公司 | Method, device, equipment and medium for multi-open Android application |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102439564A (en) * | 2011-10-24 | 2012-05-02 | 华为技术有限公司 | Method and system for starting application program in linux container |
| CN103530189A (en) * | 2013-09-29 | 2014-01-22 | 中国科学院信息工程研究所 | Automatic scaling and migrating method and device oriented to stream data |
| CN103986608A (en) * | 2014-05-29 | 2014-08-13 | 浪潮电子信息产业股份有限公司 | J2EE application virtualization management method based on Itanium Linux application containers |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103312661B (en) * | 2012-03-07 | 2016-02-17 | 腾讯科技（深圳）有限公司 | A kind of service access method and device |
-
2015
- 2015-09-28 CN CN201510626718.6A patent/CN105357256B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102439564A (en) * | 2011-10-24 | 2012-05-02 | 华为技术有限公司 | Method and system for starting application program in linux container |
| CN103530189A (en) * | 2013-09-29 | 2014-01-22 | 中国科学院信息工程研究所 | Automatic scaling and migrating method and device oriented to stream data |
| CN103986608A (en) * | 2014-05-29 | 2014-08-13 | 浪潮电子信息产业股份有限公司 | J2EE application virtualization management method based on Itanium Linux application containers |
Non-Patent Citations (2)
| Title |
|---|
| 基于LinuxContainer的Android移动终端虚拟化;陈晓;《中国优秀硕士学位论文全文数据库》;20140615;第66-81页 * |
| 计算机桌面虚拟化技术在教学及管理中的实现路径研究;韩芳，袁宇宾;《重庆理工大学学报（自然科学版）》;20140731;第28卷(第7期);第105-109页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105357256A (en) | 2016-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105357256B (en) | Manage the method and server of mobile device | |
| JP6387579B2 (en) | System and method for branding of deferred and remotely operated devices | |
| CN104704471B (en) | Virtual machine multicast/broadcast in virtual network | |
| CN102202289B (en) | Method and system for remote calling software and hardware resources through mobile terminal | |
| US9141325B2 (en) | Communications management | |
| EP3353987B1 (en) | Enabling communication while limiting access to user information | |
| RU2683620C1 (en) | Method of the data sharing implementation between the client and the virtual desktop, the client and the system | |
| CN105099706A (en) | Data communication method, user equipment and server | |
| CN105247526A (en) | Providing an enterprise application store | |
| CN102523304A (en) | Application cloud platform and implementation method thereof | |
| CN105323229B (en) | A kind of data transmission method based on CPE, network element, platform and system | |
| CN102868732A (en) | Account password-based login implementation method, system and device | |
| CN102546788A (en) | Cloud platform management method and cloud platform | |
| CN112311851B (en) | Network policy configuration method and device | |
| CN109154968B (en) | System and method for secure and efficient communication within an organization | |
| CN102821161A (en) | Method, device and system for network security auditing | |
| CN109246138A (en) | Resource access method and device, VPN terminal and medium based on Virtual Private Network | |
| CN103581111A (en) | Communication method and system | |
| CN102546166A (en) | Method, system and device for identity authentication | |
| US10396828B2 (en) | Virtualized hardware support for mobile devices | |
| CN104091102B (en) | A kind of multi-user management method and its device based on Android system | |
| US8860740B2 (en) | Method and apparatus for processing a display driver in virture desktop infrastructure | |
| CN103763370B (en) | A kind of method, system and device for changing mobile terminal workspace screen-lock password | |
| US20220217582A1 (en) | User plane replicator | |
| US20150381385A1 (en) | Packet encapsulation with redirected dma for software defined networks |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200611 Address after: Nanshan District Xueyuan Road in Shenzhen city of Guangdong province 518000 No. 1001 Nanshan Chi Park building A1 layer Patentee after: SANGFOR TECHNOLOGIES Inc. Address before: Nanshan District Xueyuan Road in Shenzhen city of Guangdong province 518000 No. 1001 Nanshan Chi Park A1 building five floor Patentee before: Shenxin network technology (Shenzhen) Co.,Ltd. |