Increasingly consumers are conducting financial transactions through Self-Service Terminals (SSTs) without the assistance of a clerk. In fact, in many cases these transactions are conducted without any individual in the vicinity of the SSTs; other than, perhaps, a security camera integrated into the SSTs or in proximity to the SSTs. The most common SST transaction occurs by a customer at an Automated Teller Machine (ATM).
An ATM may be configured to self-configure as much as possible by requiring minimal information to enable it to communicate with a configuration server in the enterprise. Service personnel enter this information into the ATM that is being setup so that the ATM may use this information to access the configuration server to complete the configuration process. It is up to the service personnel to correctly entering this minimal information as efficiently and effectively as possible. However, manual human input at the time of installation is “lengthy” and error prone (e.g. inputting the data using the keyboard), which leads to extra time spent on installation and possibly further causing human error and frustration.
In various embodiments, methods and a system for providing self-configuration of Self-Service Terminals (SST) are presented.
According to an embodiment, media is used to providing initial configuration information to an SST, such as an ATM. Specifically, in an embodiment, configuration connection details are obtained and the configuration connection details are used to connect to a configuration server and configure a self-service terminal (SST).
The techniques, methods, and system presented herein and below for supporting SST configuration processes can be implemented in whole or in part in one, all, or some combination of the components shown with the architecture 100. The techniques and methods are programmed as executable instructions in memory and/or non-transitory computer-readable storage media and processed on one or more processors associated with the various components.
The discussion of the architecture 100 is within the context of a banking facility for banking transactions that may be made in person and at Automated Teller Machines (ATMs). It is noted that the architecture 100 is also applicable to any enterprise providing SSTs and in-person customer assistance. Thus, the description that follows below is but one embodiment and it not intended to limit embodiments to financial transactions at financial facilities.
The example architecture 100 includes a bank branch 110, an Automated Teller Machine (ATM) 120, a branch server 140, and an external financial system 150. The bank branch 110 includes the Automated Teller Machine (ATM) 120 operated by customers, and a branch server 140.
The ATM 120 includes an application 122 and an encryptor 130. The encryptor 130 may include a secure microprocessor 131. The ATM 120 is presented in greatly simplified form and is used to illustrate those portions of components modified for purposes of providing configuration processes. The application 122 includes an Application Programming Interface (API) for interacting with the encryptor 130 and the local bank server 140. The application 122 also includes a forward-facing Graphical User Interface (GUI and not shown in the
The bank server 140 communicates with the ATM 120, which includes an application 122, an assistance interface 124, a transaction interface 126, a encryptor 130, and a secure processor 131. The interaction of the components is now discussed with an example configuration and operational scenario. It is noted that other scenarios are possible without departing from the beneficial teachings provided herein.
According to an embodiment, media 160 may be used to store information used to semi-automate the input of relevant information at a newly installed ATM 120, e.g., a physically installed ATM 120 on site rather than a software installed ATM. The ATM 120 may read the relevant, initial configuration information from the media 160 and connect to the correct configuration server 170 with the information for completing the self-configuration.
The ATM 120 seeks to self-configure as much as possible by requiring minimal information for the initial configuration information to enable the ATM 120 to communicate with the configuration server 170 in the enterprise or bank branch 110. By providing the initial configuration information on media 160 for semi-automating the configuration process, reduces time spent on installation and possible human error and frustration.
The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments that may be practiced. These embodiments are also referred to herein as “examples.” Such examples may include elements in addition to those shown or described. However, also contemplated are examples that include the elements shown or described. Moreover, also contemplate are examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.
Publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) are supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to suggest a numerical order for their objects.
The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) may be used in combination with others. Other embodiments may be used, such as by one of ordinary skill in the art upon reviewing the above description. The Abstract is to allow the reader to quickly ascertain the nature of the technical disclosure, for example, to comply with 37 C.F.R. §1.72(b) in the United States of America. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features may be grouped together to streamline the disclosure. However, the claims may not set forth features disclosed herein because embodiments may include a subset of said features. Further, embodiments may include fewer features than those disclosed in a particular example. Thus, the following claims are hereby incorporated into the Detailed Description, with a claim standing on its own as a separate embodiment. The scope of the embodiments disclosed herein is to be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.