WikiPatents - Community Patent Review
Create Free Account  |  License or Sell Your Patent  |  WikiPatents Marketplace  |  WikiPatents Blog
Username:  Password:  
    
Advanced Search
Systems and methods for automatically sharing information among remote/mobile nodes    
United States Patent5664207   
Link to this pagehttp://www.wikipatents.com/5664207.html
Inventor(s)Crumpler; Dennis M. (Atlanta, GA); Estes; Robert B. (Atlanta, GA); Jackson, Jr.; Kirby Bryan (Decatur, GA)
AbstractInformation is automatically shared among a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to a data processing server by distributing an information form to users corresponding to first remote/mobile nodes. A user may complete the form to create an instance of the form and define an instance distribution list. The instance is automatically distributed to users corresponding to the distribution list. As owner of the form, the user may also modify the form, and these modifications are also automatically distributed to the users at the third node. A second form may be linked to the form and automatically distributed to the third nodes as well. When distributing a file to a node, any other files which are required are also automatically distributed.
   














 Title Information Submit all comments and votes
 
Patent Text Patent PDF Print Page Summary File History
Plain text PDF images Print Summary File History
Drawing from US Patent 5664207
Systems and methods for automatically sharing information among

     remote/mobile nodes - US Patent 5664207 Drawing
Systems and methods for automatically sharing information among remote/mobile nodes
Inventor     Crumpler; Dennis M. (Atlanta, GA); Estes; Robert B. (Atlanta, GA); Jackson, Jr.; Kirby Bryan (Decatur, GA)
Owner/Assignee     XcelleNet, Inc. (Atlanta, GA)
Patent assignment
All assignments
Publication Date     September 2, 1997
Application Number     08/358,106
PAIR File History     Application Data   Transaction History
Image File Wrapper   Patent Term   Fees
Litigation
Filing Date     December 16, 1994
US Classification     715/505 705/3 707/9 709/219 709/227 715/733 715/751
Int'l Classification     G06F 017/30 766 767 768 770
Examiner     Black; Thomas G.
Assistant Examiner     Alam; Hosain T.
Attorney/Law Firm     Bell, Seltzer, Park & Gibson, P.A.
Address
Parent Case    
Priority Data    
USPTO Field of Search     395/600 395/610 395/617 395/209 395/216 395/221 395/331 395/332 395/202 395/203 395/608 395/609 395/200.03 395/200.19 395/200.02 395/200.08
Patent Tags     methods automatically sharing information among remote/mobile nodes
   
Enter a comma (,) or semicolon (;) between multiple tag words/phrases.
Describe this patent:
 Amusing   
 Clever   
 Complex   
 Efficient   
 Historic   
 Important   
 Innovative   
 Interesting   
 Practical   
 Simple   
[no votes]
Patent WIKI

Share information and news about this patent, including information and news about the technology, inventors, company, ligation and licensing.

 References Submit all comments and votes
 
*references marked with an asterisk below are user-added references
 U.S. References
 
Add a new US reference:  
ReferenceRelevancyCommentsReferenceRelevancyComments
5513126
Harkins
709/228
Apr,1996

[0 after 0 votes]
5495610
Shing
709/221
Feb,1996

[0 after 0 votes]
5493692
Theimer
455/26.1
Feb,1996

[0 after 0 votes]
5319543
Wilhelm
705/3
Jun,1994

[0 after 0 votes]
5077666
Brimm

Dec,1991

[0 after 0 votes]
 Foreign References
 Other References
 Market Review Submit all comments and votes
   
Market Size
Estimate the gross annual revenues of the relevant market sector:
> $10B
$5B - $10B
$2B - $5B
$500M - $2B
$100M - $500M
$10M - $100M
$1M - $10M
$500K - $1M
$100K - $500K
< $100K
[No votes]
$0
 
$0   $2.5B   $5B   $7.5B   $10B
Market Share
Estimate the percentage of the relevant market sector this invention will capture:
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Reasonable Royalty
What percentage of gross sales should the inventor or assignee be paid?
75% - 100%
50% - 74.99%
25% - 49.99%
10 - 24.99%
5 - 9.99%
2 - 4.99%
1 - 1.99%
< 1%
[No votes]
0.0%
 
0%   25%   50%   75%   100%
Public's "Guesstimation" of Royalty Value
Market SizeN/A[No votes]
xMarket ShareN/A[No votes]
xReasonable RoyaltyN/A[No votes]

N/A

License Availablity
If you are NOT the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
License Availablity
If you ARE the owner or assignee, answer here:
Yes, license is available for purchase

No, license is not currently available



[No votes]
Competitive Advantage
Does this invention have a significant competitive advantage over similar technologies?
Yes

No



[No votes]
Most helpful competitive advantage comment
[No comments]

Commercial Alternatives
Are there viable commercial alternatives for this invention?
Yes

No



[No votes]
Most helpful commercial alternative comment
[No comments]

 Technical Review Submit all comments and votes
 Claims Submit all comments and votes
 


That which is claimed:

1. A method for automatically sharing information among a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to a data processing server for communication therebetween, said automatic information sharing method comprising the steps of:

placing an information form for entering information from a user at a remote/mobile data processing node, on said server;

identifying said form as being sharable;

assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said form to said at least one node of said first remote/mobile nodes, in response to establishment of the remote/mobile communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said form at a second remote mobile node selected from said first remote/mobile nodes to thereby create an instance of said form at said second remote/mobile node;

assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes selected from said first remote/mobile nodes;

establishing a remote/mobile communications link between said second node and said server;

automatically transferring said instance of said form to said server, in response to establishment of the remote/mobile link between said second node and said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

2. An automatic information sharing method according to claim 1 further comprising the steps of:

placing a second information form for entering information from a user at a remote/mobile data processing node, on said server;

linking said second information form to said information form;

assigning said form distribution list to said second form to identify said users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said second form to said at least one node of said first remote/mobile nodes, in response to establishment of the remote/mobile communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said second form at a fourth remote mobile node selected from said third remote/mobile nodes to thereby create an instance of said second form at said fourth remote/mobile node;

establishing a remote/mobile communications link between said fourth remote/mobile node and said server;

automatically transferring said instance of said second form to said server, in response to establishment of said remote/mobile communications link between said fourth remote/mobile node and said server;

disconnecting said remote/mobile communications link between said fourth remote/mobile node and said server;

establishing remote/mobile communications links between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance of said second form from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

3. An automatic information sharing method according to claim 1:

wherein said step of assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes is performed at said server;

wherein said step of assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes is performed at said second node; and

wherein said step of transferring said instance of said form to said server further comprises the step of transferring said instance distribution list to said server.

4. An automatic information sharing method according to claim 2 wherein said step of creating an instance of said second form at a fourth remote/mobile node comprises the steps of:

viewing said instance of said form at said fourth remote/mobile node;

launching said instance of said second form at said fourth remote/mobile node; and

completing said instance of said second form at said fourth remote/mobile node.

5. An automatic information sharing method according to claim 1 further comprising the steps of:

modifying said instance of said form at said second remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

6. An automatic information sharing method according to claim 5 further comprising the step of:

replacing corresponding information in said instance of said form at said third remote/mobile nodes with the modifications.

7. An automatic information sharing method according to claim 5 wherein said step of transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said second remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said second remote/mobile node.

8. An automatic information sharing method according to claim 2 further comprising the steps of:

modifying said instance of said second form at said fourth remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

9. An automatic information sharing method according to claim 8 further comprising the step of:

replacing corresponding information in said instance of said second form at said third remote/mobile nodes with the modifications.

10. An automatic information sharing method according to claim 8 wherein said step of automatically transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said fourth remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said fourth remote/mobile node.

11. An automatic information sharing method according to claim 1 wherein said step of automatically transferring said form to at least one node of said first remote/mobile nodes comprises the steps of:

identifying files which are required in order to use said form;

probing said at least one node of said first nodes in order to determine if the identified files are present at said at least node one of said first remote/mobile nodes; and

automatically transferring the identified files from said server to said at least one node of said first remote/mobile nodes if the identified files are not present at said at least one node of said first remote/mobile nodes.

12. A method for automatically sharing information among a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to a data processing server for communication therebetween, said automatic information sharing method comprising the steps of:

placing an information form for entering information from a user at a remote/mobile data processing node, on said server;

identifying said form as being sharable;

assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said form to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said form at a second remote/mobile node selected from said first remote/mobile nodes to thereby create an instance of said form at said second remote/mobile node;

assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes selected from said first remote/mobile nodes;

establishing a remote/mobile communications link between said second node and said server;

automatically transferring said instance of said form to said server, in response to establishment of the remote/mobile communications link between said second node and said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes;

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes;

modifying said instance of said form at said second remote/mobile node;

establishing a remote/mobile communications link between said second node and said server;

transmitting the modifications to said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transmitting the modifications from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

13. An automatic information sharing method according to claim 12 further comprising the steps of:

placing a second information form for entering information from a user at a remote/mobile data processing node, on said server;

linking said second information form to said information form;

assigning said form distribution list to said second form to identify said users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said second form to said at least one node of said first remote/mobile nodes, in response to establishment of the communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said second form at a fourth remote/mobile node selected from said third remote/mobile nodes to thereby create an instance of said second form at said fourth remote/mobile node;

establishing a remote/mobile communications link between said fourth remote/mobile node and said server;

automatically transferring said instance of said second form to said server, in response to establishment of the remote/mobile communications link between said fourth remote/mobile node and said server;

disconnecting said remote/mobile communications link between said fourth remote/mobile node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance of said second form from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes.

14. An automatic information sharing method according to claim 12:

wherein said step of assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes is performed at said server;

wherein said step of assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes is performed at said second node; and

wherein said step of transferring said instance of said form to said server further comprises the step of transferring said instance distribution list to said server.

15. An automatic information sharing method according to claim 13 wherein said step of creating an instance of said second form at a fourth remote/mobile node comprises the steps of:

viewing said instance of said form at said fourth remote/mobile node;

launching said instance of said second form at said fourth remote/mobile node; and

completing said instance of said second form at said fourth remote/mobile node.

16. An automatic information sharing method according to claim 12 further comprising the step of:

replacing corresponding information in said instance of said form at said at least one node of said third remote/mobile nodes with the modifications.

17. An automatic information sharing method according to claim 12 wherein said step of automatically transmitting the modifications from said server to said at least one node of said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said second remote/mobile node; and

transmitting the modifications to said at least one node of said third remote/mobile nodes only if the modifications originated from said second remote/mobile node.

18. An automatic information sharing method according to claim 13 further comprising the steps of:

modifying said instance of said second form at said fourth remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

19. An automatic information sharing method according to claim 18 further comprising the step of:

replacing corresponding information in said instance of said second form at said third remote/mobile nodes with the modifications.

20. An automatic information sharing method according to claim 18 wherein said step of automatically transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said fourth remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said fourth remote/mobile node.

21. An automatic information sharing method according to claim 12 wherein said step of transferring said form to at least one of said first remote/mobile nodes comprises the steps of:

identifying files which are required in order to use said form;

probing said at least one of said first nodes in order to determine if the identified files are present at said at least one of said first remote/mobile nodes; and

transferring the identified files from said server to said at least one of said first remote/mobile nodes if the identified files are not present at said at least one of said first remote/mobile nodes.

22. A computer program storage device which tangibly embodies a program of instructions executable on a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to a data processing server for communication therebetween, to perform a method for automatically sharing information among the plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to the data processing server for communication therebetween, said automatic information sharing method comprising the steps of:

placing an information form for entering information from a user at a remote/mobile data processing node, on said server;

identifying said form as being sharable;

assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said form to said at least one node of said first remote/mobile nodes, in response to establishment of the remote/mobile communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said form at a second remote mobile node selected from said first remote/mobile nodes to thereby create an instance of said form at said second remote/mobile node;

assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes selected from said first remote/mobile nodes;

establishing a remote/mobile communications link between said second node and said server;

automatically transferring said instance of said form to said server, in response to establishment of the remote/mobile link between said second node and said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

23. A computer program storage device according to claim 2 wherein said method further comprises the steps of:

placing a second information form for entering information from a user at a remote/mobile data processing node, on said server;

linking said second information form to said information form;

assigning said form distribution list to said second form to identify said users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said second form to said at least one node of said first remote/mobile nodes, in response to establishment of the remote/mobile communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said second form at a fourth remote mobile node selected from said third remote/mobile nodes to thereby create an instance of said second format said fourth remote/mobile node;

establishing a remote/mobile communications link between said fourth remote/mobile node and said server;

automatically transferring said instance of said second form to said server, in response to establishment of said remote/mobile communications link between said fourth remote/mobile node and said server;

disconnecting said remote/mobile communications link between said fourth remote/mobile node and said server;

establishing remote/mobile communications links between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance of said second form from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

24. A computer program storage device according to claim 22:

wherein said step of assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes is performed at said server;

wherein said step of assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes is performed at said second node; and

wherein said step of transferring said instance of said form to said server further comprises the step of transferring said instance distribution list to said server.

25. A computer program storage device according to claim 23 wherein said step of creating an instance of said second form at a fourth remote/mobile node comprises the steps of:

viewing said instance of said form at said fourth remote/mobile node;

launching said instance of said second form at said fourth remote/mobile node; and

completing said instance of said second form at said fourth remote/mobile node.

26. A computer program storage device according to claim 22 wherein said method further comprises the steps of:

modifying said instance of said form at said second remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

27. A computer program storage device according to claim 26 wherein said method further comprises the step of:

replacing corresponding information in said instance of said form at said third remote/mobile nodes with the modifications.

28. A computer program storage device according to claim 26 wherein said step of transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said second remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said second remote/mobile node.

29. A computer program storage device according to claim 23 wherein said method further comprises the steps of:

modifying said instance of said second form at said fourth remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

30. A computer program storage device according to claim 29 wherein said method further comprises the step of:

replacing corresponding information in said instance of said second form at said third remote/mobile nodes with the modifications.

31. A computer program storage device according to claim 29 wherein said step of automatically transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said fourth remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said fourth remote/mobile node.

32. A computer program storage device according to claim 22 wherein said step of automatically transferring said form to at least one node of said first remote/mobile nodes comprises the steps of:

identifying files which are required in order to use said form;

probing said at least one node of said first nodes in order to determine if the identified files are present at said at least node one of said first remote/mobile nodes; and

automatically transferring the identified files from said server to said at least one node of said first remote/mobile nodes if the identified files are not present at said at least one node of said first remote/mobile nodes.

33. A computer program storage device which tangibly embodies a program of instructions executable on a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to a data processing server for communication therebetween, to perform a method for automatically sharing information among the plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to the data processing server for communication therebetween, said automatic information sharing method comprising the steps of:

placing an information form for entering information from a user at a remote/mobile data processing node, on said server;

identifying said form as being sharable;

assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said form to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said form at a second remote/mobile node selected from said first remote/mobile nodes to thereby create an instance of said form at said second remote/mobile node;

assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes selected from said first remote/mobile nodes;

establishing a remote/mobile communications link between said second node and said server;

automatically transferring said instance of said form to said server, in response to establishment of the remote/mobile communications link between said second node and said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes;

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes;

modifying said instance of said form at said second remote/mobile node;

establishing a remote/mobile communications link between said second node and said server;

transmitting the modifications to said server;

disconnecting said remote/mobile communications link between said second node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transmitting the modifications from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications links between said server and said at least one node of said third remote/mobile nodes.

34. A computer program storage device according to claim 33 wherein said method further comprises the steps of:

placing a second information form for entering information from a user at a remote/mobile data processing node, on said server;

linking said second information form to said information form;

assigning said form distribution list to said second form to identify said users corresponding to first remote/mobile nodes;

establishing a remote/mobile communications link to at least one node of said first remote/mobile nodes;

automatically transferring said second form to said at least one node of said first remote/mobile nodes, in response to establishment of the communications link to said at least one node of said first remote/mobile nodes;

disconnecting said remote/mobile communications link from said at least one node of said first remote/mobile nodes;

accepting user entry of information into said second form at a fourth remote/mobile node selected from said third remote/mobile nodes to thereby create an instance of said second form at said fourth remote/mobile node;

establishing a remote/mobile communications link between said fourth remote/mobile node and said server;

automatically transferring said instance of said second form to said server, in response to establishment of the remote/mobile communications link between said fourth remote/mobile node and said server;

disconnecting said remote/mobile communications link between said fourth remote/mobile node and said server;

establishing a remote/mobile communications link between said server and at least one node of said third remote/mobile nodes;

automatically transferring said instance of said second form from said server to said at least one node of said third remote/mobile nodes, in response to establishment of the remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes; and

disconnecting said remote/mobile communications link between said server and said at least one node of said third remote/mobile nodes.

35. A computer program storage device according to claim 33:

wherein said step of assigning a form distribution list to said form to identify users corresponding to first remote/mobile nodes is performed at said server;

wherein said step of assigning an instance distribution list to said instance of said form to identify users corresponding to third remote/mobile nodes is performed at said second node; and

wherein said step of transferring said instance of said form to said server further comprises the step of transferring said instance distribution list to said server.

36. A computer program storage device according to claim 34 wherein said step of creating an instance of said second form at a fourth remote/mobile node comprises the steps of:

viewing said instance of said form at said fourth remote/mobile node;

launching said instance of said second form at said fourth remote/mobile node; and

completing said instance of said second form at said fourth remote/mobile node.

37. A computer program storage device according to claim 33 wherein said method further comprises the step of:

replacing corresponding information in said instance of said form at said at least one node of said third remote/mobile nodes with the modifications.

38. A computer program storage device according to claim 33 wherein said step of automatically transmitting the modifications from said server to said at least one node of said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said second remote/mobile node; and

transmitting the modifications to said at least one node of said third remote/mobile nodes only if the modifications originated from said second remote/mobile node.

39. A computer program storage device according to claim 34 wherein said method further comprises the steps of:

modifying said instance of said second form at said fourth remote/mobile node;

transmitting the modifications to said server; and

transmitting the modifications from said server to said third remote/mobile nodes.

40. A computer program storage device according to claim 39 wherein said method further comprises the step of:

replacing corresponding information in said instance of said second form at said third remote/mobile nodes with the modifications.

41. A computer program storage device according to claim 39 wherein said step of automatically transmitting the modifications from said server to said third remote/mobile nodes comprises the steps of:

determining whether said modifications originated from said fourth remote/mobile node; and

transmitting the modifications to said third remote/mobile nodes only if the modifications originated from said fourth remote/mobile node.

42. A computer program storage device according to claim 33 wherein said step of transferring said form to at least one of said first remote/mobile nodes comprises the steps of:

identifying files which are required in order to use said form;

probing said at least one of said first nodes in order to determine if the identified files are present at said at least one of said first remote/mobile nodes; and

transferring the identified files from said server to said at least one of said first remote/mobile nodes if the identified files are not present at said at least one of said first remote/mobile nodes.
 Description Submit all comments and votes
 


FIELD OF THE INVENTION

This invention relates to data processing systems and methods and more particularly to systems and methods for linking a plurality of data processing systems for communication therebetween.

BACKGROUND OF THE INVENTION

Since the early days of computing, data processing systems have been linked to users via communications networks. Initially, a host or mainframe computer was linked to user terminals. With the advent of the personal computer, "intelligent workstations" have been linked to host computers.

As more and more computing systems have become personal computer based, personal computers have been linked into Local Area Networks (LAN) which are managed by a server to provide client/server applications. These client/server networks can also be linked to mainframe and other computers.

Traditional LAN-based client/server networks, and most other computer networks, assume a near-ideal operating environment. In particular, LANs assume continuously connected users who are computer literate. Since the LAN connections between computers are hard wired, error-free reliable connections are assumed. Thus, the LAN-based client/server environment allows knowledge-workers and PC professionals to operate in a near ideal environment.

Unfortunately, traditional LAN-based client/server networks poorly serve the needs of important classes of users, referred to herein as "remote/mobile" users. As used herein, "remote/mobile" means "temporarily and intermittently linked", wherein temporarily means "lasting for a limited time" and intermittently means "coming and going at intervals, not continuous, or occasional". An example of remote/mobile users is point-of-sale terminals in a chain of, for example, 5,000 retail stores, where each point-of-sale terminal needs to connect to the headquarters central computer for short periods of time for communication therebetween, rather than continuously. Another example of remote/mobile users is a mobile sales force which typically uses laptop computers and connects with the home office for short periods of time from various locations, such as hotels, customer sites or cars.

Users of remote/mobile computers, such as laptop and notebook computers, point-of-sale systems, personal computers, personal digital assistants and the like are typically "transactional" workers rather than knowledge workers, and are not typically PC literate. They need to link to a central office on a temporary and intermittent basis to obtain information from the central office or to transfer information to the central office. The connections between the remote/mobile node and the data processing server may use switched wire or wireless connections. Accordingly, communications tend to be slow and unreliable.

Traditional LAN-based client/server systems have attempted to meet the needs of remote/mobile users by allowing remote dial-in to the LAN. However, remote dial-in has heretofore worked effectively only for small numbers of remote/mobile users, and has used a LAN-based paradigm which is not amenable to the unique requirements of the remote/mobile user.

A major breakthrough in remote/mobile computing was provided with the introduction of RemoteWear versions 1.0-1.4 by XcelleNet, Inc., Atlanta, Ga., assignee of the present invention. The RemoteWare systems provided a communication model which was specifically geared to remote/mobile environments. One or more RemoteWare servers can be connected to a LAN to control the exchange of information between a central site and hundreds or thousands of remote/mobile computers and their users and applications. The RemoteWare server provides information management, resource management, scheduling, communication services, information monitoring and control services needed by large numbers of remote/mobile users who are temporarily and intermittently linked to the remote/mobile network.

Communications between the server and the remote/mobile nodes are designed to keep connect time at a minimum. Thus, the connection cost is minimized and the time that the transactional worker needs to spend connected to the central system are minimized. Moreover, the system is designed to support low bandwidth and unreliable connections.

RemoteWare Versions 1.0-1.4 include an application which provides a remote transactional management system. The remote transactional management system, designated as "RemoteWare FORMS" includes a forms editor which is used to create forms with graphics, fields, text and bitmaps. Once completed, the form becomes an application that can be assigned to a remote/mobile users desktop. Once the form is assigned to a user's desktop, the system sends the form to the users to whom that user desktop is assigned. A forms node program displays the form at the node. The node user enters the required information on the form. The node user then posts the completed form which is automatically sent to the RemoteWare server. If routing has been enabled for the form, the user may forward a data set to another user and sends copies to others via a messaging service. The data may be viewed in the context of the form in which it was entered, and may be printed. The RemoteWare FORMS system is described in a publication entitled "RemoteWare FORMS and RemoteWare QUERY Reference Manual, Software Release 1.3", Copyright 1993, XcelleNet, Inc.

Notwithstanding the ability to create and route forms to remote/mobile users which was provided with the introduction of RemoteWare Version 1.0-1.4, there continues to be a need to provide improved methods and systems for automatically sharing information among users of remote/mobile computers.

SUMMARY OF THE INVENTION

The invention provides methods and systems for automatically sharing information among remote/mobile users. Many business processes require automatic sharing of information among large numbers of remote/mobile users. For example, a remote/mobile sales or service force may need access to a customer profile for a particular customer. The customer profile may need to be updated with address changes and other changes, an