Mobile communication method and device, storage medium, and electronic device

Abstract

The present invention provides a mobile communication method and device, a storage medium, and an electronic device, which are applied to a Linux system. The Linux system includes: a main system and a subsystem, wherein the main system is a Linux system, and the subsystem is an Android system running in the main system. The main system includes: a subsystem and an Android mobile communication HAL daemon service module. The method includes: when the main system is started, starting the mobile communication management service of the main system, and starting and running the subsystem and the Android mobile communication HAL daemon service module in the main system; adding an interface adapted to the Android mobile communication HAL daemon service module to the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication HAL daemon service module; adding an interface adapted to the Android mobile communication framework module of the subsystem to the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a mobile communication method and device, a storage medium, and an electronic device. Background Art

[0002] With the increasing popularity of smart devices and the continuous improvement of network speeds, users are not only enjoying the convenience brought by the Internet, but also paying more attention to system security. Therefore, multi-system mobile communication devices have emerged. In a multi-system, the work system with higher security requirements and the daily life system can operate independently, meeting the security needs of work without hindering the free internet access needs of the daily life system.

[0003] Android accounts for over 80% of all smart devices and boasts the most comprehensive ecosystem. However, its security is inferior to that of Linux, which strictly controls user access rights. Therefore, to balance ecosystem and security, most multi-operating systems choose to integrate both Android and Linux. However, there is currently no mature solution for supporting Android mobile communication applications on Linux.

[0004] Regarding related technologies, there is no effective technical solution for how to support Android mobile communication applications on Linux systems. Summary of the Invention

[0005] The embodiments of the present invention provide a mobile communication method and device, a storage medium, and an electronic device to at least solve the problem in the related art of how to support Android mobile communication applications on a Linux system.

[0006] According to one embodiment of the present invention, a mobile communication method is provided, which is applied to a Linux system, wherein the Linux system includes: a main system and a subsystem, wherein the main system is a Linux system, and the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and the Android mobile communication hal daemon service module, including: when the main system is started, starting the mobile communication management service of the main system, and starting and running the subsystem and the Android mobile communication hal daemon service module in the main system; adding an interface adapted to the Android mobile communication hal daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; adding an interface adapted to the Android mobile communication framework module of the subsystem in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0007] Optionally, after starting the mobile communication management service of the main system, the method further includes: adding a conflict handling module in the mobile communication management service of the main system; processing the transfer and conflict of communication commands through the conflict handling module so that the mobile communication application of the subsystem can operate normally in the main system.

[0008] Optionally, the processing of the transfer and conflict of communication commands by the conflict handling module so that the mobile communication application of the subsystem can operate normally in the main system includes: processing the transfer and conflict of the communication commands between the main system and the subsystem by the conflict handling module so that the mobile communication status of the main system and the mobile communication status of the subsystem are kept synchronized.

[0009] Optionally, the permissions between the main system and the subsystem are processed by the conflict processing module to ensure that the permissions of the subsystem in the main system are normal.

[0010] Optionally, when an operation request corresponding to an Android mobile communication application is generated, the operation request is sent to the Android mobile communication hal daemon service module for processing; when the Android mobile communication hal daemon service module responds to the operation request and obtains a processing result, the processing result is reported to the Android mobile communication application through the Android mobile communication hal daemon service module, wherein the Android mobile communication application is an application in the subsystem.

[0011] According to another embodiment of the present invention, a mobile communication device is also provided, which is applied to a Linux system, and the Linux system includes: a main system and a subsystem, wherein the main system is a Linux system, and the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and the Android mobile communication hal daemon service module, including: a startup unit, which is used to start the mobile communication management service of the main system when the main system is started, and start and run the subsystem and the Android mobile communication hal daemon service module in the main system; a first processing unit, which is used to add an interface adapted to the Android mobile communication hal daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; a second processing unit, which is used to add an interface adapted to the Android mobile communication framework module of the subsystem in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0012] Optionally, the device also includes: an adding unit for adding a conflict handling module in the mobile communication management service of the main system; and a third processing unit for handling the transit and conflict of communication commands through the conflict handling module so that the mobile communication application of the subsystem can operate normally in the main system.

[0013] Optionally, the third processing unit is further used to process the transfer and conflict of the communication commands between the main system and the subsystem through the conflict processing module, so as to keep the mobile communication status of the main system and the mobile communication status of the subsystem synchronized.

[0014] According to another embodiment of the present invention, a computer-readable storage medium is provided, wherein the storage medium includes a stored program, wherein the program executes any one of the above mobile communication methods when running.

[0015] According to another embodiment of the present invention, an electronic device is provided, wherein the storage medium includes a stored program, wherein the program executes any one of the above mobile communication methods when running.

[0016] Through the present invention, when the main system is started, the mobile communication management service of the main system is started, and the subsystem and the Android mobile communication hal daemon service module are started and run in the main system; an interface adapted to the Android mobile communication hal daemon service module is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; an interface adapted to the Android mobile communication framework module of the subsystem is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module. The above technical solution solves the problems of supporting Android mobile communication applications on Linux systems in the related art. Through the above technical solution, when the main system (such as the Linux system) is started, the subsystem in the main system and the Android mobile communication hal daemon service module can be started, which can achieve the technical effect of enabling the mobile communication management service of the main system to communicate with the Android mobile communication hal daemon service module, and the mobile communication management service of the main system to communicate with the Android mobile communication framework module. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0018] Figure 1 is a hardware structure block diagram of a terminal according to an optional mobile communication method of an embodiment of the present invention;

[0019] Figure 2 is a flow chart of an optional mobile communication method according to an embodiment of the present invention;

[0020] Figure 3 is a schematic diagram of an optional method for supporting Android mobile communication applications on a Linux system according to an embodiment of the present invention;

[0021] Figure 4 This is a structural block diagram of an optional system for supporting Android mobile communication applications on a Linux system according to an embodiment of the present invention;

[0022] Figure 5 is a structural block diagram of an optional mobile communication device according to an embodiment of the present invention;

[0023] Figure 6This is another structural block diagram of an optional mobile communication device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The present invention will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0025] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0026] The method embodiments provided in the embodiments of the present application can be executed in a terminal, a computer terminal or a similar computing device. Taking running on a computer terminal as an example, Figure 1 FIG. 1 is a block diagram of the hardware structure of a terminal according to an optional mobile communication method of an embodiment of the present invention. Figure 1 As shown, the computer terminal 10 may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data. Optionally, the terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above terminal. Figure 1 More or fewer components than shown, or with Figure 1 Equivalent functions or comparisons shown Figure 1 Shown are different configurations with more functionality.

[0027] The memory 104 can be used to store computer programs, such as software programs and modules of application software, such as the computer program corresponding to the mobile communication method in the embodiment of the present invention. The processor 102 executes the computer program stored in the memory 104 to execute various functional applications and data processing, thereby implementing the above-mentioned method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories may be connected to the terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0028] The transmission device 106 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the communication provider of the terminal 10. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0029] In this embodiment, a method for operating on the above Figure 1 The mobile communication method of the terminal shown, Figure 2 is a flow chart of an optional mobile communication method according to an embodiment of the present invention, such as Figure 2 As shown, the method is applied to a Linux system, the Linux system including: a main system and a subsystem, wherein the main system is a Linux system, the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and an Android mobile communication HAL daemon service module. The method includes the following steps:

[0030] Step S202, when the main system is started, starting the mobile communication management service of the main system, and starting and running the subsystem and the Android mobile communication HAL daemon service module in the main system;

[0031] Step S204, adding an interface adapted to the Android mobile communication HAL daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication HAL daemon service module;

[0032] Step S206 , adding an interface adapted to the Android mobile communication framework module of the subsystem to the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0033] Through the present invention, when the main system is started, the mobile communication management service of the main system is started, and the subsystem and the Android mobile communication hal daemon service module are started and run in the main system; an interface adapted to the Android mobile communication hal daemon service module is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; an interface adapted to the Android mobile communication framework module of the subsystem is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module. The above technical solution solves the problems of how to support Android mobile communication applications on Linux systems in related technologies. Through the above technical solution, when the main system (such as the Linux system) is started, the subsystem in the main system and the Android mobile communication hal daemon service module can be started, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module, and the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0034] In an embodiment of the present invention, after the above-mentioned step S202, the following steps may also be included: after starting the mobile communication management service of the main system, the method may also include: adding a conflict handling module in the mobile communication management service of the main system; processing the transfer and conflict of communication commands through the conflict handling module, so that the mobile communication application of the subsystem can operate normally in the main system.

[0035] Optionally, the processing of the transfer and conflict of communication commands by the conflict handling module so that the mobile communication application of the subsystem can operate normally in the main system includes: processing the transfer and conflict of the communication commands between the main system and the subsystem by the conflict handling module so that the mobile communication status of the main system and the mobile communication status of the subsystem are kept synchronized.

[0036] In an embodiment of the present invention, the above method may further perform the following operations: processing the permissions between the main system and the subsystem by the conflict processing module, so that the permissions of the subsystem in the main system are normal.

[0037] Optionally, the above method may also include the following steps: when an operation request corresponding to an Android mobile communication application is generated, the operation request is sent to the Android mobile communication hal daemon service module for processing; when the Android mobile communication hal daemon service module responds to the operation request and obtains a processing result, the processing result is reported to the Android mobile communication application through the Android mobile communication hal daemon service module, wherein the Android mobile communication application is an application in the subsystem.

[0038] The mobile communication process is explained below with reference to an example, but is not intended to limit the technical solution of the embodiment of the present invention. The technical solution of the example of the present invention is as follows:

[0039] The embodiment of the present invention is a method for supporting Android mobile communication applications on a Linux system, including a main system and a subsystem. The specific steps are as follows:

[0040] The main system, namely the Linux system module, includes device management, permission management, communication management, service startup management, service startup management module and mobile communication management module related to the operation of Android mobile communication applications, Android mobile communication framework module, Android mobile communication hal daemon service module, etc.

[0041] The subsystem, that is, the Android system running in the main system Linux, is a module of the main system and supports the corresponding Android functions.

[0042] When the main system starts, its service management module starts the main system's mobile communication management service and starts the subsystem module and Android mobile communication HAL daemon service module as services, allowing them to run in the main system. An interface compatible with the Android mobile communication HAL daemon service module is added to the main system's mobile communication management service, enabling direct communication between the main system's mobile communication management service and the Android mobile communication HAL daemon service module. A new interface compatible with the subsystem's mobile communication framework is added to the main system's mobile communication management service, enabling direct communication between the main system's mobile communication management service and the subsystem's mobile communication framework, while maintaining the interface between the Android mobile communication application and the subsystem's mobile communication framework. A conflict handling mechanism is added to the main system's mobile communication management service to resolve possible mobile communication command conflicts between the subsystem and the main system. Through the subsystem's startup, the Android mobile communication HAL daemon service running, and the main system's mobile communication module's relaying and conflict resolution of communication commands, Android mobile communication applications can operate normally on the Linux system.

[0043] Through the embodiments of the present invention, by adopting the above technical solution, the Android mobile communication application can be allowed to run normally on the Linux system. Since the security of the Linux system is relatively high, the security of the Android mobile communication application is further improved.

[0044] Optionally, an embodiment of the present invention further provides a system applied to the above-mentioned method of supporting Android mobile communication applications on a Linux system. The system is a system for supporting Android mobile communication applications on a Linux system, and the system includes:

[0045] 1. Main system service management module, including:

[0046] (1) Service startup unit: Starts various services of the main system, such as the main system mobile communication management service, starts subsystem services in the main system, and Android mobile communication hal daemon service;

[0047] (2) Package management unit: used to manage the installation and uninstallation of various Linux application packages and the maintenance of their running status, including the management of Linux mobile communication applications;

[0048] 2. Main system communication management module, including:

[0049] (1) The main-subsystem mobile communication hal adaptation unit adds an adaptation to the inter-process communication mechanism of the Android mobile communication hal daemon service in the main system mobile communication management service, and uses this adaptation as the client and the Android mobile communication hal daemon service as the server; the mobile communication commands received by this hal adaptation unit can be directly sent to the Android mobile communication hal daemon service through this adaptation unit, and the command processing result message returned and the status message actively reported are forwarded to each mobile communication command receiving terminal;

[0050] (2) The main-subsystem mobile communication framework adapter unit adds an inter-process communication mechanism to the main system mobile communication management service and acts as a server to receive communication commands issued by the subsystem mobile communication framework and send the received commands to the main-subsystem mobile communication HAL adapter unit, which sends them to the Android mobile communication HAL daemon service; and dispatches the received command processing result message and active reporting status message to the subsystem mobile communication framework;

[0051] (3) The main-subsystem mobile communication conflict processing unit is used to handle the conflicting commands issued by the main system and the subsystem, so that the main system mobile communication status and the subsystem mobile communication status are kept synchronized, and at the same time, sensitive command permissions are uniformly controlled.

[0052] 3. Subsystem management module, including:

[0053] (1) Subsystem mobile communication framework adapter unit: used to cut off the mobile communication command on the subsystem side and send it directly to the Android mobile communication hal daemon service, and add an inter-process communication mechanism with the main-subsystem mobile communication framework adapter unit and act as a client to send the subsystem mobile communication command to the main-subsystem mobile communication framework adapter unit, receive the command processing result message and active reporting status message sent by the main-subsystem mobile communication framework adapter unit and send them to the Android mobile communication application.

[0054] (2) Subsystem application management unit: used to manage the installation and uninstallation of Android applications, including mobile communication applications, and maintain the running status.

[0055] The mobile communication method is explained below with reference to another example, but is not intended to limit the technical solution of the embodiment of the present invention. The technical solution of the example of the present invention is as follows:

[0056] The embodiment of the present invention is another method for supporting Android mobile communication applications on a Linux system. The specific steps are as follows:

[0057] Step 1: Start the subsystem as a module in the main system, and start the Android mobile communication HAL daemon service in the main system to ensure its normal operation and the required permissions.

[0058] Step 2: Start the main system mobile communication management service, which includes the main-subsystem mobile communication HAL adaptation unit, the main-subsystem mobile communication conflict handling unit, and the main-subsystem mobile communication framework adaptation unit, in the main system to ensure that it and the Android mobile communication HAL daemon service and the subsystem mobile communication framework adaptation unit inter-process communication service end operate normally;

[0059] Step 3: Start the subsystem service in the main system and ensure that the subsystem mobile communication framework adaptation unit and the subsystem application management unit are running normally;

[0060] Step 4: Install the Android mobile communication application in the subsystem. The operations such as calls, text messages, and Internet access performed through this mobile communication application, and the mobile communication commands related to the operations are transferred through -->Android mobile communication application-->subsystem mobile communication framework adaptation unit-->main-subsystem mobile communication framework adaptation unit-->main-subsystem mobile communication conflict handling unit-->main-subsystem mobile communication HAL adaptation unit, and sent to the Android mobile communication HAL daemon service for processing. The processed operation result message and the status message actively reported by the Android mobile communication HAL daemon service are reported to the Android mobile communication application through the opposite path, thereby realizing the Linux system's support for the corresponding mobile communication functions of calls, text messages, and Internet access of the Android mobile communication application.

[0061] It should be noted that in the multi-system fusion of Linux and Android, by adding core modules such as master-subsystem adaptation and conflict handling, the Android mobile communication signaling is transferred to the Linux system; and after the Android mobile communication daemon is adapted and run in the Linux system, the mobile communication signaling issued by Linux is uniformly handed over to the Android mobile communication daemon for processing, ensuring the normal operation of the respective mobile communication functions of Linux and Android. Therefore, in the multi-system fusion of Linux and Android, the communication signaling transfer method is implemented by adding master-subsystem adaptation to support Android mobile communication applications on the Linux system. At the same time, other peripheral applications of Android, such as Bluetooth, NFC, GPS, fingerprint, audio, camera, etc., can all be implemented by adding system adaptation and communication signaling transfer through the same or similar methods to support corresponding Android applications on the Linux system. The embodiments of the present invention do not impose any restrictions on this.

[0062] Through the embodiments of the present invention, Android mobile communication applications are run on the Linux system, which not only ensures the security of Linux but also integrates the usability of Android. At the same time, it expands the application ecology of Linux, reduces the cost of expanding the Linux system ecology, improves the usability of the Linux system, and enhances the user experience of the Linux system.

[0063] The following example illustrates how to support Android mobile communication applications on a Linux system, but does not limit the technical solution of the embodiment of the present invention. The technical solution of the example of the present invention is as follows:

[0064] Figure 3FIG is a schematic diagram of an optional method for supporting Android mobile communication applications on a Linux system according to an embodiment of the present invention, such as Figure 3 As shown:

[0065] Support Android mobile communication applications on Linux systems. Its mobile communication command flow is as follows: Figure 3 As shown in the direction of the arrow, when the Android mobile communication application initiates a text message, phone call or mobile data Internet access request, the mobile communication application operation command passes through the Android mobile communication application <-----> subsystem mobile communication framework adaptation unit <----> main-subsystem mobile communication framework adaptation unit <----> main-subsystem mobile communication conflict handling unit <-----> main-subsystem mobile communication HAL adaptation unit <----> Android mobile communication HAL daemon service, forming the establishment of a mobile communication command flow path, which can realize the timely reporting, distribution and processing of mobile communication command request messages, processing result messages and actively reported status messages.

[0066] By establishing the mobile communication command flow path and dispatching and processing the corresponding messages, the normal functioning of the Android mobile communication application on the Linux system is guaranteed.

[0067] Optionally, an embodiment of the present invention further provides another system for the method of supporting Android mobile communication applications on a Linux system. The system is another system for supporting Android mobile communication applications on a Linux system, such as Figure 4 As shown, the system includes:

[0068] E1, the main system service management module, is used to manage the startup, termination, and restart of various system services of the main system; as well as the installation, uninstallation, and operation status maintenance of various Linux application packages of the main system;

[0069] E2, the main system communication management module, is used to receive mobile communication commands issued by the main system Linux mobile communication application and the subsystem mobile communication framework, as well as timely reporting, dispatching and processing of messages on processing results and proactive status reporting from the Android mobile communication HAL daemon service; processing conflicting commands issued by the main system Linux mobile communication application and the subsystem mobile communication framework, and synchronizing the mobile communication status of the main and subsystems.

[0070] E3, the subsystem management module, is used to manage the running status of each subsystem service and the installation, uninstallation and running status maintenance of each Android application in the subsystem.

[0071] Corresponding to step E1, the method further includes:

[0072] E101, service startup unit, is used to start the main services of the main system, including starting the main system mobile communication management service, main system package management service, subsystem service, and Android mobile communication HAL daemon service;

[0073] E102, the package management unit, is used to manage the installation and uninstallation of various Linux applications in the main system and maintain their running status.

[0074] Corresponding to step E2, the method further includes:

[0075] E201, the main-subsystem mobile communication HAL adaptation unit, is used to establish a mobile communication command communication channel between the main system mobile communication management service and the Android mobile communication HAL daemon service, and realize the communication between the Android mobile communication HAL daemon service and the main system mobile communication management service;

[0076] E202, a main-subsystem mobile communication framework adaptation unit, is used to receive communication commands issued by the subsystem mobile communication framework adaptation unit and forward processing result messages and actively reported status messages;

[0077] E203, the main-subsystem mobile communication conflict processing unit, is used to handle the conflicting commands issued by the main system Linux mobile communication application and the subsystem mobile communication framework adaptation unit and to synchronize the communication status of the main and subsystems;

[0078] Corresponding to step E3, the method further includes:

[0079] E301, the subsystem mobile communication framework adapter unit, is used to cut off the communication with the Android mobile communication HAL daemon service and communicate with the main-subsystem mobile communication framework adapter unit, transfer the mobile communication command issued by the subsystem mobile communication framework adapter unit to the main-subsystem mobile communication framework adapter unit, and receive the processing result message and active reporting message from the main-subsystem mobile communication framework adapter unit;

[0080] E302, a subsystem application management unit, is used to manage the installation, uninstallation and running status maintenance of various applications in the subsystem, including mobile communication applications.

[0081] In summary, in this embodiment of the present invention, the Android mobile communication application's runtime environment is placed within the subsystem's application management unit, and the Android mobile communication HAL daemon service is run within the Linux main system. When communication commands corresponding to calls, text messages, and mobile data requested by the Android mobile communication application are forwarded via the subsystem's mobile communication framework adapter unit to the master-subsystem mobile communication framework adapter unit within the main system's mobile communication management service, they undergo master-subsystem mobile communication conflict resolution and are then forwarded by the master-subsystem HAL adapter unit. Ultimately, the commands are sent to the Android mobile communication HAL daemon service for processing, and the processing result message is dispatched back to the Android mobile communication application. Simultaneously, the Android mobile communication HAL daemon service's proactive reporting message is also dispatched back to the Android mobile communication application. The master-subsystem mobile communication conflict resolution unit within the main system's mobile communication management service processes conflicting commands issued by the main and subsystems and synchronizes their communication status. By providing the Android mobile communication application runtime environment and establishing a path for issuing communication commands, processing result messages, and proactive reporting messages, support for Android mobile communication applications on Linux systems is achieved.

[0082] It should be noted that the above method in the embodiment of the present invention can be used for multi-system PCs, mobile devices, pads, smart devices, etc. with Linux systems, which not only expands the application ecology of the Linux system, improves usability, but also enhances user experience.

[0083] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0084] This embodiment also provides a mobile communication device for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented using software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0085] Figure 5 is a structural block diagram of an optional mobile communication device according to an embodiment of the present invention, such as Figure 5 As shown, the mobile communication device can be applied to a Linux system, the Linux system including: a main system and a subsystem, wherein the main system is a Linux system, the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and the Android mobile communication hal daemon service module. The device includes:

[0086] The starting unit 502 is used to start the mobile communication management service of the main system when the main system is started, and to start and run the subsystem and the Android mobile communication hal daemon service module in the main system; the first processing unit 504 is used to add an interface adapted to the Android mobile communication hal daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; the second processing unit 506 is used to add an interface adapted to the Android mobile communication framework module of the subsystem in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0087] Through the present invention, when the main system is started, the mobile communication management service of the main system is started, and the subsystem and the Android mobile communication hal daemon service module are started and run in the main system; an interface adapted to the Android mobile communication hal daemon service module is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; an interface adapted to the Android mobile communication framework module of the subsystem is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module. The above technical solution solves the problems of how to support Android mobile communication applications on Linux systems in related technologies. Through the above technical solution, when the main system (such as the Linux system) is started, the subsystem in the main system and the Android mobile communication hal daemon service module can be started, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module, and the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0088] In the embodiment of the present invention, Figure 6 As shown, the device also includes:

[0089] An adding unit 508 is used to add a conflict handling module to the mobile communication management service of the main system; a third processing unit 510 is used to handle the transfer and conflict of communication commands through the conflict handling module so that the mobile communication application of the subsystem can operate normally in the main system.

[0090] In the embodiment of the present invention, Figure 6 As shown, the third processing unit 510 is further used to process the transfer and conflict of the communication commands between the main system and the subsystem through the conflict processing module, so as to keep the mobile communication status of the main system and the mobile communication status of the subsystem synchronized.

[0091] In the embodiment of the present invention, Figure 6 As shown, the device further includes: a fourth processing unit 512, configured to process the permissions between the main system and the subsystem through the conflict processing module, so as to make the permissions of the subsystem in the main system normal.

[0092] In the embodiment of the present invention, Figure 6 As shown, the device also includes: a sending unit 514, which is used to send the operation request to the Android mobile communication hal daemon service module for processing when an operation request corresponding to the Android mobile communication application is generated; a reporting unit, which is used to report the processing result to the Android mobile communication application through the Android mobile communication hal daemon service module when the Android mobile communication hal daemon service module responds to the operation request and obtains the processing result, wherein the Android mobile communication application is an application in the subsystem.

[0093] An embodiment of the present invention further provides a computer-readable storage medium, which includes a stored program, wherein the program executes any of the above methods when running.

[0094] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0095] S1, when the main system is started, starting the mobile communication management service of the main system, and starting and running the subsystem and the Android mobile communication HAL daemon service module in the main system;

[0096] S2, adding an interface adapted to the Android mobile communication HAL daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication HAL daemon service module;

[0097] S3, adding an interface adapted to the Android mobile communication framework module of the subsystem to the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0098] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0099] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0100] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0101] Optionally, in this embodiment, the processor may be configured to execute the following steps through a computer program:

[0102] S1, when the main system is started, starting the mobile communication management service of the main system, and starting and running the subsystem and the Android mobile communication HAL daemon service module in the main system;

[0103] S2, adding an interface adapted to the Android mobile communication HAL daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication HAL daemon service module;

[0104] S3, adding an interface adapted to the Android mobile communication framework module of the subsystem to the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module.

[0105] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0106] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, centralized on a single computing device, or distributed across a network of multiple computing devices. Alternatively, they can be implemented using program code executable by a computing device, which can then be stored in a storage device and executed by the computing device. In some cases, the steps shown or described can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0107] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A mobile communication method, characterized in that: Applied to a Linux system, the Linux system includes: a main system and a subsystem, wherein the main system is a Linux system, the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and the Android mobile communication HAL daemon service module, including: When the main system is started, the mobile communication management service of the main system is started, and the subsystem and the Android mobile communication hal daemon service module are started and run in the main system; Add an interface adapted to the Android mobile communication hal daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication hal daemon service module; An interface adapted to the Android mobile communication framework module of the subsystem is added to the mobile communication management service of the main system so that the mobile communication management service of the main system communicates with the Android mobile communication framework module, wherein: When an operation request corresponding to an Android mobile communication application is generated, the operation request is sent to the Android mobile communication hal daemon service module for processing; When the Android mobile communication hal daemon service module responds to the operation request and obtains a processing result, the processing result is reported to the Android mobile communication application through the Android mobile communication hal daemon service module, wherein the Android mobile communication application is an application in the subsystem.

2. The method according to claim 1, characterized in that After starting the mobile communication management service of the main system, the method further includes: Adding a conflict handling module to the mobile communication management service of the main system; The conflict handling module handles the transfer and conflict of communication commands, so that the mobile communication application of the subsystem can run normally in the main system.

3. The method according to claim 2, characterized in that The processing of the transfer and conflict of communication commands by the conflict processing module so as to enable the mobile communication application of the subsystem to operate normally in the main system includes: The conflict handling module handles the transfer and conflict of the communication commands between the main system and the subsystem, so that the mobile communication state of the main system and the mobile communication state of the subsystem are kept synchronized.

4. The method according to claim 2, characterized in that The method further comprises: The conflict handling module handles the permissions between the main system and the subsystem, so that the permissions of the subsystem in the main system are normal.

5. A mobile communication device, characterized in that: Applied to a Linux system, the Linux system includes: a main system and a subsystem, wherein the main system is a Linux system, the subsystem is an Android system running in the main system, and the main system includes at least one of the following: the subsystem and the Android mobile communication HAL daemon service module, including: A starting unit, configured to start the mobile communication management service of the main system when the main system is started, and start and run the subsystem and the Android mobile communication HAL daemon service module in the main system; A first processing unit is configured to add an interface adapted to the Android mobile communication HAL daemon service module in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication HAL daemon service module; The second processing unit is configured to add an interface adapted to the Android mobile communication framework module of the subsystem in the mobile communication management service of the main system, so that the mobile communication management service of the main system communicates with the Android mobile communication framework module, wherein: The device further includes: a sending unit for sending the operation request to the Android mobile communication hal daemon service module for processing when an operation request corresponding to the Android mobile communication application is generated; When the Android mobile communication hal daemon service module responds to the operation request and obtains a processing result, the processing result is reported to the Android mobile communication application through the Android mobile communication hal daemon service module, wherein the Android mobile communication application is an application in the subsystem.

6. The device according to claim 5, characterized in that The device further comprises: an adding unit, configured to add a conflict handling module to the mobile communication management service of the main system; The third processing unit is configured to process the transfer and conflict of communication commands through the conflict processing module, so as to enable the mobile communication application of the subsystem to operate normally in the main system.

7. The device according to claim 6, characterized in that The third processing unit is further configured to process the transfer and conflict of the communication commands between the main system and the subsystem through the conflict processing module, so as to synchronize the mobile communication state of the main system and the mobile communication state of the subsystem.

8. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 4 when executed.

9. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 4.

Images