[go: up one dir, main page]

WO1999048007A1 - Procede et systeme permettant de faire fonctionner des peripheriques repartis a distance sur un reseau a travers differentes plates-formes - Google Patents

Procede et systeme permettant de faire fonctionner des peripheriques repartis a distance sur un reseau a travers differentes plates-formes Download PDF

Info

Publication number
WO1999048007A1
WO1999048007A1 PCT/IL1999/000157 IL9900157W WO9948007A1 WO 1999048007 A1 WO1999048007 A1 WO 1999048007A1 IL 9900157 W IL9900157 W IL 9900157W WO 9948007 A1 WO9948007 A1 WO 9948007A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
client
computer
remote
remote server
Prior art date
Application number
PCT/IL1999/000157
Other languages
English (en)
Inventor
Barak Cohen
Asher Kariv
Amir Glick
Original Assignee
Barak Cohen
Asher Kariv
Amir Glick
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 Barak Cohen, Asher Kariv, Amir Glick filed Critical Barak Cohen
Priority to AU29544/99A priority Critical patent/AU2954499A/en
Publication of WO1999048007A1 publication Critical patent/WO1999048007A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45537—Provision of facilities of other operating environments, e.g. WINE
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • 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/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • 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

  • the present invention relates to a system and method for remote operation of hardware devices and, more specifically, to a system and a method which enables distributed hardware devices to be browsed, operated and managed on a network across platforms.
  • Networks are able to provide a connection for many different types of computers being operated by different operating systems. Such networks are useful for communication between computers, for example with electronic mail. However, networks also enable distributed resources to be available to remote users. For example, disk storage could be provided on one server computer but then accessed by a plurality of remote client computers. Such distribution of resources can be very useful for corporate networks, enabling two remote users to examine files without requiring local copies of these files to be available, for example.
  • hardware devices can be mounted for local operation by a remote computer.
  • a computer being operated according to the UNIX operating system could mount a tape backup device attached to a remote computer through the network.
  • the local computer could then control the operation of the remote tape backup device.
  • Such functionality is particularly useful when each computer of a group on a network has attached disk storage space which must be backed up. Rather than purchase and install a separate tape backup device for each computer, the group of computers being operated according to the UNIX operating system could share one such device.
  • the ability to share hardware devices across a network is clearly desirable.
  • a far more convenient and efficient system would enable many different computers on a network to share remote hardware resources, such as tape backup devices, as though these devices were directly attached to the local computer. Such a system would sharply reduce or eliminate duplication of hardware resources, and simplify administration and operation of these resources.
  • remote hardware resources such as tape backup devices
  • Such a system would sharply reduce or eliminate duplication of hardware resources, and simplify administration and operation of these resources.
  • embedded platforms such as a smart-card device being operated according to the Windows CETM operating system or another embedded operating system, to interact with remote computers and server as hardware servers for other computers. Unfortunately, such a system for sharing hardware resources across a network is not currently available.
  • a system for remote operation of a hardware device by a client computer comprising: (a) a server computer for being connected to the hardware device, the server computer being connected to the client computer tlrrough a network; (b) a driver for communicating 3 with the hardware device, the driver being operated by the server computer; and (c) a remote server for communicating with the driver and the client computer, the remote server being operated by the server computer, such that the client computer is able to communicate with the hardware device through the remote server.
  • the system further includes a plurality of client computers, wherein the remote server is able to cache data from the hardware device and to provide the data to each of the plurality of client computers individually, such that substantially all of the plurality of client computers are able to receive substantially the same data.
  • the client computer is operated according to a 32-bit version of a WindowsTM operating system. More preferably, the operating system for the client computer is each individually selected from the group consisting of Windows95TM, Windows CETM, Windows NTTM and Windows98TM.
  • the server computer is preferably operated by a multithreaded operating system that supports TCP/IP. Alternatively and preferably, one of the server computer and the client computer is operated according to a Java-VM operating system.
  • the remote server and the client computer are capable of communication according to the TCP/IP suite of protocols- According to other preferred embodiments of the present invention, the remote server and the client computer communicate according to different communication protocols, and the system further includes: (d) a proxy module for translating between the remote server and the client computer, such that the remote server and the client computer are able to communicate. .Preferably, the proxy module further transforms a data format for the remote server and the client computer, such that the remote server and the client computer are able to exchange data.
  • the system fui her includes (d) a legacy application for being operated by the client computer, such that the legacy application only communicates indirectly with the remote server; (e) a legacy driver for being operated by the client computer and for 4 interacting directly with the legacy application; and (f) a client service module for being operated by the client computer and for communicating with the legacy driver, the client service module communicating with the remote server, such that the legacy application is able to interact with the hardware device through the legacy driver, the client service module and the remote server.
  • the remote server and the client service module communicate according to different communication protocols, the system further comprising: (g) a proxy module for translating between the remote server and the client service module, such that the remote server and the client service module are able to communicate. More preferably, the proxy module transforms a data format between the legacy application and the remote server, such that the legacy application and the remote server are able to exchange data.
  • the remote server and the client service module communicate according to substantially the same communication protocol.
  • the system further includes (g) a virtual bus driver, the virtual bus driver enabling the legacy driver and the client service module to communicate; and (h) a remote class module, the remote class module registering the hardware device with the remote server.
  • the client computer and the server computer are being operated according to an OnNow enabled operating system.
  • a system for management of a plurality of remote hardware devices comprising: (a) a plurality of server computers, each of the server computers being connected to at least one of the plurality of remote hardware devices; (b) a plurality of server modules, each of the plurality of server modules being run by one of the server computers; (c) a plurality of client computers, each of the client computers interacting with the server computers through the server modules; (d) a plurality of management modules for managing an interaction of the client computers and the server modules; and (e) a name server for registering information regarding the server modules and providing the information to the management modules.
  • the information includes a location of a server computer upon receipt of a browsing request.
  • the information includes at least one attribute of the hardware devices. More preferably, the information includes a description of the hardware devices.
  • network refers to a connection between any two computers which permits the transmission of data.
  • computer includes, but is not limited to, personal computers (PC) having an operating system such as DOS, WindowsTM, OS/2TM or; MacintoshTM computers; computers having
  • JAN ATM -OS as the operating system
  • graphical workstations such as the computers of Sun Microsystems TM and Silicon GraphicsTM, and other computers having some version of the UNIX operating system such as AIX or SOLARISTM of Sun MicrosystemsTM; or any other known and available operating system.
  • WindowsTM includes but is not limited to Windows95TM, Windows 3.xTM in which "x" is an integer such as "1”, Windows NTTM, Windows98TM, Windows CETM and any upgraded versions of these operating systems by Microsoft Inc. (Seattle, Washington, USA).
  • PC or "PC computer” refer to computers having an operating system such as DOS, WindowsTM, OS/2TM or Linux.
  • the term "netPC” includes, but is not limited to, a computer having JANATM-OS or Java-NM as the operating system.
  • the terms “Embedded platform” refer to computers having an embedded operating system such as "Windows CE”, pSOS, Q ⁇ X or any other embedded operating system.
  • a software application could be written in substantially any suitable programming language, wliich could easily be selected by one of ordinary skill in the art.
  • the programming language chosen should be compatible with the computing platfo ⁇ n according to which the software application is executed. Examples of suitable programming, languages include, but .are not limited to, C, C++ and Java.
  • the present invention could be implemented as software, firmware, or hardware or as a combination thereof.
  • the functional steps performed by the method could be described as a plurality of instructions perf oimed by a data processor.
  • FIG. 1 is a schematic illustration of a prior art system for operating a hardware device
  • FIG. 2 is a schematic illustration of a native system for remote operation of hardware according to the present invention
  • FIG. 3 is a schematic illustration of the system of Figure 2 with a proxy according to the present invention
  • FIG. 4 is a schematic illustration of a legacy system for remote operation of hardware according to the present invention.
  • FIG. 5 is a schematic illustration of the system of Figure 4 with a proxy according to the present invention.
  • FIG. 6 is a schematic illustration of a virtual bus system for remote operation of hardware according to the present invention
  • FIG. 7 is a schematic illustration of a management system for remote operation of hardware according to the present invention.
  • the present invention is of a method and a system to administer, browse and operate a remote hardware device over a network by a local computer as though the remote hardware device is directly attached to the local computer.
  • FIG. 1 depicts the currently available prior art system for operation of a hardware device.
  • a prior art system 10 features a local computer 12, which could be a PC or netPC computer, for example.
  • Local computer 12 has a hardware device 14 directly attached.
  • Hardware device 14 could be a tape backup device, for example.
  • the operation of hardware device 14 is controlled by a software application 16, which communicates with hardware device 14 through a driver 18.
  • Software application 16, driver 18 and hardware device 14 are all operated through local computer 12.
  • Local computer 12 controls the operation of hardware device 14, such that any communication with or instructions to hardware device 14 can only be given by local computer 12.
  • the remote computer would still not be able to control the operation of hardware device 14, which is clearly a disadvantage of prior art system 10.
  • FIG. 2 is a schematic illustration of a system for remote operation of hardware according to the present invention, for a native client.
  • Figure 2 shows a remote system 20 for a native client 22.
  • Remote system 20 features a remote server 24, which is a software module being operated by a server computer (not shown).
  • the server computer is connected to native client 22 ttirough a network 26.
  • both native client 22 and the server computer are running the same communication protocol, such as TCP/IP(or other socket based communication protocol).
  • Native client 22 is a computer which uses the same communication protocol as the server computer.
  • the server computer could 8 be a computer being operated according to the Windows NTTM operating system, for example, or any other suitable operating system.
  • Native client 22 could also be a computer being operated according to the Windows NTTM operating system, for example or any other suitable operating system.
  • Remote system 20 also features a hardware driver 28 for operating a hardware device which is attached to the server computer (not shown).
  • Remote server computer 24 is able to interact with hardware driver 28 in order to enable the hardware device to be exported through network 26.
  • Remote server 24 supports both point to point connections, as shown, and a point to multipoint connection. The point to multipoint connection enables the exported hardware device to be shared by multiple native clients 22.
  • Remote server 24 can also provide multicasting streaming services by caching data from hardware driver 52, and then storing the cached data. Remote server 24 then serves the cached data upon request by native clients 22. Such streaming of the data enables all of the native clients 22 to get the same information.
  • native client 22 is also able to control the operation of the exported hardware device by directly interacting with hardware driver 28, as though the hardware device was directly attached to native client 22.
  • Such interaction occurs because the hardware device is exported by remote server 24, which provides the support for the direct interaction of native client 22 and the exported hardware device.
  • remote server 24 Since both the operating system of native client 22 and the operating system of the computer running remote server 24 share the same communication model and since an object communication model on the client, such as DCOM (distributed component object model), exports the hardware interfaces, the interaction of remote server 24 and software applications running on native client 22 occurs through this object communication model. Thus, no additional software is required for native client 22 to run in order for native client 22 to control the hardware device.
  • DCOM distributed component object model
  • DCOM is an object protocol which enables software objects to communicate directly across a network, as though both objects were being operated by the same 9 local computer. In other words, each software object is able to call the methods of the other software object directly over the network. DCOM enables any software application running on native client 22 to communicate directly with remote server 24 in order to communicate with, and to send instructions to, the hardware device. Of course, DCOM is simply one example of an object communication model, and is not meant to be limiting in any way.
  • FIG. 3 shows a proxy remote system 30 according to the present invention.
  • proxy remote system 30 also features a remote server 32 and a native client 34, similar to Figure 2.
  • Remote server 32 is also a software module being operated by a server computer (not shown).
  • the server computer is connected to a hardware device (not shown) which is controlled through a hardware driver 36.
  • the server computer is connected to native client 34 tahrough a network 38.
  • native client 34 and the server computer are not running the same object communication protocol, and could be different platforms.
  • Proxy 40 is a software module running on a computer (not shown) which is connected to network 38. Proxy 40 is able to translate the communication protocol used by remote server 32 into the protocol which is used by native client 34. If necessary, proxy 40 is able to transform the data from the format used by remote server 32 to the format used by native client 34, and vice versa.
  • the Windows CETM operating system does not support DCOM. If remote server 32 were being operated according to the Windows CETM operating system, proxy 40 would translate the DCOM-based communication from native client 34 into TCP/IP communication for remote server 32. Proxy 40 could be used to translate many other types of communication protocols, for example in order to further promote cross-platform compatibility. Thus, remote server 32 could communicate with many different types of native clients 34 through proxy 40.
  • FIG 4 shows a system according to the present invention for enabling interactions of a hardware device with a legacy client.
  • a legacy system 42 is 10 shown, again with a remote server 44 connected to a legacy client 46 through a network 48.
  • Legacy client 46 is a computer which runs a legacy application 50, which can be software or a driver.
  • Legacy application 50 interacts with a hardware device controlled through a hardware driver 52 in a transparent manner.
  • Hardware driver 52 is run on the computer which is running remote server 44 (not shown).
  • the hardware device is also connected to the same computer (not shown).
  • legacy client 46 In order for legacy application 50 to interact with the hardware device, the hardware device must appear to be connected directly to legacy client 46 as far as legacy application 50 is concerned. Therefore, all commands and instructions to, and communication with, the hardware device must appear to occur locally. In order for such communication to occur locally, legacy client 46 also runs two other software modules: a client service module 54 and a legacy driver 56. Client service module 54 interacts with remote server 44 in order to communicate with the hardware device through hardware driver 52.
  • client service module 54 is an example of software operated by a native client, and can use native client communication protocols to communicate with remote server 54.
  • Legacy driver 56 is a software module which also runs on legacy client 46 and emulates the behavior of the hardware device as though the hardware device was installed on legacy client 46.
  • Legacy driver 56 is specially adapted for each operating system, so that legacy application 50 can communicate with legacy driver 56 as though legacy driver 56 was the hardware driver for the remote hardware device.
  • Legacy driver 56 understands how to communicate with legacy application 50 through a hardware profile.
  • the hardware profile is a data profile on legacy client 46 which indicates the protocol to be used when communicating with legacy application 50 as well as the necessary configuration parameters, so that legacy driver 56 can expose itself to the operating system of legacy client 46 as the proper type of hardware device.
  • Legacy driver 56 then communicates with client service module 54, which communicates in turn with remote server 44.
  • Remote server 44 then communicates 11 with the hardware device through hardware driver 52.
  • legacy system 42 enables legacy application 50 to interact with the hardware device as though the hardware device was installed on the local computer, which is legacy client 46.
  • Figure 5 shows a second embodiment of legacy system 42, in which remote server 44 communicates with legacy client 46 through a proxy 58.
  • the computer running remote server 44 and legacy client 46 have different communication and data protocols, and could optionally be different platforms.
  • Proxy 58 enables legacy client 46 to communicate with remote server 44.
  • the remaining aspects of the system are similar to that shown in Figure 4.
  • Figure 6 shows a virtual bus system 60 according to the present invention.
  • Nirtual bus system 60 features a remote server 62 being run on a computer (not shown).
  • Remote server 62 is connected to a legacy client 64 through a client service module 68.
  • Legacy client 64 is a computer which runs client service module 68.
  • Legacy client 64 also features a legacy application 66 and a legacy driver 70.
  • Legacy application 66 communicates with legacy driver 70, while client service module 68 communicates with remote server 62.
  • legacy driver 70 communicates with client service module 68 through a virtual bus driver 72.
  • Nirtual bus driver 72 is a software module which .runs on OnNowTM enabled operating systems, such as Windows NTTM and Windows95TM, or an upgraded version of one of these systems such as Windows98TM.
  • OnNowTM is a standard for operating systems for controlling the operation of hardware devices.
  • OnNowTM permits notification of virtual bus driver 72 when the hardware device controlled by hardware driver 74 becomes operational, for example by being installed on the hardware bus on the remote computer.
  • virtual bus driver 72 enables legacy driver 70 to reflect the operational status of the remote hardware device.
  • virtual bus driver 72 simulates a bus to which hardware devices are attached. These hardware devices are exported by remote server 62 through network 48.
  • remote server 62 communicates with a hardware driver 74 tlirough a remote class module 76.
  • Remote class module 76 is a software module which 12 inns on OnNow enabled operating systems, such as Windows NTTM and
  • Remote class module 76 provides registration services for hardware drivers 74 to be exported through network 48.
  • Remote class module 76 and virtual bus driver 72 can communicate through the WindowsTM Driver Model (WDM), for example.
  • WDM is a bus driver which provides certain services accessible to any software program being run by a computer operated according to one of these operating systems.
  • WDM enables a driver to receive notification as soon as a device is connected to a local hardware bus.
  • legacy application 66 can communicate with the remote hardware device as follows.
  • the remote hardware device becomes activated, for example after "sleeping".
  • Hardware driver 74 now notifies remote class module 76.
  • Remote class module 76 then notifies remote server 62, which in turn notifies client service module 68.
  • Client service module 68 notifies virtual bus driver 72 as though virtual bus driver 72 was an actual hardware bus.
  • Nirtual bus driver 72 communicates with legacy driver 70 so that legacy driver 70 can reflect the cuixent status of the remote hardware device. This communication occurs as though the remote hardware device was connected to a local hardware bus on legacy client 64.
  • FIG. 7 shows a management system according to the present invention.
  • a management system 78 includes a plurality of remote servers 80 connected to network 48, which could be remote servers from any of the preceding Figures 2-6.
  • management system 78 includes a plurality of clients 82 connected to network 48, which could be clients from any of the preceding Figures 2-6.
  • Management system 78 additionally features a plurality of remote management modules 84 connected to network 48.
  • Remote management modules 84 provides device browsing capabilities so that clients 82 can browse network 48 for hardware devices (not shown) exported by remote servers 80.
  • remote management modules 84 provides device security management, so an administrator 13 could decide which devices an individual user could access, for example.
  • Name server 86 contains the information from all remote servers 80 attached to network 48.
  • name server 86 contains the information concerning the location of hardware devices on network 48, and the attributes and description of these devices
  • management system 78 When a user sends a request for browsing to management system 78, management system 78 then draws this information from name server 86.
  • Any remote server 80 which exports hardware devices preferably registers with name server 86 to indicate the location of the hardware device, and the attributes and description of the hardware device.
  • management system 78 is optionally integrated with the standard directory services offered by the operating system according to the ActiveDirectoryTM implementation on certain 32-bit WindowsTM operating systems, such as Windows NTTM and Windows98TM.
  • This integration enables management system 78 to permit the user to browse and explore devices without remote server 80 or management module 84, through standard directory services.
  • the hardware device is published to the ActiveDirectoryTM services or other standard directory services, so that every client 82 can browse through these published device resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un système permettant de faire fonctionner à distance un périphérique au moyen d'un ordinateur client (54) et comprenant un ordinateur serveur à connecter au périphérique, le serveur étant connecté à l'ordinateur client sur un réseau (48) et un pilote (52) permettant de communiquer avec le périphérique, le pilote étant mis en route par l'ordinateur serveur et un serveur à distance (44) permettant de communiquer avec le pilote et l'ordinateur client, le serveur à distance étant mis en route par l'ordinateur serveur de manière que l'ordinateur client soit en mesure de communiquer avec le périphérique via le serveur à distance et une application déjà installée destinée à être lancée par l'ordinateur client de manière que cette application (48) ne communique qu'indirectement avec le serveur à distance et un pilote déjà installé (56) destiné à être mis en route par l'ordinateur client et interagissant directement avec l'application déjà installée.
PCT/IL1999/000157 1998-03-19 1999-03-18 Procede et systeme permettant de faire fonctionner des peripheriques repartis a distance sur un reseau a travers differentes plates-formes WO1999048007A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU29544/99A AU2954499A (en) 1998-03-19 1999-03-18 A method and system for operating distributed hardware devices remotely on a network across different platforms

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US4416798A 1998-03-19 1998-03-19
US09/044,167 1998-03-19

Publications (1)

Publication Number Publication Date
WO1999048007A1 true WO1999048007A1 (fr) 1999-09-23

Family

ID=21930866

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL1999/000157 WO1999048007A1 (fr) 1998-03-19 1999-03-18 Procede et systeme permettant de faire fonctionner des peripheriques repartis a distance sur un reseau a travers differentes plates-formes

Country Status (2)

Country Link
AU (1) AU2954499A (fr)
WO (1) WO1999048007A1 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1022699A3 (fr) * 1999-01-21 2002-06-19 Ncr International Inc. Réseau pour terminaux self-service
WO2002045382A3 (fr) * 2000-11-30 2003-01-23 Palm Inc Enregistrement de service pour une application fonctionnant sur un appareil sans fil
WO2001077878A3 (fr) * 2000-04-10 2003-12-31 Storage Technology Corp Commande de bibliotheques robotisees par serveur
US6842777B1 (en) 2000-10-03 2005-01-11 Raja Singh Tuli Methods and apparatuses for simultaneous access by multiple remote devices
US6874009B1 (en) 2000-02-16 2005-03-29 Raja Tuli Portable high speed internet device with user fees
US6941382B1 (en) 2000-02-07 2005-09-06 Raja Tuli Portable high speed internet or desktop device
US7023572B2 (en) 2000-02-02 2006-04-04 Raja Singh Tuli Portable high speed internet access device
US7068381B1 (en) 2000-02-02 2006-06-27 Raja Tuli Portable high speed internet access device
US7356570B1 (en) 2000-08-29 2008-04-08 Raja Tuli Portable high speed communication device
US7360173B2 (en) 2000-02-02 2008-04-15 Raja Tuli Portable high speed internet device integrating cellular telephone and palm top computer
US8176428B2 (en) 2002-12-03 2012-05-08 Datawind Net Access Corporation Portable internet access device back page cache

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4751635A (en) * 1986-04-16 1988-06-14 Bell Communications Research, Inc. Distributed management support system for software managers
US5748980A (en) * 1994-05-27 1998-05-05 Microsoft Corporation System for configuring a computer system
US5754830A (en) * 1996-04-01 1998-05-19 Openconnect Systems, Incorporated Server and web browser terminal emulator for persistent connection to a legacy host system and method of operation
US5838916A (en) * 1996-03-14 1998-11-17 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US5848236A (en) * 1996-03-22 1998-12-08 Sun Microsystems, Inc. Object-oriented development framework for distributed hardware simulation
US5881230A (en) * 1996-06-24 1999-03-09 Microsoft Corporation Method and system for remote automation of object oriented applications
US5898835A (en) * 1996-08-16 1999-04-27 Electronic Data Systems Corporation System and method for remotely executing a command
US5909545A (en) * 1996-01-19 1999-06-01 Tridia Corporation Method and system for on demand downloading of module to enable remote control of an application program over a network

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4751635A (en) * 1986-04-16 1988-06-14 Bell Communications Research, Inc. Distributed management support system for software managers
US5748980A (en) * 1994-05-27 1998-05-05 Microsoft Corporation System for configuring a computer system
US5909545A (en) * 1996-01-19 1999-06-01 Tridia Corporation Method and system for on demand downloading of module to enable remote control of an application program over a network
US5838916A (en) * 1996-03-14 1998-11-17 Domenikos; Steven D. Systems and methods for executing application programs from a memory device linked to a server
US5848236A (en) * 1996-03-22 1998-12-08 Sun Microsystems, Inc. Object-oriented development framework for distributed hardware simulation
US5754830A (en) * 1996-04-01 1998-05-19 Openconnect Systems, Incorporated Server and web browser terminal emulator for persistent connection to a legacy host system and method of operation
US5881230A (en) * 1996-06-24 1999-03-09 Microsoft Corporation Method and system for remote automation of object oriented applications
US5898835A (en) * 1996-08-16 1999-04-27 Electronic Data Systems Corporation System and method for remotely executing a command

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"P1394A DRAFT STANDARD FOR A HIGH PERFORMANCE SERIAL BUS (SUPPLEMENT)", P1394A DRAFT 0.05 DRAFT STANDARD FOR A HIGH PERFORMANCE SERIALBUS (SUPPLEMENT), XX, XX, 1 February 1997 (1997-02-01), XX, pages COMPLETE, XP002919496 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1022699A3 (fr) * 1999-01-21 2002-06-19 Ncr International Inc. Réseau pour terminaux self-service
US7360173B2 (en) 2000-02-02 2008-04-15 Raja Tuli Portable high speed internet device integrating cellular telephone and palm top computer
US7068381B1 (en) 2000-02-02 2006-06-27 Raja Tuli Portable high speed internet access device
US7023572B2 (en) 2000-02-02 2006-04-04 Raja Singh Tuli Portable high speed internet access device
US6941382B1 (en) 2000-02-07 2005-09-06 Raja Tuli Portable high speed internet or desktop device
US6874009B1 (en) 2000-02-16 2005-03-29 Raja Tuli Portable high speed internet device with user fees
US6856985B1 (en) 2000-04-10 2005-02-15 Storage Technology Corporation Server based control of robotic libraries
WO2001077878A3 (fr) * 2000-04-10 2003-12-31 Storage Technology Corp Commande de bibliotheques robotisees par serveur
US7356570B1 (en) 2000-08-29 2008-04-08 Raja Tuli Portable high speed communication device
US6842777B1 (en) 2000-10-03 2005-01-11 Raja Singh Tuli Methods and apparatuses for simultaneous access by multiple remote devices
US6826387B1 (en) 2000-11-30 2004-11-30 Palmsource, Inc. Efficient service registration for legacy applications in a bluetooth environment
WO2002045382A3 (fr) * 2000-11-30 2003-01-23 Palm Inc Enregistrement de service pour une application fonctionnant sur un appareil sans fil
US8176428B2 (en) 2002-12-03 2012-05-08 Datawind Net Access Corporation Portable internet access device back page cache

Also Published As

Publication number Publication date
AU2954499A (en) 1999-10-11

Similar Documents

Publication Publication Date Title
US9239762B1 (en) Method and apparatus for virtualizing file system placeholders at a computer
US6654794B1 (en) Method, data processing system and program product that provide an internet-compatible network file system driver
JP5753665B2 (ja) クラウドストレージを提供するクライアント、仲介サーバ及び方法
US8677111B2 (en) Booting devices using virtual storage arrays over wide-area networks
JP4567293B2 (ja) ファイルサーバ
US8560593B2 (en) System for provisioning, allocating, and managing virtual and physical desktop computers in a network computing environment
US20070180280A1 (en) Controlling the allocation of power to a plurality of computers whose supply of power is managed by a common power manager
CN104412252B (zh) 使用虚拟媒体客户端并通过远程访问器具来访问远程磁盘镜像的系统和方法
US8151360B1 (en) System and method for administering security in a logical namespace of a storage system environment
WO1999048007A1 (fr) Procede et systeme permettant de faire fonctionner des peripheriques repartis a distance sur un reseau a travers differentes plates-formes
Bender et al. Unix for nomads: Making unix support mobile computing
US20030233510A1 (en) Storage resource integration layer interfaces
EP1631896A2 (fr) Emulation d'une unite de bande virtuelle multiplateforme
Sacks Demystifying storage networking das, san, nas, nas gateways, fibre channel, and iscsi
US20070162564A1 (en) File system interface to web and network services
EP1492028B1 (fr) Accès à un dispositif de disque partagé dans un réseau de stockage
EP1235156B1 (fr) Unité de gestion à distance avec interface pour échange de données à distance
US20050132084A1 (en) Method and apparatus for providing server local SMBIOS table through out-of-band communication
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management
Cisco XRemote Configuration and Management

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

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

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase