Self service terminal

[0001] [Technical field to which the invention belongs] The present invention relates to a self service terminal (hereinafter referred to as "SST") and a network including such a self-service terminal device, and in particular, the present invention relates to a transaction terminal device such as a deposit or retail transaction terminal device and such a terminal device. Consists of a network consisting of. [0002] [Conventional technology] Typical trading terminal devices are automated teller machines (hereinafter referred to as "ATMs"), point of sale (hereinafter referred to as "POS") terminal devices, investment information service centers, or Can be a point-of-sale kiosk. Each terminal device typically has a central processor based on a PC, which controls the operation of the terminal device. Conventionally, application software that controls the operation of the terminal device is stored in a mass storage device (a very large storage device) such as a hard disk in the terminal device. [0003] The trading terminal device is connected to a server containing (or having access to) an information database (called a legacy host) via a communication link. A plurality of terminal devices of the same type or different types are connected to a server in a transaction network. A simple client-server transaction takes place between the terminal device and the server to obtain customer-specific information used to process the customer's transaction. In the case of deposit (banking) or financial terminals (such as ATMs), the transaction can typically be a cash withdrawal or balance request. For retail terminals (such as point-of-sale terminals), a typical transaction is a price search. [0004] FIG. 1 is a block diagram of an ATM 10 (shown by a dashed line) connected to legacy host 12 via server 14, which is a card reader 16, a receipt printer 18, and a cash dispenser 20. And also has a user interface 22 (including an encrypted keyboard and display). These devices are equipped with appropriate control software and require some form of embedding processing function to execute communication with the central processor and execute commands received from the central processor. [0005] All application software, peripheral drivers, and user interface files are stored on the mass storage device in the ATM10. Typically, these applications, drivers, and files form a large, monolithic (or integrated) central program 24 that is used to control all aspects of ATM10's operation. This central program 24 runs or runs on a central processor to determine, for example, what graphic image to display to a customer on a display, an encrypted PIN (Personal Identification Number) from a card reader. Through an encrypted keyboard for information retrieval and verification, it performs a number of functions such as checking if the customer's account has sufficient funds when a cash withdrawal is requested. [0006] This central program 24 minimizes the required business logic (integrating and managing the different functions of the terminal device) and the possibility that the terminal device will have to leave the service due to a failure. Includes error handling routines. Therefore, the design of this Central Program 24 is very complex and time consuming. In addition, application software associated with updater drivers or peripherals is complicated by the size of the central program 24. [0007] Future self-service terminals (SSTs) will depend, for example, on what type of "Smart" card is used or in what type of graphic format it should be printed. Therefore, it is expected that the ability to change the function of the terminal device itself during operation is required. [0008] Application development tools are available to allow developers to consider peripherals (hereafter referred to as peripherals) as functional components, but for these components within a single central program. -It is still necessary to provide logic and error handling facilities. [0009] [Problems to be Solved by the Invention] An object of the present invention is to provide a self-service terminal device (SST) and a network consisting of a plurality of cell service terminal devices that alleviate or overcome one or more of the problems described above. [0010] [Means for solving problems] This purpose is to remove control of the terminal device from one central program and provide individual peripherals with a dedicated program for the individual peripherals themselves to control the corresponding individual peripherals. Overall achieved. Each peripheral operates on a peer-to-peer or peer-to-peer basis, and each peripheral is a team or one, although the peripherals are not controlled by one central program. Have a common application flow to act and interact as a companion. The term "application flow" refers to a sequence of possible events within a terminal device. [0011] Therefore, the present invention is a network system of a self-service terminal device composed of a self-service terminal device provided with a plurality of peripheral devices and a server connected to the self-service terminal device via a communication line. Each of the plurality of peripheral devices includes hardware that performs a predetermined function, control means for controlling the hardware, and communication link means for communicating with the server via the network. The server comprises the plurality of peripherals.<u style="single">apparatus</u>Each of the above-mentioned peripherals operates independently of other control applications for transaction processing executed by each of the above.<u style="single">apparatus</u>A plurality of control application and driver software corresponding to the above are stored, and each of the plurality of peripheral devices individually downloads the control application and driver software for the transaction processing from the server, and the self. The downloaded control application of the plurality of peripheral devices constituting the service terminal device transmits the status signal generated in each of the transaction processes to the other peripheral devices.<u style="single">apparatus</u>Communicate with each other based on a predetermined process communication protocol to the control application of the above, and the plurality of peripherals.<u style="single">apparatus</u>Each of the other surroundings<u style="single">apparatus</u>Each of the peripheral devices performs processing according to the operating state in the above, and each of the peripheral devices is the other peripheral device functioning in the self-service terminal device.<u style="single">apparatus</u>Equipped with registers to keep a record of<u style="single">apparatus</u>A receipt confirmation signal is returned according to the signal communicated from, and the surrounding area where the receipt confirmation signal is not returned.<u style="single">apparatus</u>Is identified as a faulty peripheral device, and the faulty peripheral<u style="single">apparatus</u>It provides a network system for a self-service terminal device, characterized in that it communicates its functional deviations to other peripheral devices. [0012] According to the present invention, these peripheral device specific control applications do not need to operate and interact as a team to instruct a central program to manage and operate those peripheral devices. Another advantage of the present invention is that the control application for each peripheral can be easily updated because it does not form part of a large central program. [0014] Preferably, the control applications interact with one process (one control application) and another process (another control application) by communicating with each other using a process that processes a communication protocol such as TCP / IP. Both processes (both control applications) allow each other to communicate whether they run or run on the same processor. [0015] Control applications can communicate with each other using broadcast signals so that one peripheral communicates its current state to all other peripherals in its terminal device. Alternatively or incidentally, the control application may communicate with the selected peripheral using a directly addressed signal, with one peripheral depending on the state of the peripheral. Or try to communicate with the peripheral device that has the operation connected to that state. [0016] Preferably, one control application that operates in response to a signal communicated from another peripheral device confirms receipt of that signal. This can be done by the protocol used for communication between peripherals, i.e. its receipt confirmation can be specific to the protocol used. [0017] Preferably, each control application communicates the functional deviation of the failed peripheral to other peripherals in order to identify any peripheral (failed peripheral) that does not confirm receipt of the signal. It is possible to operate as much as possible. In an embodiment in which a broadcast message is used, any peripheral can identify the faulty peripheral and notify other peripherals of the functional deviation of the faulty peripheral (broadcast message or Communicates (by direct message). In the embodiment in which the direct signal is transmitted, the peripheral device that has transmitted the signal whose receipt has not been confirmed can identify the failed peripheral device and send a message to other peripheral devices. [0018] A control application for each peripheral may have a register that keeps a record of the peripheral operating in the terminal device. [0019] Preferably, the control applications perform a team building process, thereby indicating their availability to them. [0020] Preferably, each control application associated with each peripheral available to the terminal device transmits a startup signal as part of the team creation process. This startup signal includes an identifier or ID for the peripheral device to be initialized and an address from which the peripheral device will receive the signal. The startup signal is broadcast or communicated directly to a predetermined address corresponding to another peripheral device. The startup signal can be transmitted by the control application over the power-up of the associated peripheral device or within a short time after the power-on. In the reception of the startup signal, the control application associated with each peripheral device available to the terminal device transmits a response signal to the control application that transmitted the startup signal. This response signal informs the sender of the startup signal of the address and identifier of the control application transmitting the response signal. [0021] [0021] Preferably, the control application associated with each peripheral creates a functional group register containing the address and ID of each peripheral that transmitted the startup signal. During use, the peripheral can use its functional group registers to determine the addresses of other peripherals to which the signal should be transmitted. The term "functional group" is used herein to refer to a team of peripherals working together via intercommunication to provide all the functionality of each peripheral within that group. [0022] Preferably, each control application transmits a shutdown signal when its associated peripheral can no longer operate properly (eg, due to a failure), and each control application functions in response to a shutdown signal from another peripheral. It can act to change the group register, suggesting its removal from the operation of the peripheral. Thus, the function group register in each active peripheral (a peripheral that receives power and operates as part of a function group) suggests the IDs and addresses of all other active peripherals in that function group. The functional group registers of such peripherals can be updated synchronously as one peripheral transmits a startup or shutdown signal. [0023] Preferably, each control application associated with the active peripheral transmits an active-confirmation signal, extending to the detection of the startup signal communicated from another peripheral after a substantial period of time following the communication of the first startup signal. Therefore, the peripheral device (newly started peripheral device) that has transmitted the startup signal can correctly construct the function group register. When this is used, when one peripheral is started after another peripheral, the register of that peripheral is started before the peripheral that is already active (ie, the newly started peripheral becomes active). It can be constructed to include the peripheral device that transmitted the signal). The advantage of this is that when a new peripheral is launched, all current members of the feature group (all currently active peripherals) will self-self to the new peripheral by sending their ID and address. To introduce. [0024] Alternatively, each control application associated with the active peripheral can transmit an active-acknowledgement signal each time it receives a startup signal. This guarantees that the newly launched peripheral will know all current members of the functional group. [0025] As you can see, the peripheral is removed from the functional group, but the peripheral is still accessible by the terminal (eg, to check its condition). Removal from the feature group means that the functionality provided by the peripheral is no longer available to the user of the terminal and that the peripheral is no longer in communication with the terminal. do not do. [0026] In use, control applications can all run on a single central processor. Alternatively, during use, each of the control applications can run on a processor in its associated peripheral. [0027] Peripherals may be selected from the following list of non-exclusive peripherals: user interfaces, card readers, receipt printers, and cash dispensers. The user interface can include a keyboard and a display unit. The self-service terminal device (SST) can be an ATM. [0028] According to a third aspect of the invention, a self-service terminal device network with a server communicating with the terminal device is provided, the terminal device includes a plurality of peripheral devices, and each device communicates with other independent control applications. It has an independent control application that can operate as much as possible, and is characterized in that one peripheral device operates in response to one or more signals generated by the control application of another peripheral device. [0029] Each terminal device can communicate with the server using a dedicated link. Alternatively, each terminal device can communicate with the server using a modem and information signal transfer means, and the signal from the modem can be transferred to the server via the telephone network. [0030] Control applications associated with each peripheral have direct access to the server. Alternatively, the control application associated with each peripheral may access the server indirectly, eg, via a communication controller, so that the communication controller assists in communicating with the server. Respond to each of the control applications. [0031] The network may include the information database (legacy host) by means of a communication link extending between the information database (legacy host) and the server. [0032] According to the fourth aspect of the present invention, by transmitting the ID of any peripheral device that failed to confirm the receipt of the preceding communication, the functional of the other peripheral device from the connection system including the transaction processing terminal device. Peripherals are provided to notify the deviation. [0033] This transmission can be in the form of broadcast communication. [0034] According to the fifth aspect of the present invention, a transaction is performed by removing the reference mark in the internal register for any peripheral device that signals that it has shut down or failed to respond to the preceding communication. Peripherals are provided that record functional deviations of other peripherals within a connected system, including processing terminal devices. [0035] Preferably, this peripheral has a memory queue that stores messages coming in from other peripherals that are part of one functional group, and those messages are stored in that queue in the order in which they were received. , The device accesses the first stored message, and once accessed, removes one message from its queue. [0036] According to the sixth aspect of the present invention, a functional group consisting of a plurality of peripheral devices is provided so as to identify a functionally existing device and to be directed to communication within the functional group consisting of the plurality of devices. A functional group consisting of a plurality of peripheral devices that cooperate with each other via communication over a connection network in which the dynamic registers used are maintained synchronously is provided, and the functional group provides a transaction processing terminal device. Includes. [0037] According to the seventh aspect of the present invention, a plurality of network-connected peripheral devices that cooperate with each other via peer-to-peer communication, the network-connected device, and a server connected to the network. A transaction terminal device is provided that allows communication between devices but includes a firewall that prevents peer-to-peer communication between devices from being transmitted to the server. [0038] According to an eighth aspect of the invention, as a container for software used by multiple collaborative peripherals communicating over a connected network, and by at least one of the peripherals to process a transaction. A server device that operates as a proxy server (proxy server) for the required data is provided. [0039] According to a ninth aspect of the invention, a peripheral is provided, based on the hardware state communicated through an interface to the hardware under the control of the peripheral, and from other peripherals across the connected network. Peripherals are provided that act as state machines based on received messages. [0040] Examples of the present invention will be described below with reference to the remaining drawings in the accompanying drawings for illustrative purposes. [0041] BEST MODE FOR CARRYING OUT THE INVENTION As referred to in FIG. 2, a block diagram of a software control of a peripheral device according to an embodiment of the present invention is shown, where similar numbers in FIG. 2 refer to similar features or configurations in FIG. Is what you do. In Figure 2, the ATM26 includes four peripherals 16,18,20,22, each with a corresponding control application 30,32,34,36. For example, the card reader 16 has an associated card reader control application 30. Each of these control applications is connected to the server 14 via a communication controller 38 that assists in communicating with the server 14 in response to each of the control applications 30, 32, 34, 36. Each control application (eg, 30) controls its associated peripheral (eg, 16) using a dedicated device driver (not shown) for that peripheral. [0042] As referenced in FIG. 3, a self-service network 100 in the form of an ATM transaction network, including an ATM 102, which is part of a wide area network and is connected to the server 14 via an upper communication link 104. A block diagram is shown. Link 104 provides efficient data transfer from server 14 to ATM 102. The transaction database (or legacy host) 12 is also connected to the server 14 via the traditional communication link 106. [0043] The ATM 102 includes a card reader 116, a receipt printer 118, a cash dispenser 120, an encrypted keyboard 128, and a display 130 (the keyboard 128 and the display 130 jointly form a user interface). Contains peripheral equipment. A typical ATM keyboard will have a numeric keypad and a small number of additional keys that can be labeled as "ENTER", "CANCEL", and so on. These peripherals 116,118,120,128,130 are connected by RS-232 link 136 to the central processor 138 housed in the ATM102. [0044] The ATM 102 also has a mass storage device 140 in the form of a hard disk. This hard disk 140 stores at least one device driver and at least one control application (similar to 30,32,34,36 in Figure 2) for peripherals 116,118,120,128,130. The TCP / IP protocol is used for communication within ATM102. [0045] When power is applied to the ATM 102, the central processor 138 is initialized, which includes loading device drivers and control applications from the mass storage device 140 into the central processor 138. Each control application is a process that runs independently on processor 138. Once the device driver and control application is loaded on the central processor 138, the control application performs a team creation process to form a team of multiple peripherals as described below. [0046] As part of the team building process, the control application for each peripheral creates a functional group register that is stored as a linked list (link list). The first entry on this list is the peripheral itself, the other entries are used for other peripherals. Figure 4A shows the completed functional group register 150 for a card reader control application. This register 150 has an entry for each peripheral that can be part of its team, including card reader peripherals. Each entry has three fields: peripheral device identification field 152, peripheral device IP address field 154, and port address field 156. [0047] Peripheral IP address field 154 is the address of the processor on which the control application associated with the peripheral operates. Thus, in the embodiment of FIG. 3, the peripheral device IP address field 154 for each peripheral device is the same, which is the address of the processor 138 that runs all the control applications. However, in an embodiment where each peripheral operates its associated control application on its own processor, such an address field 154 will include the address of the associated peripheral processor, i.e. the address of each peripheral. Field 154 is different. [0048] The port address field 156 on which each peripheral receives the signal is predetermined and is written within the control application associated with that peripheral. [0049] First, register 150 for the card reader control application leaves all entries in the peripheral identification field 152 blank, except for the identifier of its associated peripheral, as shown in FIG. 4B. It will appear as shown. [0050] Even if the peripheral receives power, it may not be valid for use and therefore may not be valid for joining the team. For example, a peripheral may be shut down due to a malfunction and needing replenishment of paper (in the case of a receipt printer) or currency (in the case of a cash dispenser). Therefore, the card reader control application performs a card reader test to ensure that the card reader is functioning properly. If the card reader is functioning properly, the control application will broadcast the validity of joining the team to other control applications by broadcasting a startup signal ("HELLO message"). Suggest. [0051] Broadcast messages on TCP / IP networks use a special pending IP address (255.255.255.255). A broadcast communication message is received for each node (for each device having an IP address) connected to the TCP / IP network. [0052] The "hello" message includes an identifier for the peripheral being initialized and an address on that peripheral to receive the signal. For example, a card read control application might have an identifier "card reader", a processor address "178.132.152.212" (from processor IP address field 154), and a port address (from port address field 156). Transmit "6040". The TCP stack in processor 138 does not carry broadcast communications across the physical layer, recognizing that its IP address "178.132.152.212" is only relevant to itself. Control applications associated with other peripherals (running on processor 138) will receive this "hello" message, and if it is useful to join the team, they will respond accordingly. Register 150 will be updated. [0053] As you can see, the IP address used in this example ("178.132.152.212") is just one example of a typical IP address. [0054] If the cache dispenser control application transmits a "hello" message with the identifier "cash dispenser", the IP address "178.132.152.212", and the port address "6010", the card reader control application The register 150 is to be updated and contains this information as shown in Figure 4C. Each peripheral control application thus maintains a register of identifiers (or IDs) and addresses for all other active peripherals in the team. [0055] Once the team-building process is complete, the individual control applications running on the central processor 138 use client-server technology to communicate with server 14 to obtain customer-specific transaction information from legacy host 12. [0056] The team-building process also causes Display 130 to determine which peripherals are available and therefore which services should be displayed to offer to the user, with services that are not available in different colors. Show or hide at all. [0057] As you can see, while the ATM102 is running, all control applications reside in the central processor 138, but each control application is independent of the other control applications. [0058] [0058] Peripherals may withdraw from the team in the event of a malfunction during operation (for example, if the card jams in the card reader 116 or the paper jams in the receipt printer 118). it can. To do this, the control application for the peripheral sends a shutdown signal (a "GOODBYE" message) to suggest that it is no longer available. This "Gubai" message contains the ID or identifier of the peripheral device to be withdrawn. Each control application in the team updates the register 150 by removing the reference mark for the withdrawal peripheral from the register 150, thereby removing the peripheral from the team. [0059] If the peripheral is physically removed, or if the power to the peripheral goes down, the first application module that attempts to send a message to the now missing peripheral , It will detect that the peripheral is missing and is sending a "Gubai" message instead. In such a case, the "Gubai" message contains the ID of the missing peripheral rather than the ID of the peripheral device sending the "Gubai" message. Control applications for other (residual) peripherals update their registers in response to this "give" message. [0060] When the peripheral is reconnected, its associated control application broadcasts a "hello" message, allowing other control applications to update their registers 150. Once the team creation process is complete, any new peripheral will need information about the current members of that team. Therefore, when a "hello" message is received after the team creation process is complete, each active control application (ie, the control application for each active peripheral) retransmits the "hello" message and joins. Allows peripherals to create the exact register 150 for that team. [0061] Individual control applications are configured to operate as a team, and each application module can be considered as a team member or peer (or colleague). [0062] Having a common application flow for all control applications ensures uniformity or uniformity such that each control application interfaces to another control application or any other device in the ATM102. [0063] A control application is a driven event. Internal events (eg, user input or hardware activity) drive the state of each control application. When the state of one control application changes, it sends the appropriate message to all other members of the team (ie, all other active control applications). Events based on these messages are used to allow other control applications to set themselves to the proper state. [0064] As the state of any control application changes, event messages are broadcast to allow other members of the team to act appropriately. The state of the control application can change as a result of, for example, a hardware event, user input, or a time-out state. [0065] ATM102 operates as an event-driven system. A message is transmitted from a control application for a peripheral device in which an event is occurring internally to another control application in the ATM 102. These other control applications may or may not be related to the event. A typical transaction sequence is shown in Figure 5 for ATM102. [0066] As referenced herein in FIG. 5, column 160 shows a sequence from multiple events and the event messages associated with them. The second row 162, the third row 164, and the fourth row 166 follow the generation of each event message listed in the first row 160 of the display 130, the card reader 116, and the cash dispenser 120. Shows all operations. In the second column 162 showing the operation of the display 160, the wording in the quotation marks is an example of text display to the user. [0067] If the ATM102 is operating with a team of peripherals including a card reader 116, a receipt printer 118, a cash dispenser 120, a keyboard 128, and a display 130, the card will be card reader 116 by a new user. At the time of the event inserted into, the message "CARD_INSERTED" is transmitted by the card reader control application to other peripherals in the team. [0068] Due to the influence of the message, the display 130 is made to display the text "Enter PIN". When the user enters a PIN (Personal Identification Number), the "Verify User PIN" operation occurs. This would involve using link 104 to communicate with the leverage host 12 via server 14. If the PIN entered is found to be valid for that particular card inserted into the card reader 116, the display 130 will be notified accordingly and its control application will be "USER_VALID". Generate an event message. This will display the cache selection request. The user then enters an event message, a specific amount that causes the transmission of "CASH_REQUEST". [0069] This "CASH_REQUEST" message activates the cache dispenser 120 to calculate its request amount and at the same time causes the display 130 to display the text "Calculating your cache" on its screen. When the cache dispenser 120 completes its task, its associated control application generates and transmits a "CASH_STAGED" message. Upon receiving this "CASH_STAGED" message, the card reader 116 partially presents the inserted card from the card entry slot on the ATM 102, allowing the user to remove the card. The control application associated with the card reader 116 then transmits the event message "CARD_PRESENTED" to display the text "Please take the card" on the display 130. [0070] When the card reader 116 detects a card removal, its associated control application generates and transmits a "CARD_TAKEN (card removed)" message. Upon receipt of this "CARD_TAKEN" message, the cash dispenser 120 presents the calculated cache. When the cache is presented, the control application associated with the cache dispenser 120 will generate and transmit a "CASH_PRESENTED" message to display "Please take cash" on the display 130. Display it. Reaching the cache removal detection of the dispenser 120, the associated control application transmits a "CASH_TAKEN (cache removed)" message to all control applications associated with each module in its team. Upon receipt of this "CASH_TAKEN" message, each peripheral control application in the team resets its corresponding peripheral to its initial state ready for other users. [0071] It is clear from the above description that the messages listed in column 160 of Figure 5 are used to drive individual and separate applicable peripherals, thus exemplifying overall operation. .. [0072] Various messages are transmitted to all peripherals, but in many cases only one peripheral or only some of the peripherals will use those messages. For example, the card reader 116 may need to know the cash withdrawal amount entered by the user, and if the cash withdrawal is validated by the server 14 and distributed by the cash dispenser 120, the card can be properly renewed. Will be. Although not shown in Figure 5, there are various communications that occur between the individual peripherals and the server 14 and the legacy host 12. [0073] An alternative hardware architecture that can provide an embodiment of the invention is shown in FIG. 6, which includes multiple intelligent devices including a card reader 216, a receipt printer 218, a cache dispenser 220, and a user interface 222. Shown is an ATM transaction network 200 with an ATM 202 with peripherals. User interface 222 includes both a keyboard and a display unit. [0074] The fundamental difference between the peripherals in FIGS. 3 and 6, such as the difference between the card reader 116 and the card reader 216, is that the peripherals in FIG. 6 operate individually and independently of any central processor. That is, it is built so that each peripheral can communicate directly with the server 14, software can be downloaded from them, and the downloaded software can be downloaded on its own processor. It can be operated to operate directly. However, in contrast, the peripheral in Figure 3 communicates directly with the server 14, downloads software from hard disk 140, and centrally operates the downloaded software to control the peripheral. -Controlled by processor 138. [0075] However, in both embodiments (Figures 3 and 6), control applications for peripherals, whether running on a central processor (Figure 3) or within separate peripherals (Figure 6), are mutually exclusive. It communicates and operates according to mutually generated signals. [0076] In FIG. 6, each peripheral device 216,218,220,222 has an embedded processor, associated volatile memory (eg, 32 megabyte RAM), non-volatile memory for launching the peripheral device, and a TCP / IP network connection. The ATM 202 is connected to the server 214 by a communication link 204, which is part of a wide area network (WAN) that connects multiple ATMs to the server 214. Link 204 is a high bandwidth network connection that enables efficient and quick download of software and utilizes TCP / IP transfer protocol. [0077] A feature of the communication link 204 is that each peripheral device 216,218,220,222 in the ATM 202 is directly and independently connected to the server 214 via the link 104, thus being an individual client-to-server 214. This is required in this embodiment because each peripheral must be able to download the software independently of the other peripherals. As in the third embodiment, the server 214 is connected to the legacy host 12 (basic financial information database) via the communication link 106. [0078] The control application used by the peripheral device in ATM 102 is stored in server 214. The same application software can also be used by the corresponding peripherals in other terminals within network 200 linked to server 214. Thus, one advantage of this configuration is that the control application software can be updated on server 214 and all related peripherals will download the updated software, thereby centralizing the software update. .. [0079] In addition to the link 204, which provides a direct connection from each peripheral 216,218,220,222 to the server 214, the link 204 also allows for communications that occur between the individual peripherals 216,218,220,222 of the ATM 202. In this way, information about the operating state of any of the peripherals 216,218,220,222 can be transmitted to all other peripherals 216,218,220,222. [0080] [0080] When a peripheral device (eg, 216) is first powered up, it boots up using non-volatile memory and then transmits a message to server 214. Upon receiving this message, the server uploads the software to its peripheral, allowing the peripheral to initialize and begin the team-building process. [0081] Although the hardware architecture of FIG. 6 is different from that of FIG. 3, the team creation process and the subsequent behavior described with reference to FIGS. 4 and 5 are identical in these two examples. FIG. 7 shows a typical functional group register 150'for the embodiment of FIG. 6, as each peripheral device in its terminal device has a processor in each peripheral device running its associated control application. Have different IP addresses. [0082] During operation, one request is made to the server 214 by the peripheral device, the information specified by the user is requested, and the current transaction is properly performed. For example, the cash dispenser 220 will require the user's current balance to determine if it has sufficient funds for the requested cash withdrawal. User interface 222 may require account balance and periodic account reporting, which are displayed to the user. [0083] By having a direct connection from the peripheral device to the server 214, it is possible to avoid using the central processor and the mass storage device. [0084] As you can see, the functionality of the communication controller 38 shown in FIG. 2 can be incorporated into the central processor 138 (Example 3) or into each peripheral device 216,218,220,222 (Example 6). It is possible, or it can be an individual network router that transfers data from each peripheral device 216,218,220,222 (Figure 6 Example) to server 214 (Figure 6 Example). [0085] The individual control applications running in any of the hardware embodiments of the invention (FIG. 3 or 6) are configured to operate as a team, and each application module is a team member or peer (or peer). Is considered as a colleague). [0086] Various modifications can be made to the above embodiments within the scope of the invention, eg, the communication link 104 is any convenient link and is part of a local area network. It is possible, or it can be a dedicated link with a dial-up modem connection. In another embodiment, the communication link 204 can be a low speed dial-up modem, for example for a single off-site terminal device. In other embodiments, communication mechanisms other than the RS-232 link 136 can be used, for example, USB (Universal Serial Bus), Firewire, or Ethernet Link. [0087] In embodiments where secret transactions are processed, a firewall can be used to ensure that the transaction is secured and that its peripherals are accessed by unauthorized persons. .. The firewall runs between server 14 and leverage host 12. [0088] In an embodiment where a point-of-sale (POS) terminal device is used in a network, the legacy host can be a retail information database. In another embodiment, the address of another peripheral that can receive the signal can be written to the control application for each peripheral, and each control application can write the address of its associated peripheral or all of the other peripherals. Get to know the possible addresses of. In other embodiments, different communication protocols may be used, eg RS232 based protocols may be used instead of TCP / IP. [Simple explanation of drawings] FIG. 1 is a block diagram showing an ATM network according to the prior art and software control of peripheral devices in the ATM. FIG. 2 is a block diagram showing software control of peripheral devices in an ATM according to an embodiment of the present invention. FIG. 3 is a block diagram of an ATM network according to an embodiment of the present invention. 4A, 4B, and 4C are tables showing the features of the embodiment of FIG. FIG. 5 is a flowchart showing a typical event sequence in an ATM terminal device as shown in FIG. FIG. 6 is a block diagram of an ATM network according to an alternative embodiment of the present invention. FIG. 7 is a table showing the features of the embodiment of FIG. [Explanation of symbols] 12 Legacy host 14,214 server 16,116,216 card reader 18,118,218 Receipt Printer 20,120,220 Cash dispenser 22,128,130,222 User interface 24 Central Program 26,102,202 ATM (automated teller machine) or self-service terminal 30,32,34,36 Control application 38 Communication controller 100 cell service network