CN117793165A - Method and system for realizing program remote call across physical network - Google Patents

Abstract

The application discloses a method and a system for realizing remote program call across a physical network, wherein the method comprises the following steps: synchronizing data of the intranet database and the extranet database by a data ferrying method; deploying a master control server in the intranet system and deploying a controlled server in the extranet system; the master control server and the controlled side server are used for realizing data communication between an intranet system and an extranet system; when the master side server is started, loading a master side RMI object manager, a slave side RMI object manager proxy, a slave side RMI service proxy and a slave side RMI distribution service; remote call of the master control server to the controlled side server is realized; when the controlled side server is started, loading a controlled side RMI object manager, a main control side RMI object manager proxy, a main control side RMI service proxy and a main control side RMI distribution service; and realizing remote call of the controlled server to the master server.

Description

Method and system for realizing program remote call across physical network

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and system for implementing remote program invocation across a physical network.

Background

An intranet, i.e., a local area network, refers to a set of computers interconnected by multiple computers in a certain area. For communication between internal employees or devices. An intranet typically contains sensitive data and resources such as company confidential documents, databases, internal systems, and the like. The external network, i.e. the wide area network, is also called public network. Is a remote network for connecting computers of local area networks or metropolitan area networks in different areas to support network interconnection in the global scope. The extranet is open and anyone can access resources on the extranet through the internet.

In view of the safety and isolation of the network system, in the prior art, physical isolation is generally set between the internal network and the external network, and the safety of the network system is protected through the internal network and the external network which are physically isolated.

Although the external security of the information is effectively ensured by the method, in the practical application process, a large amount of necessary data exchange is still needed between the internal network and the external network in order to meet the business requirements of departments. Physical isolation also limits many functions, including: the external network system cannot call some related services of the internal network system at will, etc. Causing inconvenience in use of the network system.

Disclosure of Invention

In order to solve the technical problems, the application provides a method and a system for realizing remote program call across a physical network, and the method is used for realizing data synchronization and service call of a physically isolated internal network and external network system.

Specifically, the technical scheme of the application is as follows:

in a first aspect, the present application discloses a method for implementing remote invocation of a program across a physical network, including:

synchronizing data of the intranet database and the extranet database by a data ferrying method;

deploying a master control server in the intranet system and deploying a controlled server in the extranet system; the master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system;

the master side server loads a master side RMI object manager, a slave side RMI object manager proxy, a slave side RMI service proxy and a slave side RMI distribution service when started; remote call of the master side server to the controlled side server is realized;

the controlled side server loads a controlled side RMI object manager, a main control side RMI object manager proxy, a main control side RMI service proxy and a main control side RMI distribution service when started; and realizing remote call of the controlled side server to the master side server.

In some embodiments, there is physical isolation between the intranet system and the extranet system;

the intranet system is connected with the intranet database, and the extranet system is connected with the extranet database.

In some embodiments, the method for implementing remote program call across a physical network further includes:

after the data in the intranet database is updated, completing the data synchronization from the data in the intranet database to the extranet database through a data ferrying method;

or after the data in the external network database is updated, finishing the data synchronization from the data in the external network database to the internal network database through a data ferrying method.

In some embodiments, the master server loads a master RMI object manager, a slave RMI object manager agent, a slave RMI service agent and a slave RMI distribution service when started, and specifically includes:

the master server loads and generates a master RMI object manager by acquiring a master RMI port, an intranet message receiving and transmitting object, a master RMI protocol address and a first distribution RMI calling service;

the master RMI object manager is used for managing a master RMI service object so as to be called by the controlled server;

the master side server loads and generates a controlled RMI object manager agent through a controlled RMI port and a controlled RMI protocol address; and then loading and generating a controlled RMI service agent and a controlled RMI distribution service in turn.

In some embodiments, the implementation of the remote call from the master server to the slave server specifically includes:

the master side server realizes remote method call of the slave side server through the slave side RMI distribution service;

or the master side server obtains the RMI distribution service of the controlled side through a controlled side service proxy factory to realize remote method call of the controlled side server.

In some embodiments, the controlled server loads the controlled RMI object manager, the master RMI object manager agent, the master RMI service agent and the master RMI distribution service when started, and specifically includes:

the controlled party server loads and generates the controlled party RMI object manager by acquiring a controlled party RMI port, a controlled party RMI protocol address and a second distribution RMI call service;

the controlled party RMI object manager is used for managing the controlled party RMI service object so as to be called by the master party server;

the controlled side server loads and generates the master side RMI object manager proxy through a master side RMI port and a master side RMI protocol address; and then loading and generating the RMI service agent of the master side and the RMI distribution service of the master side in sequence.

In some embodiments, the master RMI service proxy is further configured to load and generate a master message service proxy.

In some embodiments, the implementation of the remote call from the controlled server to the master server specifically includes:

the controlled side server realizes the remote message service of the main control side server through the main control side message service proxy;

or the controlled side server obtains the message service proxy of the main control side through a service proxy factory of the main control side, and realizes the remote message service of the main control side server;

or the controlled side server distributes service through the master side RMI to realize remote method call of the master side server;

or the controlled side server obtains the RMI distribution service of the main control side through the main control side service proxy factory to realize remote method call of the main control side server.

In some embodiments, the method for implementing remote program call across a physical network further includes:

the external network system loads and generates a message manager of a controlled party through the message service agent of the main control party;

and the external network system calls the internal network message receiving and transmitting object in the internal network system through the controlled party message manager, and then calls the internal network message service to finish the sending of the message.

In a second aspect, the present application discloses a system for implementing remote procedure call across a physical network, where the system is configured to implement a method for implementing remote procedure call across a physical network according to any one of the foregoing embodiments, where the method includes:

the synchronization module is used for synchronizing the data of the intranet database and the extranet database through a data ferrying method;

the deployment module is used for deploying a master server in the intranet system and deploying a controlled server in the extranet system; the master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system;

the master control module is used for loading a master control RMI object manager, a controlled party RMI object manager agent, a controlled party RMI service agent and a controlled party RMI distribution service when the master control server is started; remote call of the master side server to the controlled side server is realized;

the controlled module is used for loading a controlled RMI object manager, a master RMI object manager agent, a master RMI service agent and a master RMI distribution service when the controlled server is started; and realizing remote call of the controlled side server to the master side server.

Compared with the prior art, the application has at least one of the following beneficial effects:

1. in the application, the external network system calls the internal network system and other related services through the remote method call mode, so that network isolation is achieved, and the safety of the internal network system is ensured. And the data synchronization of the internal network and the external network databases is completed through a database ferrying program, and the communication of the internal network system and the external network system is completed through the service of the main control party and the service of the controlled party.

2. The method and the device can selectively open partial functions of the external network system, and ensure that the data of the open external network system functional part is consistent with the data of the internal network system functional part. The method can be suitable for a plurality of service scenes, for example, only intranet maintenance data is required for some intranet system functions, only data can be queried by an external network, and the method for realizing program remote calling by crossing physical networks in the method can meet the requirements of the specified service scenes.

Drawings

The above features, technical features, advantages and implementation of the present application will be further described in the following description of preferred embodiments in a clear and easily understood manner with reference to the accompanying drawings.

FIG. 1 is a flow chart of steps of one method embodiment of the present application;

fig. 2 is a schematic diagram of physical isolation and data synchronization between an intranet and an extranet in an embodiment provided in the present application;

fig. 3 is a schematic diagram of an intranet and extranet system call in an embodiment provided in the present application;

fig. 4 is a schematic diagram of loading condition when an intranet system (a master) is started in the embodiment of the present application;

fig. 5 is a schematic diagram of loading condition when an external network system (controlled party) is started in the embodiment of the present application;

fig. 6 is a schematic diagram of a message service of an extranet system calling intranet system in an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

For simplicity of the drawing, only the parts relevant to the invention are schematically shown in each drawing, and they do not represent the actual structure thereof as a product. Additionally, in order to simplify the drawing for ease of understanding, components having the same structure or function in some of the drawings are shown schematically with only one of them, or only one of them is labeled. Herein, "a" means not only "only this one" but also "more than one" case.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

In this context, it should be noted that the terms "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected, unless explicitly stated or limited otherwise; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context.

In addition, in the description of the present application, the terms "first," "second," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will explain specific embodiments of the present application with reference to the accompanying drawings. It is obvious that the drawings in the following description are only examples of the present application, and that other drawings and other embodiments may be obtained from these drawings by those skilled in the art without undue effort.

The intranet generally refers to a local area network inside an organization or an organization, and the local area network can realize functions of file management, application software sharing, printer sharing, scheduling in a work group, email, fax communication service and the like. The local area network is closed, and may be composed of two computers in an office, or thousands of computers in a company.

The external network, i.e. the wide area network, is also called public network. Is a remote network for connecting computers in local area networks or metropolitan area networks in different areas. Typically span a large physical range, ranging from tens of kilometers to thousands of kilometers, which can connect multiple areas, cities and countries, or span several continents and provide long-range communications, forming an international long-range network. The wide area network is not equivalent to the internet.

As network attack technology continues to increase, the risk of malicious intrusion into the internal network increases dramatically. A security technology capable of meeting the information and data exchange requirements of the internal and external networks and preventing the occurrence of network security events has been developed, and the technology is called a physical isolation technology. The basic principle of the physical isolation technology is to avoid direct information exchange and physical communication between two computers, and the isolation purpose is to block direct network attack activities, avoid sensitive data from leaking to the outside, ensure information and data exchange between different network security domains and protect sensitive information in an intranet from unauthorized external access and attack.

In the prior art, physical isolation is achieved by using different network devices, network topologies and network connections. The physical isolation may be achieved by:

1. using a firewall: a firewall is a network security device that can monitor and control network traffic. By configuring firewall rules, the traffic of the external access intranet can be limited and potential attacks can be prevented.

2. Using a network isolation device: such as a gatekeeper. The intranet and the extranet can use different network address spaces and are connected through equipment such as a router, so that the flow between the intranet and the extranet is ensured not to interfere with each other.

Through physical isolation, the security and privacy of the intranet can be effectively protected, and unauthorized access and attack are prevented. Meanwhile, physical isolation can improve the performance and stability of the intranet and reduce the influence of external attack on the intranet.

Although physical isolation can guarantee information security, in the practical application process, physical isolation has a certain limitation in limiting data exchange, which causes inconvenience. The traditional cross-network data exchange mode has potential safety hazards, such as manual U disk ferry and optical disk ferry machine. The U disk ferrying mode is convenient and quick, but has risks of data leakage and virus infection. Compared with the ferry of a U disk, the optical disk ferry machine has the advantages that the safety is improved, but the hidden danger of the mobile storage equipment exists. With the continuous development of network attack means and the enhancement of network security demands, a more flexible and safe data exchange mode is required to be sought, so that the data exchange demands among different networks or systems can be met, and potential safety hazards can be effectively prevented.

According to the method and the device, based on a physical isolation technology, the two networks are opened through a technical means at the same time, so that communication between the internal network and the external network is realized. When the system is deployed, a scheme of deploying a set of system by adopting an intranet and an extranet which are physically isolated is adopted for deployment, the intranet and the extranet are communicated through technical means, the intranet system comprises other services related to the system, the extranet system needs to communicate by calling the services of the intranet system and calling the other services related to the system, and meanwhile, the functions and the data of the two sets of systems are required to be kept consistent.

Referring to fig. 1 of the drawings, an embodiment of a method for implementing remote program call across a physical network provided in the present application includes the following steps:

and S100, synchronizing the data of the intranet database and the extranet database by a data ferrying method.

Specifically, after the data in the intranet database is updated, the data synchronization from the data in the intranet database to the extranet database is completed through a data ferrying method. Or after the data in the external network database is updated, finishing the data synchronization from the data in the external network database to the internal network database through a data ferrying method.

S200, a master server is deployed in the intranet system, and a slave server is deployed in the extranet system. The master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system.

Specifically, physical isolation exists between the intranet system and the extranet system.

The intranet system is connected with the intranet database, and the extranet system is connected with the extranet database.

S300, when the master server is started, loading a master RMI object manager, a slave RMI object manager agent, a slave RMI service agent and a slave RMI distribution service. And realizing remote call of the master side server to the controlled side server.

S400, the controlled side server loads the controlled side RMI object manager, the main control side RMI object manager agent, the main control side RMI service agent and the main control side RMI distribution service when starting. And realizing remote call of the controlled side server to the master side server.

Specifically, RMI (Remote Method Invocation) is a remote method call, which is a method that allows an object running on one Java virtual machine to call an object running on another Java virtual machine. The two virtual machines may be different processes running on the same computer or may be different computers running on a network. Communication can be carried out between an intranet system and an extranet system through the RMI technology, and the mutual calling of the extranet service and the synchronization of data are achieved.

Another embodiment of a method for implementing remote program call across a physical network is provided, and the technical scheme is as follows:

1. the intranet and the extranet are physical isolation networks, the intranet system is connected with the intranet database, the extranet system is connected with the extranet database, and the intranet database and the extranet database are communicated in a database synchronization mode through a database ferrying program, so that bidirectional synchronization of database data is completed.

2. On the premise of communicating the data of the internal network and the external network, the internal network system and the external network system are respectively deployed as a master control side server and a controlled side server by technical means, so that the communication between the internal network and the external network system is achieved.

3. The master server is booted up with loads RMIObject Manager (master RMI object manager), RMIObject Client Proxy Manager (slave RMI object manager proxy), RMI Service Proxy (slave RMI service proxy), service Proxy Factory Bean (slave RMI distribution service).

4. When the master server calls the slave server, the remote call is performed by acquiring the slave service proxy method through Service Proxy Factory Bean (slave service proxy factory).

5. The slave server boot-time loads RMIObject Manager (slave RMI object manager), RMIObject Client Proxy Manager (master RMI object manager proxy), RMI Service Proxy (master RMI service proxy), service Proxy Factory Bean (master RMI distribution service).

6. When the controlled server calls the main control server, the main control service proxy method is obtained through Service Proxy Factory Bean (main control service proxy factory) to carry out remote call.

7. Through the mutual call of the master control side server and the slave control side server, the communication between the intranet system and the extranet system can be realized, and other services related to the intranet system, such as message service and the like, can be called by the extranet system.

8. And after the data of the intranet system is changed, finishing the data synchronization from the data of the intranet system to the data of the extranet system through a database ferrying program. After the data of the external network system is changed, the data synchronization from the data of the external network system to the data of the internal network system is completed through a database ferrying program.

In particular, in this embodiment, the following improvements are provided compared to the prior art: 1. and the data synchronization of the internal network and the external network databases is completed through a database ferrying program, and the communication of the internal network system and the external network system is completed through the service of the main control party and the service of the controlled party.

2. The external network system calls the internal network system and other related services through the remote method call mode, so that network isolation is achieved, and the safety of the internal network system is ensured.

3. The method and the device can selectively open partial functions of the external network system, and ensure that the data of the open external network system functional part is consistent with the data of the internal network system functional part.

4. The method and the device can be suitable for many business scenes, for example, only intranet maintenance data are required by some intranet system functions, only data can be queried by an extranet, and the business scene requirements can be met by applying the method and the device.

Another embodiment of a method for implementing remote program invocation across a physical network according to the present application is further described in the foregoing embodiments with reference to the accompanying drawings. Comprising the following steps:

in step S100, the intranet and the extranet are physically isolated and data synchronized, as shown in fig. 2 of the specification: specifically, the intranet and the extranet are physically isolated, and the data synchronization of the intranet database and the extranet database is completed through a database ferrying program. After the intranet system maintains the data and stores the data in an intranet database, the intranet system can be synchronized into the database of the extranet system through a database ferrying program. And the data attributes changed by the external network system are also synchronized into the database of the internal network system through the database ferrying program after being stored into the external network database.

In step S200, the intranet and extranet system calls are as shown in fig. 3 of the specification: specifically, the intranet system adopts a main control party deployment mode, and other related services, such as message service, are deployed in the intranet. The external network system adopts a controlled party deployment mode, and completes business operations such as message transmission, data synchronization and the like by calling the RMI service of the master party. And the intranet system (master control party) completes business operations such as data synchronization and the like by calling the RMI service of the extranet system (slave party).

In step S300, the intranet system (the master) is loaded when started, as shown in fig. 4: specifically, when the intranet system (the master) starts, a master RMI object manager (master RMIObject Manager) is generated by loading a master RMI protocol address (via uri), a master RMI port (RMIPort), a distribution RMI call service (RMIDispatcher Service) and an intranet messaging object (dsNet CommProxy Manager). The master RMI object manager (master RMIObject Manager) is configured to manage the master RMI service objects for invocation by the controlled party. The controlled RMI object manager proxy (slave RMIObject Client Proxy Manager) is generated by a controlled RMI protocol address (via Uri), controlled RMI port (RMIPort) load. The generation controlled RMI service proxy (slave RMI Service Proxy), controlled RMI distribution service (mirror RMIDispatcher Service) are then loaded in sequence. The controlled RMI distribution service (mirror RMIDispatcher Service) is for the master to invoke the controlled RMI service.

In step S400, the external network system (controlled party) is loaded during startup, as shown in fig. 5 in the specification: specifically, the external network system (controlled party) generates a controlled RMI object manager (slave RMIObject Manager) by loading a controlled RMI protocol address (via Uri), a controlled party RMI port (RMIPort), and a distribution RMI call service (RMIDispatcher Service) at startup. The controlled RMI object manager (slave RMIObject Manager) is operable to manage the controlled RMI service objects for invocation by the master. The master RMI object manager proxy (master RMIObject Client Proxy Manager) is generated by a master RMI protocol address (via Uri), a master RMI port (RMIPort) load. The master RMI service proxy (master RMI Service Proxy), master RMI distribution service (mirror RMIDispatcher Service) are then loaded in sequence. The master RMI distribution service (mirror RMIDispatcher Service) is used for the controlled party to invoke the master RMI service. The master message service agent (dsNet Comm Proxy Manager) is generated by the master RMI service agent (master RMI Service Proxy) loading. A master message service proxy (dsNet Comm Proxy Manager) is used for the slave to invoke the master message service.

In another implementation manner of this embodiment, S500 is further included, and the external network system invokes a message service of the internal network system. Specific: and the external network system loads and generates a message manager of the controlled party through the message service agent of the main control party. And calling the intranet message receiving and transmitting object in the intranet system through the controlled side message manager, and calling intranet message service to complete the sending of the message.

More preferably, as shown in fig. 6 of the specification: the external network system loads and generates a controlled message manager (dsNet Comm Manager) through a main control party message service agent (dsNet CommProxy Manager), the external network system calls an internal network message receiving and transmitting object (dsNet Comm Proxy Manager) of the internal network system through the controlled message manager (dsNet Comm Manager), the internal network message receiving and transmitting object (dsNet Comm Proxy Manager) of the internal network system calls the internal network message service again, and finally the sending of the message is completed.

Based on the same technical conception, the application also discloses a system for realizing program remote call across physical networks, which can be used for realizing any method for realizing program remote call across physical networks, and concretely, the embodiment of the system for realizing program remote call across physical networks comprises the following steps:

and the synchronization module is used for synchronizing the data of the intranet database and the extranet database through a data ferrying method.

The deployment module is used for deploying the master server in the intranet system and deploying the controlled server in the extranet system. The master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system.

And the main control module is used for loading a main control RMI object manager, a controlled party RMI object manager agent, a controlled party RMI service agent and a controlled party RMI distribution service when the main control party server is started. And realizing remote call of the master side server to the controlled side server.

And the controlled module is used for loading the controlled RMI object manager, the master RMI object manager proxy, the master RMI service proxy and the master RMI distribution service when the controlled server is started. And realizing remote call of the controlled side server to the master side server.

The method and the system for realizing remote program call across the physical network have the same technical conception, and the technical details of the two embodiments are mutually applicable, so that repetition is reduced, and the description is omitted.

It will be apparent to those skilled in the art that the above-described program modules are only illustrated in the division of the above-described program modules for convenience and brevity, and that in practical applications, the above-described functional allocation may be performed by different program modules, i.e., the internal structure of the apparatus is divided into different program units or modules, to perform all or part of the above-described functions. The program modules in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one processing unit, where the integrated units may be implemented in a form of hardware or in a form of a software program unit. In addition, the specific names of the program modules are also only for distinguishing from each other, and are not used to limit the protection scope of the present application.

In the foregoing embodiments, the descriptions of the embodiments are focused on, and the parts of a certain embodiment that are not described or depicted in detail may be referred to in the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The above-described embodiments of the apparatus are exemplary only, and exemplary, the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, exemplary, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims (10)

1. A method for implementing remote invocation of a program across a physical network, comprising:

synchronizing data of the intranet database and the extranet database by a data ferrying method;

deploying a master control server in the intranet system and deploying a controlled server in the extranet system; the master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system;

the master side server loads a master side RMI object manager, a slave side RMI object manager proxy, a slave side RMI service proxy and a slave side RMI distribution service when started; remote call of the master side server to the controlled side server is realized;

the controlled side server loads a controlled side RMI object manager, a main control side RMI object manager proxy, a main control side RMI service proxy and a main control side RMI distribution service when started; and realizing remote call of the controlled side server to the master side server.

2. A method of implementing remote invocation of a program across a physical network as recited in claim 1, wherein: physical isolation exists between the intranet system and the extranet system;

the intranet system is connected with the intranet database, and the extranet system is connected with the extranet database.

3. The method for implementing remote invocation of a program across a physical network as recited in claim 1, further comprising:

after the data in the intranet database is updated, completing the data synchronization from the data in the intranet database to the extranet database through a data ferrying method;

or after the data in the external network database is updated, finishing the data synchronization from the data in the external network database to the internal network database through a data ferrying method.

4. A method of implementing remote invocation of a program across a physical network as recited in claim 1, wherein: the master server loads a master RMI object manager, a slave RMI object manager proxy, a slave RMI service proxy and a slave RMI distribution service when started, and specifically comprises the following steps:

the master server loads and generates a master RMI object manager by acquiring a master RMI port, an intranet message receiving and transmitting object, a master RMI protocol address and a first distribution RMI calling service;

the master RMI object manager is used for managing a master RMI service object so as to be called by the controlled server;

the master side server loads and generates a controlled RMI object manager agent through a controlled RMI port and a controlled RMI protocol address; and then loading and generating a controlled RMI service agent and a controlled RMI distribution service in turn.

5. The method for implementing remote program call across physical network as recited in claim 4, wherein said implementing remote call from said master server to said slave server comprises:

the master side server realizes remote method call of the slave side server through the slave side RMI distribution service;

or the master side server obtains the RMI distribution service of the controlled side through a controlled side service proxy factory to realize remote method call of the controlled side server.

6. The method for implementing remote program call across physical network as recited in claim 4, wherein the controlled server loads the controlled RMI object manager, the master RMI object manager proxy, the master RMI service proxy, and the master RMI distribution service when starting up, specifically comprising:

the controlled party server loads and generates the controlled party RMI object manager by acquiring a controlled party RMI port, a controlled party RMI protocol address and a second distribution RMI call service;

the controlled party RMI object manager is used for managing the controlled party RMI service object so as to be called by the master party server;

the controlled side server loads and generates the master side RMI object manager proxy through a master side RMI port and a master side RMI protocol address; and then loading and generating the RMI service agent of the master side and the RMI distribution service of the master side in sequence.

7. The method for implementing remote invocation of a program across a physical network as recited in claim 6, wherein: the master RMI service proxy is further configured to load and generate a master message service proxy.

8. The method for implementing remote program call across physical network as recited in claim 7, wherein said implementing remote call from said controlled server to said master server comprises:

the controlled side server realizes the remote message service of the main control side server through the main control side message service proxy;

or the controlled side server obtains the message service proxy of the main control side through a service proxy factory of the main control side, and realizes the remote message service of the main control side server;

or the controlled side server distributes service through the master side RMI to realize remote method call of the master side server;

or the controlled side server obtains the RMI distribution service of the main control side through the main control side service proxy factory to realize remote method call of the main control side server.

9. A method of implementing remote invocation of a program across a physical network as recited in any of claims 6-8, further comprising:

the external network system loads and generates a message manager of a controlled party through the message service agent of the main control party;

and the external network system calls the internal network message receiving and transmitting object in the internal network system through the controlled party message manager, and then calls the internal network message service to finish the sending of the message.

10. A system for implementing remote invocation of a program across a physical network, the system being configured to implement a method for implementing remote invocation of a program across a physical network as recited in any of claims 1-9, comprising:

the synchronization module is used for synchronizing the data of the intranet database and the extranet database through a data ferrying method;

the deployment module is used for deploying a master server in the intranet system and deploying a controlled server in the extranet system; the master control side server and the controlled side server are used for realizing data communication between the intranet system and the extranet system;

the master control module is used for loading a master control RMI object manager, a controlled party RMI object manager agent, a controlled party RMI service agent and a controlled party RMI distribution service when the master control server is started; remote call of the master side server to the controlled side server is realized;

the controlled module is used for loading a controlled RMI object manager, a master RMI object manager agent, a master RMI service agent and a master RMI distribution service when the controlled server is started; and realizing remote call of the controlled side server to the master side server.