CN111400055A - Method, device, equipment and storage medium for communication among multiple processes - Google Patents
Method, device, equipment and storage medium for communication among multiple processes Download PDFInfo
- Publication number
- CN111400055A CN111400055A CN201910004763.6A CN201910004763A CN111400055A CN 111400055 A CN111400055 A CN 111400055A CN 201910004763 A CN201910004763 A CN 201910004763A CN 111400055 A CN111400055 A CN 111400055A
- Authority
- CN
- China
- Prior art keywords
- interface
- communication
- definition information
- calling
- called
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 309
- 230000008569 process Effects 0.000 title claims abstract description 231
- 230000006854 communication Effects 0.000 title claims abstract description 129
- 238000004891 communication Methods 0.000 title claims abstract description 128
- 230000004044 response Effects 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device, equipment and a storage medium for communication among multiple processes, and relates to the technical field of communication. The method for communication among multiple processes comprises the following steps: receiving a communication instruction from a calling process, wherein the communication instruction comprises an interface identifier 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 performing communication between the calling process and the called process according to the interface definition information matched with the interface identification of the called process. By using the technical scheme of the invention, the efficiency of the communication among the multiple processes can be improved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for inter-process communication.
Background
During application layer development of an operating system, communication between different processes may need to be used. For example, if the process a needs to communicate with the process B, a developer needs to manually define the relevant information of the process a and then manually search the relevant information of the process B. And defining a communication method between the process A and the process B by utilizing the relevant information of the process A and the relevant information of the process B, thereby initiating the communication between the process A and the process B.
With the increase of the number of applications, in order to realize the inter-process communication, a large amount of manual operation and maintenance are needed by developers, which takes long time and reduces the efficiency of the multi-process communication.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for communication among multiple processes, which can improve the efficiency of communication among the multiple processes.
In a first aspect, an embodiment of the present invention provides a method for communication among multiple processes, including: receiving a communication instruction from a calling process, wherein the communication instruction comprises an interface identifier 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 performing communication between the calling process and the called process according to the interface definition information matched with the interface identification of the called process.
In some possible embodiments, the method for inter-process communication further includes: and writing the interface definition information of all the processes into a shared memory of the operating system.
In some possible embodiments, the communication between the calling process and the called process is performed according to the interface definition information matching the interface identification of the called process, including: 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.
In some possible embodiments, the shared memory stores an executable file, and the method for communication among multiple processes further includes: 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 the interface pointer corresponding to the interface definition information when being executed.
In some possible embodiments, the method for inter-process communication further includes: interface definition information of processes in a shared memory of an operating system is updated.
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 the 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 inter-process communication, including: 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, and 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.
In some possible embodiments, the apparatus for inter-process communication further includes: and the definition module is used for writing the interface definition information of all the processes into a shared memory of the operating system.
In some possible embodiments, the definition module is further configured to update interface definition information of a process in the shared memory of the operating system.
In some possible embodiments, 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.
In some possible embodiments, the shared memory stores an executable file, and the apparatus for inter-process communication further includes: 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.
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 the process to which the interface corresponding to the interface identifier belongs.
In a third aspect, an embodiment of the present invention provides an apparatus for inter-process communication, including a memory, a processor, and a program stored in the memory and executable on the processor, where when the processor executes the program, the method for inter-process communication in the foregoing technical solution is implemented.
In a fourth aspect, an embodiment of the present invention provides a storage medium, on which a program is stored, where the program, when executed by a processor, implements the method for inter-process communication in the foregoing technical solution.
The embodiment of the invention provides a method, a device, equipment and a storage medium for communication among multiple processes. And performing communication between the calling process and the called process by using the matched interface definition information. That is, after receiving the communication instruction, the device bearing the method for communication between multiple processes can automatically complete the communication between the processes. Developers or maintainers are not required to manually search information and establish communication, so that the time spent on communication among multiple processes is reduced, and the efficiency of communication among the multiple processes is improved.
Drawings
The present invention will be better understood from the following description of specific embodiments thereof taken in conjunction with the accompanying drawings, in which like or similar reference characters designate like or similar features.
FIG. 1 is a flow chart illustrating a method for inter-process communication according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for inter-process communication according to another embodiment of the present invention;
FIG. 3 is a block diagram of an apparatus for inter-process communication according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an apparatus for inter-process communication according to another embodiment of the present invention;
fig. 5 is a schematic structural diagram of a device for inter-process communication according to an embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be 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. It will be apparent, however, 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 merely intended to provide a better understanding of the present invention by illustrating examples of the present invention. The present invention is in no way limited to any specific configuration and algorithm set forth below, but rather covers any modification, replacement or improvement of elements, components or algorithms without departing from the spirit of the invention. In the drawings and the following description, well-known structures and techniques are not shown in order to avoid unnecessarily obscuring the present invention.
The embodiment of the invention provides a method, a device, equipment and a storage medium for communication among multiple processes, which can be applied to scenes needing communication among the multiple processes. Each process has a part of independent resources, and the independent resources of each process are isolated from each other. In order to enable different processes to access resources and perform coordination work, the processes need to communicate with each other. For example, a developer developing an operating system requires multiple processes to communicate with each other. Alternatively, in the process of maintaining a plurality of applications, the maintenance personnel need to communicate the processes of the respective applications with each other.
In the embodiment of the invention, developers or maintainers are not required to manually search the relevant information of the processes and manually establish communication between the processes. The communication between the calling process and the called process can be automatically carried out, so that the time spent on the communication between the multiple processes is reduced, and the efficiency of the communication between the multiple processes is improved.
FIG. 1 is a flowchart illustrating a method for inter-process communication according to an embodiment of the present invention. As shown in fig. 1, the method of multi-process communication may include steps S101 to S103.
In step S101, a communication instruction from a call process is received.
The communication instruction is used for indicating that the calling process is to communicate with the called process, for example, the communication instruction can be specifically an IPC-CA LL instruction, the communication instruction comprises an interface identifier of the called process in an operating system, the interface identifier is used for identifying an interface, and the interface identifiers of different interfaces are different.
In step S102, based on the interface identifier of the called process, interface definition information matching the interface identifier of the called process is called in the shared memory of the operating system.
Wherein, shared content can be set in the operating system. The shared content is shared by all processes, and the interface definition information of all processes can be stored in the shared memory. The interface definition information is used to define an interface of the process. The processes utilize interfaces to enable communication. By using the interface definition information, the communication between the processes of the interface pointed by the interface definition information can be completed. Here, "match" means that the interface identification and the 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 the process to which the interface corresponding to the interface identifier belongs. If the interface identification which is the same as the interface identification of the called process is stored in the shared content, determining the interface definition information to which the interface identification which is the same as the interface identification of the called process belongs, and the interface definition information is matched with the interface identification of the called process.
In step S103, communication between the calling process and the called process is performed according to the interface definition information matching the interface identification of the called process.
And acquiring the interface definition information matched with the interface identification of the called process, namely acquiring the interface definition information of the called process. According to the interface definition of the called process, a communication channel between the calling process and the called process can be established, and communication between the calling process and the called process is performed.
For example, the interface definition information may include 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. 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, the process, and the channel information.
It should be noted that the method for communication among multiple processes is not only applied to the process of calling the called process by the calling process, but also applied to the process of responding to the calling process by the called process, and is not limited herein.
In the embodiment of the invention, when a communication instruction from a calling process is received, interface definition information matched with the interface identification of the called process can be called in the shared content based on the interface identification of the called process in the communication instruction. And performing communication between the calling process and the called process by using the matched interface definition information. That is, after receiving the communication instruction, the device bearing the method for communication between multiple processes can automatically complete the communication between the processes. Developers or maintainers are not required to manually search information and establish communication, so that the time spent on communication among multiple processes is reduced, and the efficiency of communication among the multiple processes is improved. Congestion that may occur when multi-process communication is performed can also be avoided.
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 and changed. The method facilitates the extension loading of the process of the multi-process communication, and also enhances the applicability of the multi-process communication.
FIG. 2 is a flowchart illustrating a method for inter-process communication according to another embodiment of the present invention. Fig. 2 differs from fig. 1 in that step S103 in fig. 1 can be subdivided into step S1031 and step S1032. The method of 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 provided in a shared memory. One memory block may be allocated to the interface definition information of each process, and the interface definition information of the process may be stored in the corresponding memory block. In the process of executing step S102, the interface definition information matching the interface identifier of the called process in the corresponding memory block may 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. And writing the interface definition information compiled into the binary data into the corresponding memory block to finish the calling of the interface definition information required by calling.
In step S105, the interface definition information of the called process is compiled into the interface definition segment in the executable file, so that the executable file realizes the call of the interface pointer corresponding to the interface definition information when being executed.
The shared memory stores executable files. And executing the executable file to call the interface pointer corresponding to the interface definition information. In some examples, the executable file may include a program execution segment and a program exit segment. The program execution segment is used for realizing each call in the multi-process communication process. The program exit segment is used for exiting the process.
The interface definition segment may be added before the program execution segment 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 segment. When the executable file is executed, the interface definition information of the called program can be known from the interface definition segment, so that the interface pointer corresponding to the interface definition information of the called program is called.
The interface logout segment can be added before the program logout segment of the executable file, and the interface definition information of the process needing to logout the operating system can be compiled into the interface logout segment in the process that the process quits the operating system. When the executable file is executed, the process needing to quit the operating system can be known from the interface logout segment, so that the operating system is quitted.
In some examples, the interface definition message may be derived by defining an interface via a custom Inter-Process Communication (DEF-IPC).
In step S1031, according to the interface definition information matching the interface identification of the called process, an interface pointer corresponding to the interface definition information is called to access the execution address of the called process.
The interface pointer points to the interface. The interface pointer is called, so that 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 interface definition information that matches the interface identifier of the called process.
In step S1032, response information from the called process is received, and the response information is returned to the calling process.
Since communication has already been established between the calling process and the called process, 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. And completing the communication between the calling process and the called process.
FIG. 3 is a block diagram of an apparatus for inter-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 a called process in an operating system.
And the calling module 202 is used for calling interface definition information matched with the interface identification of the called process in the shared memory of the operating system based on the interface identification of the called process, wherein the interface definition information is used for defining the interface of the process.
And the execution module 203 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.
In some examples, the executing module 203 may be 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.
In the embodiment of the invention, when a communication instruction from a calling process is received, interface definition information matched with the interface identification of the called process can be called in the shared content based on the interface identification of the called process in the communication instruction. And performing communication between the calling process and the called process by using the matched interface definition information. That is, after receiving the communication instruction, the device bearing the method for communication between multiple processes can automatically complete the communication between the processes. Developers or maintainers are not required to manually search information and establish communication, so that the time spent on communication among multiple processes is reduced, and the efficiency of communication among the multiple processes is improved.
FIG. 4 is a block diagram of an apparatus for inter-process communication according to another embodiment of the present invention. Fig. 4 is different from fig. 3 in that the apparatus 200 for inter-process communication shown in fig. 4 may further include a definition module 204 and a compiling module 205.
The defining module 204 is configured to write the interface definition information of all the processes into the shared memory of the operating system.
And the compiling module 205 is configured to compile 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.
The shared memory stores executable files.
In some examples, the interface definition information may include an interface identifier, a process to which an interface corresponding to the interface identifier belongs, and channel information of a 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 the shared memory of the operating system.
Fig. 5 is a schematic structural diagram of a device for inter-process communication according to an embodiment of the present invention. As shown in fig. 5, the device 300 for multiprocess 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 processor 302 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more integrated circuits of 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 these. Memory 301 may include removable or non-removable (or fixed) media, where appropriate. The memory 301 may be internal or external to the device 300 for interprocess communication, where appropriate. In a particular embodiment, the memory 301 is a non-volatile solid-state memory. In certain embodiments, memory 301 comprises Read Only Memory (ROM). Where appropriate, the ROM may be 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 these.
The processor 302 runs a program corresponding to the executable program code by reading the executable program code stored in the memory 301, for controlling the method of inter-process communication in the above-described embodiment.
In one example, the device 300 for interprocess communication may also include a communication interface 303 and a bus 304. As shown in fig. 5, the memory 301, the processor 302, and the communication interface 303 are connected via a bus 304 to complete communication therebetween.
The communication interface 303 is mainly used for implementing communication between modules, apparatuses, units and/or devices in the embodiment of the present application. Input devices and/or output devices may also be accessed through communication interface 303.
The bus 304 comprises hardware, software, or both that couple components of the device 300 for interprocess communication to one another, by way of example and not limitation, the bus 304 may comprise an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low pin count (L PC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics Association local (V L B) bus, or other suitable bus, or a combination of two or more of these.
An embodiment of the present application further provides a storage medium, where the storage medium stores a program, and the program, when executed by a processor, controls the method for inter-process communication in the foregoing embodiment.
It should be clear that the embodiments in this specification are described in a progressive manner, and the same or similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. For apparatus embodiments, device embodiments and storage medium embodiments, reference may be made to the description of the method embodiments for relevant points. The present 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 the steps after appreciating the spirit of the invention. Also, a detailed description of known process techniques is omitted herein for the sake of brevity.
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, plug-in, function card, or the like. When implemented in software, the elements of the invention are the 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 by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium 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 so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910004763.6A CN111400055A (en) | 2019-01-03 | 2019-01-03 | Method, device, equipment and storage medium for communication among multiple processes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910004763.6A CN111400055A (en) | 2019-01-03 | 2019-01-03 | Method, device, equipment and storage medium for communication among multiple processes |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111400055A true CN111400055A (en) | 2020-07-10 |
Family
ID=71430196
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910004763.6A Pending CN111400055A (en) | 2019-01-03 | 2019-01-03 | Method, device, equipment and storage medium for communication among multiple processes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400055A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1595363A (en) * | 2003-05-09 | 2005-03-16 | 太阳微系统公司 | Interprocess communication in operating system partition |
| US20080127206A1 (en) * | 2006-08-02 | 2008-05-29 | Microsoft Corporation Microsoft Patent Group | Conducting client-server inter-process communication |
| CN101739300A (en) * | 2008-11-18 | 2010-06-16 | 中兴通讯股份有限公司 | Method and system for inter-process communication of multimedia terminal |
| CN107133109A (en) * | 2017-04-24 | 2017-09-05 | 京信通信系统（广州）有限公司 | A kind of method of intermodule communication, device and computing device |
| CN107688502A (en) * | 2017-08-18 | 2018-02-13 | 苏州科达特种视讯有限公司 | Inter-process communication methods and device |
-
2019
- 2019-01-03 CN CN201910004763.6A patent/CN111400055A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1595363A (en) * | 2003-05-09 | 2005-03-16 | 太阳微系统公司 | Interprocess communication in operating system partition |
| US20080127206A1 (en) * | 2006-08-02 | 2008-05-29 | Microsoft Corporation Microsoft Patent Group | Conducting client-server inter-process communication |
| CN101739300A (en) * | 2008-11-18 | 2010-06-16 | 中兴通讯股份有限公司 | Method and system for inter-process communication of multimedia terminal |
| CN107133109A (en) * | 2017-04-24 | 2017-09-05 | 京信通信系统（广州）有限公司 | A kind of method of intermodule communication, device and computing device |
| CN107688502A (en) * | 2017-08-18 | 2018-02-13 | 苏州科达特种视讯有限公司 | Inter-process communication methods and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110960855B (en) | Communication protocol code updating method and device, electronic equipment and storage medium | |
| CN111158756B (en) | Method and apparatus for processing information | |
| CN111611145A (en) | Breakdown information collection method and device, storage medium and electronic equipment | |
| CN108694052B (en) | Firmware upgrading method, firmware upgrading device and firmware upgrading system | |
| CN110659210A (en) | Information acquisition method and device, electronic equipment and storage medium | |
| CN116455694A (en) | Baud rate setting method, baud rate setting device, baud rate setting equipment and storage medium | |
| CN104978204A (en) | Application installing and updating method based on mobile terminal and application installing and updating device based on mobile terminal | |
| CN118034924A (en) | Data processing method and device based on many-core system, electronic equipment and medium | |
| CN113050985A (en) | Front-end engineering dependence automatic registration method and device | |
| CN111400055A (en) | Method, device, equipment and storage medium for communication among multiple processes | |
| CN112162919A (en) | Debugging method and system for vehicle-mounted equipment and computer readable storage medium | |
| CN113821486B (en) | Method and device for determining dependency relationship between pod libraries and electronic equipment | |
| CN116049000A (en) | Environment parameter configuration method, device, equipment, storage medium and product | |
| CN114675822A (en) | AUTOSAR software component development method, device, equipment and storage medium | |
| CN110968334B (en) | Application resource updating method, resource package manufacturing method, device, medium and equipment | |
| CN112181496A (en) | AI extended instruction execution method and device based on open source instruction set processor, storage medium and electronic equipment | |
| CN114265593B (en) | Instruction scheduling method, device, equipment and computer readable storage medium | |
| CN110851150B (en) | Method and apparatus for installing applications | |
| CN114415612B (en) | Intelligent production monitoring method and server based on artificial intelligence | |
| CN111209225B (en) | Method, device, medium and electronic equipment for acquiring real address | |
| CN113468065B (en) | Test case operation method and device | |
| CN113031914B (en) | Floating point rounding mode control method, device, equipment and storage medium | |
| CN108206745B (en) | Business operation method and device and cloud computing system | |
| CN117806696A (en) | Installation package construction method and device | |
| CN117130898A (en) | Test software development method and device of Internet of things module and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200710 |