[go: up one dir, main page]

WO1996017461A1 - Procedes et systemes de livraison de fichiers par un serveur a un n×ud mobile eloigne - Google Patents

Procedes et systemes de livraison de fichiers par un serveur a un n×ud mobile eloigne Download PDF

Info

Publication number
WO1996017461A1
WO1996017461A1 PCT/US1995/014494 US9514494W WO9617461A1 WO 1996017461 A1 WO1996017461 A1 WO 1996017461A1 US 9514494 W US9514494 W US 9514494W WO 9617461 A1 WO9617461 A1 WO 9617461A1
Authority
WO
WIPO (PCT)
Prior art keywords
files
server
remote
delivering
identified
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US1995/014494
Other languages
English (en)
Inventor
Rebecca M. Lever
Dennis M. Crumpler
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XcelleNet Inc
Original Assignee
XcelleNet Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by XcelleNet Inc filed Critical XcelleNet Inc
Priority to AU45012/96A priority Critical patent/AU4501296A/en
Publication of WO1996017461A1 publication Critical patent/WO1996017461A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • 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.
  • 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.
  • remote/mobile users.
  • 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.
  • 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.
  • RemoteWare Systems provide 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.
  • the connection cost is minimized and the time that the transactional worker needs to spend connected to the central system are minimized.
  • 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.
  • remote/mobile users can access, view, print, search, copy and scroll through the information and applications. Any updates or changes are automatically available.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • archive copies of files may also be saved by the administrator and requested by a user.
  • Archive copies are older versions of a file.
  • 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.
  • 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.
  • 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.
  • a remote/mobile communications link between the remote/mobile node and the server.
  • FIG. 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.
  • 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.
  • Each remote/mobile server 110 is 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.
  • operations performed at the server to deliver files to remote/mobile nodes 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.
  • 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.
  • 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
  • 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.
  • the list of files is distributed during a remote/mobile communication.
  • a remote/mobile communication may be initiated by the server for the sole purpose of distributing the list of files.
  • the list of files may be distributed during a next scheduled remote/mobile communication.
  • a list of files may be distributed during remote/mobile communications which are initiated by the node .
  • 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.
  • requested files are identified, for example, by clicking on selected files in the list.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Procédé de distribution par des serveurs de traitement de données de fichiers essentiels à des n÷uds mobiles/éloignés permettant de réduire le temps d'établissement de la liaison mobile/éloignée entre le serveur et les n÷uds. Des fichiers sélectionnés dans la liste des fichiers livrables par les serveurs aux n÷uds au cours d'une liaison mobile éloignée peuvent être identifiés comme étant forcés, ou demandables, ou demandables individuellement ou demandables par groupe et/ou archivés. Les dossiers forcés sont fournis automatiquement à un n÷ud suite à l'établissement d'une liaison mobile éloignée entre le n÷ud et le serveur, tandis que les dossiers demandables ne sont fournis que si la demande en a été adressée au serveur. Un fichier demandable individuellement est fourni dès l'établissement d'une liaison mobile éloignée entre le serveur et le n÷ud à la réception d'une demande adressée au serveur. Si une demande est faite pour un fichier qui n'est demandable qu'en groupe, ledit fichier et tous les dossiers faisant partie du groupe sont fournis. Por ce qui est des fichiers archivés, des copies d'archives sélectionnées du fichier ou toutes les copies d'archives du dossier sont fournies sur demande. Les fonctions ci-dessus peuvent s'utiliser individuellement ou en combinaison pour assurer la distribution de données de fichiers essentiels tout en réduisant au minimum le temps d'établissement des liaisons mobiles/éloignées.
PCT/US1995/014494 1994-12-02 1995-11-21 Procedes et systemes de livraison de fichiers par un serveur a un n×ud mobile eloigne Ceased WO1996017461A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU45012/96A AU4501296A (en) 1994-12-02 1995-11-21 Methods and systems for delivering files from a server to remote/mobile nodes

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US34848694A 1994-12-02 1994-12-02
US08/348,486 1994-12-02

Publications (1)

Publication Number Publication Date
WO1996017461A1 true WO1996017461A1 (fr) 1996-06-06

Family

ID=23368252

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1995/014494 Ceased WO1996017461A1 (fr) 1994-12-02 1995-11-21 Procedes et systemes de livraison de fichiers par un serveur a un n×ud mobile eloigne

Country Status (2)

Country Link
AU (1) AU4501296A (fr)
WO (1) WO1996017461A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2335832A (en) * 1994-12-16 1999-09-29 Xcellenet Inc Automatic file transfer between a server and a mobile node
WO2001050800A1 (fr) * 1999-12-30 2001-07-12 Sonera Oyj Procede et systeme pour transmission du temps de connexion

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991002313A1 (fr) * 1989-08-03 1991-02-21 International Business Machines Corporation Reseau de traitement de donnees
WO1994012938A1 (fr) * 1992-12-02 1994-06-09 Compaq Computer Corporation Ordinateur portatif a synchronisation automatique de donnees avec l'ordinateur central

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991002313A1 (fr) * 1989-08-03 1991-02-21 International Business Machines Corporation Reseau de traitement de donnees
WO1994012938A1 (fr) * 1992-12-02 1994-06-09 Compaq Computer Corporation Ordinateur portatif a synchronisation automatique de donnees avec l'ordinateur central

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2335832A (en) * 1994-12-16 1999-09-29 Xcellenet Inc Automatic file transfer between a server and a mobile node
GB2335832B (en) * 1994-12-16 1999-11-10 Xcellenet Inc Systems and methods for transferring information from a server to a remote/mobile node
WO2001050800A1 (fr) * 1999-12-30 2001-07-12 Sonera Oyj Procede et systeme pour transmission du temps de connexion

Also Published As

Publication number Publication date
AU4501296A (en) 1996-06-19

Similar Documents

Publication Publication Date Title
US5819274A (en) Methods, systems and computer program products for transferring files from a data processing server to a remote/mobile data processing node
US5680548A (en) Systems and methods for work assignment and distribution from a server to remote/mobile nodes
US5734903A (en) System and method for object oriented message filtering
WO1996018257A9 (fr) Systeme et procede d'attribution et de repartition de taches d'un serveur alimentant des n×uds mobiles/eloignes
US6633898B1 (en) System, apparatus, method and computer program product for processing distributed service modules
US6728766B2 (en) Methods, systems and computer program products for license use management on a network
US6026366A (en) Method for providing software to a remote computer
US5933601A (en) Method for systems management of object-based computer networks
US7171660B2 (en) Intelligent patch checker
US7194468B1 (en) Apparatus and a method for supplying information
CN101902494A (zh) 更新服务节点
WO1994018626A1 (fr) Procede et appareil pour selectionner entre une pluralite de trajets de communication
WO1996017460A9 (fr) Procede et systeme permettant d'eviter les transferts inutiles de fichiers entre un serveur et un noeud eloigne
WO1996017460A1 (fr) Procede et systeme permettant d'eviter les transferts inutiles de fichiers entre un serveur et un noeud eloigne
JPH10171635A (ja) 分散環境におけるソフトウエア資源を管理するシステムと方法
WO1996017461A1 (fr) Procedes et systemes de livraison de fichiers par un serveur a un n×ud mobile eloigne
US5862176A (en) Data transfer processing system achieving high speed transfer of continuously updated/renewed data using pre-renewal and post-renewal information
US20050198229A1 (en) Methods, systems, and computer program products for template-based network element management
AU702268B2 (en) Adaptable user interface
JPH1185694A (ja) サーバー間連携業務運用システム
WO1999034622A1 (fr) Procede et systeme de mise en oeuvre technique dans un reseau intelligent avance
JPH07250064A (ja) ネットワークエレメント増設業務管理装置
JPH0895880A (ja) ソフトウェア配信方式
JPH086834A (ja) ファイル資源管理システムおよびその方法
JP3171658B2 (ja) ネットワークにおけるソフトウェア管理方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LK LR LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TT UA UG US UZ VN

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase