WO1998006207A1 - A system, method and article of manufacture for seamless, server application support of network and non-network client terminals - Google Patents

A system, method and article of manufacture for seamless, server application support of network and non-network client terminals Download PDF

Info

Publication number
WO1998006207A1
WO1998006207A1 PCT/US1997/013057 US9713057W WO9806207A1 WO 1998006207 A1 WO1998006207 A1 WO 1998006207A1 US 9713057 W US9713057 W US 9713057W WO 9806207 A1 WO9806207 A1 WO 9806207A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
server
terminal
network
application
Prior art date
Application number
PCT/US1997/013057
Other languages
French (fr)
Inventor
Richard Cowan
Gordon P. Eckley
Prasad V. R. Panchangam
Winston C. W. Leong
Original Assignee
Verifone, 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 Verifone, Inc. filed Critical Verifone, Inc.
Priority to EP97937021A priority Critical patent/EP0919092B1/en
Priority to DE69732968T priority patent/DE69732968T2/en
Priority to AU39638/97A priority patent/AU730088B2/en
Publication of WO1998006207A1 publication Critical patent/WO1998006207A1/en
Priority to HK99102575A priority patent/HK1017539A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/104Peer-to-peer [P2P] networks
    • H04L67/1087Peer-to-peer [P2P] networks using cross-functional networking aspects
    • H04L67/1091Interfacing with client-server systems or between P2P systems

Definitions

  • This invention generally relates to improvements in computer systems, and more particularly, to system software for managing a network of heterogeneous client terminals communicating with a server in a consistent manner.
  • a device While operational devices are somewhat hazy and non-standard, a device is referred to as a terminal if a user interacts with the device to communicate to a host processor, referred to as a server in a network computing environment.
  • Examples of terminals include keyboard /printer terminals, cathode-ray tube (CRT) terminals, remote-batch terminals, real-time data-acquisition and control terminals, transaction and point-of-sale terminals, and smart terminals.
  • CTR cathode-ray tube
  • a terminal is considered to be intelligent if it contains, hard-, firm-, and or software which allows it to perform alphanumeric or graphic message entry, display buffering, verifying, editing and block transmissions, either on host or human command. If the terminal contains a microprocessor which runs a standard program to service the terminal, and not arbitrary, user-loaded programs, the terminal has a fixed function, and is still just an intelligent terminal. Only when the device contains a general purpose computer which is easily accessible to the ordinary user for offering a wide range of programs selectable by a user or by devices attached to the device does the terminal become a network terminal in accordance with a preferred embodiment.
  • Java is a general-purpose, concurrent, class-based, object-oriented programming language and support structure, specifically designed to have as few implementation dependencies as possible. Java allows application developers to write a program once and then be able to run it everywhere on a computer network.
  • the Java language solves many of the client-side problems by: o enabling dynamic class bindings; o providing enhanced portability of applications; and o providing a secure environment in which applications execute.
  • Java is compiled into bytecodes in an intermediate form instead of machine code (like C, C++, Fortran, etc.).
  • the bytecodes execute on any machine with a Java bytecode interpreter.
  • Java applications can run on a variety of client machines, and the bytecodes are compact and designed to transmit efficiently over a network which enhances a preferred embodiment with universal clients and server- centric policies.
  • UI User Interface
  • Custom “widgets” e.g. real-time stock tickers, animated icons, etc.
  • client-side validation e.g. real-time stock tickers, animated icons, etc.
  • Dynamic, real-time applications can be created using the above-mentioned components.
  • Sun's Java language has emerged as an industry-recognized language for "programming the Internet.”
  • Sun defines Java as: "a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language.
  • Java supports programming for the Internet in the form of platform-independent Java applets.”
  • Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add "interactive content" to Web documents (e.g. simple animations, page adornments, basic games, etc.). Applets execute within a Java- compatible browser (e.g. Netscape Navigator) by copying code from the server to client.
  • Java's core feature set is based on C++.
  • Sun's Java literature states that Java is basically "C++, with extensions from Objective C for more dynamic method resolution”.
  • a network terminal in accordance with a preferred embodiment would execute Java applications in stand-alone mode, but have the capability to interact with a server for such functions as retrieving information, database processing, massive computation processing and access to shared devices such as high-speed printers, plotters and magnetic tapes.
  • distributed computing refers both to the devices at remote locations and to the logic which has been used to enhance the intelligence of the devices.
  • Such distributed or decentralized computing with remote intelligent terminals and network terminals is a fact of life in today's computer literate society.
  • a nonstandard terminal might require a special-purpose interface and might not be recognized by the host. Even standard interfaces are notorious for crashing the operating system. In any case, "mixed systems" containing multiple vendor hardware are becoming the norm, but lead to the blame for system problems being placed on the other system, and result in difficult debugging and resolving of system problems.
  • host operating system support for a heterogeneous terminal environment can be a nightmare. To provide support for all of the various protocols, communication rates and processing demands with the peculiarities intrinsic to a motley crew of downstream terminals is a system administration headache.
  • this type of support ranges from minimal (say, a compiler for the particular terminal) to a mail program that is compatible with every different terminal attached to the host server.
  • Some applications can be rebuilt for a particular terminal by simply recompiling the application, but many are only distributed as runtime modules with no support provided for some terminals.
  • the dispatcher spawns a server application in the server which responds to the client application in the client. Going forward, the server application responds to all future requests from the client application. If the client is not a network terminal, then the application dispatcher initiates a client application in the server to service the client terminal application requirements. Requests from the client application on behalf of the client terminal are subsequently serviced by a server application at the server which communicates to the client terminal via the client application at the server.
  • Figure 1 is a block schematic diagram of a computer system for example, a personal computer system on which the inventive object oriented information manager operates;
  • Figure 2 illustrates a client - server network in accordance with a preferred embodiment
  • FIG. 3 illustrates a server architecture in accordance with a preferred embodiment
  • FIG. 4 illustrates a client - server architecture in accordance with a preferred embodiment
  • Figure 5 illustrates a first client request to a server in accordance with a preferred embodiment
  • Figure 6 illustrates a client server environment which accesses support services in accordance with a preferred embodiment
  • Figure 7 is an architecture diagram of a client - server system in accordance with a preferred embodiment
  • Figure 8 is an architecture diagram of a client - server system in accordance with a preferred embodiment
  • Figure 9 is an architecture Hiagram of a client - server system in accordance with a preferred embodiment
  • Figure 10 illustrate ' s the message format utilized in accordance with a preferred embodiment
  • Figure 11 presents a table showing additional details associated with the device types, commands and data blocks in accordance with a preferred embodiment
  • Figure 12 presents additional detail on the message format in accordance with a preferred embodiment
  • Figure 13 illustrates the display commands and responses in accordance with a preferred embodiment
  • Figure 14 presents the status values associated with various operations in accordance with a preferred embodiment.
  • Figure 15 is a communication flow diagram in accordance with a preferred embodiment.
  • the invention is preferably practiced in the context of an operating system resident on a computer such as a SUN, IBM, HP, or a
  • FIG. 1 A representative hardware environment is depicted in Figure 1, whichfillustrates a typical hardware configuration of a computer 100 in accordance with the subject invention.
  • the computer 100 is controlled by a central processing unit 102 (which may be a conventional microprocessor) and a number of other units, all interconnected via a system bus 108, are provided to accomplish specific tasks.
  • a particular computer may only have some of the units illustrated in Figure 1, or may have additional components not shown, most server computers will include at least the units shown.
  • computer 100 shown in Figure 1 includes a random access memory (RAM) 106 for temporary storage of information, a read only memory (ROM) 104 for permanent storage of the computer's configuration and basic operating commands and an input/output (I/O) adapter 110 for connecting peripheral or network devices such as a disk unit 113 and printer 114 to the bus 108, via cables 115 or peripheral bus 112, respectively.
  • a user interface adapter 116 is also provided for connecting input devices, such as a keyboard 120, and other known interface devices including mice, speakers and microphones to the bus 108.
  • Visual output is provided by a display adapter 118 which connects the bus 108 to a display device 122, such as a video monitor.
  • the computer has resident thereon and is controlled and coordinated by operating system software such as the SUN Solaris, Windows NT or JavaOS operating system.
  • FIG. 2 illustrates a client-server network in accordance with a preferred embodiment.
  • a set of consumer devices (client terminals 200) are attached to a server 210 and the server is attached to a legacy host 220 to process applications requiring information at the host 220.
  • the connection could be by means of the Internet, a dialup link, token ring, cellular phone, satellite, Tl or X.25 telco link or other communication means.
  • the sever software is written using a combination of Java, C or possibly C++. C or C++ will be used mainly to implement platform /06207
  • a server architecture in accordance with a preferred embodiment supports two types of client terminals.
  • Network terminals These are client terminals capable of directly executing the Java applications on the client terminal which are initially stored on a server. The server will simply download this code to the client's network terminal which the client will then execute to provide a particular service. This service may or may not interact with other clients or servers.
  • Network terminals can be connected to a server through a dial up modem link, directly through a local area network, or by other network communication means in accordance with a preferred embodiment.
  • Non-network terminals These are client's terminals which are not capable of executing Java applications on the client terminal. When dealing with this class of client the server will execute the
  • FIG. 3 illustrates a server architecture in accordance with a preferred embodiment.
  • a client 300 would initiate a connection with a server 350 by, for example, dialing in to a modem pool which is intercepted by the point-to-point stack software 311 which conforms information received to the TCP layer 312 which obtains a socket 313 for connecting the client 310 to the server 350.
  • the Java net layer 314 further refines the request to conform with the TERMIO and NET layer 315 which passes the request along to the application dispatcher 319.
  • the application dispatcher 319 spawns the appropriate server application selected from the server applications 330.
  • the non-network terminal initiates a "first connection" by dialing up a modem, for example.
  • the dial up goes through the native OS 316 (Solaris or Windows NT dial up layer) and is connected with the serial communication in the VFI. SERIAL layer 317 which abstracts the serial input/ output functions into a higher level communication layer.
  • the VFI.NET layer 315 takes the abstracted serial layer and maps it into a similar communication as the communication from the network terminal 300. It makes the
  • dialup asynchronous connection appear to the server application as a new socket connection.
  • Network Terminal - "First Connection" Figure 4 illustrates a client - server architecture in accordance with a preferred embodiment.
  • the architecture is illustrated initially for a network terminal for clarity and then follows with a non-network terminal.
  • Processing commences at 400 when a network terminal requests connection through a layered communication system to a set of server threads 420 which are triggered by a detection of a "ring” 430 to initiate possible client updates and the subsequent client appplication to server application processing.
  • Ring refers to a "first connection” in socket processing in accordance with a preferred embodiment.
  • the network terminal makes its connection through the Point-to- Point-Protocol stack 411 utilizing the TCP layer 412 and the sockets layer 413, which is like an electrical socket, for attaching terminals to communication sockets to facilitate communication through the network. All of this is managed by the Java.net 414 which connects the socket 1111 via the TCP layer 412 and the PPP stack 411.
  • the layer above is the VFI.net and VFI.TERMIO 415 which is responsible for detecting that the connection is made and mapping the connection to an application dispatcher 431 to further process the first connection (ring) request.
  • the server 450 waits for a "first connection” request much like an interrupt manager.
  • the application dispatcher has a method that detects a connect request or a LAN "first connection” request that would arrive through the TCP layer as a socket connect. That connection is translated into a logical ring which is equivalent to an event or interrupt.
  • the server 450 responds to the "first connection” with a query initiated by the application dispatcher 431 requesting "who are you” via an enquiry message asking for identification by the client loader thread 421.
  • the network terminal responds with ID information, including the identification of the application that the network terminal requires.
  • the client loader thread 421 performs any necessary client application updates via a download using a file transfer program such as UDP or FTP, or any other socket layer protocols that are available for network file transfers to the network terminal 400.
  • a file transfer program such as UDP or FTP, or any other socket layer protocols that are available for network file transfers to the network terminal 400.
  • Figure 5 illustrates a first client request to a server in accordance with a preferred embodiment.
  • the application dispatcher 530 spawns the corresponding server application 520 for servicing the request at the server 550 via the assigned socket 1112.
  • the server application 520 responds to the request and transmits information to the network terminal 500.
  • the application dispatcher 530 has completed its responsibilities for this client 500 and can return to a wait state until the next "first connection" request from a client.
  • the client application request could be as simple as a get current time request or a request for data from a server database.
  • FIG. 6 illustrates a network terminal 600 with a downloaded client application 610 which accesses support services in the server 650 through its assigned server application 620 in accordance with a preferred embodiment.
  • the terminal 600 communicates to a server application 620 which accesses host processing capabilities and database services 640 to service requests emanating from the client application 610.
  • the server application 620 handles any events that originate from the client application 610 via the assigned socket 1112. These events could include data requests from a database application, or data transfer to a server. Remote data from another server application could also be accessed by the client.
  • Server application 620 accesses support services directly or via a socket interface 660.
  • FIG. 7 is an architecture diagram of a client - server system in accordance with a preferred embodiment.
  • a layered communication system 700 is used by a non-network terminal 710 to detect a ring providing an indicia of communication 740 and dispatch an application 730. Dispatching an application 730 also initiates a server thread 720 for servicing the client request.
  • the non-network terminal 710 initiates a "first connection" by dialing up a modem, for example. The dial up goes through the native OS 711 (Solaris or Windows NT dial up layer) and is connected with the serial communication in the VFI.
  • SERIAL layer 712 which abstracts the serial input/output functions into a higher level communication layer.
  • the VFI.NET layer 715 takes the abstracted serial layer and maps it into a similar communication as the communication from the network terminal. It makes the dialup asynchronous connection appear to the server application as a new socket connection 1111.
  • the communication is an event 740 that triggers actions by the application dispatcher 741 which responds to the "first connection" event by requesting ID information from the client, via an enquiry message, and starting the requested client application 720 at the server 750.
  • FIG. 8 is an architecture diagram of a client - server system in accordance with a preferred embodiment.
  • the client application 822 is responsible for managing the non-network terminal 810.
  • the client application 822 writes information, utilizing a server version of VFI.TERMIO 855, to and responds to key presses by the non-network terminal 810 at the server 850.
  • the client application 822 initially makes a request for service from a socket 1112 that is associated with the non-network terminal 810 when the application dispatcher 840 spawns the client application 822.
  • the first request 845 is generated by the client application 822 residing on the server 850, at application startup, the first request for service is routed in the server 850 to the application dispacher 840 and spawns the server application 820 which will handle subsequent requests.
  • the server application 820 makes a request for service from a socket 1112 that is associated with the client application 822 which transmits an appropriate command through the VFI.TERMIO 855 to the VFI. SERIAL layer 856 using the operating system communication support 857 to the non- network terminal 810.
  • This processing is identical to the network terminal processing with the exception that all applications reside on the server 850 as opposed to a Java application executing remotely on the network terminal.
  • Java is machine independent and does not care whether a Java application resides on the client or the server.
  • the client application In the case of the non-network terminal, the client application resides in the server and controls the Java incapable terminal.
  • FIG. 9 is an architecture diagram of a client - server system in accordance with a preferred embodiment.
  • a layered communication system 900 is used by a non-network terminal 910 to manage the interconnection of a server Application 940 to a client application 920 and facilitate communication between the terminal 910 and server application 940 via a client application 920 resident on the server 950.
  • Figure 9 shows the processing after the first request has been completed and the client application 920 is coupled with the server application 940 via the assigned socket 1112 just as in the network terminal example, except the client application 920 and server application 940 both reside on the server 950.
  • a terminal responds with a message that indicates it is a non- network terminal, then the terminal is supported with the command streams described in Figures 10-14. If the terminal is a network terminal, then the application is downloaded via a FTP or other network file transfer procedure.
  • Figure 10 illustrates the structure of a packet in accordance with a preferred embodiment.
  • Figure 11 shows the format of each field of
  • I a communication and describes the contents of the same.
  • the header is two bytes in length and has various values that correspond to different types of transactions.
  • the Packet Type, Header CRC, Sequence #, Data Block and CRC- 16 fields are described in the table set forth in Figure 11.
  • Figure 12 represents a table showing additional details associated with the device types, commands and data parameters.
  • the device type field is one byte long and specifies the selected Input/ Output device.
  • Figure 13 illustrates the display commands in accordance with a preferred embodiment. The display's device type is zero.
  • Figure 14 presents the status values associated with various requested operations in accordance with a preferred embodiment.
  • FIG. 15 is a communication flow diagram in accordance with a preferred embodiment.
  • a terminal 1500 either has firmware or an application 1504 that initiates a connection 1506 with a server 1502 by contacting a dispatcher 1508.
  • the connect initiate 1506 also connects a socket 1111 to handle the connection.
  • the dispatcher 1508 transmits an identification enquiry 1510 which the client terminal replies to with an identification message 1512.
  • the client loader 1522 performs any necessary client application updates 1520 on the client terminal 1500.
  • the dispatcher starts the client application.
  • the client then sends a request to start the server application 1530 to the server which results in the connection of a socket 1112 and the server application 1550 being started and a confirmation message 1532 being transmitted back to the client application 1540. Then, when the client application 1540 requests data 1542 from the server application 1550, the server application 1550 responds with the application response data 1560.
  • Configured modem ports that will take part in transactions are pre-configured.
  • the Application Dispatcher (AD) startup code looks at this configuration stream to determine the number of S threads (serial port listeners).
  • S classes instantiate a VFI.NET. serversocket object which in turn create a VFI.NET.ModemlO.ModemPort object.
  • the ModemPort object binds to a low level VFI.NET.ModemlO.Port object which utilizes native methods to configure and wait on the communications port.
  • S threads are transient threads. And even when alive they perform efficient waits (No CPU cycles are consumed).
  • the AD receives the RequestID from each S thread. Request processing is performed by database lookup. Typically Requests, are simple text messages with delimiters and are parsed using a StringTokenizer object.
  • the AD will query a database to determine which applications should be initiated based on the enquiry message utilizing an SQL query of the form:
  • ClientThread new Thread (fieldl , f ⁇ eld2... , SOConnSocket);
  • the field list contains appropriate fields (those required for client application processing) and are passed down to the client thread along with the connected socket object.
  • Client Threads proxy the actual application.
  • Application output meant for the terminal's devices are routed out using VFI.TERMIO as directives to the client terminal's firmware.
  • the connected socket (which translates to a live dial-up connection) is passed down from the AD to the client thread.
  • Client threads are long living - usually transferring data to corresponding servlets that initiate connections to upstream hosts or make database transactions. Despite the fact that client threads can be JDBC aware, servlets handle database transactions. This helps to maintain code constancy when the same client class is downloaded to a Java capable terminal for remote execution.
  • Terminal I/O is performed through a VFI.TermlO object that in turn instantiates a VFI.TermlO. ServProtocol object.
  • the protocol object implements the actual data transfer with the client terminal.
  • the protocol object requires the socket object passed down from the AD to the client thread.
  • the AD runs a T thread (spawned off during startup) that listens on a well-known socket (e.g. 1 1 12) waiting for initi.al ClientRequests from a client application.
  • the T thread processes the ClientRequest to determine which servlet class needs loading.
  • ClientlnitialRequestListener new ServerSocket ( ⁇ wellknown socket (e.g. 1112)>);
  • HostThread HO new Thread (connSocket, "class name”); ⁇
  • the T thread is a daemon thread and lives as long as the AD lives.
  • client application is downloaded to a Java capable terminal initial requests arrive over the PPP link.
  • Host Threads service client requests for upstream and database connectivity.
  • a host thread can make TCP connections with remote hosts, forward financial transactions originating from the client application and route the response.
  • Socket upstreamSock new Socket (upstreamHost, Port);
  • the design of the PTS server aims to provide a uniform interface to third party client component and server component applet writers to the async dial-up protocol module and the
  • ModemlO classes
  • the actual modem handling code may use the TAPI client calls instead of direct Win32 communication calls.
  • Multiple libraries that conform to the same interface allow different link level protocol stacks (like MNP3). This ensures the constancy (and hence direct portability) of VFI. ModemlO.*.
  • the station address (InetAddress as in TCP/IP) is the dial string. Configure upon connection.
  • the listen port (analogous to the bound TCP port) is the COM port.
  • the valid port numbers range from 0 - OxFF (which is the maximum number of COM ports allowed in NT). Configure upon initialization.
  • Configure(String) sends out an AT command and returns TRUE if the modem returned OK ⁇ cr> ⁇ lf>.
  • configureDM(String) sends out the same command to the modem when in data mode.
  • the package encapsulates two major classes found in java.net.* - Socket and ServerSocket. To present a familiar interface and yet avoid conflicts, the package instantiates its own socket and 15 serversocket objects via constructors that take an extra parameter (that identifies the lower object that needs to be instantiated). This is illustrated after the class definition.
  • the InetAddress object refers to an unique long value that corresponds to the machines TCP/IP address.
  • the async dial-up line may however use multiple COM ports to open a connection with the host. Heuristically, it may seem that fitting the TCP/IP host/ machine address into the native COM support library will
  • InetAddress will still correspond only to a TCP/IP address.
  • the versions of the java.net. Socket constructor that accept the host name (as a String) will, instead, be overloaded. This value will now refer to a dial String that identifies the remote station address.
  • nProtocolType may take one of two values :
  • VFI.NET.serversocket ⁇ //Constructors public serversocket(int nPort, int nProtocolType); /* nProtocolType may take one of two values : PF NET #defined to 1 PF_VFI_PTS_MODEMIO #defined to 2
  • HANDLE OpenDevice int nDevNum, DCB * pNewDCB
  • void CloseDevice HANDLE TiDevice
  • int WriteDevice HANDLE hDev, int n Byte sTo Write, unsigned char * pWriteBuf
  • int ReadDevice HANDLE hDev, int nBytesToRead, unsigned char * pReadBuf
  • BOOL ConfigureDevice HANDLE hDev, DCB * pNewDCB

Abstract

A plurality of clients (200) are connected to one or more servers (210). When a client initiates a connection with a server (210), the server (210) responds to the request for connection by transmitting a message back to the client to determine whether the client is a network terminal or not. The client responds with a message that is received by an application dispatcher at the server (210) which takes one of a pair of actions based on whether the client is a network terminal. If the client terminal is a network terminal, then the application dispatcher spawns a server application in the server which responds to the client application in the client. Going forward, the server application responds to all future requests from the client application. If the client is not a network terminal, then the application dispatcher initiates a client application in the server (210) to service the client terminal application requirements. Requests from the client application on behalf of the client terminal are subsequently serviced by a server application at the server (210) which communicates to the client terminal via the client application at the server (210).

Description

A SYSTEM, METHOD AND ARTICLE OF MANUFACTURE
FOR SEAMLESS, SERVER APPLICATION SUPPORT OF
NETWORK AND NON-NETWORK CLIENT TERMINALS
COPYRIGHT NOTIFICATION
Portions of this patent application contain materials that are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document, or the patent disclosure, as it appears in the Patent and Trademark Office.
Field of the Invention
This invention generally relates to improvements in computer systems, and more particularly, to system software for managing a network of heterogeneous client terminals communicating with a server in a consistent manner.
Background of the Invention
Recently, it has become increasingly fashionable to speak of "intelligent," "smart," or "programmable" terminals and systems. Very few mainframe or peripheral manufacturers omit such a device from their standard product line. Although "intelligence," like beauty or art, is in the eye of the beholder, the adjective generally connotes that the device has a degree of autonomy or processing ability which allows it to perform certain tasks without assistance from the mainframe to which it is connected. Many such devices are programmable by virtue of including a microprocessor.
While operational devices are somewhat hazy and non-standard, a device is referred to as a terminal if a user interacts with the device to communicate to a host processor, referred to as a server in a network computing environment. Examples of terminals include keyboard /printer terminals, cathode-ray tube (CRT) terminals, remote-batch terminals, real-time data-acquisition and control terminals, transaction and point-of-sale terminals, and smart terminals.
A terminal is considered to be intelligent if it contains, hard-, firm-, and or software which allows it to perform alphanumeric or graphic message entry, display buffering, verifying, editing and block transmissions, either on host or human command. If the terminal contains a microprocessor which runs a standard program to service the terminal, and not arbitrary, user-loaded programs, the terminal has a fixed function, and is still just an intelligent terminal. Only when the device contains a general purpose computer which is easily accessible to the ordinary user for offering a wide range of programs selectable by a user or by devices attached to the device does the terminal become a network terminal in accordance with a preferred embodiment.
S- Sun has recently introduced a new language that is designed to provide consistency for network applications, named Java. Java is a general-purpose, concurrent, class-based, object-oriented programming language and support structure, specifically designed to have as few implementation dependencies as possible. Java allows application developers to write a program once and then be able to run it everywhere on a computer network.
The Java language solves many of the client-side problems by: o enabling dynamic class bindings; o providing enhanced portability of applications; and o providing a secure environment in which applications execute.
Java is compiled into bytecodes in an intermediate form instead of machine code (like C, C++, Fortran, etc.). The bytecodes execute on any machine with a Java bytecode interpreter. Thus, Java applications can run on a variety of client machines, and the bytecodes are compact and designed to transmit efficiently over a network which enhances a preferred embodiment with universal clients and server- centric policies.
With Java, developers can create robust User Interface (UI) components. Custom "widgets" (e.g. real-time stock tickers, animated icons, etc.) can be created, and client- side performance is improved. Unlike HTML, Java supports the notion of client-side validation, offloading appropriate processing onto the client for improved performance. Dynamic, real-time applications can be created using the above-mentioned components.
Sun's Java language has emerged as an industry-recognized language for "programming the Internet." Sun defines Java as: "a simple, object-oriented, distributed, interpreted, robust, secure, architecture-neutral, portable, high-performance, multithreaded, dynamic, buzzword-compliant, general-purpose programming language. Java supports programming for the Internet in the form of platform-independent Java applets." Java applets are small, specialized applications that comply with Sun's Java Application Programming Interface (API) allowing developers to add "interactive content" to Web documents (e.g. simple animations, page adornments, basic games, etc.). Applets execute within a Java- compatible browser (e.g. Netscape Navigator) by copying code from the server to client. From a language standpoint, Java's core feature set is based on C++. Sun's Java literature states that Java is basically "C++, with extensions from Objective C for more dynamic method resolution".
A network terminal in accordance with a preferred embodiment would execute Java applications in stand-alone mode, but have the capability to interact with a server for such functions as retrieving information, database processing, massive computation processing and access to shared devices such as high-speed printers, plotters and magnetic tapes.
The term "distributed computing" refers both to the devices at remote locations and to the logic which has been used to enhance the intelligence of the devices. Such distributed or decentralized computing with remote intelligent terminals and network terminals is a fact of life in today's computer literate society.
There are a number of drawbacks to distributed computing environments which are not found in a centralized computing environment. First, hardware problems: when a user locates a software solution that is optimal for the user's terminal environment, the software often will not execute on the host processor that is universally accessible by other's in a company. Moreover, the software will often be incompatible with other user's terminals.
Second, interfacing problems: a nonstandard terminal might require a special-purpose interface and might not be recognized by the host. Even standard interfaces are notorious for crashing the operating system. In any case, "mixed systems" containing multiple vendor hardware are becoming the norm, but lead to the blame for system problems being placed on the other system, and result in difficult debugging and resolving of system problems. Third, host operating system support for a heterogeneous terminal environment can be a nightmare. To provide support for all of the various protocols, communication rates and processing demands with the peculiarities intrinsic to a motley crew of downstream terminals is a system administration headache.
Fourth, local software support: this type of support ranges from minimal (say, a compiler for the particular terminal) to a mail program that is compatible with every different terminal attached to the host server. Some applications can be rebuilt for a particular terminal by simply recompiling the application, but many are only distributed as runtime modules with no support provided for some terminals.
SUMMARY OF THE INVENTION The foregoing problems are overcome in an illustrative embodiment of the invention in a network computing environment in which a plurality of clients are connected to one or more servers. When a client initiates a connection with a server, the server responds to the request for connection by transmitting a message back to the client to determine whether the client is a network terminal or not. The client responds with a message that is received by an application dispatcher at the server which takes one of a pair of actions based on whether the client is a network terminal. If the client terminal is a network terminal, then the application Λ» ,«.,„-, PCT/US97/13057 98/06207
dispatcher spawns a server application in the server which responds to the client application in the client. Going forward, the server application responds to all future requests from the client application. If the client is not a network terminal, then the application dispatcher initiates a client application in the server to service the client terminal application requirements. Requests from the client application on behalf of the client terminal are subsequently serviced by a server application at the server which communicates to the client terminal via the client application at the server.
Brief Description of the Drawings
The above and further advantages of the invention may be better understood by referring to the following description in conjunction with the accompanying drawings, in which:
Figure 1 is a block schematic diagram of a computer system for example, a personal computer system on which the inventive object oriented information manager operates;
Figure 2 illustrates a client - server network in accordance with a preferred embodiment;
Figure 3 illustrates a server architecture in accordance with a preferred embodiment;
1 Figure 4 illustrates a client - server architecture in accordance with a preferred embodiment;
Figure 5 illustrates a first client request to a server in accordance with a preferred embodiment;
Figure 6 illustrates a client server environment which accesses support services in accordance with a preferred embodiment;
Figure 7 is an architecture diagram of a client - server system in accordance with a preferred embodiment;
Figure 8 is an architecture diagram of a client - server system in accordance with a preferred embodiment;
Figure 9 is an architecture Hiagram of a client - server system in accordance with a preferred embodiment;
Figure 10 illustrate's the message format utilized in accordance with a preferred embodiment;
Figure 11 presents a table showing additional details associated with the device types, commands and data blocks in accordance with a preferred embodiment;
<s /06207
Figure 12 presents additional detail on the message format in accordance with a preferred embodiment;
Figure 13 illustrates the display commands and responses in accordance with a preferred embodiment;
Figure 14 presents the status values associated with various operations in accordance with a preferred embodiment; and
Figure 15 is a communication flow diagram in accordance with a preferred embodiment.
Detailed Description
The invention is preferably practiced in the context of an operating system resident on a computer such as a SUN, IBM, HP, or a
Windows NT computer. A representative hardware environment is depicted in Figure 1, whichfillustrates a typical hardware configuration of a computer 100 in accordance with the subject invention. The computer 100 is controlled by a central processing unit 102 (which may be a conventional microprocessor) and a number of other units, all interconnected via a system bus 108, are provided to accomplish specific tasks. Although a particular computer may only have some of the units illustrated in Figure 1, or may have additional components not shown, most server computers will include at least the units shown.
^ „„,„-„-- PCT/US97/13057 8/06207
Specifically, computer 100 shown in Figure 1 includes a random access memory (RAM) 106 for temporary storage of information, a read only memory (ROM) 104 for permanent storage of the computer's configuration and basic operating commands and an input/output (I/O) adapter 110 for connecting peripheral or network devices such as a disk unit 113 and printer 114 to the bus 108, via cables 115 or peripheral bus 112, respectively. A user interface adapter 116 is also provided for connecting input devices, such as a keyboard 120, and other known interface devices including mice, speakers and microphones to the bus 108. Visual output is provided by a display adapter 118 which connects the bus 108 to a display device 122, such as a video monitor. The computer has resident thereon and is controlled and coordinated by operating system software such as the SUN Solaris, Windows NT or JavaOS operating system.
Figure 2 illustrates a client-server network in accordance with a preferred embodiment. A set of consumer devices (client terminals 200) are attached to a server 210 and the server is attached to a legacy host 220 to process applications requiring information at the host 220. The connection could be by means of the Internet, a dialup link, token ring, cellular phone, satellite, Tl or X.25 telco link or other communication means.
Server Software The sever software is written using a combination of Java, C or possibly C++. C or C++ will be used mainly to implement platform /06207
dependent code (such as dealing with the comm ports). While a preferred embodiment discloses support for a dial up network and Internet processing utilizing TCP/IP, one of ordinary skill in the art will readily realize that a token ring, SNA or other network, such as those discussed in US Patents (5,530,961 ; 5,491 ,796; 5,457,797; 5,442,791 ; 5,430,863; 5,394,401 ; 5,291 ,597; 5,287,537; 5,287,461; 5,201 ,049; 4,991 ,089; and 4,588,21 1) could be readily interchanged as the network.
Architecture
A server architecture in accordance with a preferred embodiment supports two types of client terminals.
Network terminals. These are client terminals capable of directly executing the Java applications on the client terminal which are initially stored on a server. The server will simply download this code to the client's network terminal which the client will then execute to provide a particular service. This service may or may not interact with other clients or servers. Network terminals can be connected to a server through a dial up modem link, directly through a local area network, or by other network communication means in accordance with a preferred embodiment.
Non-network terminals. These are client's terminals which are not capable of executing Java applications on the client terminal. When dealing with this class of client the server will execute the
U application on behalf of the client. In this case the server will only expect necessary input and output operations to be performed by the client terminal. An example of how to connect a plurality of non-network terminals to a host server is described in US Patent 5,287,461 , the disclosure of which is hereby incorporated by reference in its entirety.
Figure 3 illustrates a server architecture in accordance with a preferred embodiment. A client 300 would initiate a connection with a server 350 by, for example, dialing in to a modem pool which is intercepted by the point-to-point stack software 311 which conforms information received to the TCP layer 312 which obtains a socket 313 for connecting the client 310 to the server 350. The Java net layer 314 further refines the request to conform with the TERMIO and NET layer 315 which passes the request along to the application dispatcher 319. The application dispatcher 319 spawns the appropriate server application selected from the server applications 330. On a non-network terminal, The non-network terminal initiates a "first connection" by dialing up a modem, for example. The dial up goes through the native OS 316 (Solaris or Windows NT dial up layer) and is connected with the serial communication in the VFI. SERIAL layer 317 which abstracts the serial input/ output functions into a higher level communication layer. The VFI.NET layer 315 takes the abstracted serial layer and maps it into a similar communication as the communication from the network terminal 300. It makes the
\Z_ /06207
dialup asynchronous connection appear to the server application as a new socket connection.
Network Terminal - "First Connection" Figure 4 illustrates a client - server architecture in accordance with a preferred embodiment. The architecture is illustrated initially for a network terminal for clarity and then follows with a non-network terminal. Processing commences at 400 when a network terminal requests connection through a layered communication system to a set of server threads 420 which are triggered by a detection of a "ring" 430 to initiate possible client updates and the subsequent client appplication to server application processing. "Ring" refers to a "first connection" in socket processing in accordance with a preferred embodiment.
The network terminal makes its connection through the Point-to- Point-Protocol stack 411 utilizing the TCP layer 412 and the sockets layer 413, which is like an electrical socket, for attaching terminals to communication sockets to facilitate communication through the network. All of this is managed by the Java.net 414 which connects the socket 1111 via the TCP layer 412 and the PPP stack 411. The layer above is the VFI.net and VFI.TERMIO 415 which is responsible for detecting that the connection is made and mapping the connection to an application dispatcher 431 to further process the first connection (ring) request.
\ The server 450 waits for a "first connection" request much like an interrupt manager. When a "first connection" request arrives, then the application dispatcher has a method that detects a connect request or a LAN "first connection" request that would arrive through the TCP layer as a socket connect. That connection is translated into a logical ring which is equivalent to an event or interrupt. The server 450 responds to the "first connection" with a query initiated by the application dispatcher 431 requesting "who are you" via an enquiry message asking for identification by the client loader thread 421. The network terminal responds with ID information, including the identification of the application that the network terminal requires. If the terminal answers with an identifier indicating that the terminal is a network terminal, then the client loader thread 421 performs any necessary client application updates via a download using a file transfer program such as UDP or FTP, or any other socket layer protocols that are available for network file transfers to the network terminal 400.
Network Terminal - First Client Request to Server
Figure 5 illustrates a first client request to a server in accordance with a preferred embodiment. When a first client request is transmitted from the network terminal 500 with a client
\4 application resident thereon 510 to the server 550, the application dispatcher 530 spawns the corresponding server application 520 for servicing the request at the server 550 via the assigned socket 1112. The server application 520 responds to the request and transmits information to the network terminal 500. The application dispatcher 530 has completed its responsibilities for this client 500 and can return to a wait state until the next "first connection" request from a client. The client application request could be as simple as a get current time request or a request for data from a server database.
Network Terminal - Subsequent Client Request to Server
Figure 6 illustrates a network terminal 600 with a downloaded client application 610 which accesses support services in the server 650 through its assigned server application 620 in accordance with a preferred embodiment. The terminal 600 communicates to a server application 620 which accesses host processing capabilities and database services 640 to service requests emanating from the client application 610. The server application 620 handles any events that originate from the client application 610 via the assigned socket 1112. These events could include data requests from a database application, or data transfer to a server. Remote data from another server application could also be accessed by the client. Server application 620 accesses support services directly or via a socket interface 660.
V5> Non-network Terminal - "First Connection"
Figure 7 is an architecture diagram of a client - server system in accordance with a preferred embodiment. A layered communication system 700 is used by a non-network terminal 710 to detect a ring providing an indicia of communication 740 and dispatch an application 730. Dispatching an application 730 also initiates a server thread 720 for servicing the client request. The non-network terminal 710 initiates a "first connection" by dialing up a modem, for example. The dial up goes through the native OS 711 (Solaris or Windows NT dial up layer) and is connected with the serial communication in the VFI. SERIAL layer 712 which abstracts the serial input/output functions into a higher level communication layer. The VFI.NET layer 715 takes the abstracted serial layer and maps it into a similar communication as the communication from the network terminal. It makes the dialup asynchronous connection appear to the server application as a new socket connection 1111. The communication is an event 740 that triggers actions by the application dispatcher 741 which responds to the "first connection" event by requesting ID information from the client, via an enquiry message, and starting the requested client application 720 at the server 750.
Non-network Terminal - First Client Request to Server
\^ Λ no.Λ*«M PCT/US97/13057 O 98/06207
Figure 8 is an architecture diagram of a client - server system in accordance with a preferred embodiment. The client application 822 is responsible for managing the non-network terminal 810. The client application 822 writes information, utilizing a server version of VFI.TERMIO 855, to and responds to key presses by the non-network terminal 810 at the server 850. The client application 822 initially makes a request for service from a socket 1112 that is associated with the non-network terminal 810 when the application dispatcher 840 spawns the client application 822.
When the first request 845 is generated by the client application 822 residing on the server 850, at application startup, the first request for service is routed in the server 850 to the application dispacher 840 and spawns the server application 820 which will handle subsequent requests. The server application 820 makes a request for service from a socket 1112 that is associated with the client application 822 which transmits an appropriate command through the VFI.TERMIO 855 to the VFI. SERIAL layer 856 using the operating system communication support 857 to the non- network terminal 810. This processing is identical to the network terminal processing with the exception that all applications reside on the server 850 as opposed to a Java application executing remotely on the network terminal.
One advantage of Java is that it is machine independent and does not care whether a Java application resides on the client or the server. In the case of the non-network terminal, the client application resides in the server and controls the Java incapable terminal.
Non-network Terminal - Subsequent Client Requests to Server
Figure 9 is an architecture diagram of a client - server system in accordance with a preferred embodiment. A layered communication system 900 is used by a non-network terminal 910 to manage the interconnection of a server Application 940 to a client application 920 and facilitate communication between the terminal 910 and server application 940 via a client application 920 resident on the server 950. Figure 9 shows the processing after the first request has been completed and the client application 920 is coupled with the server application 940 via the assigned socket 1112 just as in the network terminal example, except the client application 920 and server application 940 both reside on the server 950.
If a terminal responds with a message that indicates it is a non- network terminal, then the terminal is supported with the command streams described in Figures 10-14. If the terminal is a network terminal, then the application is downloaded via a FTP or other network file transfer procedure.
Figure 10 illustrates the structure of a packet in accordance with a preferred embodiment. Figure 11 shows the format of each field of
I a communication and describes the contents of the same. For example, the header is two bytes in length and has various values that correspond to different types of transactions. Similarly, the Packet Type, Header CRC, Sequence #, Data Block and CRC- 16 fields are described in the table set forth in Figure 11.
Figure 12 represents a table showing additional details associated with the device types, commands and data parameters. For example, the device type field is one byte long and specifies the selected Input/ Output device. Figure 13 illustrates the display commands in accordance with a preferred embodiment. The display's device type is zero. Figure 14 presents the status values associated with various requested operations in accordance with a preferred embodiment.
Figure 15 is a communication flow diagram in accordance with a preferred embodiment. A terminal 1500 either has firmware or an application 1504 that initiates a connection 1506 with a server 1502 by contacting a dispatcher 1508. The connect initiate 1506 also connects a socket 1111 to handle the connection. The dispatcher 1508 transmits an identification enquiry 1510 which the client terminal replies to with an identification message 1512. In the case of a network terminal, the client loader 1522 performs any necessary client application updates 1520 on the client terminal 1500. In the case of a non-network terminal, the dispatcher starts the client application. The client then sends a request to start the server application 1530 to the server which results in the connection of a socket 1112 and the server application 1550 being started and a confirmation message 1532 being transmitted back to the client application 1540. Then, when the client application 1540 requests data 1542 from the server application 1550, the server application 1550 responds with the application response data 1560.
3C> Application Dispatcher - Control Flow Application Dispatcher startup
Configured modem ports that will take part in transactions are pre-configured. The Application Dispatcher (AD) startup code looks at this configuration stream to determine the number of S threads (serial port listeners). S classes instantiate a VFI.NET. serversocket object which in turn create a VFI.NET.ModemlO.ModemPort object. The ModemPort object binds to a low level VFI.NET.ModemlO.Port object which utilizes native methods to configure and wait on the communications port.
SO
{ serversocket SOSocket - new serversocket ("socketl 1 1 1", 1); // Listener object
{ socket S0ConnSocket= SOSocket. acceptfj; //
Translates to
WaitDevice(CONNECT) ReadAhdValidate (RequestID); return RequestID, SOConnSocket;
}
}
Request Processing
> \ As illustrated above, S threads are transient threads. And even when alive they perform efficient waits (No CPU cycles are consumed). The AD receives the RequestID from each S thread. Request processing is performed by database lookup. Typically Requests, are simple text messages with delimiters and are parsed using a StringTokenizer object.
StringTokenizer stParseHelp = new StringTokenizer ((String) Request);
field 1 = stParseHelp. nextToken(); field2 = .... and so on.
The AD will query a database to determine which applications should be initiated based on the enquiry message utilizing an SQL query of the form:
"SELECT <Field ClassPath> from <TableName> where <fl = field 1 and >;
is handled by the JDBC layers to return data to the AD. The AD is now ready to run the client thread.
ClientThread = new Thread (fieldl , fιeld2... , SOConnSocket);
<_^ The field list contains appropriate fields (those required for client application processing) and are passed down to the client thread along with the connected socket object.
Client Threads
Client Threads proxy the actual application. Application output meant for the terminal's devices are routed out using VFI.TERMIO as directives to the client terminal's firmware. The connected socket (which translates to a live dial-up connection) is passed down from the AD to the client thread. Client threads are long living - usually transferring data to corresponding servlets that initiate connections to upstream hosts or make database transactions. Despite the fact that client threads can be JDBC aware, servlets handle database transactions. This helps to maintain code constancy when the same client class is downloaded to a Java capable terminal for remote execution.
Terminal I/O is performed through a VFI.TermlO object that in turn instantiates a VFI.TermlO. ServProtocol object. The protocol object implements the actual data transfer with the client terminal. The protocol object requires the socket object passed down from the AD to the client thread.
CO (Appropriate Request fields, SOConnSocket) (
£> VFI.TermlO IOObject = new TermlO (SOConnSocket); //IO object / /instantiation. This cascades into a ServProtocol
Object instantiation.
lOObject.WriteString (Stringlndex); //Displays a particular string on the P-ATM.
//If the client needs to retrieve data from upstream hosts (OmniHost, VISA etc), //or needs data from a database it makes a TCP stream connection to a servlet.
/ /This is consistent with the behavior of the network terminal which would //make the same connection over PPP. clienTransObject = new Socket (<Host>, <Well known socket>); / / Explained further down under initial client requests
//Further processing
/ / Send out host requests clienTransObject.write (HostRequest); clienTransObject.read (HostResponse); lOObject.WriteString (Striήglndex + n); //Displays status on the P-ATM.
}
3^ Initial Client Request processing
The AD runs a T thread (spawned off during startup) that listens on a well-known socket (e.g. 1 1 12) waiting for initi.al ClientRequests from a client application. The T thread processes the ClientRequest to determine which servlet class needs loading.
T
{ ClientlnitialRequestListener = new ServerSocket (<wellknown socket (e.g. 1112)>);
/ / Wait for initial requests and spawn off server connSocket = ClientlnitialRequestListener. acceptQ;
connSocket. Stream. read (InitialRequest); Parse (InitialRequest);
HostThread HO = new Thread (connSocket, "class name"); }
The T thread is a daemon thread and lives as long as the AD lives. When the client application is downloaded to a Java capable terminal initial requests arrive over the PPP link.
3 Host Threads or Servlets
Host Threads (H) service client requests for upstream and database connectivity. A host thread can make TCP connections with remote hosts, forward financial transactions originating from the client application and route the response.
HO (connSocket)
{ connSocket. Stream. read (ClientRequest);
ParseRequest (StringTokenizer);
Socket upstreamSock = new Socket (upstreamHost, Port);
//Transact
connSocket. Stream. Write (HostResponse);
}
Transient and Long-living Threads in the Application Dispatcher
A sockets based abstraction of the Win32 Communication API
Consistence in the access of transport layer services needs no over emphasis. The design of the PTS server aims to provide a uniform interface to third party client component and server component applet writers to the async dial-up protocol module and the
3le> system's TCP/SLIP/PPP stack. This interface comprises a set of Java Classes collectively called VFI.NET.*. It should be noted that this package does not provide pure TCP/UDP/IP specific objects and methods that are already defined and implemented in java.net.*. Programmers, however, do not need to explicitly import java.net.*. This is automatically done by the package. Further, this document does not discuss the functionality of java.net.* which may be found in the appropriate JDK documentation. It, merely, details a class design that overloads methods specifically necessary to build a BSD sockets like layer between calling applets (servlets) and the machine specific Java serial communications package.
Hierarchy A uniform upper edge interface for the ModemlO classes permits easy replacement of the implementation. The actual modem handling code, for instance, may use the TAPI client calls instead of direct Win32 communication calls. Multiple libraries that conform to the same interface allow different link level protocol stacks (like MNP3). This ensures the constancy (and hence direct portability) of VFI. ModemlO.*.
Required ModemlO Functionality
1. Open an end-to-end async, duplex dial-up connection. The station address (InetAddress as in TCP/IP) is the dial string. Configure upon connection.
2 - 2. Listen for an incoming dial-up connection. The listen port (analogous to the bound TCP port) is the COM port. In this regard the valid port numbers range from 0 - OxFF (which is the maximum number of COM ports allowed in NT). Configure upon initialization.
3. Obtain Input and Output streams that re-direct from/ to the open connection.
4. Hang-up (close as in TCP/IP) a live connection.
The following classes form a part of VFI. ModemlO.* :-
Raw Serial Port Handling public class VFI. ModemlO. Port
{
//Contructors public Port (int nPortNum); public Port (i t nPortNum, int nBaud, int nParity, int nDataBits, int nStopBits); public Port (int nPortNum, String sCfgStr); public Port (String sPortName); public Port (String sPortName, String sCfgStr);
S& //Methods public void closeQ; public int getPortID(); public String getPortNamefJ; public String getCfgStr(); public InputStream getInputStream(); public OutputStream getOutputStreamQ;
Modem initialization and methods public class VFI. ModemlO. ModemPort
{
/ /Constructors public ModemPort (int nPortNum); public ModemPort (Port objPort); public ModemPort (String sPortName); public ModemPort (int nPortNum, String sInitString); public ModemPort (Port objPort, String sInitString); public ModemPort (String sPortName, String sInitString);
//Methods public Port getPort(); public boolean connect (String sDialString); public void disconnect(); public void reset(); public boolean configure (String sCfgStr);
ct\ „,Λ MBrtWI PCT/US97/13057
WO 98/06207
public boolean configureDM (String sCfgStr);
Programmers must use getPort() to capture a stream and transfer data over the ModemPort. Configure(String) sends out an AT command and returns TRUE if the modem returned OK<cr><lf>. configureDM(String) sends out the same command to the modem when in data mode.
10
NET - The Sockets wrapper
The package encapsulates two major classes found in java.net.* - Socket and ServerSocket. To present a familiar interface and yet avoid conflicts, the package instantiates its own socket and 15 serversocket objects via constructors that take an extra parameter (that identifies the lower object that needs to be instantiated). This is illustrated after the class definition.
Station address resolution
20 The InetAddress object refers to an unique long value that corresponds to the machines TCP/IP address. The async dial-up line may however use multiple COM ports to open a connection with the host. Heuristically, it may seem that fitting the TCP/IP host/ machine address into the native COM support library will
25 permit overloading of InetAddress and hence enhance elegance. This, however, results in extra and avoidable complexity. In this
3 regard, InetAddress will still correspond only to a TCP/IP address. The versions of the java.net. Socket constructor that accept the host name (as a String) will, instead, be overloaded. This value will now refer to a dial String that identifies the remote station address.
Socket initialization and connection public class VFI. ET. socket
{
/ /Constructors public socket (String sHost, int nPort, int n Pro toco-Type);
/* nProtocolType may take one of two values :
PFJNET #defined to 1
PF_VFI_PTS_MODEMIO ^defined to 2
Passing a value of 0 causes the use of java.net. Socket.*/
/ /Methods public void close (); public String getStationAddress(); public int getPortfJ; public InputStream getInputStreειm(); public OutputStream getOutputStream(); }
public class VFI.NET.serversocket { //Constructors public serversocket(int nPort, int nProtocolType); /* nProtocolType may take one of two values : PF NET #defined to 1 PF_VFI_PTS_MODEMIO #defined to 2
Passing a value of 0 causes the use of java.net.ServerSocket.*/
//Methods public socket acceptfj; public void closefj; public int getPortfJ; }
Interface Library to native Win32 Comm. API methods
HANDLE OpenDevice (int nDevNum, DCB * pNewDCB); void CloseDevice (HANDLE TiDevice); int WriteDevice (HANDLE hDev, int n Byte sTo Write, unsigned char * pWriteBuf); int ReadDevice (HANDLE hDev, int nBytesToRead, unsigned char * pReadBuf); BOOL ConfigureDevice (HANDLE hDev, DCB * pNewDCB);
15 - While the invention is described in terms of preferred embodiments in a specific system environment, those skilled in the art will recognize that the invention can be practiced, with modification, in other and different hardware and software environments within the spirit and scope of the appended claims.
Zm?-X

Claims

CLAIMSHaving thus described our invention, what we claim as new, and desire to secure by Letters Patent is:
1. A distributed computer system including a client terminal and a server which communicate via a network, comprising: (a) the client terminal initiating connection to the server computer utilizing the network; (b) the server responding to the initial connection by transmitting an enquiry message to the client terminal; (c) the client terminal responding to the enquiry message with a message comprising identification information indicative of the client terminal being a network terminal or a non- network terminal and identifying a client application the client terminal requires; (d) the server receiving and analyzing the identification information to determine if the client terminal is a network terminal or a non-network terminal; and (d l) if the client terminal is a network terminal, then the client loader on the server updates the client application, if necessary, on the client terminal utilizing the network and starts the server application to service future requests from the client terminal; and (d2) if the client terminal is a non-network terminal, then the server initiates the client application and server
54 application on the server for processing the application at the server for the client terminal.
2. The distributed computer system as recited in claim 1, wherein the update of the client application entails a download of the client application to the client terminal.
3. The distributed computer system as recited in claim 1 , in which the client terminal communicates to the server utilizing a dial-up network connection.
4. The distributed computer system as recited in claim 1 , wherein the identification information comprises configuration characteristics of the client terminal.
5. The distributed computer system as recited in claim 1 , wherein the network terminal executes Java code on the network terminal.
- 5
6. The distributed computer system as recited in claim 1 , wherein the same client application is executed on the server computer and the client terminal.
7. The distributed computer system as recited in claim 1 , wherein the non-network terminal receives commands from the client application on the server.
8. The distributed computer system as recited in claim 1 , including means for passing a client application request to another server to process the request.
--
9. A method for distributing computing between a server computer and a client terminal which communicate via a network, comprising the steps of: (a) initiating connection of the client terminal to the server computer utilizing the network; (b) responding to the initial connection request at the server computer by transmitting an enquiry message to the client terminal; (c) responding to the enquiry message at the client terminal with a message comprising identification information indicative of the client terminal being a network terminal or a non-network terminal and identifying a client application the client terminal requires; (d) receiving and analyzing the identification information at the server computer to determine if the client terminal is a network terminal or a non-network terminal; and (d 1) loading a server application if the client terminal is a network terminal, which starts the client application and services future requests from the client terminal; and (d2) loading a server application on the server, if necessary, which initiates a client application on the server for processing the client application at the server on behalf of the client terminal, if the client terminal is a non-network terminal. w
10. The method as recited in claim 9, wherein the update of the client application entails a download of the client application to the client terminal.
11. The method as recited in claim 9, including the step of communicating between the client terminal and the server utilizing a dial-up network connection.
12. The method as recited in claim 9, wherein the identification information comprises configuration characteristics of the client terminal.
13. The method as recited in claim 9, wherein the network terminal executes Java code on the network terminal.
14. The method as recited in claim 9, wherein the same client application is executed on the server computer and the client terminal.
15. The method as recited in claim 9, wherein the non-network terminal receives commands from the client application on the server.
rb 06207
16. The method as recited in claim 9, including the step of passing a client application request to another server to process the request.
17. A computer program embodied on a computer-readable medium for enabling a distributed computing system, including a client terminal and a server which communicate via a network, comprising: (a) a code segment for initiating connection of the client terminal to the server computer utilizing the network; (b) a code segment for responding to the initial connection request at the server computer by transmitting an enquiry message to the client terminal; (c) a code segment for responding to the enquiry message at the client terminal with a message comprising identification information indicative of the client terminal being a network terminal or a non-network terminal and identifying a client application the client terminal requires; (d) a code segment for receiving and analyzing the identification information at the server computer to determine if the client terminal is a network terminal or a non-network terminal; and (d l) a code segment for loading a server application if the client terminal is a network terminal, which updates the client application and services future requests from the client terminal; and
SI 06207
(d2) a code segment for loading a server application, if necessary, on the server which initiates the client application on the server for processing the client application at the server on behalf of the client terminal, if the client terminal is a non-network terminal.
18. The computer program as recited in claim 17, wherein the update of the client application entails a download of the client application to the client terminal.
19. The computer program as recited in claim 17, including a code segment for communicating between the client terminal and the server utilizing a dial-up network connection.
20. The computer program as recited in claim 17, wherein the identification information comprises configuration characteristics of the client terminal.
21. The computer program as recited in claim 17, wherein the network terminal executes Java code on the network terminal.
22. The computer program as recited in claim 17, wherein the same client application is executed on the server computer and the client terminal.
MO
23. The computer program as recited in claim 17, wherein the non-network terminal receives commands from the client application on the server.
24. The computer program as recited in claim 17, including a code segment for passing a client application request to another server to process the request.
25. The computer program as recited in claim 17, including a code segment for making a dial up connection appear to the server as a socket connection.
M \
PCT/US1997/013057 1996-08-06 1997-08-06 A system, method and article of manufacture for seamless, server application support of network and non-network client terminals WO1998006207A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP97937021A EP0919092B1 (en) 1996-08-06 1997-08-06 A system, method and article of manufacture for seamless, server application support of network and non-network client terminals
DE69732968T DE69732968T2 (en) 1996-08-06 1997-08-06 SYSTEM, METHOD AND MANUFACTURED OBJECT FOR MAINTAINING SERVER APPLICATION SOFTWARE OF NETWORK CUSTOM END USERS AND NON-NETWORK CUSTOMER DEVICES
AU39638/97A AU730088B2 (en) 1996-08-06 1997-08-06 A system, method and article of manufacture for seamless, server application support of network and non-network client terminals
HK99102575A HK1017539A1 (en) 1996-08-06 1999-06-15 A system, method and article of manufacture for seamless, server application support of network and non-network client terminals.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/692,489 US5828840A (en) 1996-08-06 1996-08-06 Server for starting client application on client if client is network terminal and initiating client application on server if client is non network terminal
US08/692,489 1996-08-06

Publications (1)

Publication Number Publication Date
WO1998006207A1 true WO1998006207A1 (en) 1998-02-12

Family

ID=24780790

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/013057 WO1998006207A1 (en) 1996-08-06 1997-08-06 A system, method and article of manufacture for seamless, server application support of network and non-network client terminals

Country Status (6)

Country Link
US (1) US5828840A (en)
EP (1) EP0919092B1 (en)
AU (1) AU730088B2 (en)
DE (1) DE69732968T2 (en)
HK (1) HK1017539A1 (en)
WO (1) WO1998006207A1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999054804A2 (en) * 1998-04-20 1999-10-28 Sun Microsystems, Inc. Method and apparatus for providing a virtual desktop system architecture
EP0965927A2 (en) * 1998-06-18 1999-12-22 Sun Microsystems, Inc. Client intermediation of server applications
EP0978976A2 (en) * 1998-07-22 2000-02-09 Hewlett-Packard Company An application dispatcher for server application
WO2000018092A1 (en) * 1998-09-24 2000-03-30 Ericsson Inc. Multi-client object-oriented interface layer
EP1119157A2 (en) * 2000-01-20 2001-07-25 Sony Corporation Terminal device, apparatus and method for controlling a terminal device, and method of controlling a process in a terminal device
WO2014164122A1 (en) * 2013-03-11 2014-10-09 Microsoft Corporation Unified game preview

Families Citing this family (163)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10361802B1 (en) 1999-02-01 2019-07-23 Blanding Hovenweep, Llc Adaptive pattern recognition based control system and method
US6088515A (en) 1995-11-13 2000-07-11 Citrix Systems Inc Method and apparatus for making a hypermedium interactive
US6437803B1 (en) 1998-05-29 2002-08-20 Citrix Systems, Inc. System and method for combining local and remote windows into a single desktop environment
US6950991B2 (en) 1995-11-13 2005-09-27 Citrix Systems, Inc. Interacting with software applications displayed in a web page
US6370552B1 (en) 1997-05-14 2002-04-09 Citrix Systems, Inc. Apparatus and method for displaying application output in an HTML document
EP0979458A4 (en) * 1996-05-14 2000-05-03 Ricoh Corp Ltd Java printer
US8229844B2 (en) 1996-06-05 2012-07-24 Fraud Control Systems.Com Corporation Method of billing a purchase made over a computer network
US7555458B1 (en) 1996-06-05 2009-06-30 Fraud Control System.Com Corporation Method of billing a purchase made over a computer network
US20030195847A1 (en) 1996-06-05 2003-10-16 David Felger Method of billing a purchase made over a computer network
US5867153A (en) 1996-10-30 1999-02-02 Transaction Technology, Inc. Method and system for automatically harmonizing access to a software application program via different access devices
US7249344B1 (en) * 1996-10-31 2007-07-24 Citicorp Development Center, Inc. Delivery of financial services to remote devices
US7668781B2 (en) 1996-10-31 2010-02-23 Citicorp Development Center, Inc. Global method and system for providing enhanced transactional functionality through a customer terminal
US8112330B1 (en) 1997-08-07 2012-02-07 Citibank Development Center, Inc. System and method for delivering financial services
US6131116A (en) * 1996-12-13 2000-10-10 Visto Corporation System and method for globally accessing computer services
US20060195595A1 (en) 2003-12-19 2006-08-31 Mendez Daniel J System and method for globally and securely accessing unified information in a computer network
US6708221B1 (en) 1996-12-13 2004-03-16 Visto Corporation System and method for globally and securely accessing unified information in a computer network
US7287271B1 (en) * 1997-04-08 2007-10-23 Visto Corporation System and method for enabling secure access to services in a computer network
US6125384A (en) * 1996-12-23 2000-09-26 International Business Machines Corporation Computer apparatus and method for communicating between software applications and computers on the world-wide web
US6901425B1 (en) 1996-12-23 2005-05-31 International Business Machines Corporation Computer apparatus and method including a disconnect mechanism for communicating between software applications and computers on the world-wide web
US6253228B1 (en) * 1997-03-31 2001-06-26 Apple Computer, Inc. Method and apparatus for updating and synchronizing information between a client and a server
US6041356A (en) * 1997-03-31 2000-03-21 Intel Corporation Method and apparatus for detecting network traffic and initiating a dial-up connection using separate upstream and downstream devices
US6766454B1 (en) 1997-04-08 2004-07-20 Visto Corporation System and method for using an authentication applet to identify and authenticate a user in a computer network
US5941949A (en) * 1997-05-14 1999-08-24 Citrix Systems, Inc. System and method for transmitting data from a server application to more than one client node
US6157944A (en) * 1997-05-14 2000-12-05 Citrix Systems, Inc. System and method for replicating a client/server data exchange to additional client notes connecting to the server
US6205469B1 (en) * 1997-05-27 2001-03-20 Yahoo! Inc. Method for client-server communications through a minimal interface
US7502752B1 (en) 1997-08-07 2009-03-10 Citicorp Development Center, Inc. System and method for delivering financial services
US6697868B2 (en) * 2000-02-28 2004-02-24 Alacritech, Inc. Protocol processing stack for use with intelligent network interface device
US6324574B1 (en) * 1997-11-07 2001-11-27 International Business Machines Corporation Relay server for unsigned applets
JPH11232349A (en) * 1997-11-18 1999-08-27 Sun Microsyst Inc System and method for managing service request for equipment and computer readable medium storing instruction sequence for managing equipment service request
US6012098A (en) * 1998-02-23 2000-01-04 International Business Machines Corp. Servlet pairing for isolation of the retrieval and rendering of data
US6834388B1 (en) 1998-03-13 2004-12-21 Iconics, Inc. Process control
US6324685B1 (en) 1998-03-18 2001-11-27 Becomm Corporation Applet server that provides applets in various forms
US6098093A (en) * 1998-03-19 2000-08-01 International Business Machines Corp. Maintaining sessions in a clustered server environment
US6243738B1 (en) * 1998-04-06 2001-06-05 National Instruments Corporation Data acquisition system which includes remote access to data acquisition devices
US6011916A (en) * 1998-05-12 2000-01-04 International Business Machines Corp. Java I/O toolkit for applications and applets
US6233341B1 (en) 1998-05-19 2001-05-15 Visto Corporation System and method for installing and using a temporary certificate at a remote site
US6405367B1 (en) * 1998-06-05 2002-06-11 Hewlett-Packard Company Apparatus and method for increasing the performance of Java programs running on a server
US6751647B1 (en) * 1998-06-19 2004-06-15 Intel Corporation Method and apparatus for automated data exchange between a user computer and a provider computer using improved object-oriented programming components
US6181692B1 (en) * 1998-09-03 2001-01-30 Genesys Telecommunications Laboratories Inc Method and apparatus for data routing, delivery, and authentication in a packet data network
US6782431B1 (en) * 1998-09-30 2004-08-24 International Business Machines Corporation System and method for dynamic selection of database application code execution on the internet with heterogenous clients
US7533064B1 (en) * 1998-10-07 2009-05-12 Paypal Inc. E-mail invoked electronic commerce
US6470346B2 (en) * 1998-10-07 2002-10-22 Millennium Pharmaceuticals, Inc. Remote computation framework
US7003558B2 (en) 1998-10-16 2006-02-21 Iconics, Inc. Method and system for communicating information and controlling equipment according to a standard protocol between two computers
US6138160A (en) * 1998-10-23 2000-10-24 International Business Machines Corporation System with wake up server and wake up monitor for facilitating dial up connection between two application partners via internet
US6349333B1 (en) 1998-12-04 2002-02-19 Sun Microsystems, Inc. Platform independent alarm service for manipulating managed objects in a distributed network management system
US6282568B1 (en) * 1998-12-04 2001-08-28 Sun Microsystems, Inc. Platform independent distributed management system for manipulating managed objects in a network
US6356282B2 (en) 1998-12-04 2002-03-12 Sun Microsystems, Inc. Alarm manager system for distributed network management system
US6757747B1 (en) * 1998-12-17 2004-06-29 International Business Machines Corporation Proxy object for managing an application instance on a dataless client machine
US6236909B1 (en) * 1998-12-28 2001-05-22 International Business Machines Corporation Method for representing automotive device functionality and software services to applications using JavaBeans
US6928469B1 (en) 1998-12-29 2005-08-09 Citrix Systems, Inc. Apparatus and method for determining a program neighborhood for a client node in a client-server network using markup language techniques
US7017116B2 (en) 1999-01-06 2006-03-21 Iconics, Inc. Graphical human-machine interface on a portable device
US6286031B1 (en) * 1999-01-21 2001-09-04 Jerry Richard Waese Scalable multimedia distribution method using client pull to retrieve objects in a client-specific multimedia list
US6473894B1 (en) 1999-01-29 2002-10-29 International Business Machines Corporation Dynamic runtime and test architecture for Java applets
SG94330A1 (en) 1999-07-24 2003-02-18 Kent Ridge Digital Labs Mobile computing system and method for a network
US6745247B1 (en) 1999-03-19 2004-06-01 Citicorp Development Center, Inc. Method and system for deploying smart card applications over data networks
US6385739B1 (en) 1999-07-19 2002-05-07 Tivo Inc. Self-test electronic assembly and test system
US7373517B1 (en) 1999-08-19 2008-05-13 Visto Corporation System and method for encrypting and decrypting files
JP3478200B2 (en) * 1999-09-17 2003-12-15 日本電気株式会社 Two-way communication system between server and client
US6654748B1 (en) 1999-12-07 2003-11-25 Rwd Technologies, Inc. Dynamic application browser and database for use therewith
US20020184057A1 (en) * 2000-05-31 2002-12-05 Sony Corporation System, apparatus, and method for providing insurance design service
US20020032706A1 (en) * 1999-12-23 2002-03-14 Jesse Perla Method and system for building internet-based applications
KR100379889B1 (en) * 2000-02-25 2003-04-14 조도원 Computer advertising method with advertisement exclusive program
US8036905B2 (en) * 2000-02-29 2011-10-11 Newgistics, Inc. Method and system for processing the local return of remotely purchased products
US8386337B2 (en) * 2000-03-24 2013-02-26 Newgistics, Inc. System and method for single-action returns of remotely purchased merchandise
US20010047387A1 (en) * 2000-03-27 2001-11-29 Exoplex, Inc. Systems and methods for providing distributed cross-enterprise portals
US6785713B1 (en) 2000-05-08 2004-08-31 Citrix Systems, Inc. Method and apparatus for communicating among a network of servers utilizing a transport mechanism
US6789112B1 (en) 2000-05-08 2004-09-07 Citrix Systems, Inc. Method and apparatus for administering a server having a subsystem in communication with an event channel
US6922724B1 (en) 2000-05-08 2005-07-26 Citrix Systems, Inc. Method and apparatus for managing server load
US6785726B1 (en) 2000-05-08 2004-08-31 Citrix Systems, Inc. Method and apparatus for delivering local and remote server events in a similar fashion
US8176145B1 (en) * 2000-05-19 2012-05-08 The Travelers Indemnity Company System and method for providing insurance data processing services via a user interface
US7699699B2 (en) 2000-06-23 2010-04-20 Igt Gaming device having multiple selectable display interfaces based on player's wagers
US7695363B2 (en) 2000-06-23 2010-04-13 Igt Gaming device having multiple display interfaces
US7225231B2 (en) 2000-09-20 2007-05-29 Visto Corporation System and method for transmitting workspace elements across a network
AU2001296993A1 (en) * 2000-10-05 2002-04-15 Christopher Peiffer Connection management system and method
US7263550B1 (en) 2000-10-10 2007-08-28 Juniper Networks, Inc. Agent-based event-driven web server architecture
US7464045B2 (en) * 2001-02-14 2008-12-09 The Workplace Helpline, Llc Method and apparatus for managing workplace services and products
US7181017B1 (en) 2001-03-23 2007-02-20 David Felsher System and method for secure three-party communications
US7143164B2 (en) 2001-05-21 2006-11-28 Exigen Group Dynamic object library software architecture
US7716091B2 (en) 2001-05-24 2010-05-11 Newgistics, Inc. Local returns of remotely purchased merchandise with return code validation
US7110525B1 (en) 2001-06-25 2006-09-19 Toby Heller Agent training sensitive call routing system
WO2003017123A1 (en) * 2001-08-16 2003-02-27 Redline Networks, Inc. System and method for maintaining statefulness during client-server interactions
US7000027B2 (en) * 2001-11-29 2006-02-14 International Business Machines Corporation System and method for knowledgeable node initiated TCP splicing
KR100606946B1 (en) * 2001-11-30 2006-08-01 후지쓰 텐 가부시키가이샤 Microcomputer logic developing apparatus
US8190530B2 (en) 2002-01-30 2012-05-29 Visa U.S.A. Inc. Method and system for providing multiple services via a point-of-sale portal architecture
US7372952B1 (en) 2002-03-07 2008-05-13 Wai Wu Telephony control system with intelligent call routing
US8135843B2 (en) * 2002-03-22 2012-03-13 Citrix Systems, Inc. Methods and systems for providing access to an application
JP2003280902A (en) * 2002-03-25 2003-10-03 Fujitsu Ten Ltd Microcomputer logic development system and its program
US9818136B1 (en) 2003-02-05 2017-11-14 Steven M. Hoffberg System and method for determining contingent relevance
US20040193438A1 (en) * 2003-02-10 2004-09-30 Stashluk Edward J. Merchandise return system with value added returns processing (dispositioning)
US20040215531A1 (en) * 2003-02-10 2004-10-28 Stashluk Edward J. Computer generated merchandise return labels with rules-based coding
US20040193436A1 (en) * 2003-02-10 2004-09-30 Stashluk Edward J. Method and system using return labels with dynamically generated multiple datapoint coding
US20040181310A1 (en) * 2003-02-10 2004-09-16 Stashluk Edward J. Merchandise return system with value added returns processing (data communications)
US7676034B1 (en) 2003-03-07 2010-03-09 Wai Wu Method and system for matching entities in an auction
US7403300B2 (en) * 2003-03-21 2008-07-22 Toshiba Corporation Wireless wide area network printing
US7978716B2 (en) 2003-11-24 2011-07-12 Citrix Systems, Inc. Systems and methods for providing a VPN solution
US20050149738A1 (en) * 2004-01-02 2005-07-07 Targosky David G. Biometric authentication system and method for providing access to a KVM system
US20050261969A1 (en) * 2004-05-10 2005-11-24 International Business Machines Corporation Layered architecture for POS (point-of sale) systems
US8090837B2 (en) 2004-05-27 2012-01-03 Hewlett-Packard Development Company, L.P. Communication in multiprocessor using proxy sockets
US7757074B2 (en) 2004-06-30 2010-07-13 Citrix Application Networking, Llc System and method for establishing a virtual private network
US8739274B2 (en) 2004-06-30 2014-05-27 Citrix Systems, Inc. Method and device for performing integrated caching in a data communication network
US8495305B2 (en) 2004-06-30 2013-07-23 Citrix Systems, Inc. Method and device for performing caching of dynamically generated objects in a data communication network
US7808906B2 (en) 2004-07-23 2010-10-05 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol using false acknowledgements
CN101199187A (en) 2004-07-23 2008-06-11 茨特里克斯系统公司 A method and systems for securing remote access to private networks
US20060181026A1 (en) * 2005-02-14 2006-08-17 Wong Jacob Y Chinese poker deck
US8021230B2 (en) 2004-08-19 2011-09-20 Igt Gaming system having multiple gaming machines which provide bonus awards
US8251791B2 (en) 2004-08-19 2012-08-28 Igt Gaming system having multiple gaming machines which provide bonus awards
US7963847B2 (en) 2004-08-19 2011-06-21 Igt Gaming system having multiple gaming machines which provide bonus awards
US7748032B2 (en) 2004-09-30 2010-06-29 Citrix Systems, Inc. Method and apparatus for associating tickets in a ticket hierarchy
US7680758B2 (en) 2004-09-30 2010-03-16 Citrix Systems, Inc. Method and apparatus for isolating execution of software applications
US8171479B2 (en) 2004-09-30 2012-05-01 Citrix Systems, Inc. Method and apparatus for providing an aggregate view of enumerated system resources from various isolation layers
US7711835B2 (en) * 2004-09-30 2010-05-04 Citrix Systems, Inc. Method and apparatus for reducing disclosure of proprietary data in a networked environment
US8613048B2 (en) 2004-09-30 2013-12-17 Citrix Systems, Inc. Method and apparatus for providing authorized remote access to application sessions
US8095940B2 (en) 2005-09-19 2012-01-10 Citrix Systems, Inc. Method and system for locating and accessing resources
US7752671B2 (en) * 2004-10-04 2010-07-06 Promisec Ltd. Method and device for questioning a plurality of computerized devices
US8706877B2 (en) 2004-12-30 2014-04-22 Citrix Systems, Inc. Systems and methods for providing client-side dynamic redirection to bypass an intermediary
US20060149577A1 (en) * 2004-12-30 2006-07-06 Newgistics, Inc. System and method for the customized processing of returned merchandise
US8700695B2 (en) 2004-12-30 2014-04-15 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP pooling
US8549149B2 (en) 2004-12-30 2013-10-01 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP multiplexing
US8954595B2 (en) 2004-12-30 2015-02-10 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP buffering
US7810089B2 (en) 2004-12-30 2010-10-05 Citrix Systems, Inc. Systems and methods for automatic installation and execution of a client-side acceleration program
KR20070104566A (en) 2005-01-24 2007-10-26 사이트릭스 시스템스, 인크. Systems and methods for performing caching of dynamically generated objects in a network
US8255456B2 (en) 2005-12-30 2012-08-28 Citrix Systems, Inc. System and method for performing flash caching of dynamically generated objects in a data communication network
US8024568B2 (en) 2005-01-28 2011-09-20 Citrix Systems, Inc. Method and system for verification of an endpoint security scan
US20070055562A1 (en) * 2005-08-23 2007-03-08 Way Out World, Llc System and methods for multi-modal game augmented interactive marketing
US8137188B2 (en) 2005-09-09 2012-03-20 Igt Server based gaming system having multiple progressive awards
US7841939B2 (en) 2005-09-09 2010-11-30 Igt Server based gaming system having multiple progressive awards
US8128491B2 (en) 2005-09-09 2012-03-06 Igt Server based gaming system having multiple progressive awards
US8874477B2 (en) 2005-10-04 2014-10-28 Steven Mark Hoffberg Multifactorial optimization system and method
US8131825B2 (en) 2005-10-07 2012-03-06 Citrix Systems, Inc. Method and a system for responding locally to requests for file metadata associated with files stored remotely
US7779034B2 (en) 2005-10-07 2010-08-17 Citrix Systems, Inc. Method and system for accessing a remote file in a directory structure associated with an application program executing locally
US20070157019A1 (en) * 2005-12-30 2007-07-05 Intel Corporation Location-based network access
US8301839B2 (en) 2005-12-30 2012-10-30 Citrix Systems, Inc. System and method for performing granular invalidation of cached dynamically generated objects in a data communication network
US7921184B2 (en) 2005-12-30 2011-04-05 Citrix Systems, Inc. System and method for performing flash crowd caching of dynamically generated objects in a data communication network
US20070174429A1 (en) 2006-01-24 2007-07-26 Citrix Systems, Inc. Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment
US8300798B1 (en) 2006-04-03 2012-10-30 Wai Wu Intelligent communication routing system and method
US8512130B2 (en) 2006-07-27 2013-08-20 Igt Gaming system with linked gaming machines that are configurable to have a same probability of winning a designated award
US7674180B2 (en) 2006-09-27 2010-03-09 Igt Server based gaming system having system triggered loyalty award sequences
US8616959B2 (en) 2006-09-27 2013-12-31 Igt Server based gaming system having system triggered loyalty award sequences
US7862430B2 (en) 2006-09-27 2011-01-04 Igt Server based gaming system having system triggered loyalty award sequences
US8738703B2 (en) 2006-10-17 2014-05-27 Citrix Systems, Inc. Systems and methods for providing online collaborative support
US8533846B2 (en) 2006-11-08 2013-09-10 Citrix Systems, Inc. Method and system for dynamically associating access rights with a resource
US8566247B1 (en) 2007-02-19 2013-10-22 Robert H. Nagel System and method for secure communications involving an intermediary
US8521650B2 (en) * 2007-02-26 2013-08-27 Zepfrog Corp. Method and service for providing access to premium content and dispersing payment therefore
US7985133B2 (en) 2007-07-30 2011-07-26 Igt Gaming system and method for providing an additional gaming currency
US8900053B2 (en) 2007-08-10 2014-12-02 Igt Gaming system and method for providing different bonus awards based on different types of triggered events
US8171483B2 (en) 2007-10-20 2012-05-01 Citrix Systems, Inc. Method and system for communicating between isolation environments
US9142097B2 (en) 2007-10-26 2015-09-22 Igt Gaming system and method for providing play of local first game and remote second game
KR101545137B1 (en) * 2008-04-17 2015-08-19 삼성전자주식회사 Method and apparatus for generating user interface
US8312033B1 (en) 2008-06-26 2012-11-13 Experian Marketing Solutions, Inc. Systems and methods for providing an integrated identifier
US8149431B2 (en) * 2008-11-07 2012-04-03 Citrix Systems, Inc. Systems and methods for managing printer settings in a networked computing environment
US8090797B2 (en) 2009-05-02 2012-01-03 Citrix Systems, Inc. Methods and systems for launching applications into existing isolation environments
US9039516B2 (en) 2009-07-30 2015-05-26 Igt Concurrent play on multiple gaming machines
US9116778B2 (en) 2010-04-29 2015-08-25 Microsoft Technology Licensing, Llc Remotable project
US9104514B2 (en) * 2011-01-11 2015-08-11 International Business Machines Corporation Automated deployment of applications with tenant-isolation requirements
US9665854B1 (en) * 2011-06-16 2017-05-30 Consumerinfo.Com, Inc. Authentication alerts
US9633322B1 (en) 2013-03-15 2017-04-25 Consumerinfo.Com, Inc. Adjustment of knowledge-based authentication
US10664936B2 (en) 2013-03-15 2020-05-26 Csidentity Corporation Authentication systems and methods for on-demand products
US9721147B1 (en) 2013-05-23 2017-08-01 Consumerinfo.Com, Inc. Digital identity
US10373240B1 (en) 2014-04-25 2019-08-06 Csidentity Corporation Systems, methods and computer-program products for eligibility verification
US9875618B2 (en) 2014-07-24 2018-01-23 Igt Gaming system and method employing multi-directional interaction between multiple concurrently played games
SG11201703521UA (en) 2014-11-03 2017-05-30 Genentech Inc Methods and biomarkers for predicting efficacy and evaluation of an ox40 agonist treatment
US9972171B2 (en) 2015-09-24 2018-05-15 Igt Gaming system and method for providing a triggering event based on a collection of units from different games
US10911234B2 (en) 2018-06-22 2021-02-02 Experian Information Solutions, Inc. System and method for a token gateway environment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0326699A2 (en) * 1988-02-01 1989-08-09 International Business Machines Corporation A remote trusted path mechanism for telnet
EP0666681A2 (en) * 1989-11-09 1995-08-09 Transaction Technology, Inc. Computer and telephone apparatus with user friendly computer interface and enhanced integrity features
US5506832A (en) * 1993-11-24 1996-04-09 Intel Corporation Remote confidence testing for computer-based conferencing system

Family Cites Families (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3956615A (en) * 1974-06-25 1976-05-11 Ibm Corporation Transaction execution system with secure data storage and communications
US4277837A (en) * 1977-12-30 1981-07-07 International Business Machines Corporation Personal portable terminal for financial transactions
US4303904A (en) * 1979-10-12 1981-12-01 Chasek Norman E Universally applicable, in-motion and automatic toll paying system using microwaves
US4454414A (en) * 1982-06-16 1984-06-12 Vericard Corporation Funds transfer system using optically coupled, portable modules
US4877950A (en) * 1982-08-23 1989-10-31 Paperless Accounting, Inc. Electronic purse-device
US4906828A (en) * 1983-02-28 1990-03-06 Paperless Accounting, Inc. Electronic money purse and fund transfer system
US4630201A (en) * 1984-02-14 1986-12-16 International Security Note & Computer Corporation On-line and off-line transaction security system using a code generated from a transaction parameter and a random number
IL75702A0 (en) * 1984-07-27 1985-11-29 Technion Res & Dev Foundation Apparatus for effecting and recording monetary transactions
US4614861A (en) * 1984-11-15 1986-09-30 Intellicard International, Inc. Unitary, self-contained card verification and validation system and method
US4689478A (en) * 1984-12-24 1987-08-25 Ncr Corporation System for handling transactions including a portable personal terminal
US4766293A (en) * 1986-06-26 1988-08-23 Visa International Service Association Portable financial transaction card capable of authorizing a transaction in foreign currencies
US4780821A (en) * 1986-07-29 1988-10-25 International Business Machines Corp. Method for multiple programs management within a network having a server computer and a plurality of remote computers
JPH07104891B2 (en) * 1986-08-05 1995-11-13 沖電気工業株式会社 Transaction processor
US4859837A (en) * 1987-03-23 1989-08-22 Halpern John Wolfgang Portable data carrier incorporating manually presettable processing modes
US4968873A (en) * 1987-09-08 1990-11-06 Juergen Dethloff Smart card issuing and receiving apparatus
CA1321649C (en) * 1988-05-19 1993-08-24 Jeffrey R. Austin Method and system for authentication
FR2639742B2 (en) * 1988-05-30 1992-03-13 Dassault Electronique TRANSACTION SYSTEM OF THE MIXED ELECTRONIC PURSE TYPE
US4949248A (en) * 1988-07-15 1990-08-14 Caro Marshall A System for shared remote access of multiple application programs executing in one or more computers
JPH0622030B2 (en) * 1988-10-03 1994-03-23 富士通株式会社 Transaction validity confirmation method
US5016274A (en) * 1988-11-08 1991-05-14 Silvio Micali On-line/off-line digital signing
US5249293A (en) * 1989-06-27 1993-09-28 Digital Equipment Corporation Computer network providing transparent operation on a compute server and associated method
ZA907106B (en) * 1989-10-06 1991-09-25 Net 1 Products Pty Ltd Funds transfer system
US5452352A (en) * 1990-03-20 1995-09-19 Talton; David Automatic dialing system
GB9008362D0 (en) * 1990-04-12 1990-06-13 Hackremco No 574 Limited Banking computer system
AU639802B2 (en) * 1990-08-14 1993-08-05 Oracle International Corporation Methods and apparatus for providing dynamic invocation of applications in a distributed heterogeneous environment
US5221838A (en) * 1990-12-24 1993-06-22 Motorola, Inc. Electronic wallet
JPH06503218A (en) * 1991-04-16 1994-04-07 バラス,ジョン Method and apparatus for placing orders from remote locations
GB9121995D0 (en) * 1991-10-16 1991-11-27 Jonhig Ltd Value transfer system
US5453601A (en) * 1991-11-15 1995-09-26 Citibank, N.A. Electronic-monetary system
WO1993017388A1 (en) * 1992-02-26 1993-09-02 Clark Paul C System for protecting computers via intelligent tokens or smart cards
US5476259A (en) * 1992-06-11 1995-12-19 Gamin Weingardt Trust, A Nevada Trust Pari-mutuel electronic and live table gaming
CA2100134C (en) * 1992-09-29 1999-06-22 Raymond Otto Colbert Secure credit/debit card authorization
CH685891A5 (en) * 1993-01-18 1995-10-31 Ascom Autelca Ag A method as security concept to prevent unauthorized use of a payment instrument for cashless settling on imprest
US5420405A (en) * 1993-02-26 1995-05-30 Chasek; Norman E. Secure, automated transaction system that supports an electronic currency operating in mixed debit & credit modes
US5546583A (en) * 1994-04-05 1996-08-13 International Business Machines Corporation Method and system for providing a client/server interface in a programming language
EP0684553B1 (en) * 1994-05-26 2004-06-16 Sun Microsystems, Inc. Method and apparatus for generating and using short operation identifiers in object oriented systems
US5459304A (en) * 1994-09-13 1995-10-17 At&T Ipm Corp. Smart card techniques for motor vehicle record administration
JP3071469B2 (en) * 1994-12-13 2000-07-31 ノベル,インコーポレイテッド Apparatus and method for providing simple and secure management of a remote server
US5583563A (en) * 1995-01-12 1996-12-10 Us West Marketing Resources Group, Inc. Method and system for delivering an application in an interactive television network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0326699A2 (en) * 1988-02-01 1989-08-09 International Business Machines Corporation A remote trusted path mechanism for telnet
EP0666681A2 (en) * 1989-11-09 1995-08-09 Transaction Technology, Inc. Computer and telephone apparatus with user friendly computer interface and enhanced integrity features
US5506832A (en) * 1993-11-24 1996-04-09 Intel Corporation Remote confidence testing for computer-based conferencing system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WAYNER P: "Inside the NC", BYTE, vol. 21, no. 11, November 1996 (1996-11-01), MCGRAW HILL,USA, pages 105 - 110, XP002050423 *

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999054804A3 (en) * 1998-04-20 2000-04-27 Sun Microsystems Inc Method and apparatus for providing a virtual desktop system architecture
US7346689B1 (en) 1998-04-20 2008-03-18 Sun Microsystems, Inc. Computer architecture having a stateless human interface device and methods of use
CN1310487C (en) * 1998-04-20 2007-04-11 太阳微系统公司 Method and apparatus for providing virtual desktop system architecture
WO1999054804A2 (en) * 1998-04-20 1999-10-28 Sun Microsystems, Inc. Method and apparatus for providing a virtual desktop system architecture
AU763158B2 (en) * 1998-04-20 2003-07-17 Sun Microsystems, Inc. Method and apparatus for providing a virtual desktop system architecture
EP0965927A3 (en) * 1998-06-18 2000-03-22 Sun Microsystems, Inc. Client intermediation of server applications
EP0965927A2 (en) * 1998-06-18 1999-12-22 Sun Microsystems, Inc. Client intermediation of server applications
EP0978976A3 (en) * 1998-07-22 2001-04-04 Hewlett-Packard Company An application dispatcher for server application
EP0978976A2 (en) * 1998-07-22 2000-02-09 Hewlett-Packard Company An application dispatcher for server application
US6356631B1 (en) 1998-09-24 2002-03-12 Ericsson Inc. Multi-client object-oriented interface layer
WO2000018092A1 (en) * 1998-09-24 2000-03-30 Ericsson Inc. Multi-client object-oriented interface layer
EP1119157A2 (en) * 2000-01-20 2001-07-25 Sony Corporation Terminal device, apparatus and method for controlling a terminal device, and method of controlling a process in a terminal device
EP1119157A3 (en) * 2000-01-20 2004-04-28 Sony Corporation Terminal device, apparatus and method for controlling a terminal device, and method of controlling a process in a terminal device
US6934777B2 (en) 2000-01-20 2005-08-23 Sony Corporation Terminal device, apparatus and method for controlling a terminal device, and method of controlling a process in a terminal device
WO2014164122A1 (en) * 2013-03-11 2014-10-09 Microsoft Corporation Unified game preview

Also Published As

Publication number Publication date
DE69732968T2 (en) 2006-02-16
AU730088B2 (en) 2001-02-22
EP0919092A1 (en) 1999-06-02
AU3963897A (en) 1998-02-25
US5828840A (en) 1998-10-27
HK1017539A1 (en) 1999-11-19
DE69732968D1 (en) 2005-05-12
EP0919092B1 (en) 2005-04-06

Similar Documents

Publication Publication Date Title
AU730088B2 (en) A system, method and article of manufacture for seamless, server application support of network and non-network client terminals
US6163797A (en) Application dispatcher for seamless, server application support for network terminals and non-network terminals
US5499343A (en) Object-oriented networking system with dynamically configurable communication links
US5548723A (en) Object-oriented network protocol configuration system utilizing a dynamically configurable protocol stack
US5515508A (en) Client server system and method of operation including a dynamically configurable protocol stack
US5491800A (en) Object-oriented remote procedure call networking system
US7971207B2 (en) Method, system, and computer program product for representing and connection-oriented device in a known format
US6393497B1 (en) Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
US5764915A (en) Object-oriented communication interface for network protocol access using the selected newly created protocol interface object and newly created protocol layer objects in the protocol stack
US5625678A (en) Method and system for allowing switched voice and data communication among multiple application programs
US5809235A (en) Object oriented network event management framework
US5894557A (en) Flexible point-to-point protocol framework
JP2514303B2 (en) Method and system for transferring message to network using virtual device driver
US20050172295A1 (en) System and method for adaptable provisioning of generic application content
US7536688B2 (en) Segmented virtual machine
US8387039B2 (en) System and method for customized provisioning of application content
JP2006511100A (en) Method and system for extending the functionality of a mobile platform using plug-in software
US20020046304A1 (en) Dynamic class loading
US20050021800A1 (en) Method for transferring data in a system having multiple transports
US20020087945A1 (en) System and method for providing flexible network service application components
EP1058880A1 (en) Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system
WO1998035478A1 (en) A system, method and article of manufacture for seamless serverapplication support of client terminals and personal automated tellers
EP1560114A1 (en) Computer system and method for customized provisioning of application content
CN112214333A (en) Webpage and local application communication protocol based on HTTP (hyper text transport protocol) and application
EP2088505A1 (en) Computer system and method for adaptable provisioning of generic application content

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH HU IL 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 TJ TM TR TT UA UG US UZ VN YU AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH KE LS MW SD SZ UG ZW AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

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
WWE Wipo information: entry into national phase

Ref document number: 1997937021

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1997937021

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1998507985

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: CA

WWG Wipo information: grant in national office

Ref document number: 1997937021

Country of ref document: EP