CN108040060B - Method and device for cross-gatekeeper communication - Google Patents

Method and device for cross-gatekeeper communication Download PDF

Info

Publication number
CN108040060B
CN108040060B CN201711369770.3A CN201711369770A CN108040060B CN 108040060 B CN108040060 B CN 108040060B CN 201711369770 A CN201711369770 A CN 201711369770A CN 108040060 B CN108040060 B CN 108040060B
Authority
CN
China
Prior art keywords
file
request
response
access
gatekeeper
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
Application number
CN201711369770.3A
Other languages
Chinese (zh)
Other versions
CN108040060A (en
Inventor
许海涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Youyun Software Co ltd
Original Assignee
Hangzhou Youyun Software Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou Youyun Software Co ltd filed Critical Hangzhou Youyun Software Co ltd
Priority to CN201711369770.3A priority Critical patent/CN108040060B/en
Publication of CN108040060A publication Critical patent/CN108040060A/en
Application granted granted Critical
Publication of CN108040060B publication Critical patent/CN108040060B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281Proxies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

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)

Abstract

The invention provides a method and a device for cross-gateway communication, wherein the method is applied to an agent program of an access party and comprises the following steps: receiving an access request sent by an access party; writing the access request into the request file, and sending the request file to the gatekeeper so that the gatekeeper synchronizes the request file to the server side agent program, so that the server side agent program sends the access request to the target server according to the request file; and acquiring a response file synchronized by the gatekeeper, and sending response information carried in the response file to the access party. According to the method for communication across the gatekeeper, the agent programs are configured at the two ends of the gatekeeper, then network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper cannot communicate in the prior art is solved.

Description

Method and device for cross-gatekeeper communication
Technical Field
The invention relates to the technical field of communication, in particular to a method and a device for cross-gatekeeper communication.
Background
In the field of IT operation and maintenance, especially for industries with high safety requirements, gatekeepers become an important part for constructing network architectures. Between two independent host systems connected with the physical isolation gatekeeper, no physical connection, logical connection, information transmission command and information transmission protocol exist in communication, no information packet forwarding according to the protocol exists, and only the protocol-free ferry of the data file exists. Some industries deploy multiple gatekeepers throughout the network architecture to isolate the various network environments.
But this also causes the problem of abnormal communication among multiple networks. For example, in an operation and maintenance scene, monitoring data of devices in each network needs to be simultaneously displayed on one platform, and in this case, correct data transmission cannot be achieved, which increases the difficulty of operation and maintenance.
In summary, in the prior art, the network environments at both ends of the gatekeeper cannot communicate.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a method and an apparatus for cross-gatekeeper communication, so as to alleviate the technical problem in the prior art that the network environments at both ends of the gatekeeper cannot communicate.
In a first aspect, an embodiment of the present invention provides a method for cross-gatekeeper communication, which is applied to an access-side agent program, where the access-side agent program is set in an access-side server, and the method includes:
receiving an access request sent by an access party, wherein the access request comprises: HTTP access request, HTTPs access request;
writing the access request into a request file, and sending the request file to a gatekeeper so that the gatekeeper synchronizes the request file to a server-side agent program, so that the server-side agent program sends the access request to a target server according to the request file, wherein the target server returns a response file containing response information to the gatekeeper through the server-side agent program after receiving the access request;
and acquiring the response file synchronized by the gatekeeper, and sending response information carried in the response file to the access party.
With reference to the first aspect, an embodiment of the present invention provides a first possible implementation manner of the first aspect, where acquiring the response file synchronized by the gatekeeper, and sending response information carried in the response file to the access party includes:
monitoring whether the response file is generated or not;
when the response file is generated, acquiring the response file synchronized by the gatekeeper;
analyzing the response file to obtain the response information;
and sending the response information to the access party.
With reference to the first aspect, an embodiment of the present invention provides a second possible implementation manner of the first aspect, where when the response file is not generated, the method further includes:
judging whether the waiting time reaches a preset time length or not;
if the waiting time reaches the preset duration, sending error information to the access party;
and if the waiting time does not reach the preset duration, waiting for the response file.
With reference to the first aspect, an embodiment of the present invention provides a third possible implementation manner of the first aspect, where the access request includes: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
In a second aspect, an embodiment of the present invention further provides a method for cross-gateway communication, where the method is applied to a server-side agent program, where the server-side agent program is arranged in a server of a server, and the method includes:
acquiring a request file of gatekeeper synchronization, wherein the request file comprises an access request;
analyzing the request file to obtain the access request, wherein the access request comprises: HTTP access request, HTTPs access request;
sending the access request to a target server;
receiving response information returned by the target server according to the access request;
and writing the response information into a response file, and sending the response file to the gatekeeper so that the gatekeeper synchronizes the response file to an access party agent program, so that the access party agent program sends the response information to an access party according to the response file.
With reference to the second aspect, an embodiment of the present invention provides a first possible implementation manner of the second aspect, where the access request includes: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
In a third aspect, an embodiment of the present invention further provides an apparatus for cross-gatekeeper communication, where the apparatus is disposed in an access server, and the apparatus includes:
a first receiving module, configured to receive an access request sent by an accessing party, where the access request includes: HTTP access request, HTTPs access request;
the first writing module is used for writing the access request into a request file and sending the request file to a gateway so that the gateway synchronizes the request file to a server-side agent program to enable the server-side agent program to send the access request to a target server according to the request file, wherein the target server returns a response file containing response information to the gateway through the server-side agent program after receiving the access request;
and the first acquisition module is used for acquiring the response file synchronized by the gatekeeper and sending response information carried in the response file to the access party.
With reference to the third aspect, an embodiment of the present invention provides a first possible implementation manner of the third aspect, where the first obtaining module includes:
the monitoring unit is used for monitoring whether the response file is generated or not;
the acquiring unit is used for acquiring the response file synchronized by the gatekeeper when the response file is generated;
the analysis unit is used for analyzing the response file to obtain the response information;
and the sending unit is used for sending the response information to the access party.
With reference to the third aspect, an embodiment of the present invention provides a second possible implementation manner of the third aspect, where, when the response file is not generated, the apparatus includes:
the judging module is used for judging whether the waiting time reaches a preset time length or not;
the first sending module is used for sending error information to the access party if the waiting time reaches the preset duration;
and the waiting module waits for the response file if the waiting time does not reach the preset duration.
In a fourth aspect, an embodiment of the present invention further provides an apparatus for cross-gatekeeper communication, where the apparatus is disposed in a server, and the apparatus includes:
the second acquisition module is used for acquiring a request file of gateway synchronization, wherein the request file comprises an access request;
the analysis module is used for analyzing the request file to obtain the access request, wherein the access request comprises: HTTP access request, HTTPs access request;
the second sending module is used for sending the access request to the target server;
the second receiving module is used for receiving response information returned by the target server according to the access request;
and the second writing module is used for writing the response information into a response file and sending the response file to the gatekeeper so that the gatekeeper synchronizes the response file to the access party agent program and the access party agent program sends the response information to an access party according to the response file.
The embodiment of the invention has the following beneficial effects: the embodiment of the invention provides a method and a device for cross-gateway communication, wherein the method is applied to an access party agent program, the access party agent program is arranged in an access party server, and the method comprises the following steps: receiving an access request sent by an access party, wherein the access request comprises: HTTP access request, HTTPs access request; writing the access request into a request file, and sending the request file to a gatekeeper so that the gatekeeper synchronizes the request file to a server-side agent program, so that the server-side agent program sends the access request to a target server according to the request file, wherein the target server returns a response file containing response information to the gatekeeper through the server-side agent program after receiving the access request; and acquiring a response file synchronized by the gatekeeper, and sending response information carried in the response file to the access party.
In the prior art, network environments at two ends of a network gate cannot communicate. In the method for cross-gateway communication provided by the embodiment of the invention, the access party agent program receives an access request sent by an access party, then writes the access request into a request file, sends the request file to the gateway, further, the gateway can synchronize the request file to the service party agent program, and the service party agent program sends the access request to the target server according to the request file, so that the target server returns a response file containing response information to the gateway through the service party agent program after receiving the access request, and finally, the access party agent program obtains the response file synchronized with the gateway and sends the response information carried in the response file to the access party, thereby realizing cross-gateway communication. According to the method for communication across the gatekeeper provided by the embodiment of the invention, the agent programs are configured at the two ends of the gatekeeper, and then the network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, so that the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper can not communicate in the prior art is solved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of a method for cross-gatekeeper communication according to an embodiment of the present invention;
fig. 2 is a flowchart of acquiring a response file synchronized by a gatekeeper and sending response information carried in the response file to an access party according to an embodiment of the present invention;
fig. 3 is a flowchart of determining a waiting duration by an agent of an accessing party according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an agent deployment method and a data flow transfer process according to an embodiment of the present invention;
FIG. 5 is a flowchart of another method for cross gatekeeper communication according to an embodiment of the present invention;
fig. 6 is a schematic diagram of an apparatus for cross-gatekeeper communication according to an embodiment of the present invention;
fig. 7 is a schematic diagram of another apparatus for cross-gatekeeper communication according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For the convenience of understanding the present embodiment, a method for cross-gatekeeper communication disclosed in the present embodiment is first described in detail.
The first embodiment is as follows:
a method for communication across gateways, which is applied to an access-side agent program, the access-side agent program is arranged in an access-side server, and with reference to fig. 1, the method includes:
s102, receiving an access request sent by an access party, wherein the access request comprises: HTTP access request, HTTPs access request;
in the embodiment of the invention, the access party can be understood as a terminal device on the gateway side, and the agent program of the access party is arranged in the server of the access party. Specifically, the agent of the access party is actually an installation package, and in practice, the user can install the installation package in any server of the access party.
Meanwhile, the gatekeeper is configured, for example, a file transfer service is established on the gatekeeper, and synchronization folders are respectively established for the access party and the service party, which may be referred to as an access party synchronization folder and a service party synchronization folder for convenience of description.
S104, writing the access request into the request file, and sending the request file to the gatekeeper so that the gatekeeper synchronizes the request file to the server-side agent program, so that the server-side agent program sends the access request to the target server according to the request file, wherein the target server returns a response file containing response information to the gatekeeper through the server-side agent program after receiving the access request;
after receiving an access request sent by an access party, an agent program of the access party writes the access request into a request file and sends the request file to a gatekeeper, specifically, sends the request file to an access party synchronous folder configured by the gatekeeper.
The process of the gatekeeper synchronizing the request file to the server agent is described in detail below:
after the request file is sent to the access party synchronous folder configured by the gatekeeper, the gatekeeper synchronizes the request file in the access party synchronous folder to the service party synchronous folder, and the service party agent program can acquire the request file in the service party synchronous folder.
And after the service side agent program obtains the request file, analyzing the request file to obtain an access request, and then sending the access request to the target server.
After receiving the access request, the target server returns response information to the server side agent program according to the access request, after receiving the response information, the server side agent program writes the response information into a response file and sends the response file to a server side synchronous folder configured by the gateway, and the gateway synchronizes the response file in the server side synchronous folder to the access side synchronous folder.
It should be noted that the access-side agent is the same as the service-side agent, and when the agent is provided in the access-side server, it is referred to as the access-side agent for convenience of description, and when the agent is provided in the service-side server, it is referred to as the service-side agent for convenience of description. The access party and the service party can exchange roles, namely, the two-way communication across the gateway is supported.
And S106, acquiring the response file of the gatekeeper synchronization, and sending response information carried in the response file to the access party.
Specifically, a response file in an access party synchronization folder configured by the gatekeeper is obtained, and finally, response information carried in the response file is sent to the access party, so that complete communication is realized.
In the prior art, network environments at two ends of a network gate cannot communicate. In the method for cross-gateway communication provided by the embodiment of the invention, the access party agent program receives an access request sent by an access party, then writes the access request into a request file, sends the request file to the gateway, further, the gateway can synchronize the request file to the service party agent program, and the service party agent program sends the access request to the target server according to the request file, so that the target server returns a response file containing response information to the gateway through the service party agent program after receiving the access request, and finally, the access party agent program obtains the response file synchronized with the gateway and sends the response information carried in the response file to the access party, thereby realizing cross-gateway communication. According to the method for communication across the gatekeeper provided by the embodiment of the invention, the agent programs are configured at the two ends of the gatekeeper, and then the network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, so that the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper can not communicate in the prior art is solved.
There are various ways to obtain the response file synchronized by the gatekeeper and send the response information carried in the response file to the access party, and in an optional embodiment, referring to fig. 2, the step of obtaining the response file synchronized by the gatekeeper and sending the response information carried in the response file to the access party includes the following steps:
s201, monitoring whether a response file is generated;
s202, when a response file is generated, acquiring the response file of the gatekeeper synchronization;
s203, analyzing the response file to obtain response information;
and S204, sending the response information to the access party.
Specifically, the access request includes: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
Optionally, when no response file is generated, referring to fig. 3, the method further includes:
s301, judging whether the waiting time reaches a preset time length;
s302, if the waiting time reaches a preset duration, sending error information to an access party;
s303, if the waiting time does not reach the preset duration, waiting for a response file.
Referring to fig. 4, a method of cross-gatekeeper communication is described colloquially with HTTP requests as an example:
the transmitted information (HTTP request and response content) is packaged into a file, and the HTTP request and the response content are transmitted in the environments at two ends of the gatekeeper in a mode of file ferrying (namely synchronization) of the gatekeeper, so that the internal and external networks can normally access. The method comprises the following specific steps:
for example, an intranet accesses an external network, an HTTP request is initiated in the intranet, information in the HTTP request is stored as a request file, and the file is placed in a synchronous folder of a gatekeeper;
the network gate synchronizes the request file in the internal network to a synchronous folder in the external network;
the external network analyzes the request file, forwards the HTTP request to a server which really needs to be accessed, acquires response content, writes the response content into the response file, and places the response content into a synchronous folder of the gatekeeper;
the network gate synchronizes the response file in the external network to the synchronous folder in the internal network;
and the intranet analyzes the response file, acquires the response content and returns the response content to the access party.
The above is a procedure when the access-side agent is the execution subject, and the following description is made when the service-side agent is the execution subject.
Example two:
a method for cross-gateway communication, which is applied to a server-side agent program, and the server-side agent program is disposed in a server of a server, with reference to fig. 5, the method includes:
s502, acquiring a request file for gateway synchronization, wherein the request file comprises an access request;
s504, analyzing the request file to obtain an access request, wherein the access request comprises: HTTP access request, HTTPs access request;
s506, sending an access request to a target server;
s508, receiving response information returned by the target server according to the access request;
s510, writing the response information into the response file, and sending the response file to the gatekeeper, so that the gatekeeper synchronizes the response file to the access party agent program, and the access party agent program sends the response information to the access party according to the response file.
Optionally, the access request comprises: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
The process is similar to that in the first embodiment, and specific contents may refer to the first embodiment, which is not described herein again.
In the prior art, network environments at two ends of a network gate cannot communicate. In the method for cross-gateway communication provided by the embodiment of the invention, the access party agent program receives an access request sent by an access party, then writes the access request into a request file, sends the request file to the gateway, further, the gateway can synchronize the request file to the service party agent program, and the service party agent program sends the access request to the target server according to the request file, so that the target server returns a response file containing response information to the gateway through the service party agent program after receiving the access request, and finally, the access party agent program obtains the response file synchronized with the gateway and sends the response information carried in the response file to the access party, thereby realizing cross-gateway communication. According to the method for communication across the gatekeeper provided by the embodiment of the invention, the agent programs are configured at the two ends of the gatekeeper, and then the network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, so that the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper can not communicate in the prior art is solved.
Example three:
an apparatus for cross-gatekeeper communication, the apparatus being provided in an accessor server, and referring to fig. 6, the apparatus comprising:
a first receiving module 11, configured to receive an access request sent by an accessing party, where the access request includes: HTTP access request, HTTPs access request;
the first writing module 12 is configured to write the access request into the request file, and send the request file to the gatekeeper, so that the gatekeeper synchronizes the request file to the service-side agent program, so that the service-side agent program sends the access request to the target server according to the request file, where after receiving the access request, the target server returns a response file containing response information to the gatekeeper through the service-side agent program;
the first obtaining module 13 is configured to obtain a response file for gatekeeper synchronization, and send response information carried in the response file to the access party.
In the device for cross-gateway communication provided by the embodiment of the invention, the device arranged in the access server receives an access request sent by an access party, then writes the access request into a request file, and sends the request file to the gateway, so that the gateway can synchronize the request file to a service party proxy program, and the service party proxy program sends the access request to a target server according to the request file, so that the target server returns a response file containing response information to the gateway through the service party proxy program after receiving the access request, and finally, the device obtains the response file synchronized with the gateway and sends the response information carried in the response file to the access party, thereby realizing cross-gateway communication. In the device for cross-gatekeeper communication provided by the embodiment of the invention, the agent programs are configured at the two ends of the gatekeeper, and then the network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, so that the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper can not communicate in the prior art is solved.
Optionally, the first obtaining module includes:
the monitoring unit is used for monitoring whether a response file is generated or not;
the acquiring unit is used for acquiring the response file of the gatekeeper synchronization when the response file is generated;
the analysis unit is used for analyzing the response file to obtain response information;
and the sending unit is used for sending the response information to the access party.
Optionally, when no response file is generated, the apparatus includes:
the judging module is used for judging whether the waiting time reaches a preset time length or not;
the first sending module is used for sending error information to the access party if the waiting time reaches a preset time length;
and the waiting module waits for the response file if the waiting time does not reach the preset duration.
Optionally, the access request comprises: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
For details in the third embodiment, reference may be made to the contents in the first embodiment, and details are not repeated herein.
Example four:
an apparatus for cross-gatekeeper communication, the apparatus being provided in a server of a server, with reference to fig. 7, the apparatus comprising:
a second obtaining module 21, configured to obtain a request file for gatekeeper synchronization, where the request file includes an access request;
the parsing module 22 is configured to parse the request file to obtain an access request, where the access request includes: HTTP access request, HTTPs access request;
a second sending module 23, configured to send an access request to the target server;
the second receiving module 24 is configured to receive response information returned by the target server according to the access request;
and a second writing module 25, configured to write the response information into the response file, and send the response file to the gatekeeper, so that the gatekeeper synchronizes the response file to the agent program of the access party, so that the agent program of the access party sends the response information to the access party according to the response file.
Optionally, the access request comprises: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
For details in the fourth embodiment, reference may be made to the contents in the first embodiment, and details are not repeated herein.
In the device for cross-gateway communication provided by the embodiment of the invention, the device arranged in the access server receives an access request sent by an access party, then writes the access request into a request file, and sends the request file to the gateway, so that the gateway can synchronize the request file to a service party proxy program, and the service party proxy program sends the access request to a target server according to the request file, so that the target server returns a response file containing response information to the gateway through the service party proxy program after receiving the access request, and finally, the device obtains the response file synchronized with the gateway and sends the response information carried in the response file to the access party, thereby realizing cross-gateway communication. In the device for cross-gatekeeper communication provided by the embodiment of the invention, the agent programs are configured at the two ends of the gatekeeper, and then the network environment communication at the two ends of the gatekeeper is realized through the cooperation of the agent programs and the gatekeeper, so that the communication safety is high, and the technical problem that the network environments at the two ends of the gatekeeper can not communicate in the prior art is solved.
The computer program product of the method and the apparatus for cross-gatekeeper communication provided in the embodiments of the present invention includes a computer readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In addition, in the description of the embodiments of the present invention, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (10)

1. A method for cross-gatekeeper communication, applied to an accessor agent, the accessor agent being provided in an accessor server, the method comprising:
receiving an access request sent by an access party, wherein the access request comprises: HTTP access request, HTTPs access request;
writing the access request into a request file, and sending the request file to a gatekeeper so that the gatekeeper synchronizes the request file to a server-side agent program, so that the server-side agent program sends the access request to a target server according to the request file, wherein the target server returns a response file containing response information to the gatekeeper through the server-side agent program after receiving the access request;
acquiring the response file synchronized by the gatekeeper, and sending response information carried in the response file to the access party;
wherein the response file of the gatekeeper synchronization is: after receiving the response information, the service side agent program writes the response information into the response file and sends the response file to a service side synchronous folder configured by the gateway;
wherein sending the response information carried in the response file to the access party includes:
after the response file is sent to a server side synchronization folder configured by a gatekeeper, the response file in the server side synchronization folder is synchronized to the access side synchronization folder by the gatekeeper.
2. The method of claim 1, wherein obtaining the response file synchronized by the gatekeeper, and sending response information carried in the response file to the visitor comprises:
monitoring whether the response file is generated or not;
when the response file is generated, acquiring the response file synchronized by the gatekeeper;
analyzing the response file to obtain the response information;
and sending the response information to the access party.
3. The method of claim 2, wherein when the response file is not generated, the method further comprises:
judging whether the waiting time reaches a preset time length or not;
if the waiting time reaches the preset duration, sending error information to the access party;
and if the waiting time does not reach the preset duration, waiting for the response file.
4. The method of claim 1,
the access request includes: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
5. A method for cross-gateway communication, which is applied to a server-side agent program, wherein the server-side agent program is arranged in a server of a server side, and the method comprises the following steps:
acquiring a request file of gatekeeper synchronization, wherein the request file comprises an access request;
analyzing the request file to obtain the access request, wherein the access request comprises: HTTP access request, HTTPs access request;
sending the access request to a target server;
receiving response information returned by the target server according to the access request;
writing the response information into a response file, and sending the response file to the gatekeeper so that the gatekeeper synchronizes the response file to an access party synchronization folder of an access party agent program, so that the access party agent program sends the response information to an access party according to the response file;
the request file is a file which is obtained by writing an access request into a request file after the access request sent by an access party is received by the access party agent program, and sending the request file to a gateway so that the gateway synchronizes the request file to a server party agent program.
6. The method of claim 5,
the access request includes: a request mode, request content and request address;
the response information includes: HTTP status code, response content stored in JSON form.
7. An apparatus for cross-gatekeeper communication, the apparatus being disposed in an accessor server, the apparatus comprising:
a first receiving module, configured to receive an access request sent by an accessing party, where the access request includes: HTTP access request, HTTPs access request;
the first writing module is used for writing the access request into a request file and sending the request file to a gateway so that the gateway synchronizes the request file to a server-side agent program to enable the server-side agent program to send the access request to a target server according to the request file, wherein the target server returns a response file containing response information to the gateway through the server-side agent program after receiving the access request;
the first acquisition module is used for acquiring the response file synchronized by the gatekeeper and sending response information carried in the response file to the access party;
wherein the response file of the gatekeeper synchronization is: after receiving the response information, the service side agent program writes the response information into the response file and sends the response file to a service side synchronous folder configured by the gateway;
wherein the first obtaining module is configured to:
after the response file is sent to a server side synchronization folder configured by a gatekeeper, the response file in the server side synchronization folder is synchronized to the access side synchronization folder by the gatekeeper.
8. The apparatus of claim 7, wherein the first obtaining module comprises:
the monitoring unit is used for monitoring whether the response file is generated or not;
the acquiring unit is used for acquiring the response file synchronized by the gatekeeper when the response file is generated;
the analysis unit is used for analyzing the response file to obtain the response information;
and the sending unit is used for sending the response information to the access party.
9. The apparatus of claim 8, wherein when the response file is not generated, the apparatus comprises:
the judging module is used for judging whether the waiting time reaches a preset time length or not;
the sending module is used for sending error information to the access party if the waiting time reaches the preset duration;
and the waiting module waits for the response file if the waiting time does not reach the preset duration.
10. An apparatus for cross-gatekeeper communication, the apparatus being disposed in a server, the apparatus comprising:
the second acquisition module is used for acquiring a request file of gateway synchronization, wherein the request file comprises an access request;
the analysis module is used for analyzing the request file to obtain the access request, wherein the access request comprises: HTTP access request, HTTPs access request;
the second sending module is used for sending the access request to the target server;
the second receiving module is used for receiving response information returned by the target server according to the access request;
the second writing module is used for writing the response information into a response file and sending the response file to the gatekeeper so that the gatekeeper synchronizes the response file into an access party synchronization folder of an access party agent program, and the access party agent program sends the response information to an access party according to the response file;
the request file is a file which is obtained by writing an access request into a request file after the access request sent by an access party is received by the access party agent program, and sending the request file to a gatekeeper, wherein the gatekeeper synchronizes the request file to a server party agent program.
CN201711369770.3A 2017-12-18 2017-12-18 Method and device for cross-gatekeeper communication Active CN108040060B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711369770.3A CN108040060B (en) 2017-12-18 2017-12-18 Method and device for cross-gatekeeper communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711369770.3A CN108040060B (en) 2017-12-18 2017-12-18 Method and device for cross-gatekeeper communication

Publications (2)

Publication Number Publication Date
CN108040060A CN108040060A (en) 2018-05-15
CN108040060B true CN108040060B (en) 2021-04-27

Family

ID=62099654

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711369770.3A Active CN108040060B (en) 2017-12-18 2017-12-18 Method and device for cross-gatekeeper communication

Country Status (1)

Country Link
CN (1) CN108040060B (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110719307A (en) * 2018-07-12 2020-01-21 深圳云天励飞技术有限公司 Data transmission method, client, server and computer readable storage medium
CN111355752A (en) * 2018-12-20 2020-06-30 阿里巴巴集团控股有限公司 File transmission method, device and equipment based on gatekeeper
CN112688981A (en) * 2019-10-18 2021-04-20 中国司法大数据研究院有限公司 System for remotely operating Linux host through one-way isolation optical gate and implementation method
CN110995698A (en) * 2019-11-29 2020-04-10 上海依图网络科技有限公司 Cross-network request transmission method and device
CN111447256B (en) * 2020-03-05 2022-07-01 中国司法大数据研究院有限公司 Cross-domain micro-service registration and release method and system based on file exchange
CN111444029A (en) * 2020-03-05 2020-07-24 中国司法大数据研究院有限公司 Cross-domain micro-service calling method and system based on file exchange
CN113452653B (en) * 2020-03-25 2022-06-03 成都鼎桥通信技术有限公司 Cross-gatekeeper communication method and system
CN111526124B (en) * 2020-03-26 2022-06-24 郑州信大捷安信息技术股份有限公司 Isolated communication system and method based on internal and external networks
CN113497790B (en) * 2020-04-01 2023-01-17 海能达通信股份有限公司 Data transmission method and system based on gatekeeper and computer storage medium
CN113596184B (en) * 2020-04-30 2023-08-08 华为云计算技术有限公司 Hybrid cloud system, gatekeeper, network access method and storage medium
CN114124929B (en) * 2021-09-29 2024-03-29 奇安信科技集团股份有限公司 Cross-network data processing method and device
CN114257580A (en) * 2021-12-22 2022-03-29 北京博思致新互联网科技有限责任公司 Non-inductive interaction method for border gatekeeper
CN114374562A (en) * 2022-01-14 2022-04-19 中国建设银行股份有限公司 Data transmission method, device, equipment and computer storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103702348A (en) * 2013-12-20 2014-04-02 京信通信系统(中国)有限公司 Detection method and device for network quality under family base station
CN104202300A (en) * 2014-08-06 2014-12-10 广东电网公司电力科学研究院 Data communication method and device based on network isolating device
CN104243495A (en) * 2014-10-11 2014-12-24 中国南方电网有限责任公司 Reverse isolating device cross method and system for JMS (java message service)
CN105635079A (en) * 2014-11-11 2016-06-01 无锡清杨机械制造有限公司 Network isolation gap data exchange system
CN106936780A (en) * 2015-12-30 2017-07-07 北京明朝万达科技股份有限公司 A kind of method for monitoring network and system
CN107454094A (en) * 2017-08-23 2017-12-08 北京明朝万达科技股份有限公司 A kind of data interactive method and system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103702348A (en) * 2013-12-20 2014-04-02 京信通信系统(中国)有限公司 Detection method and device for network quality under family base station
CN104202300A (en) * 2014-08-06 2014-12-10 广东电网公司电力科学研究院 Data communication method and device based on network isolating device
CN104243495A (en) * 2014-10-11 2014-12-24 中国南方电网有限责任公司 Reverse isolating device cross method and system for JMS (java message service)
CN105635079A (en) * 2014-11-11 2016-06-01 无锡清杨机械制造有限公司 Network isolation gap data exchange system
CN106936780A (en) * 2015-12-30 2017-07-07 北京明朝万达科技股份有限公司 A kind of method for monitoring network and system
CN107454094A (en) * 2017-08-23 2017-12-08 北京明朝万达科技股份有限公司 A kind of data interactive method and system

Also Published As

Publication number Publication date
CN108040060A (en) 2018-05-15

Similar Documents

Publication Publication Date Title
CN108040060B (en) Method and device for cross-gatekeeper communication
CN110365793B (en) Illegal external connection monitoring method, device and system and storage medium
US10284644B2 (en) Information processing and content transmission for multi-display
JP5963766B2 (en) System and method for delivering application traffic to a server based on dynamic service response time
CN108512821B (en) Data transmission method, device and system, network gate and transaction data storage method
EP2930911B1 (en) Method and apparatus for controlling sending of heartbeat signal
EP3313022B1 (en) Resending method and device for hypertext transfer request, and client
US10021182B2 (en) Method and apparatus for data synchronization
CN102763373B (en) The method and apparatus using the service of local network devices based on remote access
EP3032838A1 (en) Message processing method, device, gateway, set-top box and internet protocol television system
CN109547524B (en) User behavior storage method, device, equipment and storage medium based on Internet of things
CN106657180B (en) Information transmission method and device for cloud service, terminal equipment and system
CN102761456A (en) Method, device and system for acquiring performance parameters of browser of mobile terminal
US20160205278A1 (en) Information processing apparatus, system, and control method for information processing apparatus
EP2709337A1 (en) Service data processing method, device and system
US9582561B2 (en) Size-based data synchronization
CN117978888A (en) Gateway and data transmission method using same
CN107819599B (en) Message processing method and device
CN113873057A (en) Data processing method and device
CN111600883A (en) Vehicle diagnosis method and system, electronic equipment and storage medium
CN116233085A (en) Multi-terminal streaming media transmission method, system and streaming media server cluster
JP5645008B2 (en) Coexistence communication system, coexistence processing method between communication networks
CN112383617A (en) Method, device, terminal equipment and medium for long connection
CN114827197B (en) Service communication method, device, equipment and medium based on Internet of things
KR102707204B1 (en) Data processing method, apparatus, computer device, and storage 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