CN115016844A - A method to use chroot and gRPC to achieve program compatibility based on different runtime libraries - Google Patents

Abstract

The invention relates to a method for realizing program compatibility operation based on different runtime libraries by using a port and a gPC (graphics guide computer). The gRPC is used to accomplish information format transfer between the off-user spaces. Two or more user spaces communicate with each other using a local socket (unix domain socket). For the programs and the shared libraries with closed sources, partial functions in the programs and the shared libraries are realized again in a mode of modifying the basic runtime libraries with open sources, so that the runtime environment needing to be compatible can run in a host runtime (default user space runtime) environment.

Description

A way to use chroot and gRPC to achieve compatibility of programs based on different runtime libraries

technical field

The invention relates to a method, in particular to a method for realizing program compatibility operation based on different runtime libraries by using chroot and gRPC, and belongs to the technical field of multi-operating system fusion.

Background technique

At present, the mainstream embedded operating system on the market is the Android system. Most of the embedded chip manufacturers have made chip adaptations for the Android system and produced many chip driver control programs based on the Android runtime library. For example, a baseband processor (BP, also known as Modem) is generally responsible for providing basic voice services and data services on a mobile device. The chip manufacturer will design a special basic service program for the BP chip, including but not limited to, the program (or code base) to start the BP, and the program (or code base) to encrypt and check the BP data. These programs are based on the operation of the Android system. It runs from time to time. At the same time, in order to protect the chip manufacturer's own power and information security, it is generally provided to customers in binary form rather than source code form; , developers can only get binary programs or libraries. When the target operating system changes, such as Android version upgrade, or the upper operating system needs to be replaced (such as keeping the Linux kernel unchanged, but replacing Android with OpenHarmony), the closure The source program/library cannot run, because the program can no longer correctly access the dependent libraries (such as libc, etc.) in its original design, and libd itself may depend on a new libe, libf, etc. Therefore, it is urgently needed. A new solution solves the above technical problems.

SUMMARY OF THE INVENTION

The present invention is aimed at the problems existing in the prior art, and provides a method for realizing program compatibility operation based on different runtime libraries by using chroot and gRPC. The technical solution is mainly aimed at the transplantation compatibility problem of closed source programs/libraries. , to solve the problem of runtime dependencies, and to further solve the dependencies of the runtime itself, convert the achievable dependencies to the new operating system/runtime environment for implementation, so that closed-source programs and libraries can run on the new operating system /runtime environment.

In order to achieve the above object, the technical solution of the present invention is as follows, a method for realizing program compatibility operation across different user spaces and runtime libraries by using chroot and gRPC, the method includes the following steps:

Step 1: Prepare the runtime environment of the Linux-based operating system Android; including but not limited to the basic libc runtime library, etc.;

Step 2: Implement the API of the necessary basic library, use the gRPC protocol for interface conversion, and generate the server program and the client library program;

Step 3: The Linux-based operating system OpenHarmony starts the basic library service program in the host runtime space;

Step 4: Linux-based operating system OpenHarmony uses system call chroot to switch the runtime environment; switch to the Android runtime environment prepared by step 1, execute the program that needs to be compatible in Android;

Step 5: When the program in the Android runtime environment accesses the API of its runtime library or system basic library, it connects to the basic library server program in the host runtime space, and uses the implementation in OpenHarmony to complete the Android runtime. The API implementation of the library or system base library.

The specific implementation process of step 1 is as follows:

(1) Confirm the dependent libraries and basic libraries required by compatible applications in the Android operating system by means of readelf or direct running check;

(2) Collect these dependent libraries and put them in the specified path.

The specific implementation process of step 2 is as follows:

(1) Using the gRPC protocol, convert the necessary API calls in the Android system into gRPC-based server programs and client library programs;

(2) The client library program can access the server program through gRPC;

(3) The server program uses the implementation in OpenHarmony to re-implement the API function in Android;

(4) The client library needs to be compiled and run in the Android environment;

(5) Link the APIs that need to be reimplemented in the basic library and runtime library collected in step 1 to the gRPC client library prepared in this step.

Wherein, the specific implementation process of step 3 is as follows:

(1) Start a background service in the OpenHarmony system, which is the server program defined in step 2

(2) The service will open a Linux local socket interface

(3) The service waits for the client to connect

Wherein, the specific implementation process of step 4 is as follows:

(1) OpenHarmony calls chroot through the Linux system, switches the root directory to the dependency library prepared in step 1, and executes the program that should run in the Android operating system.

Wherein, the specific implementation process of step 5 is as follows:

(1) The program running on the Android operating system will call the basic library or the API of the runtime library in the Android operating system to implement some business logic;

(2) The APIs of the base library and runtime library in Android that have been re-linked to the gRPC client library will access the server API in step 3.

Compared with the prior art, the advantages of the present invention are as follows: 1. The scheme can run directly without the source code of the target-compatible program, Android itself is open source, and the closed source program will eventually access the open source library; 2, the scheme gRPC greatly reduces the complexity of API interface compatibility; 3. The solution will use Linux's local Socket method to communicate, and the performance is better; It is the simplest system call chroot of the kernel, which can be closed source again; 5. This scheme bypasses closed source libraries and closed source code, and all modifications are not GPL agreement, and can be closed source again; 6. This scheme will significantly Reduce the resource dependence on the original chip factory, reduce the difficulty and time and resource investment of adapting to the new operating system, and the original chip does not require every generation of operating system

(and runtime libraries) or each operating system (and runtime libraries) to redo the source code level adaptation. As long as the basic library required by the program is transplanted and the key parts are implemented, the target closed source program/library can run correctly in the new operating system (runtime library environment).

Description of drawings

Fig. 1 is a prior art architecture diagram;

Fig. 2 is the technical framework relation diagram of the present invention;

FIG. 3 is a schematic diagram of a calling flow of the present invention.

Detailed ways

In order to deepen the understanding of the present invention, the present embodiment will be described in detail below with reference to the accompanying drawings.

Embodiment 1: Referring to FIG. 2-FIG. 3, a method for realizing program compatibility operation across different user spaces and runtime libraries using chroot and gRPC, the method includes the following steps:

Step 1: Prepare the runtime environment of the Linux-based operating system Android; including but not limited to the basic libc runtime library, etc.

Step 2: Implement the API of the necessary basic library, use the gRPC protocol for interface conversion, and generate the server program and the client library program;

Step 3: The Linux-based operating system OpenHarmony starts the basic library service program in the host runtime space;

Step 4: Linux-based operating system OpenHarmony uses system call chroot to switch the runtime environment; switch to the Android runtime environment prepared by step 1, execute the program that needs to be compatible in Android;

Step 5: When the program in the Android runtime environment accesses the API of its runtime library or system basic library, it connects to the basic library server program in the host runtime space, and uses the implementation in OpenHarmony to complete the Android runtime. The API implementation of the library or system base library.

The specific implementation process of step 1 is as follows:

(1) Confirm the dependent libraries and basic libraries required by compatible applications in the Android operating system by means of readelf or direct running check;

(2) Collect these dependent libraries and put them in the specified path. It can be run directly without the source code of the target compatible program

The specific implementation process of step 2 is as follows:

(1) Using the gRPC protocol, convert the necessary API calls in the Android system into gRPC-based server programs and client library programs;

(2) The client library program can access the server program through gRPC;

(3) The server program uses the implementation in OpenHarmony to re-implement the API function in Android;

(4) The client library needs to be compiled and run in the Android environment;

(5) Link the APIs that need to be reimplemented in the basic library and runtime library collected in step 1 to the gRPC client library prepared in this step. Android itself is open source, and closed source programs will eventually access open source libraries. The specific implementation process of step 3 is as follows:

(1) Start a background service in the OpenHarmony system, which is the server program defined in step 2

(2) The service will open a Linux local socket interface

(3) The service waits for the client to connect;

Advantages: gRPC greatly reduces the complexity of API interface compatibility

And it will use the Linux local Socket method to communicate, and the performance is better.

Wherein, the specific implementation process of step 4 is as follows:

(1) OpenHarmony calls chroot through the Linux system, switches the root directory to the dependency library prepared in step 1, and executes the program that should run in the Android operating system. No more complicated use of GPL license

The third-party repository, using the simplest kernel system call chroot, can be closed source again

Wherein, the specific implementation process of step 5 is as follows:

(1) The program running on the Android operating system will call the basic library or the API of the runtime library in the Android operating system to implement some business logic;

(2) The APIs of the base library and runtime library in Android that have been re-linked to the gRPC client library will access the server API in step 3.

In the above scheme, the closed source library and closed source code are bypassed, and all modifications are not GPL protocol, and can be closed again; the basic runtime library file of the Android system is prefabricated in the OpenHarmony system; use gRPC to redefine the necessary API interface; start the gRPC Service module D in the OpenHarmony system; use chroot to switch to the operating environment of the B system in the OpenHarmony system and run the target program C; the program C accesses the dependent runtime library according to its own needs, as follows: Dependency run The time library needs to access the Client module of gRPC:

(1) gRPC forwards the data request to D through the agreed access method (referring to the protocol definition of gRPC);

(2) D implements the requested function of C according to the new operating system/runtime implementation;

(3) D responds the data to C in an agreed manner;

(4) C gets the processing result and continues to run.

It should be noted that the above-mentioned embodiments are not intended to limit the protection scope of the present invention, and equivalent transformations or substitutions made on the basis of the above-mentioned technical solutions all fall into the protection scope of the present invention.

Claims (6)

1. a method for realizing the program compatibility operation based on different runtime libraries using chroot and gRPC, is characterized in that, described method comprises the following steps: Step 1: Prepare the runtime environment of the Linux-based operating system Android; Step 2: Implement the API of the necessary basic library, use the gRPC protocol for interface conversion, and generate the server program and the client library program; Step 3: The Linux-based operating system OpenHarmony starts the basic library service program in the host runtime space; Step 4: Linux-based operating system OpenHarmony uses system call chroot to switch the runtime environment; switch to the Android runtime environment prepared by step 1, execute the program that needs to be compatible in Android; Step 5: When the program in the Android runtime environment accesses the API of its runtime library or system basic library, it connects to the basic library server program in the host runtime space, and uses the implementation in OpenHarmony to complete the Android runtime. The API implementation of the library or system base library. 2. use chroot and gRPC according to claim 1 to realize the method for the program compatibility operation based on different runtime libraries, it is characterized in that, the concrete realization process of step 1 is as follows: (1) Confirm the dependent libraries and basic libraries required by compatible applications in the Android operating system through readelf or directly running the check method; (2) Collect these dependent libraries and put them in the specified path. 3. use chroot and gRPC according to claim 2 to realize the method based on the program compatibility operation of different runtime libraries, it is characterized in that, the concrete realization process of step 2 is as follows: (1) Using the gRPC protocol, convert the necessary API calls in the Android system into gRPC-based server programs and client library programs; (2) The client library program can access the server program through gRPC; (3) The server program uses the implementation in OpenHarmony to re-implement the API function in Android; (4) The client library needs to be compiled and run in the Android environment; (5) Link the APIs that need to be reimplemented in the basic library and runtime library collected in step 1 to the gRPC client library prepared in this step. 4. use chroot and gRPC according to claim 3 to realize the method for the program compatibility operation based on different runtime libraries, it is characterized in that, step 3 concrete realization process is as follows: (1) Start a background service in the OpenHarmony system, which is the server program defined in step 2; (2) The service will open a local Socket interface of Linux; (3) The service waits for the client to connect. 5. use chroot and gRPC according to claim 4 to realize the method for the program compatibility operation based on different runtime libraries, it is characterized in that, the concrete realization process of step 4 is as follows: (1) OpenHarmony calls chroot through the Linux system, switches the root directory to the dependency library prepared in step 1, and executes the program that should run in the Android operating system. 6. use chroot and gRPC according to claim 5 to realize the method for the program compatibility operation based on different runtime libraries, it is characterized in that, the concrete realization process of step 5 is as follows: (1) The program running on the Android operating system will call the basic library or the API of the runtime library in the Android operating system to implement some business logic; (2) The APIs of the base library and runtime library in Android that have been re-linked to the gRPC client library will access the server API in step 3.

Images