WO2017059724A1

WO2017059724A1 - Operating system starting method and device

Info

Publication number: WO2017059724A1
Application number: PCT/CN2016/091046
Authority: WO
Inventors: 张耀东; 何志强
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-10-09
Filing date: 2016-07-22
Publication date: 2017-04-13
Also published as: CN106569842A

Abstract

An operating system starting method and device, comprising: compiling a first operating system gateway platform based on a first kernel, wherein the first kernel supports a code running a second operating system on the basis of a first operating system; transplanting an LXC container into the first operating system gateway platform, and establishing a component for running the starting of the second operating system, wherein the LXC container is used for managing the first operating system gateway platform and the second operating system; and triggering the starting of the second operating system in the component via the LXC container. The embodiments of the present invention achieve the simultaneous starting of two operating systems on a gateway platform, and achieve the effect of fusing a function of a gateway platform operating system and an intelligent service of the other operating system, without adding hardware costs.

Description

Operating system startup method and device

Technical field

This document relates to, but is not limited to, the field of computers, and in particular, to a method and apparatus for starting an operating system.

Background technique

In the past, telecom operators mainly focused on improving access bandwidth and penetration rate (bandwidth monthly traffic and duration). With the development of the Internet, especially the mobile Internet and Internet application services (Over The Top, referred to as OTT) The development of the broadband operation of operators has shifted from the competition of broadband access to the competition of broadband content.

In order to cope with competition, operators need to deeply understand this change, and consider the three layers of services, access, and terminals to establish a "cloud-pipe-end" system architecture. The "end", that is, the home gateway, is operated. The merchants extend their tentacles into the natural entry point of each user's family, combining the three aspects of “cloud”, intelligent gateway, and ubiquitous access to expand the boundaries of the home network. For this reason, telecom operators have proposed Android-based ( Android) operating system's intelligent gateway related requirements, that is, the gateway must meet the basic gateway functions, but also support the current mainstream Android operating system platform. However, the gateway platform in the related art can only start one operating system at a time, such as the Android operating system or Apple's mobile operating system (IOS operating system), which is difficult to meet the above requirements.

In view of the above problems in the related art, there is currently no effective solution.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a method and a device for starting an operating system, which can implement the gateway platform to simultaneously start two operating systems.

According to an aspect of the embodiments of the present invention, a method for starting an operating system is provided, including: compiling a first operating system gateway platform based on a first kernel, wherein the first kernel is configured by using the first operating system gateway platform The base supports running the code of the second operating system; porting the LXC container to And configuring, in the first operating system gateway platform, a component for running the second operating system, where the LXC container is configured to manage the first operating system gateway platform and the second operating system; The second operating system is triggered to be launched in the component by the LXC container.

Optionally, in the porting the LXC container to the first operating system gateway platform, the booting method further includes: installing the second operating system to the first operating system by using a predetermined rule based on the LXC container In the specified system partition, wherein the specified system partition is a system partition other than the system partition on which the first operating system gateway platform is installed.

Optionally, the component includes: an interaction channel between the first operating system gateway platform and the second operating system, and the establishing, for running, starting the component of the second operating system includes: at the first Establishing a first proxy process of the second operating system in an operating system gateway platform; designing a second proxy process of the first operating system gateway platform in the second operating system; wherein the first proxy process and The second proxy process separately manages the second operating system and the first operating system gateway platform through an interaction channel, so as to implement and start the second operating system.

Optionally, the component further includes: a resource restriction policy and a management allocation policy, where the method further includes: establishing the resource restriction policy and the management allocation policy in the first operating system gateway platform, where The resource restriction policy and the management allocation policy are used to block network functions of the first operating system in the second operating system gateway platform.

Optionally, the triggering, by the LXC container, the starting of the second operating system in the component comprises: triggering a preset script of the first operating system gateway platform to start after starting the first operating system The LXC container; the LXC container that invokes the startup initiates the first operating system through the interaction channel.

Optionally, after the triggering, by the LXC container, that the second operating system is started in the component, the method further includes: upgrading the first operating system and/or the specified command by receiving the specified command a device environment required by the second operating system; loading network parameter information, configuring network parameters required to upgrade the first operating system and/or the second operating system; separately receiving and executing the first Upgrading the first operating system and/or the second operating system by a first command of the operating system and/or a second command for upgrading the second operating system.

Optionally, after the triggering, by the LXC container, that the second operating system is started in the component, the starting method further includes: setting up a remote upgrade of the first operating system by using a network management system And/or a device environment required by the second operating system; loading network parameter information, configuring network parameters required to upgrade the first operating system and/or the second operating system; performing After the third command of the first operating system, verifying the second operating system; when the verification fails, receiving a fourth command for indicating the second operating system in the upgraded cache area, The second operating system is upgraded.

Optionally, the verifying the second operating system includes: downloading the second operating system to be upgraded to a buffer area; and verifying the second operating system in the buffer area.

Optionally, the first operating system is a Linux system, and the second operating system is an android system.

According to another aspect of the present invention, an apparatus for booting an operating system is provided, comprising: a compiling module configured to compile a first operating system gateway platform based on a first kernel, wherein the first kernel is in the first An operating system gateway platform supports code for running a second operating system;

a processing module, configured to migrate the LXC container to the first operating system gateway platform, and establish a component for running the second operating system, where the LXC container is used to manage the first operating system a gateway platform and the second operating system;

Activating a module, configured to trigger the second operating system to be launched in the component by the LXC container.

According to the embodiment of the present invention, the first operating system gateway platform is compiled based on the first kernel, wherein the first kernel supports running the code of the second operating system based on the first operating system gateway platform, and then transplants the LXC container to the first In the operating system gateway platform, a component for running the second operating system is started, wherein the LXC container is used to manage the first operating system gateway platform and the second operating system, and finally the second operating system is triggered in the component by the LXC container. The startup solves the problem that the gateway platform can only start one operating system at the same time in the related technology, and realizes that two operating systems are simultaneously started on the gateway platform, and the functions and other operations of the gateway platform operating system are realized without increasing the hardware cost. The effect of the system's intelligent business integration.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a flowchart of a method for starting an operating system according to an embodiment of the present invention;

2 is a structural block diagram of an apparatus for starting an operating system according to an embodiment of the present invention;

3 is a block diagram 1 of an optional structure of an operating device startup device according to an embodiment of the present invention;

4 is a block diagram 2 of an optional structure of an operating device startup device according to an embodiment of the present invention;

5 is a block diagram 3 of an optional structure of an operating device startup device according to an embodiment of the present invention;

6 is a block diagram 4 of an optional structure of an operating device startup device according to an embodiment of the present invention;

7 is a structural block diagram of an apparatus for upgrading an operating system according to an embodiment of the present invention;

8 is a block diagram 1 of an optional structure of an upgrading apparatus of an operating system according to an embodiment of the present invention;

9 is a block diagram 2 of an optional structure of an operating device upgrade apparatus according to an embodiment of the present invention;

10 is a system framework diagram of a Linux gateway platform and an Android platform integrated according to an optional embodiment of the present invention;

11 is a flowchart showing a system version startup according to an alternative embodiment of the present invention;

Figure 12 is a flow chart showing the startup of the LXC container in accordance with an alternative embodiment of the present invention;

13 is a flowchart of a startup of an android system according to an alternative embodiment of the present invention;

14 is a flowchart of a boot phase system version program upgrade according to an alternative embodiment of the present invention;

15 is a flow chart of system version program upgrade after version startup according to an alternative embodiment of the present invention.

Embodiments of the invention

Embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

In this embodiment, a method for starting an operating system is provided. FIG. 1 is a flowchart of a method for starting an operating system according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step 102: Compile a first operating system gateway platform based on the first kernel, where the first kernel supports running the code of the second operating system based on the first operating system gateway platform;

In this embodiment, the first operating system gateway platform includes a hardware and a software system, and the first kernel may be a kernel of a first operating system of the first operating system gateway platform;

Optionally, when the first kernel is compiled, the code supporting the second operating system is migrated to the original kernel of the first operating system gateway platform to form and support the first operating system gateway platform and the second operating system. The first kernel.

Optionally, the primary and secondary functions of the first operating system gateway platform and the second operating system may be set, or the first operating system gateway platform and the second operating system are not divided into primary and secondary; in this embodiment, the first operation The system gateway platform can be the primary operating system, and the second operating system can be the secondary operating system. The first operating system and the second operating system are simultaneously run on the first operating system gateway platform. Optionally, the first operating system and the second operating system may be, but are not limited to, a linux system, an android system, and a windows system. In this embodiment, the linux system commonly used by the home gateway is used as the first operating system, and the android system with rich application is used as the second operating system as an example.

Step 104: The LXC container is transplanted into the first operating system gateway platform, and a component for running the second operating system is started, where the LXC container is used to manage the first operating system gateway platform and the second operating system;

In this embodiment, the LXC container is a linux system container, runs in the first operating system, and can also start the second operating system when the first operating system is started, and manages the first in the first operating system gateway platform. The second operating system, the component for running the second operating system may include a system plug-in, a software process, a virtual channel, a system space, and the like.

Step 106, triggering the second operating system to start in the component through the LXC container.

In this embodiment, the first operating system gateway platform is compiled based on the first kernel, wherein the first kernel can support running the code of the second operating system based on the first operating system gateway platform, and then transplanting the LXC container to the first In the operating system gateway platform, and establishing a component for running the second operating system, wherein the LXC container is used to manage the first operating system gateway platform and the second operating system, and finally the second operating system is triggered in the component by the LXC container. The startup solves the problem that the gateway platform can only start one operating system at the same time in the related technology, and realizes the effect of integrating the functions of the gateway platform operating system with the intelligent services of other operating systems without increasing the hardware cost.

In an optional implementation manner of the embodiment of the present invention, after the LXC container is migrated to the first operating system gateway platform, the startup method further includes: installing the second operating system to the first operating system by using a predetermined rule based on the LXC container Specifies the system partition where the specified system partition is a system partition other than the one on which the first operating system gateway platform is installed.

In this optional implementation manner, the system space of the first operating system gateway platform may be isolated and partitioned. In the partitioning process, a namespace or a cgroup may be used (cgroup is a limitation provided by the Linux kernel, The mechanism for recording and isolating the physical resources used by the process group) is to isolate the Linux system from the android system, and divide the first operating system gateway platform into the first operating system space and the second operating system space, and the LXC container passes the predetermined rule The second operating system reserves the second operating system space, that is, specifies the system partition, and then installs the second operating system in the specified system partition, and the first operating system is installed in the first operating system space.

In an optional implementation manner of the embodiment of the present invention, the component includes: an interaction channel between the first operating system gateway platform and the second operating system, and the component for running the startup second operating system includes:

Step (S, Step) 11, establishing a first proxy process of the second operating system in the first operating system gateway platform;

S12. Establish a second proxy process of the first operating system gateway platform in the second operating system.

The first agent process and the second agent process respectively manage the second operating system and the first operating system gateway platform through the interaction channel, so as to implement and start the second operating system.

Optionally, the interaction between the first operating system and the second operating system in the first operating system gateway platform is completed by using the first proxy process and the second proxy process, where the interaction channel is set in the first operating system gateway platform. The transmission of data and signals for the first agent process and the second agent process when managing the second operating system and the first operating system, respectively.

In an optional implementation manner of the embodiment of the present invention, the component further includes: a resource restriction policy and a management allocation policy, where the method further includes: establishing a resource restriction policy and a management allocation policy in the first operating system gateway platform, The resource restriction policy and the management allocation policy are used to block the network function of the first operating system in the second operating system gateway platform.

In this optional implementation manner, by shielding the network function of the first operating system in the second operating system gateway platform, the second operating system can only use the first operating system to access the Internet after being started, for example, The android application running on the android system and the gateway platform business process running on the linux system use the network communication module of the gateway platform to implement the Internet access.

In an optional implementation manner of the embodiment of the present invention, triggering the second operating system to start in the component by using the LXC container includes:

S21. After starting the first operating system, trigger a preset script of the first operating system gateway platform to start the LXC container.

S22. Call the activated LXC container to start the first operating system through the interactive channel.

In this optional implementation manner, after the first operating system is started, the LXC container is started by triggering the preset script, and is triggered by the startup script of the Linux gateway. In S22, the LXC triggers the startup of the android system. Including the startup of the kernel part of the android system through the startup of the application layer framework part has been started in the Linux system.

It should be noted that the preset script here is a script generated according to the related art.

Optionally, in the embodiment of the present invention, after the first operating system and the second operating system are started in the first operating system gateway platform, the first operating system and the second operating system may be upgraded, and the upgrade process is performed. In the middle, you can use the local command upgrade and the network management remote upgrade to achieve two options.

The following is a description of upgrading the operating system by local commands. After the second operating system is started in the component by the LXC container, the upgrade includes:

S31. Upgrade a device environment required by the first operating system and/or the second operating system by using the specified command received;

S32. Load network parameter information, and configure network parameters required for upgrading the first operating system and/or the second operating system. The network parameter information may include an IP address, a subnet mask, and a file transfer protocol (FTP) username and password. And other parameters. Loading network parameter information can be implemented by receiving an external command of an input parameter or loading a configuration file containing network parameter information.

S33. Receive and execute a first command for upgrading the first operating system and a second command for upgrading the second operating system, respectively.

Optionally, the specified command may include a downver command under the script command line, and the first command for upgrading the first operating system may be downloading the linux platform version (for example, downver) The linuxVersion command, the second command for upgrading the second operating system, may be downloading the Android platform version (downver android) command. The upgrade is successful, restart the device, and run the system version. The first command and the second command can exist through a configuration file that can be directly loaded. A first command for upgrading the first operating system and a second command for upgrading the second operating system are executed by executing the configuration file.

The following is a description of the method for remotely upgrading an operating system by using a network management system. After the second operating system is started in the component by the LXC container, the startup method of the embodiment of the present invention further includes:

S41, the device environment required for remotely upgrading the first operating system and/or the second operating system by using the network management device; where the device environment may be configured according to the IP address and MAC address of the terminal; and registering the optical line terminal of the central office device (OLT) ), the method of connecting the server to the server and setting up the device environment can be implemented by loading the configuration file or receiving external commands. The principle of the implementation is the same as the principle of loading the network parameter information.

S42: Load network parameter information, and configure network parameters required to upgrade the first operating system and/or the second operating system.

S43. After executing the third command for upgrading the first operating system, verifying the second operating system.

S44. When the verification passes, receiving a fourth command for instructing the second operating system in the upgrade buffer to upgrade the second operating system.

It should be noted that the buffer area involved in this embodiment includes a cache area.

Optionally, the network parameter required to upgrade and run the first operating system and/or the second operating system includes, in addition to the data parameter, preparing the optical network device, and the third command for upgrading the first operating system may be download linuxVersion. The verification is performed before the upgrade of the second operating system to consider the security of the system backup. The upgrade is successful, restart the device, and run the system version.

In the above upgrade mode of upgrading the operating system through the network management system, the verification of the second operating system includes:

S51. Download the second operating system to be upgraded to the buffer area.

S52. Verify the second operating system in the buffer area. Here, the verification can be implemented by using a verification method of a related art, for example, a Cyclic Redundancy Check (CRC) check, The CRC checksum is calculated by comparing it with the checksum field in the version header.

Optionally, the second operating system to be upgraded may be downloaded to the cache area. After the verification is passed in the buffer area, an upgrade command may be triggered to mirror the root file system of the cache area (root. Img) The file is read out and written to the root area. Then, the system version (system.img) of the cache area is read out and written to the system area; when the verification fails, the upgrade is not performed, and the network management platform is notified, and the upgrade is required.

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 a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the embodiments of the present invention.

An embodiment of the operating system is provided in the embodiment, and the device is used to implement the foregoing embodiments and optional implementations, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the devices described in the following embodiments may be implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the startup method of the operating system.

2 is a structural block diagram of a booting device of an operating system according to an embodiment of the present invention. As shown in FIG. 2, the device includes: a compiling module 20, a processing module 22, and a booting module 24, wherein

The compiling module 20 is configured to compile the first operating system gateway platform based on the first kernel, wherein the first kernel supports the code for running the second operating system based on the first operating system gateway platform;

In this embodiment, the first operating system gateway platform includes a hardware and a software system, and the first kernel may be a kernel kernel of the first operating system of the first operating system gateway platform, optionally, When the first kernel is translated, the code supporting the operation of the second operating system is transplanted into the original kernel of the first operating system gateway platform to form a first kernel capable of supporting simultaneous startup and operation of the first operating system gateway platform and the second operating system.

The processing module 22 is coupled to the compiling module 20, configured to port the LXC container to the first operating system gateway platform, and establish a component for running the second operating system, where the LXC container is used to manage the first operating system. Gateway platform and second operating system;

The startup module 24 is coupled to the processing module 22 and configured to trigger the second operating system to boot in the component through the LXC container.

FIG. 3 is a block diagram of an optional structure of an operating device startup device according to an embodiment of the present invention. As shown in FIG. 3, the device includes, in addition to all the modules shown in FIG. 2, an installation module 30, which is configured to be After the LXC container is migrated into the first operating system gateway platform, the processing module 22 installs the second operating system into the designated system partition of the first operating system by using a predetermined rule, wherein the specified system partition is installed except Other system partitions other than the system partition of the first operating system gateway platform.

It should be noted that whether or not the migration is completed may be determined by a preset system message or a notification message or the like.

4 is a block diagram 2 of an optional structure of an operating device startup device according to an embodiment of the present invention, as shown in FIG. 4 As shown, the device includes, in addition to all the modules shown in FIG. 2, the components include: an interaction channel between the first operating system gateway platform and the second operating system, and the processing module 22 includes: a first establishing unit 40 and a second establishing unit 42. ,among them,

The first establishing unit 40 is configured to establish a first proxy process of the second operating system in the first operating system gateway platform;

The second establishing unit 42 is configured to establish a second proxy process of the first operating system gateway platform in the second operating system;

The first agent process and the second agent process separately manage the second operating system and the first operating system gateway platform through the interaction channel, so as to implement and start the second operating system.

FIG. 5 is a block diagram 3 of an optional structure of an operating device startup apparatus according to an embodiment of the present invention. As shown in FIG. 5, the device includes: a resource restriction policy and a management allocation policy, in addition to all the modules shown in FIG. The processing module 22 includes: a third establishing unit 50 configured to establish a resource limiting policy and a management allocation policy in the first operating system gateway platform, wherein the resource limiting policy and the management allocation policy are used to shield the first operating system from being in the second Network functionality in the operating system gateway platform.

FIG. 6 is a block diagram of an optional structure of an operating device of the embodiment of the present invention. As shown in FIG. 6 , the device includes a first starting unit 60 in addition to all the modules shown in FIG. 4 . a second starting unit 62, wherein

The first startup unit 60 is configured to trigger a preset script of the first operating system gateway platform to start the LXC container after starting the first operating system;

The second starting unit 62 is configured to invoke the activated LXC container to start the second operating system through the interactive channel.

Optionally, according to the embodiment of the present invention, after the first operating system and the second operating system are started in the first operating system gateway platform, the first operating system and the second operating system may also be upgraded, and the upgrade is performed. In the process, you can use two options: local command upgrade and network management remote upgrade.

The following is a description of the configuration of the operating system of the operating system according to the embodiment of the present invention. As shown in FIG. 7, the first building module 70, the first configuration module 72, and the execution Module 74, wherein

The first building module 70 is configured to upgrade a device environment required by the first operating system and/or the second operating system by using the specified command received;

The first configuration module 72 is configured to load network parameter information, and configure network parameters required for upgrading the first operating system and/or the second operating system;

The executing module 74 is configured to separately receive and execute a first command for upgrading the first operating system and/or a second command for upgrading the second operating system, and upgrade the first operating system and/or the second operating system. .

The following is a description of an optional operating system for upgrading an operating system through a network management system. FIG. 8 is a block diagram of an optional structure of an operating system upgrade apparatus according to an embodiment of the present invention. As shown in FIG. 8, the method includes: a second building module 80 and a second configuration module. 82, a verification module 84, an upgrade module 86, wherein

The second building module 80 is configured to set up a device environment required for remotely upgrading the first operating system and/or the second operating system by using the network management system;

The second configuration module 82 is configured to load network parameter information, and configure network parameters required for upgrading the first operating system and/or the second operating system;

The verification module 84 is configured to perform verification on the second operating system after executing the third command for upgrading the first operating system;

The upgrade module 86 is configured to receive a fourth command for indicating a second operating system in the upgrade cache to upgrade the second operating system when the verification passes.

FIG. 9 is a block diagram 2 of an optional structure of an operating system upgrade apparatus according to an embodiment of the present invention. As shown in FIG. 9, in addition to all the modules shown in FIG. 8, the verification module 84 further includes: a download unit 90 and a verification unit. 92, of which

The downloading unit 90 is configured to download the second operating system to be upgraded to the buffer area;

The verification unit 92 is configured to check the second operating system in the buffer area.

It should be noted that the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are respectively located in multiple processes. In the device.

The following describes an alternative embodiment of the present invention, and provides a solution for starting an Android system using an LXC container, including:

S61, designing the kernel (kernel) of the linux gateway, based on the kernel of the universal Linux gateway platform, porting the code supporting the running of the android system to the kernel;

S62. Compile the linux gateway platform version based on the new kernel, test the basic gateway function, and ensure that the basic gateway function is normal; the new kernel is a kernel for porting the code supporting the android system.

S63. Porting the LXC container to the linux gateway platform version;

S64. Establish a resource restriction and management module; that is, establish a component that includes a resource restriction policy and a management allocation policy;

S64. Establish an interactive channel between the gateway platform and the android system.

S65, compiling the android system version, and installing to the specified system partition of the gateway platform;

S66. Start the Linux gateway system version.

S67, starting the LXC container;

S68, triggering the startup of the android system by the LXC container;

Optionally, in the foregoing embodiment, in S67, starting the LXC container may be triggered by a startup script of the Linux gateway; in S68, the LXC triggers the startup of the android system, including starting through the application layer framework part, android The startup of the system-related kernel part is complete.

The following describes the upgrade method of the system version. There are two ways to upgrade the system version:

One is to upgrade through the downver command under the boot command line. The upgrade steps include:

S71. Set up a device environment for upgrading the system version program in the boot phase.

S72. Power on the optical network unit (ONU, optical network device) to configure network parameters.

S73. Execute the downver linuxVersion command to upgrade the gateway platform program.

S74, executing the downver android command, upgrading the android system program;

S75. When the upgrade is successful, restart the device and run the system version.

Another optional upgrade method is remotely upgraded through the NMS. The upgrade steps are as follows:

S81. The device environment for upgrading the system version program under the build version;

S82. The ONU device is powered on and configured with network parameters. The optical network device is configured.

S83, executing download linuxVersion, upgrading the gateway platform program;

S84, execute download androidSys, first download the android version to the cache area;

S85, verifying the android version;

S86, check pass, and then trigger an upgrade command, read the root.img of the cache area, write to the root area. Then read out the system.img of the cache area and write it to the system area;

S87. If the verification fails, the upgrade is not performed, and the network management platform is notified, and the upgrade is required.

S88. Restart the device when the upgrade is successful, and run the system version.

Optionally, androidSys contains the root.img and system.img required for the android system to run.

Due to the large version of the android system and the security of the system backup, the cache partition is introduced to facilitate version verification and system recovery.

10 is a system framework diagram of a linux gateway platform and an android platform in an alternative embodiment of the present invention. As shown in FIG. 10, the technical solution of the embodiment of the present invention is described below with reference to FIG. 10 and the embodiment:

A technology and system upgrade method for starting an android system using an LXC container according to an embodiment of the present invention includes:

According to the system framework diagram of the Linux gateway platform and the android platform integrated in FIG. 10,

The process includes:

S91: Prepare the Linux kernel, transplant the kernel code of the android system to the gateway kernel code, and make the gateway platform and the android system share a Linux kernel;

S92: Compile the basic version of the Linux gateway platform;

S93: Compile the android system version;

S94: Establish an LXC container, and use the namespace and cgroup technology to isolate the Linux gateway platform from the android operating system.

S95: Establish resource restriction and management allocation strategy.

S96: Establish an interactive channel between the linux gateway platform and the android system; set on the side of the gateway platform The agent process of the android system, the agent process of the gateway platform is designed on the android side. The interaction of both systems is done through a proxy.

S97: The network function of the android system is shielded, so that the android application and the gateway platform business process both use the network communication module of the gateway platform.

S98: Download the linux gateway platform version and the android system version to the board, and start the version.

FIG. 11 is a flowchart showing a system version startup according to an optional embodiment of the present invention. As shown in FIG. 11, the process includes:

Step 201: The system is powered on, the bootloader program starts, initializes the central processing unit (CPU) register, and initializes the peripheral hardware of the system, including memory, flash (flash), network port, serial port and other device initialization.

Step 202: Start the Linux kernel.

Step 203: The initialization (init) process of the Linux kernel starts.

Step 204: After the basic function version of the linux gateway platform is started, the initialization (init) process starts to start the LXC container.

Step 205: After the LXC container is started, the child process calls the start program to start the init process of the android system in the container space by executing the file (execve).

Step 206: The init process of the android system starts to execute some service processes (services) of the android system.

Step 207: After the services are started, start the zygote of the portal process of the Andorid application framework.

Step 208: Start a system service process (system server).

Step S209: Start a server manager.

Step S210: Finally launch the related application (app);

Figure 12 is a flowchart showing the startup of the LXC container according to an alternative embodiment of the present invention. The main function (Main) calls LXC to open (lxc_start), as shown in Figure 12, including:

S301, initialization processing; including a management structure LXC management (lxc_handler) structure of the initialization container, returning the structure, lxc_handler in addition to containing the container name, attributes, and containing char *cgroup members are used to associate a corresponding cgroup;

S302, passing the parameter assignment or parsing the configuration file;

S303, setting the LXC container status to ON (STARTING);

S304, namespace attribute setting;

S305. Create a network device of the container or a virtual console (tty) or a console device (console);

S306. Set a path of the specified root file system.

S307. Create a process by using a new namespace (namespace) according to the namespace clone identifier (clone_flags); therefore, the processes of the container are isolated from each other;

S308, create a cgroup container, and add a task task number (pid) to the cgroup;

S309, the parent process responds to the child process by setting a cgroup attribute according to the configuration file; the notification response child process may be lxc_sync_barrier_child, and the lxc_sync_barrier_child process includes: when the child process is ready to set cgroups, the child process is notified to continue initialization.

S310, setting a sub-process network interface attribute establishment network (setup_network), including an Internet Protocol (IP) address, an interface name, and the like;

S311, root file system establishment (Setup_rootfs), and mount (mount) loading;

S312, setting a child process tty/console;

S313, changing the root directory location (Changroot) referenced by the execution of the program to set the root file system (Setup_rootfs_pivot_root);

S314, querying the parent process synchronization setting cgroups; for example, calling lxc_sync_barrier_parent to query the parent process synchronization setting cgroups;

S315, Lxc-poll (processing container command, etc.);

S316, the child process calls the startup process start, and starts the initialization application by executing the file (execve); and comprises initializing the init by the application after the file startup parameter -d is executed.

13 is a flowchart of an android system startup process according to an alternative embodiment of the present invention. As shown in FIG. 13, the android system starts an init process and performs a boot task, including a ril daemon (ril-daemon) (as a very important part of Windows Mobile). Components, RIL enables wireless voice and data applications It is possible; the location of the RIL is on the protocol stack of the wireless baseband system, under the CellCore layer of Windows Mobile. Android RIL is located between the application framework and the kernel, divided into two parts, one part responsible for the socket (socket) to communicate with the application framework. The other part is responsible for communicating with Radio Broadcasting (RADIO) in two ways. They are the AT command channel that communicates directly with the radio and the channel used to transmit the packet data. The data channel is used for the Internet access function of the mobile phone. Multimedia (Media), Bootsound, boot animation, service manager, etc., then launch the application framework's portal process zygote (Zygote), start the virtual machine, such as Dalvik VM, open the system service (Systemserver), open more A variety of applications to prepare, call Window Manager, Package Manager, Power Manager, AccountManager, Content Manager , Handare Service, Sensor Service, Connectivity Service, Location Manager, Search Service, Battery Service, and finally enter the activity (Activity ) Manager, start the system component Home Activity, fully start the android system.

14 is a flowchart of a boot phase system version program upgrade according to an alternative embodiment of the present invention. As shown in FIG. 14, the boot phase system version program upgrade method includes:

Step 501: Establish a device environment for upgrading the system version program in the boot phase; including: connecting the ONU device to the PC through the network cable and the serial cable, and opening the Tftp (Trivial File Transfer Protocol) client on the PC side. , ready to upgrade the version of the program.

Step 502: Power on the boot program, configure the network parameters, including: powering on the ONU device, pressing the enter key during the boot process, entering the boot command line, inputting the setenv command, configuring the ONU side and the TFTP server. The IP address of the side is on the same network segment.

Step 503: Execute downloading the linux platform version (downver linuxVersion) command, and upgrading the gateway platform program;

Step 504: Execute downloading the Android platform (downver android) command, and upgrading the Android (android) system program;

Step 505: The upgrade is successful, and the device is restarted; the system version is run at this time.

15 is a flowchart of a system version program upgrade after version startup according to an alternative embodiment of the present invention. As shown in FIG. 15, the method for upgrading a system version after a gateway version includes the following steps:

Step 601: The device environment for upgrading the system version program after the version is built; includes: connecting the ONU device to the PC through the network cable, opening the client for downloading the file on the PC side, and preparing the version program to be upgraded. The client that downloads the file can be a WFTP client, and the WFTP client is a client that includes a file download tool.

Step 602: The ONU is powered on, and the network parameters are configured, including: the ONU device is powered on, and after the version is completely completed, the IP address and the virtual LAN (vlan) parameter of the ONU are remotely configured by using a PC to remotely connect to the gateway.

Step 603: Execute the download linuxVersion command to upgrade the gateway platform program.

Step 604: The upgrade is successful, and the downloading of the Android platform system file (download androidSys) is performed, the android version is downloaded to the cache area, and the version is verified; if the upgrade is unsuccessful in step 603, the network management platform needs to be reported, and then step 603 is performed again. Gateway platform program;

Step 605: The android version is successfully verified, and the android version is upgraded to the root area and the system area. If the android version verification is not successful, you need to report to the network management platform and re-download the android version.

Step 606: The upgrade is successful, and the device is restarted.

On the one hand, the smart home gateway of the embodiment supports the intelligent services of the anroid operating system, such as Thunder downloading, smart home, one-click speeding, etc. These intelligent services can be implemented by installing a third-party android plug-in, and can also implement existing ones. The basic functions of the home gateway, such as voice service, Internet service, IPTV, etc., realize the integration of the gateway basic service and the anroid intelligent service by using the LXC container technology.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. Compiling a first operating system gateway platform based on the first kernel, where the first kernel supports running the code of the second operating system based on the first operating system gateway platform;

S2, the LXC container is transplanted into the first operating system gateway platform, and a component for running the second operating system is started, where the LXC container is used to manage the first operating system gateway platform and the second operating system;

S3, triggering the second operating system to start in the component through the LXC container.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Obviously, those skilled in the art should understand that the above-described modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented by program code executable by a computing device such that they may be stored in a storage device by a computing device and, in some cases, may be executed in a different order than herein. The steps shown or described are either fabricated as integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and the present invention may be modified and changed by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions. The invention is not limited to any specific form of combination of hardware and software.

The embodiments disclosed in the present application are as described above, but the descriptions are only for the purpose of understanding the present application, and are not intended to limit the present application, such as the specific implementation method in the embodiments of the present invention. Any modifications and changes in the form and details of the embodiments may be made by those skilled in the art without departing from the spirit and scope of the disclosure. The scope defined by the appended claims shall prevail.

Industrial applicability

The above technical solution realizes that two operating systems are simultaneously started on the gateway platform, and the effect of the function of the gateway platform operating system and the intelligent service of other operating systems is realized without increasing the hardware cost.

Claims

An operating system startup method includes:

Compiling a first operating system gateway platform based on the first kernel, wherein the first kernel supports code for running the second operating system based on the first operating system;

Porting an LXC container into the first operating system gateway platform and establishing a component for running the second operating system, wherein the LXC container is configured to manage the first operating system gateway platform and the Second operating system;

The second operating system is triggered to be launched in the component by the LXC container.
The booting method according to claim 1, after the migrating the LXC container to the first operating system gateway platform, the booting method further includes:

Installing the second operating system into a specified system partition of the first operating system by a predetermined rule based on the LXC container, wherein the specified system partition is a system partition other than the first operating system gateway platform installed Other system partitions than others.
The booting method according to claim 1, wherein the component comprises: an interaction channel between the first operating system gateway platform and the second operating system, and the establishing is used to run the second operating system Components include:

Establishing a first proxy process of the second operating system in the first operating system gateway platform;

Establishing a second proxy process of the first operating system gateway platform in the second operating system;

The first agent process and the second agent process respectively manage the second operating system and the first operating system gateway platform through an interaction channel, so as to implement and start the second operating system.
The startup method according to any one of claims 1 to 3, the component further comprising: a resource restriction policy and a management allocation policy, the startup method further comprising:

Establishing the resource restriction policy and the management allocation policy in the first operating system gateway platform, wherein the resource restriction policy and the management allocation policy are used to block the first operation The network function of the system in the second operating system gateway platform.
The booting method according to claim 3, wherein the triggering the booting of the second operating system in the component by the LXC container comprises:

Triggering a preset script of the first operating system gateway platform to start the LXC container after starting the first operating system;

The LXC container that invokes the launch initiates the second operating system through the interactive channel.
The booting method of claim 1, after the triggering, by the LXC container, that the second operating system is started in the component, the booting method further comprises:

Upgrading a device environment required by the first operating system and/or the second operating system by receiving the specified command;

Loading network parameter information, and configuring network parameters required to upgrade the first operating system and/or the second operating system;

Receiving and executing a first command for upgrading the first operating system and/or a second command for upgrading the second operating system, respectively, upgrading the first operating system and/or the second operating system .
The booting method according to claim 1, after the triggering the second operating system to be started in the component by the LXC container, the booting method further includes:

Establishing a device environment required for remotely upgrading the first operating system and/or the second operating system by using a network management system;

Loading network parameter information, and configuring network parameters required to upgrade the first operating system and/or the second operating system;

After performing the third command for upgrading the first operating system, verifying the second operating system;

When the verification passes, a fourth command for indicating the second operating system in the upgrade buffer is received to upgrade the second operating system.
The method of claim 7, wherein the verifying the second operating system comprises:

Downloading the second operating system to be upgraded to a cache area;

The second operating system is verified in the buffer area.
The method according to any one of claims 1 to 8, wherein the first operating system is a Linux system and the second operating system is an Android Android system.
An operating device startup device includes:

Compiling a module, configured to compile a first operating system gateway platform based on the first kernel, wherein the first kernel supports running the code of the second operating system based on the first operating system gateway platform;

a processing module, configured to migrate the LXC container to the first operating system gateway platform, and establish a component for running the second operating system, where the LXC container is used to manage the first operating system a gateway platform and the second operating system;

Activating a module, configured to trigger the second operating system to be launched in the component by the LXC container.