CN111444029A - Cross-domain micro-service calling method and system based on file exchange - Google Patents
Cross-domain micro-service calling method and system based on file exchange Download PDFInfo
- Publication number
- CN111444029A CN111444029A CN202010147008.6A CN202010147008A CN111444029A CN 111444029 A CN111444029 A CN 111444029A CN 202010147008 A CN202010147008 A CN 202010147008A CN 111444029 A CN111444029 A CN 111444029A
- Authority
- CN
- China
- Prior art keywords
- network
- request
- file
- response
- cross
- 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
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/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention relates to a cross-domain micro-service calling method and a system based on file exchange. In the method, the first network is a called end network, the second network is a calling end network, and the method comprises the following steps: the second network receives a cross-domain micro-service calling request of a user, generates a request file according to the calling request and puts the request file into a request directory of the second network; the network gate/optical gate synchronizes the request files in the request directory of the second network to the request directory of the first network; the first network generates a response file according to the request file in the request directory of the first network, and the response file is placed in the response directory of the first network; the network gate/optical gate synchronizes the response files in the response directory of the first network to the response directory of the second network; the second network returns the response file in the response directory of the second network to the user. The invention can realize service calling among all departments under the premise of ensuring mutual independence of networks among all departments of the official examination department.
Description
Technical Field
The invention belongs to the field of system integration, and particularly relates to a cross-domain micro-service calling method and a system based on file exchange.
Background
Some confidential units have the mutual cooperation and need to maintain independent business requirements, particularly in the field of politics and law. In recent years, the country has made higher requirements on the cooperation of intelligent judicial services of official survey departments and the like, but if the safety, reliability, accuracy and timeliness of obligation data in sharing and exchange cannot be guaranteed, the application and construction of the judicial cooperation services are anhydrous sources and wood-free. At present, service systems of a public security bureau, a court, a detection institute and a judicial institution are arranged in respective confidential intranets, and data intercommunication with other political institutions is realized on the premise of ensuring relative independence of networks of all departments of a public inspection department by adopting a network gate/optical gate technology.
After the relative independence of each door network is realized through the modes of a network gate, an optical gate and the like, the legal department team also faces some new problems. The physical isolation of the network brings inconvenience to the data exchange of the judicial business system, especially when service invocation is involved.
At present, service invocation is mainly that when a user completes service registration and requests a file from a server, the server processes the request and directly transmits the service file to the user. For the case that the user and the server are in different networks, cross-domain service invocation needs to be performed. In the prior art, no scheme for realizing cross-domain micro-service calling based on secure file exchange exists in the environment of a gatekeeper/an optical gate.
Disclosure of Invention
The invention provides a cross-domain micro-service calling scheme based on file exchange to realize service calling between two secret-involved internal networks under the condition that a network gate/optical gate exists, and realize service calling between all the departments under the premise of ensuring that networks between all the departments of a public inspection department are mutually independent.
The technical scheme adopted by the invention is as follows:
in a first aspect, the present invention provides a file exchange-based cross-domain microservice calling method, which is applicable to a first network and a second network isolated by using a gatekeeper/optical gate, wherein the first network is a called end network, and the second network is a calling end network, and the method includes the following steps:
the second network receives a cross-domain micro-service calling request of a user, generates a request file according to the cross-domain micro-service calling request, and places the request file into a request directory of the second network;
the network gate/optical gate synchronizes the request files in the request directory of the second network to the request directory of the first network;
the first network generates a response file according to the request file in the request directory of the first network, and the response file is placed in the response directory of the first network;
the network gate/optical gate synchronizes the response files in the response directory of the first network to the response directory of the second network;
the second network returns the response file in the response directory of the second network to the user.
Further, the first network comprises a first front-end processor and a first cross-domain proxy sub-platform; the second network comprises a second front-end processor and a second cross-domain proxy sub-platform; wherein:
the first front-end processor is connected with the first cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the first cross-domain agent sub-platform is connected with the service node and the first front-end processor and used for subscribing service messages and generating response files according to the request files;
the second front-end processor is connected with the second cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the second cross-domain agent sub-platform is connected with the user and the second front-end processor and used for receiving a cross-domain micro-service calling request of the user and returning a response file to the user.
Further, the second cross-domain agent sub-platform generates a globally unique identifier UUID of the call according to a cross-domain micro-service call request of a user, records a corresponding user callback interface, further generates a request file UUID.json, and sends the request file UUID.json to the second front-end processor; the gatekeeper/photogate synchronizes the request file of the second front-end processor to the first front-end processor.
Further, the first cross-domain agent sub-platform analyzes the request file, acquires a service response by calling the service, generates a response file R-UUID.json according to the service response, and sends the response file R-UUID.json to the first front-end processor; the gatekeeper/photogate synchronizes the response file of the first front-end processor to the second front-end processor.
Further, the second cross-domain agent sub-platform reads the response file from the second front-end processor, then analyzes the response file and queries the user callback interface corresponding to the UUID, and returns the response file to the user by calling the user callback interface.
Further, the gatekeeper/optical gate detects newly added request files or corresponding files in the first network and the second network at intervals, and synchronizes the newly added request files or corresponding files to the network on the other side.
The invention also provides a cross-domain micro-service calling system based on file exchange, which comprises a first network and a second network which are isolated by adopting a gatekeeper/an optical gate, wherein the first network is a called end network, and the second network is a calling end network;
the second network receives a cross-domain micro-service calling request of a user, generates a request file according to the cross-domain micro-service calling request, and places the request file into a request directory of the second network;
the network gate/optical gate synchronizes the request files in the request directory of the second network to the request directory of the first network;
the first network generates a response file according to the request file in the request directory of the first network, and the response file is placed in the response directory of the first network;
the network gate/optical gate synchronizes the response files in the response directory of the first network to the response directory of the second network;
the second network returns the response file in the response directory of the second network to the user.
The invention has the following beneficial effects and contributions: aiming at the circumstance that a gatekeeper/an optical gate exists, the invention creatively provides a method and a system for cross-domain service calling based on secure file exchange, which not only ensures the relative independence of each department network of different government and law departments, but also can realize the service calling capability of the gatekeeper/the optical gate.
Drawings
FIG. 1 is a flowchart and a system structure diagram of the steps of the cross-domain microservice calling method based on secure file exchange according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions and specific implementations of the present invention will be described in further detail with reference to the accompanying drawings.
In the file exchange-based cross-gateway/optical gate data exchange technology, an A network and a B network (which can be regarded as different secret-involved internal networks or internal and external networks) realize data intercommunication through a gateway/optical gate. The A network is a called end network, the B network is a calling end network, a service program deployed by the A network server is accessed/called by a user in the B network, and once the calling request is received, the calling request is generated into an xml or other format file which is put into a sharing request directory of the B network server. The shared request directory and the shared response directory between the network A and the network B are configured in the network gate/optical gate, the network gate/optical gate can scan a plurality of specified directories of the network A and the network B at regular time, and if the network gate/optical gate has the new file, the network gate/optical gate synchronizes in the network A and the network B. And B, scanning the appointed request directory in the program of the network server B at regular time, synchronizing the request file of the network server B to the request directory of the network server A by using a network gate/optical gate, immediately triggering and calling the services of other machines in the network A when the network program A detects the request file, and generating a response file according to the result and putting the response file into the response directory. The network gate/optical gate detects the newly added files of the response directory in the network A, synchronizes the files to the response directory of the network server B, and after the program thread of the network server B receives the call request, the program thread of the network server B waits for the specified time all the time, scans whether the response files are generated under the response directory (the request files and the response files adopt different name modes for distinguishing), reads the response files and returns the response files to the user caller of the network B.
Fig. 1 is a flowchart and a system structure diagram of the service invocation method of the present embodiment, including a front-end processor, a shutter/gatekeeper, and an agent sub-platform. Wherein different front-end computers A and B and different cross-domain agent sub-platforms A and B are positioned at two sides of the net gate/optical gate. The cross-domain agent sub-platforms a and B are respectively referred to as the sub-platform a and the sub-platform B in fig. 1.
Cross-domain agent sub-platform a: a service node (service provider) and a front-end processor a are connected for subscribing to service messages.
A front-end processor A: and the cross-domain agent sub-platform A and the gatekeeper/optical gate are connected and used for storing files (request files or response files) for the gatekeeper/optical gate to synchronize the files.
Optical/mesh gate: the isolation of the two-end networks (network A and network B) is realized, namely, the two-end network programs cannot directly access each other.
A front-end processor B: and the cross-domain agent sub-platform B and the gatekeeper/optical gate are connected and used for storing files (request files or response files) for the gatekeeper/optical gate to synchronize the files.
Cross-domain proxy sub-platform B: and the front-end processor B is connected with the user and used for receiving the subscription message, the file and the analysis message file.
As shown in fig. 1, in the service invocation method based on file exchange provided in this embodiment, a service node and a user are in a gatekeeper/optical gate isolated network, and the service node issues a service to the user in a file manner through a gatekeeper, which is specifically implemented as follows:
1) and the user after registering the information subscribes the message: calling a proxy interface based on the micro-service method; the micro-service method can adopt the prior art, the micro-service method can be adjusted to be small and flexible, and any relatively independent functional service is not a module but an independent service;
2) generating a UUID (globally unique identifier) called at this time by the cross-domain agent sub-platform B, recording a corresponding user callback interface, packaging a user calling message into a request file UUID.json, and sending the request file to a synchronous folder of a gatekeeper/an optical gate, namely to the front-end processor B;
3) the gateway/optical gate synchronizes the request file to the domain where the service is located, i.e. to the front-end processor A;
4) a cross-domain agent sub-platform A reads a request file in a synchronous folder from a front-end processor A;
5) the cross-domain agent sub-platform A analyzes the request file, generates a request message, calls a service and obtains a service result;
6) the cross-domain agent sub-platform A packages the service response into a response file R-UUID.json, and sends the response file to a synchronous folder of a gatekeeper/an optical gate, namely to the front-end processor A;
7) the gatekeeper/optical gate synchronizes the response file R-UUID.json to the domain where the service calling user is located, namely to the front-end processor B;
8) the cross-domain agent sub-platform B reads the response file from the front-end processor B, analyzes the response file and queries a user callback interface corresponding to the UUID;
9) and the cross-domain agent sub-platform B calls a user callback interface and returns a service response.
Wherein, step 3) specifically includes:
the front-end processor B (folder) synchronizes the request file, i.e. the Service subscription file (including Web Service, DB, HTTP or FTP, and other requests), to the front-end processor A on the other side of the gatekeeper through the gatekeeper/optical gate Service information (the gatekeeper/optical gate detects new files at regular intervals, and synchronizes the new files to the front-end processor on the other side of the gatekeeper, i.e. the front-end processor A).
The above embodiments are only intended to illustrate the technical solution of the present invention and not to limit the same, and a person skilled in the art can modify the technical solution of the present invention or substitute the same without departing from the principle and scope of the present invention, and the scope of the present invention should be determined by the claims.
Claims (10)
1. A cross-domain micro-service calling method based on file exchange is suitable for a first network and a second network which are isolated by adopting a gatekeeper/an optical gate, wherein the first network is a called end network, and the second network is a calling end network, and is characterized by comprising the following steps:
the second network receives a cross-domain micro-service calling request of a user, generates a request file according to the cross-domain micro-service calling request, and places the request file into a request directory of the second network;
the network gate/optical gate synchronizes the request files in the request directory of the second network to the request directory of the first network;
the first network generates a response file according to the request file in the request directory of the first network, and the response file is placed in the response directory of the first network;
the network gate/optical gate synchronizes the response files in the response directory of the first network to the response directory of the second network;
the second network returns the response file in the response directory of the second network to the user.
2. The method of claim 1, wherein the first network comprises a first front-end processor and a first cross-domain proxy sub-platform; the second network comprises a second front-end processor and a second cross-domain proxy sub-platform; wherein:
the first front-end processor is connected with the first cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the first cross-domain agent sub-platform is connected with the service node and the first front-end processor and used for subscribing service messages and generating response files according to the request files;
the second front-end processor is connected with the second cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the second cross-domain agent sub-platform is connected with the user and the second front-end processor and used for receiving a cross-domain micro-service calling request of the user and returning a response file to the user.
3. The method according to claim 2, wherein the second cross-domain agent sub-platform generates a globally unique identifier UUID of the call according to the cross-domain micro-service call request of the user, records a corresponding user callback interface, further generates a request file uuid.json, and sends the request file uuid.json to the second front-end processor; the gatekeeper/photogate synchronizes the request file of the second front-end processor to the first front-end processor.
4. The method of claim 3, wherein the first cross-domain agent sub-platform parses the request file, obtains a service response by calling a service, generates a response file R-UUID.json according to the service response, and sends the response file R-UUID.json to the first front-end processor; the gatekeeper/photogate synchronizes the response file of the first front-end processor to the second front-end processor.
5. The method of claim 4, wherein the second cross-domain proxy sub-platform reads the response file from the second front-end processor, then parses the response file and queries the user callback interface corresponding to the UUID, and returns the response file to the user by calling the user callback interface.
6. The method of claim 1, wherein the gatekeeper/photogate detects new request files or corresponding files in the first network, the second network at intervals, and synchronizes the new request files or corresponding files to the network on the other side.
7. A cross-domain micro-service calling system based on file exchange is characterized by comprising a first network and a second network which are isolated by adopting a gatekeeper/an optical gate, wherein the first network is a called end network, and the second network is a calling end network;
the second network receives a cross-domain micro-service calling request of a user, generates a request file according to the cross-domain micro-service calling request, and places the request file into a request directory of the second network;
the network gate/optical gate synchronizes the request files in the request directory of the second network to the request directory of the first network;
the first network generates a response file according to the request file in the request directory of the first network, and the response file is placed in the response directory of the first network;
the network gate/optical gate synchronizes the response files in the response directory of the first network to the response directory of the second network;
the second network returns the response file in the response directory of the second network to the user.
8. The system of claim 7, wherein the first network comprises a first front-end processor and a first cross-domain proxy sub-platform; the second network comprises a second front-end processor and a second cross-domain proxy sub-platform; wherein:
the first front-end processor is connected with the first cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the first cross-domain agent sub-platform is connected with the service node and the first front-end processor and used for subscribing service messages and generating response files according to the request files;
the second front-end processor is connected with the second cross-domain agent sub-platform and the gatekeeper/optical gate and is used for storing the request file or the response file and enabling the gatekeeper/optical gate to synchronize the files; the second cross-domain agent sub-platform is connected with the user and the second front-end processor and used for receiving a cross-domain micro-service calling request of the user and returning a response file to the user.
9. The system according to claim 8, wherein the second cross-domain agent sub-platform generates a globally unique identifier UUID of the call according to the cross-domain micro-service call request of the user, records a corresponding user callback interface, further generates a request file uuid.json, and sends the request file uuid.json to the second front-end processor; the gatekeeper/photogate synchronizes the request file of the second front-end processor to the first front-end processor.
10. The system of claim 9, wherein the first cross-domain agent sub-platform parses the request file, obtains a service response by calling a service, generates a response file R-uuid.json according to the service response, and sends the response file R-uuid.json to the first front-end processor; the network gate/optical gate synchronizes the response file of the first front-end processor to the second front-end processor; and the second cross-domain agent sub-platform reads the response file from the second front-end processor, analyzes the response file, queries a user callback interface corresponding to the UUID, and returns the response file to the user by calling the user callback interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010147008.6A CN111444029A (en) | 2020-03-05 | 2020-03-05 | Cross-domain micro-service calling method and system based on file exchange |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010147008.6A CN111444029A (en) | 2020-03-05 | 2020-03-05 | Cross-domain micro-service calling method and system based on file exchange |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111444029A true CN111444029A (en) | 2020-07-24 |
Family
ID=71654023
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010147008.6A Pending CN111444029A (en) | 2020-03-05 | 2020-03-05 | Cross-domain micro-service calling method and system based on file exchange |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111444029A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113162995A (en) * | 2021-04-02 | 2021-07-23 | 青岛以萨数据技术有限公司 | Method and system for picture cross-network transmission |
| CN113709250A (en) * | 2021-08-31 | 2021-11-26 | 中国电子科技集团公司第二十八研究所 | Cross-domain user data synchronization method based on subscription sending mode |
| CN114124929A (en) * | 2021-09-29 | 2022-03-01 | 奇安信科技集团股份有限公司 | Cross-network data processing method and device |
| CN114448686A (en) * | 2022-01-14 | 2022-05-06 | 武汉三江中电科技有限责任公司 | Cross-network communication device and method based on micro-service |
| WO2023015412A1 (en) * | 2021-08-09 | 2023-02-16 | 中国科学院深圳先进技术研究院 | Cross-domain access control method and system, storage medium, and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106657010A (en) * | 2016-11-16 | 2017-05-10 | 东软集团股份有限公司 | Data access method, device and system |
| KR20180030006A (en) * | 2009-08-25 | 2018-03-21 | 한국전자통신연구원 | Syncronization control method for data transmission/receipt and station for data transmission/receipt syncronization |
| CN108040060A (en) * | 2017-12-18 | 2018-05-15 | 杭州优云软件有限公司 | The method and device of inter-network lock communication |
| CN108243143A (en) * | 2016-12-23 | 2018-07-03 | 北京明朝万达科技股份有限公司 | A kind of gateway penetrating method and system based on different web agent |
| CN109729053A (en) * | 2017-10-31 | 2019-05-07 | 北京国双科技有限公司 | The exchange method and device of data between intranet and extranet |
-
2020
- 2020-03-05 CN CN202010147008.6A patent/CN111444029A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20180030006A (en) * | 2009-08-25 | 2018-03-21 | 한국전자통신연구원 | Syncronization control method for data transmission/receipt and station for data transmission/receipt syncronization |
| CN106657010A (en) * | 2016-11-16 | 2017-05-10 | 东软集团股份有限公司 | Data access method, device and system |
| CN108243143A (en) * | 2016-12-23 | 2018-07-03 | 北京明朝万达科技股份有限公司 | A kind of gateway penetrating method and system based on different web agent |
| CN109729053A (en) * | 2017-10-31 | 2019-05-07 | 北京国双科技有限公司 | The exchange method and device of data between intranet and extranet |
| CN108040060A (en) * | 2017-12-18 | 2018-05-15 | 杭州优云软件有限公司 | The method and device of inter-network lock communication |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113162995A (en) * | 2021-04-02 | 2021-07-23 | 青岛以萨数据技术有限公司 | Method and system for picture cross-network transmission |
| WO2023015412A1 (en) * | 2021-08-09 | 2023-02-16 | 中国科学院深圳先进技术研究院 | Cross-domain access control method and system, storage medium, and device |
| CN113709250A (en) * | 2021-08-31 | 2021-11-26 | 中国电子科技集团公司第二十八研究所 | Cross-domain user data synchronization method based on subscription sending mode |
| CN113709250B (en) * | 2021-08-31 | 2023-09-15 | 中国电子科技集团公司第二十八研究所 | Cross-domain user data synchronization method based on subscription transmission mode |
| CN114124929A (en) * | 2021-09-29 | 2022-03-01 | 奇安信科技集团股份有限公司 | Cross-network data processing method and device |
| CN114124929B (en) * | 2021-09-29 | 2024-03-29 | 奇安信科技集团股份有限公司 | Cross-network data processing method and device |
| CN114448686A (en) * | 2022-01-14 | 2022-05-06 | 武汉三江中电科技有限责任公司 | Cross-network communication device and method based on micro-service |
| CN114448686B (en) * | 2022-01-14 | 2024-01-05 | 武汉三江中电科技有限责任公司 | Cross-network communication device and method based on micro-service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111444029A (en) | Cross-domain micro-service calling method and system based on file exchange | |
| US9071656B2 (en) | Router and method for routing service | |
| US7953102B2 (en) | System and method for generic data mapping between wireless component applications and application data sources | |
| CN106375458B (en) | Service calling system, method and device | |
| RU2366099C2 (en) | Updating presence information | |
| US20110078231A1 (en) | Method and apparatus for providing device compatibility information | |
| US20100198854A1 (en) | System and method for searching multiple contact information sources in a network-based address book system | |
| CN102377617A (en) | Systems, methods, and apparatus to monitor and authenticate mobile internet activity | |
| CN102694830B (en) | A kind of mthods, systems and devices realizing Web content and share | |
| CN111447256B (en) | Cross-domain micro-service registration and release method and system based on file exchange | |
| US7783718B2 (en) | Locating services using compiled scopes | |
| US20060259523A1 (en) | System and method of synchronization of internal data cache with wireless device application data repositories | |
| Nordström et al. | A search-based network architecture for mobile devices | |
| US8340652B2 (en) | System and method of waste management | |
| WO2014176991A1 (en) | Multimedia service processing apparatus, method and system | |
| CN114448686B (en) | Cross-network communication device and method based on micro-service | |
| JP2004535743A (en) | Domain naming system (DNS) for accessing databases | |
| CN101567879A (en) | Method, server, equipment and system for treating terminal request | |
| US12004059B2 (en) | Enhanced identification in communication networks | |
| CN116647552A (en) | Service processing method and system in heterogeneous micro-service cluster, terminal and storage medium | |
| US20090067600A1 (en) | Method And Arrangement For Services Running On Service Execution Platform | |
| Naik et al. | Security attacks on information centric networking for healthcare system | |
| EP1715647B1 (en) | System and Method for Generic Data Mapping Between Wireless Component Applications and Application Data Sources | |
| US20050076135A1 (en) | UDDI web service registry system based on an ebXML registry and management method therefor | |
| CN116095081A (en) | Event processing method and device based on block chain 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200724 |
|
| RJ01 | Rejection of invention patent application after publication |