Patent ID: 12248926

DETAILED DESCRIPTION

Exemplary embodiments may enable synchronization of a display of a mobile computing device with a display of an ATM. The displays first may be synched when a user positions the mobile computing device in proximity to the ATM. Near field communication (NFC) initially may be used when the mobile phone is in proximity with the ATM. A party may be prompted to tap the mobile computing device with a designated area on the face of the ATM or scan a scannable code with the mobile computing device at the ATM to prompt the connection in some exemplary embodiments. The NFC communication may be used to establish a communication connection between the mobile computing device and the ATM and may prompt an initial sequence on the displays indicating that the displays are synched.

The displays may reflect when a mobile computing device is in proximity to an ATM. For instance, a particular graphic may be displayed when the mobile computing device is in proximity to an ATM. The graphic may change as the mobile computing device gets closer to the ATM. The change may be, for example, in the form of changing intensity, color, shape or the like. In addition, the displays may provide a visual cue indicating that a communication connection between the mobile computing device and ATM has been realized. Once the communication connection has been realized, the displays may be synchronized to reflect the connection.

After the NFC connection has been realized, a cellular connection between a user's mobile computing device with a server having a secure connection with the ATM may be established. This may be prompted by opening an application responsive to the NFC communication and the application establishing the cellular connection. One or more financial transactions may be initiated with the ATM from the mobile computing device via the cellular connection. The display of the mobile computing device and the ATM may remain synched during the one or more financial transactions.

FIG.1depicts components of an environment100in which exemplary embodiments may be practiced. This depiction is merely illustrative and is not intended to be limiting. A mobile computing device102is connected to a wireless network104. The mobile computing device102may take many forms. The wireless network104may be, for instance, a cellular network or an 802.11 network. The wireless network104may interface with a wired network106, such as the Internet and/or other networks. In an illustrative case, the wired network106, includes the Internet and other wired networks, such as private networks of a financial institution that have an interface with the Internet. An ATM108and a server110may be interfaced with the wired network106. The ATM108may be for the financial institution or may be for another financial institution but allow access to customers of the financial institution. The server110may be resident on a private network for a financial institution or may be provided as part of secure cloud services provided for the financial institution. The server110has a secure connection with the ATM108.

FIG.2Adepicts illustrative components for a mobile computing device200for use with exemplary embodiments. The mobile computing device200may include a processor202. The processor202may be a microprocessor, such as a central processing unit (CPU), a graphics processing unit (GPU), etc. The processor202may be realized as a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a controller, electric circuitry or the like that provides the functionality described herein for the processor of the mobile computing device200. The mobile computing device200may include a storage204. The204storage may include volatile memory and/or non-volatile memory. The storage204may include optical and/or magnetic storage devices and may include non-transitory computer-readable storage media storing instructions for execution by the processor202. The storage204may include magnetic disk drives, optical disk drives, solid state storage, read only memory, random access memory, flash memory and the like. In the depiction ofFIG.2, the storage204stores an application program206and proximity protocol support208for NFC communication. It will be appreciated that the storage204may store other programs and data.

The mobile computing device202may include a wireless transceiver210, such as required to participate in NFC communications. The transceiver may be part of an NFC reader. The mobile computing device202may additionally include a display device212, such as a light emitting diode (LED) display, a liquid crystal display (LCD) or a retinal display. The mobile computing device may include a wireless modem214for enabling communication over a wireless network, such as a cellular phone network. The mobile computing device200may include a camera216for capturing images and/or video. The camera216may also be used in scanning optical codes.

FIG.2Bdepicts a block diagram240that depicts some of the different forms that mobile computing device242may take. For example, the mobile computing device242may be a mobile phone244or a tablet computing device246. In addition, the mobile computing device242may be a wearable248, such as a smart watch, that has cellular and NFC capabilities. The mobile computing device242may be an intelligent pager248or a personal digital assistant252with NFC and cellular capabilities.

FIG.3depicts a block diagram of an illustrative ATM300. The ATM300may include a processor302for executing software and providing functionality as described herein. The processor302may take many forms, such as those described above relative to the mobile computing device200. The ATM300may include a network interface304, such as a network adapter, for interfacing with a network, such as a secure local area network (LAN). The ATM300additionally may include a display306for displaying images, video and graphic content. The display304may take various forms, such as those described above for the mobile computing device200. A storage308may be provided in the ATM300and may be used to store executable programming language code and data. The storage may take many forms, like those described above for the mobile computing device200.

In order to support NFC communications, the ATM300may include NFC components310. These NFC components310may include an NFC tag or reader as well as software that supports an NFC protocol.

The ATM300may include a keypad312that enables a user to provide input to the ATM. The keypad312may include buttons for entering alpha-numeric values. For example, a user may enter a PIN or a dollar amount value using the keypad312. The ATM may have a cash dispenser314for dispensing currency such as bills. The ATM300may include a camera316for capturing images of parties in proximity to the ATM. The camera316may take the form of a digital camera that captures snapshot and/or videos. The camera316may be used for security purposes. The ATM300may also include deposit hardware318for accepting deposits in the form of checks or cash. The ATM300may include further components, such as a card reader320for reading ATM cards and a printer322for printing receipts, statements and the like.

The depiction of the ATM components inFIG.3is merely illustrative and is not intended to be limiting.

FIG.4Adepicts one possible configuration of a front face of an ATM400for use in an exemplary embodiment. The front face is the face that faces the customer. Not only of the components of the front face are depicted inFIG.4A. The front face of the ATM includes a display402for displaying graphical and video content, such as has been described above relative to display306ofFIG.3. The front face of the ATM also includes the keypad404for the user to enter alpha number input and press any function keys. A card reader408and a cash dispenser410may be provided. Further, a deposit slot412and a receipt slot414may be provided along with a camera416. The front face further includes a designated area406. The designated area406may contain NFC hardware and is designed to be an area where a user may put a mobile computing device in proximity or contact to initiate an NFC communication session as will be described below.

FIG.4Bdepicts an alternative configuration for the front face of the ATM for some exemplary embodiments. In this configuration, the designated area406is not provided. Instead, scannable code418, such as a QR code, a barcode or other scannable code is provided. The scannable code418may be optical or magnetic. In this configuration, the user scans the scannable code with the mobile computing device to trigger a communication session as will be described below. For instance, the camera216(FIG.2A) of the mobile computing device may be used to capture an image of the scannable code and software may be used to process the image, identify the code and respond accordingly.

It should be appreciated that the front face configurations ofFIGS.4A and4Bneed not be mutually exclusive; rather they may be combined to provide both a designated area406and a scannable code418.

The exemplary embodiments may provide visual feedback regarding proximity of a mobile computing device to an ATM and visual feedback regarding creation of a communication connection between a mobile computing device and an ATM.FIG.5Adepicts one example of such visual feedback. InFIG.5Aa user has positioned a mobile phone506in close proximity to a designated area504on an ATM. The user may even tap the mobile phone506with the designated area. A graphic508is displayed on the display of the mobile phone506but not on an ATM display. The graphic508in this instance is a dot. The graphic508is indicative of the mobile phone being in proximity to the ATM. Once a communication session between the ATM and the mobile computing device has been established, the graphic506may be shown on the mobile computing device display. A corresponding version of the graphic512may also be displayed on a display of the ATM504. A graphic connector514may be shown on both displays to connect graphic506with corresponding graphic512.

FIG.5Bshows another example of how visual cues may be provided. Initially an ATM display is blank. Then a graphic521is displayed on the display520of the ATM, which may appear and pulse as the mobile computing device gets closer (see successive views522,524,526and528). As shown in the rightmost depiction, when a communication session has been established the graphic521may be shown on both the display of the mobile computing device and the display of the ATM. The portion of the graphic521and the relative position of the portion may be based on the location of one display relative to the other. The visual result is that the displays are synchronized, and the visual result is as if a single shared graphic521is displayed.

FIG.6depicts a flowchart600of illustrative steps that may be performed in establishing an initial connection between a mobile computing device and an ATM. The process starts with a wireless protocol exchange, such as an NFC protocol exchange, being initiated (602). With an NFC protocol, the process may be initiated by the mobile device with NFC capabilities being in proximity with the ATM. In response to the communication session being initiated, the display of the mobile computing device is updated to provide a visual cue that the communications have begun (604). An example of this is the graphic506ofFIG.5A. The mobile computing device and the ATM then exchange messages until a connection is established (606). When the connection is established, the display of the mobile computing device and the display of the ATM may be updated to provide a visual cue of the connection (608), such as508,512and514shown inFIG.5A and521shown inFIG.5B.

Once the cellular connection has been established, the mobile computing device and the ATM may establish and communicate via a cellular telephone connection (702in flowchart700ofFIG.7). This may be initiated by the mobile computing device, such as by activating an application program that initiates a cellular connection with a server for the financial institution that operates the ATM. Other alternatives are possible. For instance, a user of the mobile computing device may be prompted to initiate the cellular connection, or a financial institution server may initiate the cellular connection. Once the cellular connection is established, a financial transaction with the ATM may be initiated by the user of the mobile computing device (704). In one example case, the application206(FIG.2) on the mobile computing device provides a user interface for a user to initiate any of a number of different types of financial transactions. The user interface may provide menu options, user interface elements like selectable button, dropdown lists, a prompt, or other mechanisms for selecting a transaction.

FIG.8shows a diagram800depicting some of the types of transactions802that may be available to the user of the mobile computing device. A user may be able to check the current balance of one or more accounts with the financial institution (804). This may entail displaying the balance on a display or printing a receipt containing the balance. The user may be able to make a deposit (806). The ATM may include one or more receptacles for receiving cash and/or checks for a deposit (such as found in the deposit hardware318inFIG.3). The user may request to make a withdrawal of cash from an account (808). The cash will be dispensed via a cash dispenser (such as314inFIG.3) of the ATM. A user may transfer funds from one account to another (810). The account may be owned by the user or may be external. Examples of such fund transfers include a transfer between a checking account and a savings account, an electronic funds transfer, such as a wire transfer, an electronic bill payment or the like, and an automated clearing house (ACH) transaction. A user may also make purchases (812) in some embodiments. The purchases may buy goods, like stamps or tickets, or services using funds from an account or using credit for an associated credit card account.

It should be appreciated that that the list of transactions is intended to be illustrative and not limiting. Other types of transactions may be realized via the approach disclosed herein.

Once the transaction is initiated the display of the mobile computing device may be synched with the display of the ATM (706inFIG.7).FIG.9depicts a flowchart900of steps that may be performed to synch the displays. Initially, the position of the mobile computing device (and hence the associated display) relative to the display of the ATM is determined (902). This position determination may be based on the NFC interaction, GPS information and/or gyroscopic information from a gyroscope in the mobile computing device. In some instances, a camera (such as camera216inFIG.2) on the mobile computing device may be used to determine the relative location. The camera may capture image of the ATM and know the proximity based on those images using conventional techniques for image processing. The location is communicated from the mobile computing device to the server (such as server110inFIG.1) (904). Based on the communicated position information, the server or the ATM update the ATM display (906) so that the displays display content in the appropriate portions on the respective displays to appear to be in synch spatially as will be described below. Subsequently, based on the position information transmitted from the mobile computing device, the position of the display of the mobile computing device may be detected as changing (908) and the display of the ATM is updated accordingly (910). Since the display of the ATM is fixed, there is no need to be concerned with the position of the display of the ATM.

FIG.10Aillustrates an example of synchronized content1006and1008being shown on both a display of a mobile computing device1004and on an ATM display1002. The synchronized content1006and1008are displayed in a manner that is synchronized both temporally and spatially. For example, if the synchronized content is graphic content where a portion is shown on both displays1002and1004, the mobile computing device and the ATM must communicate to synch the timing of when the graphic content is displayed and where on the screen the respective portions of the content1006and1008are displayed. Moreover, the timing of removal of the content must be synched and communicated between the mobile computing device and ATM. When the content is dynamic, such as an animation or video, timing and positioning of the display of the respective portions is critical.

When the transaction is complete (708inFIG.7), the transaction session between the mobile computing and the ATM may be completed (710). This is akin to the ending of a traditional ATM transaction. The cellular connection between the mobile computing device is terminated at the end of the session. The displays1002and1004are updated to provide a visual cue that the transaction is complete (712).FIG.10Bshows a diagram1000depicting an example of the synched display of an end of transaction message1018and1020on the respective displays1002and1004.

The positioning and the timing of synchronized timing can be especially acute when the content is a shared animation.FIG.11depicts a flowchart1100of steps that may be taken with respect to showing an animation across synchronized displays on a mobile computing device and an ATM. The first step is to determine where and when to display the animation across the displays (1102). This step will be described below in more detail with reference toFIG.12. The starting of the separate displays of the animation between the mobile computing device and the ATM are coordinated (1104). For instance, the mobile computing device and the ATM may synch their clocks and agree to start the animations at a specific clock time. Alternatively, the camera of the mobile computing device may be used to capture the animation on the ATM display and the captured images may be used to synch accordingly. In some instance a portion of a common animation may be displayed on both displays. In other instances, separate but related animations may be displayed on both displays. The synchronized animations are then displayed on the displays of the mobile computing device and the ATM (1106). Communications may be exchanged during the playing to ensure the animations remain temporally and spatially synched. In some embodiments, frames may be added or removed to slow down or speed up an animation.

FIG.12depicts a flowchart1200of steps that may be performed in resolving the location and timing of the display of animations on the mobile computing device and the ATM. First, the relative position of the display of the mobile computing device relative to the display of the ATM is determined (1202), such as has been described above. Next, a determination is made regarding where to position an animation window is on each display (1204). This may depend what effect is sought. If the desired effect is to have the animations appear as a single animation, the windows may be positioned on a display edge so that content appears to rollover from one display to another. In other cases, the animations may be distinct and therefore the positioning of the animation window may be independent of the positioning in the other display. The timing of the start of the animations is then synched such as described above (1206). The animations are then displayed in the respective animation windows (1208). The animations may take the form of video or dynamic graphic content.

While the present invention has been described with reference to exemplary embodiments, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the intended scope of the present invention as defined in the appended claims.