Michael A Greene

US Patent:

6421673, Jul 16, 2002

Filed:

Dec 13, 1999

Appl. No.:

09/459734

Inventors:

R. Russell Caldwell - Atlanta GA
Michael C. Merrill - Marietta GA
Michael L. Greene - Dunwoody GA
Roy G. Wells - Griffin GA

Assignee:

Novient, Inc. - Atlanta GA

International Classification:

G06F 1730

US Classification:

707 10, 707513, 707529

Abstract:

A disclosed method includes mapping at least one local application module to respective message type data, and storing the message type data in association with the local application module in a local database accessible to a local server. The method includes mapping gateway account data for internetwork access to at least one remote database, to respective message type data. The first method further includes storing the message type data in association with respective gateway account data in the local database, mapping remote attribute data to local attribute data, and storing the remote attribute data in association with the local attribute data in the local database. Similar steps can be used to prepare the remote server and database for operation. Using the local client device a user can generate message type data transmitted from the local client device to the local server that determines whether the received message type data is associated with a local application module. If so, the local server runs the local application module using optional attribute data.

US Patent:

20020046286, Apr 18, 2002

Filed:

Dec 13, 2000

Appl. No.:

09/738916

Inventors:

R. Caldwell - Atlanta GA, US
Michael Merrill - Marietta GA, US
Michael Greene - Atlanta GA, US
Roy Wells - Atlanta GA, US
Arnshea Clayton - Atlanta GA, US

International Classification:

G06F015/16

US Classification:

709/229000

Abstract:

A disclosed method includes mapping data identifying at least one first application module to respective message type data, and storing the message type data in association with the data identifying the first application module in a first database accessible to a first server. The method includes mapping universal resource locator for internetwork access to at least one second server, to respective message type data. The first method further includes storing the message type data in association with a respective universal resource locator in the first database, mapping second attribute data to first attribute data, and storing the second attribute data in association with the first attribute data in the first database. Similar steps can be used to prepare the second server and database for operation. Using the first client device a user can generate message type data transmitted from the first client device to the first server that determines whether the received message type data is associated with a first application module. If so, the first server runs the first application module using optional attribute data. The first server also determines whether the received message type data is associated with universal resource locator. If so, the universal resource locator is used to transmit the message type data from the first server over the internetwork to the second server. The second server determines whether the message type data is mapped to a second application module in the second database. If so, the second server runs a second application module corresponding to the message type data.