Method of controlling exchanges of data between two applications, namely a client-type application and a server-type application respectively

• US 7,440,959 B2
• Filed: 07/01/2002
• Issued: 10/21/2008
• Est. Priority Date: 07/03/2001
• Status: Expired due to Fees

• Current Assignee: Cochard Plociennik Elzbieta
• Original Assignee: Cochard Plociennik Elzbieta
• Inventors: Elzbieta, Cochard Plociennik
• Primary Examiner(s): PANNALA, SATHYANARAYA R
• Application Number:
  US10/482,667
• Publication Number:
  US 20040216128A1
• Time in Patent Office: 2,304 Days
• Field of Search: 707/10, 709200-250, 705/5
• US Class Current: 1/1
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

The invention relates to a method of controlling exchanges of files or other transferable objects between two applications, namely a client-type application and a server-type application respectively, using a TCP/IP FTP-type protocol or similar. One of said applications is an FTP-type application while the other is either an FTP-type application or a compatible application. The inventive method makes use of a Hyperserver application which is executed on a host platform and which performs the role of intermediary between the two applications in transfer protocol negotiations and in the transfer of files or other transferable objects.

Claims

1. Computer implemented method for the control of files or other transferable objects exchanges between FTP type or compatible applications, being a membership of a controlled population, and FTP type applications being a membership of common placed population and being executed on different platforms, said method implementing:

A common placed population of hosts residing in a IP network and having access to a Hyperserver application and sheltering;

FTP type applications or applications able to generate a data flow compatible with FTP protocol,

Files or other transferable objects identifiable and visible to those applications,

A Hyperserver application being executed on a host having access to FTP type or compatible said applications and including;

A controlled and common placed hosts directory database designating communicating applications with their IP addresses and lists of users authorized to access them as well as authorization attributes if necessary,

files or other transferable objects transfer profiles directory database,

Hyperserver application central LOG file containing transfer'"'"'s events log records,

Hyperserver application central journal file containing transfers summary records,

A controlled population of hosts residing in a IP network and sheltering;

Applications of FTP type or being able to generate a data flow compatible with FTP protocol,

Files or other transferable objects identifiable and visible for those applications,

Hyperserver agent applications eventually supplied with their own LOG and journal files,

wherein, in the case of a transfer request coming from Internet network, it comprises the following operations sequence;

Opening of the connection with the Hyperserver application by the Internet network requesting client owing to a set of connection opening commands comprising a user name, a password and, eventually authentication data,

Determination by the Hyperserver application of the directory database entry defining Intranet network aimed application connection attributes in the case where said pieces of information are sufficient keeping into accounts rules defined in the controlled and common placed hosts directory, otherwise using of a supplementary FTP commands to enable to do it,

Research done by the Hyperserver application in the controlled and common placed hosts directory database of all pieces of information concerning the requestor access authorities, the transfer protocol, connection'"'"'s with aimed server modalities, the identification of the process to be executed at the beginning of the connection, as well as eventual start of said process or some number of processes,

Opening of the connection with the aimed application by the Hyperserver application and the exchange of eventually planned commands as soon as it and connection modalities are known,

Carrying out of the negotiation between the client requester and the Hyperserver application up to one of command types store, store unique, retrieve reception,

Identification of a file or other transferable object transfer profile by the Hyperserver application which constitute an entry of the files or other transferable objects transfer profiles directory database following a transfer command reception by the Hyperserver application,

Verification by the Hyperserver application of transfer direction, of the identification of the file to be transferred, its attributes, eventual processes to be executed at the beginning, during and at the end of the transfer as well as the designation of applications under control of which they have to be executed owing to the definition of the determined profile,

Acknowledgement, by the Hyperserver application, of the transfer request received from the client at the end of eventual negotiations of transfer leaded by the transfer profile with aimed application,

Opening of two, FTP meaning, DATA connections to be seen;

one connection between the FTP client and Hyperserver application, and the other one between the Hyperserver application and aimed application, the data received by the Hyperserver application on one connection being afterwards sent to the other one application undergoing, eventually, said during transfer treatment,

Execution of eventual processes at the beginning or at the end of transfer under the control of the Hyperserver agent application of the aimed application host, synchronized with the dialog between this application and the Hyperserver application,

Closing of connections in progress with releasing of eventual end of connection processes,

Recording of the events arrived during the sequence in corresponding files LOG file as well as statistic information in the journal Hyperserver application file and the transmission of records copies to the concerned Hyperserver agent application to be recorded in appropriated local files.

2. Computer implemented for the control of files or other transferable objects exchanges between FTP type or compatible applications, being a membership of a controlled population, and FTP type applications being a membership of common placed population and being executed on different platforms, said method implementing:

A common placed population of hosts residing in a IP network and having access to an Hyperserver application and sheltering;

FTP type applications or applications able to generate a data flow compatible with FTP protocol,

Files or other transferable objects identifiable and visible to those applications,

An Hyperserver application being executed on an host having access to FTP type or compatible said applications and including;

A controlled and common placed hosts directory database designating communicating applications with their IP addresses and lists of users authorized to access them as well as authorization attributes if necessary,

files or other transferable objects transfer profiles directory database,

Hyperserver application central LOG file containing transfer'"'"'s events log records,

Hyperserver application central journal file containing transfers summary records,

A controlled population of hosts residing in a IP network and sheltering;

Applications of FTP type or being able to generate a data flow compatible with FTP protocol,

Files or other transferable objects identifiable and visible for those applications,

Hyperserver agent applications eventually supplied with their own LOG and journal files,

wherein, in the case of a transfer request coming from Intranet network host, the request contains all the information needed to determine the controlled and common placed hosts directory database as well as the files or other transferable objects transfer profiles directory database entries and that it comprises the following operations sequence;

Initialization by the Hyperserver application as a client of two connections, to be seen;

a first connection with the server FTP type or compatible application on the Intranet network and a second connection with a FTP type server on the Internet network, this initialization using the information found in the determined controlled and common placed hosts directory database entry respecting identification, authorization rules applying necessary encryption functions and executing eventual at the start of connection processes,

Negotiation of two FTP transfers according to pieces of information found in the files or other transferable objects transfer profiles directory database and in the request itself, one of transfers being a receipt and the other one transmission of the file or another transferable object,

Releasing of eventual at the beginning of transfer processes, the determination by the Hyperserver application of two sides file names and all transfer attributes as well processes to be released at the beginning, during and at the end of transfer owing to transfer profile and other request parameters,

Forwarding by the Hyperserver application of file data from its origin to its destination trough two DATA connections, if necessary, in FTP meaning or compatibles, between Hyperserver application and two server applications, applying processes said during transfer,

Execution of eventual processes at the end of transfer under the control of the agent of Hyperserver application of the aimed application host, synchronized with the dialog of this application and the Hyperserver application,

Closing of connections in progress with releasing of eventual end of connection processes,

Recording of the events arrived during the sequence in corresponding files LOG files as well as statistic information in the journal Hyperserver application file and the transmission of records copies to the concerned Hyperserver agent application to be recorded in appropriated local files.