EP1247261A1 - Terminal libre-service - Google Patents

Terminal libre-service

Info

Publication number
EP1247261A1
EP1247261A1 EP00977673A EP00977673A EP1247261A1 EP 1247261 A1 EP1247261 A1 EP 1247261A1 EP 00977673 A EP00977673 A EP 00977673A EP 00977673 A EP00977673 A EP 00977673A EP 1247261 A1 EP1247261 A1 EP 1247261A1
Authority
EP
European Patent Office
Prior art keywords
user
data
terminal
screen
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP00977673A
Other languages
German (de)
English (en)
Inventor
Sharon Dickie
Wolf Dieter Rossmann
Mark Michael Grossi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NCR International Inc
Original Assignee
NCR International 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 NCR International Inc filed Critical NCR International Inc
Publication of EP1247261A1 publication Critical patent/EP1247261A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F19/00—Complete banking systems; Coded card-freed arrangements adapted for dispensing or receiving monies or the like and posting such transactions to existing accounts, e.g. automatic teller machines
    • G07F19/20—Automatic teller machines [ATMs]
    • G07F19/201—Accessories of ATMs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/18—Payment architectures involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F19/00—Complete banking systems; Coded card-freed arrangements adapted for dispensing or receiving monies or the like and posting such transactions to existing accounts, e.g. automatic teller machines
    • G07F19/20—Automatic teller machines [ATMs]

Definitions

  • the present invention relates to a self-service terminal- (SST) .
  • SST self-service terminal-
  • the invention relates to an SST, such as an automated teller machine (ATM) ,
  • ATM automated teller machine
  • ATMs It is becoming increasingly common for ATMs to provide a variety of different services to users. These services include conventional transactions such as withdrawal of cash and printing a statement, but they also include paying utility bills, cashing cheques, buying money orders, transferring funds between accounts, and such like.
  • screen is used herein to denote the graphics, text, controls (such as menu options) , and such like, that are displayed on an SST monitor; the term “screen” as used herein does not refer to the hardware (that is, the monitor) that displays the graphics, text, controls, and such like.
  • a self-service terminal including a graphical user interface, characterised in that the terminal has a link to a remote server storing user data and associated screen configuration data for each of a plurality of authorised users; whereby, the terminal is operable to identify a user, to receive from the server the screen configuration data associated with the identified user, and to operate on the screen configuration data to generate one or more screens for displaying to the user.
  • a user is able to customise the appearance of the screens that are presented to him/her when using a terminal.
  • each user of an SST may have their own personal user-defined screens that present the user's most commonly used transactions in a format pleasing to the user.
  • the link to a remote server is also adapted for connecting to a public access network such as the Internet .
  • the screen configuration data may include details of additional services that may be displayed on the screen.
  • the screen may include an area for displaying the exchange rate from pound sterling to US dollar, the weather forecast in Edinburgh, or such like.
  • the additional services may be provided by one or more third parties, and may be retrieved from a Web page.
  • the terminal is adapted to receive at least some of the user data and the screen configuration data. This has the advantage that the terminal can display account information for the user.
  • the terminal is also adapted to receive formatting data, so that the terminal is able to use the formatting data to extract information from the user data and the screen configuration data, and to present the extracted data in a consistent format.
  • the user data may include financial details, such as account information and transaction history.
  • the server may include PIN information for authorising a transaction.
  • the screen configuration data may include pre-defined transactions, such as withdraw ten pounds, pay a utility bill, print a statement or such like.
  • the screen configuration data may include details of the user's name and how the user is to be addressed (for example, "Mr Smith”, “John”, or such like) by the terminal, so that the SST can display the user's name on the first screen seen by the user, and/or on any subsequent screen.
  • the screen configuration data may also include information relating to financial details, such as a user- defined name for each of the different bank accounts held by the user, so that an account may be displayed as, for example, "John's Savings account”, or "Mary's Current account”, and the balance of the account (retrieved from the user data) displayed next to the user-defined name.
  • financial details such as a user-defined name for each of the different bank accounts held by the user, so that an account may be displayed as, for example, "John's Savings account”, or "Mary's Current account”, and the balance of the account (retrieved from the user data) displayed next to the user-defined name.
  • the screen configuration data may include details of the screen appearance, for example, the background colour, the shape of any buttons used on the screen, whether the screen is to be accessed by a right-handed or left-handed user, the number and type of services to be displayed on the first screen, and such like.
  • the screen configuration data can be updated by the user as frequently as desired.
  • a method of providing a self-service terminal with a user-defined screen or screens being characterised by the steps of: accessing an enrolment process providing a plurality of user configurable options for selection by a user, storing options selected by the user in a computer database, storing formatting information, and, in response to the terminal identifying the user, providing a terminal with the options selected by the user and the formatting information for use by the terminal in generating a user-defined screen.
  • the step of accessing an enrolment process may be performed at a self-service terminal or remote from a self- service terminal, for example, at a home PC, via a cellular radiotelephone, or such like.
  • a self-service terminal having a graphical interface, characterised in that the terminal is adapted to retrieve user-specific screen configuration data from a remote server, to operate on the configuration data to generate a user-specific screen, and to display the user- specific screen to a user.
  • a server for supplying a self-service terminal with screen configuration data specific to a user
  • the server comprises a database for storing user data and associated screen configuration data for each of a plurality of authorised users, a network connection for receiving user details from a remote terminal, and a controller; where, in use, the controller is operable to access the database to retrieve user data and screen configuration data corresponding to the user details, and to transmit the retrieved data to the remote terminal .
  • a server that stores customised screen information relating to each user, and transmits this information to a SST on receipt of a request from the SST.
  • the controller is also operable to access a network, such as the Internet, an Extranet, or an Intranet, for retrieving publicly available information and/or information from a third party, for incorporating into a user's screen.
  • a network such as the Internet, an Extranet, or an Intranet
  • the server includes an XML converter for receiving data from the database and converting the data into one or more XML (extensible Markup Language) files; and for receiving Web pages (which may be in HTML format) and converting them into XML files.
  • the server includes one or more XSL (extensible Stylesheet Language) files for extracting and formatting data from the XML files.
  • the server conveys the XML files and the XSL files to the terminal, where the terminal includes an XSL processor for using the XSL files to operate on the XML files to generate HTML for displaying as a screen.
  • the terminal includes a Web browser or a browser component, for receiving XSL files and XML files and generating HTML files therefrom.
  • a self-service terminal system characterised in that the system comprises a server interconnected to a plurality of self-service terminals, where the server is operable to receive enrolment data from a user relating to a customised screen, to associate the enrolment data with user data, and to store the enrolment data and associated data in a database; whereby, when the user uses one of the terminals, the terminal transmits user details to the server; the server accesses the stored data corresponding to the user details, and transmits the accessed data to the terminal; and the terminal operates on the transmitted data to generate and display a customised screen.
  • Fig 1 is a block diagram of a server system according to one embodiment of the present invention.
  • Fig 2 is a block diagram of the server of Fig 1 ;
  • Fig 3 is a block diagram of one of the terminals of Fig 1;
  • Fig 4 is a pictorial view of an enrolment screen showing one interface style
  • Fig 5 is a pictorial view of an enrolment screen showing a second interface style
  • Fig 6 is a pictorial view of one customised screen as seen by a user operating the terminal of Fig 1;
  • Fig 7 is a pictorial view of another customised screen as seen by a user operating the terminal of Fig 1;
  • Fig 8 is a pictorial view of yet another customised screen as seen by a user operating the terminal of Fig 1;
  • Fig 9 illustrates XML code relating to three previous transactions by a user.
  • Fig 10 illustrates XSL code relating to formatting data for the code of Fig 9.
  • a self-service terminal system 10 is owned and operated by a financial institution, and comprises a server 12 interconnected to a plurality of terminals 14 by a network 16.
  • the terminals 14 are in the form of ATMs (only two of which are shown) and the network 16 is in the form of a private Intranet .
  • the Intranet 16 is connected to a public access network 18 in the form of the Internet by a gateway 20.
  • the gateway 20 includes various security features, such as firewalls, to restrict access to the Intranet 16.
  • Both the Intranet 16 and the Internet 20 are TCP/IP-based networks.
  • numerous electronic devices such as personal computers (PCs) , cellular telephones, personal digital assistants (PDAs) , and such like, may connect to the Internet 18; one such device, PC 22, is shown in Fig 1.
  • the server 12 comprises a controller 30, a datastore 32, and a network connection 34.
  • a system bus (or buses) 40 connects the network connection 34 to the controller 30 and datastore 32.
  • the controller 30 further comprises a BIOS 42 stored in non-volatile memory, a microprocessor 44, associated main memory 46, and storage space 48 in the form of a magnetic disk drive.
  • the datastore 32 is shown including five databases (32a to 32e) , but the actual arrangement of data and the number of databases used is not critical.
  • Database 32a is used for storing user information for each authorised user.
  • the user information includes an interface style reference for referencing database 32b; in this embodiment three different interface styles are available (as illustrated in Figs 6, 7, and 8) , so that a user can select one of these three styles.
  • Database 32a also includes user preferences for buttons to be displayed on a screen, as will be described in more detail below.
  • Database 32b is used for storing the fonts, colours, text, button shapes, and such like, for each possible user interface style.
  • Database 32c is used for storing account details for each user, such as PIN, balance in each account, recent transaction history, and such like information.
  • Database 32d is used for storing formatting data; in this embodiment, XSL files.
  • the XSL files are independent of any user selections, and contain processing instructions for extracting and formatting user information, interface style data, account data, and third party service data from XML files; and to generate HTML using the extracted data.
  • the XSL files are controlled by the financial institution, and the same XSL files are used for every user.
  • Database 32e is used for storing an enrolment application program. The enrolment program assists users in customising their ATM screens .
  • the magnetic drive 48 stores a server operating system, an XML conversion application, and a Web server application.
  • the main memory 46 is loaded with the server operating system kernel 50, the XML converter 52, and the Web server application 54.
  • the Web server 54 includes a database application programming interface (API) 56 for providing SQL access to the datastore 32.
  • API application programming interface
  • a system bus (or a plurality of system buses) 60 interconnects a user interface 62, a network connection 64, and an ATM controller 66, to facilitate mutual intercommunication.
  • the user interface 62 comprises the following user interface elements (peripheral devices) : a card reader 70, a monitor 72 , a touchscreen module 74 mounted onto the monitor 72, a printer 76, and a cash dispenser 78.
  • the controller 66 comprises modules for driving the user interface elements 70 to 78, namely: card reader controller 80, monitor controller 82, touchscreen controller 84, printer controller 86, and dispenser controller 88.
  • These user interface elements (70 to 78) and associated controllers (80 to 88) are standard modules that are used on conventional ATMs and will not be described in detail herein.
  • the controller 66 also comprises a BIOS 90 stored in non-volatile memory, a microprocessor 92, associated main memory 94, and storage space 96 in the form of a magnetic disk drive.
  • the controller 66 loads an operating system kernel 100 and an ATM application 102 into memory 94.
  • the ATM application 102 is used to operate the ATM and includes a browser 104 for displaying Web pages on monitor 72.
  • the browser 104 is an Internet Explorer 5 (trade mark) browser from Microsoft Corporation (trade mark) .
  • the IE5 browser 104 includes an XSL processor for receiving XSL and XML files and processing the XML files using the instructions contained in the XSL files to generate HTML.
  • a user accesses the enrolment application program stored in database 32e using PC 22.
  • the enrolment application program is provided on a Web page operated by the Web server 12 , so the user enters the appropriate URL on a Web browser executing on PC 22 to access the enrolment application.
  • the enrolment application allows a user to configure the screen layout he will be presented with when using any ATM 14 in system 10.
  • the user can choose a particular pre-defined interface style for his customised screen by selecting an option from interface selection area 110 (shown as a dotted line) .
  • interface selection area 110 shown as a dotted line
  • Three interface style options are shown in Figs 4 and 5.
  • the selected style is shown in preview area 112.
  • the interface style selected is the "Trekie” style; whereas, in Fig 5, the interface style selected is the "Jade” style.
  • the interface styles are chosen by the financial institution to provide a template for use by each user.
  • the financial institution stores full details of each interface style (for example, background colour, button size, button shape, font size, and such like) in database 32b.
  • the user can indicate whether he is left or right- handed by selecting one of two buttons from area 114. If the user is left-handed then, on the customised screen, any selection buttons are located to the left side; whereas, any selection buttons are located to the right side if the user is right-handed.
  • Button programming area 116 enables the user to select how many buttons will be presented on the customised screen, what function each button will perform, and what label is applied to each button.
  • Programming area 116 presents the different transaction options available on the ATMs 14 in the system 10. The user selects a transaction option, for example withdraw cash; the user is then shown another enrolment screen (not shown) for specifying the amount to be withdrawn, for example ten pounds; the user is then shown another enrolment screen (not shown) for specifying a label to be attached to the button, for example, "usual". The effect of this selection is that in the customised screen a button is presented that is labelled "usual"; when the button is selected the transaction is authorised and ten pounds are dispensed.
  • the user selects all the transactions that he wishes to be presented on his customised screen. These transactions may include transferring funds, printing a statement, paying a bill, or such like.
  • the user can select another tab from tab area 118. If the user selects the personal details tab 120, he can enter the name (if any) to be displayed on the customised screen, for example, John Smith, Mr Smith, Dr Smith, or such like.
  • the user can also select the language to be used on the screen, for example, English, French, German, or such like.
  • a financial details tab 122 When the user has finished entering personal details, he can select a financial details tab 122 to enter details relating to the accounts the user has, such as labels to be applied to the accounts, for example, "Spending Money”, “Savings Account”, or such like.
  • the user can select a services tab 124 for selecting additional services provided by third parties and available via the Internet, such as the exchange rate between one pound sterling and the US dollar.
  • additional services provided by third parties and available via the Internet, such as the exchange rate between one pound sterling and the US dollar.
  • the user enters the URL for the Web page to be accessed, and any identifier required to indicate the data that is to be extracted from that Web page.
  • the enrolment data is then transmitted to the server 12 via the Internet 18, gateway 20 and Intranet 16.
  • the server 12 stores the enrolment data in the user information database 32a in a record indexed by identification data stored on the user's magnetic stripe card, in this embodiment the card number.
  • the ATM then sends the identification data stored on the user's card to the server 12.
  • the server 12 accesses the databases 32a to 32d to retrieve user data (such as account information stored in database 32c) , screen configuration data (such as the user information stored in database 32a and the interface styles information stored in database 32b) , and formatting data (the XSL files stored in database 32d) .
  • the data retrieved from databases 32a, 32b, and 32c is converted into XML files by XML converter 52 (Fig 2) ; the data retrieved from database 32d is transmitted as an XSL file.
  • the server 12 also accesses the Internet 18 to retrieve any data required from a third party (for example, the pound to dollar exchange rate) .
  • the server 12 receives this in HTML format and converts it into an XML file using XML converter 52.
  • the server 12 then transmits the XML and XSL files to the ATM 14 via Intranet 16.
  • the ATM 14 operates on the files by using the XSL files to extract information from the XML files and to generate HTML files for displaying on the monitor 72 (Fig 3) .
  • the user is then presented with a customised display that reflects the options selected during the enrolment process.
  • Figs 6, 7, and 8 show three different customised screens as displayed on an ATM 14.
  • the screens each have the same transaction options and the same account details, but the interface style chosen for each is different.
  • Each screen has a service area 140 for displaying third party services.
  • the third party service is obtained from the Internet 18 rather than the Intranet 16
  • the service is not displayed (as in Figs 6, 7, and 8) . This ensures that the user does not have to wait too long before he can execute a transaction.
  • the server 12 may send the available data first, to allow the user to initiate a transaction, and then send the third party service data at some later time (when it arrives from the Internet 18) , so that the ATM 14 may display the third party service data during the transaction.
  • Fig 9 illustrates XML code relating to three previous transactions by a user. This code is generated by the XML converter 52 (Fig 2) from data stored in database 32c.
  • Fig 10 illustrates XSL code relating to formatting information for the data contained in the XML file of Fig 9.
  • the XSL code creates HTML in the style of the user ' s interface (e.g. the "Trekie” style) , extracts the data from the XML code of Fig 9, inserts the extracted code into the newly created HTML, and displays the HTML.
  • this embodiment has the advantage that each user can personalise an ATM screen, so that the screen displays the services and information that the user wishes to see on each visit to an ATM.
  • the SST may be an information kiosk.
  • more or fewer than three interface styles may be used.
  • the server 12 may receive information in a format other than HTML format and convert it into an XML file using an XML converter; the server 12 may receive information in XML format from an external source.
  • the enrolment process may be performed using a cellular radiotelephone, a personal digital assistance (PDA) , a dedicated Internet access device, an interactive television, or such like.
  • PDA personal digital assistance

Abstract

La présente invention concerne un terminal libre-service (10) comprenant une interface graphique utilisateur. Le terminal (10) est relié à un serveur distant (12) qui stocke des données utilisateur pour plusieurs utilisateurs autorisés. Pour chaque utilisateur, le serveur stocke aussi des données de configuration d'écran associé. Le terminal fonctionne par identification d'un utilisateur, reçoit du serveur les données de configuration d'écran associées à l'utilisateur identifié, et met en oeuvre ces données afin de générer un ou plusieurs écrans d'affichage pour l'utilisateur. Ceci permet au terminal (10) d'afficher un écran spécifique pour chaque utilisateur autorisé. L'invention concerne aussi un système terminal libre-service et un procédé de mise en oeuvre de terminal libre-service avec un ou des écrans définis par l'utilisateur.
EP00977673A 1999-12-03 2000-11-22 Terminal libre-service Ceased EP1247261A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB9928733 1999-12-03
GBGB9928733.6A GB9928733D0 (en) 1999-12-03 1999-12-03 Self-service terminal
PCT/GB2000/004427 WO2001041090A1 (fr) 1999-12-03 2000-11-22 Terminal libre-service

Publications (1)

Publication Number Publication Date
EP1247261A1 true EP1247261A1 (fr) 2002-10-09

Family

ID=10865741

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00977673A Ceased EP1247261A1 (fr) 1999-12-03 2000-11-22 Terminal libre-service

Country Status (4)

Country Link
EP (1) EP1247261A1 (fr)
AU (1) AU1531101A (fr)
GB (1) GB9928733D0 (fr)
WO (1) WO2001041090A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1049057A3 (fr) * 1999-04-26 2004-05-06 Citishare Corporation Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière
GB2416058B (en) 2004-07-09 2008-01-23 Tricerion Ltd A method of secure data communication
DE102004046596A1 (de) * 2004-09-25 2006-04-13 Wincor Nixdorf International Gmbh Verfahren zum Ausdrucken von Formulardrucken an SB-Geräten
EP1736947A1 (fr) * 2005-06-09 2006-12-27 NCR International, Inc. Procédé de sécurité personnalisé pour un système de caisse d'enregistrement en libre-service

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5966695A (en) * 1995-10-17 1999-10-12 Citibank, N.A. Sales and marketing support system using a graphical query prospect database
US6047261A (en) * 1997-10-31 2000-04-04 Ncr Corporation Method and system for monitoring and enhancing computer-assisted performance
US6119104A (en) * 1997-11-24 2000-09-12 Keycorp Composite banking desktop system
US6104334A (en) * 1997-12-31 2000-08-15 Eremote, Inc. Portable internet-enabled controller and information browser for consumer devices
ES2313770T3 (es) * 1998-05-27 2009-03-01 Diebold, Incorporated Maquina bancaria automatica con acceso a datos basandose en entradas de cliente que incluyen la identificacion biometrica del cliente y la produccion de visualizaciones seleccionadas basandose en la identidad del cliente (bean de perfil).
JP3028484B2 (ja) * 1999-05-17 2000-04-04 豊 塚本 情報提供システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0141090A1 *

Also Published As

Publication number Publication date
WO2001041090A1 (fr) 2001-06-07
GB9928733D0 (en) 2000-02-02
AU1531101A (en) 2001-06-12

Similar Documents

Publication Publication Date Title
JP3809857B2 (ja) 取引システム、取引端末、取引履歴出力装置、サーバ、取引の履歴表示方法、コンピュータプログラム
US7661590B1 (en) Electronic fund transfer or transaction system
US5705798A (en) System and method for processing a customized financial transaction card
US6796492B1 (en) Electronic fund transfer or transaction system
US7822684B2 (en) Personalized bank teller machine
US8429077B2 (en) Web enabled bank teller machine
US8589868B2 (en) Creating a terminal application
EP1378877A2 (fr) Code d'autorisation
US20040004116A1 (en) Automatic transaction machine
US6763999B2 (en) Self-service terminal
US20200058010A1 (en) Managing pre-accounting, accounting and e-trade systems from a single panel
US20030020747A1 (en) User input peripheral device substitution for web commerce delivery
EP1247261A1 (fr) Terminal libre-service
US7225973B2 (en) Self-service terminal
KR20050044215A (ko) 금융자동화기기의 계좌내역분석시스템 및 이를 이용한계좌내역 분석정보 제공방법
JP3498679B2 (ja) 画面表示方法および装置
MXPA99004932A (es) Sistema y aparato de maquina de cajero automatizado.
MXPA99004934A (es) Sistema y aparato de maquina de cajero automatizado.
JP2004013765A (ja) 商取引システムおよび商取引端末装置
MXPA99004933A (es) Sistema y aparato de maquina de cajero automatizado.
JP2003030433A (ja) 申込書送信装置、申込書送信方法、申込書送信プログラム、記憶媒体、申込書送受信装置及び申込書送受信方法
JP2005071032A (ja) 現金自動取引システム、取引内容入力装置
MXPA01007891A (en) Method and system for connecting services to an automated transaction machine
JP2001351150A (ja) 自動取引装置および自動取引システム
JP2004118779A (ja) 媒体取引情報入力装置、媒体取引情報処理装置、カード型媒体、媒体取引情報入力方法、媒体取引情報処理方法、コンピュータ・プログラム及び記録媒体

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020703

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

RBV Designated contracting states (corrected)

Designated state(s): DE ES FR GB IT

17Q First examination report despatched

Effective date: 20040519

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20051208