CN102103526A - Method and system for performing inter-process communication between server and client by service management - Google Patents
Method and system for performing inter-process communication between server and client by service management Download PDFInfo
- Publication number
- CN102103526A CN102103526A CN 201110037259 CN201110037259A CN102103526A CN 102103526 A CN102103526 A CN 102103526A CN 201110037259 CN201110037259 CN 201110037259 CN 201110037259 A CN201110037259 A CN 201110037259A CN 102103526 A CN102103526 A CN 102103526A
- Authority
- CN
- China
- Prior art keywords
- service end
- client
- service
- message
- service management
- 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
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a method for performing inter-process communication between a server and a client by service management. The method is characterized by comprising the following steps that: an operating system starts a server process and registers the server process by service management; a client process requests the service management for using the server process to transmit a message to the server; and the server processes the message and returns the processed message to the client process. By the method, the coupling of the operating system module is reduced, and great convenience is brought to the management on the inter-process communication.
Description
Technical field
The invention belongs to operating system inter-process communication techniques field, be specifically related to be undertaken by Service Management between a kind of service end and client the method and system of interprocess communication.
Background technology
Interprocess communication (IPC, Inter-Process Communication) refers to that at least two processes or cross-thread transmit some technology or the method for data or signal.Process is the least unit of computer system Resources allocation.The part that each process all has oneself is system resource independently, isolates each other.In order to make the mutual access resources of different processes and to carry out co-ordination, just interprocess communication has been arranged.On the various computing machine that process may operate on the same computing machine or network connects.Each process is endowed its virtual address space, and when a thread in the process was moving, this thread can be visited the internal memory of the process that only belongs to it.And the user's space of process is mutually independently, and the internal memory that belongs to other process is then hidden, and can not have access to the information of other process.
On traditional sense, interprocess communication have usually the message transmission, synchronously, shared drive and remote procedure call.The message transmission comprises the signature pipeline again, FIFO, and Posix and System V message Socket etc., comprise mutual exclusion lock again synchronously to row, conditional-variable, Read-Write Locks, file and record lock, Posix and System V signal lamp; Shared drive comprises anonymous shared drive district, signature Posix shared drive district, signature System V shared drive district.Common having is following several: pipeline communication, signal communication, socket (Socket), shared drive etc.
Pipeline is a kind of data structure, visits as the file of a serializing.It is a kind of half-duplex communication mode, and it is big that pipeline has the data volume of transmission, but slow characteristics.Pipeline is by being divided into two kinds of anonymous pipeline and named pipess, anonymous pipeline can only have communication (sibship generally refers to set membership) in the process of sibship, named pipes then can be two irrelevant interprocess communications, and be relatively easy to be applied in the relation of one-to-many, so be used for multithreaded server mostly.
Signal is the most ancient interprocess communication mode in the Unix system, and signal is complicated with respect to other modes, is used to notify the generation of certain process event, except being used for the interprocess communication, also can use between with process.Signal be on the software level to a kind of simulation of interrupt mechanism, on principle, process receives that a signal and processor receive that an interrupt request can be described as the same.Signal is asynchronous, and a process needn't be come the arrival of waiting signal by any operation, and in fact, process does not know when signal arrives on earth yet.
Socket is a kind of more generally communication mode, and is more convenient for the communication that data volume is bigger between the various computing machine, and the interprocess communication in a computing machine is then not too suitable, and size of code is bigger.Shared drive is exactly the memory headroom that can be visited by other processes of mapping in internal memory, and this internal memory is by a process creation, and other processes also can be visited.Relatively and other communication modes, this mode realizes fairly simple and is the fastest a kind of communication mode, it is a two-way process, and shared drive is mapped to the address space of each process of using it, and any process of shared region can be to read/write memory.So it appears to another variable in in-process statement.The unfavorable factor of memory shared mechanism is exactly its synchronous and all poorly control of agreement, must guarantee handle is passed to subprocess and thread.
And above these all are with respect to the realization than the data transmission of the interprocess communication of lower level, though can both finish finishing of interprocess communication from technical standpoint, the total solution of interprocess communication also do not had.
Summary of the invention
The object of the invention is to provide the method for carrying out interprocess communication between a kind of service end and client by Service Management, the whole to a certain extent difficult problem of communicating by letter between multi-process in the prior art that solved.
In order to solve these problems of the prior art, technical scheme provided by the invention is:
Carry out the method for interprocess communication between a kind of service end and client by Service Management, it is characterized in that by Service Management the service end process being enrolled after described method comprises os starting service end process, client process is by using the service end process to service end pass-along message to service administration request; Service end is handled the step that returns to client process after the message again.
Preferably, said method comprising the steps of:
(1) start the service end process, and the service end process is registered in the Service Management, specific handle sign is set in Service Management, the service end process enters the LOOP state, waits for the request of client;
(2) client process is according to the agent object of specific handle sign to the services request acquisition service end of Service Management submission use service end, the agent object of client call service end;
(3) agent object be encapsulated into message in the container by Send () function and be transferred to service end after enter blocked state, wait for that service end returns result;
(4) service end is taken out message from container by OnSend () function, calls local realization function operation, and the return messages container of packing into is returned to agent object; Client works on after receiving return message.
Preferably, the direct process switching of process of client process and service end in the described method.
Preferably, when carrying out the message transmission in the described method, operating system nucleus is mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by local realization function operation.
Another object of the present invention is to provides the system that carries out interprocess communication between a kind of service end and client by Service Management, comprises the service management module that is arranged between service end and client; It is characterized in that described service management module accepts the registration of service end process, the sign handle of the service end process of registration is provided; Client process submits to the services request of using service end to obtain the agent object of service end according to specific handle sign to service management module, and the agent object of client by calling service end passes to the service end process with the message of client; Service end to the Message Processing of client after agent object by service end be transferred to client.
Preferably, when service end is obtained the message of client by agent object in the described system, operating system nucleus is mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by the local function operation of realizing of service end.
Technical solution of the present invention obtains a kind of solution of complete interprocess communication, comprising a client, and a service end, a Service Management and a model that makes up service and Service Management.At first make up service end process and Service Management, start service end process and registration service in Object Request Broker by the model that provides, can specific sign handle of application in registration process.Finish after the registration work, service end enters the loop state, waits for client-requested.
Client obtains the agent object of a service end according to the service of specific handle to the service administration request correspondence.The method that client uses agent object to provide just as the method for this process of calling.Agent object only provides an agent functionality, and concrete realization is not provided, and it can be encapsulated into information such as parameter in the container, is transferred to service end by Send () function then.Enter blocked state then, the wait service end is returned result.
Service end is taken out various parameters by OnSend () function from container class, calls concrete realization function again and goes to realize real function, and the container of again information being packed into returns to client.Client receives return message, works on.
The invention provides a kind of CORBA framework that adopts scaled-down version based on shared drive mechanism interprocess communication system, a kind of solution of complete interprocess communication is provided, provide a kind of framework of interprocess communication to be used for the code framework of total system, application program, make system code clear in structure, succinct, interprocess communication is stable, efficient.
Relate to coming two big processes in the whole interprocess communication process of the present invention, first client process is served accordingly to service administration request, and returns the Service Management of object.Second is exactly that Service Management transmits data to service end, return message after finishing actual function.These two processes all will relate to the communication between process, all are to realize the transmission of data between two processes by shared drive.So here also just as can be seen, Service Management also can be regarded a big service in fact as in fact, it obtains the specifically agency of service by the interprocess communication visit earlier, is realizing by the agency and is asking communicating by letter of service.
With respect to scheme of the prior art, advantage of the present invention is:
The invention provides a kind of model and make up service and Service Management, and actual interprocess communication also is to finish in the framework that is hidden in service and Service Management, has made things convenient for writing of service end code so greatly.
The interprocess communication model of this miniature object broker framework provided by the invention makes that the framework orderliness of system code is clear.The bottom service is by the local actual proxy interface that realizes and provide away of the interface framework that provides, and Service Management manages all services, and application program obtains proxy interface by Service Management, carries out actual communication.
The present invention adopts direct process switching strategy, and promptly when the IPC operation took place, kernel was directly handed to the recipient of IPC to operation power from the promoter without scheduler, thereby has avoided unnecessary scheduling overhead.What whole process adopted is that the mode that is similar to thread migration realizes, entire I PC seems similarly to be that a process enters another process run time version and returns with the result who carries out then.
Actual data transmission is finished in the present invention's employing mode of shared drive the most efficiently, promptly carry out direct transmission of messages by the temporary address mapping, being kernel is mapped to IPC recipient (here just service end) in the address space zone of a kernel administration, directly the data with the sender of the message copy to this zone, thereby only need can read information by a memory copying recipient.The space of the kernel of the service correspondence that each is different is different, has only the process of acceptance just can read.
The present invention needs all information transmitted to be encapsulated in the container to go, and forms the data transmission format that unified height is integrated, and greatly facilitates the transmission and the parsing of data between process.
Compare with general communication mode, the present invention greatly facilitate the place system code structure with write and the formation of the framework of total system, reduced each module of system coupling, made things convenient for application program, also greatly facilitate the management of interprocess communication simultaneously.In addition because the temporary address mapping also makes the speed of interprocess communication be greatly improved.
Description of drawings
Below in conjunction with drawings and Examples the present invention is further described:
Fig. 1 carries out the specific implementation system architecture diagram of interprocess communication for the embodiment of the invention;
Fig. 2 is the service relation synoptic diagram of embodiment of the invention process and Service Management;
Fig. 3 is that the embodiment of the invention is based on the process flow diagram that calls between the system kernel process;
Fig. 4 is the specific implementation process flow diagram of embodiment of the invention interprocess communication.
Embodiment
Below in conjunction with specific embodiment such scheme is described further.Should be understood that these embodiment are used to the present invention is described and are not limited to limit the scope of the invention.The implementation condition that adopts among the embodiment can be done further adjustment according to the condition of concrete producer, and not marked implementation condition is generally the condition in the normal experiment.
Embodiment
Shown in Fig. 1~4, carry out the system of interprocess communication between this service end and client by Service Management, comprise the service management module that is arranged between service end and client; Described service management module is accepted the registration of service end process, and the sign handle of the service end process of registration is provided; Client process submits to the services request of using service end to obtain the agent object of service end according to specific handle sign to service management module, and the agent object of client by calling service end passes to the service end process with the message of client; Service end to the Message Processing of client after agent object by service end be transferred to client.When service end was obtained the message of client by agent object in the described system, operating system nucleus was mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by the local function operation of realizing of service end.
When carrying out Inter-Process Communication, start the service end process earlier, and the service end process is registered in the Service Management, specific handle sign is set in Service Management, the service end process enters the LOOP state, waits for the request of client; Client process is according to the agent object of specific handle sign to the services request acquisition service end of Service Management submission use service end, the agent object of client call service end; Agent object be encapsulated into message in the container by Send () function and be transferred to service end after enter blocked state, wait for that service end returns result; Service end is taken out message from container by OnSend () function, calls local realization function operation, and the return messages container of packing into is returned to agent object; Client works on after receiving return message.
Specific implementation is, a kind of system architecture is provided, and as shown in Figure 1, comprises two interfaces in the framework: service end interface NsXXX, client-side interface PsXXX.These two interfaces are finished each the concrete service content of serving self and the concrete service content of client.NsXXX is responsible for (NsService) receiving and acting on behalf of the data that biography comes and go to finish concrete function by the specific implementation function again by OnSend (), be provided with the corresponding function of a cover on the PsXXX, what does not all do and just all information (PsService) is transferred to NsXXX by Send () and holds the function only here yet.
As shown in Figure 2, the framework framework code of service end process by providing passes through the registration service of register () function then in Service Management; AddService () is set in the Service Management and findService () function is used to register and search the handle object of service end.Client process specifically need to obtain the process object of communication by getService ()
*Handle, this parameter of wherein transmitting has just comprised a handle identification information.
As shown in Figure 3, the handle identification information that Service Management passes over according to client process, search the service end process of having registered, if found the agent object that just returns this service end to give request process (the PsXXX object of corresponding requests process just), can not find and then return an abnormal information.The Service Management here also is a service (service end process), so actual invoked procedure is client process in fact to be passed through getDefaultService () and imports acquiescence handle=0 into, obtain the agency service object of Service Management earlier, thereby realize directly just finishing the realization of striding course the Service Management operation.
As shown in Figure 4, client process obtains Service Management and just can directly operate on it later, all at last operation informations all can be packaged in the container class that is called Mbox, by Send () function information is being sent, oneself enters suspended state then, concrete realization is exactly by calling talkwithdriver () function, call the read-write of ioctl () function realization again to kernel, information is write the zone of requested service process in kernel mappings, wake request process then.
After service processes is waken up, calls OnSend () function and read information in the container, call actual processing function and finish actual work of treatment, return processing by reply () at last, process is the same with the process that transmits.Last client receives the information of returning, and finishes the communication between process.
In this process, the direct process switching of the process of client process and service end.When carrying out the message transmission, operating system nucleus is mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by local realization function operation.
Above-mentioned example only is explanation technical conceive of the present invention and characteristics, and its purpose is to allow the people who is familiar with this technology can understand content of the present invention and enforcement according to this, can not limit protection scope of the present invention with this.All equivalent transformations that spirit is done according to the present invention or modification all should be encompassed within protection scope of the present invention.
Claims (6)
1. the method for carrying out interprocess communication by Service Management between service end and client, it is characterized in that by Service Management the service end process being enrolled after described method comprises os starting service end process, client process is by using the service end process to service end pass-along message to service administration request; Service end is handled the step that returns to client process after the message again.
2. method according to claim 1 is characterized in that said method comprising the steps of:
(1) start the service end process, and the service end process is registered in the Service Management, specific handle sign is set in Service Management, the service end process enters the LOOP state, waits for the request of client;
(2) client process is according to the agent object of specific handle sign to the services request acquisition service end of Service Management submission use service end, the agent object of client call service end;
(3) agent object passes through Send() function be encapsulated into message in the container and be transferred to service end after enter blocked state, wait for that service end returns result;
(4) service end is passed through OnSend() function takes out message from container, calls local realization function operation, and the return messages container of packing into is returned to agent object; Client works on after receiving return message.
3. method according to claim 1 is characterized in that the process of client process and service end is directly switched in the described method.
4. method according to claim 1, when it is characterized in that carrying out in the described method message transmission, operating system nucleus is mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by the local function operation of realizing.
5. the system that carries out interprocess communication by Service Management between service end and client comprises the service management module that is arranged between service end and client; It is characterized in that described service management module accepts the registration of service end process, the sign handle of the service end process of registration is provided; Client process submits to the services request of using service end to obtain the agent object of service end according to specific handle sign to service management module, and the agent object of client by calling service end passes to the service end process with the message of client; Service end to the Message Processing of client after agent object by service end be transferred to client.
6. the system that carries out interprocess communication by Service Management between service end according to claim 5 and client, when it is characterized in that service end is obtained the message of client by agent object in the described system, operating system nucleus is mapped to service end in the address space zone of kernel administration, and directly the data with client copy to this zone by the local function operation of realizing of service end.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN 201110037259 CN102103526A (en) | 2011-02-14 | 2011-02-14 | Method and system for performing inter-process communication between server and client by service management |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN 201110037259 CN102103526A (en) | 2011-02-14 | 2011-02-14 | Method and system for performing inter-process communication between server and client by service management |
Publications (1)
Publication Number | Publication Date |
---|---|
CN102103526A true CN102103526A (en) | 2011-06-22 |
Family
ID=44156315
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN 201110037259 Pending CN102103526A (en) | 2011-02-14 | 2011-02-14 | Method and system for performing inter-process communication between server and client by service management |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN102103526A (en) |
Cited By (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102355429A (en) * | 2011-08-12 | 2012-02-15 | 北京思创银联科技股份有限公司 | Pipeline-based inter-process message communication method |
CN102591726A (en) * | 2011-12-31 | 2012-07-18 | 青岛海信宽带多媒体技术有限公司 | Multiprocess communication method |
CN102609310A (en) * | 2012-02-14 | 2012-07-25 | 浪潮(北京)电子信息产业有限公司 | Computer operating system and inter-process communication method therefor |
CN102654840A (en) * | 2011-11-30 | 2012-09-05 | 天津书生投资有限公司 | Function callback method and system |
CN102662778A (en) * | 2012-04-28 | 2012-09-12 | 杭州格畅科技有限公司 | Callback response method of inter-application communication on online application platform, application and online application platform |
WO2015067162A1 (en) * | 2013-11-07 | 2015-05-14 | Tencent Technology (Shenzhen) Company Limited | Method and device for exchanging data between processes |
CN105279015A (en) * | 2014-05-29 | 2016-01-27 | 黑莓有限公司 | System and method for coordinating process and memory management across domains |
CN105337849A (en) * | 2015-12-07 | 2016-02-17 | 上海斐讯数据通信技术有限公司 | Synchronous message handling method, synchronous message controller and sending and receiving devices |
CN106027365A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股(北京)有限公司 | Information interaction method and device |
CN106330474A (en) * | 2015-06-15 | 2017-01-11 | 国核(北京)科学技术研究院有限公司 | Nuclear power plant reactor core monitoring and managing device and monitoring and managing method thereof |
CN106354608A (en) * | 2016-09-30 | 2017-01-25 | 北京海誉动想科技股份有限公司 | Device and method for requesting for registration and management of electronic equipment hardware |
CN106878376A (en) * | 2016-12-23 | 2017-06-20 | 微梦创科网络科技(中国)有限公司 | A configuration management method and system |
CN107239353A (en) * | 2017-06-02 | 2017-10-10 | 浪潮金融信息技术有限公司 | Inter-process communication methods and system |
CN107438060A (en) * | 2016-05-28 | 2017-12-05 | 华为技术有限公司 | Remote procedure calling (PRC) method and the network equipment in a kind of network equipment |
CN107526645A (en) * | 2017-09-06 | 2017-12-29 | 武汉斗鱼网络科技有限公司 | A kind of communication optimization method and system |
CN108287723A (en) * | 2016-12-30 | 2018-07-17 | 华为技术有限公司 | A kind of application exchange method, device, physical machine and system |
CN108322307A (en) * | 2017-01-16 | 2018-07-24 | 中标软件有限公司 | Communication system and method between container based on kernel memory sharing |
CN108345452A (en) * | 2017-01-23 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of thread management method and device |
CN109062507A (en) * | 2018-07-18 | 2018-12-21 | 武汉中旗生物医疗电子有限公司 | The processing storage method and device of electrocardiogram (ECG) data |
CN109213611A (en) * | 2018-08-01 | 2019-01-15 | 天津字节跳动科技有限公司 | The striding course means of communication, device, terminal and storage medium |
CN109314726A (en) * | 2016-06-20 | 2019-02-05 | 华为技术有限公司 | The system and method communicated between operating system container |
CN109688128A (en) * | 2018-12-21 | 2019-04-26 | 成都安世亚太科技有限公司 | Real-time distributed objective system software frame based on reliable UDP agreement |
CN109933443A (en) * | 2019-03-07 | 2019-06-25 | 腾讯科技(深圳)有限公司 | Inter-process communication methods, device, computer equipment and readable storage medium storing program for executing |
CN110018908A (en) * | 2018-01-08 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | A kind of inter-process communication methods, electronic equipment and readable storage medium storing program for executing |
CN110046047A (en) * | 2019-04-15 | 2019-07-23 | Oppo广东移动通信有限公司 | An inter-process communication method, device and computer-readable storage medium |
CN110532106A (en) * | 2019-07-16 | 2019-12-03 | 华为技术有限公司 | The means of communication, device, equipment and storage medium between process |
CN106470221B (en) * | 2015-08-18 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Method for improving inter-process communication coordination efficiency |
CN111385251A (en) * | 2018-12-28 | 2020-07-07 | 武汉斗鱼网络科技有限公司 | Method, system, server and storage medium for improving operation stability of client |
CN111756846A (en) * | 2020-06-24 | 2020-10-09 | 杭州安森智能信息技术有限公司 | Method for light-weight robot cross-process communication |
CN112068906A (en) * | 2020-08-31 | 2020-12-11 | 南京卓盛云信息科技有限公司 | Calling method and system based on container technology proxy dynamic library |
CN112241329A (en) * | 2020-09-28 | 2021-01-19 | 深圳市商汤科技有限公司 | Monitoring method, device and equipment of recognition engine and storage medium |
CN112667419A (en) * | 2021-01-04 | 2021-04-16 | 南京海兴电网技术有限公司 | Multi-process communication method based on client server model |
CN112866403A (en) * | 2021-02-02 | 2021-05-28 | 世邦通信股份有限公司 | Communication system |
CN113010333A (en) * | 2021-03-24 | 2021-06-22 | 北京中电兴发科技有限公司 | Multi-scene inter-process communication method suitable for Linux server cluster |
CN113886105A (en) * | 2021-09-30 | 2022-01-04 | 北京字节跳动网络技术有限公司 | Cross-process calling method and device, storage medium and electronic equipment |
CN114697162A (en) * | 2022-03-26 | 2022-07-01 | 浪潮云信息技术股份公司 | A kind of IoT gateway implementation method and system based on microkernel architecture |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1470988A (en) * | 2002-07-25 | 2004-01-28 | 梁肇新 | Inter-process calling gate technique |
US20060036722A1 (en) * | 2004-07-09 | 2006-02-16 | Alcatel | NMS with multi-server change requests processing |
CN1811717A (en) * | 2006-01-10 | 2006-08-02 | 杭州东信灵通电子实业公司 | Universal interprocess communication achieving method |
CN101782864A (en) * | 2009-12-01 | 2010-07-21 | 深圳市蓝韵实业有限公司 | Method for improving communication service stability of Web server |
-
2011
- 2011-02-14 CN CN 201110037259 patent/CN102103526A/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1470988A (en) * | 2002-07-25 | 2004-01-28 | 梁肇新 | Inter-process calling gate technique |
US20060036722A1 (en) * | 2004-07-09 | 2006-02-16 | Alcatel | NMS with multi-server change requests processing |
CN1811717A (en) * | 2006-01-10 | 2006-08-02 | 杭州东信灵通电子实业公司 | Universal interprocess communication achieving method |
CN101782864A (en) * | 2009-12-01 | 2010-07-21 | 深圳市蓝韵实业有限公司 | Method for improving communication service stability of Web server |
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102355429A (en) * | 2011-08-12 | 2012-02-15 | 北京思创银联科技股份有限公司 | Pipeline-based inter-process message communication method |
CN102654840A (en) * | 2011-11-30 | 2012-09-05 | 天津书生投资有限公司 | Function callback method and system |
CN102591726A (en) * | 2011-12-31 | 2012-07-18 | 青岛海信宽带多媒体技术有限公司 | Multiprocess communication method |
CN102591726B (en) * | 2011-12-31 | 2014-04-09 | 青岛海信宽带多媒体技术有限公司 | Multiprocess communication method |
CN102609310A (en) * | 2012-02-14 | 2012-07-25 | 浪潮(北京)电子信息产业有限公司 | Computer operating system and inter-process communication method therefor |
CN102662778A (en) * | 2012-04-28 | 2012-09-12 | 杭州格畅科技有限公司 | Callback response method of inter-application communication on online application platform, application and online application platform |
WO2015067162A1 (en) * | 2013-11-07 | 2015-05-14 | Tencent Technology (Shenzhen) Company Limited | Method and device for exchanging data between processes |
US9965341B2 (en) | 2013-11-07 | 2018-05-08 | Tencent Technology (Shenzhen) Company Limited | Method and device for exchanging data between processes |
CN105279015B (en) * | 2014-05-29 | 2021-01-01 | 黑莓有限公司 | System and method for cross-domain coordination of processes and memory management |
CN105279015A (en) * | 2014-05-29 | 2016-01-27 | 黑莓有限公司 | System and method for coordinating process and memory management across domains |
CN106330474A (en) * | 2015-06-15 | 2017-01-11 | 国核(北京)科学技术研究院有限公司 | Nuclear power plant reactor core monitoring and managing device and monitoring and managing method thereof |
CN106470221B (en) * | 2015-08-18 | 2019-12-31 | 北京京东尚科信息技术有限公司 | Method for improving inter-process communication coordination efficiency |
CN105337849B (en) * | 2015-12-07 | 2019-09-13 | 上海斐讯数据通信技术有限公司 | Synchronous message processing method, synchronous message controller, sending and receiving equipment |
CN105337849A (en) * | 2015-12-07 | 2016-02-17 | 上海斐讯数据通信技术有限公司 | Synchronous message handling method, synchronous message controller and sending and receiving devices |
CN106027365A (en) * | 2016-04-29 | 2016-10-12 | 乐视控股(北京)有限公司 | Information interaction method and device |
CN107438060A (en) * | 2016-05-28 | 2017-12-05 | 华为技术有限公司 | Remote procedure calling (PRC) method and the network equipment in a kind of network equipment |
US10831574B2 (en) | 2016-05-28 | 2020-11-10 | Huawei Technologies Co., Ltd. | Remote procedure call method for network device and network device |
CN109314726A (en) * | 2016-06-20 | 2019-02-05 | 华为技术有限公司 | The system and method communicated between operating system container |
CN106354608A (en) * | 2016-09-30 | 2017-01-25 | 北京海誉动想科技股份有限公司 | Device and method for requesting for registration and management of electronic equipment hardware |
CN106354608B (en) * | 2016-09-30 | 2019-08-23 | 北京海誉动想科技股份有限公司 | The device and method of electronic equipment hardware requests registration management |
CN106878376A (en) * | 2016-12-23 | 2017-06-20 | 微梦创科网络科技(中国)有限公司 | A configuration management method and system |
CN108287723B (en) * | 2016-12-30 | 2022-07-12 | 华为技术有限公司 | Application interaction method and device, physical machine and system |
US10866846B2 (en) | 2016-12-30 | 2020-12-15 | Huawei Technologies Co., Ltd. | Application interaction method, apparatus, and system, and physical machine |
CN108287723A (en) * | 2016-12-30 | 2018-07-17 | 华为技术有限公司 | A kind of application exchange method, device, physical machine and system |
CN108322307A (en) * | 2017-01-16 | 2018-07-24 | 中标软件有限公司 | Communication system and method between container based on kernel memory sharing |
CN108345452A (en) * | 2017-01-23 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of thread management method and device |
CN108345452B (en) * | 2017-01-23 | 2021-07-23 | 斑马智行网络(香港)有限公司 | A thread management method and device |
CN107239353A (en) * | 2017-06-02 | 2017-10-10 | 浪潮金融信息技术有限公司 | Inter-process communication methods and system |
WO2019047441A1 (en) * | 2017-09-06 | 2019-03-14 | 武汉斗鱼网络科技有限公司 | Communication optimization method and system |
CN107526645A (en) * | 2017-09-06 | 2017-12-29 | 武汉斗鱼网络科技有限公司 | A kind of communication optimization method and system |
CN110018908A (en) * | 2018-01-08 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | A kind of inter-process communication methods, electronic equipment and readable storage medium storing program for executing |
CN110018908B (en) * | 2018-01-08 | 2021-05-28 | 武汉斗鱼网络科技有限公司 | An inter-process communication method, electronic device and readable storage medium |
CN109062507A (en) * | 2018-07-18 | 2018-12-21 | 武汉中旗生物医疗电子有限公司 | The processing storage method and device of electrocardiogram (ECG) data |
CN109213611A (en) * | 2018-08-01 | 2019-01-15 | 天津字节跳动科技有限公司 | The striding course means of communication, device, terminal and storage medium |
CN109688128A (en) * | 2018-12-21 | 2019-04-26 | 成都安世亚太科技有限公司 | Real-time distributed objective system software frame based on reliable UDP agreement |
CN111385251A (en) * | 2018-12-28 | 2020-07-07 | 武汉斗鱼网络科技有限公司 | Method, system, server and storage medium for improving operation stability of client |
CN109933443A (en) * | 2019-03-07 | 2019-06-25 | 腾讯科技(深圳)有限公司 | Inter-process communication methods, device, computer equipment and readable storage medium storing program for executing |
CN110046047A (en) * | 2019-04-15 | 2019-07-23 | Oppo广东移动通信有限公司 | An inter-process communication method, device and computer-readable storage medium |
CN110532106A (en) * | 2019-07-16 | 2019-12-03 | 华为技术有限公司 | The means of communication, device, equipment and storage medium between process |
CN110532106B (en) * | 2019-07-16 | 2023-01-13 | 华为技术有限公司 | Inter-process communication method, device, equipment and storage medium |
CN111756846A (en) * | 2020-06-24 | 2020-10-09 | 杭州安森智能信息技术有限公司 | Method for light-weight robot cross-process communication |
CN111756846B (en) * | 2020-06-24 | 2023-09-29 | 杭州安森智能信息技术有限公司 | Cross-process communication method for lightweight robot |
CN112068906A (en) * | 2020-08-31 | 2020-12-11 | 南京卓盛云信息科技有限公司 | Calling method and system based on container technology proxy dynamic library |
CN112241329A (en) * | 2020-09-28 | 2021-01-19 | 深圳市商汤科技有限公司 | Monitoring method, device and equipment of recognition engine and storage medium |
CN112667419A (en) * | 2021-01-04 | 2021-04-16 | 南京海兴电网技术有限公司 | Multi-process communication method based on client server model |
CN112667419B (en) * | 2021-01-04 | 2024-10-22 | 南京海兴电网技术有限公司 | Multi-process communication method based on client server model |
CN112866403A (en) * | 2021-02-02 | 2021-05-28 | 世邦通信股份有限公司 | Communication system |
CN113010333B (en) * | 2021-03-24 | 2021-10-15 | 北京中电兴发科技有限公司 | Multi-scene inter-process communication method suitable for Linux server cluster |
CN113010333A (en) * | 2021-03-24 | 2021-06-22 | 北京中电兴发科技有限公司 | Multi-scene inter-process communication method suitable for Linux server cluster |
CN113886105A (en) * | 2021-09-30 | 2022-01-04 | 北京字节跳动网络技术有限公司 | Cross-process calling method and device, storage medium and electronic equipment |
CN113886105B (en) * | 2021-09-30 | 2023-07-21 | 抖音视界有限公司 | Cross-process calling method and device, storage medium and electronic equipment |
CN114697162A (en) * | 2022-03-26 | 2022-07-01 | 浪潮云信息技术股份公司 | A kind of IoT gateway implementation method and system based on microkernel architecture |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102103526A (en) | Method and system for performing inter-process communication between server and client by service management | |
CN101354693B (en) | An inter-core communication scheduling system and method for a heterogeneous multi-core processor | |
JP4690437B2 (en) | Communication method, communication apparatus and program for network application | |
US6272559B1 (en) | Deferred reconstruction of objects and remote loading for event notification in a distributed system | |
CN103442049B (en) | The mixed clouds operating system architecture of a kind of component-oriented and communication means thereof | |
CN104050007B (en) | Binary translation and application stream processes and system based on QOS | |
JP2000020490A (en) | Computer having remote procedure call mechanism or object request broker mechanism, data transfer method, and transfer method storage medium | |
US9274972B2 (en) | Handling cross-platform system call with a shared page cache in a hybrid computing system | |
US20210365389A1 (en) | Execution space agnostic device drivers | |
JP2002505466A (en) | Remote method invocation method and apparatus | |
CN101303656A (en) | A Java Application Program Remote Direct Memory Access Method | |
WO2021159820A1 (en) | Data transmission and task processing methods, apparatuses and devices | |
CN101158936A (en) | A data transmission system, device and method between nodes | |
CN110471777A (en) | Multiple users share uses the method and system of Spark cluster in a kind of Python-Web environment | |
CN107682460A (en) | A kind of distributed storage trunked data communication method and system | |
CN114371935B (en) | Gateway processing method, gateway, device and medium | |
CN109800035B (en) | Algorithm integrated service framework system | |
CN105573852B (en) | A kind of method of Ultrahigh speed data object communication under virtual address isolation environment | |
CN113296890B (en) | An Android virtualization method and system based on system call proxy | |
CN112783675B (en) | IPC communication method | |
CN115934385A (en) | A multi-core inter-core communication method, system, device and storage medium | |
CN102480480B (en) | Resource scheduling method under ubiquitous computing environment | |
CN101004677A (en) | Method for implementing CASE environment tools bus based on CORBA criterion | |
CN108200177A (en) | A kind of method and system of Non-blocking Synchronization pattern database middleware network communication | |
Peng et al. | Fast interprocess communication algorithm in microkernel |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20110622 |