CN105335171B - Method and device for application program resident in operating system background - Google Patents

Abstract

The invention discloses a kind of method and devices on application program resident operating system backstage.This method comprises: receiving destination application starting request, corresponding destination application is requested to create host process for destination application starting；The host process calls function creation host keep-alive process；Host's keep-alive process calls function creation keep-alive process, and after keep-alive process creation, by the keep-alive process trustship to operating system；Building host process is connect with keep-alive process, is triggered connection of the host process with keep-alive process based on building and is mutually monitored；After listening to host process or keep-alive process is closed, start pent process.With the application of the invention, application program length, which may be implemented, resides in operating system backstage.

Description

Method and device for application program resident in operating system background

technical field

The invention relates to application program communication technology, in particular to a method and device for an application program to reside in the background of an operating system.

Background technique

With the popularization of the Internet, users are more and more resistant to network communication services, and have higher and higher requirements for the stability, responsiveness and zero-downtime service characteristics of network communication service systems. As a carrier for carrying network communication services, a communication device installs an operating system and installs an application program (App, Application) based on the installed operating system, thereby providing users with convenient Internet services.

Taking the Android operating system as an example, the Android operating system is an operating system applied to mobile communication devices. The source code is provided by google for customization by major manufacturers, and the application program is an executable program installed on the Android. In the current Android operating system environment, some third-party apps need to reside in the background of the operating system due to the needs of running tasks. For example, for instant messaging applications, the latest news needs to be updated from the server in real time to ensure normal services. For another example, for electronic market applications, it is necessary to monitor the installation and uninstallation of other applications in the communication device in the background, so as to upload the installation and uninstallation data of the application in the communication device, so as to analyze the user's preference behavior characteristics. For another example, for a Location Based Services (LBS, Location Based Services) application, it is necessary to monitor the geographic location information of the communication device, so as to realize the precise placement of the operator's advertisement. Therefore, how to realize a third-party App resident in the background of the operating system has become a technical problem that needs to be solved urgently.

In the prior art, because the Android operating system allows system-level applications developed by third-party developers to reside in the operating system background (referred to as the background), therefore, by obtaining the root (Root) authority of the operating system on the communication device, modify the operating system. The configuration information of the /system/build.prop file can realize the permanent residence of the third-party App in the background of the operating system, that is, by exploiting the loopholes in the configuration file of the operating system, so as to realize the permanent residence in the background. The specific process is as follows:

First, obtain the Root permission of the operating system; then, modify the configuration information of the /system/build.prop file under the operating system, and add sys.keep_App_1=xxx.xxx.xxx to the configuration information of the build.prop file, where xxx .xxx.xxx is the package name of the third-party App; then, it takes effect after restarting the communication device, and a parent process for the third-party App and a child process directly associated with the parent process are constructed through a fork function (fork). In this way, since the configuration information of the /system/build.prop file under the operating system is added with the relevant information of the third-party App, the operating system can manage and control the parent process and child process built by the third-party App. After the app exits the operating system, the parent process and child process corresponding to the third-party app can still reside in the background, so that the third-party app can reside in the operating system background.

However, the above method of resident application in the background of the operating system, first of all, requires the communication device to have the root function, but according to incomplete statistics, the current ratio of root is about 20%, the application is limited, and the applicability is not wide; secondly, the Android operating system A task manager is provided to record information such as the parent process corresponding to the application and the memory resources occupied by the child process directly associated with the parent process. There are many applications running in the background of the operating system and occupy a large amount of memory resources, resulting in insufficient operating system memory resources. In the case of system cleanup, the parent process and child process corresponding to the third-party App built by obtaining the operating system root permission are operated by The system is managed and controlled by querying the task manager and according to preset rules, for example, according to the memory resource usage or application priority to close (kill) the parent process corresponding to some applications and the child process directly related to the parent process. process, thereby terminating the running of the application, and reclaiming the memory resources occupied by the application to ensure the normal operation of the operating system, resulting in the parent process and the associated child process corresponding to the third-party App residing in the background may be blocked by the operating system Clear to release memory resources; or, in the process of anti-virus software installed in the communication device for virus detection, the parent process corresponding to the third-party App and the child process directly associated with the parent process may also be cleared. When the third-party App is cleared, the third-party App can be placed in the background running mode again only by restarting the communication device and running the third-party App.

As can be seen from the above, the method for the existing application program resident in the operating system background, because the application program resident in the background is cleared when the operating system memory resources are insufficient or in the process of checking and killing viruses, the third-party App resident ( For example, 24 hours) operating system background, the reliability of the application program resident in the background is low, which brings inconvenience to the user's normal communication service, affects the normal operation of the user's communication service, and reduces the user's communication service experience. However, loading the application program through the restart of the communication device to restart the closed process resides in the background, not only the operation process is more cumbersome, it takes a long time to realize the application program resides in the background, but also causes the communication of the entire communication device to be interrupted. It has a greater impact on the user's communication service experience.

SUMMARY OF THE INVENTION

In view of the above problems, the present invention is proposed in order to provide a method and apparatus for an application program resident in the background of an operating system which overcomes the above problems or at least partially solves the above problems.

According to one aspect of the present invention, there is provided a method for an application program to reside in the background of an operating system, the method comprising:

Receive a target application startup request, and create a main process for the target application corresponding to the target application startup request;

The main process calls a function to create a host keep-alive process;

The host keep-alive process calls a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system;

constructing a connection between the main process and the keep-alive process, triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

After listening to the main process or the keepalive process being shut down, start the shut down process.

Preferably, the operating system includes, but is not limited to, an Android operating system, a Linux operating system, and a Symbian operating system.

Preferably, the target application is stored in a preset startup list, and after each startup of the communication device, it is automatically triggered to initiate a target application startup request to the operating system, and the operating system obtains the preset startup request according to the received target application startup request. Set the startup list, automatically load the applications in the startup list, and assign the corresponding main process to each application in the startup list.

Preferably, the host keep-alive process places itself in a shutdown state so that the keep-alive process is hosted by the operating system.

Preferably, said placing itself in a closed state comprises:

When creating a host keep-alive process, the main process sets a life cycle for the created host keep-alive process, and after the set life cycle ends, the host keep-alive process is closed naturally.

Preferably, said placing itself in a closed state comprises:

After receiving the message that the keep-alive process is successfully created, the host keep-alive process resets its own life cycle to zero.

Preferably, the linking of the building main process with the keep-alive process includes:

The main process creates the server socket, and the keep-alive process creates the client socket;

Bind the server socket address and listen to the client socket through the server socket;

Waiting for client socket connection;

The client socket establishes a socket connection with the server socket.

Preferably, establishing a socket connection between the client socket and the server socket includes:

The main process creates a keep-alive process host object through the server socket, and allocates a corresponding keep-alive process identifier to the keep-alive process host object;

The main process uses the created keep-alive process host object to start the keep-alive process, and sends a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle;

The keepalive process starts and receives the resurrection command from the main process;

The keep-alive process creates a corresponding keep-alive process object through the client socket, and initializes the keep-alive process object;

The keep-alive process object sends a start-up response message to the main process, and the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object;

After receiving the start-up response message of the keep-alive process, the main process determines the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message, and sets the corresponding keep-alive process communication for the keep-alive process host object Interface handle.

Preferably, after establishing the socket connection, the method further includes:

The main process receives data from the keep-alive process through the main process communication interface handle, and sends data to the corresponding keep-alive process through the keep-alive process communication interface handle of the keep-alive process host object;

The keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle.

Preferably, the monitoring that the main process or the keep-alive process is shut down includes:

The first process is closed and is in a closed state;

The monitoring component corresponding to the first process side obtains that the first process is in a closed state, and sets the state parameter identifier of the first process to 0;

The second process connected through the socket reads the status parameter identifier of the first process;

The second process determines that the state parameter identifier of the first process is 0, and determines that the opposite process is closed.

Preferably, the monitoring that the main process or the keep-alive process is shut down includes:

The main process and the keep-alive process use the socket connection to monitor each other, determine that the virtual socket connection is disconnected, and determine that the main process or the keep-alive process is closed.

Preferably, after monitoring the shutdown of the main process or the keep-alive process, starting the shutdown process includes:

The main process monitors that the keep-alive process is closed, and calls the resurrection instruction to start the keep-alive process.

Preferably, after monitoring the shutdown of the main process or the keep-alive process, starting the shutdown process includes:

The keepalive process monitors that the main process is shut down, invokes the resurrection instruction to start the main process and triggers the activated main process to execute the calling function to create the process of the host keepalive process, and puts itself in a closed state after the main process is successfully started.

Preferably, the keep-alive process starts the main process in the non-Android life cycle, and uses the am instruction to start the main process in the linux-C process.

Preferably, the function is a bifurcation function.

Preferably, the main process and the host keep-alive process are in a parent-child process relationship, and the host keep-alive process and the keep-alive process are in a parent-child process relationship.

Preferably, the closed process is started by the keep-alive process or the main process that is not closed.

According to another aspect of the present invention, there is provided a device for an application program to reside in the background of an operating system, the device comprising: a main process creation module, a host keep-alive process creation module, a keep-alive process creation module, a connection module, and a monitoring processing module, in,

The main process creation module is used to receive the target application startup request, and create a main process for the target application corresponding to the target application startup request;

The host keep alive process creation module is used to trigger the main process to call the function to create the host keep alive process;

A keep-alive process creation module is used to trigger the host keep-alive process to call a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system;

a connection module, used for constructing a connection between the main process and the keep-alive process, and triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

The monitoring processing module is used to start the closed process after monitoring that the main process or the keep-alive process is closed.

Preferably, the keep-alive process creation module includes: a keep-alive process creation unit, a life cycle setting unit, and a life cycle running unit, wherein,

The keep-alive process creation unit is used to trigger the host keep-alive process to call a function to create a keep-alive process;

a life cycle setting unit, used to set a life cycle for the created host keep-alive process;

The life cycle running unit is used to run the set life cycle, and after the set life cycle ends, trigger the host keep-alive process to shut down naturally.

Preferably, the connection module includes: a connection preprocessing unit, a connection unit and a monitoring unit, wherein,

The connection preprocessing unit is used to trigger the main process to create a server socket, and the keep alive process to create a client socket; make the main process bind the server socket address, and monitor the client socket through the server socket connect; wait for client socket connection;

The connection unit is used to trigger the client socket to establish a socket connection with the server socket;

The monitoring unit triggers the main process and the keep-alive process to monitor each other based on the established connection.

Preferably, the connection unit includes: a keep alive process host object creation subunit, a promoter subunit, a keep alive process starter subunit, an initialization subunit, a response subunit, and a response processing subunit, wherein,

The keep-alive process host object creation subunit is used to trigger the main process to create a keep-alive process host object through the server socket, and assign a corresponding keep-alive process identifier to the keep-alive process host object;

A start-up subunit, used to trigger the main process to use the created keep-alive process host object to start the keep-alive process, and send a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle ;

The keep-alive process startup subunit is used to trigger the start of the keep-alive process and receive the resurrection instruction from the main process;

an initialization subunit, configured to trigger the keep-alive process to create a corresponding keep-alive process object through the client socket, and initialize the keep-alive process object;

a response subunit, configured to trigger the keep-alive process object to send a start-up response message to the main process, where the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object;

The response processing subunit is used to trigger the main process to determine the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message after receiving the start-up response message of the keep-alive process, and host the keep-alive process The object sets the corresponding keepalive process communication interface handle.

Preferably, the connection unit further comprises: a data transmission subunit, configured to trigger the main process to receive data from the keep-alive process through the main process communication interface handle, and to use the keep-alive process communication interface handle of the keep-alive process host object Send data to the corresponding keep-alive process; the keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle.

Preferably, the monitoring processing module includes: a state parameter identification setting unit, a state parameter identification reading unit, a state parameter identification determining unit, and a process restarting unit, wherein,

a state parameter identifier setting unit, used for, after the first process is closed and is in the closed state, the monitoring component corresponding to the first process side acquires that the first process is in the closed state, and sets the state parameter identifier of the first process to the closed state;

a state parameter identifier reading unit, used for reading the state parameter identifier of the first process through the second process connected by the socket;

a state parameter identification determining unit, configured to determine, in the second process, that the state parameter identification of the first process is a closed state, and determine that the first process is closed;

The process restarting unit is used to start the closed first process.

According to the method and device for the application program resident in the background of the operating system of the present invention, after the operating system creates the main process for the application program, the main process creates the host keep-alive process by calling the fork function fork(), sets the host keep-alive process, and then creates the host keep-alive process. Create a keep-alive process by calling the fork function fork(), and end its own life cycle after the keep-alive process is successfully created. In this way, the user process is separated by two-level processes, and after the host keep-alive process is closed, there is no direct correlation between the main process corresponding to the same application and the keep-alive process, which solves the problem of direct correlation between the operating system or antivirus software. The technical problem that the application cannot be resident in the background due to the killing, and the closed process is started through the process that has not been closed, so that the application can still reside in the background, which can well meet the needs of 7x24h running in the background. The business requirements of the application program and the beneficial effect of improving the reliability of the application program resident in the background; further, the method can be used on both Root and non-Root communication devices; moreover, there is no need to wait for the communication device to restart and reload the configuration file In order to make the process resident, the operation process is relatively simple, the time required to realize the application program resident in the background is short, the communication of the communication device is not affected, and the user's communication service experience is improved.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

FIG. 1 shows a method flow of an application program resident in the background of an operating system according to an embodiment of the present invention;

Fig. 2 shows the specific flow of the method for the application program to reside in the background of the operating system according to the embodiment of the present invention; and,

FIG. 3 shows an apparatus structure in which an application program resides in the background of an operating system according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

At present, by obtaining the operating system root authority, and then modifying the configuration information of the /system/build.prop file in the operating system, the parent process built based on the fork function and the child process directly associated with the parent process are hosted on the operating system to implement the application. The method of resident in the background, after the application exits the foreground, the parent process running in the foreground and the child process directly related to the parent process running in the background can still be activated, but the application residing in the background is insufficient in the operating system memory resources From time to time or in the process of virus checking, the active parent process and the child process directly related to the parent process may be cleared, and the third-party App cannot be resident (for example, 24 hours) in the operating system background; Restarting and loading an application program to restart the shut-down process resides in the background, not only the operation process is more cumbersome, it takes a long time to realize the application program resides in the background, but also causes the communication of the entire communication device to be interrupted.

Since the application creates the parent process and the child process directly associated with the parent process through the fork function, the application can be resident in the operating system background. If one of the two processes corresponding to the application is closed by the operating system or antivirus software After that, another process can be used to start the closed process in time, so that it can ensure the timely resurrection of the closed process in the background of the operating system, so that the application program corresponding to the process can be restored and reside in the background. However, due to the existing direct relationship between the parent process and the child process created for the application, when the task manager releases the memory resources, the resources occupied by the parent process and the directly related child process will be released together. Therefore, the parent process and the child process are closed at the same time, so that there is no situation in which one of the two processes corresponding to the application is closed by the operating system or antivirus software.

The fork function fork() originates from the needs of multi-threaded tasks in the operating system (OS, Operation System). After the application is started in the foreground, the operating system first allocates a process for the application, and calls it through the operating system to create a A process (parent process) is an almost identical process (child process). Among them, two processes can perform exactly the same function, or they can perform different functions. When the parent process calls the fork() function, the operating system first allocates resources to the new process (child process), such as space for storing data and code; then copies all the resources of the original process to the new new process, of course, After completing the fork, you can also modify the copied resources yourself. In this way, after the fork function is executed, two processes appear, one is the child process and the other is the parent process. In the child process, the fork function returns 0, and in the parent process, fork returns the process ID of the newly created child process. Thus, the child process can reside in the background after the application exits.

In the embodiment of the present invention, it is considered that after the operating system creates a child process for the parent process by calling the fork function fork(), it then creates a subordinate child process for the child process by calling the fork function fork(). In this way, there is no direct relationship between the parent process and the lower-level child process. After the child process is closed, the lower-level child process becomes an orphan process, which will be hosted by the operating system process. The same application, therefore, in subsequent use, when the system memory resources are insufficient or the anti-virus software is in the process of anti-virus checking, since there is no direct relationship between the parent process and the subordinate child process, the task manager will process the process shutdown according to the relationship. When the two processes are simultaneously cleared by the operating system or killed by anti-virus software at the same time, the probability is low , so as to ensure that the application runs continuously in the background, which can well meet the business needs of (third-party) applications that must run in the background 7x24h. Compared with the technical solution using Root, the embodiments of the present invention can be used on both Root and non-Root communication devices, are basically not affected by anti-virus software (anti-software), and have low power consumption.

FIG. 1 shows a flow of a method for an application program to reside in the background of an operating system according to an embodiment of the present invention. Referring to Figure 1, the process includes:

Step 101, receiving a target application startup request, and creating a main process for the target application corresponding to the target application startup request;

In this step, the target application is an application that needs to reside in the background of the operating system, for example, an instant messaging application, an electronic market application, and a positioning service application, etc., where the instant messaging application may be QQ, WeChat, Weibo, etc.

In the embodiment of the present invention, as an optional embodiment, the target application startup request is received by the operating system, and the operating system includes but is not limited to the Android operating system, the Linux operating system, the Symbian operating system, and the like.

In the embodiment of the present invention, the operating system background refers to the operating system background where the foreground application program resides in the operating system after it is closed.

In practical applications, the application programs that need to reside in the background of the operating system can be set in the startup list for startup of the communication device in advance. That is, the target application is stored in a preset startup list. In this way, after each startup of the communication device, it is automatically triggered to initiate a target application startup request to the operating system, and the operating system obtains a preset startup list according to the received target application startup request, automatically loads the applications in the startup list, and Assign the corresponding master process to each application in the startup list.

Of course, as an optional embodiment, after starting the communication device, the user can also click on the application program that needs to be started and reside in the background of the operating system, to trigger the starting request of the target application program to the operating system. In this way, the user can select one or more application programs that need to reside in the background of the operating system according to their actual needs.

In the embodiment of the present invention, the process of creating the main process for the target application is a known technology, and the detailed description is omitted here.

Step 102, the main process calls a function to create a host keep-alive process;

In this step, as an optional embodiment, the function is a bifurcation function. For the main process and the host keep-alive process, the main process corresponds to the parent process, and the host keep-alive process corresponds to the child process.

In the embodiment of the present invention, the parent process calls the fork function to generate a child process, and the child process has the same resources as the parent process.

Step 103, the host keep-alive process calls the fork function to create the keep-alive process, and after the keep-alive process is created, the keep-alive process is managed to the operating system;

In this step, the process of the host keep-alive process calling the fork function to create the keep-alive process is the same as the process of the main process calling the fork function to create the host keep-alive process, and details are omitted here.

In the embodiment of the present invention, for the host keep-alive process and the keep-alive process, the host keep-alive process corresponds to the parent process, and the keep-alive process corresponds to the child process.

In the main process, the host keep-alive process and the keep-alive process, a state parameter identifier is set. For example, when the state parameter identifier is 1, it means that the process is in a normal state; when the state parameter identifier is 0, it means that the process is in a closed state. That is, if the process is in the shutdown state, the state parameter flag corresponding to the process is automatically set to 0. In this way, in subsequent applications, the peer process reads the state parameter identifier corresponding to the process, so that the peer process can actively and timely know whether the process is alive or closed during the life cycle. Of course, in practical applications, it can also be set that when the status parameter identifier is 0, it indicates that the process is in a normal state; when the status parameter identifier is 1, it indicates that the process is in a closed state.

In the embodiment of the present invention, taking the Linux operating system as an example, on the Linux operating system, when the host keep-alive process is closed, the keep-alive process becomes an orphan process. Fork out of the process, that is, the operating system process. In this way, by separating the user process by two-level process, there can be no direct relationship between the main process and the keep-alive process, so that the task manager or antivirus software can effectively prevent the main process from killing the process according to the direct relationship. And keep alive processes are killed. That is to say, for example, when the task manager or antivirus software detects and kills the main process and needs to clear the main process, it can query the host keep-alive process according to the stored direct relationship of the main process, but because the host keep-alive process is It has been closed. Therefore, the main process is closed to release memory resources. In the case that the subsequent keep-alive process is not killed, the keep-alive process that has not been killed can revive the killed main process, making the main process. Applications corresponding to keep-alive processes can still reside in the operating system background.

As an optional embodiment, the host keep-alive process puts itself in a shutdown state, so that the keep-alive process is hosted by the operating system.

Among them, placing itself in a closed state includes:

When creating a host keep-alive process, the main process sets a life cycle for the created host keep-alive process, and after the set life cycle ends, the host keep-alive process is closed naturally.

In this step, when setting the life cycle for the created host keep-alive process, the main process considers the time required for the subsequent host keep-alive process to create the keep-alive process, so that the set life cycle is greater than or equal to the host keep-alive process creation life cycle. The time required for the live process is sufficient.

As another optional embodiment, placing itself in an off state may also include:

After receiving the message that the keep-alive process is successfully created, the host keep-alive process resets its own life cycle to zero.

In this step, when the main process sets the life cycle for the created host keep-alive process, it defaults to the maximum value set by the operating system, that is, the default life cycle is infinitely long, the host keep-alive process creates a keep-alive process, and the keep-alive process After the creation is successful, the creation success information is returned to the host keep-alive process. Therefore, it is possible to set the host keep-alive process to zero its own life cycle after receiving the successful message of the keep-alive process creation, so that the host keep-alive process naturally dies.

Step 104, constructing a connection between the main process and the keep-alive process, triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

In this step, as an optional embodiment, establishing a connection between the main process and the keep-alive process includes:

A11, the main process creates a server socket (LocalServerSocket), and the keep alive process creates a client socket (LocalSocket);

In this step, when connections are made based on multiple Transmission Control Protocols (TCP, Transmission Control Protocol) or there are multiple application programs, data may need to be transmitted through the same TCP protocol port. In order to distinguish different application processes and connections, a computer operating system provides an interface called a socket (Socket) for the interaction between applications and Transmission Control Protocol/Internet Protocol (TCP/IP, Transfer Control Protocol/Internet Protocol). Among them, the socket is used to distinguish the network communication and connection between different application processes. It is the basic operation unit of network communication that supports the TCP/IP protocol, and is the endpoint for two-way communication between processes between different hosts. That is to say, The two communicating parties can complete the communication process through the related functions in the socket.

In the embodiment of the present invention, the main process and the keep-alive process communicate in a client/server (C/S, Client/Service) mode. The main process creates a server-side Unix domain socket, that is, LocalServerSocket is used as a server, establishes a socket to monitor client requests, and the keep-alive process creates a client socket (LocalSocket), and the client socket runs in the keep-alive process.

In the embodiment of the present invention, taking creating a server socket as an example, a file descriptor is used to create an existing server socket, for example, the server socket resource address dev/socket/… is specified in init.rc ..., create a socket as a server, the program code segment is as follows:

LocalServerSocket socket=new LocalServerSocket(createFileDescriptor(fileDesc)).

As an optional embodiment, in this embodiment of the present invention, the socket types based on the TCP/IP protocol may include: a stream socket (SOCK_STREAM), a datagram socket (SOCK_DGRAM), and a raw socket (SOCK_RAW). The socket type is a well-known technology, and the detailed description is omitted here.

The content of the socket includes: the destination IP address of the communication, the used transport layer protocol, for example, the TCP protocol or the User Datagram Protocol (UDP, User Datagram Protocol), and the used port number.

A12, bind the server socket address, and monitor the client socket through the server socket;

In this step, the server socket does not locate a specific client socket, but is in a state of waiting for a connection, and monitors the network state in real time.

The program code that binds the server socket address and listens to the client socket through the server socket can be as follows:

// bind address

localAddress=new LocalSocketAddress(name);

impl.bind(localAddress);

//monitor

impl.listen(LISTEN_BACKLOG);

A13, waiting for client socket connection;

In this step, the client sets the connection address and establishes the connection. Specifically, the client socket of the keep-alive process sends a connection request, which carries the communication destination IP address, where the communication destination IP address is the server-side socket. That is, the client socket first describes the server socket that needs to be connected, writes the address and port number of the server socket, and then sends a connection request to the server socket.

The program code segment for setting the connection address can be as follows:

LocalSocketAddress address=new LocalSocketAddress("installd", LocalSocketAddress.Namespace.RESERVED);

/establish connection

mSocket.connect(address);

A14, the client socket establishes a socket connection with the server socket.

In this step, after the server-side socket monitors or receives the connection request sent by the client-side socket, it responds to the client-side socket request, establishes a new thread, and sends the information of the server-side socket. Give the keep-alive process corresponding to the client socket, and the keep-alive process confirms the socket connection. Specifically, this step includes:

A01, the main process creates a keep-alive process host object through the server socket, and allocates a corresponding keep-alive process identifier for the keep-alive process host object;

In this step, the main process creates and manages a keep-alive process host object, each keep-alive process host object corresponds to a keep-alive process, and has the same keep-alive process identifier as the corresponding keep-alive process.

A02, the main process uses the created keep-alive process host object to start the keep-alive process, and sends a resurrection instruction to the keep-alive process, and the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle;

In this step, the keep-alive process host object provides a method for creating and starting the keep-alive process, and provides a data communication interface for sending a resurrection instruction to the keep-alive process. Specifically, the main process uses a command line to create a new keep alive process by calling a process creation method provided by the keep alive process host object, and the command line includes the resurrection instruction.

A03, the keep alive process starts and receives the resurrection instruction from the main process;

A04, the keep-alive process creates a corresponding keep-alive process object through the client socket, and initializes the keep-alive process object;

In this step, during the initialization process, the keep-alive process saves the command-line parameters such as the keep-alive process identifier and the main process communication interface handle carried in the received resurrection instruction.

A05, the keep-alive process object sends a start-up response message to the main process, where the start-up response message carries the keep-alive process communication interface handle and keep-alive process identifier corresponding to the keep-alive process object;

In this step, after completing the initialization, the keep-alive process object sends a start-up response message to the main process by using Inter-Process Communication (IPC, Inter-Process Communication).

A06, after receiving the activation response message of the keep-alive process, the main process determines the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message, and sets the corresponding keep-alive process host object for the keep-alive process host object Process communication interface handle.

In this way, the keep-alive process host object in the main process has the keep-alive process communication interface handle of its corresponding keep-alive process object, and the keep-alive process also obtains the communication interface handle corresponding to the main process. Based on the obtained keep-alive process communication interface handle, the keep-alive process host object externally provides a communication interface for inter-process communication with the corresponding keep-alive process object, so that the main process can send data to the corresponding keep-alive process by calling the communication interface .

After the socket connection is established, both the main process and the keep-alive process are in a listening state, monitoring the state of each other.

Further, after establishing the socket connection, the method may further include:

A15, the main process and the keep-alive process establish a communication channel for data transmission.

This step can specifically include:

The main process receives data from the keep-alive process through the main process communication interface handle, and sends data to the corresponding keep-alive process through the keep-alive process communication interface handle of the keep-alive process host object;

The keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle.

Step 105, after monitoring that the main process or the keep-alive process is shut down, start the shut down process.

In this step, the main process and the keep-alive process are each other's processes, that is, after monitoring that the other process is closed, the closed process is started.

As an optional embodiment, monitoring that the peer process is shut down includes:

B11, the first process is closed and is in a closed state;

In this step, the first process may be either a main process or a keep-alive process. If the process is closed, it may be because the operating system needs to release memory resources to close the process when the memory resources are insufficient; it may also be that the antivirus software kills the process and closes the process during the antivirus detection process; it may also be other In this case, close the process.

B12, the monitoring component corresponding to the first process side acquires that the first process is in a closed state, and sets the state parameter identifier of the first process to 0;

B13, read the status parameter identifier of the first process through the second process connected by the socket;

In this step, if the first process is the main process, the second process is the keep-alive process; if the first process is the keep-alive process, the second process is the main process.

B14, the second process determines that the state parameter identifier of the first process is 0, and determines that the opposite process is closed.

As another optional embodiment, monitoring that the opposite process is shut down includes:

The main process and the keep-alive process use the socket connection to monitor each other, determine that the virtual socket connection is disconnected, and determine that the other process is closed.

In the embodiment of the present invention, the socket connection is used to monitor each other, the power consumption is small and stable, and it is not easy to make mistakes.

Preferably, after the operating system or antivirus software closes the process, all resources of the closed process are further released, so that the operating system can automatically reclaim system resources such as memory and CPU occupied by the closed process.

As an optional embodiment, after monitoring that the opposite process is shut down, starting the shut down process may include:

The main process monitors that the keep-alive process is closed, and calls the resurrection instruction to start the keep-alive process.

As another optional embodiment, after monitoring that the opposite process is shut down, starting the shut down process may further include:

The keep-alive process monitors that the main process is shut down, calls the resurrection instruction to start the main process and triggers the activated main process to execute the process of calling the fork function to create the host keep-alive process, and puts itself in a closed state after the main process is successfully started .

In this step, in order to avoid the resurrected main process creating a host keep-alive process and passing in a resurrection instruction to create a keep-alive process, redundant keep-alive processes exist in the operating system, thus occupying unnecessary operating system memory. Therefore, when the keep-alive process starts the main process, it ends its own life cycle and exits the operating system background.

Preferably, the keep-alive process starts the main process in the non-Android life cycle, and uses the am instruction to start the main process in the linux-C process, thereby restoring the Android service, so that the application program can reside in the operating system background.

FIG. 2 shows a specific flow of a method for an application program to reside in the background of an operating system according to an embodiment of the present invention. Referring to Figure 2, taking the main process being shut down as an example, the process includes:

Step 201, after the main process is started, call the fork function to create a host keep-alive process, and transmit a resurrection instruction to the created host keep-alive process, instructing to start the keep-alive process;

Step 202, the host keep-alive process receives the incoming resurrection instruction, and calls the fork function to create the keep-alive process;

In this step, the keep-alive process is created by calling the fork instruction in the fork function in the operating system to copy the keep-alive process.

Step 203, the life cycle of the host keep-alive process ends, and it dies naturally;

In this step, after the life cycle ends, the host keepalive process shuts down itself.

Step 204, the main process creates LocalServerSocket and waits for connection;

Step 205, the keep-alive process is connected to the main process and monitors each other;

In this step, the keep-alive process and the main process monitor the state of the other party, that is, read the state parameter identifier of the other party.

Step 206, the keep alive process monitors that the main process is killed (closed), and invokes the resurrection instruction to revive the main process;

In this step, if the keep-alive process detects that the connection with the main process is disconnected, it calls the resurrection instruction to resurrect the main process, and returns to step 201 .

Step 207, the life cycle of the keep-alive process ends, and it dies naturally.

In this step, when the life cycle of the keep-alive process ends, exit the operating system background, so as to prevent the resurrected main process from creating a host keep-alive process by creating a host keep-alive process and passing in a resurrection instruction to create a keep-alive process, so that the operating system has redundant keep-alive processes. live processes, thus occupying unnecessary operating system memory.

In the embodiment of the present invention, after the operating system creates the main process for the application, the main process creates the host keep-alive process by calling the fork function fork(), and the host keep-alive process creates the keep-alive process by calling the fork function fork(). , and ends its own life cycle after the keep-alive process is successfully created. In this way, the user process is separated by two-level processes. After the host keep-alive process is closed, the keep-alive process becomes an orphan process, which will be hosted by the operating system process, and there is no direct relationship between the main process and the keep-alive process. relation. Therefore, in the subsequent application, when one of the main process and the keep-alive process is closed, because the main process and the keep-alive process do not have a direct relationship, the other process that is killed according to the direct relationship is simultaneously killed. The probability of closing is low, so that the closed process can be started by the process that is not closed, so that the application can still reside in the background, which can well meet the business needs of the application that must run in the background 7x24h. Compared with the technical solution of using Root (that is, obtaining super administrator authority), the method of the embodiment of the present invention can be used on both Root and non-Root communication devices, has a wide range of applications, and has low power consumption, so that it can be used at a lower cost. It is especially important for applications that combine software and hardware that must reside in the background, so that the reliability of the application in the background is high; further, since the main process does not exit, all resources are There is no change, the generated keep-alive process inherits the resources of the main process, which can ensure that the resources of the keep-alive process remain unchanged, thereby ensuring the reliable operation of the application; Another process is instantly revived, and there is no need to load the application through the restart of the communication device to restart the closed process to stay in the background. The interruption of the communication of the communication device effectively improves the user's communication service experience.

FIG. 3 shows an apparatus structure in which an application program resides in the background of an operating system according to an embodiment of the present invention. Referring to Figure 3, the device is a communication device, including: a main process creation module, a host keep-alive process creation module, a keep-alive process creation module, a connection module and a monitoring processing module, wherein,

The main process creation module is used to receive the target application startup request, and create a main process for the target application corresponding to the target application startup request;

In the embodiment of the present invention, the operating system receives the target application startup request, and creates a main process, including but not limited to the Android operating system, the Linux operating system, the Symbian operating system, and the like.

As an optional embodiment, the target application is stored in a preset startup list. In this way, after each startup of the communication device, it is automatically triggered to initiate a target application startup request to the operating system, and the operating system obtains a preset startup list according to the received target application startup request, automatically loads the applications in the startup list, and Assign the corresponding master process to each application in the startup list.

The host keep alive process creation module is used to trigger the main process to call the function to create the host keep alive process;

In this embodiment of the present invention, the function is a bifurcation function.

A keep-alive process creation module is used to trigger the host keep-alive process to call a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system;

In this embodiment of the present invention, the main process, the host keep-alive process, and the keep-alive process are provided with a state parameter identifier used to indicate whether the process is in a closed state.

As an optional embodiment, the keep-alive process creation module includes: a keep-alive process creation unit, a life cycle setting unit, and a life cycle running unit (not shown in the figure), wherein,

The keep-alive process creation unit is used to trigger the host keep-alive process to call the fork function to create the keep-alive process;

a life cycle setting unit, used to set a life cycle for the created host keep-alive process;

The life cycle running unit is used to run the set life cycle, and after the set life cycle ends, trigger the natural death of the host keep-alive process.

In the embodiment of the present invention, when setting the life cycle for the created host keep-alive process, the main process considers the time required for the subsequent host keep-alive process to create the keep-alive process, so that the set life cycle is greater than or equal to the host keep-alive process The time required to create the keepalive process is sufficient.

a connection module, used for constructing a connection between the main process and the keep-alive process, and triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

As an optional embodiment, the connection module includes: a connection preprocessing unit, a connection unit, and a monitoring unit (not shown in the figure), wherein,

The connection preprocessing unit is used to trigger the main process to create a server socket, and the keep alive process to create a client socket; make the main process bind the server socket address, and monitor the client socket through the server socket connect; wait for client socket connection;

The connection unit is used to trigger the client socket to establish a socket connection with the server socket;

In the embodiment of the present invention, the connection unit includes: a keep alive process host object creation subunit, a promoter subunit, a keep alive process starter subunit, an initialization subunit, a response subunit, and a response processing subunit, wherein,

The keep-alive process host object creation subunit is used to trigger the main process to create a keep-alive process host object through the server socket, and assign a corresponding keep-alive process identifier to the keep-alive process host object;

A start-up subunit, used to trigger the main process to use the created keep-alive process host object to start the keep-alive process, and send a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle ;

The keep-alive process startup subunit is used to trigger the start of the keep-alive process and receive the resurrection instruction from the main process;

an initialization subunit, configured to trigger the keep-alive process to create a corresponding keep-alive process object through the client socket, and initialize the keep-alive process object;

a response subunit, configured to trigger the keep-alive process object to send a start-up response message to the main process, where the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object;

The response processing subunit is used to trigger the main process to determine the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message after receiving the start-up response message of the keep-alive process, and host the keep-alive process The object sets the corresponding keepalive process communication interface handle.

As an optional embodiment, the connection unit may further include:

The data transmission subunit is used to trigger the main process to receive data from the keep-alive process through the main process communication interface handle, and send data to the corresponding keep-alive process through the keep-alive process communication interface handle of the keep-alive process host object; The keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle.

The monitoring unit is configured to trigger the main process and the keep-alive process to monitor each other based on the established connection.

The monitoring processing module is used to start the closed process after monitoring that the other process is closed.

In the embodiment of the present invention, the monitoring processing module includes: a state parameter identification setting unit, a state parameter identification reading unit, a state parameter identification determining unit, and a process restarting unit (not shown in the figure), wherein,

a state parameter identifier setting unit, used for, after the first process is closed and is in the closed state, the monitoring component corresponding to the first process side acquires that the first process is in the closed state, and sets the state parameter identifier of the first process to the closed state;

In this embodiment of the present invention, the first process may be either a main process or a keep-alive process. If the process is closed, it may be because the operating system needs to release memory resources to close the process when the memory resources are insufficient; it may also be that the antivirus software kills the process and closes the process during the antivirus detection process; it may also be other In this case, close the process.

a state parameter identifier reading unit, used for reading the state parameter identifier of the first process through the second process connected by the socket;

In this embodiment of the present invention, if the first process is the main process, the second process is the keep-alive process; if the first process is the keep-alive process, the second process is the main process.

a state parameter identification determining unit, configured to determine, in the second process, that the state parameter identification of the first process is a closed state, and determine that the first process is closed;

The process restarting unit is used to start the first process.

In the embodiment of the present invention, the main process monitors that the keep-alive process is closed, and invokes the resurrection instruction to start the keep-alive process; or,

The keep-alive process monitors that the main process is shut down, calls the resurrection instruction to start the main process and triggers the activated main process to execute the process of calling the fork function to create the host keep-alive process, and puts itself in a closed state after the main process is successfully started .

Preferably, the keep-alive process starts the main process in the non-Android life cycle, and uses the am instruction to start the main process in the linux-C process, thereby restoring the Android service, so that the application program can reside in the operating system background.

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used with teaching based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not directed to any particular programming language. It is to be understood that various programming languages may be used to implement the inventions described herein, and that the descriptions of specific languages above are intended to disclose the best mode for carrying out the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or its description. This disclosure, however, should not be construed as reflecting an intention that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination, unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that although some of the embodiments described herein include certain features, but not others, included in other embodiments, that combinations of features of different embodiments are intended to be within the scope of the invention within and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all of some or all of the components of the apparatus in which the application program resides in the background of the operating system according to the embodiment of the present invention. Full functionality. The present invention can also be implemented as apparatus or apparatus programs (eg, computer programs and computer program products) for performing part or all of the methods described herein. Such a program implementing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such signals may be downloaded from Internet web servers, or provided on carrier signals, or in any other form.

It should be noted that the above-described embodiments illustrate rather than limit the invention, and that alternative embodiments may be devised by those skilled in the art without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names.

The invention discloses A1. A method for an application program to reside in the background of an operating system, comprising:

Receive a target application startup request, and create a main process for the target application corresponding to the target application startup request;

The main process calls a function to create a host keep-alive process;

The host keep-alive process calls a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system;

constructing a connection between the main process and the keep-alive process, triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

After listening to the main process or the keepalive process being shut down, start the shut down process.

A2. The method according to A1, the operating systems include but are not limited to Android operating systems, Linux operating systems, and Symbian operating systems.

A3. The method according to A1, the target application program is stored in a preset startup list, and after each startup of the communication device, it is automatically triggered to initiate a target application program startup request to the operating system, and the operating system is based on the received target application program. A program startup request, obtains a preset startup list, automatically loads the applications in the startup list, and assigns a corresponding main process to each application program in the startup list.

A4. The method of A1, wherein the host keep-alive process places itself in a shutdown state so that the keep-alive process is hosted by the operating system.

A5. The method according to A4, wherein the placing itself in an off state comprises:

When creating a host keep-alive process, the main process sets a life cycle for the created host keep-alive process, and after the set life cycle ends, the host keep-alive process is closed naturally.

A6. The method according to A4, wherein the placing itself in an off state comprises:

After receiving the message that the keep-alive process is successfully created, the host keep-alive process resets its own life cycle to zero.

A7. The method according to A1, wherein the building the connection between the main process and the keep-alive process includes:

The main process creates the server socket, and the keep-alive process creates the client socket;

Bind the server socket address and listen to the client socket through the server socket;

Waiting for client socket connection;

The client socket establishes a socket connection with the server socket.

A8. The method according to A7, wherein establishing a socket connection between the client socket and the server socket includes:

The main process creates a keep-alive process host object through the server socket, and allocates a corresponding keep-alive process identifier to the keep-alive process host object;

The main process uses the created keep-alive process host object to start the keep-alive process, and sends a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle;

The keepalive process starts and receives the resurrection command from the main process;

The keep-alive process creates a corresponding keep-alive process object through the client socket, and initializes the keep-alive process object;

The keep-alive process object sends a start-up response message to the main process, and the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object;

After receiving the start-up response message of the keep-alive process, the main process determines the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message, and sets the corresponding keep-alive process communication for the keep-alive process host object Interface handle.

A9. The method according to A8, after the socket connection is established, the method further comprises:

The main process receives data from the keep-alive process through the main process communication interface handle, and sends data to the corresponding keep-alive process through the keep-alive process communication interface handle of the keep-alive process host object;

The keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle.

A10. The method according to A1, the monitoring that the main process or the keep-alive process is shut down includes:

The first process is closed and is in a closed state;

The monitoring component corresponding to the first process side obtains that the first process is in a closed state, and sets the state parameter identifier of the first process to 0;

The second process connected through the socket reads the status parameter identifier of the first process;

The second process determines that the state parameter identifier of the first process is 0, and determines that the opposite process is closed.

A11. The method according to A1, the monitoring that the main process or the keep-alive process is shut down comprises:

The main process and the keep-alive process use the socket connection to monitor each other, determine that the virtual socket connection is disconnected, and determine that the main process or the keep-alive process is closed.

A12. The method according to A1, after monitoring that the main process or the keep-alive process is closed, starting the closed process includes:

The main process monitors that the keep-alive process is closed, and calls the resurrection instruction to start the keep-alive process.

A13. The method according to A1, after monitoring that the main process or the keep-alive process is closed, starting the closed process includes:

The keepalive process monitors that the main process is shut down, invokes the resurrection instruction to start the main process and triggers the activated main process to execute the calling function to create the process of the host keepalive process, and puts itself in a closed state after the main process is successfully started.

A14. The method according to A12 or 13, wherein the keep-alive process starts the main process in the non-Android life cycle, and uses the am instruction to start the main process in the linux-C process.

A15. The method according to A1, wherein the function is a bifurcation function.

A16. The method according to A1, wherein the main process and the host keep-alive process have a parent-child process relationship, and the host keep-alive process and the keep-alive process have a parent-child process relationship.

A17. The method according to A1, starting the shut down process through the keep-alive process or the main process that has not been shut down.

A18. A device for an application program resident in the background of an operating system, the device comprising: a main process creation module, a host keep-alive process creation module, a keep-alive process creation module, a connection module and a monitoring processing module, wherein,

The main process creation module is used to receive the target application startup request, and create a main process for the target application corresponding to the target application startup request;

The host keep alive process creation module is used to trigger the main process to call the function to create the host keep alive process;

A keep-alive process creation module is used to trigger the host keep-alive process to call a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system;

a connection module, used for constructing a connection between the main process and the keep-alive process, and triggering the main process and the keep-alive process to monitor each other based on the constructed connection;

The monitoring processing module is used to start the closed process after monitoring that the main process or the keep-alive process is closed.

A19. The device according to A18, wherein the keep-alive process creation module comprises: a keep-alive process creation unit, a life cycle setting unit, and a life cycle running unit, wherein,

The keep-alive process creation unit is used to trigger the host keep-alive process to call a function to create a keep-alive process;

a life cycle setting unit, used to set a life cycle for the created host keep-alive process;

The life cycle running unit is used to run the set life cycle, and after the set life cycle ends, trigger the host keep-alive process to shut down naturally.

A20. The device according to A18, wherein the connection module comprises: a connection preprocessing unit, a connection unit and a monitoring unit, wherein,

The connection preprocessing unit is used to trigger the main process to create a server socket, and the keep alive process to create a client socket; make the main process bind the server socket address, and monitor the client socket through the server socket connect; wait for client socket connection;

The connection unit is used to trigger the client socket to establish a socket connection with the server socket;

The monitoring unit triggers the main process and the keep-alive process to monitor each other based on the established connection.

A21. The device according to A20, wherein the connection unit comprises: a keep-alive process host object creation subunit, a promoter subunit, a keep-alive process starter subunit, an initialization subunit, a response subunit, and a response processing subunit, wherein,

The keep-alive process host object creation subunit is used to trigger the main process to create a keep-alive process host object through the server socket, and assign a corresponding keep-alive process identifier to the keep-alive process host object;

A start-up subunit, used to trigger the main process to use the created keep-alive process host object to start the keep-alive process, and send a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle ;

The keep-alive process startup subunit is used to trigger the start of the keep-alive process and receive the resurrection instruction from the main process;

an initialization subunit, configured to trigger the keep-alive process to create a corresponding keep-alive process object through the client socket, and initialize the keep-alive process object;

a response subunit, configured to trigger the keep-alive process object to send a start-up response message to the main process, where the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object;

The response processing subunit is used to trigger the main process to determine the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message after receiving the start-up response message of the keep-alive process, and host the keep-alive process The object sets the corresponding keepalive process communication interface handle.

A22. The device according to A21, wherein the connection unit further comprises: a data transmission subunit, configured to trigger the main process to receive data from the keep-alive process through the main process communication interface handle, and pass the data of the keep-alive process host object The keepalive process communication interface handle sends data to the corresponding keepalive process; the keepalive process receives data from the main process through the keepalive process communication interface handle, and sends data to the main process through the main process communication interface handle.

A23. The device according to A18, the monitoring processing module comprises: a state parameter identification setting unit, a state parameter identification reading unit, a state parameter identification determining unit and a process restarting unit, wherein,

a state parameter identifier setting unit, used for, after the first process is closed and is in the closed state, the monitoring component corresponding to the first process side acquires that the first process is in the closed state, and sets the state parameter identifier of the first process to the closed state;

a state parameter identifier reading unit, used for reading the state parameter identifier of the first process through the second process connected by the socket;

a state parameter identification determining unit, configured to determine, in the second process, that the state parameter identification of the first process is a closed state, and determine that the first process is closed;

The process restarting unit is used to start the closed first process.

Claims (19)

1. A method for an application program to reside in the background of an operating system, comprising: Receive a target application startup request, and create a main process for the target application corresponding to the target application startup request; The main process calls a function to create a host keep-alive process; The host keep-alive process calls a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system; Building a connection between the main process and the keep-alive process, triggering the main process and the keep-alive process to monitor each other based on the constructed connection; the building the connection between the main process and the keep-alive process includes: the main process creates a server socket, and the keep-alive process Create a client socket; bind the server socket address, and listen to the client socket through the server socket; wait for the client socket to connect; the client socket and the server socket are established The socket connection includes: the main process creates a keep-alive process host object through the server socket, and assigns a corresponding keep-alive process identifier to the keep-alive process host object; the main process uses the created keep-alive process host object to start Keep-alive process, and send a revival instruction to the keep-alive process, the revival instruction carries the keep-alive process identifier and the main process communication interface handle; the keep-alive process starts and receives the revival instruction from the main process; the keep-alive process The process creates a corresponding keep-alive process object through the client socket, and initializes the keep-alive process object; the keep-alive process object sends a startup response message to the main process, and the startup response message carries the keep-alive The keepalive process communication interface handle and the keepalive process identifier corresponding to the process object; after receiving the start response message of the keepalive process, the main process determines the corresponding keepalive process host object according to the keepalive process identifier in the start response message, and setting a corresponding keep-alive process communication interface handle for the keep-alive process host object; After listening to the main process or the keepalive process being shut down, start the shut down process. 2. The method of claim 1, wherein the operating systems include but are not limited to Android operating systems, Linux operating systems, and Symbian operating systems. 3. The method according to claim 1, wherein the target application program is stored in a preset startup list, and after each startup of the communication device, it is automatically triggered to initiate a target application program startup request to the operating system, and the operating system is based on the received The target application starts a request, obtains a preset startup list, automatically loads the applications in the startup list, and assigns a corresponding main process to each application in the startup list. 4. The method of claim 1, the host keepalive process places itself in a shutdown state so that the keepalive process is hosted by the operating system. 5. The method of claim 4, said placing itself in an off state comprising: When creating a host keep-alive process, the main process sets a life cycle for the created host keep-alive process, and after the set life cycle ends, the host keep-alive process is closed naturally. 6. The method of claim 4, said placing itself in an off state comprising: After receiving the message that the keep-alive process is successfully created, the host keep-alive process resets its own life cycle to zero. 7. The method of claim 1, after said establishing a socket connection, the method further comprising: The main process receives data from the keep-alive process through the main process communication interface handle, and sends data to the corresponding keep-alive process through the keep-alive process communication interface handle of the keep-alive process host object; The keep-alive process receives data from the main process through the keep-alive process communication interface handle, and sends data to the main process through the main process communication interface handle. 8. The method of claim 1, wherein monitoring that the main process or the keep-alive process is shut down comprises: The first process is closed and is in a closed state; The monitoring component corresponding to the first process side obtains that the first process is in a closed state, and sets the state parameter identifier of the first process to 0; The second process connected through the socket reads the status parameter identifier of the first process; The second process determines that the state parameter identifier of the first process is 0, and determines that the opposite process is closed. 9. The method of claim 1, wherein monitoring that the main process or the keep-alive process is shut down comprises: The main process and the keep-alive process use the socket connection to monitor each other, determine that the virtual socket connection is disconnected, and determine that the main process or the keep-alive process is closed. 10. The method according to claim 1, wherein after monitoring that the main process or the keep-alive process is closed, starting the closed process comprises: The main process monitors that the keep-alive process is closed, and calls the resurrection instruction to start the keep-alive process. 11. The method of claim 1, wherein after monitoring that the main process or the keep-alive process is closed, starting the closed process comprises: The keepalive process monitors that the main process is shut down, invokes the resurrection instruction to start the main process and triggers the activated main process to execute the calling function to create the process of the host keepalive process, and puts itself in a closed state after the main process is successfully started. 12. The method according to claim 10 or 11, wherein the keep-alive process starts the main process in the non-Android life cycle, and uses the am instruction to start the main process in the linux-C process. 13. The method of claim 1, the function is a bifurcation function. 14. The method of claim 1, wherein the main process and the host keep-alive process are in a parent-child process relationship, and the host keep-alive process and the keep-alive process are in a parent-child process relationship. 15. The method of claim 1, the shut down process is started by the keep alive process or the main process that is not shut down. 16. A device for an application program to reside in the background of an operating system, the device comprising: a main process creation module, a host keep-alive process creation module, a keep-alive process creation module, a connection module and a monitoring processing module, wherein, The main process creation module is used to receive the target application startup request, and create a main process for the target application corresponding to the target application startup request; The host keep alive process creation module is used to trigger the main process to call the function to create the host keep alive process; A keep-alive process creation module is used to trigger the host keep-alive process to call a function to create a keep-alive process, and after the keep-alive process is created, the keep-alive process is entrusted to the operating system; a connection module, used for constructing a connection between the main process and the keep-alive process, and triggering the main process and the keep-alive process to monitor each other based on the constructed connection; The connection module includes: a connection preprocessing unit, a connection unit and a monitoring unit, wherein, The connection preprocessing unit is used to trigger the main process to create a server socket, and the keep alive process to create a client socket; make the main process bind the server socket address, and monitor the client socket through the server socket connect; wait for client socket connection; The connection unit is used to trigger the client socket to establish a socket connection with the server socket; a monitoring unit, which triggers the main process and the keep-alive process to monitor each other based on the established connection; The connection unit includes: a keep-alive process host object creation sub-unit, a promoter sub-unit, a keep-alive process promoter sub-unit, an initialization sub-unit, a response sub-unit, and a response processing sub-unit, wherein, The keep-alive process host object creation subunit is used to trigger the main process to create a keep-alive process host object through the server socket, and assign a corresponding keep-alive process identifier to the keep-alive process host object; A start-up subunit, used to trigger the main process to use the created keep-alive process host object to start the keep-alive process, and send a resurrection instruction to the keep-alive process, where the resurrection instruction carries the keep-alive process identifier and the main process communication interface handle ; The keep-alive process startup subunit is used to trigger the start of the keep-alive process and receive the resurrection instruction from the main process; an initialization subunit, configured to trigger the keep-alive process to create a corresponding keep-alive process object through the client socket, and initialize the keep-alive process object; a response subunit, configured to trigger the keep-alive process object to send a start-up response message to the main process, where the start-up response message carries a keep-alive process communication interface handle and a keep-alive process identifier corresponding to the keep-alive process object; The response processing subunit is used to trigger the main process to determine the corresponding keep-alive process host object according to the keep-alive process identifier in the start-up response message after receiving the start-up response message of the keep-alive process, and host the keep-alive process The object sets the corresponding keepalive process communication interface handle; The monitoring processing module is used to start the closed process after monitoring that the main process or the keep-alive process is closed. 17. The apparatus according to claim 16, wherein the keep-alive process creation module comprises: a keep-alive process creation unit, a life cycle setting unit and a life cycle running unit, wherein, The keep-alive process creation unit is used to trigger the host keep-alive process to call a function to create a keep-alive process; a life cycle setting unit, used to set a life cycle for the created host keep-alive process; The life cycle running unit is used to run the set life cycle, and after the set life cycle ends, trigger the host keep-alive process to shut down naturally. 18. The apparatus according to claim 16, wherein the connection unit further comprises: a data transmission subunit, configured to trigger the main process to receive data from the keep-alive process through the main process communication interface handle, and host the keep-alive process through the main process The keepalive process communication interface handle of the object sends data to the corresponding keepalive process; the keepalive process receives data from the main process through the keepalive process communication interface handle, and sends data to the main process through the main process communication interface handle. 19. The apparatus according to claim 16, wherein the monitoring processing module comprises: a state parameter identification setting unit, a state parameter identification reading unit, a state parameter identification determining unit and a process restarting unit, wherein, a state parameter identifier setting unit, used for, after the first process is closed and is in the closed state, the monitoring component corresponding to the first process side acquires that the first process is in the closed state, and sets the state parameter identifier of the first process to the closed state; a state parameter identifier reading unit, used for reading the state parameter identifier of the first process through the second process connected by the socket; a state parameter identification determining unit, configured to determine, in the second process, that the state parameter identification of the first process is a closed state, and determine that the first process is closed; The process restarting unit is used to start the closed first process.