Transfer client of a secure system for unattended remote file and message transfer

• US 7,536,435 B2
• Filed: 06/29/2004
• Issued: 05/19/2009
• Est. Priority Date: 01/08/2002
• Status: Expired due to Term

• Current Assignee: Bottomline Technologies Incorporated
• Original Assignee: Bottomline Technologies Incorporated
• Inventors: Hoffman, Robert F, Campbell, Eric, Lemanis, Maris N, Maloney, Robert Jr., Mintzer, Andrew
• Primary Examiner(s): Harrell; Robert B
• Application Number:
  US10/879,234
• Publication Number:
  US 20050066012A1
• Time in Patent Office: 1,785 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

A transfer client system exchanges files with a transfer server over an open network such as the Internet. The transfer client comprises a download directory for storing binary objects obtained from a transfer client server for subsequent retrieval by a local data processing system. The transfer client sends a log-on message to a remote transfer server over the open network, the log-on message including the authentication credentials. In response a session ID is obtained from the remote transfer server. The transfer client further sends a read event message to the remote transfer server over the open network, the read event message including the session ID. Event parameters are returned in response, the event parameters comprise identification of a file name and identification of the download directory. The transfer client sends a download message to the remote transfer server over the open network, the download message comprises the session ID and identification of a binary object. A message containing the binary object is returned in response to the file download message and the binary object is stored as a file in the download directory with the file name.

Claims

1. A transfer client system for exchanging files with a transfer server over an open network, the transfer client system comprising:

a download directory for storing binary objects obtained from the transfer server for subsequent retrieval by a local data processing system;

an authentication registry securely storing authentication credentials;

a transfer client for;

i) sending a log-on message to a remote transfer server over a secure transport protocol logical connection established over the open network, the log-on message including the authentication credentials;

ii) obtaining a session ID from the remote transfer server in response to the log-on message;

iii) sending a retrieve active event keys message to the remote transfer server over a secure transport logical connection established over the open network, the retrieve active event keys message comprising the session ID;

iv) obtaining an event key value from the remote transfer server in response to the retrieve active event keys message;

v) sending a read event message to the remote transfer server over a secure transport protocol logical connection established over the open network, the read event message including the session ID, and the event key value;

vi) obtaining an XML file comprising event parameters from the remote transfer server in response to the read event message, the event parameters of the XML file comprise a file name identifying a name of a file to be downloaded, a directory path parameter identifying the download directory to which the file is to be stored by the transfer client system, a profile ID identifying data to be retrieved by the transfer server, and extract rules defining formatting of retrieved data to a defined file format;

vii) sending a create binary large object message to the remote transfer server over a secure transport protocol logical connection established over the open network, the create binary large object message comprising the session ID, the profile ID identifying the data to be retrieved by the transfer server, and the extract rules defining formatting of the retrieved data to the defined file format;

viii) receiving a class value from the remote transfer server in response to the create binary large object message, the class value identifying a type of data in a binary large object;

ix) sending a check for available binary large object message to the remote transfer server, the check for available binary large object message comprising the session ID and the class value;

x) receiving a binary large object ID from the remote transfer server in response to the check for available binary large object message, the binary large object ID identifying a binary large object being a file in the defined file format and including the retrieved data;

xi) sending a download message to the remote transfer server over a secure transport protocol logical connection established over the open network, the file download message comprising the session ID and the binary large object ID; and

xii) receiving a message from the remote transfer server containing the binary object in response to the download message; and

xiii) storing the binary object as a file in the download directory with the file name.

2. The transfer client system of claim 1, wherein:

the event parameters further include a printer ID value associated with a printer available to the transfer client; and

the transfer client further provides for sending the file to the printer associated with the printer ID value.

3. A transfer client system for exchanging files with a transfer server over an open network, the transfer client system comprising:

a download directory for storing binary objects obtained from a transfer client server for subsequent retrieval by a local data processing system;

an authentication registry securely storing authentication credentials;

a transfer client comprising;

an authentication process for;

sending a log-on message to a remote transfer server over a secure transport protocol logical connection established over the open network, the log-on message including the authentication credentials;

obtaining a session ID from the remote transfer server in response to the log-on message;

sending a retrieve active event keys message to the remote transfer server over a secure transport logical connection established over the open network, the retrieve active event keys message comprising the session ID;

obtaining an event key value from the remote transfer server in response to the retrieve active event keys message;

sending a read event message to the remote transfer server over a secure transport protocol logical connection established over the open network, the read event message including the session ID and the event key value;

obtaining an XML file comprising event parameters from the remote transfer server in response to the read event message, the event parameters of the XML file comprising a file name identifying a name of a file to be downloaded, a directory path parameter identifying the download directory to which the file is to be stored by the transfer client system, a profile ID identifying data to be retrieved by the transfer server, and extract rules defining formatting of retrieved data to a defined file format;

a download process spawned in response to receiving the event parameters, the download process providing for;

sending a create binary large object message to the remote transfer server over a secure transport protocol logical connection established over the open network, the create binary large object message comprising the session ID, the profile ID identifying the data to be retrieved by the transfer server, and the extract rules defining formatting of the retrieved data to the defined file format;

receiving a class value from the remote transfer server in response to the create binary large object message, the class value identifying a type of data in the binary large object;

sending a check for available binary large object message to the remote transfer server, the check for available binary large object message comprising the session ID and the class value;

receiving a binary large object ID from the remote transfer server in response to the check for available binary large object message, the binary large object ID identifying a binary large object being a file in the defined file format and including the retrieved data;

sending a download message to the remote transfer server over a secure transport protocol logical connection established over the open network, the download message comprising the session ID and the binary large object ID; and

receiving a message from the remote transfer server containing the binary object in response to the file download message; and

storing the binary object as a file in the download directory with the file name.

4. The transfer client system of claim 3, wherein:

the event parameters further include a printer ID value associated with a printer available to the transfer client; and

the download process further provides for sending the file to the printer associated with the printer ID value.

5. A method of operating a transfer client system for exchanging files with a transfer server over an open network, the method comprising:

i) sending a log-on message to a remote transfer server over a secure transport protocol logical connection established over the open network, the log-on message including authentication credentials retrieved from a secure authentication registry;

ii) obtaining a session ID from the remote transfer server in response to the log-on message;

iii) sending a retrieve active event keys message to the remote transfer server over a secure transport logical connection established over the open network, the retrieve active event keys message comprising the session ID;

iv) obtaining an event key value from the remote transfer server in response to the retrieve active event keys message;

v) sending a read event message to the remote transfer server over a secure transport protocol logical connection established over the open network, the read event message including the session ID and the event key value;

vi) obtaining an XML file comprising event parameters from the remote transfer server in response to the read event message, the event parameters of the xml file comprising a file name identifying a name of a file to be downloaded, a directory path parameter identifying the download directory to which the file is to be stored by the transfer client system, a profile ID identifying data to be retrieved by the transfer server, and extract rules defining formatting of retrieved data to a defined file format;

vii) sending a create binary large object message to the remote transfer server over a secure transport protocol logical connection established over the open network, the create binary large object message comprising the session ID, the profile ID identifying the data to be retrieved by the transfer server, and the extract rules defining formatting of the retrieved data to the defined file format;

viii) receiving a class value from the remote transfer server in response to the create binary large object message, the class value identifying a type of data in the binary large object;

ix) sending a check for available binary large object message to the remote transfer server, the check for available binary large object message comprising the session ID and the class value;

x) receiving a binary large object ID from the remote transfer server in response to the check for available binary large object message, the binary large object ID identifying a binary large object being a file in the defined file format and including the retrieved data;

xi) sending a download message to the remote transfer server over a secure transport protocol logical connection established over the open network, the download message comprising the session ID and the binary large object ID; and

xii) receiving a message from the remote transfer server containing the binary object in response to the download message; and

xiii) storing the binary object as a file in the download directory with the file name.

6. The method of claim 5, wherein:

the event parameters further include a printer ID value associated with a printer available to the transfer client;

and the method further comprises sending the file to the printer associated with the printer ID value.