CN111917737B - Cross-network RPC calling system and method - Google Patents
Cross-network RPC calling system and method Download PDFInfo
- Publication number
- CN111917737B CN111917737B CN202010675477.5A CN202010675477A CN111917737B CN 111917737 B CN111917737 B CN 111917737B CN 202010675477 A CN202010675477 A CN 202010675477A CN 111917737 B CN111917737 B CN 111917737B
- Authority
- CN
- China
- Prior art keywords
- client
- request
- cross
- server
- file
- 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.)
- Active
Links
Images
Classifications
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0209—Architectural arrangements, e.g. perimeter networks or demilitarized zones
-
- 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
-
- 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/2866—Architectures; Arrangements
- H04L67/2876—Pairs of inter-processing entities at each side of the network, e.g. split proxies
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a cross-network RPC calling system and a method, which comprises the following steps: the client is arranged at the side of a first local area network; and a server side arranged on a second local area network side, wherein the server is in communication connection with the client side through a cross-optical-gate universal RPC calling component, and the cross-optical-gate universal RPC calling component further comprises: the proxy server is in communication connection with the client; the proxy client is in communication connection with the proxy server and the server; the proxy server receives request parameters initiated by the client and sends the request parameters to the server through the proxy client in a cross-optical gate communication mode; and the proxy client receives response parameters returned by the server and sends the response parameters to the client through the proxy server in a cross-optical gate communication mode. The cross-network RPC calling system adopting the scheme adopts a cross-optical-gate universal RPC calling component, realizes data transmission between different network segments, ensures that the communication efficiency is improved, and reduces the development cost.
Description
Technical Field
The invention belongs to the technical field of information transmission, and particularly relates to a cross-network RPC calling system and a method.
Background
An optical gate, FGAP for short, is a unidirectional isolation software and hardware system based on light, developed on the basis of a security isolation GAP (GAP), and used for connecting two physically isolated local area networks a and B, that is, two different local area networks cannot be directly connected, and the optical gate allows the local area network a to unidirectionally send a file to the local area network B or the local area network B to the local area network a.
At present, the cross-network call is often involved in a public security system or an enterprise system due to a security problem, that is, data interaction is performed between two different network segments. The traditional mode is adopted, namely, the two interactive ends interact through codes for developing a file transfer protocol, and the reusability and the isolation are not provided.
An example is illustrated below: suppose that the lan a sends a file to the lan B, the configuration is as follows:
network A certain host X directory: data/gz/send
B network certain host Y directory: data/gz/recv
If a file is added under the directory/data/gz/send of the host X, the file is transferred to the corresponding directory/data/gz/recv of the host Y through the optical gate, wherein the basic process mainly comprises the following steps: the host X processes the content to be requested into a file, the file is placed in an optical shutter directory, the optical shutter transmits the file to the host Y, the host Y obtains a request generation result after finding the request file, and then the request generation result is stored as the file in the optical shutter directory; then the optical gate transmits the file to the host X; and after finding the request file, the host X analyzes the response result and processes the response result.
In the calling process, the programs of the host X and the host Y need frequent file operation, complex coding design is carried out, the light gate directory needs to be configured when the project is deployed, and the development cost and the debugging cost are high.
Disclosure of Invention
In order to solve the technical problems, the invention provides a cross-network RPC calling system, which adopts a cross-optical gate universal RPC calling component to realize data transmission between different network segments, ensures that the communication efficiency is improved, and reduces the development cost.
In one aspect, the invention discloses a cross-network RPC calling system, which comprises:
the client is arranged at the side of a first local area network; and
the server is arranged on a second local area network side and is in communication connection with the client through a cross-optical-gate universal RPC calling component;
the cross-shutter generic RPC call component further comprises:
the proxy server is in communication connection with the client; and
the proxy client is in communication connection with the proxy server and the server;
the proxy server receives request parameters initiated by the client and sends the request parameters to the server through the proxy client in a cross-optical gate communication mode; and the proxy client receives response parameters returned by the server and sends the response parameters to the client through the proxy server, so as to provide a cross-network communication function between the client and the server.
Further, the cross-optical gate universal RPC calling component supports the FTP file transfer protocol.
Further, the cross-optical-gate universal RPC calling component communicates with the client and the server by adopting any one of communication protocols such as HTTP, GRPC and Thrift, and specifically, the client sends an REST request to the proxy server by adopting an HTTP embodiment.
Furthermore, the agent server and the agent client of the cross-optical-gate universal RPC calling component are packaged into jar packages which are respectively integrated on the client and the server in a component mode, so that the communication function of the client is greatly enriched, and the client has better applicability.
Further, data transmission in the system communication process is based on a JSON structure to carry out data exchange.
On the other hand, the invention also discloses a cross-network RPC calling method, which comprises the following steps:
s1: initiating a call request, wherein a client at the first local area network side initiates a request parameter and then sends the request parameter to a service end at the second local area network side through a cross-optical-gate universal RPC call component;
s2: and responding to the call request, wherein the server receives the request parameters, processes the request parameters and returns a response result to the client through the cross-optical-gate universal RPC call component.
Further, in the step S1, a proxy server of the cross-optical-gate general RPC call component receives a request parameter cross-optical-gate communication initiated by the client on the first local area network side, and sends the request parameter cross-optical-gate communication to the server through the proxy client;
further, in step S2, a proxy client of the cross-optical-gate generic RPC call component receives response parameters returned by the server and sends the response parameters to the client through the proxy server.
Further, the step S1 further includes:
s101: the client side of the first local area network initiates a service calling request and outputs a request parameter;
s102: a proxy server in the cross-optical-gate universal RPC calling component receives the request parameters, packages the request parameters into a request file, and writes a request unique identifier into the request file;
s103: the request file is sent to a proxy client of the cross-optical-gate universal RPC calling component through an optical gate;
s104: and the proxy client receives the request file, analyzes the file content into the request parameter and sends the request parameter to the server side of the second local area network.
Further, the step S2 further includes:
s201: the server side of the second local area network receives the request parameters, processes the request parameters and returns a response result;
s202: the proxy client of the cross-optical-gate universal RPC calling component receives the response result and packages the response result into a response file, and adds a unique request identifier to the response file;
s203: the response file is sent to a proxy server of the cross-optical-gate universal RPC calling component through another optical gate;
s204: and the proxy server receives the response file, analyzes the response file to obtain a response result, and compares the request unique identifier so as to return the response result to the client side of the first local area network according to the request unique identifier.
Further, the step S1 further includes an RPC call failure retry step, configured to send the request parameter to the proxy client again when the client does not receive the response result for a set time, and cancel sending the request parameter when the client does not receive the response result after a limited number of requests.
Further, the cross-optical gate universal RPC calling component supports the FTP file transfer protocol.
Further, the cross-optical-gate universal RPC calling component is communicated with the client and the server by adopting any one of communication protocols such as HTTP, GRPC and Thrift.
Further, the proxy server and the proxy client of the cross-optical-gate universal RPC calling component are packaged into jar packages which are respectively integrated on the client on the first local area network side and the server on the second local area network side in a component mode.
Further, data transmission in the cross-network RPC calling method communication process is based on a JSON structure to carry out data exchange.
Compared with the prior art, the invention has the advantages and positive effects that:
according to the invention, cross-network communication RPC calling can be carried out between a client side at a first local area network side and a server side at a second local area network side by arranging a cross-optical gate universal RPC calling component without carrying out complicated coding design and configuration of an optical gate directory, data transmission is equivalently carried out between the client side and the server side in the same local area network, the client side can carry out RPC calling in the same network segment and the cross-network segment at the same time, and the client side and the server side do not need to carry out complicated file operation, so that the optical gate component is shielded, the development cost and the debugging cost are reduced;
the unique identifier of the request is added in the RPC calling process, and a response result is returned to the corresponding client according to the unique identifier of the request, so that when a plurality of services are used, only one set of optical gate components is required to be constructed, and the better expansibility is achieved;
the invention also integrates the agent server and the agent client of the cross-optical-gate universal RPC calling component into the client and the server in a jar package component form, thereby greatly enriching the communication function of the client and leading the client to have better applicability.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a schematic structural diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 2 is another schematic structural diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 4 is another schematic diagram of a cross-network RPC call system according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a cross-network RPC calling method according to an embodiment of the present invention.
Wherein: 1. a client; 2. a server side; 3. an optical gate-crossing universal RPC calling component; 31. a proxy server; 32. a proxy client; 33. and (4) a shutter.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only some embodiments, not all embodiments, of the present invention.
It should be noted that all the directional indicators (such as upper, lower, left, right, front, and rear … …) in the embodiment of the present invention are only used to explain the relative position relationship between the components, the motion situation, and the like in a specific posture (as shown in the drawing), and if the specific posture is changed, the directional indicator is changed accordingly.
In addition, the descriptions related to "first", "second", etc. in the present invention are for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature.
FIG. 1 is a schematic structural diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 2 is another schematic structural diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 4 is another schematic diagram of a cross-network RPC call system according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a cross-network RPC calling method according to an embodiment of the present invention
The first embodiment is as follows:
fig. 1 is a schematic structural diagram of a cross-network RPC call system according to an embodiment of the present invention, and referring to fig. 1, an embodiment of the present invention discloses a cross-network RPC call system, including:
the client 1 is arranged on a local area network A side; and;
the server 2 is arranged on a local area network B side, and the server 2 is in communication connection with the client through a cross-optical-gate universal RPC calling component 3;
the cross-shutter universal RPC call component 3 further comprises:
the proxy server 31 is in communication connection with the client 1; and
the proxy client 32 is in communication connection with the proxy server 31 and the server 2;
the agent server 31 receives a request parameter initiated by the client 1, and sends the request parameter to the server 2 through the agent client 32 in the optical gate crossing communication; the agent client 32 receives response parameters returned by the server 2 and sends the response parameters to the client 1 through the agent server 31, so as to realize a cross-network communication function between the client and the server, the cross-optical-gate universal RPC calling component 3 communicates with the client 1 and the server 2 by adopting any one of communication protocols such as HTTP, GRPC and Thrift, the cross-optical-gate universal RPC calling component 3 supports an FTP file transmission protocol, in the embodiment, the client 1 sends a universal REST request to the agent server 31, and the client does not need to perform complex file operation, so that any client library does not need to be integrated.
It should be noted that, in the communication process of the above system, data transmission is performed based on JSON structure for data exchange, which is illustrated below, for example:
req content of request file uuid as follows:
for another example, the content of response file uuid.
Fig. 5 is a schematic flow diagram of a cross-network RPC calling method according to an embodiment of the present invention, and referring to fig. 5, the present invention further discloses a cross-network RPC calling method, including:
s1: initiating a call request, wherein a client 1 at the side of a local area network A initiates a request parameter and then sends the request parameter to a server 2 at the side of a local area network B through a cross-optical-gate universal RPC call component 3;
s2: responding the call request, wherein the server 2 receives the request parameters, processes the request parameters according to the request parameters, returns a response result to the corresponding client 1 through the cross-optical-gate universal RPC call component 3,
specifically, the proxy server 31 of the cross-optical-gate general RPC calling component 3 receives request parameters initiated by the client 1 of the local area network a, and sends the request parameters to the server 2 of the local area network B through the proxy client 32; the proxy client 32 of the cross-optical-gate universal RPC calling component 3 receives the response parameter returned by the server 2, and sends the response parameter to the client 1 through the proxy server 1 in cross-optical-gate communication.
Wherein, step S1 further comprises:
s101: a local area network A client 1 initiates a service calling request and outputs a request parameter;
s102: the agent server 31 in the cross-optical-gate universal RPC calling component 3 receives the request parameters, packages the request parameters into a request file, and writes a request unique identifier into the request file;
s103: the request file is sent to the agent client 32 through the optical gate a;
s104: the proxy client 32 receives the request file, and parses the file content into request parameters and sends the request parameters to the server 2 on the side of the local area network B.
The step S2 further includes:
s201: the server 2 at the side of the local area network B receives the request parameters, processes the request parameters and returns a response result;
s202: the proxy client 32 receives the response result and packages the response result into a response file, and adds a unique request identifier to the response file;
s203: the response file is sent to the agent server 31 through the optical gate B;
s204: the proxy server 31 receives the response file, analyzes the response file to obtain a response result, compares the request unique identifier, and returns the response result to the client 1 of the local area network a according to the request unique identifier.
It should be noted that if the local area network a client 1 does not receive the response result within 1 second, the request parameter is sent again, and further, if the request parameter is sent 3 times and the response result is not received yet, the request parameter is cancelled and the request fails.
By adopting the RPC calling system and method of the embodiment, cross-network communication data transmission can be carried out between the client 1 at the side of the local area network A and the server 2 at the side of the local area network B by arranging the cross-optical gate universal RPC calling component 3 without carrying out complicated coding design and optical gate directory configuration, RPC calling can be carried out in the same local area network between the client 1 and the server 2, the client 1 can carry out RPC calling in the same network segment and cross-network segment at the same time, and the client 1 and the server 2 do not need to carry out complicated file operation, so that the optical gate component is shielded, the development cost and the debugging cost are reduced; in the RPC calling process, the unique request identifier is added, and a response result is returned to the corresponding client 1 according to the unique request identifier, so that when a plurality of services are used, only one set of optical gate components is required to be constructed, and the RPC calling method has better expansibility.
The second concrete embodiment:
only the differences between the present embodiment and the first embodiment are described below, and the same parts are not repeated, but the differences between the present embodiment and the first embodiment are:
fig. 2 and 4 are a schematic structural diagram and a schematic diagram of the cross-network RPC call system of the present embodiment, and refer to fig. 2 and 4, an agent server 31 and an agent client 32 of the cross-optical gate universal RPC call component 3 of the present embodiment are respectively packaged into jar packages and then integrated into a client 1 on the side of a local area network a and a server 2 on the side of a local area network B in a component form, and are not separately deployed any more, so that the client has functions of internal network and external network RPC calls, and client communication functions are greatly enriched, so that the client has better applicability.
The above description is only a preferred embodiment of the present invention, and not intended to limit the present invention in other forms, and any person skilled in the art may apply the above modifications or changes to the equivalent embodiments with equivalent changes, without departing from the technical spirit of the present invention, and any simple modification, equivalent change and change made to the above embodiments according to the technical spirit of the present invention still belong to the protection scope of the technical spirit of the present invention.
Claims (6)
1. A cross-network RPC calling system, comprising:
the client is arranged at the side of a first local area network; and
a server side, set up in a second LAN side, the server side is through a cross optical gate general RPC calling component communication connection the client side, cross optical gate general RPC calling component further includes:
the proxy server is arranged on the first local area network side and is in communication connection with the client; and
the agent client is arranged on the second local area network side and is in communication connection with the agent server and the server;
the method comprises the steps that an agent server and an agent client of the cross-optical-gate universal RPC calling component are packaged into jar packages and integrated into the client and the server in a component mode, wherein the agent server receives request parameters initiated by the client and sends the request parameters to the server through the agent client, specifically, the agent server is used for receiving the request parameters and packaging the request parameters into a request file, a request unique identifier is written into the request file, and the request file is sent to the agent client through an optical gate; the proxy client receives the request file, analyzes the file content into request parameters and sends the request parameters to the server;
the proxy client receives response parameters returned by the server and sends the response parameters to the client through the proxy server in a cross-optical gate communication mode, specifically, the response parameters are response results processed and returned by the server according to the request parameters, the proxy client receives the response results and packages the response results into a response file, meanwhile, a unique request identifier is added to the response file, and the response file is sent to the proxy server through another optical gate; and the proxy server receives the response file, analyzes the response file to obtain a response result, compares the request unique identifier, and returns the response result to the client according to the request unique identifier.
2. The cross-network RPC call system of claim 1, wherein the cross-shutter generic RPC call component supports the FTP file transfer protocol.
3. The cross-network RPC calling system of claim 2, wherein the cross-optical gate general RPC calling component communicates with the client and the server by using any one of HTTP, GRPC and Thrift.
4. The cross-network RPC calling system of claim 1, wherein data transfer during the system communication process is based on JSON structure for data exchange.
5. A cross-network RPC calling method is characterized by comprising the following steps:
s1: initiating a call request, wherein a client at the first local area network side initiates a request parameter and then sends the request parameter to a service end at the second local area network side through a cross-optical-gate universal RPC call component;
s2: responding to a calling request, wherein the server receives request parameters, processes the request parameters and returns a response result to the client through the cross-optical-gate universal RPC calling component;
the step S1 further includes:
s101: the client side of the first local area network initiates a service calling request and outputs a request parameter;
s102: the proxy server of the cross-optical-gate universal RPC calling component receives the request parameters, packages the request parameters into a request file, and writes a request unique identifier into the request file;
s103: the request file is sent to a proxy client of the cross-optical-gate universal RPC calling component through an optical gate;
s104: the proxy client receives a request file, analyzes the file content into the request parameter and sends the request parameter to the server side of the second local area network;
the step S2 further includes:
s201: the server side of the second local area network receives the request parameters, processes the request parameters and returns a response result;
s202: the proxy client of the cross-optical-gate universal RPC calling component receives the response result and packages the response result into a response file, and adds a unique request identifier to the response file;
s203: the response file is sent to a proxy server of the cross-optical-gate universal RPC calling component through another optical gate;
s204: the proxy server receives the response file and analyzes the response file to obtain a response result, and compares the request unique identifier to return the response result to the client side of the first local area network according to the request unique identifier;
and packaging the proxy server and the proxy client of the cross-optical-gate universal RPC calling component into jar packages, and integrating the jar packages into the client at the first local area network side and the server at the second local area network side in a component mode respectively.
6. The cross-network RPC calling method of claim 5, wherein the step S1 further comprises an RPC call failure retry step.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010675477.5A CN111917737B (en) | 2020-07-14 | 2020-07-14 | Cross-network RPC calling system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010675477.5A CN111917737B (en) | 2020-07-14 | 2020-07-14 | Cross-network RPC calling system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111917737A CN111917737A (en) | 2020-11-10 |
| CN111917737B true CN111917737B (en) | 2023-01-31 |
Family
ID=73281570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010675477.5A Active CN111917737B (en) | 2020-07-14 | 2020-07-14 | Cross-network RPC calling system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111917737B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112929454B (en) * | 2021-04-27 | 2021-07-16 | 中国电子科技集团公司第二十八研究所 | Heterogeneous service interoperation method and device |
| CN113381908B (en) * | 2021-06-07 | 2022-07-08 | 展讯半导体(成都)有限公司 | Intranet information cross-network circulation method and device and electronic equipment |
| CN114679483B (en) * | 2022-03-01 | 2023-07-25 | 南京巨鲨显示科技有限公司 | Communication method, system and storage medium for distributed service communication system |
| CN115022325B (en) * | 2022-06-07 | 2024-09-06 | 深圳市和讯华谷信息技术有限公司 | Data transmission method between Kafka clusters and related equipment |
| CN114978743B (en) * | 2022-06-08 | 2023-07-18 | 杭州指令集智能科技有限公司 | Service communication system crossing network segment |
| CN115118757A (en) * | 2022-06-24 | 2022-09-27 | 浙江海规技术有限公司 | Network remote calling method and device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102098296A (en) * | 2010-12-29 | 2011-06-15 | 北京新媒传信科技有限公司 | Method and system for realizing remote call |
| CN104142856A (en) * | 2013-05-07 | 2014-11-12 | 华为技术有限公司 | Service program call method, service program call system and intelligent equipment thereof |
| CN106034138A (en) * | 2015-03-09 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Remote service calling method and remote service calling device |
| CN106933678A (en) * | 2015-12-30 | 2017-07-07 | 中国科学院上海高等研究院 | A kind of many equipment application supporting frames and its implementation |
| US10069928B1 (en) * | 2015-01-21 | 2018-09-04 | Amazon Technologies, Inc. | Translating requests/responses between communication channels having different protocols |
| CN110727524A (en) * | 2019-10-17 | 2020-01-24 | 广州欢聊网络科技有限公司 | Method and device for realizing remote procedure call |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8090797B2 (en) * | 2009-05-02 | 2012-01-03 | Citrix Systems, Inc. | Methods and systems for launching applications into existing isolation environments |
| CN103095749A (en) * | 2011-10-28 | 2013-05-08 | 浙江大华技术股份有限公司 | Method and system used for achieving discovery of cross-network-segment equipment |
| CN108512821B (en) * | 2017-02-28 | 2021-05-28 | 阿里巴巴集团控股有限公司 | Data transmission method, device and system, network gate and transaction data storage method |
| US10389685B2 (en) * | 2017-08-17 | 2019-08-20 | Saudi Arabian Oil Company | Systems and methods for securely transferring selective datasets between terminals |
| CN108874567B (en) * | 2018-07-19 | 2021-08-17 | 广州市创乐信息技术有限公司 | Service processing method and system |
| CN110399233A (en) * | 2019-06-28 | 2019-11-01 | 口碑(上海)信息技术有限公司 | The processing method and processing device of remote procedure call |
| CN110958218B (en) * | 2019-10-16 | 2022-01-28 | 平安国际智慧城市科技股份有限公司 | Data transmission method based on multi-network communication and related equipment |
| CN110855634A (en) * | 2019-10-24 | 2020-02-28 | 北京电信易通信息技术股份有限公司 | Cross-network switching service system and method based on secure network |
-
2020
- 2020-07-14 CN CN202010675477.5A patent/CN111917737B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102098296A (en) * | 2010-12-29 | 2011-06-15 | 北京新媒传信科技有限公司 | Method and system for realizing remote call |
| CN104142856A (en) * | 2013-05-07 | 2014-11-12 | 华为技术有限公司 | Service program call method, service program call system and intelligent equipment thereof |
| US10069928B1 (en) * | 2015-01-21 | 2018-09-04 | Amazon Technologies, Inc. | Translating requests/responses between communication channels having different protocols |
| CN106034138A (en) * | 2015-03-09 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Remote service calling method and remote service calling device |
| CN106933678A (en) * | 2015-12-30 | 2017-07-07 | 中国科学院上海高等研究院 | A kind of many equipment application supporting frames and its implementation |
| CN110727524A (en) * | 2019-10-17 | 2020-01-24 | 广州欢聊网络科技有限公司 | Method and device for realizing remote procedure call |
Non-Patent Citations (2)
| Title |
|---|
| "An efficient device to device RPC framework using DBUS and KDBus";J. K. Singh et al.;《 2016 International Conference on Electronics, Information, and Communications (ICEIC)》;20160908;全文 * |
| "如何利用远程虚拟技术及网闸实现物理隔离内外网的安全互访";温诚;《网络安全技术与应用》;20140715;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111917737A (en) | 2020-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111917737B (en) | Cross-network RPC calling system and method | |
| CN109889551B (en) | Method for accessing intelligent hardware to Internet of things cloud platform | |
| US20040249926A1 (en) | System and methd for common information model object manager proxy interface and management | |
| US20200052982A1 (en) | In situ triggered function as a service within a service mesh | |
| US9037695B2 (en) | Management of networked resources on different platforms with a common interface | |
| CN113746928B (en) | Cross-cloud service calling method, device and system | |
| CN111258723B (en) | Transaction processing method, device, system, medium and equipment of distributed system | |
| CN111818158B (en) | Gateway control method, device, electronic equipment and storage medium | |
| CN113794652B (en) | Data processing method, device, electronic equipment and storage medium | |
| JP2004519168A (en) | Integrated communication server and method | |
| JP2003520533A (en) | Communication network | |
| CN107798098A (en) | A kind of method and device for realizing dynamic socket field | |
| WO2011020412A1 (en) | Method, client, server and system for accessing directory of server | |
| CN108418901A (en) | High performance remote procedure calling (PRC) method based on PHP | |
| CN111371823B (en) | Method for client to access micro-service in non-WEB scene | |
| US9756129B2 (en) | WSDL/WADL reference definition integration | |
| CN107395766A (en) | Decentralization communication system and implementation method based on HazelCast | |
| CN113722126A (en) | Request processing method and device | |
| US8046419B2 (en) | Method of processing open asynchronous application service event and open web service gateway implementing the same | |
| CN112367383A (en) | Service calling method and related equipment | |
| CN116560756B (en) | Service orchestration method, electronic device, computer-readable storage medium | |
| US20090300212A1 (en) | Heuristics processing | |
| CN118041704B (en) | Kubernetes container access method, device, computing equipment and storage medium | |
| EP1715646B1 (en) | System and method for connecting applications to heterogeneous backend servers via a gateway server | |
| CN117793117A (en) | Access control equipment adaptation method, system, equipment and medium |
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 |