CN111400055A - Method, device, equipment and storage medium for communication among multiple processes - Google Patents

Abstract

The present invention provides a method, device, device and storage medium for multi-process communication, and relates to the technical field of communication. The method for multi-process communication includes: receiving a communication instruction from a calling process, where the communication instruction includes an interface identifier of the called process in the operating system; based on the interface identifier of the called process, calling and calling in the shared memory of the operating system and the called process Interface definition information matched with the interface identifier of the process, the interface definition information is used to define the interface of the process; according to the interface definition information matched with the interface identifier of the called process, the communication between the calling process and the called process is performed. By using the technical scheme of the present invention, the efficiency of multi-process communication can be improved.

Description

Method, apparatus, device and storage medium for multi-process communication

technical field

The present invention relates to the field of communication technologies, and in particular, to a method, apparatus, device and storage medium for multi-process communication.

Background technique

During the development of the application layer of the operating system, communication between different processes will be required. For example, if the communication between process A and process B needs to be performed, the developer needs to manually define the relevant information of the process A, and then manually search for the relevant information of the process B. Using the relevant information of the process A and the relevant information of the process B, a communication method between the process A and the process B is defined, so as to initiate the communication between the process A and the process B.

As the number of applications increases, to achieve inter-process communication requires a lot of manual operation and maintenance by developers, which takes a long time and reduces the efficiency of multi-process communication.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method, apparatus, device and storage medium for multi-process communication, which can improve the efficiency of multi-process communication.

In a first aspect, an embodiment of the present invention provides a method for multi-process communication, including: receiving a communication instruction from a calling process, where the communication instruction includes an interface identifier of the called process in the operating system; based on the interface identifier of the called process, Call the interface definition information matching the interface identifier of the called process in the shared memory of the operating system, and the interface definition information is used to define the interface of the process; Communication between calling processes.

In some possible embodiments, the above method for multi-process communication further includes: writing interface definition information of all processes into the shared memory of the operating system.

In some possible embodiments, performing the communication between the calling process and the called process according to the interface definition information matched with the interface identifier of the called process includes: according to the interface definition information matched with the interface identifier of the called process, The interface pointer corresponding to the interface definition information is called to access the execution address of the called process; the response information from the called process is received, and the response information is returned to the calling process.

In some possible embodiments, an executable file is stored in the shared memory, and the above method for multi-process communication further includes: compiling the interface definition information of the called process into an interface definition section in the executable file, so that the executable When the file is executed, the interface pointer corresponding to the interface definition information is called.

In some possible embodiments, the above method for multi-process communication further includes: updating interface definition information of the process in the shared memory of the operating system.

In some possible embodiments, the interface definition information includes an interface identifier, a process to which the interface corresponding to the interface identifier belongs, and channel information of a process to which the interface corresponding to the interface identifier belongs.

In a second aspect, an embodiment of the present invention provides an apparatus for multi-process communication, including: a receiving module for receiving a communication instruction from a calling process, where the communication instruction includes an interface identifier of the called process in an operating system; a calling module, It is used to call the interface definition information matching the interface identifier of the called process in the shared memory of the operating system based on the interface identifier of the called process, and the interface definition information is used to define the interface of the process; the execution module is used to The interface identification information of the process matches the interface definition information, and the communication between the calling process and the called process is performed.

In some possible embodiments, the apparatus for multi-process communication further includes: a definition module, configured to write the interface definition information of all processes into the shared memory of the operating system.

In some possible embodiments, the definition module is further configured to update the interface definition information of the process in the shared memory of the operating system.

In some possible embodiments, the execution module is specifically configured to: call the interface pointer corresponding to the interface definition information according to the interface definition information matching the interface identifier of the called process to access the execution address of the called process; The response information of the calling process, and the response information is returned to the calling process.

In some possible embodiments, an executable file is stored in the shared memory, and the apparatus for multi-process communication further includes: a compilation module for compiling the interface definition information of the called process into an interface definition segment in the executable file , so that when the executable file is executed, the interface pointer corresponding to the interface definition information is called.

In some possible embodiments, the interface definition information includes an interface identifier, a process to which the interface corresponding to the interface identifier belongs, and channel information of a process to which the interface corresponding to the interface identifier belongs.

In a third aspect, an embodiment of the present invention provides a device for multi-process communication, including a memory, a processor, and a program stored in the memory and running on the processor. When the processor executes the program, the above technical solutions are implemented. A method for multi-process communication.

In a fourth aspect, an embodiment of the present invention provides a storage medium on which a program is stored, and when the program is executed by a processor, the method for implementing the multi-process communication in the foregoing technical solution is implemented.

Embodiments of the present invention provide a method, device, device, and storage medium for multi-process communication. After receiving a communication instruction from a calling process, based on the interface identifier of the called process in the communication instruction, in the shared content Call the interface definition information that matches the interface ID of the called process. Using the matched interface definition information, the communication between the calling process and the called process is performed. That is to say, after the device carrying the method for multi-process communication receives the communication instruction, it can automatically complete the communication between the processes. There is no need for developers or maintenance personnel to manually search for information and establish communication, thereby reducing the time spent in multi-process communication and improving the efficiency of multi-process communication.

Description of drawings

The present invention can be better understood from the following description of specific embodiments of the present invention in conjunction with the accompanying drawings, wherein the same or similar reference numerals denote the same or similar features.

1 is a flowchart of a method for multi-process communication in an embodiment of the present invention;

2 is a flowchart of a method for multi-process communication in another embodiment of the present invention;

3 is a schematic structural diagram of an apparatus for multi-process communication according to an embodiment of the present invention;

4 is a schematic structural diagram of an apparatus for multi-process communication in another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a device for multi-process communication according to an embodiment of the present invention.

Detailed ways

Features and exemplary embodiments of various aspects of the invention are described in detail below. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is only intended to provide a better understanding of the present invention by illustrating examples of the invention. The present invention is in no way limited to any specific configurations and algorithms set forth below, but covers any modification, substitution and improvement of elements, components and algorithms without departing from the spirit of the invention. In the drawings and the following description, well-known structures and techniques have not been shown in order to avoid unnecessarily obscuring the present invention.

Embodiments of the present invention provide a method, apparatus, device, and storage medium for multi-process communication, which can be applied to scenarios where communication between multiple processes is required. Each process has a part of its own independent resources, and the independent resources of each process are isolated from each other. In order to enable different processes to access resources and coordinate work, communication between processes is required. For example, developers developing operating systems require multiple processes to communicate with each other. Or, in the process of maintaining multiple applications, the maintainer needs to communicate with each other between the processes of each application.

In this embodiment of the present invention, it is not necessary for developers or maintenance personnel to manually search for process-related information and manually establish communication between processes. Communication between the calling process and the called process can be performed automatically, thereby reducing the time spent in multi-process communication and improving the efficiency of multi-process communication.

FIG. 1 is a flowchart of a method for multi-process communication in an embodiment of the present invention. As shown in FIG. 1 , the method for multi-process communication may include steps S101 to S103.

In step S101, a communication instruction from the calling process is received.

In the present invention, the calling process and the called process are used as examples for description. The calling process is the process that initiates the call. The called process is the process called by the called process. The communication instruction is used to instruct the calling process to communicate with the called process. For example, the communication instruction may specifically be an IPC-CALL instruction. The communication instruction includes the interface identification of the called process in the operating system. The interface identifier is used to identify the interface, and the interface identifiers of different interfaces are different. In some examples, the operating system may specifically include, but is not limited to, a Linux system.

In step S102, based on the interface identifier of the called process, the interface definition information matching the interface identifier of the called process is called in the shared memory of the operating system.

The shared content may be set in the operating system. The shared content is shared by all processes, and interface definition information of all processes can be stored in the shared memory. The interface definition information is used to define the interface of the process. Processes use interfaces to communicate. Using the interface definition information, the communication with the process described by the interface pointed to by the interface definition information can be completed. The "matching" here means that the interface identifier and interface definition information of the matched called process point to the same process.

In some examples, the interface definition information may include an interface identifier, a process to which the interface corresponding to the interface identifier belongs, and channel information of a process to which the interface corresponding to the interface identifier belongs. If an interface identifier identical to the interface identifier of the called process is stored in the shared content, it is determined that the interface definition information to which the interface identifier identical to the interface identifier of the called process belongs is the one that matches the interface identifier of the called process. Interface definition information.

In step S103, the communication between the calling process and the called process is performed according to the interface definition information matching the interface identifier of the called process.

The interface definition information matching the interface identifier of the called process is obtained, that is, the interface definition information of the called process is obtained. According to the interface definition of the called process, a communication channel between the calling process and the called process can be established, and the communication between the calling process and the called process can be performed.

For example, the interface definition information may include an interface identifier, a process to which the interface corresponding to the interface identifier belongs, and channel information of a process to which the interface corresponding to the interface identifier belongs. Then, the corresponding interface, the process to which the corresponding interface belongs, and the channel information of the process can be obtained according to the interface identifier, and the communication function can be executed according to the interface, process and channel information.

It should be noted that the above multi-process communication method is not only applied to the process of calling the called process, but also to the process of the called process responding to the calling process, which is not limited herein.

In this embodiment of the present invention, upon receiving a communication instruction from a calling process, based on the interface identifier of the called process in the communication instruction, the interface definition information matching the interface identifier of the called process can be called in the shared content. Using the matched interface definition information, the communication between the calling process and the called process is performed. That is to say, after the device carrying the method for multi-process communication receives the communication instruction, it can automatically complete the communication between the processes. There is no need for developers or maintenance personnel to manually search for information and establish communication, thereby reducing the time spent in multi-process communication and improving the efficiency of multi-process communication. It also avoids possible congestion when multi-process communication occurs.

Moreover, since the interface definition information can be called in the shared memory of the operating system, the interface definition information in the shared memory of the operating system can be updated in real time. Specifically, the interface definition information of the process in the shared memory of the operating system can be added, deleted, or changed. The extended loading of processes that facilitate multi-process communication also enhances the applicability of multi-process communication.

FIG. 2 is a flowchart of a method for multi-process communication in another embodiment of the present invention. The difference between FIG. 2 and FIG. 1 is that step S103 in FIG. 1 can be subdivided into steps S1031 and S1032. The method for multi-process communication shown in FIG. 2 may further include step S104 and step S105.

In step S104, the interface definition information of all processes is written into the shared memory of the operating system.

In some examples, multiple memory blocks may be set up in shared memory. A memory block can be allocated for the interface definition information of each process, and the interface definition information of the process is stored in the corresponding memory block. In the process of executing step S102, the interface definition information in the corresponding memory block that matches the interface identifier of the called process can be called.

Since all the data stored in the memory block are binary data, the interface definition information of each process can be compiled to obtain the interface definition information compiled into binary data. Write the interface definition information compiled into binary data into the corresponding memory block, so as to complete the calling of the interface definition information required for the calling.

In step S105, the interface definition information of the called process is compiled into the interface definition section in the executable file, so that when the executable file is executed, the interface pointer corresponding to the interface definition information is called.

Among them, executable files are stored in the shared memory. By executing the executable file, the interface pointer corresponding to the interface definition information can be called. In some examples, an executable file may include a program execution segment and a program exit segment. The program execution segment is used to implement each call in the multi-process communication process. The program exit segment is used to realize the exit of the process.

The interface definition section can be added before the program execution section of the executable file. In the process of multi-process communication, the interface definition information of the called process can be compiled into the interface definition section. When the executable file is executed, the interface definition information of the called program can be obtained from the interface definition section, so as to call the interface pointer corresponding to the interface definition information of the called program.

The interface logout section can be added before the program exit section of the executable file. During the process of exiting the operating system, the interface definition information of the process that needs to exit the operating system can be compiled into the interface logout section. When the executable file is executed, the process that needs to exit the operating system can be known from the logout segment of the interface, thereby exiting the operating system.

In some examples, the interface definition message may be obtained by defining an interface through a Define Inter-Process Communication (Define Inter-Process Communication, DEF-IPC).

In step S1031, according to the interface definition information matching the interface identifier of the called process, the interface pointer corresponding to the interface definition information is called to access the execution address of the called process.

An interface pointer points to an interface. By calling the interface pointer, the execution address of the called process can be accessed to complete the communication between the calling process and the called process.

It should be noted that the interface definition information in step S1032 refers to the interface definition information matching the interface identifier of the called process.

In step S1032, the response information from the called process is received, and the response information is returned to the calling process.

Since communication has been established between the calling process and the called process, the response information from the called process can be returned to the calling process through the interface of the called process and the channel of the called process. Complete a communication between the calling process and the called process.

FIG. 3 is a schematic structural diagram of an apparatus for multi-process communication according to an embodiment of the present invention. As shown in FIG. 3 , the apparatus 200 for multi-process communication may include a receiving module 201 , a calling module 202 and an executing module 203 .

The receiving module 201 is configured to receive a communication instruction from a calling process, where the communication instruction includes an interface identifier of the called process in the operating system.

The calling module 202 is configured to call interface definition information matching the interface identifier of the called process in the shared memory of the operating system based on the interface identifier of the called process, where the interface definition information is used to define the interface of the process.

The executing module 203 is configured to execute the communication between the calling process and the called process according to the interface definition information matched with the interface identifier of the called process.

In some examples, the above-mentioned execution module 203 may be specifically configured to: call the interface pointer corresponding to the interface definition information according to the interface definition information matching the interface identifier of the called process to access the execution address of the called process; The response information of the calling process, and the response information is returned to the calling process.

In this embodiment of the present invention, upon receiving a communication instruction from a calling process, based on the interface identifier of the called process in the communication instruction, the interface definition information matching the interface identifier of the called process can be called in the shared content. Using the matched interface definition information, the communication between the calling process and the called process is performed. That is to say, after the device carrying the method for multi-process communication receives the communication instruction, it can automatically complete the communication between the processes. There is no need for developers or maintenance personnel to manually search for information and establish communication, thereby reducing the time spent in multi-process communication and improving the efficiency of multi-process communication.

FIG. 4 is a schematic structural diagram of an apparatus for multi-process communication according to another embodiment of the present invention. The difference between FIG. 4 and FIG. 3 is that the apparatus 200 for multi-process communication shown in FIG. 4 may further include a definition module 204 and a compilation module 205 .

The definition module 204 is used for writing the interface definition information of all processes into the shared memory of the operating system.

The compiling module 205 is used for compiling the interface definition information of the called process into the interface definition section in the executable file, so that when the executable file is executed, the interface pointer corresponding to the interface definition information is called.

Among them, executable files are stored in the shared memory.

In some examples, the above-mentioned interface definition information may include the interface identifier, the process to which the interface corresponding to the interface identifier belongs, and the channel information of the process to which the interface corresponding to the interface identifier belongs.

In some examples, the definition module 204 may also be used to update interface definition information for processes in shared memory of the operating system.

FIG. 5 is a schematic structural diagram of a device for multi-process communication according to an embodiment of the present invention. As shown in FIG. 5 , the device 300 for multi-process communication includes a memory 301 , a processor 302 , and a program stored on the memory 301 and executable on the processor 302 .

In one example, the above-mentioned processor 302 may include a central processing unit (CPU), or a specific integrated circuit (ASIC), or may be configured as one or more integrated circuits implementing embodiments of the present application.

Memory 301 may include mass storage for data or instructions. By way of example and not limitation, memory 301 may include an HDD, floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or universal serial bus (USB) drive, or a combination of two or more of the above. Memory 301 may include removable or non-removable (or fixed) media, where appropriate. Memory 301 may be internal or external to device 300 for inter-process communication, as appropriate. In certain embodiments, memory 301 is non-volatile solid state memory. In certain embodiments, memory 301 includes read only memory (ROM). Where appropriate, the ROM may be a mask programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically rewritable ROM (EAROM) or flash memory or A combination of two or more of the above.

The processor 302 runs a program corresponding to the executable program code by reading the executable program code stored in the memory 301, so as to control the method for multi-process communication in the above-mentioned embodiment.

In one example, the device 300 for multi-process communication may further include a communication interface 303 and a bus 304 . Among them, as shown in FIG. 5 , the memory 301 , the processor 302 , and the communication interface 303 are connected through the bus 304 and complete the communication with each other.

The communication interface 303 is mainly used to implement communication between modules, apparatuses, units, and/or devices in the embodiments of the present application. Input devices and/or output devices may also be accessed through the communication interface 303 .

The bus 304 includes hardware, software, or both, coupling the components of the device 300 for multi-process communication to each other. By way of example and not limitation, bus 304 may include Accelerated Graphics Port (AGP) or other graphics bus, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), HyperTransport (HT) interconnect, Industry Standard Architecture (ISA) ) bus, Infiniband Interconnect, Low Pin Count (LPC) bus, Memory Bus, Microchannel Architecture (MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of the above. Bus 304 may include one or more buses, where appropriate. Although embodiments of this application describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

An embodiment of the present application further provides a storage medium, where a program is stored on the storage medium, and when the program is executed by a processor, the method for multi-process communication in the foregoing embodiment can be controlled.

It should be clear that each embodiment in this specification is described in a progressive manner, and the same or similar parts of each embodiment may be referred to each other, and each embodiment focuses on the differences from other embodiments. place. For the apparatus embodiment, the device embodiment, and the storage medium embodiment, reference may be made to the description part of the method embodiment for related parts. The invention is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art may make various changes, modifications and additions, or change the order between steps, after appreciating the spirit of the present invention. Also, for the sake of brevity, detailed descriptions of known methods and techniques are omitted here.

The functional blocks shown in the above structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, elements of the invention are programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted over a transmission medium or communication link by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. The code segments may be downloaded via a computer network such as the Internet, an intranet, or the like.

Claims (13)

1. A method of inter-process communication, comprising:

receiving a communication instruction from a calling process, wherein the communication instruction comprises an interface identification of a called process in an operating system;

based on the interface identification of the called process, calling interface definition information matched with the interface identification of the called process in a shared memory of an operating system, wherein the interface definition information is used for defining the interface of the process;

and executing communication between the calling process and the called process according to the interface definition information matched with the interface identification of the called process.

2. The method of claim 1, further comprising:

and writing the interface definition information of all the processes into the shared memory of the operating system.

3. The method of claim 1, wherein the performing communication between the calling process and the called process according to the interface definition information matching with the interface identification of the called process comprises:

calling an interface pointer corresponding to the interface definition information according to the interface definition information matched with the interface identification of the called process so as to access an execution address of the called process;

and receiving response information from the called process and returning the response information to the calling process.

4. The method of claim 3, wherein the shared memory has an executable file stored therein, the method further comprising:

compiling the interface definition information of the called process into an interface definition section in the executable file, so that the executable file realizes the calling of an interface pointer corresponding to the interface definition information when being executed.

5. The method of claim 1, further comprising:

and updating interface definition information of the process in the shared memory of the operating system.

6. The method according to any one of claims 1 to 5, wherein the interface definition information includes an interface identifier, a process to which an interface corresponding to the interface identifier belongs, and channel information of a process to which an interface corresponding to the interface identifier belongs.

7. An apparatus for inter-process communication, comprising:

the receiving module is used for receiving a communication instruction from a calling process, wherein the communication instruction comprises an interface identifier of a called process in an operating system;

the calling module is used for calling interface definition information matched with the interface identifier of the called process in a shared memory of an operating system based on the interface identifier of the called process, wherein the interface definition information is used for defining the interface of the process;

and the execution module is used for executing the communication between the calling process and the called process according to the interface definition information matched with the interface identification of the called process.

8. The apparatus of claim 1, further comprising:

and the definition module is used for writing the interface definition information of all the processes into the shared memory of the operating system.

9. The apparatus of claim 1, wherein the execution module is specifically configured to:

calling an interface pointer corresponding to the interface definition information according to the interface definition information matched with the interface identification of the called process so as to access an execution address of the called process;

and receiving response information from the called process and returning the response information to the calling process.

10. The apparatus of claim 9, wherein the shared memory has an executable file stored therein, the apparatus further comprising:

and the compiling module is used for compiling the interface definition information of the called process into an interface definition section in the executable file so as to realize the calling of an interface pointer corresponding to the interface definition information when the executable file is executed.

11. The apparatus according to any one of claims 7 to 10, wherein the interface definition information includes an interface identifier, a process to which an interface corresponding to the interface identifier belongs, and channel information of a process to which an interface corresponding to the interface identifier belongs.

12. An apparatus for inter-process communication, comprising a memory, a processor, and a program stored on the memory and executable on the processor, the processor implementing the method of inter-process communication according to any one of claims 1 to 6 when executing the program.

13. A storage medium having stored thereon a program which, when executed by a processor, implements a method of inter-process communication according to any one of claims 1 to 6.

Images