Self-service terminal and method

Abstract

According to various aspects, a self-service terminal (100) comprises: a user interface (1008) to provide information to a user of the self-service terminal (100); an interface modification button (206); a control device (106) configured to: determine whether an interface interaction mode of the self-service terminal (100) is a first interface interaction mode or a second interface interaction mode; in response to a user input at the interface modification button (206), the following modifications are directed: when the interface interaction mode is a first interface interaction mode, a first perceptible attribute assigned to the information; and a second perceptible attribute assigned to the information when the interface interaction mode is a second interface interaction mode.

Description

Technical Field

[0001] Various aspects are generally directed to a self-service terminal and method. Background Art

[0002] Traditionally, a variety of services are provided via so-called self-service terminals. As a general concept, a self-service terminal enables a user to request and complete services autonomously, for example, without human assistance.

[0003] As an example, in a traditional retail market, a self-service checkout terminal provides customers with the possibility to scan the desired products themselves (e.g., without assistance) as an alternative to having the products scanned by a cashier. Such a self-service checkout terminal provides faster checkout, more anonymity for customers and less labor costs for the retail market. With a self-service checkout terminal, each customer, instead of a cashier, scans the barcode of the product to be purchased. Another example is an automated teller machine.

[0004] The general challenge of such services is that the hardware of the self-service terminal must meet multiple criteria to be suitable, and the user operates the self-service terminal through this hardware. One of the criteria includes that the operation concept should be as intuitive as possible. Another criterion includes that the interaction should be as convenient and / or ergonomic as possible. However, minimizing the cost of the hardware is another criterion. In summary, conventional hardware is optimized to try to meet the criteria of the largest possible population (e.g., potential customers). Of course, the resulting configuration is not the most suitable for everyone. For example, some people, such as children or wheelchair users, may not be able to access the full range of hardware, which is optimized for standing adults. Conventional concepts to address this gap are costly, unintuitive, and usually only address one access problem. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Throughout the drawings, it should be noted that like reference numerals are used to depict the same or similar elements, features, and structures. The drawings are not necessarily to scale, but rather emphasis is generally placed on illustrating various aspects of the present disclosure. In the following description, some aspects of the present disclosure are described with reference to the following drawings,

[0006] in:

[0007] Figure 1 and Figure 2 Schematic diagrams are respectively used to illustrate self-service terminals according to various aspects;

[0008] Figure 3 and Fig. 9 A self-service terminal according to various aspects is shown in schematic views respectively;

[0009] Figure 4 and Figure 8The methods according to various aspects are respectively shown in schematic flow charts; and

[0010] Figure 5 , Figure 6 and Figure 7 Interface modifications according to various aspects are shown in schematic diagrams respectively. DETAILED DESCRIPTION

[0011] The following detailed description relates to the accompanying drawings, which illustrate by way of illustration the specific details and aspects in which the present disclosure may be practiced. One or more aspects are described in sufficient detail to enable those skilled in the art to practice the present disclosure. Other aspects may be utilized, and structural, logical, and electrical changes may be made without departing from the scope of the present disclosure. Each aspect is not necessarily mutually exclusive, as some aspects may be combined with one or more other aspects to form new aspects. Various aspects are described in conjunction with methods, and various aspects are described in conjunction with devices. However, it is to be understood that the aspects described in conjunction with methods may be similarly applicable to devices, and vice versa. Throughout the accompanying drawings, it should be noted that similar reference numerals are used to depict the same or similar elements, features, and structures.

[0012] The present disclosure relates to various functions (eg, sequences). The functions may be implemented by hardware components and / or may be embodied in computer-readable instructions (such as software), which may be used to cause a general or special-purpose processor or other logic circuits programmed with the instructions to perform the functions.

[0013] As an example, the term "processor" as used herein, for example, can be understood as any kind of entity that allows processing data, signals. As an example, data, signals can be processed according to one or more specific functions performed by the processor. Therefore, as an example, the processor can be or include an analog circuit, a digital circuit, a mixed signal circuit, a logic circuit, a processor, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a field programmable gate array (FPGA), an integrated circuit, an application-specific integrated circuit (ASIC) or any combination thereof. Any other kind of implementation of the corresponding function described in further detail below can also be understood as a processor or a logic circuit. It should be understood that any two (or more) of the processors or logic circuits described in detail herein can be implemented as a single entity with equivalent functions, and conversely, any single processor or logic circuit described in detail herein can be implemented as two (or more) separate entities with equivalent functions. It should be understood that one or more of the method steps described in detail herein can be performed (e.g., implemented) by a processor, which can be one or more specific functions performed by a processor.

[0014] The term "control device" (also referred to as a controller) may be understood as any kind of logic implementation entity, which may be a dedicated circuit or a processor that executes software stored in a memory, firmware, or any combination thereof. Thus, a "control device" may include a hardwired logic circuit or a programmable logic circuit, such as a programmable processor, for example a microprocessor (e.g., a Complex Instruction Set Computer (CISC) processor or a Reduced Instruction Set Computer (RISC) processor). A "control device" may additionally or alternatively include one or more processors that execute software or at least code segments, such as any kind of computer program, for example, a computer program using a virtual machine code (such as, for example, Java).

[0015] According to various aspects, one or more functions implemented by one or more processors may be illustratively implemented as a counterpart by a code segment stored in a memory, wherein if the code segment is executed by one or more processors, the code segment causes the one or more processors to perform a process (e.g., functions and methods). The code segment, for example, provided as part of software, can be updated, for example, via a (e.g., mobile) network as needed.

[0016] Reference to a condition of a process or function, for example using terms such as "if" and "when", may, for example, include that the process or function is performed in response to the condition (eg, triggered by the condition).

[0017] The control device can be configured to control one or more components of the self-service terminal, for example, by guiding one or more components. The process of guiding can include generating instructions (for example, as messages) and transmitting the instructions to the components to be controlled. The control device can optionally include a memory, for example, storing a code segment representing a function implemented by the control device, for example, controlling one or more operating functions. Additionally or alternatively, the memory can store one or more criteria, rules, and algorithms, as examples, as described in detail herein.

[0018] As used herein, "memory" is understood to be a computer-readable medium (e.g., a non-transitory computer-readable medium) in which information can be stored for retrieval. Therefore, references to "memory" included herein are understood to refer to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state memory, magnetic tape, hard disk drives, optical drives, 3D XPoint TM and others or any combination thereof. Among others, registers, shift registers, processor registers, data buffers are also included in this document by the term memory. The term "software" refers to any type of executable instructions, including firmware.

[0019] Unless expressly specified, the term "transmit" covers both direct transmission (point-to-point) and indirect transmission (via one or more intermediate points). Similarly, the term "receive" covers both direct reception and indirect reception. Further, the terms "transmit", "receive", "transfer", "send", "output" and other similar terms cover both physical transmission (e.g., transmission of signals, such as electric current) and logical transmission (e.g., transmission of digital data through a logical software-level connection). For example, a processor or controller can transmit or receive data in the form of signals with another processor or controller through a software-level connection, wherein the physical transmission and reception are handled by a signal transmission layer component (such as a transceiver), and the logical transmission and reception performed through the software-level connection is performed by the processor or controller. The term "transfer" covers one or both of transmission and reception, i.e., unidirectional or bidirectional communication in one or both of the input and output directions.

[0020] The transmission of information (information transmission), for example for guidance, may be in accordance with a (e.g., network) communication protocol. Generally, the transmission of information may include generating and / or sending messages including information (e.g., instructions) in accordance with a communication protocol. A communication protocol may indicate an agreement according to which information is transmitted between two or more components. In its simplest form, a communication protocol may be defined as a set of rules that define the syntax, semantics, and synchronization of the transmission. The communication protocol(s) used (e.g., one or more network protocols) may (but need not) be configured in accordance with an OSI (Open Systems Interconnection) reference model. Any protocol may also be used in the respective protocol layers. For example, the transmission of information via a certain type of network may include generating and / or sending messages including information in accordance with a network communication protocol.

[0021] As used herein, the term "information" may be understood to include information in any suitable (e.g., analog or digital) form. Examples of information may be provided as computer-readable information, transmitted by (e.g., electrical, electromagnetic, mechanical, optical, etc.) signals (e.g., sound or light), include or be user-perceivable information (e.g., transmitted by sound waves or visible light), etc. However, the term information is not limited to the above examples, and may take various forms and represent any information understood in the art.

[0022] The term "user interface" (also referred to herein as UI) may be understood as any type of entity that is capable of interacting with a user (also referred to herein as human-computer interaction), for example, to provide the user with control of a machine (e.g., a terminal) and to feed information back to the user. The user interface may include one or more layers, at least one of which (also referred to as a human-computer interface device, user interface hardware, user interface device, or simply an interface device) interfaces the machine with physical input hardware and physical output hardware (e.g., speakers and screens) that sense the user's input (also referred to as user input). The human-computer interface device may interact with one or more human senses, including, by way of example, touch senses (providing tactile perception), visual senses (providing video perception), auditory senses (providing audio perception), and the like. Other layers of the user interface may include a signal transmission layer, a data processing layer (e.g., processing data representing user input or data representing information provided to the user), a control layer, a data interface layer, and the like.

[0023] The term "interface interaction mode" may be understood herein as an operation mode related to the type of user perception used for human-computer interaction (e.g., interaction between a user and a self-service terminal (e.g., its UI)). For example, according to the user's perception ability, human-computer interaction may be based on video (e.g., image) perception, based on audio (e.g., auditory) perception, based on touch perception (such as force perception or tactile perception), and the like. When the self-service terminal is in the interface interaction mode, each interface interaction mode may correspond to one or more types of user perception used for human-computer interaction. Therefore, examples of interface interaction modes may include video interaction mode (e.g., video-only interaction mode), audio interaction mode (e.g., audio-only interaction mode), non-video interaction mode (without vision), and the like. In the video user interaction mode, video-based (e.g., visible) information may be provided, where the user may respond to each touch, voice, gesture, and the like. The same may apply to one or more other user interaction modes referenced herein.

[0024] Different interface interaction modes differ from each other in terms of at least one type of user perception used for human-computer interaction. Therefore, the self-service terminal, such as its UI, may be able to appeal to the type of user perception, for example, the senses (also referred to herein as human senses or perceptual senses) used for the type of user perception. For example, for each interface interaction mode, the self-service terminal, such as its UI, includes at least one user interface device, which is configured to interact with the user based on the type of user perception corresponding to the interface interaction mode. For example, the self-service terminal may include a video (e.g., graphical) user interface for implementing a video interaction mode (e.g., a visual-based interaction mode) and / or include an audio user interface for implementing an audio interaction mode (e.g., a voice-based interaction mode).

[0025] The video UI may include at least one display device (in other words, one or more devices) as a human-machine interface device and a graphical UI that provides data-based graphics (including symbols and other graphical elements, for example, enhanced by text), and the graphics are displayed by at least one display device. The graphical UI may include multiple layers, including: a client layer (for example, including one or more clients), a display processing layer, and a display driver layer (for example, implemented by a kernel). The display processing layer may include a display server layer and / or a graphical interface layer. The display processing layer connects the client layer (for example, a software application, also referred to as an operating application) to the display driver layer. The display processing layer may receive data from one or more clients of the client layer, process the data, and transmit the data to the display driver layer (for example, as a component of the kernel). The display driver layer writes the data to a frame buffer. The contents of the frame buffer are transmitted to the connected display device.

[0026] The term "button" may be understood as a type of physical input hardware (e.g., implemented by a sensor) that is configured to sense user input, for example, by sensing user interaction using a button. For example, a user interaction may include a force imparted to a button by a user, for example, when a user presses a button. For example, a user interaction may include physical contact with a user, for example, when a user touches a button. Exemplary embodiments of a button may include: a push button, a touch button, a soft button (also referred to as a soft key, which is a function key marked on a screen), a switch, and the like.

[0027] According to various aspects, the modification (e.g., reconfiguration) of the user interface can be triggered by a user input at an interface modification button. The modification of the user interface can modify one or more parameters representing the perceptible attributes of the output of the user interface. The type of perceptible attribute can be a function of the interface interaction mode. For example, the perceptible attribute can be modified by modifying one or more video (e.g., visual) parameters, one or more audio (e.g., auditory) parameters, and / or one or more tactile parameters. For example, the perceptible attribute can be an attribute of one or more programmable interface components (such as soft keys or other graphical operating elements), an auditory output, etc. A soft key is a button that can be flexibly programmed to call any type of function, rather than being associated with a single fixed function or a set of fixed functions. Examples of soft keys can include: function keys marked on the screen, function keys displayed on the screen (e.g., implemented via a touch screen). As an example, the perceptible attribute can be a visual attribute of a graphical output of the UI, or (e.g., in the case of an audio parameter) can be represented by an electrical signal (e.g., its amplitude) output by the UI or digitally encoded by the electrical signal.

[0028] As an example, changing the configuration of a user interface (also referred to as modifying the user interface) can change the soft keys (as an example for graphical interface components) in one or more of the following properties: position (also referred to as rearrangement), size (also referred to as resizing), color, brightness, and / or labeling. For example, a user in a wheelchair can be enabled to access all relevant soft keys by rearranging relevant soft keys near the bottom-most position of the user interface (e.g., a touch surface). Interface modifications can change configurations at the client layer, display processing layer, and / or display driver layer (e.g., a combination thereof). For example, scaling of a graphical operating element can be defined by the client layer (e.g., within a running software application) and / or by the driver layer (e.g., defining a rendering scale).

[0029] Changing the interface interaction mode can facilitate the user's interaction with the self-service terminal, for example, according to the user's physiological condition, for example, according to the sensory condition, the body structure condition, the muscle movement condition (for example, motor skills) or a combination thereof. The physiological condition can be (but need not be) a severe or permanent disability. As an example, the physiological condition can reflect the physiological function capacity (PFC) of the person, for example, with respect to the task of operating the self-service terminal. In general, PFC refers to the ability to perform physical tasks of daily life and the ease with which a person can perform these tasks. PFC may automatically decline with age (even for healthy adults) and / or may decline with injuries that occur during a person's lifetime or after a person is born. It is understood that the reference to the physiological condition (also referred to as physiological condition) of a person (for example, a user of a self-service terminal) is not intended to assume a judgment of the physiological condition, but is related to the accessibility of the user interface of the self-service terminal. The interface interaction mode can be guided to be most suitable for a certain physiological condition or a series of physiological conditions, for example, a certain body height, visual and / or auditory function of a person. Any deviation therefrom may (but not necessarily) increase the difficulty of interaction between a person and the user interface, for example, the difficulty of operating the self-service terminal. For example, operating elements should be within reach of a wheelchair user, but due to market demands for ever larger touch screens, meeting these user-specific requirements is becoming increasingly challenging, or even impossible.

[0030] To address such deviations, the user interface (UI) of the self-service terminal can be modifiable in a technical sense, for example, in terms of size, type of interaction layer, arrangement of UI components, visibility of UI components, audio volume, and / or location of graphical UI components. For example, the UI of the self-service terminal can be temporarily configured to be accessible to users in a seated position or to a blind person as much as possible. The UI can be modified when a user requests it through a user input at an interface modification button.

[0031] The term "self-service terminal" may be understood as any type of (e.g., stationary or mobile) physical (e.g., ground or wall-mounted) terminal that is configured to perform a self-service session that provides execution (e.g., generation or use) of services to a user of the self-service terminal, e.g., without relying on the involvement of direct service employees. The self-service terminal may include a user interface for interacting with a user and a processor for operating the user interface according to the self-service session. As an example, the processor may be configured to guide the user through the self-service session via the user interface, e.g., via a dialogue, and / or communicate with a data source external to the terminal depending on the interaction with the user. The self-service terminal may optionally access a service database that stores service information according to the self-service session. For example, the service database may be at least partially stored in a memory of the self-service terminal and / or at least partially requested by the self-service terminal according to a network communication protocol (e.g., from an external data source). In some embodiments, the self-service session includes an initialization process for starting the self-service session. Examples of the initialization process may include a user identification (e.g., authentication) process requesting the user to identify himself and / or a service selection (e.g., authentication) process requesting the user to select one or more types of services from the services provided by the self-service terminal. In some embodiments, the self-service terminal, for example, its processor, may be configured to execute an operating system (e.g., Microsoft Windows) as the basis for one or more applications that provide a self-service session. It may be noted that such applications may not necessarily be executed locally by the self-service terminal, but may also be cloud-hosted and / or configured as a web application.

[0032] In the following, reference is made to a specific type of self-service terminal, such as an automated teller machine, which is not intended to be limiting. Exemplary types of self-service terminals include: automated teller machines (ATMs), bank terminals, self-service vending machines (e.g., for snacks, alcoholic beverages, cigarettes and / or jewelry), self-service checkout terminals, self-service gas stations, self-service scales, self-service kiosks, self-service information terminals (e.g., for providing information requested by users, such as geological areas, tourist destinations, etc.), self-service kiosks and bank terminals, self-charging terminals at gas stations, self-service ticket purchase terminals on the Internet, and self-service check-out terminals and / or vending machines at hotels. In general, a self-service terminal can be configured to provide a self-service session represented by an output of a UI (e.g., guided). Examples of self-service kiosks include information terminals and self-service ordering terminals (e.g., used in self-service restaurants and / or for accessing online stores). References to specific types of self-service terminals can similarly apply to other types of self-service terminals.

[0033] In an exemplary embodiment of a self-service session, a user may register a product that the user wants to purchase, for example by scanning the product with a product scanning device (e.g., a barcode scanner). Further, the self-service checkout terminal may include a (e.g., digital) cash register system (e.g., with a self-service cash register or cash register workstation), which is configured to perform a payment process. For example, the payment process may include a user initiating a financial transaction to pay for the product to be purchased. The cash register system may include one or more of the following components of a user interface: a screen (e.g., a touch-sensitive screen, also referred to as a touch screen), a printer (e.g., for printing invoices and / or labels), a (e.g., programmable) cash register keyboard (which may also be part of the touch-sensitive screen), a payment terminal for accepting a financial transaction medium (e.g., cash or a debit card). For example, the payment terminal may be an electronic payment terminal (also referred to as an EC terminal, "EC" - electronic cash, for example, for reading a debit card and / or a credit card). For example, the self-service checkout terminal may include a (e.g., digital) cash register system, which is configured to perform one or more cash register processes, such as a registration session. For example, a registration session may include a calculation process, an inventory process, and / or a registration process.

[0034] According to various aspects, one or more of the following are provided:

[0035] - the graphical output application is repositioned downward on the screen in response to user input at an interface modification button of a self-service terminal (e.g., as a vending machine) that may also provide a blind user with control over the audio volume (also referred to in this context as a volume control button);

[0036] - Facilitate compliance with the Americans with Disabilities Act (ADA) without fundamentally changing the system concept;

[0037] - Practical implementation of graphical interface modifications that are activated only when needed by the user, otherwise maintaining the normal "look and feel" of the graphical user interface (e.g., application);

[0038] -Compatibility with existing hardware in all aspects, without the need for application customization and dependency;

[0039] - Graphical interface modifications may be implemented by native functions of the kiosk's operating system (e.g. Windows, IOS or Android), for example via a magnification API (application programming interface);

[0040] - No need to develop proprietary mechanisms for each aspect of the implementation;

[0041] -Optimal user guidance by displaying a specific ADA user interface including a timeout (which automatically resets);

[0042] - Alternatively or additionally, after each click / touch on the UI, it is conceivable that the UI resets the image to make the application fully visible;

[0043] -Users can activate and reset functions independently;

[0044] - The available buttons of the self-service terminal can be used to implement the interface modification buttons,

[0045] - the available button can conventionally be used to allow a blind user to change the audio volume, but is conventionally disabled when no headphones are plugged in;

[0046] - When no earphones (e.g., including headphones) are plugged into the kiosk, the interface modification button can be used to reposition downward the image (or portion thereof) displayed by the UI;

[0047] - A flexible configuration can be implemented to limit the extent to which the image can be repositioned downwards;

[0048] - The interface modification may be adaptive, for example, according to the height difference (floor difference) between the self-service terminal and the ground (eg, street).

[0049] Generally, the modification of the user interface may be implemented by a software application executed by the kiosk (eg, by the control device). Additionally or alternatively, the modification of the user interface may include scaling the image at the driver / platform level.

[0050] Figure 1 A self-service terminal 100 (also referred to as a "terminal") according to various aspects is illustrated in a schematic diagram. The terminal 100 may include a user interface 1008. The user interface 1008 may include one or more of the following: a display device (e.g., including a touch screen), one or more microphones, one or more speakers, one or more audio connection devices, one or more physical keys (also referred to as buttons). The user interface 1008 may be configured to receive one or more inputs from a user (e.g., information including instructions, approvals, and / or selections) and / or present one or more outputs to the user (e.g., information including prompts, processing results, options, and / or explanations). In this way, the user interface 1008 may provide interaction with the user, for example, by exchanging information with each other.

[0051] User interface 1008 (UI) can include one or more interface devices as components, for example, configured as input devices and / or output devices. Examples of interface devices may include: one or more tactile interface devices (interacting via touch), one or more video interface devices (interacting via vision) and / or one or more audio interface devices (interacting via sound (e.g., voice)), for example, including one or more audio connection devices. For example, UI 1008 can be configured to implement one or more graphical user interfaces (also referred to as video UI or GUI) through one or more video interface devices. Each video interface device can be configured to display graphics, such as one or more graphical operation (e.g., input) elements. Similarly, UI 1008 can be configured to implement a tactile UI, which is configured to receive input from a user by touch and / or pressure. Additionally or alternatively, the tactile UI can be implemented via Braille interaction. Optionally, a video interface device can be combined with a tactile interface device to implement a visual / tactile UI 1008 (e.g., including a touch screen). Similarly, UI 1008 may be configured to implement an audio UI configured to provide voice interaction with a user via one or more audio interface devices, such as via audio output and / or audio input.

[0052] The terminal 100 may further include an interface modification button 206 (also referred to herein as an IM button). The IM button 206 may be configured to sense a user's input (also referred to as a user input), for example, by sensing that the user interacts with the IM button 206, for example, by sensing that the user presses and / or touches the IM button 206. In this way, the IM button 206 allows the user to interact with the terminal 100 in order to direct the interface modification.

[0053] The terminal 100 may include a control device 106. The control device 106 may be communicatively coupled to the IM button 206 and / or the user interface 1008. In this way, the control device 106 may communicate with the IM button 206 and / or the UI 1008. The communication coupling 101 may include a network, such as a CAN network, an Ethernet network and / or a communication bus (e.g., a universal serial bus), or any other type of data transmission coupling. The information transmitted to the control device 106 may be converted into data (also referred to as input data) for further processing by the control device 106. The information from the IM button 206 may include sensor data representing user input sensed by the IM button 206. The information from the user interface 1008 may include sensor data representing user input at the user interface 1008. The information transmitted to the user interface 1008 may include instructions for outputting information and / or modifying the user interface 1008.

[0054] The control device 106, the user interface 1008 and / or the IM button 206 may include a corresponding infrastructure (e.g., a processor, a storage medium and / or a bus system), etc., which implements a sensing and processing chain (SPC). The SPC may be configured to control (one or more) corresponding sensors, process the quantities sensed by them as input, and provide output representing the measurement results based thereon.

[0055] The control device 106 may be configured to determine (also referred to as "mode determination") whether the interface interaction mode (also referred to herein as the actual interface interaction mode) of the terminal 100 is the first interface interaction mode or the second interface interaction mode. For example, the first interface interaction mode may be a video interaction mode, for example, as a default interaction mode, or another default interaction mode. For example, the second interface interaction mode may be a non-video interaction mode, for example, an audio interaction mode, for example, an audio-only interaction mode.

[0056] In an example, the mode determination may be based on an indicator (also referred to as a mode indicator). The mode indicator may be a function of the actual interface interaction mode, or the actual interface interaction mode may be a function of the mode indicator. Examples of mode indicators may include: a state of the terminal 100 (e.g., a connection state), a user interacting with the terminal 100 (e.g., via), a perceptible (e.g., auditory) signal from the user, an operational state of the UI 1008, etc. The mode indicator will be explained in more detail later.

[0057] Herein, for demonstration purposes, reference is made to a video interaction mode and a non-video (e.g., audio only) interaction mode, which is not intended to be limiting. References to these modes may also apply to other types of modes, e.g., if more than two modes are applied and / or any other type of mode is used.

[0058] In one or more examples of terminal 100, terminal 100 may include one or more additional components 108 as described below.

[0059] In an example where the terminal 100 is a self-checkout terminal, the one or more additional components 108 may include a product scanning device 102 configured to scan one or more products. Illustratively, the product scanning device 102 may be operated by a user (also referred to as a self-service scanning process), for example, by presenting the product to be scanned to the scanning device 102. Thus, the user may register each desired product to be purchased at the terminal 100. For example, the product scanning device 102 may include an optical scanning device, an RFID (radio frequency identification) scanning device, etc. As an example, the optical scanning device may include a barcode scanning device or an image scanning device. The barcode scanning device may include respective sensors, such as one or more infrared sensors, one or more cameras, etc., to implement the scanning function.

[0060] In operation, a product (e.g., a market product) may have an information medium, such as a barcode and / or an RFID tag, scanned by the product scanning device 102. The information medium may include product information assigned to the product, such as by a product database. For example, the product information may represent a product identifier, a product type, or a product price.

[0061] In an example where the terminal 100 is an automated teller machine (ATM) or a self-service checkout terminal, one or more additional components 108 may include a bank teller safe configured to store one or more monetary documents (also referred to as document storage) that may be received from or provided to a user. The bank teller safe may include a cavity for document storage and a transfer device configured to transfer one or more monetary documents into and / or out of the cavity. The bank teller safe (e.g., its transfer device) may be configured to communicate with the control device 106. Communications between the bank teller safe and the control device 106 may be protected, for example, by one or more encryption processes.

[0062] Figure 2 The terminal 100 according to various aspects 200 is illustrated in a schematic diagram. The control device 106 can be configured to control (e.g., direct) 201c UI 1008 (also referred to as UI control). The UI control can include transmitting a control message 106m to the UI 1008. The control message 106m can include various information 201d (also referred to as user addressing information) addressed to the user, which can (but need not be) provided by the control device 106. In this context, the user addressing information 204 refers to logical information (e.g., self-service session related information) for the user, such as, for example, language (or at least text-based) information, cognitive information, dialog information, guidance information, etc. Examples of the user addressing information 204 can include: user control related information (e.g., input request, input graphics, such as a virtual keyboard or virtual signature pad, soft keys), financial transaction related information (e.g., account information, currency information, purchase information, payment information, cash withdrawal information, cash deposit information) or other self-service session related information (such as product information), etc.

[0063] The control message 106m may include one or more instructions 201c, for example, to direct 201c to modify the UI 1008 (also referred to as modification instructions in this case). The control device 106 may be configured to generate modification instructions in response to user input at the IM button 206, for example, according to a (e.g., stored) interface modification profile 222 (also referred to herein as an IR profile) and / or based on the interface interaction mode 212. The IR profile 222 may define one or more parameters of the UI 1008 (also referred to herein as modification parameters) that are changed by the interface modification, and / or the amount of change. Optionally, the IR profile 222 may be programmable, for example, when the terminal 100 is set to service mode.

[0064] The control device 106 may be configured to perform mode determination 212, for example, based on the mode indicator. As an example, the result of mode determination 212 may be output or stored. When the interface interaction mode (also referred to as the actual interface interaction mode) of the terminal 100 is the first interface interaction mode 212a (also referred to herein as the default case), the result of mode determination 212 may include (e.g., indicate) the first interface interaction mode 212a. When the interface interaction mode (also referred to as the actual interface interaction mode) of the terminal 100 is the second interface interaction mode 212b, the result of mode determination 212 may include (e.g., indicate) the second interface interaction mode 212b.

[0065] The control device 106 may be configured to determine a user input at the IM button 206. As an example, the control device 106 may receive an electrical signal 201b from the IM button 206 representing the user input.

[0066] The UI 1008 can be configured to convert the control message 106m into an output (also referred to as a UI output) according to the modification instructions and according to the user-addressed information 201d. According to various aspects, the UI output can include or be the user-addressed information 201d.

[0067] For example, UI 1008 may include an application (e.g., a GUI) that converts user-addressed information 201 d into data representing a data-based (e.g., graphical) representation of user-addressed information 201 d. For example, UI 1008 may include one or more device drivers that convert the data-based representation into output data, such as video data, audio data, etc.

[0068] To implement one or more of the one or more interaction modes, the UI 1008 may include an interface device 252 configured to provide a user-perceivable UI output (such as light, sound, Braille, etc.), for example, including one or more perceivable attributes related to (e.g., representing) the user-addressed information 201d. Exemplary implementations of the interface device 252 may include a loudspeaker, a display device, a tactile keyboard, etc. For example, the UI 1008 may include a screen (also referred to as a display device) as the interface device 252 to output the user-addressed information via a graphical representation presented by the screen. For example, the UI 1008 may include a loudspeaker (e.g., a bone conduction speaker or an air conduction speaker) as the interface device 252 to output the user-addressed information 204 via an auditory representation presented by the loudspeaker.

[0069] For example, a perceptible attribute may be a physical quantity perceptible to a user. Examples of perceptible attributes may include visual attributes (attributes visible to a user), audio attributes (e.g., attributes audible to a user), tactile attributes (e.g., Braille), etc. Examples of visual attributes may include graphic positions on the screen of UI 1008, brightness of the screen of UI 1008, contrast of the screen of UI 1008. Examples of audio attributes may include audio volume (also referred to as audio output power or volume level), audio speed, language, etc. For embodiments in which the IM button 206 triggers a change in volume as a modification of the second perceptible attribute, the IM button 206 is also referred to as a volume control button 206.

[0070] It is understood that UI 1008 may not necessarily be configured to provide perceptible output for each interaction mode. In order to implement one or more of such interaction modes, UI 1008 may include (e.g., audio) connection device 254 (e.g., audio transmitter). Connection device 254, when coupled to a user device (e.g., a portable user device), may be configured to implement an interface device. Exemplary embodiments of connection device 254 may include an audio jack, a Bluetooth transceiver, etc. Exemplary embodiments of user devices may include headphones (e.g., wireless headphones and / or wire-based headphones) or bone conduction speakers. For example, headphones may be part of headphones as a user device.

[0071] For example, the connection device 254 can be configured to output an analog signal as a UI output, wherein the physical quantity (e.g., amplitude or electrical power) of the analog signal can represent a modified perceptible attribute (such as a volume level). For example, the connection device 254 can be configured to output a digital signal as a UI output (e.g., according to a network communication protocol), wherein the digital signal includes a data-based representation of a perceptible attribute, such as encoded audio volume data. For example, the data-based representation of a perceptible attribute can indicate a volume level (also referred to herein as audio volume).

[0072] Further exemplary embodiments of the terminal 100 (eg, for providing a session) are described below.

[0073] In an example, the control device 106 may be configured to receive an electrical signal 201a from the product scanning device 102 (if present), the electrical signal 201a representing product information of a product scanned by the product scanning device 102 (also referred to as a scanned product). The control device 106 may be configured to determine purchase information 202a (also referred to as a registered product) based on the product information. For each scanned product, purchase information 202a, ..., 202n may be determined and added to the product list 202.

[0074] The control device 106 may further be configured to determine payment information 204 (as user addressing information) based on the purchase information (e.g., product list 202), for example, taking into account the number of products and / or the amount to be paid for each product. Illustratively, the payment information 204 may represent the total amount to be paid for the products registered by the terminal 100.

[0075] For example, a product may have a product information medium to be scanned by the product scanning device 102, such as a barcode and / or an RFID tag, for example. The product information medium may include product information assigned to the product, for example, by a product database. Examples of product information may represent product identifiers, product types, or product prices. The control device 106 may query the product database based on the product information, and may determine purchase information 202a based on the product database. Illustratively, the product database may include various information about products provided by the market. For each product, an exemplary product database may assign a product identifier to purchase information. The product database may be stored by a storage medium, for example, inside the terminal 100 or outside the terminal 100 (also referred to as database storage).

[0076] The control device 106 may be configured to direct the UI 1008 to output (e.g., display) the payment information 204 as the user addressing information 201d. For example, the graphical UI 1008 may be directed to display the payment information 204. Additionally or alternatively, the control device 106 may be configured to direct the UI 1008 to output the purchase information 202a or the registered product list 202 as the user addressing information.

[0077] In another example, the control device 106 can be configured to perform a financial transaction as part of the session. Examples of financial transactions can include: payment for a registered product (based on the payment information 204), cash withdrawal, cash deposit, fund transfer (e.g., between two accounts). For example, when the terminal 100 is an ATM, the terminal 100 can be configured to implement one or more of the following functions (e.g., operable via a user interface): cash withdrawal, deposit, fund transfer (e.g., between two accounts) and / or account information query; the ATM optionally includes a bank teller safe (also known as a safe).

[0078] In this example, the user addressing information 201d may include information representing a financial transaction and / or account information. Examples of information representing a financial transaction may include: cash value, direction of funds transfer, request for user credential input, request for user account input, etc.

[0079] The user-addressed information 201d may be output by the UI 1008 in accordance with the selected perceptible attribute. Additionally or alternatively, the user may interact with the UI 1008 configured in accordance with the selected perceptible attribute.

[0080] Figure 3 A terminal 100 according to various aspects 300 is schematically illustrated, for example implementing a self-service checkout terminal.

[0081] The terminal 100 may include a body 302, e.g., including a housing, a power plug, a bracket 302s, etc. Certain (e.g., electronic) components of the terminal 100 may be housed by and / or attached to the body 302, e.g., the product scanning device 102 (if present), one or more interface devices of the UI 1008, and / or the IM button 206. For example, the UI 1008 and / or the IM button 206 may be housed by and / or attached to the tower 302t of the body 302.

[0082] UI 1008 may include at least one input device and / or at least one output device. The input device may be configured to receive user input, such as one or more instructions from the user and / or one or more confirmations from the user. The output device may be configured to output information that is perceptible to the user, such as auditorily and / or graphically (i.e., via audio and / or sound).

[0083] For example, UI 1008 may include or be formed by a display device 1008d (e.g., including one or more screens), which implements an output device and optionally implements an input device (e.g., via touch). For example, user interface device 1008 may include a touch screen as an input / output (I / O) device and / or one or more physical keys as an input device and / or a keyboard 1008k as an input device. Alternatively, keyboard 1008k may be implemented by a touch screen of display device 1008d. Alternatively or additionally, UI 1008 may include an audio user interface, for example, implemented by connection device 254.

[0084] UI 1008 may optionally include a financial transaction device 1008t (e.g., in the case of a self-service checkout terminal 100 or a bank terminal), which may be used for one or more financial transactions. For example, financial transaction device 1008t may include a card reader device configured to receive a bank card and read account information from the bank card. Additionally or alternatively, the card reader device may be configured to read bank account information from a mobile device and / or a bank card, for example, via NFC.

[0085] The display device 1008d (e.g., its graphical user interface) can be configured to display information based on the interaction with the user (e.g., self-checkout information and / or financial transaction information). The self-checkout information can include a representation of the payment information, such as a (searchable or editable) virtual bill. The financial transaction information can include a representation of the financial transaction, such as a confirmation.

[0086] For example, the financial transaction device 1008t may include at least one verification device configured to receive verification input associating a bank card with a user. Of course, other forms of payment may be used in addition to or in place of a bank card. Examples of forms of payment may include a debit card, a debit account, a credit card, a credit account, or currency.

[0087] Optionally, for example, the financial transaction device 1008t may include other components that enable financial transactions to be performed, such as a secure data interface for transmitting secure data about the financial transaction. For example, the secure data interface may communicate with a bank server.

[0088] Optionally, the financial transaction device 1008t may further include a printer of the UI 1008 to print a statement including a representation of the financial transaction conducted, such as its details and / or a summary thereof.

[0089] Optionally, the self-service checkout terminal 100 (e.g., in the case of a self-service checkout terminal 100) may include a deposit area 1002. The deposit area 1002 may include a security sensor device 1002s (also referred to as security sensor device 1002s) that is used to monitor the self-service scanning process performed by the user. Illustratively, the security sensor device 1002s is used to detect fraud during the self-service scanning process. For example, the security sensor device 1002s may include a scale (also referred to as a security scale) or another type of sensor.

[0090] Figure 4 A method 400 for operating a self-service checkout terminal 100 according to various aspects is illustrated in a schematic flow chart. For example, the method 400 for operating a self-service checkout terminal can be implemented by the control device 106. Interaction with a user (by exchanging information), such as receiving user input and / or outputting (e.g., displaying) information to a user, as described below, can be performed by the UI 1008, such as one or more graphical output devices 1008d and / or one or more graphical input devices 1008d of the UI 1008.

[0091] Optionally, the method 400 includes executing a self-service session 423, for example, initiated, continued and / or ended in response to user input, for example, at the IM button 206 and / or the UI 1008. Examples of the self-service session 423 may include: a self-service checkout session, a self-scanning process, a self-service banking session (e.g., at an ATM), a self-service retail session, etc. The self-service session 423 may be permanently provided by the self-service terminal 100, for example, via the UI 1008. An exemplary self-service checkout session may include: monitoring if a product is scanned by the scanning device 102. Each time the scanning device 102 scans a product, purchase information 202a of the product is added to the product list based on the sensor data of the product scanning device 102. The exemplary self-service checkout session may further include: receiving an input representing a request to complete the autonomous checkout session (also referred to as an end request). When the end request is received, the payment information 204 may be output, and the user may initiate a financial transaction based on the payment information 204.

[0092] In 401, method 400 may include a mode determination. In an exemplary embodiment thereof, mode determination 401 may be based on mode indicator 451. For example, mode indicator 451 may include a stored indication of an actual interface interaction mode. For example, mode indicator 451 may include a usage state of connection device 254. For example, mode indicator 451 may include a user interaction with self-service terminal 100, for example, indicating a type of user perception that the user wishes to use for interaction with terminal 100.

[0093] In 403, method 400 may include selecting an interface interaction mode (also referred to as mode selection 403) from a plurality of predefined (e.g., stored) interface interaction modes as the actual interface interaction mode. Mode determination 401 may (but need not) include changing the interface interaction mode, for example, by selecting an interface interaction mode that is different from the actual interface interaction mode. Mode determination 401 may (but need not) be based on a mode indicator 451 and / or a result of mode selection 403. In an example, mode selection 403 may be triggered by changing the usage state of a connected device 254 as mode indicator 451. In some embodiments, mode determination 401 and mode selection 403 may be implemented as the same process, for example, automatically outputting the result of mode selection 403 as the result of mode determination 401 (or vice versa) and / or both are based on the same mode indicator 451.

[0094] In an exemplary embodiment, mode determination 401 and / or mode selection 403 may include determining whether connection device 254 (e.g., its audio jack or Bluetooth connection) is in use (indicated by its use state) as a mode indicator 451. When a user device is plugged into an audio jack, when a Bluetooth connection is established between connection device 254 and a user device, and / or when a UI output is provided to connection device 254 (e.g., its audio jack), it may be determined that connection device 254 is in use. Illustratively, the use state may represent an indication of the type of user perception that a user wishes to use for interacting with terminal 100, as mode indicator 451. For example, when a visually impaired person (e.g., a blind user) wishes to use a non-visual interaction mode, the user may connect an audio user device (e.g., a portable user device) to connection device 254 (e.g., its audio jack). In response, UI 1008 may be modified to provide a self-service session 423 via non-visual perception (e.g., via pure audio perception).

[0095] For example, when the usage state of the connection device 254 (e.g., its audio jack) is not being used (also referred to as not being used), the terminal 100 can be in a video interaction mode (in this case, the default interaction mode) or in another default interaction mode by default. Additionally or alternatively, when the usage state of the connection device 254 (e.g., its audio jack) is being used (also referred to as "using"), the terminal 100 can be in a non-video interaction mode (e.g., an audio interaction mode, e.g., a pure audio interaction mode).

[0096] At 411, method 400 may include interface modification in response to user input at IM button 206. Interface modification 411 may include modifying UI 1008 or at least directing modification of UI 1008. The modification of UI 1008 may include modification of one or more perceptible attributes, for example, according to the results of mode determination 401. The perceptible attributes modified by interface modification 411 may change in response to a change in the results of mode determination 401 (see 407).

[0097] When the interface interaction mode is the first interface interaction mode, the interface modification 411 may be of the first type, or when the interface interaction mode is the second interface interaction mode, the interface modification 411 may be of the second type. The first type of interface modification 411 may include (e.g., exclusively) modifying at least one first perceptible (e.g., visible) attribute related to the UI output (e.g., graphic position). The second type of interface modification 411 may include (e.g., exclusively) modifying at least one second perceptible (e.g., audible) attribute related to the UI output (e.g., audio volume).

[0098] According to various aspects, the UI output can include or be user-addressed information. Additionally or alternatively, the user-addressed information can be constant for interface modification 411. For example, the user-addressed information can be output twice (e.g., identically), e.g., before and after interface modification 411. According to various aspects, the UI output can (but need not) be different between the first type of interface modification 411 and the second type of interface modification 411.

[0099] As an example of an implementation of method 400, when connection device 254 is in use, for example, when the connector is plugged into an audio jack and / or when the interface interaction mode is the second interface interaction mode, the user addressing information may include audio-based guidance for the user through the self-service session. The audio-based guidance may be transmitted to the user device by connection device 254, for example, as a (digital or analog) audio signal. In this case, the user input at IM button 206 may cause the audio volume (as a perceptible attribute) of the audio-based guidance to change.

[0100] In this or another implementation example of method 400, when connection device 254 is not in use, for example, when no connector is plugged into the audio jack and / or when the interface interaction mode is the first interface interaction mode, the user addressing information may include video-based guidance of the user through the session. The video-based guidance may be provided to the user by a screen of UI 1008. In this case, user input at IM button 206 may cause the position (as a perceptible attribute) of the video-based guidance on the screen to change.

[0101] To facilitate interface modification 411, method 400 may optionally include selecting a perceptible attribute, for example based on the results of mode determination 401, at 407. Interface modification 411 may then be configured to modify only the selected perceptible attribute (and no other perceptible attributes).

[0102] Figure 5 An interface modification 411 (e.g., its display device 1008d) according to various aspects 500 is schematically illustrated, wherein the interface modification 411 includes rearranging (e.g., repositioning) a graphical user interface 501 (also referred to herein as a graphical interface modification) displayed by one or more touch screens of UI1008 when the interface interaction mode is a video interaction mode.

[0103] The graphical user interface 501 may present one or more graphical input (e.g., control) options (for example, here options 1 to 3) as operating elements, such as soft buttons, etc. Each graphical input option may represent a certain option of operating the terminal 100 (e.g., implementing a dialogue of a self-service session) as user addressing information. The user may interact with the self-service terminal 100 by pressing and / or touching the touch screen at the location of the graphical input option, for example, to select one of the options 1 to 3.

[0104] In an exemplary first scenario, the user's accessibility is highly restricted. For example, the user may be a young person, a person with growth restriction (also known as short stature), or using a wheelchair. In this first scenario, the user may have difficulty reaching the upper area of ​​the touch screen, for example, thereby limiting access to graphical input options at the upper area. However, the user may be able to reach the IM button 206, thereby triggering the interface modification 411.

[0105] As an example, the graphical interface modification can be performed on a client layer (e.g., including one or more clients), a display processing layer, and / or a display driver layer. Additionally or alternatively, the graphical interface modification can be configured to cause a modification of a video signal representing a graphical user interface of UI 1008. The graphical interface modification can be configured to reposition one or more graphical input options, for example, toward a lower area of ​​a touch screen (e.g., without changing the operational function of the graphical input option). This rearrangement can facilitate interaction with the user of the first exemplary scenario and the self-service terminal 100.

[0106] The rearrangement may be configured to change the position coordinates to perceptible properties of one or more graphical input options as an exemplary graphical output (representing user-addressed information) of UI 1008. It will be appreciated that, in addition to or in lieu of the position coordinates, one or more further perceptible properties of the graphical output may be changed via the graphical interface modification, such as, for example, size, shape, text size, contrast, hue, brightness, etc.

[0107] Optionally, input at the IM button 206 can trigger a graphical interface modification, wherein a subsequent input at the IM button 206 can reverse the graphical interface modification. This facilitates operation of the self-service terminal 100.

[0108] Figure 6 Schematically illustrates interface modification 411 according to various aspects 600, similar to aspect 500, except that interface modification 411 includes mirroring graphical output (representing user-addressed information), such as one or more graphical input options of a graphical user interface. Mirroring can include copying (e.g., duplicating) the graphical output (e.g., at least a portion thereof) to another location on the screen (also referred to as a duplicate graphical output). In some embodiments, mirroring includes creating an overlay 611 (also referred to herein as an overlay graphic) of the current graphical user interface, wherein the overlay includes a duplicate graphical output (or another graphical output) of the mirrored graphical user interface.

[0109] Mirroring may be configured to change the position coordinates to perceptible properties of one or more graphical input options as an exemplary graphical output (representing user-addressed information) of UI 1008. It will be appreciated that, in addition to or in lieu of the position coordinates, one or more further perceptible properties of the replicated graphical input options may be changed, such as, for example, size, shape, text size, contrast, hue, brightness, etc. For example, interface modification 411 may be configured to provide enlarged graphical input options that are evenly distributed across the width of display device 1008 d (e.g., across the screen(s) thereof).

[0110] For example, when the terminal 100 is set to the service mode, the parameters of the graphical interface modification, such as the overlay size, the graphical components to be mirrored, the position coordinates of the overlay, etc., may be stored by the terminal 100, for example, which may be programmable.

[0111] Optionally, input at the IM button 206 can trigger a graphical interface modification, wherein a subsequent input at the IM button 206 can reverse the graphical interface modification. This facilitates operation of the self-service terminal 100.

[0112] In an exemplary embodiment of mirroring, the overlay can be created using an API (such as a magnification API). This facilitates implementation, for example, independent of the software and / or hardware architecture of the self-service terminal 100. The magnification API can be applied to screen magnification applications running on Microsoft Windows. The magnification API supports two types of magnifiers, namely a full-screen magnifier and a magnifier control. The full-screen magnifier magnifies the contents of the entire screen, while the magnifier control magnifies the contents of a specific area of ​​the screen and displays the content in a window (e.g., as an overlay). For both magnifiers, both images and text are magnified, and both can control the amount of magnification. The magnification API is started by calling the respective initialization function.

[0113] Figure 7 Schematically illustrates interface modification 411 (e.g., its connected device 254) according to various aspects 700, similar to the above aspects, except that the interface modification includes modification of the audio user interface 701 (also referred to as audio interface modification in this case). As an example, the audio user interface 701 can be a voice user interface.

[0114] The audio user interface 701 can present various audio input options as operating elements (for example, here are options 1 to 3), for example, as a voice input request or another voice output. Each audio input option can represent a certain option of operating the terminal 100 as user addressing information, for example, a dialogue for implementing a self-service session. The user can interact with the self-service terminal 100 by voice, for example, by saying the audio input option (thereby selecting one of the options 1 to 3), but can also interact with the self-service terminal 100 by touch.

[0115] For example, audio user interface 701 can be represented by an audio signal provided by connection device 254, e.g., as an analog audio signal or a digital audio signal. In some embodiments, for example, the audio signal can be provided to a user device (e.g., including a headset) when the user device is coupled to connection device 254. For example, the headset can be part of a headset that is a user device.

[0116] For example, the audio interface modification may change the volume level 701v of the audio signal 701 as a perceptible property. In the case of a digital audio signal 701, the volume level 701v may be encoded in the digital signal. In the case of an analog audio signal 701, the volume level 701v may correspond to an electrical property of the audio signal 701, such as its amplitude.

[0117] In an exemplary embodiment of audio interface modification, the control device 106 can be configured to change (e.g., increase or decrease) the volume level 701v (also referred to herein as volume modification) of the audio signal 701 in response to each user input at the IM button 206. The change (e.g., increase or decrease) of the volume level can be incremental and / or within the range of the minimum level to the maximum level. In an exemplary embodiment of volume modification, when the volume level is at the maximum level, the volume level can be set to the minimum level in response to the user input at the IM button 206 and the volume difference can be increased in other ways. This realizes a rotational volume change. In the example, the audio volume can only be changed between two values. Parameters of audio interface modification, such as minimum level, maximum level and / or volume difference (e.g., positive or negative), etc., can be stored by the terminal 100.

[0118] Figure 8 A method 400 for operating a self-service checkout terminal 100 according to various aspects 800 is illustrated in a schematic flow chart, similar to the above aspects, for using the usage status (eg, coupling status) of a connection device 254 as an exemplary implementation of a mode indicator 451 .

[0119] At 801, method 400 includes selecting and / or determining a non-default interaction mode (e.g., a non-video interaction mode) as the selected interaction mode in response to determining that the connection device 254 is "in use" (e.g., "coupled to a user device"), otherwise selecting and / or determining a default interaction mode (e.g., a video interaction mode) as the selected interaction mode.

[0120] When the selected interaction mode is a non-default interaction mode (e.g., a non-video interaction mode), the method 400 optionally includes the instruction UI 1008 to: deactivate the video output and / or graphical user interface of the user addressing information; and / or activate the audio output (e.g., via the connection device 254) or the voice user interface of the user addressing information. When the selected interaction mode is the default interaction mode (e.g., a video interaction mode), the method 400 optionally includes the instruction UI 1008 to: activate the video output and / or graphical user interface of the user addressing information; and / or deactivate the audio output (e.g., via the connection device 254) or the voice user interface of the user addressing information. This increases security and facilitates the operation of the self-service terminal 100.

[0121] In 803, method 400 includes determining user input at IM button 206 (also referred to herein as IR request determination), and in 411, first interface modification 411 in response to each user input at IM button 206. When it is determined that there is no user input at IM button 206, method 400 may return to 801.

[0122] When the selected interaction mode is a non-default interaction mode (e.g., a non-video interaction mode), the first interface modification 411 includes an audio interface modification. For example, the audio interface modification may include modifying (e.g., changing) the volume level of the audio output of the user-addressed information (e.g., via the connection device 254).

[0123] When the selected interaction mode is the default interaction mode (e.g., video interaction mode), the first interface modification 411 includes a video interface modification. For example, the video interface modification may include modifying (e.g., changing) the position (e.g., on the screen) of the video output of the user-addressed information (also referred to as repositioning). The modification of the position may include mirroring the video output of the user-addressed information, for example, by overlaying.

[0124] Optionally, at 805 , method 400 includes a second interface modification in response to a first interface modification (eg, as a video interface modification), in response to an event (eg, a reversal trigger event), and / or in response to user input at IM button 206 .

[0125] In the first embodiment of the second interface modification, the second interface modification is configured to reverse the video interface modification (also referred to as reverse interface modification in this case). For example, the reverse interface modification can set UI 1008 to the configuration (also referred to as the startup configuration herein) in which the video interface modification is applied.

[0126] In a second embodiment of the second interface modification, the second interface modification is configured to continue the first interface modification (also referred to as continuing the interface modification in this case). For example, the first interface modification and continuing the interface modification can apply iterative changes to UI 1008, for example, towards a target configuration of UI 1008. As an example of continuing the interface modification, a change in position coordinates directed as the first interface modification (e.g., by a number of pixels) can be directed again to continue the interface modification (e.g., by the number of pixels or another number of pixels). As an alternative or additional example of continuing the interface modification, a change in a graphical magnification factor directed as the first interface modification (e.g., by overlay implementation) can be directed again to continue the interface modification (e.g., by the magnification factor or another magnification factor). As a further alternative or additional example of continuing the interface modification, a scrolling down activity directed as the first interface modification (e.g., by a number of lines) can be directed again to continue the interface modification (e.g., by the number of lines or another number of lines). As a further alternative or additional example of continuing with an interface modification, a change in audio volume that was directed as a first interface modification (e.g., by a volume value) can again be directed as continuing with an interface modification (e.g., by that volume value or another volume value).

[0127] For example, when the interface interaction mode of the self-service terminal is the first interface interaction mode or when the interface interaction mode of the self-service terminal is the second interface interaction mode, the first implementation, the second implementation, or the third implementation of the second interface modification can be triggered by user input at the IM button 206. Reversing the interface modification allows the user to react to an unexpected interface modification. Continuing the interface modification allows the user to amplify the changes made by the first interface modification, for example, iteratively or at least stepwise.

[0128] In the first or fourth implementation of the second interface modification, for example, when the user cannot address the user addressing information and / or there is no user input (e.g., at UI 1008 or IM button 206), the second interface modification 805 can be triggered as a reversal trigger event by a timeout. In some alternative or additional embodiments, the second interface modification 805 can be triggered as a reversal trigger event by a user input (e.g., at UI 1008 or IM button 206). For example, the second interface modification 805 can be triggered in response to a user input at UI 1008 and / or in response to a timeout when there is no user input at UI 1008. This allows facilitation of operation, for example, when UI 1008 is reset.

[0129] Further embodiments of the reversal triggering event are described below.

[0130] In a first embodiment, for example, when the interface interaction mode is the first interface interaction mode and / or when the interface interaction mode is the video interface interaction mode, the reversal trigger event may include time sequence information. Examples of time sequence information may include a state of a timer and / or a timestamp of the first interface modification 411. For example, a timer may be initiated in response to an event (also referred to as a timer initiator). Examples of timer initiators may include: user input (e.g., at the IM button 206 and / or at the UI 1008), a first interface modification 411 (e.g., a first type and a second type of interface modification 411). For example, when the decrement timer reaches zero or another value, the video UI output may be set to default.

[0131] In a first embodiment, UI 1008 may optionally output chronological information or another information representing chronological information, such as the remaining time of a timer. For example, UI 1008 may display the status of a decrementing timer and an interface interaction mode. Additionally or alternatively, when a decrementing timer reaches zero or another value (also referred to herein as a timeout), an interface modification 411 may be triggered. In some configurations, the decrementing timer may be reset (to a default value) in response to user input at UI 1008.

[0132] In the first or second embodiment, when the interface interaction mode is the first interface interaction mode and / or when the interface interaction mode is the video interface interaction mode (also referred to as the vision-based interface interaction mode), the reversal trigger event may include a timer starter, such as a user input at UI 1008. For example, in response to the user input at UI 1008, the video UI output may be set to default.

[0133] In the first, second or third embodiment, for example, when the interface interaction mode is the second interface interaction mode and / or when the interface interaction mode is the non-video interface interaction mode, the reversal trigger event may include a change in the usage state of the connection device 254. For example, when the connector is inserted into the audio jack, the video-based UI output may be activated and / or the audio-based UI output may be deactivated.

[0134] Fig. 9 A terminal 100 according to various aspects 900 is schematically illustrated, for example implementing an ATM or another type of banking terminal.

[0135] The terminal 100 may include a body 302, for example, including a housing, a power plug, a bracket 302s, etc. Certain (e.g., electronic) components of the terminal 100 may be accommodated by and / or attached to the body 302, for example, a cash exchange device 902 (if present), one or more interface devices of the UI 1008, and / or an IM button 206. For example, the UI 1008 and / or the IM button 206 may be accommodated by and / or attached to the tower 302t of the body 302. The UI 1008 may include at least one input device and / or at least one output device. The input device may be configured to receive user input, for example, one or more instructions of the user and / or one or more confirmations of the user. The output device may be configured to output information perceptible to the user, for example, audibly and / or graphically (i.e., via audio and / or sound).

[0136] For example, UI 1008 may include a display device 1008d (e.g., including one or more screens) or be formed by a display device 1008d that implements an output device and optionally implements an input device (e.g., via touch). For example, user interface device 1008 may include a touch screen as an input / output (I / O) device and / or one or more physical keys as an input device and / or a keyboard 1008k as an input device. Alternatively, keyboard 1008k may be implemented by a touch screen of display device 1008d. Alternatively or additionally, UI 1008 may include an audio user interface 701, for example, implemented by connection device 254.

[0137] UI 1008 may optionally include a financial transaction device 1008t, which may be used for one or more financial transactions. Financial transactions may include transfers of funds (also referred to as money transfers), for example, as cash to a user (also referred to as a cash withdrawal), as cash from a user (also referred to as a cash deposit), and / or between multiple accounts.

[0138] For example, the financial transaction device 1008t may include a card reader device configured to receive a bank card and read account information (information representing a user's account) from the bank card, such as bank account information (information representing a user's bank account). Additionally or alternatively, the card reader device may be configured to read bank account information wirelessly (e.g., via NFC), such as from a mobile device, a bank card, or from other user devices (e.g., from a mobile wallet of a mobile device).

[0139] The display device 1008t (e.g., a graphical user interface thereof) may be configured to display information representing a financial transaction (also referred to as financial transaction information) performed (e.g., initiated) by a user, for example, money transfer information (information representing a money transfer). The money transfer information may include a representation of a monetary amount transferred from a terminal to a user (e.g., via a cash withdrawal) or from a user to a terminal (e.g., via a cash deposit). The financial transaction information may include a representation of a financial transaction, such as a confirmation, money transfer information, a request to enter user credentials, and / or a request for verification input. The money transfer may include a cash withdrawal from the exchange device 902 and / or a cash deposit at the exchange device 902.

[0140] Generally, the exchange device 902 may be configured to transfer cash between a user and the terminal 100, for example, by conveying cash received from a user into the terminal 100 or conveying a user's cash out of the terminal 100. Exemplary components of the exchange device 902 may include: a cash exchange chamber, a cash exchange slot, a door for opening and closing the chamber, etc.

[0141] For example, the financial transaction device 1008t may include at least one verification device configured to receive verification input associating a bank card with a user. Of course, other cash transfer forms may be used in addition to or in place of a bank card. Examples of cash transfer forms may include a debit card, a debit account, a credit card, a credit account, or cash.

[0142] Optionally, for example, the financial transaction device 1008t may include other components that enable financial transactions, such as a secure data interface for transmitting secure data about financial transactions. For example, the secure data interface may communicate with a bank server or another data storage entity of a financial institution.

[0143] Optionally, the financial transaction device 1008t may optionally include a printer of the UI 1008 to print a statement including a representation of the financial transaction conducted, such as its details and / or a summary thereof.

[0144] The terminal 100 may include a bank teller safe configured to store cash (also referred to as cash storage), which may be received from a user or provided to a user depending on the direction of the money transfer. The bank teller safe may include a cavity for cash storage (also referred to as a cash storage cavity) and a transfer device configured to transfer cash from the exchange device 902 to the cash storage cavity and / or from the cash storage cavity to the exchange device 902. Optionally, the bank teller safe may be configured to store one or more cash cards on the cash storage cavity. The bank teller safe (e.g., its transfer device) may include a communication device (also referred to as a secure communication device) configured to communicate with the control device 106 and / or one or more cash cards. The communication between the secure communication device and the control device 106 and / or one or more cash cards may be protected, for example, by one or more encryption processes.

[0145] The control device 106 may be further configured to exchange money transfer information and / or account information with a bank server or another data storage entity of a financial institution, for example, to allow the financial institution to record money transfers in a user's bank account.

[0146] References made herein to cash may similarly apply to any type of monetary document or monetary value.

[0147] It is understood that the functions of both the self-service checkout terminal and the bank terminal (e.g., ATM) can be configured to perform financial transactions. The self-service checkout terminal can provide the user with purchased items according to the financial transaction. The bank terminal can issue or accept cash according to the financial transaction. However, in some embodiments, the functions of both the self-service checkout terminal and the bank terminal can be implemented by the same architecture of the terminal 100 (e.g., configured to be used for electronic funds transfer at the point of sale) or by different architectures. In some embodiments, the functions of the financial transaction can be implemented by XFS (Financial Services Extension). XFS (e.g., configured as middleware software) provides a client-server architecture for financial applications on the Microsoft Windows platform, for example, running on a terminal 100 configured to be used for electronic funds transfer at the point of sale and / or configured as an ATM.

[0148] A working example is explained below. A computer program (e.g., including several small executable files) implementing the interface modifications described herein is added to the software of the terminal 100 that executes the computer program. When the volume control button 206 (of the terminal 100) for the headset is pressed without inserting the headset, the computer program guides the creation of an overlay (also referred to as an overlay screen) on the display, for example, set as a foreground graphic. The overlay mirrors the actual application displayed at the display, but moves it to the bottom of the display of the touch screen (basically sliding from the top of the screen to the bottom of the screen). The actual application displayed at the display may include a conversation representing a financial transaction. Virtual buttons (e.g., of the conversation) implemented by the touch screen near the top of the touch screen are mirrored to the lower half of the touch screen through the overlay, making the virtual buttons easier to access. The original displayed content of the application (e.g., the conversation representing the financial transaction) still exists, but in the background of the overlay and may be grayed out. For example, the original displayed content is still visible, but is obscured. When the user touches the virtual button of the overlay (e.g., the "cash withdrawal" button), both the background of the overlay and the overlay can display a repeated or visible response to the touch at the virtual button of the overlay. The overlay (e.g., providing a mirror screen) can transpose the virtual button pressed by itself to the correct position on the transaction screen in the background. For example, the actual application displayed at the display is bypassed (e.g., unaffected) by the overlay creation. When the user touches the original virtual button, the actual application can make the same response to the situation without the overlay, and when the user touches the copy of the original virtual button provided by the overlay, the same response can be made to the situation with the overlay. Once the overlay is created, the overlay can last for a predetermined period of time (e.g., 5 seconds). After a predetermined period of time (e.g., after 5 seconds) (see timeout), the overlay may disappear (see reversal interface modification), and the actual application displayed on the display before the overlay was created is displayed in the foreground again. Additionally or alternatively, the user can press the volume control button again to remove the overlay. In this case, the volume control button 206 acts as a toggle key that makes the overlay appear (also referred to as activating the overlay) or disappear (also referred to as deactivating the overlay), see, for example, the above-mentioned double modification toggle key. On Vista operating systems, when headphones are plugged in, volume control button 206 may trigger an increase in audio volume and activation / deactivation of the overlay.

[0149] In the following, various examples are provided with reference to the above aspects.

[0150] Example 1 is a terminal (e.g., a self-service terminal), comprising: a user interface for providing information to a user of the terminal; an interface modification (e.g., reconfiguration) button; and a control device, which is configured to: determine whether the interface interaction mode of the terminal is a first interface interaction mode (e.g., a default mode) or a second interface interaction mode; in response to user input at the interface modification button, when the interface interaction mode is the first interface interaction mode, a guided modification (e.g., reconfiguration) is assigned to a first perceptible attribute of the information, and when the interface interaction mode is the second interface interaction mode, a guided modification (e.g., reconfiguration) is assigned to a second perceptible attribute of the information.

[0151] Example 2 is a terminal comprising: a first (e.g., video) user interface device (e.g., perceptible by a first sensory sense); a second (e.g., audio) user interface (e.g., providing an audio signal) component; a control device configured to: determine whether the interface interaction mode of the terminal is a first interface interaction mode or a second interface interaction mode (e.g., based on a usage state of the second user interface); in response to user input at an interface modification button, guide modification of the first user interface when the interface interaction mode is the first interface interaction mode (e.g., as a case where the usage state of the second user interface is not being used), and guide modification of the second user interface when the interface interaction mode is the second interface interaction mode (e.g., as a case where the usage state of the second user interface is being used).

[0152] Example 3 is a terminal, comprising: a user interface for providing information (e.g., a request) to a user of the terminal; an interface modification button; a control device configured to: determine whether the interface interaction mode of the terminal is a first interface interaction mode or a second interface interaction mode; and in response to user input at the interface modification button, change: a first parameter of a first perceptible attribute of information that controls the user interface when the interface interaction mode is the first interface interaction mode (e.g., as a function of the first parameter), and a second parameter of a second perceptible attribute of information that controls the user interface when the interface interaction mode is the first interface interaction mode (e.g., as a function of the second parameter).

[0153] Example 4 is a method, for example, performed by a control device of one of Examples 1 to 3, the method comprising: providing information to a user of a terminal through a user interface of the terminal; determining whether an interface interaction mode of the terminal is a first interface interaction mode or a second interface interaction mode; in response to user input at an interface modification button of the terminal, when the interface interaction mode is the first interface interaction mode, guiding modification of a first perceptible attribute assigned to the information, and when the interface interaction mode is the second interface interaction mode, guiding modification of a second perceptible attribute assigned to the information.

[0154] Example 5 is a (eg, non-transitory) computer-readable medium comprising instructions (eg, code segments representing instructions) that, when executed by one or more processors, cause the processors to perform the method of Example 4.

[0155] Example 6 is a computer program comprising instructions (eg, code segments representing instructions) that, when executed by one or more processors, cause the processors to perform the method of Example 4.

[0156] Example 7 is a control device comprising one or more processors configured to execute the method of Example 4, and the control device is optionally further configured according to the control device of one of Examples 1 to 3.

[0157] In an exemplary configuration, when the interface interaction mode is a first interface interaction mode, user input at an interface modification button can cause (e.g., trigger, induce, guide) a quantitative change in a first perceptible attribute, and when the interface interaction mode is a second interface interaction mode, user input at an interface modification button can cause (e.g., trigger, induce, guide) a quantitative change in a second perceptible attribute.

[0158] The quantitative change of the first perceptible attribute may include a quantitative change of a first parameter that controls the first perceptible attribute. Illustratively, the user input at the interface modification button may cause the first parameter (e.g., spatial coordinates, brightness, contrast, etc.) to change quantitatively from the value that the first parameter had before the user input at the interface modification button (and before modification) to a different value (illustratively, after the guided modification, e.g., in response to the user input at the interface modification button). The quantitative change of the first parameter may correspond to a corresponding change in the first perceptible attribute. As a numerical example, the value of the modified first parameter may differ from the value of the first parameter before modification by at least 10%, e.g., by at least 20% or by at least 50%.

[0159] In a corresponding manner, the quantitative change of the second perceptible attribute may include a quantitative change of a second parameter that controls the second perceptible attribute. Illustratively, the user input at the interface modification button can cause the second parameter (e.g., audio volume) to change to a different value from the value that the second parameter had before the user input at the interface modification button. The quantitative change of the second parameter can correspond to a corresponding change in the second perceptible attribute. As a numerical example, the value of the modified second parameter can differ from the value of the second parameter before the modification by at least 10%, such as at least 20% or at least 50%.

[0160] Example 8 is one of Examples 1 to 7, wherein the user interface of the terminal includes a first user interface device (for example, configured to output information when the interface interaction mode of the terminal is a first interface interaction mode) and / or a second user interface device (for example, configured to output information when the interface interaction mode is a second interface interaction mode).

[0161] Example 9 is one of Examples 1 to 8, wherein the interface modification button is a physical button and / or can be reached by a seated person and / or is set at a place less than 122 cm from the ground. This facilitates implementation, for example, when the physical button is already pre-installed in the terminal.

[0162] Example 10 is one of Examples 1 to 9, wherein the interface modification button is an audio control button or a button of a pin pad or keyboard of a UI. This facilitates implementation, for example, when the terminal lacks another suitable pre-installed button.

[0163] Example 11 is one of Examples 1 to 10, wherein the interface modification button is implemented as a virtual button (e.g., via a screen of the UI) and / or is reachable by a seated person and / or is set at a height less than 122 cm from the ground. This facilitates implementation, for example, when the terminal lacks appropriate physical pre-installed buttons.

[0164] Example 12 is one of Examples 1 to 11, wherein the interface modification button is disposed below the screen of the user interface (eg, below the screen) and / or below the first user interface device.

[0165] Example 13 is one of Examples 1 to 12, wherein the first perceptual attribute is perceptible by a first perceptual (human) sense, and the second perceptual attribute is perceptible by a second perceptual (human) sense (e.g., different from the first perceptual (human) sense).

[0166] Example 14 is one of Examples 1 to 13, wherein the first interface interaction mode is a default mode and / or a video interaction mode (eg, a vision-based interaction mode).

[0167] Example 15 is one of Examples 1 to 14, wherein the second interface interaction mode is a non-default mode and / or a non-video interaction mode (e.g., a non-visual-based interaction mode), for example, an audio interaction mode (e.g., a voice interaction mode), for example, a pure audio interaction mode.

[0168] Example 16 is one of Examples 1 to 15, wherein the second perceptible attribute is different from the first perceptible attribute and / or includes (for example, is) information about audio volume and / or information provided by an audio user interaction device (also referred to as an audio device) of the UI (for example, via its audio jack) (for example, when the information is provided by an audio user interaction device (also referred to as an audio device) of the UI (for example, via its audio jack), wherein preferably, when the interface interaction mode of the terminal is the second interface interaction mode, the information is provided by the audio user interaction device.

[0169] Example 17 is one of Examples 1 to 16, wherein the first perceptible attribute includes the graphic position and / or graphic geometry (e.g., size and / or shape) of the information and / or the information is provided (e.g., presented, e.g., displayed) by a video user interaction device (also referred to as a video device) of the UI (e.g., by one or more display devices thereof) (e.g., when the information is provided (e.g., presented, e.g., displayed) by a video user interaction device (also referred to as a video device) of the UI (e.g., by one or more display devices thereof), wherein preferably, when the interface interaction mode of the terminal is the first interface interaction mode, the information is provided by the video user interaction device.

[0170] Example 18 is one of Examples 1 to 17, wherein the terminal is a self-service terminal, such as an ATM, a self-checkout terminal, or a vending machine.

[0171] Example 19 is one of Examples 1 to 18, wherein when the interface interaction mode is the first interface interaction mode, the modification includes modification of a first parameter that controls (eg, affects) the first perceptible property.

[0172] Example 20 is one of Examples 1 to 19, wherein when the interface interaction mode is the second interface interaction mode, the modification includes modification of a second parameter that controls (eg, affects) the second perceptible attribute.

[0173] Example 21 is one of Examples 1 to 20, wherein the information is unchanged with respect to the modification (eg, of the first perceptible attribute and / or the second perceptible attribute).

[0174] Example 22 is one of Examples 1 to 21, wherein the modification of the first perceptible attribute is based on stored parameters, which are optionally programmable (for example, in a service mode of the terminal), wherein, preferably, the modification of the first perceptible attribute changes the value of the first perceptible attribute (for example, location coordinates) to the stored parameters.

[0175] Example 23 is one of Examples 1 to 22, wherein when the interface interaction mode is a first interface interaction mode, information is output (e.g., presented) by a first user interface device of the user interface; and / or wherein when the interface interaction mode is a second interface interaction mode, information is output (e.g., presented) by a second user interface device of the user interface; wherein, preferably, the first user interface device is deployed to be higher than the second user interface device (e.g., on the ground) or at least away from the second user interface device.

[0176] Example 24 is one of Examples 1 to 23, wherein the information includes (or is) an input request and / or is sent to a user.

[0177] Example 25 is one of Examples 1 to 24, wherein the information includes (or is) options (also referred to as operation options) for operating (eg, controlling) a terminal, such as input options.

[0178] Example 26 is one of Examples 1 to 25, wherein the user interface is accessible (eg, at least partially perceptible) by a user of the terminal.

[0179] Example 27 is one of Examples 1 to 26, wherein the second user interface device is a physical interface and / or is reachable by a seated person and / or is disposed less than 122 centimeters from the ground.

[0180] Example 28 is one of Examples 1 to 27, wherein the first user interface device and the second user interface device differ from each other in: spatial location (e.g., by rearranging (e.g., repositioning) information), and the type of perception of the user of the terminal through which the respective user interfaces are accessible.

[0181] Example 29 is one of Examples 1 to 28, wherein the first perceptible attribute and the second perceptible attribute are different from each other, for example, in terms of the perceptual senses through which they are perceptible.

[0182] Example 30 is one of Examples 1 to 29, wherein the first perceptible attribute is a video attribute of the information (e.g., graphics and / or spatial location); and / or wherein the first (e.g., video) user interface device is a video (e.g., graphical) user interface device (e.g., comprising one or more screens, such as a touch screen).

[0183] Example 31 is one of Examples 1 to 30, wherein the modification of the first perceptible attribute is directed to an application programming interface (API) of an operating system executed by a terminal and / or an operating system of an application running output information. The application programming interface facilitates implementation and may be an amplification API, which facilitates implementation even more.

[0184] Example 32 is one of Examples 1 to 31, wherein the modification of the first perceptible attribute includes rearranging (e.g., repositioning) a graphical output (e.g., representing information), for example, a graphical output including one or more graphical (e.g., input) operating elements (e.g., each of which represents an operating option) (e.g., a soft key).

[0185] Example 33 is one of Examples 1 to 32, wherein the modification includes a first (e.g., graphical interface) modification of the user interface in response to user input at an interface modification button, and preferably, the modification includes reversing the first modification of the user interface in response to further (e.g., subsequent) user input at the interface modification button.

[0186] Example 34 is one of Examples 1 to 33, wherein the modification of the first perceptible attribute includes a graphical output (e.g., representing information) of a mirrored (e.g., graphical) user interface (e.g., at least one operating element of the graphical output), for example, a graphical output including one or more graphical (e.g., input) operating elements (e.g., each of which represents an operating option) (e.g., a soft key).

[0187] Example 35 is Example 34, wherein mirroring the graphical output comprises overlaying the graphical output with a (e.g., resized and / or rearranged, e.g., repositioned) copy of (e.g., at least a portion of) the graphical output (e.g., its operating elements (e.g., soft keys)).

[0188] Example 36 is one of Examples 1 to 35, wherein the second perceptible attribute is an audio attribute of the information (e.g., audio volume); and / or wherein the first (e.g., audio) user interface device is an audio user interface device (e.g., including a connected device).

[0189] Example 37 is one of Examples 1 to 36, wherein the information is related to a self-service session provided by the terminal (also referred to herein as self-service related information), or is related to at least an addressed user (also referred to herein as user addressing information).

[0190] Example 38 is one of Examples 1 to 37, wherein the information is related to an output of an application executed by the terminal.

[0191] Example 39 is one of Examples 1 to 38, wherein the terminal (e.g., its second user interface device) further includes a (e.g., audio) connection device (e.g., an audio jack), wherein, preferably, the determination of whether the interface interaction mode of the terminal is the first interface interaction mode or the second interface interaction mode is based on the usage status of the connection device (e.g., the connection status).

[0192] Example 40 is Example 39, wherein when (e.g., in response to) the connected device (e.g., wired or wirelessly) is coupled to another (e.g., portable) connected device (e.g., as a user device) and / or use of the connected device is initiated by a user, the second interface interaction mode is determined as the interface interaction mode, and preferably, otherwise the first interface interaction mode is determined as the interface interaction mode.

[0193] Example 41 is Example 39 or Example 40, wherein the first interface interaction mode is determined as the interface interaction mode when (e.g., in response to) the connected device is decoupled from another (e.g., portable) connected device (e.g., as a user device) and / or use of the connected device is ended by the user (e.g., indicated by decoupling the other connected device).

[0194] Example 42 is one of Examples 39 to 41, wherein the user interface is configured to implement an audio user interface, such as a voice-based user interface, through a connected device.

[0195] Example 43 is one of Examples 39 to 42, wherein when the connection devices are coupled to each other (eg, wired or wirelessly), the connection device is configured to exchange audio signals with another connection device.

[0196] Example 44 is one of Examples 1 to 43, which further includes (for example, the control device is configured to): in response to the end of use of the connection device, for example, indicated by another (for example, portable) connection device (for example, as a user device) being decoupled (for example, disconnected) from the terminal (for example, its connection device), determining the first interface interaction mode as the interface interaction mode.

[0197] Example 45 is one of Examples 1 to 44, which further includes (for example, the control device is configured to): changing the interface interaction mode (for example, changing to a second interface interaction mode), which interface interaction mode preferably includes activating an audio user interface device of the user interface and / or deactivating a video (for example, graphical) user interface device of the user interface.

[0198] Example 46 is one of Examples 1 to 45, wherein the first perceptible attribute includes one or more of: graphic contrast, graphic brightness, graphic position (e.g., height), graphic geometry (e.g., size and / or shape), font type, wherein, preferably, modification of the first perceptible attribute does not require graphic compression.

[0199] Example 47 is one of Examples 1 to 46, wherein the modification of the first perceptible property is implemented by one or more of (e.g., processing information, e.g., a data representation thereof): a graphics amplifier (e.g., an upscaling API), firmware (e.g., a display device) of a user interface (e.g., presenting information), or a separate application that converts graphical output of a user interface (e.g., soft keys); and / or a device (e.g., a graphics card) driver.

[0200] Example 48 is one of Examples 1 to 47, wherein the information represents a request to a user, such as input of user credentials, user authorization, and / or user authentication.

[0201] Example 49 is one of Examples 1 to 48, wherein the modification of the first perceptible attribute is independent of an application layer providing the information (eg, performed by a terminal).

[0202] Example 50 is one of Examples 1 to 49, which further includes (e.g., the control device is configured to): execute (e.g., initiate, conduct, or end) a financial transaction based on input at a user interface, wherein, preferably, the financial transaction may include a request to a user represented by information.

[0203] Example 51 is one of Examples 1 to 50, wherein the terminal further includes a product scanning device configured to scan a product identifier of a product presented to a product sensing device (wherein the information may optionally represent a user's request to scan the product identifier); wherein the terminal (e.g., its control device) is configured to further initiate a financial transaction based on the product identifier.

[0204] Example 52 is one of Examples 1 to 51, which further includes (for example, the control device is configured to): generating a message according to a network communication protocol, the message (for example, sent to a financial institution server) including a request to verify input of user credentials at a user interface (for example, through an information request); and further initiating a financial transaction based on a response to the message.

[0205] Example 53 is one of Examples 1 to 52, wherein the terminal further comprises: a bank teller safe, wherein the financial transaction is configured to transfer one or more currency documents to or from the bank teller safe.

[0206] Example 54 is one of Examples 1 to 53, wherein the terminal further includes: a network transceiver, wherein the control device is configured to request and / or update (e.g., according to a network protocol) one or more parameters of modification (e.g., of the first perceptible attribute and / or the second perceptible attribute).

[0207] Example 55 is one of Examples 1 to 54, wherein the terminal further comprises: a memory storing one or more parameters of the modification (eg, of the first perceptible attribute and / or the second perceptible attribute).

[0208] Example 56 is one of Examples 1 to 55, which further includes (for example, the control device is configured to): reversing the modification of the first perceptible attribute (preferably when the interface interaction mode is the first interface interaction mode) in response to one or more of the following instructions: user (e.g., touch) input at the user interface; a timestamp of the modification of the first perceptible attribute that satisfies predefined (e.g., stored) criteria; further user input at an interface modification button (e.g., implementing a double modification toggle key), wherein the criteria are optionally satisfied when the temporal difference with the timestamp exceeds a predefined (e.g., stored) value.

[0209] Example 57 is Example 56, further comprising (eg, the control device is configured to): outputting time sequence information (eg, a timer counter) via the user interface based on a timestamp of the modification of the user interface.

[0210] Example 58 is one of Examples 1 to 57, wherein another connected device (e.g., as a user device) is configured to convert the (e.g., electrical) output of the user interface into an output that is user-perceptible and / or includes information (e.g., having a second perceptible attribute).

[0211] Example 59 is one of Examples 1 to 58, wherein the additional connection device includes a microphone (also referred to as a speaker).

[0212] Although the present disclosure has been particularly shown and described with reference to certain aspects, it will be understood by those skilled in the art that various changes may be made in form or detail herein without departing from the spirit and scope of the present disclosure as defined by the appended claims. Therefore, the scope of the present disclosure is indicated by the appended claims, and therefore, it is intended to include all changes within the meaning and scope of the equivalents of the claims.

Claims

1. A self-service terminal (100), comprising: a user interface (1008) for providing information to a user of the self-service terminal (100); Interface modification button (206); A control device (106) configured to: Determining whether the interface interaction mode of the self-service terminal (100) is the first interface interaction mode or the second interface interaction mode; In response to user input at the interface modification button (206), direct the following modifications: when the interface interaction mode is the first interface interaction mode, a first perceptible attribute assigned to the information, and When the interface interaction mode is the second interface interaction mode, a second perceptible attribute assigned to the information.

2. The self-service terminal (100) according to claim 1, wherein the first perceptible attribute and the second perceptible attribute are different from each other in terms of the sensory senses through which they are perceptible.

3. The self-service terminal (100) according to claim 1, wherein the first perceptible attribute is a video attribute, preferably a graphic position.

4. The self-service terminal (100) according to claim 1, wherein the control device is configured to direct the modification of the first perceptible attribute to an application programming interface (API) of the self-service terminal.

5. The self-service terminal (100) of claim 1, wherein the modification of the first perceptible attribute comprises mirroring at least one operating element of a graphical output of the user interface (1008), the at least one operating element representing the information, in, Preferably, mirroring comprises overlaying the graphical output with a rearranged copy of the at least one operating element.

6. The self-service terminal (100) according to claim 1, which is configured as an automatic teller machine (ATM).

7. The self-service terminal (100) according to claim 1, wherein the second perceptible attribute is an audio attribute, preferably an audio volume.

8. The self-service terminal (100) according to claim 1, further comprising a connection device (254), wherein the control device (106) is configured to determine the second interface interaction mode as the interface interaction mode in response to the connection device (254) being used by the user, and preferably, otherwise determine the first interface interaction mode as the interface interaction mode; ·in, Preferably, the user interface (1008) is configured to implement an audio user interface via the connection device (254).

9. The self-service terminal (100) according to claim 8, wherein when the connection device (254) and another connection device are coupled to each other, the connection device (254) is configured to exchange audio signals with the other connection device; and / or The control device (106) is further configured to determine the first interface interaction mode as the interface interaction mode in response to the end of the use of the connection device (254).

10. The self-service terminal (100) of claim 1, wherein the control device (106) is further configured to initiate a financial transaction based on input at the user interface (1008), the financial transaction being through the information request.

11. The self-service terminal (100) according to claim 1, wherein preferably when the interface interaction mode is the first interface interaction mode, the control device (106) is further configured to direct the reversal of the modification of the first perceptible attribute in response to: User touch input at the user interface (1008); When a timestamp of said modification of said first perceptible attribute satisfies a predefined criterion; • In response to further user input at the interface modification button (206).

12. The self-service terminal (100) according to claim 1, Wherein, when the interface interaction mode is the first interface interaction mode, the modification includes modifying a first parameter that controls the first perceptible attribute.

13. The self-service terminal (100) according to claim 1, Wherein, when the interface interaction mode is the second interface interaction mode, the modification includes modifying a second parameter that controls the second perceptible attribute.

14. The self-service terminal (100) according to claim 12 or claim 13, wherein said modification of said first parameter induces a change from a value of said first perceptible attribute prior to said user input at said interface modification button (206) to a different value of said first perceptible attribute; and / or wherein the modification of the second parameter induces a change from a value of the second perceptible attribute prior to the user input at the interface modification button (206) to a different value of the second perceptible attribute.

15. The self-service terminal (100) according to claim 1, Wherein, the information remains unchanged for the modification of the first perceptible attribute and / or the second perceptible attribute.

16. The self-service terminal (100) according to claim 1, wherein said modification of said first perceptible attribute is based on stored parameters, and in, The modification of the first perceptible property changes the value of the first perceptible property to the stored parameter.

17. A method comprising: providing information to a user of the self-service terminal (100) via a user interface (1008) of the self-service terminal (100); Determining whether the interface interaction mode of the self-service terminal (100) is the first interface interaction mode or the second interface interaction mode; In response to user input at the interface modification button (206) of the self-service terminal (100), the following modifications are directed: when the interface interaction mode is the first interface interaction mode, a first perceptible attribute assigned to the information, and When the interface interaction mode is the second interface interaction mode, a second perceptible attribute assigned to the information.

18. A computer readable medium comprising instructions which, when executed by one or more processors, cause the processors to perform the method of claim 17.

19. A control device comprising one or more processors configured to perform the method according to claim 17.

20. A computer program comprising instructions which, when executed by one or more processors, cause the processors to perform the method according to claim 17.

Images