WO1996017461A1

WO1996017461A1 - Methods and systems for delivering files from a server to remote/mobile nodes

Info

Publication number: WO1996017461A1
Application number: PCT/US1995/014494
Authority: WO
Inventors: Rebecca M. Lever; Dennis M. Crumpler
Original assignee: Xcellenet, Inc.
Priority date: 1994-12-02
Filing date: 1995-11-21
Publication date: 1996-06-06
Also published as: AU4501296A

Abstract

Essential files are delivered from a data processing server to selected remote/mobile nodes while reducing the connection time of the remote/mobile links between the server and the nodes. Selected files in a listing of files which are deliverable by the server to the nodes during remote/mobile communications, may be identified as being forced or requestable, requestable individually or requestable by group, and/or archived. Forced files are automatically delivered to a node in response to establishment of a remote/mobile communications link between the node and the server, while requestable files are only delivered upon receipt of a request at the server. A file which is requestable individually is delivered upon establishment of a remote/mobile communications link between the server and the node upon receipt of a request at the server to deliver the individually requestable files. If a request is made to deliver a file which is only requestable by group, the requested file and all files which are members of the group which includes a requested file are delivered. For archived files, selected archive copies of a file, or all archive copies of a file, are delivered upon request. The above aspects may be used individually or in combination to ensure delivery of essential files while minimizing connection time of remote/mobile communications.

Description

METHODS AND SYSTEMS FOR DELIVERING FILES FROM A SERVER TO REMOTE/MOBILE NODES

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 a switched wire or wireless connection.

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 RemoteWare Versions 1.0-1.4 by XcelleNet , Inc., Atlanta, Georgia, 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 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. Accordingly, the RemoteWare software architecture was designed specifically for remote/mobile user access to mission critical enterprise-wide transaction processing client/server systems.

XcelleNet RemoteWare Version 1.4 includes a "subscriber" application which simplifies the task of delivering information and applications to remote/mobile nodes. The subscriber application allows remote/mobile users to request, view, print, search and run information and applications from a list which is defined and managed at the server. Accordingly, timely access to frequently changing information, such as sales results, profit and loss statements, inventory status or commission reports is provided. Once the files have been delivered, remote/mobile users can access, view, print, search, copy and scroll through the information and applications. Any updates or changes are automatically available. In particular, remote/mobile users mark files on their subscriber list to be automatically downloaded the next time a remote/mobile communication session takes place. Remote/mobile users can also retrieve files immediately, without waiting for a centrally initiated communications session.

With the subscriber application, a system administrator controls which information and applications remote/mobile users can access by creating a list of files. Files can be marked as printable or viewable by the remote/mobile user. Critical information and applications can be placed in files tagged for automatic distribution to remote sites during an Electronic Software Distribution (ESD) session. The subscriber application of XcelleNet RemoteWare Version 1.4 is described in publications entitled "RemoteWare SUBSCRIBER User ' s Guide Software Rel ease 1 . 2 " and "RemoteWare SUBSCRIBER Installa tion and Administra tor' s Guide" , both Copyright 1993, XcelleNet, Inc., the disclosures of which are hereby incorporated herein by reference.

Notwithstanding the improvement in remote/mobile communications which is provided by the XcelleNet RemoteWare Version 1.4 subscriber application, there is a continued need to ensure delivery of essential files from the server to the remote/mobile nodes, while reducing the amount of remote/mobile connection time which is required for these file deliveries.

Summary of the Invention

The invention ensures delivery of essential files from the server to the remote/mobile nodes while reducing connection time of the remote/mobile links by providing three related file transfer aspects. In a first aspect of the invention, selected files in a listing of files which are deliverable by the server to the nodes during remote/mobile communications, may be identified as being "forced" or "requestable". The "forced" files are automatically delivered to a node in response to establishment of a remote/mobile communications link between the node and the server. The "requestable" files are only delivered in response to establishment of a remote/mobile communications link and receipt of a request at the server to deliver the selected files which are identified as requestable. Thus, the system administrator can ensure that essential files are delivered to a remote/mobile node while the remote/mobile node user has control over the delivery of nonessential files.

According to a second aspect of the invention, files in the list may also be identified by the administrator as either "requestable individually" or "requestable by group" . A file which is requestable individually is delivered from the server to the node in response to establishment of a remote/mobile communications link between the node and the server, and receipt of a request at the server to deliver the individually requestable file. In contrast, if a request is made to deliver a file which is only requestable by group, the requested file and all files which are members of the group which include the requested file are delivered in response to establishment of remote/mobile communications link between the node and the server. Thus, the system administrator can ensure that if the user selects a particular file, all files which the administrator wants the user to view in conjunction with the selected file, and all ancillary files which are required for operation of the given file, are also provided to the user. The group of files may be automatically delivered in response to selection by the remote/mobile node of any file in the group. Alternatively, an option may be provided upon selection of an individual file in the group to inform the user of the node that all files in the group will be delivered if the individual file is selected, and to request user confirmation of the request to deliver all files in the group.

According to a third aspect of the present invention, archive copies of files may also be saved by the administrator and requested by a user. Archive copies are older versions of a file. For example, a file may be a newsletter which is updated and revised monthly. Since there may be information in each of the newsletter issues which the user of the remote/mobile node might need to access, the administrator may choose to archive this file and to maintain a maximum of twelve "back issues" (archived versions) of the file. Accordingly, selected files from the listing of files may be identified as archived, and a number of archive copies for each of the archive files may be selected. When the file listing is delivered to the nodes, the file listing includes an identification of those files which are archived and the number of archived copies. A user at the node can then select to obtain the file, a particular archived copy of the file, or all archived copies of the file upon establishment of a remote/mobile communications link between the remote/mobile node and the server. Thus, only those archived copies of a file which are desired by a user are delivered during remote/mobile communications.

Each of the above described aspects of the present invention may be utilized individually to ensure delivery of essential files while reducing connection time of remote/mobile communications. However, preferably, the "forced/requestable" , "individual/group requestable" and "archived" aspects are used in combination to provide delivery of essential files while reducing remote/mobile communication time. Brief Description of the Drawings Figure 1 is a block diagram of a known remote/mobile communications system with which the present invention may be used. Figure 2 is a flowchart which illustrates operations performed at a server prior to establishing a remote/mobile link according to the present invention.

Figures 3A - 3B are a flowchart illustrating operations performed at a remote/mobile node prior to and during remote/mobile communications according to the present invention.

Detailed Description of Preferred Embodiments

The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout . Referring now to Figure 1, a remote/mobile communication system in which the present invention may be practiced is illustrated. As shown in Figure 1, remote/mobile communication system 100 includes a local area network (LAN) 102. Mainframe computer 104, LAN workstations 106, a LAN file server 108 and a LAN database 112 are provided and interconnected in a manner well known to those having skill in the art.

In order to provide remote/mobile communications, one or more remote/mobile servers 110 are attached to the LAN 102. Each remote/mobile server may be a personal computer running in the OS/2 operating environment and which runs RemoteWare Versions 1.0-1.4 marketed by the assignee of the present invention. RemoteWare Versions 1.0-1.4 act as the control point for information management, providing the resource management, scheduling, communication services, information monitoring and control services needed by the remote/mobile network. RemoteWare Version 1.4 is described in a manual entitled "RemoteWare SERVER Opera tions Guide, Sof tware Rel ease 1 . 4 " , Copyright 1992, XcelleNet, Inc., the disclosure of which is hereby incorporated herein by reference. Remote/mobile servers 110 are linked to a remote/mobile communications network 120. Remote/mobile communications network 120 includes various wire line connections such as switched analog, ISDN, and X.25 or wireless connections such as switched and digital cellular, satellite and radio frequency. Although leased lines and other permanent communication lines may also be used, these are not preferred due to their high cost.

A large number (typically hundreds or thousands) of remote/mobile data processing nodes 116a- 116f are connected to remote/mobile communications network 120. Each remote/mobile data processing node, also referred to herein as a "node", includes a data processing unit which is temporarily and intermittently linked to server 110. Nodes 116 may include laptop computers 116a, personal computers 116b, Macintosh computers 116c, point-of-sale systems 116d, pen-based systems 116e and other remote LANs 116f. It will be understood by those having skill in the art that remote/mobile data processing nodes 116 may include any microprocessor driven units such as cellular telephones, personal digital assistants and other workstations and terminals. Each node 116 preferably runs a node software program in background, and which operates in conjunction with the remote/mobile server 110. The node software initiates or responds to communications sessions, supports interactive remote console sessions, relays node status information to the server 110, and relays command line level instructions to the node operating system. An example of node software is RemoteWare Node Version 1.4, marketed by the assignee of the present application. RemoteWare Node Version 1.4 is described in a publication entitled "RemoteWare SERVER Setup Guide, Software Release 1 . 4 " , Copyright 1992, XcelleNet, Inc., the disclosure of which is hereby incorporated herein by reference. As already described, the remote/mobile communication system is designed to reduce connect time. By reducing connect time, the costs of the physical network, such as a cellular phone network or a long distance phone line network, are reduced. Moreover, the amount of time that a node (and an end user operating the node) needs to be on line is minimized. Finally, error free connections are provided, notwithstanding the inherent unreliability of the communications links.

Referring now to Figure 2, operations performed at the server to deliver files to remote/mobile nodes according to the present invention are described. It will be understood that these operations are typically performed by a stored program at the server, or at a computer connected thereto, under direction of a user, typically a system administrator. Referring to Block 202, operations begin when the system administrator determines that a file is to be distributed. It will be understood by those having skill in the art that any file type can be distributed, such as a bitmap, an executable program, a spreadsheet, a report or other document. It will also be understood that any file that is accessible using the server can be distributed, including files resident on mainframes, minicomputers or LAN-attached personal computers . A file to be distributed is added to a subscriber list containing one or more files at Block 204. The files can be placed in a subscriber list using well known windowing techniques to create graphical card catalogs or indexes of files. For example, a subscriber editor window may be used to list the files which are to be distributed. New subscriber lists can also be created, and the files added thereto. Referring to Block 206, a determination is made as to whether a given file is to be automatically delivered to a node user during a remote/mobile communication session. If so, the file is tagged as "forced" at Block 208. If not, the file is tagged as "requestable" at Block 210. It will be understood that the default for file distribution is typically

"requestable" so that tagging predetermined files as "forced" will automatically tag the remaining files as "requestable" .

Then, at Block 212, a determination is made as to whether a file is part of a logical group of files which are to be displayed together. If so, then at Block 214, the group is identified. The group may be identified by a creating a Group Description File and then selecting files that belong to the group. Alternatively, a predetermined file can be added to a preexisting Group Description File.

A determination is then made at Block 216 as to whether files in a group can be individually requested. If they cannot be individually requested, i.e. if they are only requestable by group, then the file is tagged "by group" at Block 218. Preferably, the default is that files can be accessed individually, in order to decrease the remote/mobile connection time. However, an indication at Block 218 that the files are requestable by group will cause the individual files to only be accessible as part of a group, so that the system administrator can ensure that all related files or other necessary files are obtained along with a requested file.

Still referring to Figure 2, a determination is made at Block 222 as to whether the file is to be archiveable. In other words, a determination is made as to whether old copies of the file are requestable. If yes, then the file is tagged as archived. For example, an "archive" indication may be entered adjacent the file name in the listing of files. If the file is tagged as being archived, the maximum number of archive copies (a "retention count") is set at Block 226. The list of files is assigned to a user or a group of users.

Then, at Block 228, the list of files is distributed during a remote/mobile communication. It will be understood that a remote/mobile communication may be initiated by the server for the sole purpose of distributing the list of files. Alternatively, the list of files may be distributed during a next scheduled remote/mobile communication. As yet another alternative, a list of files may be distributed during remote/mobile communications which are initiated by the node .

Referring now to Figures 3A - 3B, operations for viewing the list of files and obtaining files during a remote/mobile communication will now be described. At Block 302, the file list which was communicated to the remote/mobile node during a remote/mobile communication is viewed when a user of a remote/mobile node desires to obtain one or more files. At Block 304, requested files are identified, for example, by clicking on selected files in the list.

At Block 306, a determination is made as to whether the selected file is part of a "group only" file. If yes, then the group is selected for delivery. In one alternative, the group which includes the requested file is automatically selected so that delivery of the requested file is accompanied by delivery of the other group members as well . In another option, the user is alerted that the file is a group file and is asked if he wishes to obtain all of the related group files. If the user indicates he does not wish to obtain all of the related files, then the requested file will not be obtained either. If the user confirms that he wishes to obtain the requested files, then the entire group will be automatically distributed.

Still referring to Figures 3A - 3B, at Block 312 a determination is made as to whether the requested file is one which is archived. If yes, the user is presented with an option to select archived copies of the files at Block 314. An option may be presented to the user to select all of the archived copies. Alternatively, the user may indicate individual archived copies which are desired. A listing of the archived copies may be presented to the user in a listbox.

Still referring to Figures 3A - 3B, a remote/mobile link is initiated at Block 316. It will be understood by those having skill in the art that the remote/mobile link may be initiated by the node immediately upon request of a file in order to obtain a copy of the file immediately. Alternatively, the remote/mobile link may be established for other purposes, and the requested files may be obtained during that link. Referring to Block 318, a determination is made at the server as to whether the forced files have been updated at the server since the last (immediately preceding) remote/mobile link to that node. If the forced files have been updated at the server since the last remote/mobile link, then the updated forced files are delivered to the node at Block 322. If not, they are not delivered. At Block 324, the group files, the requested files and the archived files which have been requested at Blocks 304, 308 and 314 are then sent from the server to the node. A test is then made at Block 326 as to whether remote/mobile communications are required for other purposes. If yes, they are initiated at Block 328. If not, the remote/mobile communication is terminated at Block 322. Figures 2 and 3A - 3B illustrate the "forced/ requested", "individual/by group" and "archive" aspects of the present invention in combination. However, it will be understood by those having skill in the art that each of these aspects may be used individually or in subcombinations to ensure that critical files are distributed while reducing remote/mobile connection time . In the drawings and specification, there have been disclosed typical preferred embodiments of the invention and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation, the scope of the invention being set forth in the following claims.

Claims

THAT WHICH IS CLAIMED:

1. A method for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to said server for communication therebetween, said file delivering method comprising the steps of : establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; identifying files in said listing as being one of forced or requestable; delivering said listing to said nodes; automatically delivering to a node each of said files which are identified as forced, in response to establishment of a remote/mobile communications link between said node and said server; and delivering selected ones of said files which are identified as requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as requestable.

2. A method according to Claim 1 wherein said automatically delivering step comprises the steps of: testing whether said files which have been identified as forced, were updated at said server after an immediately preceding remote/mobile communication link between said node and said server; and automatically delivering to said node each of said files which are identified as forced, only if said files which have been identified as forced were updated at said server after said immediately preceding remote/mobile communications link.

3. A method according to Claim 1 wherein said identifying step comprises the steps of: identifying selected files in said listing as being forced; and automatically identifying remaining files in said listing as being requestable.

4. A method according to Claim 1 wherein said identifying step further comprises the step of identifying files in said listing as being one of individually requestable or requestable by group, and wherein said method further comprises the steps of : delivering first selected ones of said files which are identified as individually requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said first selected files which are identified as individually requestable; and delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

5. A method according to Claim 1 wherein said identifying step further comprises the step of identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said method further comprises the steps of : delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies.

6. A method according to Claim 4 wherein said identifying step further comprises the step of identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said method further comprises the steps of : delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies .

7. A method for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily linked to said server for communication therebetween, said file delivering method comprising the steps of : establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; identifying files in said listing as being one of individually requestable or requestable by group; delivering said listing to said nodes; delivering first selected ones of said files which are identified as individually requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said first selected files which are identified as individually requestable; and delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

8. A method according to Claim 7 wherein said step of delivering second selected ones of said files which are identified as being requestable by group comprises the step of : automatically delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

9. A method according to Claim 7 wherein said step of delivering second selected ones of said files which are identified as being requestable by group comprises the step of : automatically delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group as well as files which are members of the groups which include said second selected files.

10. A method according to Claim 7 wherein said identifying step further comprises the step of identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said method further comprises the steps of : delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies .

11. A method for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily linked to said server for communication therebetween, said file delivering method comprising the steps of: establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; identifying files in said listing for which archive copies of the associated file are also deliverable, and a number of archive copies of each of said archive files; delivering said listing to said nodes, including the identification of archived files and of the number of archived copies; delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies.

12. A method according to Claim 11 further comprising the step of: delivering all of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver all of said archived copies.

13. A system for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily and intermittently linked to said server for communication therebetween, said file delivering system comprising: means for establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; means for identifying files in said listing as being one of forced or requestable; means for delivering said listing to said nodes; means for automatically delivering to a node each of said files which are identified as forced, in response to establishment of a remote/mobile communications link between said node and said server; and means for delivering selected ones of said files which are identified as requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as requestable.

14. A system according to Claim 13 wherein said automatically delivering means comprises: means for testing whether said files which have been identified as forced, were updated at said server after an immediately preceding remote/mobile communication link between said node and said server; and means for automatically delivering to said node each of said files which are identified as forced, only if said files which have been identified as forced were updated at said server after said immediately preceding remote/mobile communications link.

15. A system according to Claim 13 wherein said identifying means comprises: means for identifying selected files in said listing as being forced; and means for automatically identifying remaining files in said listing as being requestable.

16. A system according to Claim 13 wherein said identifying means further comprises means for identifying files in said listing as being one of individually requestable or requestable by group, and wherein said system further comprises : means for delivering first selected ones of said files which are identified as individually requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said first selected files which are identified as individually requestable; and means for delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, m response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

17. A system method according to Claim 13 wherein said identifying means further comprises means for identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said system further comprises: means for delivering selected ones of said files which are identified as archived, m response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and means for delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies.

18. A system according to Claim 16 wherein said identifying means further comprises means for identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said system further comprises: means for delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and means for delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies.

19. A system for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily linked to said server for communication therebetween, said file delivering system comprising: means for establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; means for identifying files in said listing as being one of individually requestable or requestable by group; means for delivering said listing to said nodes; means for delivering first selected ones of said files which are identified as individually requestable, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said first selected files which are identified as individually requestable; and means for delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

20. A system according to Claim 19 wherein said means for delivering second selected ones of said files which are identified as being requestable by group comprises: means for automatically delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group.

21. A system according to Claim 19 wherein said means for delivering second selected ones of said files which are identified as being requestable by group comprises : means for automatically delivering second selected ones of said files which are identified as being requestable by group, as well as files which are members of the groups which include said second selected files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request by said server to deliver said second selected files which are identified as selectable by group as well as files which are members of the groups which include said second selected files.

22. A system according to Claim 19 wherein said identifying means further comprises means for identifying files in said listing for which archive copies of the associated file are also deliverable and a number of archive copies of each of the archive files, and wherein said system further comprises: means for delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and means for delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies .

23. A system for delivering files from a data processing server to a plurality of remote/mobile data processing nodes which are temporarily linked to said server for communication therebetween, said file delivering system comprising: means for establishing at said server, a list of files which are deliverable by said server to said nodes during remote/mobile communications; means for identifying files in said listing for which archive copies of the associated file are also deliverable, and a number of archive copies of each of said archive files; means for delivering said listing to said nodes, including the identification of archived files and of the number of archived copies; means for delivering selected ones of said files which are identified as archived, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected files which are identified as archived; and means for delivering selected ones of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver said selected ones of said archived copies.

24. A system according to Claim 23 further comprising: means for delivering all of said archived copies of said selected archived files, in response to establishment of a remote/mobile communications link between said node and said server and receipt of a request at said server to deliver all of said archived copies .