TWI452517B - Software execution method and electronic apparatus using the same - Google Patents

Description

Software execution method and electronic device thereof

The present invention relates to a software execution method and an electronic device thereof, and more particularly to a software execution method and an electronic device thereof in a dual operation system.

In a dual operating system with different libraries, if the software of another operating system is to be executed in one of the operating systems, the software must be substantially modified correspondingly to make the The operating system of one can smoothly run the software of the other operating system.

For example, the current Android operating system has been widely used in many fields, including smart phones, smart TVs and so on. In the TV field, there have been many Linux-based TV software solutions before the Android operating system appeared. The Android operating system is based on the Linux operating system, but the corresponding changes have been made, especially the C library. The Android operating system does not use the glibc library as its C library, but uses the Bionic Libc library developed by Google itself. Its file building tool set (Toolchain) is also based on the Bionic Libc library instead of the glibc library.

This technical feature has caused many existing multimedia applications to be easily embedded in the Android operating system, and needs to be greatly modified, including using a communication interface such as JNI (Java Native Interface) to contact the Java program and the underlying C function. Libraries, thus increasing the difficulty of using existing multimedia applications.

The present invention provides a software execution method capable of launching an existing application library-based application in a dual operating system, and basically can run directly without modifying the applications.

The present invention provides an electronic device having a dual operating system for performing the aforementioned software execution method.

The present invention provides a software execution method comprising the following steps. Start a kernel of the operating system (Kernel). The operating system core is shared by a first operating system and a second operating system. Load one or more drive modules to the operating system core. At the root of one of the first and second operating systems, execution of the one of the first and second operating systems begins. A program is called to invoke the root directory of the other of the first and second operating systems. At the root of the other of the first and second operating systems, execution of the other of the first and second operating systems begins.

In an embodiment of the invention, the type of the operating system core described above is a core type of the first operating system.

In an embodiment of the present invention, the file directories of the first and second operating systems are respectively stored in the root directories of the first and second operating systems.

In an embodiment of the present invention, the step of starting to execute the one of the first and second operating systems includes utilizing at least one of the one or more driving modules and the first and second operating systems The library of the ones to start executing one of the first and second operating systems to the plurality of applications.

In an embodiment of the invention, at least one of the one or more drive modules is dedicated to the one of the first and second operating systems, or shared by the first and second operating systems.

In an embodiment of the invention, the step of initiating execution of the one of the first and second operating systems is performed before, after or simultaneously with the step of establishing the program.

In an embodiment of the present invention, the step of starting to execute the one of the first and second operating systems is earlier, at the same time, or later than starting the execution of the other of the first and second operating systems. The steps.

In an embodiment of the present invention, the step of starting to execute the other of the first and second operating systems includes utilizing a library of at least one of the one or more driving modules and the second operating system. Start executing one of the other of the first and second operating systems.

In an embodiment of the present invention, at least one of the one or more drive modules is dedicated to the other of the first and second operating systems, or by the first and second operating systems. Share.

In an embodiment of the invention, the first operating system is a Linux operating system.

In an embodiment of the invention, the second operating system is an Android operating system.

In an embodiment of the invention, the one or more driving modules include one or more first driving modules. At least one of the one or more first driving modules is used by the first operating system and is selected from at least one of the following driving modules: an audio driving module, a video driving module, and a drawing driving mode. Group and remote control drive module.

In an embodiment of the invention, the one or more driving modules further include one or more second driving modules. At least one of the one or more second driving modules is used by the second operating system, and the one or more second driving modules are selected from at least one of the following driving modules: a flash memory driving mode The group, the universal serial bus driver module, the driving module of the Binder Inter-Process Communication, the Ethernet driver module and the power management driver module.

In an embodiment of the invention, at least one of the one or more of the plurality of drive modules is used by the first or second operating system alone.

In an embodiment of the invention, at least one of the one or more of the plurality of drive modules is used by the first and second operating systems.

In an embodiment of the invention, the step of invoking the root directory of the other of the first and second operating systems is performed by a chroot function.

In an embodiment of the invention, the software execution method further includes executing an application management program. The application management program uniformly manages the execution of the application of the first operating system and the second operating system.

In an embodiment of the present invention, the application management program further controls an application environment to switch between an application of the first operating system and an application of the second operating system.

The present invention provides an electronic device having a dual operating system, including a memory device and a processor. The memory device stores a plurality of instructions. The plurality of instructions are used to execute the aforementioned software execution method. The processor accesses the memory device to execute the plurality of instructions.

Based on the above, in an exemplary embodiment of the present invention, the applications of the first and second operating systems can run simultaneously, and basically do not need to modify the application of any operating system.

The above described features and advantages of the present invention will be more apparent from the following description.

FIG. 1 is a schematic structural diagram of a dual operation system according to an embodiment of the present invention. Referring to FIG. 1 , the dual operating system 100 of the present embodiment includes a first operating system 110 and a second operating system 120 . Here, the first operating system 110 is, for example, a Linux operating system; the second operating system 120 is, for example, an Android operating system, but the present invention is not limited thereto.

In this embodiment, the first operating system 110 and the second operating system 120 jointly provide an application environment for the multimedia application running based on the Linux operating system and the Android operating system. In the following exemplary embodiment, the multimedia application is exemplified by the application of the television and the application of the Android operating system, but the invention is not limited thereto. The multimedia application can also be a multimedia application executable on any electronic device having a dual operating system such as a tablet computer, a notebook computer, a smart phone, or the like.

For the first operating system 110, the system architecture includes a TV application, a middleware, a platform, a device driver, a GLIBC/uClibc library, and a Linux job shared with the second operating system 120. System core 112.

In terms of the second operating system 120, the system architecture includes an Android operating system application, an application framework, various libraries and an Android runtime, an Bionic Libc library, and A Linux operating system core 112 shared by an operating system 110. The system architecture of the first operating system 110 and the second operating system 120 is for illustrative purposes only, and the present invention is not limited thereto.

When the dual operating system 100 is ready, its application is running in a multi-process manner. Therefore, the system architecture of this embodiment may further include an application management unit (not shown) for coordinating the application of the Android operating system. As well as the work of the TV application, the work of the application management unit includes but is not limited to resource management and application scene switching. The resource management work includes the management of resources such as remote controls, audio/video decoders, screens, and hardware graphics layers. The work of the application scenario switching includes switching from the application environment of the Android operating system to the application environment of the TV software, or switching from the application environment of the TV software to the application environment of the Android operating system. Therefore, the application management unit of the embodiment executes an application management program for uniformly managing the execution of the applications of the first operating system 110 and the second operating system 120. Moreover, the application management unit further controls the application environment of the system to switch between the application of the first operating system 110 and the application of the second operating system 120 by using the application management program.

2 is a flow chart showing the steps of a software execution method according to an embodiment of the present invention. Referring to FIG. 1 to FIG. 2, in step S200, the software execution method first starts a work system core. The operating system core is shared by the first operating system 110 and a second operating system 120. Preferably, the operating system core 112 is designed to be the core type of the first operating system 110, and in this embodiment also It is the Linux operating system core 112.

Next, in step S202, a plurality of drive modules are loaded to the operating system core 112 (ie, the Linux operating system core 112). In this embodiment, the driver module loaded to the Linux operating system core 112 may include, for example, a first driver module 114 required to drive the multimedia function, and a second driver module 124 required to drive the system management function.

More specifically, the first driving module 114 can be used by the first operating system 110, and at least includes an audio driving module, a video driving module, a drawing driving module, and a remote control driving module. One of the modules is at most one to provide an electronic device to perform multimedia functions. The second driving module 124 can be used by the second operating system 120, and includes at least a flash memory driving module, a universal serial bus driving module, and a Binder Inter-Process Communication. At most one of the drive modules, the Ethernet drive module and the power management drive module, etc., so that the electronic device system can operate smoothly. The driving modules included in the first driving module 114 and the second driving module 124 are for illustrative purposes only, and the present invention is not limited thereto. It should be noted that a part of the driving modules of the first driving module 114 is dedicated to the first operating system 110, and other driving modules can be shared by the first and second operating systems 110 and 120. A portion of the drive modules of the second drive module 124 are dedicated to the second operating system 120, and other portions of the drive modules are shared by the first and second operating systems 110, 120.

Then, in step S204, in the root directory of the first operating system 110, the software execution method starts to execute the first job by using the first driving module 114 and the first operating system 110, such as the GLIBC/uClibc library. The application in system 110. For example, if the television broadcast sound and the display image are to be driven, in step S204, the software execution method can be performed by using the audio driving module and the video driving module of the first driving module 114, and the GLIBC/uClibc library. An application for audio and video in the first operating system 110. That is, the TV application in the Linux operating system is executed. Therefore, after step S204, the software execution method may continue to run the application in the first operating system 110, as in step S206. That is, the TV application can continue to run.

Then, in order to be able to run the application of the second operating system 120 at the same time, in step S208, the software execution method creates a program, and calls the root directory of the second operating system 120 through the program and, for example, the chroot function. Here, the root files of the first and second operating systems 110 and 120 are respectively stored (preferably stored when the system is shipped), and the file structures of the first and second operating systems 110 and 120 are used to make the software. The execution method can smoothly execute the corresponding file function when calling the root directories of the first and second operating systems 110 and 120 through the chroot function. In this so-called file architecture, for example, an executable program, a dynamic database, a script program, a picture, an audio file, a user profile, and a system default parameter (default parameters) required to start the first operation system or the second operation system may be included. and many more.

It is to be noted that, in the present embodiment, the step S204 of starting the execution of the first operating system 110 is performed before the step S208 of establishing the calling program, but the present invention is not limited thereto. In another embodiment, the step S204 of starting execution of the first operating system 110 may also be performed after or at the same time as step S208 of establishing the calling program.

Next, in step S210, in the root directory of the second operating system 120, the software execution method starts to execute the second operating system by using the second driving module 124 and the second operating system 120, such as the Bionic Libc library. 120 apps. For example, if the overall operation of the dual operating system 100 is to be energy-saving, in step S210, the software execution method may utilize the power management driving module of the second driving module 124 and the Bionic Libc library to execute the first An application for power management in the second operating system 110. That is, the application in the Android operating system is executed. Thereafter, in step S212, the software execution method may continue to run the application in the second operating system 120. It is worth mentioning that, at the same time, the software execution method can also continuously run the application in the first operating system 110, that is, step S206.

Therefore, in the present embodiment, the applications of the first and second operating systems 110, 120 can run simultaneously, and basically do not need to modify the application of any operating system. Further, the execution of the applications of the first operating system 110 and the second operating system 120 can be uniformly managed in conjunction with the application management program.

It is to be noted that, in the present embodiment, the step S204 of starting the execution of the first operating system 110 is earlier than the step S210 of starting the execution of the second operating system 120, but the present invention is not limited thereto. In other embodiments, step S204 of starting execution of the first operating system 110 may also be performed simultaneously or later than step S210 of the second operating system 120. In practical applications, the order of execution of the first operating system 110 and the second operating system 120 may be determined according to design requirements or even according to the user. In addition, neither the application of the first operating system (ie, the application of the television) nor the application of the second operating system is required to be executed, but may be determined according to the use or application requirements. In addition, during the execution, the application of the first or second operating system can be dynamically selected to be in a sleep state and stopped to be executed as needed.

3 is a flow chart showing the steps of a software execution method according to another embodiment of the present invention. Referring to FIG. 1 to FIG. 3, the software execution method of this embodiment is similar to the software execution method of FIG. 2, but the main difference between the two is, for example, the steps of starting the execution of the first operating system 110 and starting the execution of the second operating system. The sequence of steps of 120.

In detail, in this embodiment, after the software execution method loads the plurality of driver modules to the Linux operating system core 112 (that is, after executing in step S302), first, step S304 is started, that is, in the second operating system 120. In the root directory, the second driver module 124 and the second operating system 120, such as the Bionic Libc library, are used to start executing the application in the second operating system 120. This step is similar to step S210 and will not be described again here.

Next, in step S306, the software execution method may continue to run the application in the second operating system 120. That is, the Android operating system application is continuously running.

On the other hand, in order to be able to run the application of the first operating system 110, in step S308, the software execution method creates a program, and calls the root directory of the first operating system 110 through the program and the chroot function.

It is to be noted that, in the present embodiment, the step S304 of starting the execution of the second operating system 110 is performed before the step S308 of establishing the calling program, but the present invention is not limited thereto. In another embodiment, the step S304 of starting execution of the second operating system 120 may also be performed after or at the same time as step S308 of establishing the calling program.

Then, in step S310, in the root directory of the first operating system 110, the software execution method starts to execute the first job by using the first driving module 114 and the first operating system 110, such as the GLIBC/uClibc library. The application in system 110. This step is similar to step S204 and will not be described again here. Up to this point, in the present embodiment, the step S310 of starting the execution of the first operating system 110 is later than the step S304 of starting the execution of the second operating system 120.

Then, after step S312, the software execution method can continuously run the application in the first operating system 110. It is worth mentioning that, at the same time, the software execution method can continuously run the application in the second operating system 120, that is, step S306.

4 is a schematic diagram of an electronic device with a dual operating system in accordance with an embodiment of the present invention. Referring to FIG. 4, the electronic device 400 of the present embodiment is at least adapted to execute the software execution method of FIG. 2 or FIG. 3 described above, and includes a memory device 410 and a processor 420. The memory device 410 stores a plurality of instructions for executing the software execution method of FIG. 2 or FIG. 3 described above. Processor 420 accesses memory device 410 to execute the instructions. The electronic device 400 can be, for example but not limited to, any electronic device having a dual operating system such as a tablet computer, a notebook computer, a smart phone, or the like.

In summary, in an exemplary embodiment of the present invention, the applications of the first and second operating systems can be run simultaneously, and no matter whether the application or the execution of one of the two is executed first, basically no modification is required. An application for any operating system. In addition, the order of the steps for invoking the root program does not affect the simultaneous operation of the applications of the first and second operating systems. Further, the application management program can be used to uniformly manage the execution of the application of the first operating system and the second operating system.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the invention, and any one of ordinary skill in the art can make some modifications and refinements without departing from the spirit and scope of the invention. The scope of the invention is defined by the scope of the appended claims.

100‧‧‧Double operating system

110‧‧‧First operating system

112‧‧‧Linux operating system core

114‧‧‧First drive module

120‧‧‧Second operating system

124‧‧‧Second drive module

S200, S202, S204, S206, S208, S210, S212, S300, S302, S304, S306, S308, S310, S312‧‧‧ steps of the software execution method

400‧‧‧Electronic devices

410‧‧‧ memory device

420‧‧‧ processor

FIG. 1 is a schematic structural diagram of a dual operation system according to an embodiment of the present invention.

2 is a flow chart showing the steps of a software execution method according to an embodiment of the present invention.

3 is a flow chart showing the steps of a software execution method according to another embodiment of the present invention.

4 is a schematic diagram of an electronic device having a dual operating system in accordance with an embodiment of the present invention.

100. . . Dual operating system

110. . . First operating system

112. . . Linux operating system core

114. . . First drive module

120. . . Second operating system

124. . . Second drive module

Claims (19)

A software execution method includes: starting a working system core, wherein the operating system core is shared by a first operating system and a second operating system; loading one or more driving modules to the operating system core; Starting in the root directory of one of the first and second operating systems, starting the execution of the one of the first and second operating systems; establishing a program to invoke the other of the first and second operating systems a root directory; and in the root directory of the other of the first and second operating systems, starting execution of the other of the first and second operating systems. The software execution method of claim 1, wherein the core type of the operating system is a core type of the first operating system. The software execution method of claim 1, wherein the file structures of the first and second operating systems are respectively stored in the root directories of the first and second operating systems respectively. The software execution method of claim 1, wherein the step of executing the one of the first and second operating systems comprises: utilizing at least one of the one or more driving modules and the first And a library of the one of the second operating systems to start executing one of the first and second operating systems to the plurality of applications. The software execution method of claim 4, wherein the at least one of the one or more drive modules is the first and second The person in the system is dedicated or shared by the first and second operating systems. The software execution method of claim 1, wherein the step of starting execution of the one of the first and second operating systems is performed before, after or simultaneously with establishing the program. The software execution method of claim 1, wherein the step of executing the one of the first and second operating systems is earlier, at the same time, or later than starting the execution of the first and second operating systems. The step of the other one. The software execution method of claim 1, wherein the step of starting the execution of the other one of the first and second operating systems comprises: utilizing at least one of the one or more driving modules and the The library of the second operating system begins executing one of the other of the first and second operating systems. The software execution method of claim 8, wherein the at least one of the one or more drive modules is dedicated to the other of the first and second operating systems, or by the first It is shared with the second operating system. The software execution method of claim 2, wherein the first operating system is a Linux operating system. The software execution method of claim 10, wherein the second operating system is an Android operating system. The software execution method as described in claim 10, The one or more driving modules include one or more first driving modules, and at least one of the one or more first driving modules is used by the first operating system, and is selected from the following driving At least one of the modules: an audio drive module, a video drive module, a graphics driver module, and a remote control driver module. The software execution method of claim 11, wherein the one or more driving modules further comprise one or more second driving modules, and at least one of the one or more second driving modules is The second operating system is used in execution, and the one or more second driving modules are selected from at least one of the following driving modules: a flash memory driving module, a universal serial bus driving module, and a binding program. The communication module of the communication pipe, the Ethernet drive module and the power management drive module. The software execution method of claim 1, wherein at least one of the one or more drive modules is used by the first or second operating system alone. The software execution method of claim 1, wherein at least one of the one or more drive modules is used by the first and second operating systems. The software execution method of claim 11, wherein the step of calling the root directory of the other one of the first and second operating systems is performed by a chroot function. The software execution method as described in claim 1, further comprising: executing an application management program to uniformly manage the first operating system Execution with the application of the second operating system. The software execution method of claim 17, wherein the application management program further controls an application environment to switch between an application of the first operating system and an application of the second operating system. An electronic device having a dual operating system, comprising: a memory device storing a plurality of instructions, wherein the plurality of instructions are used to execute a software execution method according to claim 1; and a processor The memory device is fetched to execute the plurality of instructions.