A dual-system cloud security mobile phone bluetooth management method

Abstract

The application provides a double-system cloud security mobile phone Bluetooth management method, and establishes a double-system cloud security mobile phone; deploys an LXC container in a mobile phone Linux kernel, and establishes a double-container system based on the LXC container; establishes a virtual Bluetooth service in each of the two container systems based on the Bluetooth hardware of a host computer; and stores the service process ID of each; sets process protection for the virtual Bluetooth service in a life system, and sets switch killing for the virtual Bluetooth service in a security system. The application sets different management schemes for different container systems, meets different use requirements of the Bluetooth of different container systems, and guarantees normal use of users.

Description

Technical Field

[0001] This invention belongs to the field of dual-system mobile phone technology, and in particular relates to a dual-system cloud security mobile phone Bluetooth management method. Background Technology

[0002] With the rapid development of cloud and mobile terminal technologies, more and more users require terminal application scenarios with internal and external isolation. Examples include users of mobile terminal devices used in public security, procuratorate, and judicial organs, and users who want to separate mobile terminal devices used for work and those used for personal life. For information security or data confidentiality reasons, these users typically adopt a dual-phone strategy: one phone for personal use and another for work. However, using two phones is inconvenient to carry and introduces operational difficulties.

[0003] Based on these user needs, dual-system phones have emerged. Leveraging container technology, dual-system phones can use both a personal system and a security system in parallel, and can switch between the foreground and background systems at any time according to the user's needs.

[0004] While dual-system phones can meet user needs for information security and data confidentiality to some extent, they also present some problems during use. In particular, both phones have Bluetooth functionality, and both dual-container systems require Bluetooth. However, the usage requirements for Bluetooth differ between the two systems. Current technologies typically use a unified management model, which may lead to confusion in Bluetooth driver usage. This not only affects the user experience but can sometimes directly impact normal user operation. Summary of the Invention

[0005] This invention proposes a Touch Penetration Method for Dual-System Cloud Security Phones, which meets the different Bluetooth usage requirements of different container systems and ensures normal user operation.

[0006] To achieve the above objectives, the technical solution of the present invention is implemented as follows:

[0007] A dual-system cloud-secure mobile phone Bluetooth management method includes:

[0008] S1. Establish a dual-system cloud-secure mobile phone; deploy an LXC container on the phone's Linux kernel, and establish a dual-container system based on the LXC container; the first container system is the life system, which is set as the default system on the phone itself, and the second container system is the security system, which is stored on a cloud server as a cloud image.

[0009] S2. Establish virtual Bluetooth services in each of the two container systems based on the host machine's Bluetooth hardware, and store their respective service process IDs;

[0010] In the life system, process protection is set for the virtual Bluetooth service. The protection method is to add the service process ID to the whitelist and continue to run the processes in the whitelist when the system switches.

[0011] The virtual Bluetooth service is set to be killed during system switching. The virtual Bluetooth service process is killed by the service process ID when the system switches.

[0012] S3. When a Bluetooth device is first connected, the current container is determined to decide which container the current Bluetooth device information is stored in.

[0013] S4. When switching between dual-container systems, perform protection or kill of the Bluetooth service based on the different settings of the current container for the Bluetooth service.

[0014] Furthermore, both container systems register Bluetooth devices as services and characteristics, identify them with UUIDs, and store them separately in the two container systems using file isolation.

[0015] Furthermore, step S3 specifically includes:

[0016] S301. In the host machine's BluetoothSettings class, through...

[0017] The devicelistpreferencefragment function determines the current container system.

[0018] S302. If the current system is a secure system, the Bluetooth device decides which container system to store the current device information in based on usage requirements.

[0019] S303. If the current system is a living system, the Bluetooth device is directly applied to the current living system.

[0020] Furthermore, step S4 specifically includes:

[0021] S401. If the living system is switched to the security system, the Bluetooth service of the living system will continue to be maintained.

[0022] S402. If the security system switches to the life system, the Bluetooth service of the security system is killed.

[0023] Furthermore, the two container systems utilize Bluetooth-driven methods including:

[0024] Standby: A ready state, prepared to transition to another state;

[0025] Broadcasting: The state of sending data outwards;

[0026] Scanning: During the scanning state, upon receiving an ADV_IND packet, a SCAN_REQ packet is sent to obtain more information;

[0027] Initiating a connection: In the connection initiation state, after ADV_IND or ADV_DIRECT_IND, a CONNECT_REQ packet is sent to establish a connection;

[0028] Connected: Based on the parameters agreed upon at the time of connection, send CONNECT_EVENT to keep the connection open.

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

[0030] This invention proposes a Bluetooth management method for dual-system cloud security mobile phones, which sets different management schemes for different container systems to meet the different Bluetooth usage requirements of different container systems and ensure normal use by users. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the dual-system cloud phone structure according to an embodiment of the present invention;

[0032] Figure 2 This is a flowchart illustrating an embodiment of the present invention. Detailed Implementation

[0033] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0034] like Figure 1 The diagram shows the basic architecture of a dual-system cloud security phone. This architecture is based on the Linux operating system, with LXC deployed in the kernel layer of the Linux system. LXC creates virtual environments, i.e., containers, that have their own processes and network space. In this invention, a container management program is set up to manage LXC containers when deploying LXC.

[0035] A dual-container system is built based on LXC containers; the first container system is set as the default system on the mobile phone, and the second container system is stored on a cloud server as a cloud image.

[0036] Based on the above architecture, the method proposed in this invention is as follows: Figure 2 As shown, it includes:

[0037] S1. Establish a dual-system cloud-secure mobile phone; deploy an LXC container on the phone's Linux kernel, and establish a dual-container system based on the LXC container; the first container system is the life system, which is set as the default system on the phone itself, and the second container system is the security system, which is stored on a cloud server as a cloud image.

[0038] S2. Establish virtual Bluetooth services in each of the two container systems based on the host machine's Bluetooth hardware. Specifically, through hardware virtualization technology, two sets of Bluetooth devices are virtualized in the two containers based on the host machine's Bluetooth hardware. Dynamic resource allocation is performed by judging the connected Bluetooth devices in the containers. The registration information of the Bluetooth devices is stored in the two containers in a file-isolated manner. When connecting, the device information of each container is read to connect.

[0039] Add a process protection whitelist to the Bluetooth service of the living system so that the process is not killed when switching systems. When switching to the secure system, Bluetooth devices connected to the living system can still be used through the background container service.

[0040] Since the security system is primarily used for its function, and in order to protect the devices within the security system, the devices within the security system can only be used within the security system. When switching, the security system's Bluetooth process will be killed to ensure the secure use of Bluetooth devices on the cloud security phone.

[0041] S3. When a Bluetooth device is first connected, the devicelistpreferencefragment function in BluetoothSettings is used to determine the current container and decide which container the current device information is stored in.

[0042] The BluetoothSettings class is used for configuration and connection management, managing functions such as loading the Bluetooth interface, searching for Bluetooth devices, connecting to Bluetooth devices, and renaming Bluetooth devices. The DeviceListPreferenceFragment function is used to provide a list of available Bluetooth devices. This invention adds a judgment module to the DeviceListPreferenceFragment function to determine whether the current foreground container system is a living system or a security system.

[0043] S4. During the switching between dual-container systems, the Bluetooth service is protected or killed based on the current container's Bluetooth service settings. When the living system switches to the secure system, its Bluetooth service continues; when the secure system switches back to the living system, its Bluetooth service is killed.

[0044] After a Bluetooth device is assigned to a front-end container system, the front-end container system controls the usage status of the Bluetooth device through the registered service and characteristic. The specific usage methods are as follows:

[0045] Standby: A ready state, prepared to transition to another state;

[0046] Broadcasting: The state of sending data outwards;

[0047] Scanning: During the scanning state, upon receiving an ADV_IND packet, a SCAN_REQ packet is sent to obtain more information;

[0048] Initiating a connection: In the connection initiation state, after ADV_IND or ADV_DIRECT_IND, a CONNECT_REQ packet is sent to establish a connection;

[0049] Connected: Based on the parameters agreed upon at the time of connection, send CONNECT_EVENT to keep the connection open.

[0050] Based on the above description, this invention realizes Bluetooth management of dual-system cloud security mobile phones, ensuring normal use by users.

[0051] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A dual system cloud security mobile phone Bluetooth management method, characterized in that, The application relates to a dual-system cloud security mobile phone. S1, establishing a dual-system cloud security mobile phone; deploying an LXC container in a mobile phone Linux kernel and establishing a dual-container system based on the LXC container; wherein a first container system is a life system and is set in a mobile phone body as a default system, and a second container system is a security system and is stored in a cloud server in a cloud image mode; S2, establishing a virtual Bluetooth service in each of the two container systems based on the Bluetooth hardware of a host computer; and storing the service process ID of each; setting process protection for the virtual Bluetooth service in the life system, and the protection method is to add the service process ID into a white list, and the process in the white list is continuously maintained to run when the system is switched; setting switch killing for the virtual Bluetooth service in the security system, and the virtual Bluetooth service process is killed through the service process ID when the system is switched; S3, when a Bluetooth device is initially connected, current container judgment is carried out to determine which container the current Bluetooth device information is stored in; S4, when the dual-container system is switched, the protection or killing of the Bluetooth service is executed according to the different settings of the Bluetooth service in the current container; Step S3 specifically comprises: S301, in the bluetoothsettings class of the host computer, current container system judgment is carried out through the devicelistpreferencefragment function; S302, if the current system is the security system, the Bluetooth device decides which container system the current device information is stored in according to the use demand; S303, if the current system is the life system, the Bluetooth device is directly applied in the current life system; Step S4 specifically comprises: S401, if the life system is switched to the security system, the Bluetooth service of the life system is continuously maintained; S402, if the security system is switched to the life system, the Bluetooth service of the security system is killed.

2. The dual system cloud security mobile Bluetooth management method of claim 1, wherein, Both container systems register the Bluetooth device service and characteristic and are identified by uuid, and are stored in the two container systems in a file isolation mode.

3. The dual system cloud security mobile Bluetooth management method of claim 1, wherein, The method for using the Bluetooth driver by the two container systems comprises: preparing standby: ready state, preparing to change into other states; broadcasting advertising: state of sending data to the outside; listening to scanning: when an ADV_IND package is accepted, a SCAN_REQ package is sent to obtain more information in the scanning state; initiating connection: initiating connection state, after ADV_IND or ADV_DIRECT_IND, a CONNECT_REQ package is sent to establish connection; connected: according to the parameters agreed upon when connecting, a CONNECT_EVENT is sent to keep the connection unbroken.

Images