Mobile account data access systems and methods
Embodiments of mobile banking systems are described herein. Other examples and related methods are also disclosed herein.
Latest Green Dot Corporation Patents:
The current application claims priority as a continuation of U.S. patent application Ser. No. 13/941,492 filed Jul. 13, 2013, entitled “Mobile Banking Systems and Related Methods”, which claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application No. 61/671,478 filed Jul. 13, 2012, entitled “Method and System for Online Mobile Banking” the disclosure of which is incorporated by reference herein in its entirety.
TECHNICAL FIELDThe present disclosure relates generally to banking systems, and relates, more particularly, to mobile banking systems and related methods.
BACKGROUNDThe popularity and widespread use of mobile devices, such as smartphones, has opened new gateways from which to engage in banking transactions, Because of the sensitive nature of information contained in bank accounts, however, strenuous security and authentication features are required to permit safe banking transactions through such mobile devices. Such security can come at a convenience cost in terms of repeated required authentications to access specific non-critical data about such bank accounts.
Considering the above, further developments can be made to ease access to such specific non-critical data without compromising the security of the bank accounts.
The present disclosure will be better understood from a reading of the following detailed description of examples of embodiments, taken in conjunction with the accompanying figures in the drawings.
For simplicity and clarity of illustration, the drawing figures illustrate the general manner of construction, and descriptions and details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the present disclosure. Additionally, elements in the drawing figures are not necessarily drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help improve understanding of embodiments of the present disclosure. The same reference numerals in different figures denote the same elements.
The terms “first,” “second,” “third,” “fourth,” and the like in the description and in the claims, if any, are used for distinguishing between similar elements and not necessarily for describing a particular hierarchical, sequential, or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms “include,” and “have,” and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, device, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, system, article, device, or apparatus.
The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,” “under,” and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.
The terms “couple,” “coupled,” “couples,” “coupling,” and the like should be broadly understood and refer to connecting two or more elements or signals, electrically, mechanically or otherwise. Two or more electrical elements may be electrically coupled, but not mechanically or otherwise coupled; two or more mechanical elements may be mechanically coupled, but not electrically or otherwise coupled; two or more electrical elements may be mechanically coupled, but not electrically or otherwise coupled. Coupling (whether mechanical, electrical, or otherwise) may be for any length of time, e.g., permanent or semi-permanent or only for an instant.
“Electrical coupling” an the like should be broadly understood and include coupling involving any electrical signal, whether a power signal, a data signal, and/or other types or combinations of electrical signals. “Mechanical coupling” and the like should be broadly understood and include mechanical coupling of all types. The absence of the word “removably,” “removable,” and the like near the word “coupled,” and the like does not mean that the coupling, etc. in question is or is not removable.
DESCRIPTIONIn one embodiment, a system for mobile banking can comprise a mobile module for providing access to a first bank account of a user. The mobile module can comprise a login module and a main account module accessible via the login module and configured to at least one of receive a first account balance of the first bank account and further account information about the first bank account, or request one or more transactions for the first bank account. The mobile module can also comprise a quick-balance module accessible separate from the main account module and configured to receive a first account balance of the first bank account and to provide a first quick-balance report of the first account balance. The login module can be configured to receive initial authentication of the user to enable initial access to the main account module and to the quick balance module for the first bank account, and to receive subsequent authentication of the user for subsequent access to the main account module. The mobile module can impede the subsequent access to the main account module until receipt of the subsequent authentication of the user via the login module. In addition, the mobile module can permit access to the quick-balance report of the quick-balance module without requiring the subsequent authentication of the user.
In one implementation, a method for facilitating mobile banking can comprise providing a mobile module for mobilely interfacing with a first bank account. Providing the mobile module can comprises providing a login module, providing a main account module accessible via the login module, and providing a quick-balance module accessible separate from the main account module. The login module can be configured to receive user initial authentication for initial access to the main account module and to the quick balance module for the first bank account, and to receive user subsequent authentication for subsequent access to the main account module. The main account module can be configured to at least one of receive a first account balance of the first bank account and further account information about the first bank account, or request one or more transactions for the first bank account. The quick-balance module can be configured to receive the first account balance for the first bank account and to provide a first quick-balance report of the first account balance. The mobile module can be configured to impede the subsequent access to the main account module until receipt of the user subsequent authentication via the login module. Furthermore, the mobile module can be configured to permit access to the quick-balance report of the quick-balance module without requiring the user subsequent authentication.
Other examples and embodiments are further disclosed herein. Such examples and embodiments may be found in the figures, in the claims, and/or in the present description.
Turning to the drawings,
Mobile device 1200 can be configured to establish wireless connection 1710 with Internet 1700. Similarly, bank server 1510 of banking institution 1500 can be configured to communicate via Internet 1700 through connection 1720, which may be wired or wireless. Thus, mobile device 1200 and bank server 1510 can communicate via Internet 1700. In some examples, a portion of connection 1710 and/or of connection 1720 can be carried out via a network configured for a wireless and/or cellular standard such as WiFi (IEEE 802.11a/b/g/n), WiPAN (IEEE 802.15, Bluetooth®), W-CDMA (Wideband Code Division Multiple Access), HSPA (High Speed Packet Access), EDGE (Enhanced Data Rate for GSM Evolution), WIMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), etc.
System bus 1014 also is coupled to memory 1088 that includes both read only memory (ROM) and random access memory (RAM). Non-volatile portions of memory 1008 or the ROM can be encoded with a boot code sequence suitable for restoring computer 900 (
Network adapters 1020 can be coupled to one or more antennas. In some embodiments, network adapter 1020 can be configured for WiFi communication (IEEE 802.11), and/or may be part of a WNIC (wireless network interface controller) card (not shown) plugged or coupled to an expansion port (not shown) in computer 900. Such WNIC card can be a wireless network card built into internal computer 900 in some examples. A wireless network adapter can be built into internal client computer 900 by having wireless Ethernet capabilities integrated into the motherboard chipset, or implemented via a dedicated wireless Ethernet chip, connected through the PCI (peripheral component interconnector) or a PCI express bus. In the same or other embodiments, network adapters 1020 can be configured for communication via other wireless protocols, such as via WPAN, W-CDMA, HSPA, EDGE, WiMAX, LTE, or others. In other embodiments, network adapter 1020 can be a wired network adapter.
Although other components of computer 900 are not shown, such components and their interconnection are well known to those of ordinary skill in the art. Accordingly, further details concerning the construction and composition of computer 900 and the circuit boards inside chassis 902 need not be discussed herein.
When computer 900 is in operation, program instructions stored on bard drive 914, on memory 1008, on a USB drive in USB port 912, and/or on a CD-ROM or DVD in CD-ROM and/or DVD drive 916, can be executed by CPU 1010 (
In the present example of
Mobile module 1600 is also shown in
As shown in
As seen in
Login module 4610 (
Main account module 4620 (
Quick-balance nodule 4630 (
The illustration of
Quick-balance interface 5630 will not present quick balance report 4631 until the user has enabled quick-balance module 4630 and/or quick-balance interface 5630 as a feature after successfully logging in via initial authentication 5611. For instance,
There can be embodiments where, when user 1900 enables quick-balance module 4630 as described above, an authentication token can be enabled for permitting quick-balance module 4630 to provide reports such as quick balance report 4631. In some examples, such authentication token can be similar to authentication token 4210 (
Once user 1900 has successfully logged-in via initial authentication 5611 (
As seen in the examples of
There can also be embodiments where quick-balance module 4630 (
Moving on,
Method 11000 comprises block 11100 for providing a mobile module for mobilely interfacing with a first bank account. In some examples, the mobile module can be similar to mobile module 1600, as described above with respect to
Block 11100 can comprise several sub-blocks in some implementations. For instance, block 11100 can comprise sub-block 11110 for providing a login module, which can be similar to login module 4610 as described above with respect to
Method 11000 also comprises block 11200 for impeding subsequent access to the main account module until receipt of user subsequent authentication via the login module. In some examples, the user subsequent authentication can be as described above with respect to subsequent authentication 8611 (
Method 11000 further comprises block 11300 for permitting access to a quick-balance report of the quick-balance module without requiring the user subsequent authentication. In some examples, the quick-balance report can be similar to quick-balance report 4631, 4632, or 4633 of quick-balance module 4630, and can be accessed via a quick-balance interface similar to quick-balance interface 5630 (
In some examples, one or more of the different blocks of method 11000 can be combined into a single block or performed simultaneously, and/or the sequence of such blocks can be changed. For example, sub-blocks 11110, 11120, and/or 11130 can be combined into a single sub-block. In the same or other examples, some of the blocks of method 11000 can be subdivided into several sub-blocks. There can also be examples where method 11000 can comprise further or different blocks. As an example, method 11000 can further comprise a block for accessing further detailed information about the first bank account, and/or for requesting transactions for the first bank account. In addition, there may be examples where method 11000 can comprise only part of the steps described above.
In some instances, the exemplary modules described above may be implemented as machine-accessible instructions utilizing any of many different programming codes stored on any combination of machine-accessible media embodied in a mobile application (e.g., an app) and/or an online application for various wired and/or wireless mobile communication devices such as handheld computers, smartphones, portable media players, tablet computers, etc. In addition or alternatively, the machine-accessible instructions may be embodied in a volatile or non-volatile memory or other mass storage device (e.g., a USB drive, a CD, or a DVD). For example, the machine-accessible instructions may be embodied in a machine-accessible medium such as a programmable gate array, an application specific integrated circuit (ASIC), an erasable programmable read only memory (EPROM), a read only memory (ROM), a random access memory (RAM), a flash memory, a magnetic media, an optical media, and/or any other suitable type of medium. The systems, apparatus, methods, and articles of manufacture described herein are not limited in this regard.
Although the mobile banking systems and related methods herein have been described with reference to specific embodiments, various changes may be made without departing from the spirit or scope of the present disclosure. Examples of such changes have been given in the foregoing description. Other permutations of the different embodiments having one or more of the features of the various figures are likewise contemplated. Accordingly, the specification and drawings herein are intended to be illustrative of the scope of the disclosure and are not intended to be limiting. It is intended that the scope of this application shall be limited only to the extent required by the appended claims.
The mobile banking systems and related methods discussed herein may be implemented in a variety of embodiments, and the foregoing discussion of certain of these embodiments does not necessarily represent a complete description of all possible embodiments. Rather, the detailed description of the drawings, and the drawings themselves, disclose at least one preferred embodiment, and may disclose alternative embodiments.
All elements claimed in any particular claim are essential to the embodiment claimed in that particular claim. Consequently, replacement of one or more claimed elements constitutes reconstruction and not repair. Additionally, benefits, other advantages, and solutions to problems have been described with regard to specific embodiments. The benefits, advantages, solutions to problems, and any element or elements that may cause any benefit, advantage, or solution to occur or become more pronounced, however, are not to be construed as critical, required, or essential features or elements of any or all of the claims, unless such benefits, advantages, solutions, or elements are expressly stated in such claim.
Moreover, embodiments and limitations disclosed herein are not dedicated to the public under the doctrine of dedication if the embodiments and/or limitations: (1) are not expressly claimed in the claims; and (2) are or are potentially equivalents of express elements and/or limitations in the claims under the doctrine of equivalents.
Claims
1. A computing device for displaying account data from a remote server, comprising:
- a display screen;
- a set of one or more processors; and
- a memory connected to the processor and storing an application, wherein the application directs the processor to: present a login graphical user interface (GUI) on the display screen comprising a login control for interfacing with a login module to log in to a remote server; authenticate a user for a first session with the remote server through the login GUI based on a first authentication token received from the remote server; present an account GUI on the display screen for displaying account data associated with the user at the remote server, wherein the account GUI comprises a set of tools for interfacing with a main account module of the application to receive account data and request transactions with the remote server; determine whether a summarized view is to be enabled in order to obtain a second authentication token; determine whether the first session has ended and whether the second authentication token has been obtained; when the first session has ended and the second authentication token has been obtained: communicating with the remote server using the second authentication token to receive a summary report of the account data associated with the user at the remote server; modifying the login GUI to include an actuating graphical element for providing the summary report of the account data when actuated, wherein the actuating graphical element conceals the summary report of the account data; presenting the modified GUI comprising the actuating graphical element on the display screen; and upon receiving a user input through the actuating graphical element of the modified login GUI to view the summary report, displaying the summary report of the account data on the modified login GUI on the display screen.
2. The computing device of claim 1, wherein authenticating the user for the first session comprises generating the first authentication token to authenticate the user at the remote server.
3. The computing device of claim 1, wherein authenticating the user for the first session comprises communicating with the remote server to receive the first authentication token from the remote server.
4. The computing device of claim 1, wherein the account data comprises account balance data.
5. The computing device of claim 1, wherein the application further directs the processor to communicate with the remote server to modify the account at the remote server based on interactions with the set of tools.
6. The computing device of claim 1, wherein modifying the account comprises at least one of the group consisting of closing the account, opening a new account, transferring funds to the account, and transferring funds from the account.
7. The computing device of claim 1, wherein the application further directs the processor to detect the end of the first session by detecting at least one of a timing out of the first session and a user input for ending the session.
8. The computing device of claim 1, wherein the summary report comprises an account balance.
9. The computing device of claim 1, wherein the actuating element is a slide bar actuator, wherein the user input comprises sliding of the slide bar actuator to reveal the summary report of the account data.
10. The computing device of claim 9, wherein the modified login interface further comprises a second slide bar actuator, wherein actuation of the second slide bar actuator reveals a summary report of a second account associated with the user.
11. The computing device of claim 1, wherein communicating with the remote server to retrieve the summary report of the account data comprises sending the enabled second authentication token to the remote server.
12. A method for displaying account data on a mobile device, the method comprising:
- presenting a login graphical user interface (GUI) on a display screen of the mobile device comprising a login control for logging in to a remote server;
- authenticating a user for a first session with the remote server through the login GUI based on a first authentication token received from the remote server;
- presenting an account GUI on the display screen for displaying account data associated with the user at the remote server, wherein the account GUI comprises a set of tools to receive account data and request transactions with the remote server;
- determining whether a summarized view is to be enabled in order to obtain a second authentication token;
- determining whether the first session has ended and whether the second authentication token has been obtained;
- when the first session has ended and the second authentication token has been obtained: communicating with the remote server using the second authentication token to receive a summary report of the account data associated with the user at the remote server; modifying the login GUI to include an actuating graphical element for providing the summary report of the account data when actuated, wherein the actuating element conceals the summary report of the account data; presenting the modified GUI comprising the actuating element on the display screen; and upon receiving a user input through the actuating element of the modified login GUI to view the summary report, displaying the summary report of the account data on the modified login GUI on the display screen.
13. The method of claim 12, wherein authenticating the user for the first session comprises generating the first authentication token to authenticate the user at the remote server.
14. The method of claim 12 further comprising detecting the end of the first session by detecting at least one of a timing out of the first session and a user input for ending the session.
15. The method of claim 12, wherein the summary report comprises an account balance.
16. The method of claim 12, wherein communicating with the remote server to retrieve the summary report of the account data comprises sending the enabled second authentication token to the remote server.
4804984 | February 14, 1989 | Heuer et al. |
4939662 | July 3, 1990 | Nimura et al. |
5086394 | February 4, 1992 | Shapira |
5320409 | June 14, 1994 | Katoh et al. |
5740915 | April 21, 1998 | Williams |
5754939 | May 19, 1998 | Herz et al. |
5758313 | May 26, 1998 | Shah et al. |
5760381 | June 2, 1998 | Stich et al. |
5777305 | July 7, 1998 | Smith et al. |
5842629 | December 1, 1998 | Sprague et al. |
D411765 | July 6, 1999 | Holihan |
5918909 | July 6, 1999 | Fiala et al. |
5975302 | November 2, 1999 | Young |
5984091 | November 16, 1999 | Orr et al. |
6014090 | January 11, 2000 | Rosen et al. |
6049711 | April 11, 2000 | Ben-Yehezkel et al. |
6052122 | April 18, 2000 | Sutcliffe et al. |
6061681 | May 9, 2000 | Collins et al. |
6109439 | August 29, 2000 | Goade, Sr. |
6112186 | August 29, 2000 | Bergh et al. |
6185545 | February 6, 2001 | Resnick et al. |
6208934 | March 27, 2001 | Bechtolsheim et al. |
6224108 | May 1, 2001 | Klure |
6272467 | August 7, 2001 | Durand et al. |
6315206 | November 13, 2001 | Hansen et al. |
6317718 | November 13, 2001 | Fano |
6349829 | February 26, 2002 | Matheis et al. |
6366568 | April 2, 2002 | Bolgiano et al. |
6456854 | September 24, 2002 | Chern et al. |
6457649 | October 1, 2002 | Hileman |
6529136 | March 4, 2003 | Cao et al. |
6529143 | March 4, 2003 | Mikkola et al. |
6539232 | March 25, 2003 | Hendrey |
6549768 | April 15, 2003 | Fraccaroli |
6618593 | September 9, 2003 | Drutman et al. |
6639905 | October 28, 2003 | Müller et al. |
6687608 | February 3, 2004 | Sugimoto et al. |
6732459 | May 11, 2004 | Clark |
6819919 | November 16, 2004 | Tanaka |
6925441 | August 2, 2005 | Jones, III et al. |
6957737 | October 25, 2005 | Frederickson et al. |
6965868 | November 15, 2005 | Bednarek |
D512456 | December 6, 2005 | Diaz |
7039423 | May 2, 2006 | Daniel et al. |
7047030 | May 16, 2006 | Forsyth |
7071842 | July 4, 2006 | Brady, Jr. |
7082365 | July 25, 2006 | Sheha et al. |
7111323 | September 19, 2006 | Bhatia |
D532452 | November 21, 2006 | Heng |
7139731 | November 21, 2006 | Alvin |
7203502 | April 10, 2007 | Wilson et al. |
7203674 | April 10, 2007 | Cohen |
7236799 | June 26, 2007 | Wilson et al. |
7256711 | August 14, 2007 | Sheha et al. |
7271742 | September 18, 2007 | Sheha et al. |
7333820 | February 19, 2008 | Sheha et al. |
7363027 | April 22, 2008 | Hon et al. |
7392935 | July 1, 2008 | Byrne |
7486958 | February 3, 2009 | Sheha et al. |
7494056 | February 24, 2009 | Sturm |
7565155 | July 21, 2009 | Sheha et al. |
7593740 | September 22, 2009 | Crowley et al. |
7634354 | December 15, 2009 | Salmre |
7813741 | October 12, 2010 | Hendrey et al. |
7840224 | November 23, 2010 | Vengroff et al. |
7877082 | January 25, 2011 | Eagle et al. |
7917154 | March 29, 2011 | Fortescue et al. |
7978900 | July 12, 2011 | Nepomniachtchi et al. |
8000726 | August 16, 2011 | Altman et al. |
8023963 | September 20, 2011 | Yonker et al. |
8086530 | December 27, 2011 | Resnick et al. |
8099109 | January 17, 2012 | Altman et al. |
8181789 | May 22, 2012 | Kohler et al. |
8234214 | July 31, 2012 | Templeton et al. |
8275699 | September 25, 2012 | Shader et al. |
8352367 | January 8, 2013 | Templeton et al. |
8427942 | April 23, 2013 | Kim et al. |
8660943 | February 25, 2014 | Chirehdast |
8768838 | July 1, 2014 | Hoffman |
8977568 | March 10, 2015 | Schattauer et al. |
8989778 | March 24, 2015 | Pernikoff et al. |
9947004 | April 17, 2018 | Shankar et al. |
10706405 | July 7, 2020 | Shankar et al. |
20010001321 | May 17, 2001 | Resnick et al. |
20020052786 | May 2, 2002 | Kim et al. |
20020077745 | June 20, 2002 | Ohmura et al. |
20030016804 | January 23, 2003 | Sheha et al. |
20030036848 | February 20, 2003 | Sheha et al. |
20030055983 | March 20, 2003 | Callegari |
20030060214 | March 27, 2003 | Hendrey et al. |
20030061211 | March 27, 2003 | Shultz et al. |
20030064705 | April 3, 2003 | Desiderio |
20030078035 | April 24, 2003 | Sheha et al. |
20030149527 | August 7, 2003 | Sikila |
20030150762 | August 14, 2003 | Biller |
20040030647 | February 12, 2004 | Hansen |
20040054428 | March 18, 2004 | Sheha et al. |
20040224703 | November 11, 2004 | Takaki et al. |
20050021560 | January 27, 2005 | Yoon et al. |
20050027543 | February 3, 2005 | Labrou et al. |
20050032527 | February 10, 2005 | Sheha et al. |
20050043060 | February 24, 2005 | Brandenberg et al. |
20050044409 | February 24, 2005 | Betz et al. |
20050054352 | March 10, 2005 | Karaizman |
20050073443 | April 7, 2005 | Sheha et al. |
20050075119 | April 7, 2005 | Sheha et al. |
20050101300 | May 12, 2005 | Hon et al. |
20050114527 | May 26, 2005 | Hankey |
20050159996 | July 21, 2005 | Lazarus |
20050166058 | July 28, 2005 | Brokenshire et al. |
20050171898 | August 4, 2005 | Bishop et al. |
20050197954 | September 8, 2005 | Maitland et al. |
20050216337 | September 29, 2005 | Roberts et al. |
20050250552 | November 10, 2005 | Eagle |
20050268254 | December 1, 2005 | Abramson et al. |
20050283620 | December 22, 2005 | Khulusi et al. |
20050289340 | December 29, 2005 | Camenisch |
20060027663 | February 9, 2006 | Tang |
20060036364 | February 16, 2006 | Matsuo et al. |
20060047825 | March 2, 2006 | Steenstra et al. |
20060064346 | March 23, 2006 | Steenstra et al. |
20060085443 | April 20, 2006 | Pae |
20060089160 | April 27, 2006 | Othmer |
20060186011 | August 24, 2006 | Palmer |
20060223518 | October 5, 2006 | Haney |
20060255154 | November 16, 2006 | Newbrough et al. |
20060270419 | November 30, 2006 | Crowley et al. |
20060278551 | December 14, 2006 | Bianchini et al. |
20070050129 | March 1, 2007 | Salmre |
20070112614 | May 17, 2007 | Maga et al. |
20070150414 | June 28, 2007 | Templeton et al. |
20070252009 | November 1, 2007 | Kingsborough et al. |
20070253712 | November 1, 2007 | Katagiri et al. |
20070278293 | December 6, 2007 | Anderson et al. |
20070281689 | December 6, 2007 | Altman et al. |
20070281690 | December 6, 2007 | Altman et al. |
20080022382 | January 24, 2008 | Bradbury et al. |
20080052182 | February 28, 2008 | Marshall et al. |
20080082424 | April 3, 2008 | Walton |
20080086414 | April 10, 2008 | Ching |
20080091535 | April 17, 2008 | Heiser |
20080103959 | May 1, 2008 | Carroll et al. |
20080109358 | May 8, 2008 | Kottmeier et al. |
20080132252 | June 5, 2008 | Altman et al. |
20080133322 | June 5, 2008 | Kalia et al. |
20080133336 | June 5, 2008 | Altman et al. |
20080188246 | August 7, 2008 | Sheha et al. |
20080195536 | August 14, 2008 | Karns et al. |
20080208697 | August 28, 2008 | Kargman |
20080227473 | September 18, 2008 | Haney |
20080237317 | October 2, 2008 | Rosendall |
20080270802 | October 30, 2008 | Ashley |
20090063286 | March 5, 2009 | Rodriguez Porras |
20090081989 | March 26, 2009 | Wuhrer |
20090090783 | April 9, 2009 | Killian et al. |
20090164366 | June 25, 2009 | Blythe et al. |
20090177375 | July 9, 2009 | Jung et al. |
20090254413 | October 8, 2009 | Chang |
20090298481 | December 3, 2009 | Hurst |
20100036770 | February 11, 2010 | Fourez et al. |
20100106568 | April 29, 2010 | Grimes |
20100106569 | April 29, 2010 | Grimes |
20100106577 | April 29, 2010 | Grimes |
20100106596 | April 29, 2010 | Grimes |
20100106598 | April 29, 2010 | Grimes |
20100211499 | August 19, 2010 | Zanzot et al. |
20100240352 | September 23, 2010 | Suri et al. |
20100306089 | December 2, 2010 | Gelerman et al. |
20100318489 | December 16, 2010 | De Barros et al. |
20110016048 | January 20, 2011 | Lindqvist et al. |
20110029434 | February 3, 2011 | Templeton et al. |
20110035284 | February 10, 2011 | Moshfeghi |
20110047619 | February 24, 2011 | King et al. |
20110051665 | March 3, 2011 | Huang |
20110099082 | April 28, 2011 | Walker et al. |
20110208550 | August 25, 2011 | Lamarche et al. |
20110208612 | August 25, 2011 | Shader et al. |
20110208641 | August 25, 2011 | Shader et al. |
20110208642 | August 25, 2011 | Shader et al. |
20110208643 | August 25, 2011 | Shader et al. |
20110208649 | August 25, 2011 | Shader et al. |
20110225063 | September 15, 2011 | Grunski et al. |
20110251892 | October 13, 2011 | Laracey |
20110258122 | October 20, 2011 | Shader |
20110270661 | November 3, 2011 | Heiser, II et al. |
20110270756 | November 3, 2011 | Tullis et al. |
20110275388 | November 10, 2011 | Haney |
20110276374 | November 10, 2011 | Heiser, II et al. |
20110276474 | November 10, 2011 | Portillo |
20110313926 | December 22, 2011 | Templeton et al. |
20120005085 | January 5, 2012 | Pitroda |
20120022971 | January 26, 2012 | Morris |
20120066081 | March 15, 2012 | Shader |
20120095909 | April 19, 2012 | Resnick et al. |
20120136789 | May 31, 2012 | Kendrick et al. |
20120136790 | May 31, 2012 | Templeton et al. |
20120150605 | June 14, 2012 | Isaacson et al. |
20120246019 | September 27, 2012 | Wolfe |
20120292206 | November 22, 2012 | Casella et al. |
20120296813 | November 22, 2012 | Templeton et al. |
20120296814 | November 22, 2012 | Templeton et al. |
20120310833 | December 6, 2012 | Templeton et al. |
20130006785 | January 3, 2013 | Perkins |
20130041729 | February 14, 2013 | Shader |
20130041741 | February 14, 2013 | Shader |
20130073403 | March 21, 2013 | Tuchman |
20130144734 | June 6, 2013 | Perkins |
20130144789 | June 6, 2013 | Aaltonen et al. |
20130204925 | August 8, 2013 | McDougall et al. |
20130291127 | October 31, 2013 | Bergman et al. |
20130317923 | November 28, 2013 | Capps |
20140006191 | January 2, 2014 | Shankar et al. |
20140012648 | January 9, 2014 | Grimes |
20140012690 | January 9, 2014 | Capps |
20140019322 | January 16, 2014 | Streit et al. |
20140058837 | February 27, 2014 | Grimes |
20140115710 | April 24, 2014 | Hughes |
20140122684 | May 1, 2014 | Brentano |
20140180819 | June 26, 2014 | Grimes |
20150081565 | March 19, 2015 | Roullier et al. |
20150101062 | April 9, 2015 | Silver et al. |
20150142655 | May 21, 2015 | Ghosh et al. |
20150180736 | June 25, 2015 | Leung |
20150193873 | July 9, 2015 | Hammock et al. |
20150199725 | July 16, 2015 | Aaltonen et al. |
20150206137 | July 23, 2015 | Mazarim et al. |
20160071083 | March 10, 2016 | Apps |
20160189213 | June 30, 2016 | Gopalan et al. |
20160189229 | June 30, 2016 | Gopalan et al. |
20160189230 | June 30, 2016 | Gopalan et al. |
20160189292 | June 30, 2016 | Deshpande et al. |
20160342967 | November 24, 2016 | Proctor et al. |
20160379211 | December 29, 2016 | Hoyos et al. |
20170024731 | January 26, 2017 | Gullett et al. |
20170039551 | February 9, 2017 | Driggs et al. |
20170053276 | February 23, 2017 | Gullett et al. |
20170097996 | April 6, 2017 | Gullett et al. |
20180268396 | September 20, 2018 | Shankar et al. |
20190095989 | March 28, 2019 | Archer et al. |
1295500 | May 2009 | EP |
2001060100 | August 2001 | WO |
- International Search Report and Written Opinion for International Application No. PCT/IB2008/02235, Search Completed Apr. 23, 2009, dated May 28, 2009, 7 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US2007/012960, Search Completed Dec. 13, 2007, dated Jan. 3, 2008, 7 pgs.
- International Search Report and Written Opinion for International Application No. PCT/US2009/049956, Search Completed Aug. 24, 2009, dated Sep. 1, 2009, 6 pgs.
- Bahl, P. et.al., “RADAR: An In-Building RF-based User Location and Tracking System”, Proceedings of IEEE INFOCOM 2000, vol. 2, Tel-Aviv, Israel, Mar. 2000, pp. 775-784.
- Chintalapudi, Krishna K., “Indoor Localization Without the Pain, in Mobicom,” Association for Computing Machinery, Inc., Sep. 2010, 12 pgs.
- Duckham et al., “Location Privacy and Location-aware computing” 2005, 20 pgs.
- Eriksson, Jakob et.al. , “Cabernet: Vehicular Content Delivery Using WiFi.” MIT CSAIL MOBICOM 2008, 13 pgs.
- Fiercewireless, “Sprint offers Loopt's social mapping service”, Internet Article, [Online] Jul. 17, 2007, Retrieved from Internet at http://fiercewireless.com/story/sprint-offers-loopts-social-mapping-service/7/17/07, 1 page.
- Non-Final Office Action in U.S. Appl. No. 11/445,727, dated Jul. 25, 2008, 12 pgs.
- Non-Final Office Action in U.S. Appl. No. 11/445,729, dated Jun. 9, 2008, 12 pgs.
- Non-Final Office Action in U.S. Appl. No. 11/445,751, dated Jul. 10, 2008. 9 pgs.
- Ji, Y. et.al., “ARIADNE: A Dynamic Indoor Signal Map Construction and Localization System”, In MobiSys, 2006, 14 pgs.
- Karouia et al., “Video Similarity Measurement Based on Attributed Relational Graph Matching”, N.T. Nguyen, R. Katarzyniak (Eds.): New Challenges in Applied Intelligence Technologies, SCI 134, pp. 173-182, 2008., 2008, 10 pgs.
- LAT49, “screen capture of http://lat49.com/howitworks/index.php”, Jun. 12, 2009, 2 pgs.
- Madigan, D. et. al. , “Bayesian Indoor Positioning Systems”, In Infocom, 2005, 11 pgs.
- “Non-Final Office Action in U.S. Appl. No. 11/445,730, dated Apr. 29, 2009” 14 pgs.
- “Non-Final Office Action in U.S. Appl. No. 11/881,836, dated Jul. 23, 2009” 22 pgs.
- Schreiner, Keri, “Where We At? Mobile Phones Bring GPS to the Masses”, IEEE Computer Graphics and Applications vol. 27, No. 3, May 2007-Jun. 2007, pp. 6-11.
- secretadmirer.com, “screen capture using http://web.archive.org of http://secretAdmirer.com website”, Dec. 2, 1998, 2 pgs.
- Youssef, M. et.al., “The Horus WLAN Location Determination System”, In MobiSys, 2005, 14 pgs.
- “Method for Avoiding and Repairing Damage to Distributed Transactions in a Coordinated Resource Recovery System”, IBM Technical Disclosure Bulletin, 1991, vol. 33, Issue 10A, pp. 362-366.
Type: Grant
Filed: Apr 19, 2018
Date of Patent: Mar 2, 2021
Patent Publication Number: 20180308157
Assignee: Green Dot Corporation (Pasadena, CA)
Inventors: Steven William Streit (Pasadena, CA), Samuel Harris Altman (Mountain View, CA), Alok Deshpande (Mountain View, CA), David Kenneth Schreiber (Mountain View, CA)
Primary Examiner: Samica L Norman
Application Number: 15/957,836
International Classification: G06Q 40/00 (20120101); G06Q 40/02 (20120101);