Non-inductive boundary data exchange method

Abstract

The invention discloses a non-inductive boundary data exchange method, and relates to the technical field of security boundary exchange, and the method comprises the following steps: calibrating non-inductive boundary data exchange components which are respectively deployed at two ends of a boundary and comprise a CNetPort component and a BNetPort component, an initiating end of the non-inductive boundary data exchange components obtains services by accessing the BNetPort component, the BNetPort component accesses the CNetPort component through the boundary, and the BNetPort component obtains services by accessing the CNetPort component through the boundary; and the CNetPort component accesses the service provided by the server, the CNetPort returns a service result to the BNetPort component through the boundary, and the BNetPort component returns information to the initiator. According to the method, a non-inductive boundary exchange component is constructed through capabilities such as request subpackage / group package, file type identification and automatic ferrying, internal routing distribution and the like, so that boundary limitation is transparent to developers, the software developers are assisted in efficient research and development and rapid deployment, and the development efficiency is improved. The problems that the boundary exchange platform bidirectionally fixes the server IP of the service developer, the transmission content limits Json and the transmission length is limited are solved, and the research and development speed of the developer is greatly increased.

Description

technical field [0001] The present invention relates to the technical field of security border exchange, in particular to a method for exchanging data without sense border. Background technique [0002] The security boundary switching platform is generally used as the boundary between the low-security network and the high-security network. Data services are usually stored in the high-security network, and service consumption applications are generally deployed in the low-security network. Usually, the following configurations are made: register the IP addresses of computer devices at both ends of the boundary with the Mac address. Register the API interfaces and parameters of services at both ends of the boundary to configure the http ferry service. In the process of calling the API interface, only json strings are allowed to be transmitted, and the border platform will review the parameter content of the call. In the process of calling the API interface, the size of the c...

AI Technical Summary

Problems solved by technology

[0003] However, there are currently the following problems. In a relatively strict dual-network interactive platform, the service interface will be registered first, and access to the Internet is strictly restricted. In addition, there are strict restrictions on the size of the data packet, and data flow is not supported. On this basis, Scenarios where it is basically impossible to connect to the internal and external networks, the details are as follows:

[0004] 1. The server is fixed in both directions. The servers at both ends of the border must be two registered computer devices. To replace the server, you need to apply to the border administrator again

[0005] 2. The transmission content is limited. Since the transmission content can only transmit json strings, the transmission of binary files is limited

[0006] 3. The transmission length is limited. Since the transmission content limits the data packet size (generally 50K), large files cannot be transmitted through the interface.

[0007] Due to the above problems, in the process of software development, it is necessary to pay attention to the existence of boundaries at all times, which causes a lot of troubles to software development. Every call must pay attention to the boundary rules, which consumes a lot of debugging time

Images