http://rdf.ncbi.nlm.nih.gov/pubchem/patent/WO-9835478-A1
Outgoing Links
| Predicate | Object |
|---|---|
| assignee | http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_9547451d1e1e30b21dbd808027ccacc9 http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_b7337c3a98d0e4e8ec617f3a921514d7 http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_85f13e956828c6fe494292d1e482d9cb http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_0155a8b9feb61012394cf810b3dbd17f http://rdf.ncbi.nlm.nih.gov/pubchem/patentassignee/MD5_199f033d5ef02aabf430c497fc7d2a33 |
| classificationCPCAdditional | http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06F2209-549 |
| classificationCPCInventive | http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G07F19-20 http://rdf.ncbi.nlm.nih.gov/pubchem/patentcpc/G06Q20-18 |
| classificationIPCInventive | http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G07F19-00 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/H04L29-06 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G06F9-445 http://rdf.ncbi.nlm.nih.gov/pubchem/patentipc/G06Q20-00 |
| filingDate | 1998-02-06-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| inventor | http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_eb8198ee8b357415a71a02597b147a69 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_06a6623364f5e63fed8bcb658df7f5fc http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_f13d1a896b8bda19bdf33a9832bea4d1 http://rdf.ncbi.nlm.nih.gov/pubchem/patentinventor/MD5_846978ce33afd30b6e7c6994a5ae064d |
| publicationDate | 1998-08-13-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| publicationNumber | WO-9835478-A1 |
| titleOfInvention | A system, method and article of manufacture for seamless serverapplication support of client terminals and personal automated tellers |
| abstract | A plurality of clients are connected to one or more servers (210). These clients (200) include network terminals, and non-network terminals, including personal automated tellers. When a client (200) initiates a connection with a server (210), the server (210) responds to the request for connection by transmitting a message back to the client (200) to determine whether the client (200) is a network terminal or not. The client (200) 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 (200) is a network terminal (200). If the client terminal is a network terminal, then the application dispatcher spawns a server application in the server (210) which responds to the client (200) application in the client (200). 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. If the client is a personal automated teller, the client application is a personal automated teller application. 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. A new communication protocol is also defined for processing automated teller transactions. |
| isCitedBy | http://rdf.ncbi.nlm.nih.gov/pubchem/patent/EP-0978976-A3 http://rdf.ncbi.nlm.nih.gov/pubchem/patent/EP-0978976-A2 http://rdf.ncbi.nlm.nih.gov/pubchem/patent/WO-0155983-A1 http://rdf.ncbi.nlm.nih.gov/pubchem/patent/WO-03017215-A1 |
| priorityDate | 1997-02-10-04:00^^<http://www.w3.org/2001/XMLSchema#date> |
| type | http://data.epo.org/linked-data/def/patent/Publication |
Incoming Links
Total number of triples: 30.