CN112199205A - Program communication method between heterogeneous platforms - Google Patents
Program communication method between heterogeneous platforms Download PDFInfo
- Publication number
- CN112199205A CN112199205A CN201910617450.8A CN201910617450A CN112199205A CN 112199205 A CN112199205 A CN 112199205A CN 201910617450 A CN201910617450 A CN 201910617450A CN 112199205 A CN112199205 A CN 112199205A
- Authority
- CN
- China
- Prior art keywords
- program
- call
- platform
- call request
- data interaction
- 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.)
- Granted
Links
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
- 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/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a program communication method between heterogeneous platforms, which introduces respective data interaction processes on each platform, the platform program puts a call request into a call cache region, the data interaction process obtains the call request, and the call request is remotely communicated with programs of other platforms based on the call request, and a call result is obtained and returned to the platform program. The method simplifies the platform program design and improves the program operation efficiency.
Description
[ technical field ] A method for producing a semiconductor device
The invention belongs to the field of computers, and particularly relates to a program communication method between heterogeneous platforms.
[ background of the invention ]
The existing computer has a plurality of different heterogeneous platforms, and with the development of network and information technology, different platforms need to communicate through the network. A typical situation is where a program on one platform needs to remotely invoke a program on another platform, which requires program communication between the different platforms. The existing inter-platform program communication method needs the program to know the condition of the opposite platform and carries out corresponding processing based on the type of the opposite platform, which brings certain difficulty to the design and the writing of the program. In addition, long-range communication between platforms may cause a timeout problem.
[ summary of the invention ]
In order to solve the above problems in the prior art, the present invention provides a program communication method between heterogeneous platforms.
The technical scheme adopted by the invention is as follows:
a program communication method between heterogeneous platforms comprises the following steps:
(1) a program PA running on a platform A generates a calling request, wherein the calling request comprises an identifier of a platform B, an identifier and an interface of a program PB, a calling parameter and a calling request identifier; wherein, the program PB is a program called by the program PA, and the program PB runs on the platform B;
(2) the program PA writes the calling request into a calling cache region of the platform A;
(3) a data interaction process CA running on the platform A reads and analyzes the call request from the call cache region to obtain the relevant information of the call request;
(4) the data interaction process CA formats the relevant information of the call request according to the relevant requirements of the platform B to generate a second call request, wherein the second call request also comprises an identifier of the platform A;
(5) the data interaction process CA sends the second call request to a platform B, and the platform B stores the received second call request in a receiving cache region;
(6) a data interaction process CB running on the platform B reads the second calling request from the receiving cache region, creates a calling thread, and calls a corresponding interface of the program PB based on the information in the second calling request and transmits the calling parameter;
(7) the program PB receives the call based on the call parameter, generates a corresponding processing result, and returns the processing result to the call thread, and the call thread stores the processing result and a corresponding call request identifier in a result cache area of the platform B;
(8) the data interaction process CB reads the processing result and the calling request identifier from the result cache region, determines a platform A corresponding to the calling request according to the calling request identifier, formats the processing result according to the relevant requirements of the platform A, and generates a second processing result meeting the requirements of the platform A, wherein the second processing result comprises the formatted result of the processing result and the calling request identifier;
(9) the data interaction process CB sends the second processing result to the platform A, and the platform A stores the received second processing result in a result return cache region;
(10) the data interaction process CA reads the second processing result from a result return cache region, and determines a program PA corresponding to the second processing result according to a call request identifier in the second processing result;
(11) and the data interaction process CA sends the second processing result to a program PA.
Further, the call request also includes a limited time parameter T, which represents the maximum acceptable waiting time for the PA to make a remote call, and the system records the time T when the call request is written into the call buffer0；
When the data interaction process CA reads the call request in step 3, the CA calculates the remaining time T1＝T0+T-TnowWherein T isnowIs the current time;
the data interaction process CA calculates the minimum expected time T of the processing resultminI.e. Tmin＝T2+T3(ii) a Wherein, T2Is the path time, T, of data transmitted back and forth between platform A and platform B3Is a predefined minimum time for program PB to process the call;
data interaction process CA judgment T1And TminThe size relationship of (1):
if T is1＜TminIf so, the data interaction process CA directly returns a failure result to the program PA;
if T is1≥TminIf the data interaction process CA continues to execute the subsequent steps, the CA starts a timer, the timer starts to time from 0, and when the timer times to T1If the CA has not obtained the corresponding second processing result, the CA returns a timeout result to the program PA, informing it that the returned result is timeout.
Furthermore, the call cache area is a storage area specially opened in the memory of the platform a, the call cache area is divided into a plurality of segments in advance, each segment stores a call request, and when the program PA writes the call request into one of the segments, the identifier of the program PA is written at the same time, and the identifier indicates that the segment is occupied by the program PA.
Further, the call buffer is controlled by the system, and allows each program to write in the empty segment, but does not allow each program to read the data of each call request in the call buffer, and only allows the data interaction process CA to read the data of the call request.
Further, after the CA sends the second call request, the CA clears the corresponding call request in the call cache.
Further, the receiving cache region is a storage region opened in the memory of the platform B and used for storing the received call request, the receiving cache region is divided into a plurality of segments, each segment stores one received call request, and the receiving cache region can only be read by the data interaction process CB on the platform B.
Further, the data interaction process CB may simultaneously start a plurality of call threads to call different programs, respectively.
Further, when the calling thread is created, the corresponding calling request identifier is obtained by the CB.
Further, the program PA is in a state of waiting for a result after issuing the call request.
Further, the CA wakes up the PA from the waiting state and delivers the second processing result after obtaining the second processing result.
The invention has the beneficial effects that: the remote calling program design among heterogeneous platform programs is simplified, the overtime processing is carried out in time, and the program operation efficiency is improved.
[ description of the drawings ]
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, and are not to be considered limiting of the invention, in which:
FIG. 1 is a schematic structural diagram of a plurality of heterogeneous platforms of the present invention.
[ detailed description ] embodiments
The present invention will now be described in detail with reference to the drawings and specific embodiments, wherein the exemplary embodiments and descriptions are provided only for the purpose of illustrating the present invention and are not to be construed as limiting the present invention.
Referring to fig. 1, the structure between multiple heterogeneous platforms according to the present invention is shown, which includes at least two or more platforms, where the platforms communicate with each other through a network, where the network may be the internet or a local area network.
Two platforms are shown in fig. 1: the system comprises a platform A and a platform B, wherein a program PA runs in the platform A, a program PB runs in the platform B, and the program PA needs to communicate with the program PB. Specifically, the communication refers to that the program PA remotely calls the program PB, and then the program PB returns the call result to the program PA.
In order to complete the communication, the invention introduces a data interaction process CA and a data interaction process CB on the platform A and the platform B respectively, and the process CA and the CB helper programs PA and PB complete the communication between the platforms. The program communication method of the present invention is explained in detail below.
(1) Program PA generates a call request comprising an identifier of platform B, an identifier and interface of program PB to be called, call parameters, a call request identifier.
In order to distinguish each platform, a unique identifier needs to be set for each platform in advance, and each program identifies the platform which needs to communicate specifically. The identifier of the program PB may be generally the name of the program PB itself, and when the program PB runs, one or more call interfaces may be provided to the outside, and when the call is performed, corresponding parameters need to be provided, which are all known to the program PA in advance. The invocation request identifier is a unique identifier generated by the PA to identify the invocation request.
Based on the above information, the program PA may generate a corresponding call request.
(2) And the program PA writes the calling request into a calling cache region of the platform A.
The calling cache area is a special storage area in the memory of the platform A and is used for placing calling requests during program communication. The calling buffer area is divided into a plurality of sections in advance, each section stores a calling request, and when the calling request is written into one of the sections by the program PA, the identifier of the program PA is written at the same time, and the identifier indicates that the section is occupied by the program PA.
According to an embodiment of the present invention, a circular queue may be formed among the plurality of segments, and each write call request is written into an empty segment at the tail of the queue. Of course, other organizations may be used, and the present invention is not limited in this regard.
For data security, the call buffer is controlled by the system, and each program can write the empty segment, but each program is not allowed to read the data of each call request in the call buffer, and only the data interaction process is allowed to read the data.
(3) And the data interaction process CA reads and analyzes the call request from the call cache region to obtain the relevant information of the call request.
Specifically, since there may be a plurality of call requests stored in the call buffer at the same time, the data interaction process CA needs to fetch the call requests from the call buffer in a predetermined order. Generally, the predetermined order is in the chronological order, i.e., first-in-first-out, that the call requests are placed into the call buffer. For example, if the call buffer is organized as a circular queue, the call request may be fetched from the head of the queue.
The related information of the call request acquired by the data interaction process CA includes an identifier of the program PA to which the data interaction process CA belongs, an identifier of the platform B, an identifier and an interface of the program PB to be called, a call parameter and a call request identifier.
(4) And the data interaction process CA formats the relevant information of the call request according to the relevant requirements of the platform B, and generates a new call request (hereinafter referred to as a second call request), wherein the second call request also comprises an identifier of the platform A.
Since different heterogeneous platforms have different requirements for data formats, call formats, and the like, the CA needs to process the call request according to the requirements of the platform B and format the call request into a second call request meeting the requirements of the platform B. By the mode, the data interaction process can automatically process format conversion among different platforms, and the details are shielded for the program PA at the upper layer, so that a designer of the program PA does not need to care about conversion requirements among heterogeneous platforms, and the program design is simplified.
(5) And the data interaction process CA sends the second call request to the platform B, and the platform B stores the received second call request in a receiving cache region.
As described above, the invocation request includes the identifier of the platform B, so the CA can know that the invocation request needs to be sent to the platform B, and based on the address of the platform B stored in advance, the CA can send the second invocation request to the platform B. After the CA sends the second call request, the CA may clear the corresponding call request in the call cache.
The receiving cache region is a storage region opened in the memory of the platform B and used for storing the received calling request. Similar to the call buffer, the receive buffer is also divided into segments, each storing a received call request, and may constitute a first-in-first-out circular queue. The receiving buffer zone can only be read by a data interaction process CB on the platform B.
(6) And the data interaction process CB reads the second calling request from the receiving cache region, creates a calling thread, calls a corresponding interface of the program PB based on the information in the second calling request, and transmits the calling parameter.
As described above, the second call request includes the program PB to be called, the interface, and the call parameter, so that the CB can obtain the call target of the second call request, call the corresponding interface of the PB, and transfer the call parameter provided by the PA to the PB.
The data interaction process CB can simultaneously start a plurality of calling threads and respectively call different programs, so that parallel processing can be ensured, and the processing efficiency is improved.
(7) And the program PB receives the call based on the call parameter, generates a corresponding processing result, and returns the processing result to the call thread, and the call thread stores the processing result and the corresponding call request identifier in a result cache region of the platform B.
When a calling thread is created, the corresponding call request identifier is obtained by the CB, and thus the call request identifier can be used to identify the call request to which the processing result belongs.
The result buffer area is similar to the receiving buffer area and is a storage area opened in the memory of the platform B and used for storing the processing result, the result buffer area is also divided into a plurality of segments, each segment stores one processing result and a corresponding calling request identifier, and a first-in first-out circular queue can also be formed.
The result buffer can be written into the empty segment by each program, but only allows the data interaction process to read, so as to ensure the data security.
(8) And the data interaction process CB reads the processing result and the calling request identifier from the result cache region, determines a platform A corresponding to the calling request according to the calling request identifier, formats the processing result according to the relevant requirements of the platform A, and generates a second processing result meeting the requirements of the platform A, wherein the second processing result comprises the formatted result of the processing result and the calling request identifier.
Specifically, the CB may query and obtain a corresponding second call request according to the call request identifier, and further obtain the platform a identifier in the second call request, so that the CB may know that the processing result should be sent to the platform a, and may format the processing result into the second processing result meeting the requirement of the platform a according to the requirement of the platform a. By the method, the data interaction process CB shields the details of remote calling for the program PB, and the program design is simplified.
(9) And the data interaction process CB sends the second processing result to the platform A, and the platform A stores the received second processing result in a result return cache region.
Similar to the other types of cache regions, the result return cache region is also a storage region opened in the memory of the platform a for storing the processing results returned by other platforms, the result return cache region is also divided into a plurality of segments, each segment stores a second processing result, and a first-in first-out circular queue can also be formed. The result return buffer can only be read by the data interaction process CA.
(10) And the data interaction process CA reads the second processing result from the result return cache region, and determines a program PA corresponding to the second processing result according to the calling request identifier in the second processing result.
When sending a call request, the data interaction process CA should store the correspondence between the call request identifier and the program PA, so that the corresponding program PA can be determined based on the call request identifier.
(11) And the data interaction process CA sends the second processing result to a program PA.
In a specific implementation, the program PA may be in a state of waiting for a result after issuing the call request, and the CA wakes up the PA from the waiting state and delivers the second processing result after obtaining the second processing result.
The above process is the basic process of the program communication method of the present invention, but in the practical process, the program remote communication between different platforms faces the time limit. For example, when the PA remotely invokes the PB, the PB fails to return the processing result in time, and the PA may not wait forever, for various reasons. Another example is: some programs have a limit on the response time of the call, requiring the called program to return results within a defined time, and therefore even if the PB returns the processed results, it may exceed the PA-defined time. Both of these situations can cause errors in the calling process.
Based on the above basic process, the invention introduces the relevant time parameter. Specifically, the call request generated by the PA further includes a limited time parameter T, where the limited time parameter T represents the maximum acceptable waiting time for the PA to make a remote call. At the same time, isThe system records the time T when the call request is written into the call buffer0。
When the data interaction process CA reads the call request in step 3 above, it can obtain T0And T, CA first calculates the remaining time T1＝T0+T-TnowWherein T isnowIs the current time. The T is1In effect representing the time remaining for an acceptable result for the PA.
The data interaction process CA calculates the minimum expected time T of the processing resultminI.e. Tmin＝T2+T3，
Wherein, T2Is the time of flight for data to travel back and forth once between platform a and platform B, which CA may acquire by timing the data transfer with the platform (e.g., by ping, or heartbeat data transfer). T is3Is a predefined minimum time for program PB to process the call, which may be obtained empirically or may be derived from past times when PB processes similar calls (e.g., minimum of past n processing times).
Data interaction process CA judgment T1And TminThe size relationship of (1):
if T is1＜TminIf the time requirement of the PA cannot be met, the data interaction process CA directly returns a failure result to the program PA.
If T is1≥TminIf the data interaction process CA continues to execute the subsequent steps, the CA starts a timer, the timer starts to time from 0, and when the timer times to T1If the CA has not obtained the corresponding second processing result, the CA returns a timeout result to the program PA, informing it that the returned result is timeout.
Through the related processing process of the limited time parameter, the timeout problem of remote calling can be better solved, and the program running efficiency is improved.
The above description is only a preferred embodiment of the present invention, and all equivalent changes or modifications of the structure, characteristics and principles described in the present invention are included in the scope of the present invention.
Claims (10)
1. A program communication method between heterogeneous platforms is characterized by comprising the following steps:
(1) a program PA running on a platform A generates a calling request, wherein the calling request comprises an identifier of a platform B, an identifier and an interface of a program PB, a calling parameter and a calling request identifier; wherein, the program PB is a program called by the program PA, and the program PB runs on the platform B;
(2) the program PA writes the calling request into a calling cache region of the platform A;
(3) a data interaction process CA running on the platform A reads and analyzes the call request from the call cache region to obtain the relevant information of the call request;
(4) the data interaction process CA formats the relevant information of the call request according to the relevant requirements of the platform B to generate a second call request, wherein the second call request also comprises an identifier of the platform A;
(5) the data interaction process CA sends the second call request to a platform B, and the platform B stores the received second call request in a receiving cache region;
(6) a data interaction process CB running on the platform B reads the second calling request from the receiving cache region, creates a calling thread, and calls a corresponding interface of the program PB based on the information in the second calling request and transmits the calling parameter;
(7) the program PB receives the call based on the call parameter, generates a corresponding processing result, and returns the processing result to the call thread, and the call thread stores the processing result and a corresponding call request identifier in a result cache area of the platform B;
(8) the data interaction process CB reads the processing result and the calling request identifier from the result cache region, determines a platform A corresponding to the calling request according to the calling request identifier, formats the processing result according to the relevant requirements of the platform A, and generates a second processing result meeting the requirements of the platform A, wherein the second processing result comprises the formatted result of the processing result and the calling request identifier;
(9) the data interaction process CB sends the second processing result to the platform A, and the platform A stores the received second processing result in a result return cache region;
(10) the data interaction process CA reads the second processing result from a result return cache region, and determines a program PA corresponding to the second processing result according to a call request identifier in the second processing result;
(11) and the data interaction process CA sends the second processing result to a program PA.
2. The method of claim 1, wherein the call request further comprises a time limit parameter T, wherein the time limit parameter T represents a maximum acceptable waiting time for the PA to make a remote call, and wherein the system records the time T when the call request is written into the call buffer0；
When the data interaction process CA reads the call request in step 3, the CA calculates the remaining time T1＝T0+T-TnowWherein T isnowIs the current time;
the data interaction process CA calculates the minimum expected time T of the processing resultminI.e. Tmin＝T2+T3(ii) a Wherein, T2Is the path time, T, of data transmitted back and forth between platform A and platform B3Is a predefined minimum time for program PB to process the call;
data interaction process CA judgment T1And TminThe size relationship of (1):
if T is1＜TminIf so, the data interaction process CA directly returns a failure result to the program PA;
if T is1≥TminIf the data interaction process CA continues to execute the subsequent steps, the CA starts a timer, the timer starts to time from 0, and when the timer times to T1CA has not yet acquired a corresponding second processing nodeIf so, the CA returns a timeout result to the program PA, informing it that the returned result is timeout.
3. Method according to any of claims 1-2, characterized in that the call buffer is a specially created memory area in the platform a memory, the call buffer is divided into a plurality of segments in advance, each segment stores a call request, when the program PA writes its call request into one of the segments, the identifier of the program PA is written at the same time, the identifier indicates that the segment is occupied by the program PA.
4. The method according to claim 3, wherein the call buffer is controlled by the system, and each program is allowed to write the empty segment, but each program is not allowed to read the data of each call request in the call buffer, and only the data interaction process CA is allowed to read the call request data.
5. The method of any of claims 1-4, wherein after the CA sends the second call request, the CA clears the corresponding call request in the call cache.
6. The method according to any one of claims 1 to 5, wherein the receiving buffer is a storage area opened in a memory of platform B for storing the received call request, the receiving buffer is divided into a plurality of segments, each segment stores one received call request, and the receiving buffer can only be read by a data interaction process CB on platform B.
7. The method according to claim 1, wherein the data interaction process CB can simultaneously start a plurality of calling threads to respectively call different programs.
8. The method of claim 1, wherein the calling thread is created with a corresponding call request identifier obtained by a CB.
9. Method according to claim 1, characterized in that the program PA is in a state of waiting for a result after issuing a call request.
10. The method of claim 9, wherein the CA wakes up the PA from a wait state and delivers the second processing result after obtaining the second processing result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910617450.8A CN112199205B (en) | 2019-07-08 | 2019-07-08 | Program communication method between heterogeneous platforms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910617450.8A CN112199205B (en) | 2019-07-08 | 2019-07-08 | Program communication method between heterogeneous platforms |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199205A true CN112199205A (en) | 2021-01-08 |
| CN112199205B CN112199205B (en) | 2023-10-27 |
Family
ID=74004716
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910617450.8A Active CN112199205B (en) | 2019-07-08 | 2019-07-08 | Program communication method between heterogeneous platforms |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199205B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5265250A (en) * | 1990-03-29 | 1993-11-23 | At&T Bell Laboratories | Apparatus and methods for performing an application-defined operation on data as part of a system-defined operation on the data |
| US6594689B1 (en) * | 1997-05-08 | 2003-07-15 | Unisys Corporation | Multi-platform helper utilities |
| CN1811717A (en) * | 2006-01-10 | 2006-08-02 | 杭州东信灵通电子实业公司 | Universal interprocess communication achieving method |
| CN104133674A (en) * | 2014-07-11 | 2014-11-05 | 国家电网公司 | Heterogeneous system and model synchronization method of heterogeneous system |
| CN105357273A (en) * | 2015-09-30 | 2016-02-24 | 山东乾云启创信息科技股份有限公司 | Universal SOCKET communication and process management platform and method in asynchronous communication mode |
| CN105357266A (en) * | 2015-09-30 | 2016-02-24 | 山东乾云启创信息科技股份有限公司 | Universal SOCKET communication and process management platform applied to multiple scenes and method |
| CN106357591A (en) * | 2015-07-16 | 2017-01-25 | 中兴通讯股份有限公司 | Inter-application data access method and device |
| CN107153583A (en) * | 2017-05-24 | 2017-09-12 | 努比亚技术有限公司 | A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium |
| CN107491355A (en) * | 2017-08-17 | 2017-12-19 | 山东浪潮商用***有限公司 | Funcall method and device between a kind of process based on shared drive |
| CN108228359A (en) * | 2016-12-15 | 2018-06-29 | 北京京东尚科信息技术有限公司 | Web programs integrate the method and system of processing data with R programs |
| US20180232403A1 (en) * | 2017-02-15 | 2018-08-16 | Ca, Inc. | Exposing databases via application program interfaces |
| CN108984317A (en) * | 2018-06-21 | 2018-12-11 | 北京奇虎科技有限公司 | The implementation method and device of interprocess communication IPC |
| CN109189584A (en) * | 2018-07-05 | 2019-01-11 | 北京三快在线科技有限公司 | Communication means, device, electronic equipment and storage medium between application program |
-
2019
- 2019-07-08 CN CN201910617450.8A patent/CN112199205B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5265250A (en) * | 1990-03-29 | 1993-11-23 | At&T Bell Laboratories | Apparatus and methods for performing an application-defined operation on data as part of a system-defined operation on the data |
| US6594689B1 (en) * | 1997-05-08 | 2003-07-15 | Unisys Corporation | Multi-platform helper utilities |
| CN1811717A (en) * | 2006-01-10 | 2006-08-02 | 杭州东信灵通电子实业公司 | Universal interprocess communication achieving method |
| CN104133674A (en) * | 2014-07-11 | 2014-11-05 | 国家电网公司 | Heterogeneous system and model synchronization method of heterogeneous system |
| CN106357591A (en) * | 2015-07-16 | 2017-01-25 | 中兴通讯股份有限公司 | Inter-application data access method and device |
| CN105357266A (en) * | 2015-09-30 | 2016-02-24 | 山东乾云启创信息科技股份有限公司 | Universal SOCKET communication and process management platform applied to multiple scenes and method |
| CN105357273A (en) * | 2015-09-30 | 2016-02-24 | 山东乾云启创信息科技股份有限公司 | Universal SOCKET communication and process management platform and method in asynchronous communication mode |
| CN108228359A (en) * | 2016-12-15 | 2018-06-29 | 北京京东尚科信息技术有限公司 | Web programs integrate the method and system of processing data with R programs |
| US20180232403A1 (en) * | 2017-02-15 | 2018-08-16 | Ca, Inc. | Exposing databases via application program interfaces |
| CN107153583A (en) * | 2017-05-24 | 2017-09-12 | 努比亚技术有限公司 | A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium |
| CN107491355A (en) * | 2017-08-17 | 2017-12-19 | 山东浪潮商用***有限公司 | Funcall method and device between a kind of process based on shared drive |
| CN108984317A (en) * | 2018-06-21 | 2018-12-11 | 北京奇虎科技有限公司 | The implementation method and device of interprocess communication IPC |
| CN109189584A (en) * | 2018-07-05 | 2019-01-11 | 北京三快在线科技有限公司 | Communication means, device, electronic equipment and storage medium between application program |
Non-Patent Citations (3)
| Title |
|---|
| JUAN A. RICO‑GALLEGO等: "Analytical Communication Performance Models as a metric in the partitioning of data‑parallel kernels on heterogeneous platforms", 《THE JOURNAL OF SUPERCOMPUTING》 * |
| ZHAOKUI LI 等: "Streaming Applications on Heterogeneous Platforms", 《ARXIV》 * |
| 张峻崎: "异构***间通信服务机制研究", 《网络与通信》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199205B (en) | 2023-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107729139B (en) | Method and device for concurrently acquiring resources | |
| US8112559B2 (en) | Increasing available FIFO space to prevent messaging queue deadlocks in a DMA environment | |
| CN112379995B (en) | DAG-based unitized distributed scheduling system and method | |
| EP0747832A2 (en) | Customer information control system and method in a loosely coupled parallel processing environment | |
| US20010016896A1 (en) | System for accessing distributed data cache channel at each network node to pass requests and data- | |
| US20050004952A1 (en) | Transaction processing method, transaction control apparatus and program thereof | |
| CN111752965A (en) | Real-time database data interaction method and system based on micro-service | |
| CN111857993B (en) | Method for calling user mode function in kernel mode | |
| JP2012512452A (en) | Multi-process barrier physical manager | |
| WO2020025049A1 (en) | Data synchronization method and apparatus, database host, and storage medium | |
| US5682507A (en) | Plurality of servers having identical customer information control procedure functions using temporary storage file of a predetermined server for centrally storing temporary data records | |
| US20110173287A1 (en) | Preventing messaging queue deadlocks in a dma environment | |
| US5790868A (en) | Customer information control system and method with transaction serialization control functions in a loosely coupled parallel processing environment | |
| JPH01142964A (en) | Memory management | |
| US5630133A (en) | Customer information control system and method with API start and cancel transaction functions in a loosely coupled parallel processing environment | |
| CN113946445A (en) | Multithreading module based on ASIC and multithreading control method | |
| CN110162381B (en) | Agent execution method in container | |
| CN112199205B (en) | Program communication method between heterogeneous platforms | |
| CN109710399B (en) | DSP communication task scheduling system and method | |
| CN112416414A (en) | Micro-service architecture containerized lightweight workflow system based on state machine | |
| CN110659303A (en) | Read-write control method and device for database nodes | |
| WO2022267646A1 (en) | Pod deployment method and apparatus | |
| CN107102901B (en) | Task processing method and device | |
| JP2001154862A (en) | Computer system and network system and recording medium | |
| CN109947732B (en) | Method for optimizing file descriptor use efficiency of cluster file system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |