US 9,075,979 B1Grant
Authentication based on proximity to mobile device
Issue Date:2015-07-07
•27 Claims
•6 Drawing Sheets
Abstract
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for performing multi-factor authentication. In one aspect, a method includes determining that a user has successfully completed an authentication factor, determining whether a mobile device associated with the user is proximate to a computer; and authenticating the user based on determining that the user has successfully completed the authentication factor, and that the mobile device is proximate to the computer.
Metadata
Assignee
- Google Inc.
Inventor
- Jean Baptiste Maurice Queru
Application Information
Application Number:US 13/487,745
Filing Date:2012-06-04
Priority Date:2011-08-11
Art Unit:2433
Classifications
IPC:
H04L29/06G06F21/34G06F21/35
Patent Drawings (6 sheets)
Description
Cross-Reference to Related Application
[0001] This application claims the benefit of priority of U.S. Application Ser. No. 61/522,352 filed on Aug. 11, 2011 and entitled “Authentication Based on Proximity to Mobile Device,” the entire contents of which are incorporated herein by reference.
Technical Field
[0002] This specification relates to multi-factor authentication.
Background
[0003] Multi-factor authentication is a security protocol that requires a user to confirm their identity using more than one authentication technique. Using two-factor authentication, for example, the identity of the user can be authenticated based both on something that the user knows, such as the password to a user account, and something that the user has, such as a security token.
Summary
[0004] In general, one innovative aspect of the subject matter described in this specification can be embodied in processes for authenticating the user of a computer systems, using an enhanced multi-factor authentication protocol. Under this enhanced protocol, one of the authentication factors can be satisfied when a mobile device belonging to the user is determined to be physically co-located with, or proximate to, the computer system which the user is attempting access.
[0005] Co-location with, or proximity to, the mobile device may be evidenced by geo-location information associated with the mobile device and the computer system, or may be based on the existence of a short-range connection between the mobile device and the computer system. Because the user of a mobile device may carry their mobile devices on their person throughout the course of their day, authentication based on the proximity to the mobile device may enhance the security of the user's authentication, without requiring the user to provide additional information, to carry additional security tokens, or to otherwise interact with the computer system or the mobile device.
[0006] In general, another innovative aspect of the subject matter described in this specification can be embodied in processes that include the actions of determining that a user has successfully completed an authentication factor, determining whether a mobile device associated with the user is proximate to a computer; and authenticating the user based on determining that the user has successfully completed the authentication factor, and that the mobile device is proximate to the computer.
[0007] Other embodiments of these aspects include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.
[0008] In some embodiments, determining that the mobile device associated with the user is proximate to the computer includes determining a location of the mobile device, determining a location of the computer, and determining that a distance between the location of the mobile device and the location of the computer is within a predetermined threshold; determining that the mobile device associated with the user is proximate to the computer includes determining the existence of a connection between the mobile device and the computer; the actions include determining, in response to determining that the mobile device is not proximate to the computer, that the user has successfully completed an additional authentication factor, and authenticating the user based on determining that the user has successfully completed both the authentication factor and the additional authentication factor; determining that the user has successfully completed the authentication factor includes determining that the user has successfully completed an authentication factor for gaining access to the computer; determining that the user has successfully completed the authentication factor includes determining that the user has successfully completed an authentication factor through interaction with the computer; the actions include associating the mobile device with the user, prior to determining whether the mobile device associated with the user is proximate to the computer, wherein the association is formed through user interaction with the mobile device; the actions include associating the mobile device with the user, prior to determining whether the mobile device associated with the user is proximate to the computer, wherein the association is formed through user interaction with the computer; and/or the actions include determining that the mobile device can no longer be used to authenticate any user prior to determining whether the mobile device associated with the user is proximate to the computer, and eliminating the association between the mobile device and the user.
[0009] Particular implementations of the subject matter described in this specification can be implemented so as to realize one or more of the following advantages. A user can be authenticated by merely possessing the mobile device proximate to the computer. In particular, the user need not execute an application on the mobile device or enter an access code either into the mobile device or the computer system. The mobile device and the computer system can exchange information wirelessly, negating any hard-wire connections. The mobile device need not be physically modified to prove the existence of a connection. The mobile device need be configured only once. Subsequently, it can be used as an authentication factor multiple times without requiring any physical connections or data input.
[0010] The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
Brief Description of the Drawings
[0011] FIGS. 1A and 1B illustrate systems that implement multi-factor authentication using a device proximity-based authentication factor.
[0012] FIG. 2 illustrates a user interface for receiving information to associate a mobile device with a user.
[0013] FIG. 3 is a flowchart of an example multi-factor authentication process.
[0014] FIG. 4 illustrates operations performed in a multi-factor authentication process.
[0015] Like reference numbers and designations in the various drawings indicate like elements.
Detailed Description
[0016] FIGS. 1A and 1B illustrate systems that implement multi-factor authentication using a device proximity-based authentication factor. In FIG. 1A , a computer system 100a authenticates a user 110a, who is attempting to access the computer system 100a. The computer system 100a authenticates users using multi-factor authentication, at least one factor of which is performed in coordination with a mobile device 120a.
[0017] The computer system 100a can include one or more processors and a computer-readable storage medium storing one or more computer program instructions executable by the one or more processors. The mobile device 120a can include, among other components, one or more processors (not shown) that execute computer applications. The mobile device 120a can be, for example, a personal digital assistant (PDA), a smart phone, a navigation system, a music player, tablet computer, e-book reader, a key fob, or any other type of computing device. Each of the computer system 100a and the mobile device 120a can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on each of them, which causes each of them to perform the actions.
[0018] The computer-readable storage medium of the computer system 100a stores computer software programs executable by the one or more processors to authenticate the user 110a. The user 110a is authenticated based on the user 110a successfully completing a multiple authentication factors, including an authentication factor that determines whether the mobile device 120a is proximate to the computer system 100a. Once the user is authenticated, the computer system 100a grants the user access to information, stored on the computer system 100a or accessible through the computer system 100a or both.
[0019] To determine that the user 110a has successfully completed the first authentication factor, the computer system 100a can implement a computer software application in which the computer system 100a that requests the user 110a to perform an action to gain access to the computer system 100a. If the computer system 100a determines that the user 110a has failed to successfully perform the requested action, then the computer system 100a determines that the user 110a has failed to successfully complete the first authentication factor, and denies the user 110a access to the computer system 100a.
[0020] In some implementations, to request the user 110a to perform the action, the computer system 110a can display a user interface 108a in a display device 106a coupled to the computer system 100a, and can request that the user 110a provide a user identifier (ID) and a password (PWD) in the user interface 108a. The user 110a may have previously created and stored a user account on the computer system 100a. When the computer system 100a determines that the password received in the user interface 108a is correct (for example, matches the stored password associated with the user account of the user 110a), the computer system 100a determines that the first authentication factor has been successfully completed. Thus, the first authentication factor may be based on something that the user has knowledge of, namely, the password.
[0021] After the user 110a has successfully completed the first authentication factor by interacting with the computer system 100a, the system 100a can implement a second authentication factor that may be satisfied through the user's possession of the mobile device 120a. For example, the computer system 100a can determine whether the mobile device 120a associated with the user 110a is proximate to the computer system 100a.
[0022] Once the computer 100a has determined (i) that the user 110a has successfully completed the authentication factor, and (ii) that the mobile device 120a is proximate to the computer, the user 110a may be considered to be successfully authenticated. In such a situation, the computer system 100a can grant the user 110a access to the computer system 100a.
[0023] The mobile device 120a and the computer system 100a can be configured to exchange information, for example, wirelessly, when in physical proximity to each other. As described below with reference to FIG. 2 , the user 110a can pair the mobile device 120a and the computer system 100a in a one-time operation, following which the computer system 100a can automatically recognize the mobile device 120a
[0024] Once the mobile device 120a and the computer system 100a are paired, the user 110a can successfully complete the second authentication factor by merely possessing the mobile device 120a when in physical proximity to the computer system 100. In particular, the user 110a need not modify the mobile device 120a, or manually invoke an application using the mobile device 120a, or receive a code on the mobile device 120a and provide the code to the computer system 100a, or provide any type of input to or using the mobile device 120a, or even touch the mobile device 120a during the authentication process, to successfully complete the corresponding authentication factor.
[0025] In some implementations, to determine physical proximity, the computer system 100a can determine whether a distance between the mobile device 120a and a reference location satisfies a threshold. The reference location can be the location of the computer system 100a or can alternatively be the location of a transceiver 130a that is coupled to the computer system 100a-through a wireless or wireline connection. In some implementations, the transceiver 130a can be integrated into the computer system 100a, and, in others, can be separate from the system 100a.
[0026] The computer system 100a can determine whether the mobile device 120a is within a threshold distance from the reference location based on the existence of a connection between the mobile device 120a. For example, the mobile device 120a and the computer system 100a can be paired by a Bluetooth connection. Such pairing may be possible only when the mobile device 120a is within the threshold distance from the computer system 100a. When the mobile device 120a is positioned outside the pre-defined distance location, then the Bluetooth connection cannot be established and consequently the threshold cannot be satisfied.
[0027] Upon determining that the password received through the user interface 108a is correct, the computer system 100a (or the transceiver 130a) can scan for Bluetooth compatible devices within a distance from the computer system 100a. The distance can be the range of the Bluetooth signal that the computer system 100a transmits. Beyond the range, the Bluetooth signal may be too weak to establish a connection.
[0028] When the mobile device 120a, which is Bluetooth compatible and was previously paired with the computer system 100a, is within this distance, the mobile device 120a can receive the signal and, in turn, can transmit signals to identify itself to the computer system 100a. Upon receiving the signals that the mobile device 120a transmits, the computer system 100a can determine that the mobile device 120a is proximate to the computer, and consequently that the second authentication factor has been successfully completed.
[0029] In another example, the computer system 100a can additionally determine whether the distance between the mobile device 120a and the reference location satisfies the threshold based on strength of the connection. For example, the computer system 100a can transmit a signal and a request that the mobile device 120a acknowledge receipt of the transmitted signal. The computer system 100a can be configured to determine a time taken for an acknowledgement signal to be received.
[0030] The mobile device 120a can include a transceiver configured to receive the signal that the computer system 100a transmits and to transmit an acknowledgement signal in return. When a time in which the computer system 100a receives the acknowledgement signal from the mobile device 120a satisfies a reference time threshold, the computer system 100a determines that the mobile device 120a is within a threshold distance from the computer system 100a, and that the second authentication factor has been successfully completed.
[0031] In some implementations, the computer system 100a can determine that the mobile device 120a associated with the user 110a is proximate to the computer system 100a by determining a location of the mobile device 120a, determining a location of the computer system 100a (or the reference location), and determining that a distance between the location of the mobile device and the location of the computer system 100a is within a predetermined threshold distance.
[0032] For example, the computer system 100a can receive its location and the location of the mobile device 120a from a position tracking system (such as, a Global Positioning System, or through WiFi triangulation). In general, the position tracking system can be any system that can determine locations with fine granularity, such that a difference between an actual location of an object and a determined location of the object is negligible (for example, of the order of one meter or a foot or less). In some implementations, the position tracking system can provide the location of the mobile device 120a and that of the computer system 100a to a different system (for example, a centralized server). The computer system 100a (or the centralized server) can determine that the distance between the two locations is within the predetermined threshold.
[0033] The computer system 100a can alternatively determine whether the mobile device 120a is within a threshold distance from the computer system 100a based on a difference between times registered by respective atomic clocks connected to each of the mobile device 120a and the computer system 100a. In metrology, one meter is defined as the length of the path traveled by light in vacuum in a pre-defined fraction of a second. The pre-defined fraction can be determined using an atomic clock. The computer system 100a can determine a distance between the mobile device 120a and the computer system 100a based on a time difference registered by the respective atomic clocks.
[0034] By implementing the techniques described above with reference to FIG. 1A , the computer system 100a determines that the mobile device 120a is proximate to the system 100a. Thus, the computer system 100a determines that the user 110a has successfully completed the second authentication factor based on something that the user 110a has, i.e., the mobile device 120a. Therefore, the computer system 100a successfully authenticates and grants the user 110a access, for example, to a computer software application 145a executing on the computer system 100a.
[0035] In FIG. 1B a computer system 100b authenticates a user 110b, who is attempting to access the computer system 100b. The computer system 100b authenticates users using multi-factor authentication, during which an attempt is made to perform at least one authentication factor in coordination with a mobile device 120b. Specifically, the computer system 100b requires a successful completion of a third authentication factor because the authentication factor implemented in the mobile device 120b was not successfully completed.
[0036] In FIG. 1B , the computer system 100b does not detect the presence of the mobile device 120b within the threshold distance from the reference location (i.e., the computer system 100b or the transceiver 130b). More particularly, the computer system 100b implements a computer software application in which the computer system 100b requests the user 110b to perform an action to gain access to the computer system 100b.
[0037] For example, the computer system 100b requests that the user 110b provide a correct password through the user interface 108b in a display device 106b coupled to the computer system 100b. The computer system 100b determines that the requested action was successfully performed, for example, because the computer system 100b determines that the password received through the user interface 108b matches a previously created password associated with a user account of user 110b. Therefore, the computer system 100b determines that the user 110b successfully completed the first authentication factor.
[0038] However, the computer system 100b determines that a mobile device 120b, which is required for authenticating the user, is not proximate to the computer system 100b. For example, the computer system 100b scans for Bluetooth compatible devices, particularly, for the mobile device 120b with which the computer system 100b was previously paired. Because the mobile device 120b is outside the range of the Bluetooth signal, the mobile device 120b cannot transmit signals to identify itself to the computer system 100b.
[0039] In another example, the computer system 100b transmits a signal and a request to acknowledge the signal. In one scenario, the mobile device 120b does not receive the request to acknowledge the signal and does not transmit an acknowledgement signal. In another scenario, the mobile device 100b is beyond proximity of the computer system 100b such that a time taken for the computer system 100b to receive the acknowledgement signal that the mobile device 120b transmits does not satisfy the reference time threshold.
[0040] Alternatively, or in addition, the computer system 100b can determine that the distance between the mobile device 120b and the computer system 100b is greater than the distance threshold by comparing the position information (for example, GPS information) describing its own position and the position of the mobile device 120b. Because the mobile device 120b is not proximate to the computer system 100b, the system 100b determines that a second authentication factor was not successfully completed. This can lead to two implications—the user 110b is an unauthorized user who does not have access to the computer system 100b, or the user is an otherwise authorized user who happens not to possess the mobile device 120b at that time.
[0041] In some implementations, the computer system 100b can deny the user 110b access to the computer software application 145b. In other words, the computer system 100b determines that the absence of the mobile device 120b is a strong implication that an unauthorized user is attempting to access the computer system 100b.
[0042] In other implementations, the user 110b may have forgotten the mobile device 120b at a different location, such as the user's home. In such situations, rather than denying the user 100b access to the computer system 100b, the system 100b can present the user 110b with an additional authentication factor and allow the user 110b to establish authenticity.
[0043] At least a portion of the additional authentication factor can be implemented in the mobile device 120b. In some implementations, the computer system 100b can determine if the mobile device 120b is within a pre-defined geographic area. When pairing the mobile device 120b and the computer system 100b, the user 110b may have specified the geographic area, for example, the city, state, or country in which the user 110b resides. The computer system 100b can receive location formation, for example, Global Positioning System (GPS) information from the mobile device 120b (such as a latitude/longitude pair) and determine whether the mobile device 120b is within the pre-defined geographic area.
[0044] If the computer system 100b determines that the mobile device 120b is within the pre-defined geographic area, then the computer system 100b can display a user interface 140b to the user 110b, and request the user to provide additional information to confirm the user's identity, such as through the use of a one-time password (OTP). Thus, if the computer system 100b determines that the mobile device 120b is within the pre-defined geographic area and the user provides correct identifying information in the user interface 140b, then the computer system 100b can determine that the user 110b is authorized and can grant access to the computer software application 145b. Unless both conditions are satisfied, the computer system 100b may not grant the user 110b access.
[0045] In this manner, in response to determining that the user 110b has successfully completed the first authentication factor and that the user 110b has not successfully completed the second authentication factor because the mobile device 120b is not proximate to the computer, the computer system 100b can require that the user 110b successfully complete an additional authentication factor. To do so, the one or more processors can execute computer software instructions stored on the computer-readable storage medium to implement a computer software application which requests additional information from the user 110b (for example, an additional password that the user 110b previously stored on the computer-readable storage medium).
[0046] When the computer system 100b determines that the additional information received, for example, through the user interface 140b, is correct, the computer system 100b determines that the user has successfully completed the additional authentication factor. Because the computer system 100b determines that the user has successfully completed both the first authentication factor and the additional authentication factor, the computer system 100b can authenticate the user 110b even though the mobile device 120b is not proximate to the computer.
[0047] FIG. 2 illustrates a user interface 200 for receiving information to associate a mobile device with a user. In some implementations, prior to determining whether the mobile device associated with the user is proximate to the computer system, the system can associate the mobile device with the user. The user can associate the mobile device and the computer system by providing information describing the mobile device in the user interface 200. The information can include, for example, a device identifier and a make/model of the device. In addition, the information can include time frames, for example, days of the week or times of the day (or combinations of them), within which the mobile device can be used as an authentication factor.
[0048] In some implementations, the association can be formed through user interaction with the computer system. For example, the computer system can display the user interface 200 in a display device coupled to the computer system through which the user can provide the association information. In some implementations, the computer system 200 can implement a Bluetooth pairing application to identify all Bluetooth-compatible devices, including the mobile device, which are within a range of the Bluetooth signal, and display the identified devices in the user interface 200. The user can select the mobile device from among the identified devices.
[0049] In some implementations, the association can be formed through user interaction with the mobile device. For example, the mobile device can display the user interface 200 in a display section of the mobile device. The user can interact with the user interface 200 to provide the association information. In alternative implementations, the association can be formed through user interactions with both the mobile device and the computer system.
[0050] In some implementations, the computer system can determine that the mobile device can no longer be used to authenticate any user prior to determining whether the mobile device associated with the user is proximate to the computer. For example, an authorized user may have reported that a mobile device, previously associated with the computer system as described above, has been lost. Subsequently, when the computer system detects an authentication attempt using the lost mobile device, then the computer system can deny access. Further, the computer system can eliminate the association between the mobile device and the user.
[0051] FIG. 3 is a flowchart of an example multi-factor authentication process 300. Briefly, the process 300, which be implemented as one or more computer programs that can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions of determining that a user has successfully completed an authentication factor (AF1) at 305. The process 300 can check if a mobile device is proximate to a computer (AF2) at 310. If the mobile device is proximate to the computer (decision branch “YES”), then the process 300 can authenticate the user based on successful completion of the authentication factor and based on determining that the mobile device is proximate to the computer at 315.
[0052] If, on the other hand, the mobile device is not proximate to the computer (decision branch “NO”), then the process 300 can present an additional authentication factor at 320. As described above, the additional authentication factor can include determining whether the mobile device is within a pre-defined geographic area and receiving additional authentication information from the user. The process 300 can check for successful completion of the additional authentication factor (AF3) at 325. If the additional authentication factor has been successfully completed (decision branch “YES”), then the process 300 can authenticate the user based on successful completion of AF1 and AF3 at 330. If not (decision branch “NO”), then the process 300 can determine authentication failure at 335.
[0053] FIG. 4 illustrates operations performed in a multi-factor authentication process. A user 402 requests access to a computer system 400. In response, the computer system 400 initiates a multi-factor authentication process. Initially, the computer system 400 requests information that only an authenticated user will know. The user 402 provides information in response to the request. When the computer system 400 verifies that the received information is accurate, the computer system 400 determines that a first authentication factor was successfully completed.
[0054] The computer system 400 searches for a device (mobile device 404, in this example) that only an authenticated user will possess. When the mobile device 404 is proximate to the computer system 400, the device 404 receives the request for identification signals from the computer system 400. In some implementations, upon receiving the request, one or more processors included in the mobile device 404 can execute computer software applications stored on a computer-readable storage medium included in the device 404 to execute a computer software application.
[0055] In response to receiving the request, the application can present a notification indicating receipt of the request. For example, the application can display a message on a display screen of the mobile device 404, execute an instruction to emit a sound or to vibrate or combinations of them. Such a notification may alert the user 402 that the mobile device 404 has received a request from the computer system 400. Alternatively, such notification may not be necessary. Instead, the application may cause the mobile device 404 to transmit signals to the computer system 400 in response to receiving the request.
[0056] The computer system 400 receives the signals that the mobile device 404 transmits, and verifies that the received signals establish that the mobile device 404 is in physical proximity to the computer system 400. In this manner, when the computer system 400 verifies that the mobile device 404 is proximate to the computer system, the system 400 authenticates the user 402 and grants access. The authenticated user 402 can then access one or more applications executed by the computer system 400.
[0057] In some implementations, the computer system can first implement the authentication factor that is based on possession of the mobile device, and then implement the authentication factor based on knowledge of the password. In such implementations, the computer system can first determine that the mobile device is proximate to the computer system. Then, the computer system can display the user interface in the display device of the computer system, and request that the user provide the user identifier and password. If the computer system determines that the mobile device is not proximate to the computer system by implementing the techniques described above, the computer system can deny the user access to the computer system and not display the user interface. Alternatively, the computer system can implement an additional authentication factor as described above, and display the user interface if the user successfully completes the additional authentication factor.
[0058] In some implementations, the computer system can be a node of a centralized network and can be coupled to a centralized server. The user may be authorized to access the centralized server only through the computer system. In such implementations, the server can store an association between the computer system and the mobile device. When the user attempts to access the network, the server can implement the authentication factors described above to determine that the user is attempting to do so through the computer system.
[0059] In some situations, the mobile device can be associated with more than one computer system to access the centralized server. Conversely, more than one mobile device can be associated with the computer system to access the computer system or the server or both.
[0060] Implementations of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, for example, a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus.
[0061] A computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them. Moreover, while a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination of computer program instructions encoded in an artificially generated propagated signal. The computer storage medium can also be, or be included in, one or more separate physical components or media (for example, multiple CDs, disks, or other storage devices).
[0062] The operations described in this specification can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources. For example, the mobile device can include one or more computer-readable storage devices that store the computer software instructions. The mobile device can further include one or more data processing apparatuses that can read the computer software instructions from the computer-readable storage devices and execute them.
[0063] The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the them. The apparatus can include special purpose logic circuitry, for example, an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
[0064] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program can, but need not, correspond to a file in a file system. A program can be stored in a portion of a file, in a single file dedicated to the program in question, or in multiple coordinated files (for example, files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
[0065] The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, for example, an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
[0066] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, for example, magnetic, magneto-optical disks, or optical disks.
[0067] However, a computer need not have such devices. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (for example, a universal serial bus (USB) flash drive), to name just a few.
[0068] Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, for example, EPROM, EEPROM, and flash memory devices; magnetic disks, for example, internal hard disks or removable disks; magneto-optical disks; and SD cards, CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
[0069] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any disclosures or of what can be claimed, but rather as descriptions of features specific to particular implementations of particular disclosures. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features can be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination can be directed to a subcombination or variation of a subcombination.
[0070] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing can be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
[0071] Thus, particular implementations of the subject matter have been described. Other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing can be advantageous.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A computer-readable storage medium storing computer software instructions executable by one or more data processing apparatus which, upon such execution, cause the one or more data processing apparatus to perform operations comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
receiving position data that includes (i) first GPS position data that specifies a position of a mobile computing device associated with the user, and (ii) second GPS position data that specifies a position of the computer system;
determining a distance between the position of the mobile computing device specified by the first GPS position data and the position of the computer system specified by the second GPS position data;
determining that the distance does not exceed a maximum threshold distance;
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor, and
(ii) the determined distance does not exceed the maximum threshold distance; and
in response to authenticating the user, providing the user access to a second user interface of the computer system.
2. The medium of claim 1, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
3. The medium of claim 1, comprising forming an association between the mobile computing device and the user prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
4. The medium of claim 3, wherein the association is formed through user interaction with the computer system.
5. The medium of claim 3, further comprising:
determining that the mobile computing device is no longer to be used to authenticate the user for access to the computer system; and
eliminating the association between the mobile computing device and the user based on determining that the mobile computing device is no longer to be used to authenticate the user for access to the computer system.
6. The medium of claim 5, wherein determining that the mobile computing device is no longer to be used to authenticate the user for access to the computer system comprises determining that the mobile computing device has been reported lost.
7. The medium of claim 3, comprising:
establishing a short-range wireless connection between the mobile computing device and the computer system,
communicating with the mobile computing device over the short-range wireless connection to determine an identity of the mobile computing device, and
confirming the association between the mobile computing device and the user based on the identity of the mobile computing device.
8. The medium of claim 7, wherein authenticating the user is further based on determining that a short-range wireless connection exists between the mobile computing device and the computer system; and
wherein determining that the short-range wireless connection exists between the mobile computing device and the computer system is performed in response to receiving the user input.
9. The medium of claim 1, wherein the user input is a username and password associated with a user account belonging to the user.
10. A system comprising:
one or more computers; and
a computer-readable storage medium storing computer software instructions executable by the one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
accessing data specifying predetermined days or times when a mobile computing device is permitted to be used in authenticating the user;
determining that a current day or a current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user;
receiving position data that specifies (i) a position of the mobile computing device associated with the user, and (ii) a position of the computer system;
determining a distance between the position of the mobile computing device and the position of the computer system;
determining that the distance does not exceed a maximum threshold distance; and
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor,
(ii) the current day or the current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user, and
(iii) the determined distance does not exceed the maximum threshold distance.
11. The system of claim 10, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
12. The system of claim 10, comprising forming an association between the mobile computing device and the user prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
13. The system of claim 12, wherein the association is formed through user interaction with the computer system.
14. The system of claim 12, further comprising:
determining that the mobile computing device is no longer to be used to authenticate the user for access to the computer system; and
eliminating the association between the mobile computing device and the user based on determining that the mobile computing device is no longer to be used to authenticate the user for access to the computer system.
15. The system of claim 12, comprising:
establishing a short-range wireless connection between the mobile computing device and the computer system,
communicating with the mobile computing device over the short-range wireless connection to determine an identity of the mobile computing device, and
confirming the association between the mobile computing device and the user based on the identity of the mobile computing device.
16. A computer-implemented method comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
receiving position data that includes (i) first GPS position data that specifies a position of a mobile computing device associated with the user, and (ii) second GPS position data that specifies a position of the computer system;
determining a distance between the position of the mobile computing device specified by the first GPS position data and the position of the computer system specified by the second GPS position data;
determining that the distance does not exceed a maximum threshold distance;
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor, and
(ii) the determined distance does not exceed the maximum threshold distance; and in response to authenticating the user, providing the user access to a second user interface of the computer system.
17. The method of claim 16, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
18. The method of claim 16, comprising forming an association between the mobile computing device and the user, the association being formed prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
19. A system comprising:
one or more computers; and
a computer-readable storage medium storing computer software instructions executable by the one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
receiving position data that includes (i) first GPS position data that specifies a position of a mobile computing device associated with the user, and (ii) second GPS position data that specifies a position of the computer system;
determining a distance between the position of the mobile computing device specified by the first GPS position data and the position of the computer system specified by the second GPS position data;
determining that the distance does not exceed a maximum threshold distance;
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor, and
(ii) the determined distance does not exceed the maximum threshold distance; and
in response to authenticating the user, providing the user access to a second user interface of the computer system.
20. The system of claim 19, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
21. The system of claim 19, comprising forming an association between the mobile computing device and the user, the association being formed prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
22. A computer-implemented method comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
accessing data specifying predetermined days or times when a mobile computing device is permitted to be used in authenticating the user;
determining that a current day or a current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user;
receiving position data that specifies (i) a position of the mobile computing device associated with the user, and (ii) a position of the computer system;
determining a distance between the position of the mobile computing device and the position of the computer system;
determining that the distance does not exceed a maximum threshold distance; and
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor,
(ii) the current day or the current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user, and
(iii) the determined distance does not exceed the maximum threshold distance.
23. The method of claim 22, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
24. The method of claim 22, comprising forming an association between the mobile computing device and the user based on user input that designates the specific mobile computing device as belonging to the user, the association being formed prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
25. A computer-readable storage medium storing computer software instructions executable by one or more data processing apparatus which, upon such execution, cause the one or more data processing apparatus to perform operations comprising:
receiving, at a computer system, user input entered by a user through a user interface of the computer system;
determining, based on the user input, that the user has successfully completed an authentication factor for gaining access to the computer system;
accessing data specifying predetermined days or times when a mobile computing device is permitted to be used in authenticating the user;
determining that a current day or a current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user;
receiving position data that specifies (i) a position of the mobile computing device associated with the user, and (ii) a position of the computer system;
determining a distance between the position of the mobile computing device and the position of the computer system;
determining that the distance does not exceed a maximum threshold distance; and
authenticating, by the computer system, the user for the access to the computer system based at least on determining that:
(i) the user has successfully completed the authentication factor,
(ii) the current day or the current time is within one of the predetermined days or times when the mobile computing device is permitted to be used to authenticate the user, and
(iii) the determined distance does not exceed the maximum threshold distance.
26. The medium of claim 25, wherein authenticating the user is further based on determining the existence of a connection between the mobile computing device and the computer system.
27. The medium of claim 25, comprising forming an association between the mobile computing device and the user, the association being formed prior to determining that the user has successfully completed the authentication factor for gaining access to the computer system.
Patent Citations (184)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5463768(A) | 1995-10-01 | Cudihy et al. | Applicant |
| US5655081(A) | 1997-08-01 | Bonnell et al. | Applicant |
| US5778444(A) | 1998-07-01 | Langan et al. | Applicant |
| US5794224(A) | 1998-08-01 | Yufik | Applicant |
| US6148368(A) | 2000-11-01 | DeKoning | Applicant |
| US6178482(B1) | 2001-01-01 | Sollars | Applicant |
| US6449671(B1) | 2002-09-01 | Patkar et al. | Applicant |
| US6490651(B1) | 2002-12-01 | Shats | Applicant |
| US6505211(B1) | 2003-01-01 | Dessloch et al. | Applicant |
| US6505248(B1) | 2003-01-01 | Casper et al. | Applicant |
| US6587866(B1) | 2003-07-01 | Modi et al. | Applicant |
| US6598179(B1) | 2003-07-01 | Chirashnya et al. | Applicant |
| US6643613(B2) | 2003-11-01 | McGee et al. | Applicant |
| US6829678(B1) | 2004-12-01 | Sawdon et al. | Applicant |
| US6891839(B2) | 2005-05-01 | Albert et al. | Applicant |
| US6898697(B1) | 2005-05-01 | Gao et al. | Applicant |
| US6996502(B2) | 2006-02-01 | De La Cruz et al. | Applicant |
| US7043455(B1) | 2006-05-01 | Cuomo et al. | Applicant |
| US7062718(B2) | 2006-06-01 | Kodosky et al. | Applicant |
| US7117243(B2) | 2006-10-01 | Peart | Applicant |
| US7356679(B1) | 2008-04-01 | Le et al. | Applicant |
| US7466703(B1) | 2008-12-01 | Arunachalam et al. | Applicant |
| US7478388(B1) | 2009-01-01 | Chen et al. | Applicant |
| US7500262(B1) | 2009-03-01 | Sanin et al. | Applicant |
| US7529836(B1) | 2009-05-01 | Bolen et al. | Applicant |
| US7584467(B2) | 2009-09-01 | Wickham et al. | Applicant |
| US7596620(B1) | 2009-09-01 | Colton et al. | Applicant |
| US7600676(B1) | 2009-10-01 | Rados et al. | Applicant |
| US7650331(B1) | 2010-01-01 | Dean et al. | Applicant |
| US7653833(B1) | 2010-01-01 | Miller et al. | Applicant |
| US7761573(B2) | 2010-07-01 | Travostino et al. | Applicant |
| US7804862(B1) | 2010-09-01 | Olson et al. | Applicant |
| US7836285(B2) | 2010-11-01 | Giri et al. | Applicant |
| US7979899(B2) | 2011-07-01 | Guo et al. | Applicant |
| US8051414(B2) | 2011-11-01 | Stender et al. | Applicant |
| US8065717(B2) | 2011-11-01 | Band | Applicant |
| US8103771(B2) | 2012-01-01 | Tanaka et al. | Applicant |
| US8108903(B2) | 2012-01-01 | Norefors et al. | Applicant |
| US8127295(B1) | 2012-02-01 | Jones et al. | Applicant |
| US8146147(B2) | 2012-03-01 | Litvin et al. | Applicant |
| US8219777(B2) | 2012-07-01 | Jacobson et al. | Applicant |
| US8261295(B1) | 2012-09-01 | Risbood et al. | Applicant |
| US8276140(B1) | 2012-09-01 | Beda, III et al. | Applicant |
| US8286227(B1) | 2012-10-01 | Zheng | Applicant |
| US8296459(B1) | 2012-10-01 | Brandwine et al. | Applicant |
| US8307406(B1) | 2012-11-01 | Aboujaoude | Applicant |
| US8468535(B1) | 2013-06-01 | Keagy et al. | Applicant |
| US8484353(B1) | 2013-07-01 | Johnson et al. | Applicant |
| US8504844(B2) | 2013-08-01 | Browning | Applicant |
| US8533796(B1) | 2013-09-01 | Shenoy et al. | Applicant |
| US8601602(B1) | 2013-12-01 | Zheng | Applicant |
| US8621005(B2) | 2013-12-01 | Boyd et al. | Applicant |
| US2002/0091902(A1) | 2002-07-01 | Hirofuji | Applicant |
| US2002/0097747(A1) | 2002-07-01 | Kirkby | Applicant |
| US2003/0046589(A1) | 2003-03-01 | Gregg | Applicant |
| US2004/0068637(A1) | 2004-04-01 | Nelson et al. | Applicant |
| US2004/0139368(A1) | 2004-07-01 | Austen et al. | Applicant |
| US2004/0148484(A1) | 2004-07-01 | Watanabe et al. | Applicant |
| US2004/0203595(A1) | 2004-10-01 | Singhal | Examiner |
| US2004/0210653(A1) | 2004-10-01 | Kanoor et al. | Applicant |
| US2005/0010715(A1) | 2005-01-01 | Davies et al. | Applicant |
| US2005/0044393(A1) | 2005-02-01 | Holdsworth | Applicant |
| US2005/0166011(A1) | 2005-07-01 | Burnett et al. | Applicant |
| US2005/0196030(A1) | 2005-09-01 | Schofield et al. | Applicant |
| US2005/0216659(A1) | 2005-09-01 | Ogawa et al. | Applicant |
| US2005/0237543(A1) | 2005-10-01 | Kikuchi | Applicant |
| US2005/0268107(A1) | 2005-12-01 | Harris et al. | Examiner |
| US2005/0269401(A1) | 2005-12-01 | Spitzer et al. | Examiner |
| US2005/0289499(A1) | 2005-12-01 | Ogawa et al. | Applicant |
| US2006/0026354(A1) | 2006-02-01 | Lesot et al. | Applicant |
| US2006/0048077(A1) | 2006-03-01 | Boyles | Applicant |
| US2006/0048130(A1) | 2006-03-01 | Napier et al. | Applicant |
| US2006/0059228(A1) | 2006-03-01 | Kasamsetty et al. | Applicant |
| US2006/0067236(A1) | 2006-03-01 | Gupta | Applicant |
| US2006/0075199(A1) | 2006-04-01 | Kallahalla et al. | Applicant |
| US2006/0083208(A1) | 2006-04-01 | Lin | Examiner |
| US2006/0098618(A1) | 2006-05-01 | Bouffioux | Applicant |
| US2006/0136676(A1) | 2006-06-01 | Park et al. | Applicant |
| US2006/0153099(A1) | 2006-07-01 | Feldman | Applicant |
| US2006/0161753(A1) | 2006-07-01 | Aschoff et al. | Applicant |
| US2006/0235795(A1) | 2006-10-01 | Johnson et al. | Applicant |
| US2006/0271547(A1) | 2006-11-01 | Chen et al. | Applicant |
| US2007/0011361(A1) | 2007-01-01 | Okada et al. | Applicant |
| US2007/0061590(A1) | 2007-03-01 | Boye et al. | Applicant |
| US2007/0112956(A1) | 2007-05-01 | Chapman et al. | Applicant |
| US2007/0118694(A1) | 2007-05-01 | Watanabe et al. | Applicant |
| US2007/0123276(A1) | 2007-05-01 | Parker et al. | Applicant |
| US2007/0177198(A1) | 2007-08-01 | Miyata | Applicant |
| US2007/0199058(A1) | 2007-08-01 | Baumgart et al. | Applicant |
| US2007/0271604(A1) | 2007-11-01 | Webster et al. | Applicant |
| US2007/0280243(A1) | 2007-12-01 | Wray et al. | Applicant |
| US2007/0288921(A1) | 2007-12-01 | King et al. | Applicant |
| US2008/0028389(A1) | 2008-01-01 | Genty et al. | Applicant |
| US2008/0086515(A1) | 2008-04-01 | Bai et al. | Applicant |
| US2008/0095176(A1) | 2008-04-01 | Ong et al. | Applicant |
| US2008/0107112(A1) | 2008-05-01 | Kuo et al. | Applicant |
| US2008/0205415(A1) | 2008-08-01 | Morales | Applicant |
| US2008/0208681(A1) | 2008-08-01 | Hammad et al. | Applicant |
| US2008/0215796(A1) | 2008-09-01 | Lam et al. | Applicant |
| US2008/0222246(A1) | 2008-09-01 | Ebling et al. | Applicant |
| US2008/0222375(A1) | 2008-09-01 | Kotsovinos et al. | Applicant |
| US2008/0244030(A1) | 2008-10-01 | Leitheiser | Applicant |
| US2008/0244471(A1) | 2008-10-01 | Killian et al. | Applicant |
| US2008/0250147(A1) | 2008-10-01 | Knibbeler et al. | Examiner |
| US2008/0250407(A1) | 2008-10-01 | Dadhia et al. | Applicant |
| US2008/0270704(A1) | 2008-10-01 | He et al. | Applicant |
| US2008/0289030(A1) | 2008-11-01 | Poplett | Examiner |
| US2008/0304516(A1) | 2008-12-01 | Feng et al. | Applicant |
| US2008/0307258(A1) | 2008-12-01 | Challenger et al. | Applicant |
| US2008/0310324(A1) | 2008-12-01 | Chaponniere | Applicant |
| US2009/0025074(A1) | 2009-01-01 | Le Saint et al. | Applicant |
| US2009/0097657(A1) | 2009-04-01 | Scheidt et al. | Applicant |
| US2009/0150629(A1) | 2009-06-01 | Noguchi et al. | Applicant |
| US2009/0199177(A1) | 2009-08-01 | Edwards et al. | Applicant |
| US2009/0222815(A1) | 2009-09-01 | Dake | Applicant |
| US2009/0235358(A1) | 2009-09-01 | Tolba | Applicant |
| US2009/0240744(A1) | 2009-09-01 | Thomson et al. | Applicant |
| US2009/0241108(A1) | 2009-09-01 | Edwards et al. | Applicant |
| US2009/0249440(A1) | 2009-10-01 | Platt et al. | Applicant |
| US2009/0276771(A1) | 2009-11-01 | Nickolov et al. | Applicant |
| US2009/0282266(A1) | 2009-11-01 | Fries et al. | Applicant |
| US2009/0300605(A1) | 2009-12-01 | Edwards et al. | Applicant |
| US2009/0300641(A1) | 2009-12-01 | Friedman et al. | Applicant |
| US2009/0310554(A1) | 2009-12-01 | Sun et al. | Applicant |
| US2010/0017859(A1) | 2010-01-01 | Kelly | Applicant |
| US2010/0023582(A1) | 2010-01-01 | Pedersen et al. | Applicant |
| US2010/0031345(A1) | 2010-02-01 | Sinclair | Examiner |
| US2010/0046426(A1) | 2010-02-01 | Shenoy et al. | Applicant |
| US2010/0057913(A1) | 2010-03-01 | DeHaan | Applicant |
| US2010/0063895(A1) | 2010-03-01 | Dominguez et al. | Applicant |
| US2010/0071035(A1) | 2010-03-01 | Budko et al. | Applicant |
| US2010/0088335(A1) | 2010-04-01 | Mimatsu | Applicant |
| US2010/0095000(A1) | 2010-04-01 | Kettler et al. | Applicant |
| US2010/0199089(A1) | 2010-08-01 | Vysogorets et al. | Applicant |
| US2010/0212004(A1) | 2010-08-01 | Fu | Applicant |
| US2010/0215050(A1) | 2010-08-01 | Kanada | Applicant |
| US2010/0217927(A1) | 2010-08-01 | Song | Applicant |
| US2010/0235649(A1) | 2010-09-01 | Jeffries et al. | Applicant |
| US2010/0274984(A1) | 2010-10-01 | Inomata et al. | Applicant |
| US2010/0287548(A1) | 2010-11-01 | Zhou et al. | Applicant |
| US2010/0293285(A1) | 2010-11-01 | Oishi et al. | Applicant |
| US2010/0303241(A1) | 2010-12-01 | Breyel | Applicant |
| US2011/0010483(A1) | 2011-01-01 | Liljeberg | Applicant |
| US2011/0022812(A1) | 2011-01-01 | van Der Linden et al. | Applicant |
| US2011/0055361(A1) | 2011-03-01 | DeHaan | Applicant |
| US2011/0060882(A1) | 2011-03-01 | Efstathopoulos | Applicant |
| US2011/0078363(A1) | 2011-03-01 | Yeh et al. | Applicant |
| US2011/0085563(A1) | 2011-04-01 | Kotha et al. | Applicant |
| US2011/0103389(A1) | 2011-05-01 | Kidambi et al. | Applicant |
| US2011/0153697(A1) | 2011-06-01 | Nickolov et al. | Applicant |
| US2011/0153838(A1) | 2011-06-01 | Belkine et al. | Applicant |
| US2011/0179412(A1) | 2011-07-01 | Nakae et al. | Applicant |
| US2011/0191485(A1) | 2011-08-01 | Umbehocker | Applicant |
| US2011/0191768(A1) | 2011-08-01 | Smith | Applicant |
| US2011/0197024(A1) | 2011-08-01 | Thomas | Applicant |
| US2011/0231280(A1) | 2011-09-01 | Farah | Applicant |
| US2011/0246767(A1) | 2011-10-01 | Chatuvedi et al. | Applicant |
| US2011/0258441(A1) | 2011-10-01 | Ashok et al. | Applicant |
| US2011/0296157(A1) | 2011-12-01 | Konetski et al. | Applicant |
| US2011/0302400(A1) | 2011-12-01 | Maino et al. | Applicant |
| US2011/0302415(A1) | 2011-12-01 | Ahmad et al. | Applicant |
| US2012/0060018(A1) | 2012-03-01 | Shinde et al. | Applicant |
| US2012/0063458(A1) | 2012-03-01 | Klink et al. | Applicant |
| US2012/0066749(A1) | 2012-03-01 | Taugbol et al. | Examiner |
| US2012/0084570(A1) | 2012-04-01 | Kuzin et al. | Applicant |
| US2012/0084768(A1) | 2012-04-01 | Ashok et al. | Applicant |
| US2012/0089981(A1) | 2012-04-01 | Tripathi et al. | Applicant |
| US2012/0159634(A1) | 2012-06-01 | Haikney et al. | Applicant |
| US2012/0173866(A1) | 2012-07-01 | Ashok et al. | Applicant |
| US2012/0179796(A1) | 2012-07-01 | Nagaraj et al. | Applicant |
| US2012/0185688(A1) | 2012-07-01 | Thornton et al. | Applicant |
| US2012/0191912(A1) | 2012-07-01 | Kadatch et al. | Applicant |
| US2012/0233678(A1) | 2012-09-01 | Pal | Applicant |
| US2012/0233705(A1) | 2012-09-01 | Boysen et al. | Applicant |
| US2012/0246637(A1) | 2012-09-01 | Kreeger et al. | Applicant |
| US2012/0266159(A1) | 2012-10-01 | Risbood et al. | Applicant |
| US2013/0074181(A1) | 2013-03-01 | Singh | Applicant |
| US2013/0081014(A1) | 2013-03-01 | Kadatch et al. | Applicant |
| US2013/0117801(A1) | 2013-05-01 | Shieh et al. | Applicant |
| US2013/0212709(A1) | 2013-08-01 | Tucker | Applicant |
| US2013/0227303(A1) | 2013-08-01 | Kadatch et al. | Applicant |
| US2013/0262405(A1) | 2013-10-01 | Kadatch et al. | Applicant |
| US2013/0276068(A1) | 2013-10-01 | Alwar | Applicant |
| WO2011/095516 | 2011-08-01 | Applicant |
Non-Patent Literature (64)
- Jansen et al., (“Proximity-based Authentication for Mobile Devices”), Proceedings fo the 2005 International Conference on Security and Management, pp. 398-404, Jun. 20, 2005.Examiner
- Jaros et al., (“A New Approach in a Multifactor Authentication and Location-based Authorization”), ICIMP 2011: The Sixth International Conference on Internet Monitoring and Protection, pp. 50-53, Mar. 20, 2011.Examiner
- Bertino et al., (“Location-Aware Authentication and Access Control—Concepts and Issues”), 2009 International Conference on Advanced Information Networking and Applications, 2009, pp. 10-15.Examiner
- Office Action dated Dec. 29, 2011 for U.S. Appl. No. 13/249,329. 33 pages.Applicant
- Notice of Allowance issued in U.S. Appl. No. 13/249,329 on Jun. 12, 2012, 21 pages.Applicant
- Office Action dated Aug. 14, 2012 for U.S. Appl. No. 12/872,111, 25 pages.Applicant
- Office Action issued in U.S. Appl. No. 12/872,111 on Feb. 28, 2013, 20 pages.Applicant
- Office Action issued in U.S. Appl. No. 13/613,841 on Mar. 12, 2014, 17 pages.Applicant
- Moller, Jan, et al., “Internal Network Security”, Feb. 1, 2000-May 18, 2001, Retrieved from the Internet: <URL: http://www.daimi.au.dk/˜fwiffo/thesis/>, 183 pages.Applicant
- Primet, Pascale, et al . . . , “HIPCAL: State of the Art of OS and Network virtualization solutions for Grids”, Sep. 14, 2007, 38 pages.Applicant
- Wikipedia, “IPSec”, [online] [retrieved on Apr. 1, 2011]. Retrieved from the Internet: <URL: http://en.wikipedia.org/wiki/IPsec/>, 8 pages.Applicant
- Abdull, AlastairIrvine, et al. “Generic Routing Encapsulation”, [online] [retrieved on Apr. 1, 2011]. Retrieved from the Internet: <URL: http:/ / creativecommons. org/ licenses/ by-sa/ 3. 0/>, 5 pages.Applicant
- Farinacci et al., “RFC 2784: Generic Routing Encapsulation (GRE)”, Mar. 2000, The Internet Society, 10 pages.Applicant
- Kent et al., “RFC 4301: Security Architecture for the Internet Protocol”, Dec. 2005, The Internet Society, 102 pages.Applicant
- Wikipedia, “Domain Name System”. [online] [Retrieved on Apr. 2, 2012]. Retrieved from the Internet: <URL: http://en.wikipedia.org/wiki/Domain—Name—System>, 13 pages.Applicant
- Bucket Explorer. “What is my AWS Access and Secret Key.” [Retrieved Apr. 26, 2011]. Retrieved from the Internet <URL: http://www.bucketexplorer.com/documentation/amazon-s3—what-is-my-aws-access-and-secret-key.html>, 1 page.Applicant
- Hongkiat. “Amazon S3—The Beginner's Guide.” [Retrieved on Apr. 26, 2011]. Retrieved from the Internet <URL: http://www.hongkiat.com/blog/amazon-s3-the-beginners-guide/>, 9 pages.Applicant
- Myerson, Judith. “Creating Applications with Amazon EC2 and S3.” O'ReillyOnLamp.com, May 13, 2008 [Retrieved on Apr. 26, 2011]. Retrieved from the Internet <URL: http://onlamp.com/pub/a/onlamp/2008/05/13/creating-applications-with-amazon-ec2-and-s3.html>, 8 pages.Applicant
- Wikipedia. “OAuth.” [online] [Retrieved on Jan. 20, 2011]. Retrieved from the Internet <URL: http://en.wikipedia.org/wiki/OAuth> , 3 pages.Applicant
- Gowalla. “API Documentation—Oauth.” [Retrieved on Apr. 26, 2011]. Retrieved from the Internet <URL: http://gowalla.com/api/docs/oauth>, 4 pages.Applicant
- Apache HTTP Server Version 2.0. “Log Files.” [Retrieved on Feb. 15, 2011]. Retrieved from the Internet <URL: http://httpd.apache.org/docs/2.0/logs.html>, 7 pages.Applicant
- Microsoft Support. “How to view and manage event logs in Event Viewer in Windows XP.” May 7, 2007, version 3.5 [Retrieved on Feb. 15, 2011]. Retrieved from the Internet <URL: http://support.microsoft.com/kb/308427>, 6 pages.Applicant
- MSDN. “Visual Basic Concepts, Visual Studio 6.0: Centralized Error Handling.” [Retrieved on Feb. 15, 2011]. Retrieved from the Internet <URL: http://msdn.microsoft.com/en-us/library/aa240795(d=printer, v=vs.60).aspx>, 4 pages.Applicant
- Laitinen, Aapo et al., Network Address Translation [Retrieved on Oct. 10, 2011] Retrieved from the Internet: <URL: http://en.wikipedia.org/wiki/Networkpages—Address—and Port—Translation>, 11 pages.Applicant
- Wikipedia., Anycast [Retrieved on Oct. 10, 2011] Retrieved from the Internet: URL<http://en.wikipedia.org/wiki/Anycast>, 5 pages.Applicant
- VMCI Overview [Retrieved on Jun. 8, 2011] Retrieved from the Internet: <URL: http://pubs.vmware.com/vmci-sdk/VMCI—intro.html>, 3 pages.Applicant
- VMware vSphere [Retrieved on Jun. 8, 2011] Retrieved from the Internet: <URL: http://www.vmware.com/products/vmotion/overview.html>, 2 pages.Applicant
- Travostino, Franco, et al., Seamless Live Migration of Virtual Machines over the MAN/WAN, 2006, Elsevier Future Generation Computer Systems 2006, 10 pages.Applicant
- VMCI Datagram API [Retrieved on Jun. 8, 2011], Retrieved from the Internet: <URL: http://pubs.vmware.com/vmci-sdk/datagram.html>, 1 page.Applicant
- VMCI Datagram—SendTo [Retrieved on Jun. 8, 2011], Retrieved from the Internet: <URL: http://pubs.vmware.com/vmci-sdk/functionsNMCIDatagram—SendTo.html>, 1 page.Applicant
- VMCIDs—Lookup [Retrieved on Jun. 8, 2011], Retrieved from the Internet: <URL: http://pubs.vmware.com/vmci-sdk/functionsNMCIDs—Lookup.html>, 2 pages.Applicant
- Chen, Per M., et al., : “Maximizing Performance in a Striped Disk Array”, 17th Annual International Symposium on Computer Architecture (SIGARCH 1990), 18 pages.Applicant
- Sarhan, Nabil J., et al., “Caching and Scheduling in NAD-Based Multimedia Servers”; IEEE Computer Society, IEEE Transactions on Parallel and Distributed Systems, vol. 15, No. 10, Oct. 2004; pp. 921-933.Applicant
- Vazhkudai, Sudharshan S., et al.; “Constructing Collaborative Desktop Storage Caches for Large Scientific Datasets”; ACM Journal Name, vol. V, No. N, Jun. 2006, 34 pages.Applicant
- OMG, Deployment and Configuration of Component-based Distributed Applications Specification—Version 4.0, OMG, 2006, pp. 1-160.Applicant
- Cala et al., “Automatic Software Deployment in the Azure Cloud”, IFIP International Federation for Information Processing, 2010, pp. 1-14.Applicant
- RSA Laboratories, “PKCS #11 v2.20: Cryptographic Token Interface Standard,” Jun. 28, 2004, RSA Security Inc. (407 pages).Applicant
- Amazon Auto Scaling—Getting Started Guide—API Version Aug. 1, 2010. Amazon Web Services LLC, 2010, 20 pages.Applicant
- Amazon Auto Scaling—Developer Guide—API Version Aug. 1, 2010. Amazon Web Services LLC, 2011, 62 pages.Applicant
- Amazon CloudWatch—Developer Guide—API Version Aug. 1, 2010. Amazon Web Services LLC, 2010, 75 pages.Applicant
- Benincosa. “Ganglia and Nagios, Part 2: Monitor enterprise clusters with Nagios-Install Nagios to effectively monitor a data center; make Ganglia and Nagios work together,” 2009, 20 pages.Applicant
- ‘Nagios’ [online]. “Monitoring Linux/Unix Machines,” 2011, [retrieved on Feb. 3, 2011]. Retrieved from the Internet: URL: <http://nagios.sourceforge.net/docs/3—0/monitoring-linux.html > 1 page.Applicant
- ‘Nagios’ [online]. “Nagios Plugins,” 2011, [retrieved on Feb. 3, 2011]. Retrieved from the Internet: URL: <http://nagios.sourceforge.net/docs/3—0/plugins.html > 2 pages.Applicant
- ‘Zabbix’ [online]. “Zabbix 1.8: The Ultimate Open Source Monitoring Solution,” 2001-2012, [retrieved on Feb. 3, 2011]. Retrieved from the Internet: URL: <http://www.zabbix.com/features.php.> 1 page.Applicant
- Amazon Elastic Compute Cloud, User Guide, API Version Mar. 1, 2012, pp. 97-103, downloaded from http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html?r=4276 on Mar. 18, 2012.Applicant
- Paravirtualization, Wikipedia Article, downloaded from http://en.wikipedia.org/wiki/Paravirtualization on Mar. 18, 2012.Applicant
- Paravirtualized File Systems, Eric Van Hensbergen, downloaded from http://www.slideshare.net/ericvh/9p-on-kvm on Mar. 18, 2012.Applicant
- “Generic Routing Encapsulation”. Creativecommons.org [online]. Creative Commons Attribution-Share Alike 3.0 Unported. [retrieved on Jan. 14, 2011]. Retrieved from the Internet:<URL: http://creativecommons.org/licenses/by-sa/3.0/ >, pp. 1-5.Applicant
- Cloud Computing Course, Part 2: Amazon's EC2, Marcel Gagne, Jun. 13, 2011. Retrieved from the Internet: <URL: http://marcelgagne.com/content/cloud-computing-course-part-2-amazons-ec2>, 6 pages.Applicant
- How to: Getting Started With Amazon EC2, Paul Stamatiou, Apr. 5, 2008. Retrieved from the Internet: <URL:http//paulstamatiou.com/how-to-getting-started-with-amazon-ec2>, 25 pages.Applicant
- Uploading Personal ssh Keys to Amazon EC2, Eric Hammond, Oct. 14, 2010. Retrieved from the Internet: <URL:http://alestic.com/2010/10/ec2-ssh-keys>, 3 pages.Applicant
- Key Management in Cloud Datacenters, Security Stackexchange.com, Retrieved from the Internet on Nov. 18, 2011; Retrieved from: <URL: http://security.stackexchange.com/questions/2514/key-management-in-cloud-datacenters>, 2 pages.Applicant
- Managing Amazon EC2—SSH Login and Protecting Your Instances, Everyday's Findings, Monday, May 18, 2009, Retrieved from the Internet on Nov. 18, 2011; Retrieved from: <URL: http://blog.taggesell.de/index.php?/aarchives/73-Managing-Amazon-EC2., 6 pages.Applicant
- Using and Managing AWS—Part 6: SSH Key Pairs, Top WordPress, May 26, 2009, Retrieved from the Internet: <URL: http://clouddb.info/2009/05/26/using-and-managing-aws-part-6-ssh-key-pairs>, 5 pages.Applicant
- L. Gommans, et al., Token-Based Authorization of Connection Oriented Network Resources, 1st International Workshop on Networks for Grid Applications (GridNets 2004), Oct. 29th 2004; 8 pages.Applicant
- Hyun, Ahn Ji, Authorized Officer for Korean Intellectual Property Office, International Search Report and Written Opinion for PCT/US2012/021846, International Search Report completed May 25, 2012, 8 pages.Applicant
- Na, Lee Da, Authorized Officer for Korean Intellectual Property Office, International Search Report and Written Opinion for PCT/US2012/020954, International Search Report completed Aug. 23, 2012, 10 pages.Applicant
- Alpern, B., “The Jalapeno virtual machine,” IBM Systems Journal, Jan. 2000, vol. 39, Issue 1, pp. 211-238.Applicant
- Bok, Jin Yo, Authorized Officer for Korean Intellectual Property Office, International Search Report and Written Opinion for PCT/US2012/029210, International Search Report completed Oct. 10, 2012, 9 pages.Applicant
- Anonymous, Storage I/O Control Technical Overview and Consideration for Deployment VMware vSphere ™ 4.1, Jan. 1, 2010, XP05504491, retrieved from the internet: URL: http://www.vmware.com/fled/pdf/techpaper/WMW-vSphere41-SIOC.pdf; [retrieved on Nov. 21, 2012], the entire document.Applicant
- Cabellos et al., LISPmob: Mobile Networking through LISP, Apr. 2, 2012, 8 pages.Applicant
- Steinmetz, Christof, Authorized Office for European Patent Office, International Search Report and Written Opinion for PCT/US2013/034140, completed Jun. 25, 2013, 21 pages.Applicant
- Hehn, Eva, Authorized Office for European Patent Office, International Search Report and Written Opinion for PCT/US2013/027456, completed Jun. 24, 2013, 11 pages.Applicant
- Eng, Lili, Australian Government, IP Australia, Examiner's First Report for 2012200562, dated Jun. 4, 2012, 2 pages.Applicant