WO2015090250A1

WO2015090250A1 - Inter-process communication method and device

Info

Publication number: WO2015090250A1
Application number: PCT/CN2015/073166
Authority: WO
Inventors: 徐翠屏
Original assignee: 腾讯科技（深圳）有限公司
Priority date: 2013-12-16
Filing date: 2015-02-16
Publication date: 2015-06-25
Also published as: TW201525698A; CN104133728B; TWI528182B; CN104133728A

Abstract

Disclosed are an inter-process communication method and device. The method comprises: according to a target node to which data to be sent of a local node is to be sent, a target channel between the local node and the target node is determined; the data to be sent is written into a local shared storage space corresponding to the target channel; if the target node is a remote node, the target channel between the local node and the target node is a remote proxy channel between a local proxy node of the local node and a target proxy node of the target node, and the remote proxy channel is used to send the data to be sent in the local shared storage space to the target proxy node of the target node via the local proxy node of the local node. In the present solution, it is of no concern whether a communication process is running on a same host or a different host. Development efficiency is therefore increased, and errors are reduced.

Description

Method and device for inter-process communication

Technical field

The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for inter-process communication.

Background technique

Inter-process communication problems are often encountered during the development of network services. Inter-process communication is divided into process communication within the machine and process communication across machines. For process communication in the machine, it is generally used: pipeline, shared memory, message queue, Unix Socket (an operating system socket) and IPC (Inter-Process Communication). For process communication across machines, TCP (Transmission Control Protocol) / UDP (User Datagram Protocol) Socket (Socket) is generally used.

If network service development needs to communicate between processes in the machine and across machines, it is necessary to select the appropriate IPC mechanism for the specific scenario, and provide the upper layer application for the inter-machine and cross-machine process communication and encapsulation and development. Developers need to be well aware of the communication mechanisms and details between in-machine and cross-machine processes. This kind of application development is relatively inefficient and error-prone.

Summary of the invention

Embodiments of the present invention provide a method and apparatus for inter-process communication, which are used to improve development efficiency and reduce errors.

A method of interprocess communication, including:

Determining a target channel between the local node and the target node according to a target node to which the to-be-sent data of the local node is to be sent;

Writing the to-be-sent data into a local shared storage space corresponding to the target channel;

If the target node is a remote node, the target channel between the local node and the target node is a remote proxy channel between a local proxy node of the local node and a target proxy node of the target node. And transmitting, by the local proxy node of the local node, the to-be-sent data in the local shared storage space to a target proxy node of the target node by using the remote proxy channel.

A device for interprocess communication, including:

a channel determining unit, configured to determine, according to a target node to which the data to be sent of the local node is to be sent, a target channel between the local node and the target node;

a data writing unit, configured to write the to-be-sent data into a local shared storage space corresponding to the target channel determined by the channel determining unit;

a sending unit, configured to: if the target node is a remote node, the target channel between the local node and the target node is a local proxy node of the local node and a target proxy node of the target node And a remote proxy channel, by which the to-be-sent data in the local shared storage space is sent to a target proxy node of the target node by a local proxy node of the local node.

It can be seen from the above technical solutions that the embodiment of the present invention has the following advantages: the channel management scheme is adopted, and the cross-machine communication is realized through the proxy node, and the process that does not need to care about the communication is running on the same host or different hosts, so the developer does not need to Understand the mechanics and details of machine core cross-machine communication, so you can improve development efficiency and reduce errors.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, One of ordinary skill in the art would not pay for creation Other drawings can also be obtained from these drawings on the premise of sexual labor.

1 is a schematic flowchart of a method according to an embodiment of the present invention;

2 is a schematic structural diagram of a system according to an embodiment of the present invention;

3 is a schematic flowchart of a method according to an embodiment of the present invention;

4 is a schematic flowchart of a method according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method according to an embodiment of the present invention;

6 is a schematic flowchart of a method according to an embodiment of the present invention;

7 is a schematic flowchart of a method according to an embodiment of the present invention;

8 is a schematic structural view of an apparatus according to an embodiment of the present invention;

9 is a schematic structural diagram of an apparatus according to an embodiment of the present invention;

10 is a schematic structural diagram of an apparatus according to an embodiment of the present invention;

11 is a schematic structural view of an apparatus according to an embodiment of the present invention;

12 is a schematic structural diagram of an apparatus according to an embodiment of the present invention;

13 is a schematic structural diagram of an apparatus according to an embodiment of the present invention;

Figure 14 is a schematic structural view of an apparatus according to an embodiment of the present invention;

FIG. 15 is a schematic structural diagram of a terminal according to an embodiment of the present invention.

detailed description

The present invention will be further described in detail with reference to the accompanying drawings, in which FIG. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiment of the invention provides a method for inter-process communication, as shown in FIG. 1 , including the following steps.

101: Determine, according to a target node to which the to-be-sent data of the local node is to be sent, a target channel between the local node and the target node.

Step 102: Write the to-be-sent data into the local shared storage space corresponding to the target channel.

Further, the embodiment of the present invention further provides a scheme for performing flow control, where the scheme performs the transmission control at the sending end of the data, as follows: the data to be sent is written into the local shared storage space corresponding to the determined target channel. Previously, it also included:

Determining whether the target channel is in a pause state, if not in the pause state, writing the to-be-sent data to the determined local shared storage space corresponding to the target channel, and otherwise stopping writing data to the local shared storage space corresponding to the target channel, Until the above target channel returns to the non-suspended state.

In this embodiment, if the target channel is not in the pause state, the transmission of data will continue. Once the state of the target channel changes to the pause state, this will indicate that the transmission speed exceeds the limit of the receiver and the transmission needs to be stopped. The state of the target channel is specified by the receiving end, and a more detailed description will be given in the subsequent embodiments.

103: If the target node is a remote node, the target channel between the local node and the target node is a remote end between a local proxy node of the local node and a target proxy node of the target node. And a proxy channel, by using the remote proxy channel, to send the to-be-sent data in the local shared storage space to a target proxy node of the target node by using a local proxy node of the local node.

In addition, this embodiment may further include:

If the target node is another local node, the target channel is a local channel between the local node and the target node, and the data to be sent written in the local shared storage space passes through the local Channel reception.

In the above embodiment, the channel management scheme is adopted, and the cross-machine communication is realized through the proxy node. You don't need to care about whether the communication process is running on the same host or a different host, so developers don't need to understand the mechanism and details of the machine core's communication between machines, so it can improve development efficiency and reduce errors.

Further, the local device in the embodiment of the present invention refers to the device at the source end of the data to be sent. The device can also be used as the receiving end of the data, and the embodiment of the present invention further provides The device is used as a solution used by the receiving end of the data, and performs flow control at the receiving end of the data, as follows: The foregoing method further includes:

Receiving data from the remote proxy node through the local proxy node and determining whether the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node, and if so, to the remote end The proxy node sends a pause indication message instructing the remote proxy node to suspend sending data to the home proxy node.

Those skilled in the art will appreciate that if the received data does not reach the local threshold of the target channel, then the data can continue to be received. The local threshold is determined according to the storage space corresponding to the local target channel, and is used to prevent overflow.

Further, the embodiment of the present invention further provides an implementation scheme for how to resume data transmission after the target channel is suspended (ie, after the data transmission is suspended) after the traffic control is performed, as follows: The foregoing method further includes:

If the local target channel is in a suspended state and there is no data, a recovery indication is sent to the remote proxy node, indicating that the remote proxy node continues to write data to the target channel.

It can be understood that if the local target channel is not in the pause state, it should currently be in the process of sending data. If the local target channel is in the pause state, then there should be no data communication at present. In this case, it is necessary to determine under what circumstances to resume communication. In this embodiment, there is no data in the target channel, in fact, if the target It is also possible that the data amount of the channel is smaller than the total data capacity setting ratio of the target channel, which is not limited by the embodiment of the present invention.

Further, the embodiment of the present invention further provides a node creation scheme, including a local node creation and a channel creation scheme according to the indication of the target proxy node, and the specific scheme is as follows: before determining the target channel according to the target node of the data to be sent, Also includes:

a local proxy node creates the local node and establishes a target channel between the local proxy node and the target proxy node, and allocates a local shared storage space for the target channel; or the local proxy node receives the target proxy node The channel information that is sent, if the channel information is not stored locally, the target channel is created, and the target channel is monitored for data reception.

Further, the embodiment of the present invention further provides a technical solution for how to synchronize information of channels across devices, and uses proxy nodes to complete synchronization of channel information, as follows: before sending the data to be sent to the target proxy node through the local proxy node, Also includes:

Reading a configuration file, determining an internet protocol address and a port number of the target proxy node, and establishing a transmission control protocol TCP connection between the local proxy node and the target proxy node by using the internet protocol address and a port number; Transmitting, by the TCP connection, channel information about the target channel created by the local proxy node to a target proxy node, so that the target proxy node establishes the target channel according to the channel information.

Further, the embodiment of the present invention further provides a scheme for channel deletion, which is specifically as follows: the foregoing method further includes:

If the local node is closed, the channel between the local node and the remote node is closed, and the channel between the local node and the remote node is not used by other processes, and the local node and the remote node are destroyed. The channel between the end nodes.

It can be understood that the purpose of destroying the channel is to release the unnecessary storage space, and the specific operation may be to destroy the information in the storage space corresponding to the channel. The process of destruction may be to release the storage space, such as memory, so that it can be used again, and does not necessarily need to perform storage space initialization.

The following embodiments respectively illustrate several important aspects of the embodiments of the present invention.

The embodiment of the invention adopts a middleware scheme based on shared memory for inter-process communication. Developers can use it to easily exchange data between processes without worrying about whether the processes that need to exchange data are running on the same host or on different hosts. When processes are on the same host, data is transferred through shared memory; for processes on different hosts, the middleware transfers data to the remote host via the agent/agent via TCP/IP.

First, the middleware scheme shown in Figure 2 contains the following parts:

Host1 and host2 are two host devices; host1 contains two data sending and receiving points (peer), peer 1 and peer2, which belong to their respective processes; host2 contains two data sending and receiving points (peer), peer3 and The peer 4s are respectively in the process of the present invention; each of the hosts may include a plurality of processes, and each of the processes may include a plurality of peers. FIG. 2 is only a schematic diagram and should not be construed as limiting the embodiments of the present invention. The process in which the Agent is executing is a proxy service, which can be called a proxy node. The following sections describe the parts shown in Figure 2 in detail as follows:

Data peer: The middleware is a client development package provided by the developer. The development package is used to create a specific peer to receive and send messages.

Channel: It is actually a shared memory. When creating a peer, the middleware creates a channel with the same name and binds to the peer. Each channel has a unique id, so there are multiple channel collections with the same channel name. The peer receives data through this channel; when sending data, the middleware first finds the channel bound to the target peer and writes the data to the target channe. The channel is divided into a local channel and a remote channel proxy. The remote proxy channels shown in Figure 2 are: host2_channel4_proxy and host2_channel3_proxy in host1; host1_channel1_proxy and host1_channel2_proxy in host2.

Channel index: actually a piece of shared memory. Store all The shared memory key (keyword) corresponding to the channel.

Message: Each time the data sent by the peer's send function is treated as a message, the peer's recv function (a function for receiving data from a connected datagram or streaming socket) is called each time. Receive a complete message.

The middleware mainly consists of two components:

(1) A client development kit for developers.

(2) A proxy service agent that performs communication between processes across machines.

Second, the important data structure

The embodiment of the present invention is an inter-process communication middleware based on shared memory, and the data structure of the channel, the channel index, and the message in the shared memory is as follows:

(1) Channel, as shown in Table 1 below

Table 1

(2) Channel index, as shown in Table 2 below:

Table 2

(3) Message (message):

The message is the basic unit of middleware data transmission. The message will be reported as a data packet during the transmission process. The maximum length of the data packet is 8K bytes. When the length of the message exceeds 8K bytes, it will be fragmented. That is, divided into multiple packet transmissions, the receiver will assemble these fragments into a complete message. The structure of the packet is shown in Table 3 below:

table 3

Third, the introduction of important processes

(1) Channel creation: The creation process of the channel is divided into a local channel actively created by the middleware client and a remote proxy channel created by the proxy service agent receiving the channel information transmitted from the peer end.

The process of the local channel actively created by the middleware client is as shown in FIG. 3, including:

301: Create a local peer;

302: Bind access channel index, obtain the channel shm key and channel sem key corresponding to the peer;

The information and usage of the above channel index are described in the previous embodiment. The channel shm key and the channel sem key are keywords for identifying channel shm and channel sem respectively; channel shm is a channel for receiving data, channel sem It is the channel used for searching.

303: Create and bind a channel shm key and a channel sem key;

304: Initialize channel shm;

This step initializes the storage space corresponding to the channel. As shown in Figure 2, channel1 to channel 4.

305: Add the channel to the channel manager and listen to the channel for data reception.

The proxy service agent receives the process of the remote proxy channel created by the channel information transmitted by the peer end, as shown in FIG. 4, including:

401: The agent receives the channel information sent by the peer end.

Specifically, it may be channel information sent by the peer agent.

402: Determine whether the channel corresponding to the received channel information exists, if yes, the process may end; otherwise, enter 403;

403: Create a remote proxy peer;

For example, host2_channel4_proxy, host2_channel3_proxy, host1_channel1_proxy, and host1_channel2_proxy shown in Figure 2 are channels corresponding to the remote proxy peer.

404: Bind access channel index to obtain the channel shm key and channel sem key corresponding to the peer;

405: Create and bind channel shm key and channel sem key;

406: Initialize channel shm;

407: Add the channel to the channel manager and listen to the channel for data reception.

In this embodiment, the channel is created, the channel information is maintained in the memory, and the corresponding channel shared memory is created.

(2) Cross-machine channel synchronization: In this embodiment, it can be deployed as a front-end agent (agent) and a back-end agent. The front-end agent needs to read remotehost.xml (the information of the remote host) to obtain all back-end agent information, including IP. (Internet Protocol Address) and Port (port) information, and actively establish a TCP connection with these backend agents for communication. Host1 and host2 perform channel synchronization. The specific process is shown in Figure 5. It includes:

501A: Read the configuration file to obtain the channel index configuration information that has been included in the Agent IP and the port.

In this embodiment, the configuration file of the agent needs to include the following information:

1, Agent IP and Port;

2, channel index shared memory key, semaphore key;

3. The maximum number of manageable channels;

4, channel corresponds to the maximum size of shared memory.

502A: Initialize channel index shm;

503A: Read remotehost.xml to obtain IP information of all peer Agents and ports;

504A: Create a TCP connection with the peer agent;

505A: Obtain all new non-Agent created channels from the channel indx and send them to the peer agent.

506A: Receive new channel information sent by the peer agent, and establish a corresponding remote channel proxy.

501B to 506B shown in FIG. 5 are steps completely corresponding to the above-described steps 501A to 506A, and will not be described again.

(3), message transmission, as shown in Figure 6, including the following steps:

601: Call the send method of the peer;

602: Find a corresponding target channel list according to the target peer name to the channel manager;

603: Take the target channel from the channel list;

604: Write data to the shm corresponding to the above channel;

605: Determine whether the channel corresponding to the above shm is a local channel; if yes, enter 606, otherwise enter 607;

606: The local channel receives the data.

607: The remote proxy channel receives the data.

608: The proxy agent sends the data received by the remote proxy channel to the peer proxy agent.

In the present embodiment, the following two points need to be explained as follows:

1. In the middleware of this embodiment, the channel manager cyclically detects and reads whether there is data receiving in the channel created by the process, and refreshes the timestamp attribute (timestamp) of the channel every time, if there is data reception, To the user. At the same time, the local process can also obtain the channel created by other processes through the channel index, and periodically check whether the channel timestamp attribute (timestamp) is updated to determine whether the channel has been closed. If it is closed, the channel memory information will be destroyed. Refer specifically to the description of channel destruction in the subsequent embodiments.

2. In this embodiment, multiple channels (channel ids) may be obtained through the target channel name, and one message channel is acquired each time as a target channel. This mechanism is also well-balanced.

(4) Flow control, the specific process is shown in Figure 7, including the following steps:

701: The peer invokes the send method of the peer;

702: Obtain a channel state from the channel state information stored in the channel shm.

703: Determine whether the target channel is in a suspended state, if yes, suspend data transmission; if not, enter 704;

704: Write data to the corresponding target channel shm;

705: Write data to the shared memory;

706: Agent 1 reads the remote channel sham data and sends it to the peer agent (Agent2).

707: Receive data sent by the peer agent.

708: Obtain channel data status.

709: Determine whether the channel data reaches the threshold; if yes, enter 710, otherwise enter 712;

710: Send a suspension receiving indication to the peer agent;

711: Receive the peer channel pause request and set the channel state to pause; Set the channel state to pause;

712: Write data to the corresponding channel shm.

713: If the channel state is paused, the step is performed periodically: periodically determining that the channel state is paused and there is no data in the channel, the channel state is restored to normal. The method of returning to the normal manner may be to send an indication message to the peer agent, indicating that the channel status is restored to normal.

(5) Channel destruction, in this embodiment the channel destruction rules are as follows:

1. The created peer is closed, and the corresponding channel memory information will be destroyed.

2. After receiving the connection close request of the peer agent, the channel memory information that is transmitted by the agent and established is completely destroyed.

3. The channel may be used by multiple processes at the same time. Only all processes destroy the channel memory information, and the shared memory corresponding to the channel will be deleted from the system.

The present invention is a middleware solution for inter-process communication based on shared memory. Provide development kits and cross-machine communication agents. You only need to create specific Peer and channel to communicate with the target Peer and channel. Don't worry if the process that needs communication is running on the same host or on a different host.

An embodiment of the present invention further provides an apparatus for inter-process communication, as shown in FIG. 8, including:

a channel determining unit 801, configured to determine, according to a target node to which the data to be sent of the local node is to be sent, a target channel between the local node and the target node;

a data writing unit 802, configured to write the to-be-sent data into a local shared storage space corresponding to the target channel determined by the channel determining unit;

a sending unit 804, configured to: if the target node is a remote node, the target channel between the local node and the target node is a local proxy node of the local node and a target proxy of the target node a remote proxy channel between the nodes, using the remote proxy channel The local proxy node passing the local node transmits the to-be-sent data in the local shared storage space to a target proxy node of the target node.

In the embodiment of the present invention, the method may further include: a local channel unit 803, configured to: if the target node is another local node, the target channel is a local channel between the local node and the target node, Then, the data to be sent written in the local shared storage space is received through the local channel.

In the above embodiment, the channel management scheme is adopted to implement cross-machine communication through the proxy node, and it is not necessary to care whether the communication process runs on the same host or different hosts, so the developer does not need to understand the mechanism and details of the inter-machine communication between the machine cores. This can improve development efficiency and reduce errors.

Further, the local device in the embodiment of the present invention refers to the device at the source end of the data to be sent. The device can also be used as the receiving end of the data, and the embodiment of the present invention further provides The device is used as a receiving end of the data, and performs flow control at the receiving end of the data, as follows: As shown in FIG. 9, the foregoing apparatus further includes:

The receiving unit 901 is configured to receive data from the remote proxy node by using the local proxy node;

a threshold determining unit 902, configured to determine whether the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node;

The sending unit 804 is further configured to: after the threshold determining unit 902 determines that the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node, then to the remote proxy node. Sending a pause indication message instructing the remote proxy node to suspend sending data to the home agent node.

Those skilled in the art will appreciate that if the received data does not reach the local threshold of the target channel, then the data can continue to be received. The above threshold is in accordance with the above local target The local storage space corresponding to the track is determined to prevent overflow.

Further, the embodiment of the present invention further provides an implementation scheme of how to resume data transmission after the target channel is suspended (ie, after the data transmission is suspended), as follows: As shown in FIG. 10, the foregoing apparatus further includes:

a first determining unit 1001, configured to determine whether a channel between the local proxy node and the remote proxy node is in a suspended state, and whether there is data;

The sending unit 804 is further configured to: if the first determining unit 1001 determines that the channel between the local proxy node and the remote proxy node is in a suspended state and has no data, send a recovery indication to the remote proxy node. Instructing the remote proxy node to continue transmitting data to the home agent node.

Further, the embodiment of the present invention further provides a scheme for performing flow control, where the scheme performs transmission control at a data sending end, as follows: as shown in FIG. 11, the foregoing apparatus further includes:

The second determining unit 1101 is configured to determine whether the target channel is in a suspended state before writing the to-be-sent data into the local shared storage space corresponding to the target channel;

The data writing unit 802 is further configured to: if the second determining unit 1101 determines that the target channel is not in a suspended state, write the to-be-sent data into the shared storage space corresponding to the determined target channel, otherwise stop the foregoing The shared memory space corresponding to the target channel writes data until the target channel returns to the non-suspended state.

In this embodiment, if the target channel is not in the pause state, then the data will be sent. If the status of the target channel changes to a paused state, this will indicate that the transmission speed exceeds the receiver's limit and needs to stop sending. The state of the target channel is specified by the receiving end, and a more detailed description will be given in the subsequent embodiments.

Further, the embodiment of the present invention further provides a node creation scheme, including a local node creation and a channel creation scheme according to the indication of the peer proxy node. The specific solution is as follows: As shown in FIG. 12, the foregoing apparatus further includes:

The node management unit 1201 is configured to create the local node and establish the local proxy before determining a target channel between the local node and the target node according to a target node to which the data to be sent of the local node is to be sent. a target channel between the node and the target proxy node, the local shared storage space is allocated to the target channel; or the channel information sent by the target proxy node is received, and if the channel information is not stored locally, the Target channel and monitor the target channel for data reception.

Further, the embodiment of the present invention further provides a technical solution for how to synchronize the information of the channel across the device, and uses the proxy node to complete the synchronization of the channel information, as follows: As shown in FIG. 13, the foregoing apparatus further includes:

a synchronization management unit 1301, configured to send, by using the remote proxy channel, the to-be-sent data in the local shared storage space to a target proxy node of the target node by using a local proxy node of the local node, Reading a configuration file, determining an internet protocol address and a port number of the target proxy node, and establishing a transmission control protocol TCP connection between the local proxy node and the target proxy node by using the internet protocol address and a port number; Transmitting, by the TCP connection, channel information about the target channel created by the local proxy node to a target proxy node, so that the target proxy node establishes the target channel according to the channel information.

Optionally, the embodiment of the present invention further provides a channel deletion scheme, which is specifically as follows: the synchronization management unit 1301 is further configured to: if the local node is closed, shut down the local node and the remote node. A channel between end nodes, and a channel between the local node and the remote node is not used by other processes, and the channel between the local node and the remote node is destroyed.

The embodiment of the present invention further provides an apparatus for inter-process communication, as shown in FIG. 14, comprising: a receiver 1401, a transmitter 1402, a processor 1403, and a memory 1404;

The processor 1403 is configured to determine, according to a target node to which the data to be sent of the local node is to be sent, a target channel between the local node and the target node, and write the to-be-sent data into the target channel. Within the local shared storage space; if the target node is a remote node, the target channel between the local node and the target node is a local proxy node of the local node and a target proxy node of the target node And a remote proxy channel, by which the to-be-sent data in the local shared storage space is sent to a target proxy node of the target node by a local proxy node of the local node. In addition, the processor 1403 may be further configured to: if the target node is another local node, the target channel is a local channel between the local node and the target node, and then write the local shared storage space. The data to be transmitted within is received through the local channel.

Further, the embodiment of the present invention further provides a scheme for performing flow control, where the scheme performs transmission control at a transmitting end of the data, as follows: the processor 1403 is further configured to write the to-be-sent data into the target. Before the channel corresponds to the local shared storage space, determine the location Whether the target channel is in a pause state; if the target channel is in a pause state, stopping writing data to the local shared storage space corresponding to the target channel until the target channel returns to a non-suspended state.

Further, the local device in the embodiment of the present invention refers to the device at the source end of the data to be sent. The device can also be used as the receiving end of the data, and the embodiment of the present invention further provides The device is used as a receiving end of the data, and performs flow control at the receiving end of the data, as follows: the processor 1403 is further configured to receive data from the remote proxy node through the local proxy node, and determine the received data. Whether the data has reached a local threshold of a channel between the local proxy node and the remote proxy node, and if so, sending a pause indication message to the remote proxy node, instructing the remote proxy node to suspend to the The local proxy node sends the data.

It will be understood by those skilled in the art that if the received data does not reach the threshold of the local target channel, the data can continue to be received. The above threshold is determined according to the storage space corresponding to the local target channel described above, and is used to prevent overflow.

Further, the embodiment of the present invention further provides an implementation scheme of how to resume data transmission after the target channel is suspended (that is, after the data transmission is suspended) after the traffic control is performed, as follows: the processor 1403 is further configured to: if the local When the channel between the proxy node and the remote proxy node is in a suspended state and there is no data, a recovery indication is sent to the remote proxy node, indicating that the remote proxy node continues to send data to the local proxy node.

It can be understood that if the local target channel is not in the pause state, it should currently be in the process of sending data. If the above local target channel is in the pause state, then it should be If there is no data communication, it is necessary to determine under what circumstances to resume communication. In this embodiment, there is no data in the target channel. In fact, if the data volume of the target channel is smaller than the total data capacity setting of the target channel. The ratio is also possible, and the embodiment of the invention does not limit this uniquely.

Further, the embodiment of the present invention further provides a node creation scheme, including a local node creation and a channel creation scheme according to the indication of the peer proxy node. The specific solution is as follows: the processor 1403 is further configured to be based on the local node. Before the target node to which the to-be-sent data is to be sent determines the target channel between the local node and the target node, create the local node, and establish a target between the local proxy node and the target proxy node Channel, the local shared storage space is allocated to the target channel; or, receiving channel information sent by the target proxy node, if the channel information is not stored locally, creating the target channel, and monitoring whether the target channel has Data reception.

Further, the embodiment of the present invention further provides a technical solution for how to synchronize the information of the channel across the device, and uses the proxy node to complete the synchronization of the channel information. The processor 1403 is further configured to use the remote proxy channel to pass the Before the local proxy node of the local node sends the to-be-sent data in the local shared storage space to the target proxy node of the target node, the configuration file is read, and the Internet Protocol address and port number of the target proxy node are determined. And establishing, by the internet protocol address and the port number, a transmission control protocol TCP connection between the local proxy node and the target proxy node; and the target channel created by the local proxy node by using the TCP connection The channel information is sent to the target proxy node, so that the target proxy node establishes the target channel according to the channel information.

Further, the embodiment of the present invention further provides a channel deletion scheme, which is specifically as follows: the processor 1403 is further configured to: if the local node is closed, close a channel between the local node and the remote node, and the The channel between the local node and the remote node is not used by other processes, and the channel between the local node and the remote node is destroyed.

The embodiment of the present invention further provides a terminal. As shown in FIG. 15 , for the convenience of description, only parts related to the embodiment of the present invention are shown. If the specific technical details are not disclosed, please refer to the method part of the embodiment of the present invention. The terminal may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), an in-vehicle computer, and the terminal is a mobile phone as an example:

FIG. 15 is a block diagram showing a partial structure of a mobile phone related to a terminal provided by an embodiment of the present invention. Referring to FIG. 15 , the mobile phone includes: a radio frequency (RF) circuit 1510 , a memory 1520 , an input unit 1530 , a display unit 1540 , a sensor 1550 , an audio circuit 1560 , a wireless fidelity (WiFi) module 1570 , and a processor 1580 . And power supply 1590 and other components. It will be understood by those skilled in the art that the structure of the handset shown in FIG. 15 does not constitute a limitation to the handset, and may include more or less components than those illustrated, or some components may be combined, or different components may be arranged.

The following describes the components of the mobile phone in detail with reference to FIG. 15:

The RF circuit 1510 can be used for receiving and transmitting signals during the transmission or reception of information or during a call. Specifically, after receiving the downlink information of the base station, the processing is processed by the processor 1580. In addition, the data designed for the uplink is sent to the base station. Generally, RF circuit 1510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuitry 1510 can also communicate with the network and other devices via wireless communication. The above wireless communication may use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division). Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), E-mail, Short Messaging Service (SMS), and the like.

The memory 1520 can be used to store software programs and modules, and the processor 1580 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 1520. The memory 1520 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to Data created by the use of the mobile phone (such as audio data, phone book, etc.). Moreover, memory 1520 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1530 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the handset. Specifically, the input unit 1530 may include a touch panel 1531 and other input devices 1532. The touch panel 1531, also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 1531 or near the touch panel 1531. Operation), and drive the corresponding connecting device according to a preset program. Optionally, the touch panel 1531 may include two parts: a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 1580 is provided and can receive commands from the processor 1580 and execute them. In addition, the touch panel 1531 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1531, the input unit 1530 may also include other input devices 1532. Specifically, other input devices 1532 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.

The display unit 1540 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone. The display unit 1540 can include a display panel 1541. Alternatively, the display panel 1541 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 1531 may cover the display panel 1541. After the touch panel 1531 detects a touch operation on or near the touch panel 1531, the touch panel 1531 transmits to the processor 1580 to determine the type of the touch event, and then the processor 1580 according to the touch event. The type provides a corresponding visual output on display panel 1541. Although the touch panel 1531 and the display panel 1541 are used as two independent components to implement the input and input functions of the mobile phone in FIG. 15, in some embodiments, the touch panel 1531 and the display panel 1541 may be integrated. Realize the input and output functions of the phone.

The handset may also include at least one type of sensor 1550, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1541 according to the brightness of the ambient light, and the proximity sensor may close the display panel 1541 and/or when the mobile phone moves to the ear. Or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the mobile phone can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, no longer Narration.

An audio circuit 1560, a speaker 1561, and a microphone 1562 can provide an audio interface between the user and the handset. The audio circuit 1560 can transmit the converted electrical data of the received audio data to the speaker 1561, and convert it into a sound signal output by the speaker 1561. On the other hand, the microphone 1562 converts the collected sound signal into an electrical signal, and the audio circuit 1560. After receiving, it is converted into audio data, and then processed by the audio data output processor 1580, sent to, for example, another mobile phone via the RF circuit 1510, or outputted to the memory 1520 for further processing.

WiFi is a short-range wireless transmission technology. The mobile phone through the WiFi module 1570 can help users to send and receive e-mail, browse the web and access streaming media, etc. It provides users with wireless broadband Internet access. Although FIG. 15 shows the WiFi module 1570, it can be understood that it does not belong to the essential configuration of the mobile phone, and may be omitted as needed within the scope of not changing the essence of the invention.

The processor 1580 is a control center for the handset that connects various portions of the entire handset using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 1520, and invoking data stored in the memory 1520, The phone's various functions and processing data, so that the overall monitoring of the phone. Optionally, the processor 1580 may include one or more processing units; preferably, the processor 1580 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like. The modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 1580.

The handset also includes a power source 1590 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 1580 via a power management system to manage functions such as charging, discharging, and power management through the power management system.

Although not shown, the mobile phone may further include a camera, a Bluetooth module, and the like, and details are not described herein again.

In the embodiment of the present invention, the processor 1580 included in the terminal further has the following functions:

Determining, by the target node to which the data to be sent of the local node is to be sent, a target channel between the local node and the target node; and writing the to-be-sent data into a local shared storage space corresponding to the target channel; The target node is a remote node, and the target channel between the local node and the target node is a remote proxy channel between a local proxy node of the local node and a target proxy node of the target node, And transmitting, by the local proxy node of the local node, the to-be-sent data in the local shared storage space to a target proxy node of the target node by using the remote proxy channel. In this embodiment, the processor 1580 also And if the target node is another local node, the target channel is a local channel between the local node and the target node, and the data to be sent in the local shared storage space is written. Local channel reception.

Further, the embodiment of the present invention further provides a scheme for performing flow control, where the scheme performs transmission control at the transmitting end of the data, as follows: the processor 1580 is further configured to write the to-be-sent data into the target. Before the local shared storage space corresponding to the channel, determining whether the target channel is in a suspended state, if yes, stopping writing data to the local shared storage space corresponding to the target channel until the target channel returns to a non-suspended state.

Further, the local device in the embodiment of the present invention refers to the device at the source end of the data to be sent. The device can also be used as the receiving end of the data, and the embodiment of the present invention further provides The device is used as a solution used by the receiving end of the data, and performs flow control at the receiving end of the data, as follows: the processor 1580 is further configured to receive data from the remote proxy node through the local proxy node, and determine the received data. Whether the data has reached a local threshold of a channel between the local proxy node and the remote proxy node, and if so, sending a pause indication message to the remote proxy node, instructing the remote proxy node to suspend to the The local proxy node sends the data.

Those skilled in the art can understand that if the received data does not reach the local The threshold of the target channel can continue to receive data. The above threshold is determined according to the storage space corresponding to the local target channel described above, and is used to prevent overflow.

Further, the embodiment of the present invention further provides an implementation scheme of how to resume data transmission after the target channel is suspended (ie, after the data transmission is suspended) after the traffic control is performed, as follows: the processor 1580 is further configured to be used if the local When the channel between the proxy node and the remote proxy node is in a suspended state and there is no data, a recovery indication is sent to the remote proxy node, indicating that the remote proxy node continues to send data to the local proxy node.

Further, the embodiment of the present invention further provides a node creation scheme, including a local node creation and a channel creation scheme according to the indication of the peer proxy node, and the specific scheme is as follows: the processor 1580 is further configured to be based on the local node. Before the target node to which the to-be-sent data is to be sent determines the target channel between the local node and the target node, create the local node, and establish a target between the local proxy node and the target proxy node Channel, the local shared storage space is allocated to the target channel; or, receiving channel information sent by the target proxy node, if the channel information is not stored locally, creating the target channel, and monitoring whether the target channel has Data reception.

Further, the embodiment of the present invention further provides a technical solution for how to synchronize the information of the channel across the device, and uses the proxy node to complete the synchronization of the channel information. The processor 1580 is further configured to use the remote proxy channel to pass the a local proxy node of the local node sends the to-be-sent data in the local shared storage space to a target proxy node of the target node And reading a configuration file, determining an internet protocol address and a port number of the target proxy node, and establishing a transmission control protocol TCP between the local proxy node and the target proxy node by using the internet protocol address and the port number And connecting, by the TCP connection, channel information about the target channel created by the local proxy node to a target proxy node, so that the target proxy node establishes the target channel according to the channel information.

Further, the embodiment of the present invention further provides a channel deletion scheme, which is specifically as follows: the processor 1580 is further configured to: if the local node is closed, close a channel between the local node and the remote node, and the The channel between the local node and the remote node is not used by other processes, and the channel between the local node and the remote node is destroyed.

It should be noted that, in the foregoing device embodiments, the included units are only divided according to functional logic, but are not limited to the foregoing division, as long as the corresponding functions can be implemented; in addition, the specific names of the functional units It is also for convenience of distinguishing from each other and is not intended to limit the scope of protection of the present invention.

In addition, those skilled in the art can understand that all or part of the steps in implementing the foregoing method embodiments may be performed by a program to instruct related hardware, and the corresponding program may be stored in a computer readable storage medium. The storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the embodiments of the present invention. All should be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A method for inter-process communication, characterized in that it comprises:

Determining a target channel between the local node and the target node according to a target node to which the to-be-sent data of the local node is to be sent;

Writing the to-be-sent data into a local shared storage space corresponding to the target channel;

If the target node is a remote node, the target channel between the local node and the target node is a remote proxy channel between a local proxy node of the local node and a target proxy node of the target node. And transmitting, by the local proxy node of the local node, the to-be-sent data in the local shared storage space to a target proxy node of the target node by using the remote proxy channel.
The method of claim 1 further comprising:

Receiving data from the remote proxy node through the local proxy node and determining whether the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node, and if so, to the remote end The proxy node sends a pause indication message instructing the remote proxy node to suspend sending data to the home proxy node.
The method of claim 2, further comprising:

And if the channel between the local proxy node and the remote proxy node is in a suspended state and has no data, sending a recovery indication to the remote proxy node, indicating that the remote proxy node continues to send data to the local proxy node .
The method of claim 1, further comprising: before the data to be sent is written into the local shared storage space corresponding to the target channel,

Determining whether the target channel is in a suspended state, and if so, stopping writing data to the local shared storage space corresponding to the target channel until the target channel returns to a non-suspended state.
The method according to claim 1, wherein before determining the target channel between the local node and the target node according to the target node to which the data to be transmitted of the local node is to be sent, the method further includes:

a local proxy node creates the local node and establishes a target channel between the local proxy node and the target proxy node, and allocates a local shared storage space for the target channel; or The local proxy node receives the channel information sent by the target proxy node. If the channel information is not stored locally, the target channel is created, and the target channel is monitored for data reception.
The method according to any one of claims 1 to 5, wherein the data to be transmitted in the local shared storage space is sent to the local proxy node of the local node by using the remote proxy channel to Before the target proxy node of the target node, the method further includes:

Reading a configuration file, determining an internet protocol address and a port number of the target proxy node, and establishing a transmission control protocol TCP connection between the local proxy node and the target proxy node by using the internet protocol address and a port number; Transmitting, by the TCP connection, channel information about the target channel created by the local proxy node to a target proxy node, so that the target proxy node establishes the target channel according to the channel information.
The method of claim 6 further comprising:

If the local node is closed, the channel between the local node and the remote node is closed, and the channel between the local node and the remote node is not used by other processes, and the local node and the remote node are destroyed. The channel between the end nodes.
The method of claim 1 further comprising:

If the target node is another local node, the target channel is a local channel between the local node and the target node, and the data to be sent written in the local shared storage space passes through the local Channel reception.
The method according to claim 8, wherein before determining the target channel between the local node and the target node according to the target node to which the data to be transmitted of the local node is to be sent, the method further includes:

The local proxy node creates the local node and establishes a target channel between the local node and the target node, and allocates a local shared storage space for the target channel.
A device for inter-process communication, characterized in that it comprises:

a channel determining unit, configured to determine, according to a target node to which the data to be sent of the local node is to be sent, a target channel between the local node and the target node;

a data writing unit, configured to write the to-be-sent data into a local shared storage space corresponding to the target channel determined by the channel determining unit;

a sending unit, configured to: if the target node is a remote node, the target channel between the local node and the target node is a local proxy node of the local node and a target proxy node of the target node And a remote proxy channel, by which the to-be-sent data in the local shared storage space is sent to a target proxy node of the target node by a local proxy node of the local node.
The device according to claim 10, further comprising:

a receiving unit, configured to receive data from the remote proxy node by using the local proxy node;

a threshold determining unit, configured to determine whether the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node;

The sending unit is further configured to: after the received data has reached a local threshold of a channel between the local proxy node and the remote proxy node, send a pause indication message to the remote proxy node, indicating The remote proxy node suspends sending data to the local proxy node.
The device according to claim 11, further comprising:

a first determining unit, configured to determine whether a channel between the local proxy node and the remote proxy node is in a suspended state, and whether there is data;

The sending unit is further configured to: if the channel between the local proxy node and the remote proxy node is in a suspended state and has no data, send a recovery indication to the remote proxy node, indicating the remote proxy The node continues to send data to the home agent node.
The device according to claim 10, characterized in that

a second determining unit, configured to determine whether the target channel is in a suspended state before writing the to-be-sent data into a local shared storage space corresponding to the target channel;

The data writing unit is further configured to stop writing data to the local shared storage space corresponding to the target channel if the target channel is in a suspended state, until the target channel returns to a non-suspended state.
The device according to claim 10, further comprising:

a node management unit, configured to create the local node and establish the local proxy node before determining a target channel between the local node and the target node according to a target node to which the to-be-sent data of the local node is to be sent a target channel between the target proxy node and a local shared storage space; or receiving the target proxy node The channel information sent, if the channel information is not stored locally, the target channel is created, and the target channel is monitored for data reception.
The device according to any one of claims 10 to 14, further comprising:

a synchronization management unit, configured to read the to-be-sent data in the local shared storage space to the target proxy node of the target node by using the remote proxy channel by the local proxy node of the local node Taking a configuration file, determining an internet protocol address and a port number of the target proxy node, and establishing, by using the internet protocol address and the port number, a transmission control protocol TCP connection between the local proxy node and the target proxy node; The TCP connection sends channel information about the target channel created by the local proxy node to a target proxy node, so that the target proxy node establishes the target channel according to the channel information.
The device of claim 15 wherein:

The synchronization management unit is further configured to: if the local node is closed, close a channel between the local node and the remote node, and the channel between the local node and the remote node is not used by another process. , destroying the channel between the local node and the remote node.
The device according to claim 10, further comprising:

a local channel unit, configured to: if the target node is another local node, the target channel is a local channel between the local node and the target node, and then write to the local shared storage space Transmit data is received through the local channel.
The device according to claim 17, further comprising:

a node management unit, configured to create the local node and establish the local node before determining a target channel between the local node and the target node according to a target node to which the data to be sent of the local node is to be sent A target channel between the target nodes, the local shared storage space is allocated to the target channel.