Patent ID: 12230110

DETAILED DESCRIPTION

In the following description of the various embodiments to accomplish the foregoing, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration, various embodiments in which the disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made.

FIG.1illustrates a functional block diagram for remote processing, central processing, and distributed networking in which certain aspects of the present disclosure may be implemented. Remote processing100functions may be performed on ultra-wideband (UWB) enabled wireless portable electronic device(s)114that can provide haptic feedback. Suitable UWB-enabled portable devices may include a smartphone114-1, a smart watch114-2, smart glasses114-3, tablet devices114-4, and/or any other UWB-enabled portable or wearable device. Alternatively, certain remote processing functions may also be handled directly and/or indirectly on alternative devices113such as computer registration machine(s)113-1and/or voice-enabled smart device(s)113-2.

The remote processing100modules, routines, components, and/or functions may reside in non-volatile local memory in one or more sectors of memory, data stores, and/or data structures in the memory. Such exemplary remote-processing modules include user registration module(s)102that can be used to register a user and/or an account with a banking or other institution to enable UWB pre-staged transaction entering, processing, and haptic feedback reminding. Hardware device registration module(s)104can be used to identify unique hardware information and associate that information with a user and/or user account(s) so that the banking or other institution knows which devices are owned by which users. Sample hardware device information can include device make/model names with serial numbers, MAC address(es), Bluetooth address(es), IMEI numbers, ICCID numbers, SEID identifiers, and/or any other identifier that may be unique for the hardware device.

Remote processing100may also include pre-stage transaction processing module(s)106to enable user(s) to remotely pre-stage transactions such as withdrawals, transfers, deposits, wires, inquiries, reports, payments, and/or any other type of banking transaction. These types of pre-stage transactions can be communicated from remote devices114to central processing such as, for example, ATM server(s) by communication module(s)108. Public and private encryption keys may be generated remotely and/or centrally and shared between the portable devices114, central processing115, and eventually with one or more ATM machine(s)134-1,134-2,134-3,134-4, . . .134-N (generically referenced herein as134) in an ATM network132. Some and/or all of the remote processing functionality may be implemented in whole or in part through the use of an app residing on or otherwise accessible from the portable device114. Alternatively, some or all of the remote processing functionality may also be implemented in whole or in part on the alternate remote processing devices113that may, for example, use an Internet interface to register device(s)114, setup users, setup accounts, pre-stage transactions that can be communicated to the devices114, etc.

Central processing115in one or more aspects of the disclosure can be implemented on ATM server(s), with central processing hardware, and/or central processing components115-1. One or more centralized and/or distributed memories, storage device(s), and/or databases115-2in communication therewith may be used to store relevant modules, jobs, routines, data, and/or computer-executable instructions for implementing various server aspects of this disclosure.

Such central processing115functionality may include user registration/validation module(s)116, which are used to enroll users in the UWB and haptic feedback functionality for pre-staged transactions. Hardware device registration/validation modules118may be used to correlate the user's UWB-enabled wireless portable electronic devices with the user and/or user account.

Pre-staged transaction processing module(s)120may communicate with devices114or113through communication module(s)108,126and app112or other interface functionality in order to schedule and initiate transactions to be pre-staged. Initiation, authentication, validation, handling, and/or processing of pre-staged transactions may be performed as part of a recurring job, a batch process, and/or on-demand fetching in module(s)112. Central processing115may also generate, share, and/or disseminate public and private encryption keys in module(s)124in order to facilitate secure communications between UWB-enabled wireless portable electronic devices(s) with haptic feedback114and one or more UWB-enabled ATMs134-1,134-2,134-3,134-4. . .134-N in an UWB ATM network132. Database management module(s)128may be used to store and/or access any information or data used, generated, and/or disseminated by central processing115. Central processing may also perform queue management and calculations regarding preferred ATMs in module130as described in more detailed below in reference toFIG.6.

FIG.2Aillustrates hardware and software components for exemplary ATM(s)134incorporating UWB functionality for use with UWB-enabled wireless user portable electronic devices114that can provide haptic feedback in which certain aspects of the present disclosure may be implemented. Various ATM machine modules202-216for implementing functionality on the ATM, communicating with ATM server(s), handling pre-staged transactions, and interacting with users and user devices114may be stored in one or more sectors of integrated and/or accessible non-volatile memory, memories, data stores, databases or the like200.

As an example, an ATM machine134will utilize user authentication and/or hardware validation module(s)202in order to authorize users to use the ATM and to proceed with pre-staged transaction(s) on validated and/or registered devices114. Pre-staged transaction(s) received from the ATM server(s)115-1or central processing115may be stored in memory and/or processed in module204. Network communication module(s)206may facilitate communications between ATM machine(s)134and ATM server(s)/central processing115via network communication interface(s)224in the ATM134. User information, hardware information, encryption keys, session information, queue information, ATM information, etc. may be communicated via module(s)206and interface(s)224.

Public and private encryption keys received from and/or distributed by central processing115can be stored in module208and used to enable establishment and securing of communications between ATM machine(s)134and UWB-enabled devices114.

One or more modules210may be used to provide detection, location determination, and/or facilitate communication with UWB-enabled devices114via UWB hardware interfaces in the ATM machine134. Such detection of UWB devices114may occur if and/or when the device114comes within UWB range of ATM machine134which, based on current UWB implementations, enable detection and communication within distances of approximately 500-800 meters or less. However, any UWB range is considered to be within the spirit and scope of the present invention.

Input/output (I/O) and/or wireless communication module(s)212in memory200may be used to accept ATM inputs via optical scanner226, touchscreen display228, keypad232, and/or voice recognition microphone236. Messages may be communicated to users via display228or speaker234and/or wirelessly to device114. ATM134may also include session management214and/or queue management216modules to perform the functionality described infra locally and/or to communicate with central processing115for remote functionality performance at ATM server(s)115-1or the like.

In particular, notifications of pre-staged transaction(s) can be communicated via UWB from UWB-enabled ATM134to a UWB-enabled device114in order to trigger haptic-feedback reminders to perform the transactions when the device114is within range of the ATM134.

Relatedly,FIG.2Billustrates hardware and software components for exemplary central processing facilities115such as ATM server(s)115-1utilized with UWB-enabled ATM(s)134and UWB-enabled wireless user portable electronic devices114that can provide haptic feedback in which certain aspects of the present disclosure may be implemented.

The central processing functionality115as implemented in ATM server(s)115-1and memories, storage device(s), and/or databases115-2as referenced inFIG.2Bhave been described above in the discussion ofFIG.1with respect to user registration/validation module(s)116, hardware device registration/validation module(s)118, pre-stage transaction processing module(s)120, recurring job/on-demand fetch processing module(s)122, public/private key encryption module(s)124, remote processing/ATM communication module(s)126, database management module(s)128, and queue management/preferred ATM calculation and/or recommendation module(s).

The foregoing central processing functionality may be implemented using one or more local and/or distributed processor(s)250, network communication interface(s)252, and I/O devices and interfaces254, and/or any other commercially available server hardware.

FIG.3illustrates hardware and software components for exemplary UWB-enabled wireless user portable electronic devices114that can provide haptic feedback in which certain aspects of the present disclosure may be implemented. As noted above, UWB-enabled portable devices may include one or more of a smart phone114-1, a smart watch114-2, smart glasses114-3, tablet devices114-4, and/or any other UWB-enabled portable or wearable device.

In addition to the remote processing100functionality and/or module(s)102-114discussed with respect toFIG.1, a UWB-enabled device114may include local non-volatile memory or memories300and hardware relevant to the particular type of device114-1,114-2,114-3,114-4, or the like.

User authentication module(s)302can be used by the device114in communication with the ATM134in order to authenticate the user in order to establish a session, recognize a device114corresponding to a user who has valid pre-schedule transaction(s) pending, and trigger a haptic feedback on the device114. App module(s)304, executed on processor(s)328, can be used to facilitate session handling and/or execution of pre-staged and/or other transactions as well as to provide haptic feedback via haptic feedback module(s)320and haptic feedback mechanism(s)326. Similarly, processor(s)328may execute instructions to perform the functionality of any of the module(s) stored in memory300.

Pre-stage transaction processing/storage module(s)306on device114can be used to set up a transaction, store a previously set up transaction, and/or locally handle a transaction at the ATM134. Wireless/network communication module(s)308can provide non-UWB wireless local communication between the device134and the ATM134or remote communication with central processing115such as ATM server(s)115-1via network communication interface(s)330. Such non-UWB wireless communication may be via Bluetooth, Wi-Fi, NFC, or the like. UWB functionality module(s)312may also provide wireless communication between the device134and the ATM134or remote communication with central processing115such as ATM server(s)115-1via UWB hardware interface(s)324. Alternatively, a combination of UWB and non-UWB functionality may be used to provide the functionality described herein.

Local public/private key encryption module(s)310may store key(s) received from ATM server(s)115-1and/or generate keys that are communicated to ATM server(s)115-1and thereafter distributed to ATMs134. Either way, the public and private encryption keys stored in module(s)310are used to establish and facilitate secure communications between the UWB-enabled ATM134and the UWB-enabled device114via interfaces324and/or330.

Session management module(s)316may enable the local device114to manage ATM sessions, may facilitate management by ATM134, and/or may facilitate management by central processing115. User preference/ATM selection module(s)318enable users to enter criteria regarding desired ATMs in the ATM network132, view information regarding ATMs in the network, and/or to make ATM selections.

Input to device114and/or output displays to provide information to the user may be accomplished through a touchscreen or non-touchscreen display332, an optical scanner334such as for facial recognition or barcode or QR code scanning, a fingerprint scanner336, and/or user interface/keypad338. A speaker340may be included in device114to provide audible information and/or feedback to the user. If desired, the haptic feedback conveyed herein may provided audibly. A voice-recognition microphone342may also be included in114to enable voice commands or dictation in order to obviate, in whole or in part, manual key entries or manual interactions with device114.

FIG.4is an illustrative flowchart of a method performed in accordance with one or more registration and/or validation implementations for users, setup of user account(s), and association of UWB-enabled wireless user portable electronic device(s) and corresponding hardware identifier(s) with the foregoing.

In step400, a user may login and a handshake process may be implemented and the user may be validated. This may occur between remote processing100and central processing115. In step402, the user and the user's devices may be registered and the same may be stored in central processing115such as memory devices115-2. This enables the ATM server(s)115-1and ultimately the ATM machine(s)134to recognize which devices114correspond to which users and/or user accounts.

In step404, public and private encryption keys may be generated. The keys are exchanged between remote processing100and central processing115.

In step406, the keys are stored respectively and are communicated to one or more ATMs134in the ATM network132. The keys are subsequently used to secure communications between device114and ATM134.

In step408, the validation/registration process for the user, the user's account, and the user's device(s) is concluded. Pre-stage transaction entering and processing as well as haptic feedback functionality on the device(s)114is enabled.

FIG.5is an illustrative flowchart of a method performed in accordance with one or more implementations for remote pre-staging, central processing, and local handling of pre-staged transactions using UWB-enabled ATM machines134and devices114that are capable of providing haptic feedback.

In step500, a login process is initiated and handshaking, validating, and authenticating is commenced and implemented between UWB-enabled wireless portable electronic device(s)114(and/or the users of such devices and/or their corresponding accounts) and central processing115such as ATM server(s)115-1.

In step502, user(s) pre-stage their transaction(s) on UWB-enabled wireless portable electronic device(s)114and/or through alternate Internet-connected computing devices113-1or113-2via web page(s) or dedicated executable applications. Transaction pre-staging in this step allows users to select one or more account(s) and/or card(s) correlated to accounts for account activity. Users may pre-stage one or more withdrawal(s), deposit(s), transfer(s), wire(s), and/or any other ATM transaction or the like including the amount(s) of any such pre-staged transaction(s). Pre-staged transaction(s) may then be locally stored306in non-volatile memory300on the UWB-enabled device(s)114. Or they may be transmitted wirelessly from central processing115or ATM server(s)115-1to device(s)114and then stored306in device memory300.

In step504, central processing115or ATM server(s)115-1process and store pre-staged transaction(s). An entry timestamp may be applied to the transaction(s) and an expiration timestamp may be assigned as well. One or both of these timestamps may be used to set time period and/or duration of time during which the pre-staged transaction(s) will be valid or will remain valid.

In step506, central processing115or ATM server(s)115-1may publish, to one or more applicable ATM machines134in an applicable geographical region, user information, user account identifier(s), timestamp transaction information or restrictions, the pre-staged transaction(s) or information that would enable ATMs134to retrieve the pre-staged transaction(s) from central processing115or ATM server(s)115-1on demand in real time.

In step508, processing regarding management of queues and queue wait times, management of resources at ATMs134, and calculations of preferred ATMs based on wait times, proximity between the user and the ATMs, user historical usage of ATMs, user preferences, and/or user selections can be performed.

In step510, user devices(s)114can be provided notifications regarding queue wait times indirectly from central processing115or ATM server(s)115-1, or directly from local ATMs134in the ATM network132. ATM location recommendations or preferences can be provided to the users as well. Based on the information and notifications provided to the users, they can make selection(s) of one or more UWB-enabled ATMs134at which they would like to complete the pre-staged transactions.

In step512, UWB-enabled ATMs134in the ATM network132constantly monitor or scan devices in the range of the ultra-wideband network to detect whether device(s)114are in range of one of the applicable ATMs134. If a UWB-enabled ATM134detects, within its UWB range, one or more UWB-enabled device(s)114, the ATM134can poll or obtain hardware identifier information regarding device114and determine whether the user and/or user device114has any time-valid pre-staged transactions scheduled for the ATM134or that are available for completion at the ATM134. Initial communication(s) between UWB-enabled ATM(s)134and UWB-enabled device(s)114can be performed securely or in an unsecure fashion as desired.

If any such pre-staged transactions are available or scheduled for device(s)114at the ATM134, an encryption handshake using the private and public keys can be performed to secure communications between the device(s) and machine(s). The ATM can then wirelessly send a notification to trigger directly a haptic-feedback reminder on a user's UWB-enabled device114or indirectly on a non-UWB-enabled wearable device or other device wirelessly coupled thereto. This would encompass any device coupled via Bluetooth, Wi-Fi, NFC, etc. to device114. It could also include ear pieces or the like in which audible triggers are provided or that vibrate when triggered.

Upon receipt of the notification, UWB-enabled device114or non-UWB-enabled wearable device wirelessly coupled thereto can provide haptic feedback in step414to the user in step512to notify or remind users about their pre-staged transaction. A session can then be established between the ATM134and device114in this step including user/device authentication, validation, and selection of one or more of the pre-staged transactions to perform, after which the pre-staged transactions are executed.

FIG.6is an illustrative flow chart and functional block diagram for queue management, proximity analysis, preference score determinations, machine/device communications regarding recommendations, options, and user selections in which certain aspects of the present disclosure may be implemented.

In step600, central processing115or ATM server(s)115-1can initiate management functions and processes relating to managing queues at ATMs134in ATM network132, and can provide notifications or communicate the results of such functions/processes to UWB-enabled ATMs134and/or UWB-enabled devices114.

In step602, one or more proximities between device(s)114and various ATMs within ATM network132can be determined by calculating the relative distances between device(s)114and ATMs134. These determinations are preferably performed in real-time, but could also be performed one time, periodically, and/or on-demand. UWB technology enables precise and fast location determinations, which facilitates the real-time performance of the calculations.

In step604, a preference score for one or more of the ATMs134in the network132can be calculated based on any desired criteria. These criteria could be based on a user's historical usage or frequency of visits to the particular ATM, where the ATM is located with respect to the user's planned path of travel, where the ATM is located based on the user's historical travel pattern for a particular time of day.

In step606, individual queue wait times for various ATMs134in the ATM network132can be calculated based on fixed and/or variable factors, either at the current time or projected for the future. This may include calculating a number of customers present at ATMs134(fixed), the number of customers in line at the ATMs134(fixed and/or variable), and/or available resources at the ATM134(fixed and/or dynamic). Resources could include the number of bills of various currency denominations that are available for withdrawal or could be based on available ATM functionality. The number of users with pre-staged transactions at the particular ATM134(variable) could be calculated as well as the available ATM resources (fixed and/or variable) can be determined or projected.

In step600, central processing115or ATM server(s)115-1can then provide notifications or output the results of such functions/processes to UWB-enabled ATMs134and/or UWB-enabled devices114.

In step608, wait time(s), location/preference score recommendation(s), and/or direction information to the ATMs can be communicated to device(s)114for user consideration.

In step610, users are able to set preferences regarding the ATM(s) at which they would like to execute their pre-staged transaction(s). Updated information from central processing115or ATM server(s)115-1can be provided as desired or as updated calculations are available. Updated user directions to the ATMs134based on user selections as well.

FIG.7is a functional block diagram depicting an exemplary “time of flight” (ToF) method of utilizing UWB technology to locate UWB-enabled devices in relation to UWB-enabled ATM machine(s) in which certain aspects of the present disclosure may be implemented.

As illustrated inFIG.7, a UWB initiator device700(e.g., a UWB-enabled ATM134) can send a poll message in step704to a UWB responder device702. The amount of time for the device114to reply to the poll message can be determined in step706. A UWB response can then be returned in step708to the UWB initiator device700and the time for the loop can be determined in step710such that the time of flight (ToF) can be calculated in step712based on subtracting the reply time from the loop time, and then dividing the result by 2. This can be used to determine whether a UWB responder device702is within range of the UWB initiator device700and/or whether the UWB responder device702is within a pre-determined “desired” range of the UWB initiator device700.

FIG.8is a geographical representation of using utilizing UWB technology in suitably enabled ATM machine(s)134in an ATM network132to detect when UWB-enabled devices114are in range and to trigger haptic feedback notifications to provide reminders of pre-staged transaction(s) in which certain aspects of the present disclosure may be implemented.

This can be accomplished in real-time, periodic, and/or on demand methods and calculations or determinations. For example, in steps800and802, ATM machines134-1and134-2can respectively broadcast UWB messages to any UWB-enabled devices114in ranges #1and #2, and can detect the presence of any such devices114. In the examples of steps800and802, no device(s)114were detected and therefore no further actions are taken at that time. Conversely, in step804, ATM134-3detects the presence of a UWB-enabled device114and can then send notification(s) to trigger haptic feedback, which can are then provided on device114.

FIG.9shows sample methods steps in which various aspects of the present disclosure may be implemented in UWB automated pre-staged transaction system(s).

In step900, an ATM sever115-1can receive unique hardware identifier(s) and unique user identifier(s) for device(s)114along with pre-staged transaction(s), and store some or all of the information in memory115-2.

In step902, ATM server115-1can generate private and public encryption keys corresponding to the user and user devices, which may also be stored in memory115-2, and can be transmitted to user device(s)114.

In step904, one or more ATM machines134can receive from the ATM server(s)115-1and store in local memory: the pre-staged transaction(s), the unique user and/or hardware identifier(s), and the public/private encryption keys.

In step906, an ATM UWB transceiver or other suitable hardware can detect device(s)114, based on the unique user and/or hardware identifiers, when within wireless range (e.g., range 3 ofFIG.9).

In step908, a secure transaction session can be established between the ATM134and device114based on the public encryption key, the private encryption key, and/or the unique identifiers.

In step910, ATM134can wirelessly transmit to device(s)114a first haptic-feedback notification if one or more pre-staged transaction(s) have not been completed and are still valid for the particular day and time, and corresponding haptic feedback can be provided on the device(s) in response thereto.

In step912, ATM134can execute the pre-staged transaction(s) if authorized by device(s)114, and ATM134can notify central processing115or ATM server(s)115-1regarding completion of the transactions.

In step914, central processing115or ATM server(s)115-1can update their records to note the same by making storing appropriate indications in their memory115-2.

FIG.10shows additional exemplary method steps through execution of one or more of the depicted steps can be used to implement certain aspects of the present disclosure in UWB automated pre-staged transaction system(s), UWB-enabled ATMs, or on UWB-enabled devices.

In step1000, central processing115or ATM server(s)115-1can receive a UWB location for the user and/or user device(s)114.

In step1002, central processing115or ATM server(s)115-1can calculate proximities from the device(s) to one or more ATM machines134.

In step1004, central processing115or ATM server(s)115-1can calculate queue wait times for one or more ATM machines134.

In step1006, central processing115or ATM server(s)115-1can calculate an ordered preference list based on the queue wait times and the proximities.

In step1008, central processing115or ATM server(s)115-1can transmit to device(s)114the ordered preference list to enable user-selection of one or more of the ATM machines134.

FIG.11shows sample steps to implement certain aspects of the present disclosure in UWB ATM transaction pre-staging method(s) for use with one or more UWB-enabled devices.

In step1100, central processing115or ATM server(s)115-1can register unique user identification and corresponding unique hardware identifiers for the user's devices114.

In step1102, central processing115or ATM server(s)115-1can generate public and private encryption keys for the user, and can transmit them to the user's devices114.

In step1104, central processing115or ATM server(s)115-1can authenticate and initiate pre-stage transaction session(s) for device(s)114.

In step1106, device(s)114can transmit to and/or schedule with ATM server115-1one or more pre-staged transaction(s).

In step1108, ATM server115-1processes one or more pre-staged transaction(s) and communicates the same to one or more ATMs134in the ATM network132.

In step1110, ATMs134detect the presence within its UWB range the device(s)114based on unique hardware identifier(s), identify unique user identification based on the unique hardware identifier(s), and identify pre-stage transaction(s) for the user.

In step1112, ATMs134transmit a notification to the device(s) to trigger haptic feedback thereon and the haptic feedback is provided.

In step1114, device(s)114complete the pre-staged transaction(s) on ATMs134.

FIG.12shows exemplary steps to implement certain aspects of the present disclosure in UWB ATM transaction pre-staging method(s) for use with one or more UWB-enabled devices.

In step1200, pre-stage transaction(s) are scheduled by device(s)114or alternate devices.

In step1202, ATMs134receive or retrieve from ATM server(s)115-1a list of all pre-staged transactions.

In step1204, ATMs134transmit identification information relating to the list.

In step1206, ATMs134perform a proximity check to determine if any devices114are in UWB range and, if so, broadcast message(s) to device(s)114, and secure communication between the machine and device(s) via public and private encryption keys.

In step1208, haptic feedback is triggered directly on or indirectly through device(s)114in response to broadcast message(s).

In step1210, a banking app is opened automatically or manually on device(s)114and is used to establish a session with ATMs134and manage the session.

In step1212, the location of device(s)114is determined in relation to ATMs134.

In step1214, ATMs134calculate wait times and manages at least one queue. And the banking app is used to complete the pre-staged transaction(s).

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.