This invention is directed to electronic devices with embedded authentication systems.
Electronic devices, and in particular portable electronic devices, are used to store personal information. For example, users may use cellular telephones, PDAs, smart phones, or other electronic devices to store contacts, e-mail, calendar information, documents, and other information used by the user. While this information may not necessarily be confidential, users may desire that at least some of that information be unavailable to other people. One approach for preventing unauthorized people from accessing and viewing the user's personal information may be to require users of the electronic device to provide a password or pass code prior to enabling device functions or accessing device resources. For example, the electronic device may require a user to enter a four number or four letter pin prior to displaying the device home screen (e.g., a spring board) or menus. As another example, an accessory device for detecting a user's fingerprint or for scanning a user's retina may be coupled to the device such that the user must first show an authorized fingerprint or retina before receiving access to the device.
While both of these approaches may be useful, restricting access based on a password or pass code is effective only so long as no other user knows the password or pass code. Once the password or pass code is known, the restriction mechanism may become ineffective. Also, a password or pass code may be forgotten, thus locking an authorized user out of the device. In addition, requiring a user to provide a fingerprint or submit to a retina scan may be time consuming and bothersome for the user, requiring an additional step before the user can access the device. While this approach is more secure than entering a password or pass code, it comes at a cost in hardware (e.g., the necessary scanner, detector, or reader) and time. It would be desirable therefore, to provide an electronic device by which biometric and other authentication mechanisms are implemented in the device such that the device authenticates the user quickly and seamlessly, for example as the user turns on, unlocks or wakes the device.
Methods, electronic devices and computer readable media for authenticating a user of an electronic device are provided. In some embodiments, an electronic device may seamlessly authenticate a user. The electronic device may receive an input from a user, the input provided by an input mechanism of the electronic device. The electronic device may detect identification information as the user provides the input from one or more sensors embedded in or adjacent to the input mechanism. The electronic device may authenticate the user by comparing the detected identification information with identification information stored in a library of the device. For example, the sensor may include a sensor for detecting features of a user's skin, or features underneath a user's skin. The sensor may be embedded in at least one of a touch screen, a button (e.g., of a keyboard or mouse), device housing near an input mechanism (e.g., laptop housing near keyboard), or any other suitable location.
In some embodiments, the electronic device may determine that a user is aligned with a sensing component of the device without directing the user to align with the sensing component. For example, the sensing component may be positioned such that the sensing region of the sensor includes expected positions of the user while the user operates the electronic device. The sensor may detect one or more biometric attributes of the user (e.g., facial or eye features) using the sensing component. For example the sensor may include a camera or optical sensor located adjacent to a display of the device. The user may then be authenticated by comparing the detected biometric attributes with a library of biometric attributes stored by or accessible to the electronic device.
In some embodiments, the electronic device may authenticate a user based on common attributes of options selected by a user. The electronic device may display several selectable options for selection by the user, and may receive a user selection of a subset of options. The electronic device may then identify one or more attributes common to some or all of the selected option. The attributes may include, for example at least one of, size, color, contour, fill pattern, shape, alignment with other options, the position of an option relative to other options, the source of the option, or any other suitable attribute. The electronic device may then authenticate the user based on the identified attribute. For example, if the user has selected all of the shapes sharing an attribute associated with a particular user, the electronic device may authenticate the user.
In some embodiments, the electronic device may authenticate a user based on a pattern of inputs received by the device. The electronic device may include a sensor operative to detect several inputs provided by a user. For example, the sensor may include an input mechanism operative to receive inputs provided by a user. As another example, the sensor may include an accelerometer or gyroscope operative to detect motion of or contacts with the electronic device. The electronic device may be operative to identify a pattern of the detected inputs, and to compare the identified pattern with patterns stored in memory to authenticate the user. The patterns may include temporal patterns (e.g., related to the delays between consecutive inputs), visual patterns (e.g., related to attributes of several options selected by the user or inputs provided by the user), or combinations of these. Upon authenticating the user, the electronic device may provide the user with access to restricted electronic device resources.
The above and other objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
An electronic device having an authentication system for restricting access to electronic device resources is provided. Access to any suitable electronic device resource may be restricted, including for example access to files or data stored on or available to the device. As another example, access to particular applications may be restricted (e.g., applications purchased by particular users, or applications associated with administrative tasks or privileges). As still another example, access to personal settings (e.g., displayed options, background images, or the icons used for applications) may be restricted until the user authenticates.
Any suitable authentication system may be implemented. In some embodiments, the authentication system may include a system for detecting biometric features or attributes of a user. For example, the electronic device may include a system operative to detect and authenticate a user based on features of or under a user's skin, such as a finger print, hand print, palm print, knuckle print, blood vessel pattern, or any other suitable portion of or under the user's skin. As another example, the electronic device may include a system operative to detect and authenticate a user based on features of a user's eyes or face, or movements of the user's eyes. As still another example, the electronic device may include a system operative to detect features of a user's ear canal, an odor associated with the user, a user's DNA, or any other suitable biometric attribute or information associated with a user.
In some embodiments, the authentication system may include a system operative to identify a user based on a visual or temporal pattern of inputs provided by the user. For example, the electronic device may display several selectable options or shapes forming a visual pattern. The user may select any suitable predetermined subset of displayed options to authenticate. For example, the user may select one or more options that have a predetermined attribute (e.g., size, color, shape or contour) in common. As another example, the user may select one or more options positioned in predetermined areas of the display (e.g., independent of the attributes of the selected options). The user may select options simultaneously, sequentially, or as a combination of these.
As another example, the user may provide a series of inputs at a particular pace or in a particular pattern. For example, the user may select options with a particular delay (e.g., pause between two selections). Alternatively, the user may provide inputs detected by a sensor (e.g., an accelerometer or a gyroscope) of the device following a predetermined temporal pattern. The device may detect the inputs from vibrations caused by tapping the device or an area adjacent to the device, moving the device in a particular manner, or any other suitable approach for detecting inputs.
The electronic device may provide any suitable combination of authentication systems, including for example biometric authentication systems and pattern-based authentication systems, several biometric authentication systems, or several pattern-based systems. In some embodiments, different authentication systems may be associated with different resources, such that a user may provide authentication information for several systems before finally accessing particular restricted resources (e.g., private or personal information). The electronic device may use any suitable approach for selecting which authentication systems to combine. For example, a user may associate several authentication systems with particular resources, or the electronic device may instead automatically (e.g., as a default) assign particular authentication systems to particular resources.
Processor 102 may include any processing circuitry operative to control the operations and performance of electronic device 100. For example, processor 102 may be used to run operating system applications, firmware applications, media playback applications, media editing applications, or any other application. In some embodiments, a processor may drive a display and process inputs received from a user interface.
Storage 104 may include, for example, one or more storage mediums including a hard-drive, solid state drive, flash memory, permanent memory such as ROM, any other suitable type of storage component, or any combination thereof. Storage 104 may store, for example, media data (e.g., music and video files), application data (e.g., for implementing functions on device 100), firmware, user preference information data (e.g., media playback preferences), authentication information (e.g. libraries of data associated with authorized users), lifestyle information data (e.g., food preferences), exercise information data (e.g., information obtained by exercise monitoring equipment), transaction information data (e.g., information such as credit card information), wireless connection information data (e.g., information that may enable electronic device 100 to establish a wireless connection), subscription information data (e.g., information that keeps track of podcasts or television shows or other media a user subscribes to), contact information data (e.g., telephone numbers and email addresses), calendar information data, and any other suitable data or any combination thereof.
Memory 106 can include cache memory, semi-permanent memory such as RAM, and/or one or more different types of memory used for temporarily storing data. In some embodiments, memory 106 can also be used for storing data used to operate electronic device applications, or any other type of data that may be stored in storage 104. In some embodiments, memory 106 and storage 104 may be combined as a single storage medium.
Communications circuitry 108 can permit device 100 to communicate with one or more servers or other devices using any suitable communications protocol. Electronic device 100 may include one more instances of communications circuitry 108 for simultaneously performing several communications operations using different communications networks, although only one is shown in
RTSP, SSH, Voice over IP (VOIP), any other communications protocol, or any combination thereof.
Input/output circuitry 110 may be operative to convert (and encode/decode, if necessary) analog signals and other signals into digital data. In some embodiments, input/output circuitry can also convert digital data into any other type of signal, and vice-versa. For example, input/output circuitry 110 may receive and convert physical contact inputs (e.g., from a multi-touch screen), physical movements (e.g., from a mouse or sensor), analog audio signals (e.g., from a microphone), or any other input. The digital data can be provided to and received from processor 102, storage 104, memory 106, or any other component of electronic device 100. Although input/output circuitry 110 is illustrated in
Electronic device 100 may include any suitable mechanism or component for allowing a user to provide inputs to input/output circuitry 110. For example, electronic device 100 may include any suitable input mechanism, such as for example, a button, keypad, dial, a click wheel, or a touch screen. In some embodiments, electronic device 100 may include a capacitive sensing mechanism, or a multi-touch capacitive sensing mechanism. Some sensing mechanisms are described in commonly owned U.S. patent application Ser. No. 10/902,964, filed Jul. 10, 2004, entitled “Gestures for Touch Sensitive Input Device,” and U.S. patent application Ser. No. 11/028,590, filed Jan. 18, 2005, entitled “Mode-Based Graphical User Interfaces for Touch Sensitive Input Device,” both of which are incorporated herein in their entirety.
In some embodiments, electronic device 100 can include specialized output circuitry associated with output devices such as, for example, one or more audio outputs. The audio output may include one or more speakers (e.g., mono or stereo speakers) built into electronic device 100, or an audio component that is remotely coupled to electronic device 100 (e.g., a headset, headphones or earbuds that may be coupled to communications device with a wire or wirelessly).
In some embodiments, I/O circuitry 110 may include display circuitry (e.g., a screen or projection system) for providing a display visible to the user. For example, the display circuitry may include a screen (e.g., an LCD screen) that is incorporated in electronics device 100. As another example, the display circuitry may include a movable display or a projecting system for providing a display of content on a surface remote from electronic device 100 (e.g., a video projector). In some embodiments, the display circuitry can include a coder/decoder (Codec) to convert digital media data into analog signals. For example, the display circuitry (or other appropriate circuitry within electronic device 100) may include video Codecs, audio Codecs, or any other suitable type of Codec.
The display circuitry also can include display driver circuitry, circuitry for driving display drivers, or both. The display circuitry may be operative to display content (e.g., media playback information, application screens for applications implemented on the electronic device, information regarding ongoing communications operations, information regarding incoming communications requests, or device operation screens) under the direction of processor 102.
Authentication system 112 may include any suitable system or sensor operative to receive or detect an input identifying the user of device 100. For example, authentication system 112 may include a skin-pattern sensing mechanism, an optical system for identifying users based on their facial patterns, eye features (e.g., retinas), or vein patterns, or any other sensor for detecting any other unique biometric feature or attribute of a user. As another example, authentication system 112 may be operative to receive secret or confidential entries identifying the user (e.g., gestures on the device, or touching a particular pattern of objects or colors on a display). As still another example, authentication system 112 may be operative to detect particular movements or vibrations of the device caused by the user. Authentication system 112 may be combined or embedded in any other element of electronic device 100 (e.g., a display or a camera), or use events detected by various sensors of the electronic device (e.g., an accelerometer or proximity sensor). In some embodiments, several types of authentication systems may be combined or implemented in the electronic device.
In some embodiments, electronic device 100 may include a bus operative to provide a data transfer path for transferring data to, from, or between control processor 102, storage 104, memory 106, communications circuitry 108, input/output circuitry 110 authentication system 112, and any other component included in the electronic device.
To prevent unauthorized access to data or information stored in memory or storage, the electronic device may direct an authentication system to identify the user and authorize access to requested resources. The electronic device may require authorization prior to providing access to any electronic device resource. In some embodiments, the electronic device may require different levels of authorization before providing access to different applications or different data or files associated with different applications. For example, the electronic device may require a user to satisfy several authentication systems prior to providing access to an application or data (e.g., a secondary authentication, for example using biometrics, in addition to a first or initial authentication, for example a pass code used to unlock the device).
In some embodiments, one or more applications may provide access to or use data or resources that are personal to one or more users. For example, options 212 and 214, associated with telephone and mail applications, respectively, may involve personal accounts or contacts that are not associated with every user of the electronic device. Prior to providing access to such applications, or to personal or confidential features or resources available via such applications, the electronic device may require the user to authenticate. In some embodiments, default features of applications may be available without authentication (e.g., allow all users to place telephone calls, but not to access a contact list).
Display screen 300 may include notice 320 instructing the user to authenticate before accessing the requested resources. Notice 320 may include a pop-up, overlay, new display screen, or any other suitable type of display for providing an instruction to the user. Notice 320 may include any suitable instruction, including for example a manner in which the user is to authenticate (e.g., specifying a particular authentication system to use). For example, notice 320 may direct the user to provide a fingerprint or provide an input that matches a predefined visual or temporal pattern. Once the user authenticates properly, the electronic device may display information 310 in a manner discernable by the user, and enable selectable options or other functions associated with the selected resource.
In some embodiments, a user may be required to authenticate prior to unlocking the electronic device (e.g., prior to accessing any resource of the device).
Display screen 400 may include notice 420 directing the user to authenticate prior to accessing the device resources (e.g., the home screen from which information and applications are launched). Notice 420 may include any suitable type of notice, including for example a pop-up, overlay, new display screen, or any other suitable type of display for providing an instruction to the user. The electronic device may display notice 420 at any suitable time, including for example when the user turns on the device (e.g., and views display screen 400), in response to the user attempting to access device resources without first authenticating (e.g., as an error message), in response to a user request for help, or at any other suitable time. Notice 420 may include any suitable instruction, including for example a manner in which the user is to authenticate, a list of authorized users, or any other suitable information.
Once the user has been properly authenticated, the electronic device may display options associated with the authenticated user (e.g., options for applications purchased by particular users). In some embodiments, the electronic device may provide access to resources or content that was previously not available (e.g., contact lists or previous messages in a telephone or mail application).
Display screen 500B may include options 510B for resources or applications available to the users. In some embodiments, options 510B may be entirely different from the options of a default screen (e.g., display screen 500B shares no options display screen 200,
Display screen 500C may include options 510C for resources or applications available to the users. In some embodiments, options 510C for the same resources as other display screens may have different appearances (e.g., different icons). For example, in
In some embodiments, the electronic device may provide access to different amounts of electronic device resources based on the identity of the authenticated user. For example, if an electronic device is used by several users (e.g., parents and children in the same family), the users may share some but not all of the resources (e.g., all users may have access to the family contact list, but not to other family members' e-mail). As another example, users of the electronic device may be organized in groups or tiers of users. Some resources may be associated with groups or tiers or users, instead of or in addition to particular users. When a particular user is authenticated and identified as being part of a group, the electronic device may provide the user with access to the resources associated with the group (e.g., common or shared contacts, shared communications, or shared documents) and to the resources associated with the particular user (e.g., personal contacts, e-mail accounts, and telephone call lists).
The electronic device may associate particular resources with one or more authentication systems. For example, a user may identify a resource and provide a protect or secure instruction (e.g., by selecting an appropriate option). A user may in addition select one or more authentication systems to satisfy before providing access to the resource. If the resource is not public (e.g., not a default application or file to remain available to all users), or if the resource was created or purchased by the user, the electronic device may associate the selected resource with the one or more selected authentication systems. Alternatively, if the user has sufficient privileges (e.g., an administrator), any resource may be secured using one or more selected authentication systems.
The electronic device may not require a user to authenticate each time the user unlocks or operates the electronic device. In some embodiments, the electronic device may allow a user to authenticate for a particular amount of time. For example, once authenticated, the electronic device may allow a user to access restricted resources for 10 hours from the time the user authenticated. As another example, the electronic device may retain the user's authentication for a particular amount of time after having received the user's last instruction or having entered a stand-by mode (e.g., retain authentication for thirty minutes after an input). The amount of time the electronic device retains authentication information may be set by the device or by the user, and may be based on the particular types or resources protected by the authentication information (e.g., allow for a longer authentication period for access to a game purchased by a particular user than to a user's personal contacts). Not requiring the electronic device to authenticate each time the user operates the device may save power consumption.
The electronic device may use any suitable type of authentication system to prevent unauthorized access of device resources. In some embodiments, the electronic device may include an authentication system based on a user's unique skin patterns. For example, the electronic device may include an authentication system operative to detect a user's finger, hand, palm, knuckle print, or any other suitable print or skin feature unique to the user. The authentication system may include a sensor operative to detect the user's unique skin pattern or feature.
The sensor may include any suitable type of sensor for detecting unique features or patterns of a user's skin. For example, the sensor may include an optical scanner operative to detect features of the user's skin. The optical sensor may include a charge coupled device, or any other suitable array of light-sensitive components (e.g., diodes) operative to record the light received by the sensor (e.g., a charge coupled device). For example, if a charge coupled device includes an array of light-sensitive components, the optical sensor may be operative to record, for each light sensitive component of the array, a pixel representing the light received by the particular light sensitive component. The value of each pixel may then reflect the distance from the sensor of the particular portion of the user's skin associated with the pixel (e.g., a ridge or valley). The recorded pixels may form an image, for example of a particular portion of the user's skin, that the electronic device can compare to a library of images associated with authorized users.
As another example, the sensor may include a capacitive sensor operative to detect features of a user's skin. The capacitive sensor may include one or more chips containing an array of cells, each of which may include at least two conductor plates separated by an insulating layer. The sensor may be coupled to an inverting amplifier operative to change the voltage between the at least two conductor plates of each cell in the chip. When a user's finger is placed over the array of cells, the sensor may be operative to distinguish the cells over which a valley (e.g., a fingerprint valley) and a ridge (e.g., a fingerprint ridge) are placed from the different capacitance values of each cell (i.e., cells under a valley will have a lower capacitance than cells under a ridge). Using the detected capacitance values of each cell in the chip, the sensor may generate an image or a representation of the skin placed over the sensor that can be compared to a library of images or representations available to the electronic device.
The authentication system may include any suitable countermeasure for preventing an unauthorized user from spoofing an authorized user's skin patterns, for example by placing an image (e.g., a printed image) or a three-dimensional structure (e.g., a polymer cast) adjacent to the authentication system sensor. For example, the authentication system may include a combination of optical and capacitance sensors, a sonar or radio-frequency sensor, a sensor for detecting a user's pulse, a heat sensor for determining the temperature of the object placed against the sensor (e.g., to determine if the temperature is within a range of expected human skin temperatures), or any other suitable countermeasure.
The sensor may be operative to detect features of the user's skin using any suitable approach. In some embodiments, the sensor may be operative to detect features of the user's skin when the user's skin is moved over the sensor. For example, the sensor may include a one-dimensional sensor or stagnant sensor (e.g., a line of sensing components) operative to detect features of a user's finger as it slides or rolls over the sensor. The sensor may include an orientation in which the user's skin is to move to provide an accurate representation of the user's skin features. For example, the sensor may require a user to move a fingertip along the axis of the finger or perpendicular to the axis of the finger.
In some embodiments, the sensor may be operative to detect features of the user's skin when the skin is held immobile over the sensor. For example, the sensor may include a two-dimensional sensor or moving sensor operative to detect features of the user's finger when the finger is stationary over the sensor. The sensor may be operative to move at a regular pace or speed under the user's immobile finger, or detect an instantaneous or near-instantaneous two-dimensional representation of the user's finger at a point in time (e.g., as the user's finger moves over the sensor). Using a two-dimensional sensor may provide a more accurate representation of the user's skin features, as a two-dimensional sensor does not depend on the user moving his skin over the sensor at a regular or even pace, unlike a one-dimensional sensor.
The sensor may be placed at any suitable location within the electronic device. In some embodiments, the sensor may be placed such that it is operative to detect an appropriate portion of the user's skin as the user operates or begins to operate the electronic device. The sensor position may vary based on the portion of the user's skin to be detected (e.g., finger, hand or palm).
To authenticate the user during the unlocking process, display 600 may include sensor 620 in the display along track 612. For example, sensor 620 may be embedded in the display stack (e.g., among the display stack that may include a capacitance sensing component, a light source, and a display surface). As another example, sensor 620 may be placed underneath the display stack. As still another example, sensor 620 may include an existing component of the display stack (e.g., the display stack for a touch screen display may include a capacitance sensor). In such an approach, the authentication system may use the detected output of a capacitance sensing component of the display stack (e.g., in a touch screen display) that has a sufficient resolution for distinguishing ridges and valleys of a user's skin. In some embodiments, the capacitance sensing component of the display stack may include several types or densities of capacitance sensing components to allow for authentication using particular portions of the display (e.g., use very fine sensing components in the display stack along at least a portion of track 612 for authentication and less fine sensing components in the remaining areas of display 600).
In some embodiments, sensor 620 may be embedded in the electronic device such that it is not visible in display 600. For example, sensor 620 may be assembled, printed or etched directly on display 600 (e.g., etched on glass) such that the user cannot see the fingerprint scanner. If a user has difficulty providing a suitable fingerprint to sensor 620, display 600 may highlight the outlines of sensor 620 (e.g., display an icon directing the user to place a finger on the icon over sensor 620) to assist the user in authenticating.
To provide for secure access to resources, electronic device 700 may include at least one sensor 720 operative to detect features of a user's fingerprint to identify the user. To provide a seamless user experience, the sensors 720 may be embedded in or under at least one of input mechanism 710 and 712. In some embodiments, input mechanism 710, which may include several distinct keys that a user may press to provide inputs to electronic device 700, may include a sensor 720 embedded in one or more keys. For example, an optical or capacitive sensor may be placed at the top surface of a key such that when a user places a finger on the key (e.g., rests his index fingers on the “F” or “J” keys), the sensor may detect features of the user's fingertips for authenticating the user. A two-dimensional or moving sensor may be used for this implementation to authenticate the user while the user's fingers are placed over the keys.
A sensor 720 may be placed in, adjacent to or behind any button or other physical input that a user may press in an electronic device. For example, a sensor 720 may be placed behind a ‘home button of a portable media player or cellular telephone (e.g., button 812,
In some embodiments, input mechanism 712 may include a sensor 720 embedded underneath some or all of the pad such that when a user places a finger on input mechanism 712 (e.g., to move an indicator on display 715), sensor 720 may detect the features of the user's finger for authenticating the user. Sensor 720 used may be a one-dimensional sensor, authenticating the user as the user moves his fingers across the pad, or a two-dimensional sensor operative to authenticate the user when the user's finger is immobile on the pad (e.g., when the user first places his finger on the pad). Sensor 720 may cover the entire surface of input mechanism 712 such that the user need not place his fingers over a particular portion of input mechanism 712 to be authenticated. Electronic device 700 may be operative to identify the position of each sensor 720 to assist the user in providing an adequately detectable input, for example using a highlight, indication on the display, or any other suitable approach. In some embodiments, any other suitable input mechanism may include a sensor 720 operative to seamlessly detect the user's fingerprint features (e.g. a button, wheel, key or screen).
In some embodiments, the authentication system may instead or in addition include a sensing mechanism for detecting features underneath a user's skin. For example, the authentication system may include a sensor operative to detect the pattern of a user's veins, arteries, follicle distribution, or any other suitable feature underneath the user's skin that may be detected. The sensor may include any suitable type of sensor, including for example an optical sensor (e.g., a camera) located on the surface of the electronic device. The sensor may be positioned so as to detect a feature underneath any suitable portion of the user's skin when the electronic device is in use. For example, the sensor may be positioned to detect features underneath a user's skin in an area of the user's fingers, hand, wrist, arm, face, or any other suitable area.
In some embodiments, the authentication system may instead or in addition include a sensor operative to detect features of the user's face. For example, the authentication system may include a sensor operative to detect radiation emitted or reflected by one or more distinctive features of the user's face when the user's face is placed opposite the sensor. The sensor may be operative to detect any suitable type of radiation. For example, the sensor may include a light sensor (e.g., a camera), an infra-red sensor, an ultra-violet sensor, a scanning laser, an ultrasound sensor (e.g., sonar), or any other sensor operative to detect a desired radiation (e.g., a particular range of radiation frequencies or periods).
The authentication system may be operative to detect any suitable element of the user's face. For example, the authentication system may identify faces by analyzing the relative to position and size of a user's head, nose, mouth, ears, cheekbones, jaw, or any other attribute of the user's face. As another example, the authentication system may identify features of the user's face using a three-dimensional authentication system to capture and analyze curved surfaces or depths of a user's facial features (e.g., contour of eye sockets, chin or nose). As still another example, the authentication system may detect unique lines, patterns or spots of the user's skin (e.g., using skin texture analysis) To enhance or facilitate authentication, combinations of these approaches may be used.
The sensor for detecting features of the user's face may be located at any suitable position on the electronic device. In some embodiments, the sensor may include a camera or other sensor provided with the electronic device for a different purpose (e.g., an embedded webcam for chatting).
In some embodiments, the authentication system may instead or in addition include a sensor operative to authenticate a user based on attributes of the user's eyes. For example, the sensor may be operative to scan a user's retina, iris or retinal blood vessels to detect unique patterns of the user. The sensor may include a light source operative to emit light, for example infrared light, to be reflected by the user's eye and detected by a lens or optical sensor. The sensor may analyze the received light to create a representation of the user's eyes that can be compared with a library of authorized user's eyes.
As another example, the sensor may instead or in addition be operative to detect movements of the user's eyes, for example by tracking the position and movement of a user's retina, iris, blood vessels, or any other feature of the user's eyes. Before providing a user with access to electronic device resources, the electronic device may direct the sensor to detect a predetermined eye movement set up by an authorized user. For example, each authorized user may create an eye movement track by moving his eyes in a particular manner (e.g., up, down, left, right, blink, blink) while looking at the sensor. When a user of the device moves his eyes in a manner that matches a predetermined eye movement, the electronic device may unlock the device or provide access to restricted resources.
The sensor may be located at any suitable position of the device, including for example adjacent to a display or other portion of the device that will face the user's eyes (e.g., a position similar to that of sensor 1120,
In some embodiments, the authentication may be operative to authenticate users based on attributes or qualities of their voices. For example, the authentication system may be operative to detect a particular voice pitch or voice signature. The authentication system may be text dependent (e.g., the user must say a particular phrase to authenticate, such as “my voice is my passport”) or text independent (e.g., any suitable words may be said to authenticate the user). In some embodiments, the authentication system may require the user to say a secret password to authenticate, thus requiring both knowledge of the user's password and the user's voice pitch to properly authenticate. The authentication system may include any suitable component for authenticating a user, including for example a microphone. In some embodiments, the microphone may be primarily used for other purposes (e.g., telephone communications or video conferencing).
In some embodiments, other types of authentication systems may be used. In some embodiments, the authentication system may be operative to identify and authenticate users from the shape of their ear canals. For example, the authentication system may include a sensor (e.g., optical, radar or sonar) operative to detect unique features of a user's ear canal (e.g., shape and length). The sensor may be located, for example, near a speaker of the device (e.g., if the device is a telephone). In some embodiments, the authentication system may be operative to identify a user based on an odor particular to the user. For example, the authentication system may include a sensor operative to detect unique attributes of the odor of a user's skin or sweat glands. The sensor may be located at any suitable position on the device, including for example at or near an input mechanism (e.g., where the user touches the device).
In some embodiments, the authentication system may be operative to identify a user based on a DNA sequence. For example, the authentication may include a sensor coupled to a processor that is operative to receive a cell having the user's DNA (e.g., from the user's skin or mouth) and determine whether a particular DNA sequence is present. The length or variation in DNA sequence may be selected to both ensure that proper authentication is provided and that the authentication process is sufficiently quick (e.g., the entire DNA strand need not be analyzed). The sensor may be positioned at any suitable location on the device, including for example on or adjacent to input mechanisms or other components that a user may touch.
The electronic device may receive biometric information reflecting authorized users using any suitable approach. For example, when a user selects an authentication system to use with particular device resources, the electronic device may direct the user to provide biometric information (e.g., a fingerprint, eye scan, or DNA sequence) to be stored in a library. The electronic device may direct the user to provide the biometric input using any suitable approach, including for example using visual cues, audio cues, and highlighting or identifying the location of the authentication system sensor. Received biometric information stored in the library may be retrieved when a user attempts to authenticate, and compared to the biometric information provided by the user. If the provided biometric authentication information matches information stored in the library (e.g., information associated with a requested resource), the electronic device may provide access to a restricted resource. In some embodiments, a similar approach may be used to receive non-biometric authentication information.
In some embodiments, the authentication system may instead or in addition not require biometric parameters to provide access to electronic device resources to users. Although non-biometric authentication systems may be, in some cases, easier to circumvent than biometric authentication systems, the non-biometric authentication systems may nevertheless be highly effective and secure. In some embodiments, the authentication system may provide access to electronic device resources in response to detecting that a key or token is within a particular distance of the electronic device. For example, a user may have a cellular telephone and a computer. One or both devices may include circuitry for detecting that the devices are within a particular range of each other (e.g., 5 feet so that a user may sit at a desk to use the computer with the cellular telephone in his pocket and authenticate). When the devices determine that they are in proximity, resources of one or both devices may become available. This approach may be particularly useful to secure access to static devices while taking advantage of the fact that a user may keep a portable device on his person. This and other embodiments are described in more detail in commonly owned U.S. patent application Ser. No. 11/823,656, filed Jun. 27, 2007.
In some embodiments, the electronic device may authenticate a user based on a particular sequence of inputs provided by the user. For example, the electronic device may require the user to provide an input corresponding to a visual pattern provided by the electronic device.
To authenticate, the user may select (e.g., as detected by an input mechanism or other sensor) any suitable subset of the displayed shapes or options. The subset may include some or all of the shapes that share one or more attributes. For example, the user may select some or all of the shapes that are of a particular color (e.g., all shapes that include a shade of yellow). As another example, the user may select some or all shapes that have the same contour (e.g. all squares). As still another example, the user may select some or all shapes that have a particular attribute in common (e.g., all 5-sided shapes, or all shapes representing pictures associated with a particular album stored by the device). As yet still another example, the user may select some or all shapes that include a particular distribution of colors (e.g., shapes that include a red portion adjacent to a blue portion). Any suitable criteria or attribute (including combinations of the examples listed above, such as selecting the top two blue shapes and the bottom two square shapes) may be used to select the particular subset of displayed shapes.
Any suitable number of shapes or options may be associated with the subset to select for authentication. For example, the number of shapes may be related to the total number of displayed shapes (e.g., select 20% of the displayed shapes). As another example, the number of shapes may be a fixed number, for example less than five (e.g., so that the user can simultaneously select all shapes using one hand) or ten (e.g., so that the user can simultaneously select all shapes using both hands). The number of shapes may be selected to optimize security (e.g., require enough shapes that it is too difficult to simply guess which shapes to select).
The user may select the subset of the shapes using any suitable approach. If a multi-touch display is provided, the authentication system may require the user to simultaneously select all of the shapes used for authentication. As another example, the authentication system may allow the user to sequentially select the shapes used for authentication. The shapes may be selected in an arbitrary or particular order (e.g., from top to bottom or left to right). As still another example, the authentication system may require the user to provide a single, moving input (e.g., dragging a finger across the display) selecting only the shapes of the authorized subset. Any other suitable approach for selecting the subset of shapes may be used.
To avoid having the user always select shapes displayed in the same relative position on the display (e.g., like entering a numeric pass code using a displayed keypad), the electronic device may change the distribution of the shapes to select for authentication. To authenticate, the user may then identify the shapes that share the attribute associated with the authentication protocol. Because the position of the shapes used to authenticate may change each time the user accesses device resources, someone looking over the user's shoulder to see the general distribution of the selected shapes may not be able to select shapes with the same distribution to authenticate (e.g., the striped shapes may not be distributed in the same areas of the device).
After each failed attempt at selecting shapes for authentication, the electronic device may change the distribution of the displayed shapes, or even change the shapes (e.g., use different colors or contours) to prevent an unauthorized user from guessing the proper subset of shapes. The electronic device may lock the device resources after a particular number of failed attempts to select the proper subset of shapes. Once locked, a user may need to couple the device with a host to re-enable the device (e.g., couple a mobile device to a fixed device) or use another authentication system (e.g., a biometric system) to re-enable the device.
In some embodiments, rather than selecting particular shapes, the user may simply select the shapes located in pre-determined portions of the screen. For example, the user may place one or more fingers over several shape positions independent of the actual displayed shape. As another example, the user may place one or more fingers over particular shapes displayed by the electronic device, and move the one or more fingers in a predetermined manner (e.g. slide one or more fingers), independent of the displayed shapes. As still another example, the user may successively select several shapes located at predetermined positions on the display (e.g., select shapes at particular locations to form a predetermined pattern).
The electronic device may, in some embodiments, provide a blank or uniform display on which the user may draw one or more patterns using one or more fingers. Such an approach may confuse or distract unauthorized users by creating a visual distraction via the displayed shapes.
In some embodiments, the electronic device may authenticate a user based instead or in addition on a received temporal pattern of inputs by the user. For example, the user may provide a particular number of inputs at a particular rate to authenticate. The electronic device may detect the inputs using any suitable approach. For example, the electronic device may detect inputs provided using an input mechanism of the device (e.g., inputs received by a touch screen). As another example, the electronic device may detect inputs from motion, contacts, vibrations or other impacts detected by an appropriate sensor of the device (e.g., an accelerometer). In such an approach, a user may tap any portion of the device (or a body in contact with the device, such as a table on which the device is placed) such that the sensor in the device detects the taps and determines whether they correspond to an authorized temporal pattern. As still another example, the electronic device may detect that it has been moved in a particular manner (e.g., shaken twice then spun) using a sensor in the device (e.g., an accelerometer or gyroscope). In response to detecting a correct temporal pattern, the electronic device may provide access to restricted resources.
In some embodiments, the authentication system may combine temporal and visual patterns for authentication. For example, a user may be required to select particular displayed shapes at a certain rate (e.g., the first two shapes quickly, then a pause before simultaneously selecting the last two). As another example, the user may be required to first select the proper shapes then provide an input for a temporal pattern. As still another example the user may be required to select one or more shapes and move the device (e.g., shake the device). Any other suitable combination of inputs may be required for authentication.
The electronic device may set up visual or temporal patterns for authorized users using any suitable approach. In some embodiments, when a user selects to use a temporal or visual pattern to restrict access to particular device resources, the electronic device may direct the user to provide or select the temporal or visual pattern. For example, the electronic device may provide a list of shape attributes that the user may select to form a pattern (e.g., a color or a contour). As another example, the electronic device may direct the user to select displayed shapes or provide a temporal pattern, and extract or identify the pattern from the received inputs. The electronic device may direct the user to provide a pattern several times before it is accepted to ensure that the user intended and remembers the selected pattern.
The electronic device may include any suitable number and types of authentication systems. For example, the electronic device may include one, more or all of the authentication systems or authentication approaches described above. Access to different resources may be restricted using one or more authentication systems, which a user may select or set up. In some embodiments, several authentication systems may be used sequentially before access to particular restricted resources is provided.
At step 1506 the electronic device may determine whether a request to access restricted resources was received. For example, the electronic device may determine whether the user provided an instruction to access data associated with a particular user (e.g., a contact list or other personal information). As another example, the electronic device may determine whether the user provided an instruction to access a restricted application (e.g., an application restricted to a particular tier of users, such as administrators, or an application purchased by a particular user). If the electronic device determines that no instruction to access restricted resources was received, process 1500 may return to step 1506 and continue to monitor inputs received from the user.
If, at step 1506, the electronic device instead determines that an instruction to access restricted resources was received, process 1500 may move to step 1508. At step 1508, the electronic device may determine whether the identified user is authorized to access the resources. For example, the electronic device may determine whether the user has provided suitable authentication information for accessing the restricted resources. The electronic device may receive suitable authentication information without the user's knowledge, for example by embedding an authentication sensor in the device such that authentication information is received during normal use. If the electronic device determines that the identified user is not authorized, process 1500 may move to step 1510. At step 1510, the electronic device may instruct the user to authenticate. For example, the electronic device may direct the user to provide authentication information to an authentication system (e.g., any of the authentication systems described above). In some embodiments, the electronic device may detect several inputs by the user, and determine whether the inputs have a pattern or share attributes associated with an authorized user (e.g., determine whether the user has provided the proper inputs that correspond to an attribute or pattern of an authorized user, or determine whether the attribute or pattern of the inputs matches an attribute or pattern associated with authorized users). Process 1500 may then return to step 1508 to determine whether the user has provided suitable authentication information.
If, at step 1508, the electronic device instead determines that the user is authorized, process 1500 may move to step 1512. At step 1512, the electronic device may provide the user with access to the requested restricted resources. For example, the electronic device may provide the user with access to personal data or to applications specific to the user. Process 1500 may then end at step 1514.
The above described embodiments of the invention are presented for the purposes of illustration and not of limitation, and the present invention is limited only by the claims which follow.
This application is a continuation of U.S. patent application Ser. No. 14/142,669, filed Dec. 27, 2013, which is a continuation of U.S. patent application Ser. No. 12/207,374, filed Sep. 9, 2008, which is now U.S. Pat. No. 8,943,580, issued Jan. 27, 2015, which claims the benefit of U.S. Provisional Patent Application No. 60/995,200, filed Sep. 24, 2007, the entire contents of which are incorporated herein by reference in their entirety. This application is related to the following applications: U.S. patent application Ser. No. 14/142,657, “Embedded Authentication Systems in an Electronic Device,” filed Dec. 27, 2013, now U.S. Pat. No. 9,134,896, issued Sep. 15, 2015; U.S. patent application Ser. No. 14/142,669, “Embedded Authentication Systems in an Electronic Device,” filed Dec. 27, 2013; and U.S. patent application Ser. No. 14/142,674, “Embedded Authentication Systems in an Electronic Device,” filed Dec. 27, 2013, now U.S. Pat. No. 9,038,167, issued May 19, 2015, which are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4353056 | Tsikos | Oct 1982 | A |
4993068 | Piosenka et al. | Feb 1991 | A |
5053608 | Senanayake | Oct 1991 | A |
5131038 | Puhl et al. | Jul 1992 | A |
5280527 | Gullman et al. | Jan 1994 | A |
5325442 | Knapp | Jun 1994 | A |
5420936 | Fitzpatrick et al. | May 1995 | A |
5465084 | Cottrell | Nov 1995 | A |
5469506 | Berson et al. | Nov 1995 | A |
5526428 | Arnold | Jun 1996 | A |
5559961 | Blonder | Sep 1996 | A |
5591949 | Bernstein | Jan 1997 | A |
5613012 | Hoffman et al. | Mar 1997 | A |
5615277 | Hoffman | Mar 1997 | A |
5615384 | Allard et al. | Mar 1997 | A |
5677710 | Thompson-Rohrlich | Oct 1997 | A |
5799098 | Ort et al. | Aug 1998 | A |
5805719 | Pare, Jr. et al. | Sep 1998 | A |
5821933 | Keller et al. | Oct 1998 | A |
5838306 | O'Connor et al. | Nov 1998 | A |
5838812 | Pare, Jr. et al. | Nov 1998 | A |
5852670 | Setlak et al. | Dec 1998 | A |
5856824 | Shieh | Jan 1999 | A |
5857028 | Frieling | Jan 1999 | A |
5870723 | Pare, Jr. et al. | Feb 1999 | A |
5907327 | Ogura et al. | May 1999 | A |
5920640 | Salatino et al. | Jul 1999 | A |
5933134 | Shieh | Aug 1999 | A |
5943043 | Furuhata et al. | Aug 1999 | A |
5952641 | Korshun | Sep 1999 | A |
5952998 | Clancy et al. | Sep 1999 | A |
5963679 | Setlak | Oct 1999 | A |
5974150 | Kaish et al. | Oct 1999 | A |
5991408 | Pearson et al. | Nov 1999 | A |
6028950 | Merjanian | Feb 2000 | A |
6037882 | Levy | Mar 2000 | A |
6038666 | Hsu et al. | Mar 2000 | A |
6041410 | Hsu et al. | Mar 2000 | A |
6084968 | Kennedy et al. | Jul 2000 | A |
6141436 | Srey et al. | Oct 2000 | A |
6151208 | Bartlett | Nov 2000 | A |
6151593 | Cho et al. | Nov 2000 | A |
6154879 | Pare, Jr. et al. | Nov 2000 | A |
6160555 | Kang et al. | Dec 2000 | A |
6167517 | Gilchrist et al. | Dec 2000 | A |
6181328 | Shieh et al. | Jan 2001 | B1 |
6181803 | Davis | Jan 2001 | B1 |
6182221 | Hsu et al. | Jan 2001 | B1 |
6185316 | Buffam | Feb 2001 | B1 |
6192478 | Elledge | Feb 2001 | B1 |
6193153 | Lambert | Feb 2001 | B1 |
6219793 | Li et al. | Apr 2001 | B1 |
6249606 | Kiraly et al. | Jun 2001 | B1 |
6256022 | Manaresi et al. | Jul 2001 | B1 |
6268788 | Gray | Jul 2001 | B1 |
6282304 | Novikov et al. | Aug 2001 | B1 |
6282649 | Lambert et al. | Aug 2001 | B1 |
6292173 | Rambaldi et al. | Sep 2001 | B1 |
6317834 | Gennaro et al. | Nov 2001 | B1 |
6317835 | Bilger et al. | Nov 2001 | B1 |
6323846 | Westerman et al. | Nov 2001 | B1 |
6327376 | Harkin | Dec 2001 | B1 |
6337919 | Dunton | Jan 2002 | B1 |
6347290 | Bartlett | Feb 2002 | B1 |
6353889 | Hollingshead | Mar 2002 | B1 |
6366682 | Hoffman et al. | Apr 2002 | B1 |
6367017 | Gray | Apr 2002 | B1 |
6421453 | Kanevsky et al. | Jul 2002 | B1 |
6424711 | Bayless et al. | Jul 2002 | B1 |
6466781 | Bromba et al. | Oct 2002 | B1 |
6484260 | Scott et al. | Nov 2002 | B1 |
6487662 | Kharon et al. | Nov 2002 | B1 |
6490680 | Scheidt et al. | Dec 2002 | B1 |
6498861 | Hamid et al. | Dec 2002 | B1 |
6501846 | Dickinson et al. | Dec 2002 | B1 |
6529885 | Johnson | Mar 2003 | B1 |
6532298 | Cambier et al. | Mar 2003 | B1 |
6560612 | Yamada et al. | May 2003 | B1 |
6570557 | Westerman et al. | May 2003 | B1 |
6573883 | Bartlett | Jun 2003 | B1 |
6581161 | Byford | Jun 2003 | B1 |
6603462 | Matusis | Aug 2003 | B2 |
6609198 | Wood et al. | Aug 2003 | B1 |
6615264 | Stoltz et al. | Sep 2003 | B1 |
6618806 | Brown et al. | Sep 2003 | B1 |
6633310 | Andrew et al. | Oct 2003 | B1 |
6636973 | Novoa et al. | Oct 2003 | B1 |
6639584 | Li | Oct 2003 | B1 |
6657538 | Ritter | Dec 2003 | B1 |
6662166 | Pare, Jr. et al. | Dec 2003 | B2 |
6668332 | McNeil | Dec 2003 | B1 |
6671808 | Abbott et al. | Dec 2003 | B1 |
6677932 | Westerman | Jan 2004 | B1 |
6681034 | Russo | Jan 2004 | B1 |
6709333 | Bradford et al. | Mar 2004 | B1 |
6719200 | Wiebe | Apr 2004 | B1 |
6720860 | Narayanaswami | Apr 2004 | B1 |
6724370 | Dutta et al. | Apr 2004 | B2 |
6728881 | Karamchetty | Apr 2004 | B1 |
6735287 | Vishik et al. | May 2004 | B2 |
6735695 | Gopalakrishnan et al. | May 2004 | B1 |
6751734 | Uchida | Jun 2004 | B1 |
6757411 | Chau | Jun 2004 | B2 |
6765470 | Shinzaki | Jul 2004 | B2 |
6766040 | Catalano et al. | Jul 2004 | B1 |
6775776 | Vogt et al. | Aug 2004 | B1 |
6786397 | Silverbrook et al. | Sep 2004 | B2 |
6819219 | Bolle et al. | Nov 2004 | B1 |
6832317 | Strongin et al. | Dec 2004 | B1 |
6836843 | Seroussi et al. | Dec 2004 | B2 |
6839688 | Drummond et al. | Jan 2005 | B2 |
6844660 | Scott | Jan 2005 | B2 |
6848052 | Hamid et al. | Jan 2005 | B2 |
6850147 | Prokoski et al. | Feb 2005 | B2 |
6850252 | Hoffberg | Feb 2005 | B1 |
6853739 | Kyle | Feb 2005 | B2 |
6857073 | French et al. | Feb 2005 | B2 |
6862443 | Witte | Mar 2005 | B2 |
6870946 | Teng et al. | Mar 2005 | B1 |
6870966 | Silverbrook et al. | Mar 2005 | B1 |
6871193 | Campbell et al. | Mar 2005 | B1 |
6871287 | Ellingson | Mar 2005 | B1 |
6871784 | Jayaratne | Mar 2005 | B2 |
6876757 | Yau et al. | Apr 2005 | B2 |
6877097 | Hamid et al. | Apr 2005 | B2 |
6879243 | Booth et al. | Apr 2005 | B1 |
6879710 | Hinoue et al. | Apr 2005 | B1 |
6879966 | Lapsley et al. | Apr 2005 | B1 |
6880749 | Green et al. | Apr 2005 | B1 |
6880750 | Pentel | Apr 2005 | B2 |
6883709 | Joseph | Apr 2005 | B2 |
6886096 | Appenzeller et al. | Apr 2005 | B2 |
6886101 | Glazer et al. | Apr 2005 | B2 |
6886104 | McClurg et al. | Apr 2005 | B1 |
6888445 | Gotfried et al. | May 2005 | B2 |
6898577 | Johnson | May 2005 | B1 |
6901154 | Dunn | May 2005 | B2 |
6901155 | Xia et al. | May 2005 | B2 |
6901266 | Henderson | May 2005 | B2 |
6901382 | Richards et al. | May 2005 | B1 |
6941001 | Bolle et al. | Sep 2005 | B1 |
6960734 | Park | Nov 2005 | B1 |
6961738 | Uchida | Nov 2005 | B1 |
6980081 | Anderson | Dec 2005 | B2 |
6985502 | Bunton | Jan 2006 | B2 |
7020270 | Ghassabian | Mar 2006 | B1 |
7030860 | Hsu et al. | Apr 2006 | B1 |
7057607 | Mayoraz et al. | Jun 2006 | B2 |
7102617 | Gust | Sep 2006 | B2 |
7124300 | Lemke | Oct 2006 | B1 |
7124433 | Little | Oct 2006 | B2 |
7137553 | Register, Jr. et al. | Nov 2006 | B2 |
7151843 | Rui et al. | Dec 2006 | B2 |
7174462 | Pering et al. | Feb 2007 | B2 |
7190816 | Mitsuyu et al. | Mar 2007 | B2 |
7203347 | Hamid | Apr 2007 | B2 |
7236576 | Schnarel et al. | Jun 2007 | B2 |
7239728 | Choi et al. | Jul 2007 | B1 |
7263670 | Rekimoto | Aug 2007 | B2 |
7286063 | Gauthey et al. | Oct 2007 | B2 |
7346778 | Guiter et al. | Mar 2008 | B1 |
7346779 | Leeper | Mar 2008 | B2 |
7347361 | Lovett | Mar 2008 | B2 |
7395506 | Tan et al. | Jul 2008 | B2 |
7420546 | Abdallah et al. | Sep 2008 | B2 |
7480870 | Anzures et al. | Jan 2009 | B2 |
7486810 | Accapadi | Feb 2009 | B1 |
7525537 | Abdallah et al. | Apr 2009 | B2 |
7626598 | Manchester | Dec 2009 | B2 |
7627904 | Tokkonen | Dec 2009 | B2 |
7630522 | Popp et al. | Dec 2009 | B2 |
7633076 | Huppi et al. | Dec 2009 | B2 |
7676748 | Barrus et al. | Mar 2010 | B1 |
7688314 | Abdallah et al. | Mar 2010 | B2 |
7689013 | Shinzaki | Mar 2010 | B2 |
7705737 | Senga | Apr 2010 | B2 |
7730401 | Gillespie et al. | Jun 2010 | B2 |
7734930 | Kirovski et al. | Jun 2010 | B2 |
7738916 | Fukuda | Jun 2010 | B2 |
7810105 | Prabandham et al. | Oct 2010 | B2 |
7810720 | Lovett | Oct 2010 | B2 |
7860536 | Jobs et al. | Dec 2010 | B2 |
RE42038 | Abdallah et al. | Jan 2011 | E |
7921297 | Ortiz et al. | Apr 2011 | B2 |
8006299 | Suominen | Aug 2011 | B2 |
8018440 | Townsend et al. | Sep 2011 | B2 |
8023700 | Riionheimo | Sep 2011 | B2 |
8095634 | Rao | Jan 2012 | B2 |
8095879 | Goertz | Jan 2012 | B2 |
8145912 | McLean | Mar 2012 | B2 |
8190907 | Tu | May 2012 | B2 |
8300023 | Forutanpour et al. | Oct 2012 | B2 |
8311514 | Bandyopadhyay et al. | Nov 2012 | B2 |
8336086 | Seo | Dec 2012 | B2 |
8352745 | McKeeth | Jan 2013 | B2 |
8358200 | Madhvanath et al. | Jan 2013 | B2 |
8395658 | Corson | Mar 2013 | B2 |
8438400 | Hoghaug et al. | May 2013 | B2 |
8443199 | Kim et al. | May 2013 | B2 |
8788838 | Fadell et al. | Jul 2014 | B1 |
8943580 | Fadell et al. | Jan 2015 | B2 |
9038167 | Fadell et al. | May 2015 | B2 |
9128601 | Fadell et al. | Sep 2015 | B2 |
9134896 | Fadell et al. | Sep 2015 | B2 |
9179298 | Jung et al. | Nov 2015 | B2 |
9250795 | Fadell et al. | Feb 2016 | B2 |
9274647 | Fadell et al. | Mar 2016 | B2 |
9304624 | Fadell et al. | Apr 2016 | B2 |
9329771 | Fadell et al. | May 2016 | B2 |
9342674 | Abdallah et al. | May 2016 | B2 |
9495531 | Fadell et al. | Nov 2016 | B2 |
9519771 | Fadell et al. | Dec 2016 | B2 |
20010012022 | Smith | Aug 2001 | A1 |
20010031072 | Dobashi et al. | Oct 2001 | A1 |
20010044906 | Kanevsky et al. | Nov 2001 | A1 |
20010047488 | Verplaetse et al. | Nov 2001 | A1 |
20020015024 | Westerman et al. | Feb 2002 | A1 |
20020095588 | Shigematsu et al. | Jul 2002 | A1 |
20020122026 | Bergstrom | Sep 2002 | A1 |
20020130841 | Scott | Sep 2002 | A1 |
20020141586 | Margalit et al. | Oct 2002 | A1 |
20020146157 | Goodman et al. | Oct 2002 | A1 |
20020190960 | Kuo et al. | Dec 2002 | A1 |
20020191029 | Gillespie et al. | Dec 2002 | A1 |
20020196274 | Comfort et al. | Dec 2002 | A1 |
20030046557 | Miller et al. | Mar 2003 | A1 |
20030048173 | Shigematsu et al. | Mar 2003 | A1 |
20030115490 | Russo et al. | Jun 2003 | A1 |
20030118217 | Kondo et al. | Jun 2003 | A1 |
20030120934 | Ortiz | Jun 2003 | A1 |
20030132974 | Bodin | Jul 2003 | A1 |
20030138136 | Umezaki et al. | Jul 2003 | A1 |
20030142138 | Brown et al. | Jul 2003 | A1 |
20030163710 | Ortiz et al. | Aug 2003 | A1 |
20030188183 | Lee | Oct 2003 | A1 |
20030195935 | Leeper | Oct 2003 | A1 |
20030206202 | Moriya | Nov 2003 | A1 |
20030210127 | Anderson | Nov 2003 | A1 |
20030222913 | Mattila et al. | Dec 2003 | A1 |
20040030934 | Mizoguchi et al. | Feb 2004 | A1 |
20040034801 | Jaeger | Feb 2004 | A1 |
20040042542 | Kawada et al. | Mar 2004 | A1 |
20040076310 | Hersch et al. | Apr 2004 | A1 |
20040085300 | Matusis | May 2004 | A1 |
20040085351 | Tokkonen | May 2004 | A1 |
20040088568 | Tokkonen | May 2004 | A1 |
20040104268 | Bailey | Jun 2004 | A1 |
20040131237 | Machida | Jul 2004 | A1 |
20040135801 | Thompson et al. | Jul 2004 | A1 |
20040172562 | Berger et al. | Sep 2004 | A1 |
20040196400 | Stavely et al. | Oct 2004 | A1 |
20040229560 | Maloney | Nov 2004 | A1 |
20040230843 | Jansen | Nov 2004 | A1 |
20040239648 | Abdallah et al. | Dec 2004 | A1 |
20040250138 | Schneider | Dec 2004 | A1 |
20040260955 | Mantyla | Dec 2004 | A1 |
20040268267 | Moravcsik | Dec 2004 | A1 |
20050024341 | Gillespie et al. | Feb 2005 | A1 |
20050040962 | Funkhouser et al. | Feb 2005 | A1 |
20050041841 | Yoo et al. | Feb 2005 | A1 |
20050050477 | Robertson et al. | Mar 2005 | A1 |
20050058438 | Hayashi | Mar 2005 | A1 |
20050060554 | O'Donoghue | Mar 2005 | A1 |
20050071635 | Furuyama | Mar 2005 | A1 |
20050078855 | Chandler et al. | Apr 2005 | A1 |
20050079896 | Kokko et al. | Apr 2005 | A1 |
20050093834 | Abdallah et al. | May 2005 | A1 |
20050097171 | Hikichi | May 2005 | A1 |
20050097608 | Penke et al. | May 2005 | A1 |
20050100198 | Nakano et al. | May 2005 | A1 |
20050111708 | Chou | May 2005 | A1 |
20050113071 | Nagata | May 2005 | A1 |
20050114686 | Ball et al. | May 2005 | A1 |
20050169503 | Howell et al. | Aug 2005 | A1 |
20050174325 | Setlak | Aug 2005 | A1 |
20050175226 | Yamamoto | Aug 2005 | A1 |
20050206501 | Farhat | Sep 2005 | A1 |
20050212760 | Marvit et al. | Sep 2005 | A1 |
20050216862 | Shinohara et al. | Sep 2005 | A1 |
20050216867 | Marvit et al. | Sep 2005 | A1 |
20050221798 | Sengupta et al. | Oct 2005 | A1 |
20050226472 | Komura | Oct 2005 | A1 |
20050248542 | Sawanobori | Nov 2005 | A1 |
20050253817 | Rytivaara et al. | Nov 2005 | A1 |
20050254086 | Shouno | Nov 2005 | A1 |
20050264833 | Hiraoka et al. | Dec 2005 | A1 |
20050289476 | Tokkonen | Dec 2005 | A1 |
20060021003 | Fisher et al. | Jan 2006 | A1 |
20060031776 | Glein et al. | Feb 2006 | A1 |
20060032908 | Sines | Feb 2006 | A1 |
20060075250 | Liao | Apr 2006 | A1 |
20060078176 | Abiko et al. | Apr 2006 | A1 |
20060080525 | Ritter et al. | Apr 2006 | A1 |
20060093183 | Hosoi | May 2006 | A1 |
20060093192 | Bechtel | May 2006 | A1 |
20060095369 | Hofi | May 2006 | A1 |
20060115130 | Kozlay | Jun 2006 | A1 |
20060116555 | Pavlidis et al. | Jun 2006 | A1 |
20060136087 | Higashiura | Jun 2006 | A1 |
20060136734 | Telek et al. | Jun 2006 | A1 |
20060156028 | Aoyama et al. | Jul 2006 | A1 |
20060161870 | Hotelling et al. | Jul 2006 | A1 |
20060174339 | Tao | Aug 2006 | A1 |
20060214910 | Mizuno et al. | Sep 2006 | A1 |
20060224645 | Kadi | Oct 2006 | A1 |
20060239517 | Creasey et al. | Oct 2006 | A1 |
20060255153 | Cheng et al. | Nov 2006 | A1 |
20060267955 | Hino | Nov 2006 | A1 |
20060274920 | Tochikubo et al. | Dec 2006 | A1 |
20060284853 | Shapiro | Dec 2006 | A1 |
20060285663 | Rathus et al. | Dec 2006 | A1 |
20060288234 | Azar et al. | Dec 2006 | A1 |
20060289638 | Schilling | Dec 2006 | A1 |
20070008066 | Fukuda | Jan 2007 | A1 |
20070014439 | Ando | Jan 2007 | A1 |
20070016958 | Bodepudi | Jan 2007 | A1 |
20070021194 | Aida | Jan 2007 | A1 |
20070061126 | Russo et al. | Mar 2007 | A1 |
20070061889 | Sainaney | Mar 2007 | A1 |
20070067642 | Singhal | Mar 2007 | A1 |
20070089164 | Gao et al. | Apr 2007 | A1 |
20070106942 | Sanaka et al. | May 2007 | A1 |
20070109274 | Reynolds | May 2007 | A1 |
20070110287 | Kim et al. | May 2007 | A1 |
20070150826 | Anzures et al. | Jun 2007 | A1 |
20070150842 | Chaudhri et al. | Jun 2007 | A1 |
20070177803 | Elias et al. | Aug 2007 | A1 |
20070189583 | Shimada et al. | Aug 2007 | A1 |
20070204037 | Kunz et al. | Aug 2007 | A1 |
20070208743 | Sainaney | Sep 2007 | A1 |
20070220273 | Campisi | Sep 2007 | A1 |
20070226778 | Pietruszka | Sep 2007 | A1 |
20070236330 | Cho et al. | Oct 2007 | A1 |
20070236475 | Wherry | Oct 2007 | A1 |
20070239921 | Toorians et al. | Oct 2007 | A1 |
20070250573 | Rothschild | Oct 2007 | A1 |
20070253604 | Inoue et al. | Nov 2007 | A1 |
20070259716 | Mattice et al. | Nov 2007 | A1 |
20070273658 | Yli-Nokari et al. | Nov 2007 | A1 |
20070273670 | Nordahl | Nov 2007 | A1 |
20070277224 | Osborn et al. | Nov 2007 | A1 |
20070280515 | Goto | Dec 2007 | A1 |
20080001703 | Goto | Jan 2008 | A1 |
20080032801 | Brunet de Courssou | Feb 2008 | A1 |
20080034292 | Brunner et al. | Feb 2008 | A1 |
20080034307 | Cisler et al. | Feb 2008 | A1 |
20080042979 | Nikbin | Feb 2008 | A1 |
20080042983 | Kim et al. | Feb 2008 | A1 |
20080048878 | Boillot | Feb 2008 | A1 |
20080055263 | Lemay et al. | Mar 2008 | A1 |
20080055269 | Lemay et al. | Mar 2008 | A1 |
20080069412 | Champagne et al. | Mar 2008 | A1 |
20080072045 | Mizrah | Mar 2008 | A1 |
20080072172 | Shinohara et al. | Mar 2008 | A1 |
20080082934 | Kocienda et al. | Apr 2008 | A1 |
20080092245 | Alward et al. | Apr 2008 | A1 |
20080094371 | Forstall et al. | Apr 2008 | A1 |
20080122796 | Jobs et al. | May 2008 | A1 |
20080133931 | Kosaka | Jun 2008 | A1 |
20080134170 | Astheimer | Jun 2008 | A1 |
20080165255 | Christie et al. | Jul 2008 | A1 |
20080168290 | Jobs et al. | Jul 2008 | A1 |
20080178283 | Pratt et al. | Jul 2008 | A1 |
20080250481 | Beck et al. | Oct 2008 | A1 |
20080292144 | Kim | Nov 2008 | A1 |
20080309632 | Westerman et al. | Dec 2008 | A1 |
20080314971 | Faith et al. | Dec 2008 | A1 |
20080317292 | Baker et al. | Dec 2008 | A1 |
20090005165 | Arezina et al. | Jan 2009 | A1 |
20090006292 | Block | Jan 2009 | A1 |
20090006846 | Rosenblatt | Jan 2009 | A1 |
20090006991 | Lindberg et al. | Jan 2009 | A1 |
20090007017 | Anzures et al. | Jan 2009 | A1 |
20090037742 | Narayanaswami | Feb 2009 | A1 |
20090043180 | Tschautscher et al. | Feb 2009 | A1 |
20090063352 | Kaufman | Mar 2009 | A1 |
20090064055 | Chaudhri et al. | Mar 2009 | A1 |
20090067685 | Boshra et al. | Mar 2009 | A1 |
20090074255 | Holm | Mar 2009 | A1 |
20090083847 | Fadell et al. | Mar 2009 | A1 |
20090128581 | Brid et al. | May 2009 | A1 |
20090153474 | Quennesson | Jun 2009 | A1 |
20090169070 | Fadell | Jul 2009 | A1 |
20090176565 | Kelly | Jul 2009 | A1 |
20090195506 | Geidl et al. | Aug 2009 | A1 |
20090201257 | Saitoh et al. | Aug 2009 | A1 |
20090213087 | Abdallah et al. | Aug 2009 | A1 |
20090215497 | Louch | Aug 2009 | A1 |
20090224874 | Dewar et al. | Sep 2009 | A1 |
20090241072 | Chaudhri et al. | Sep 2009 | A1 |
20090244019 | Choi | Oct 2009 | A1 |
20090258667 | Suzuki | Oct 2009 | A1 |
20090284482 | Chin | Nov 2009 | A1 |
20090328162 | Kokumai et al. | Dec 2009 | A1 |
20100008545 | Ueki et al. | Jan 2010 | A1 |
20100034432 | Ono et al. | Feb 2010 | A1 |
20100053301 | Ryu et al. | Mar 2010 | A1 |
20100053661 | Ushiku | Mar 2010 | A1 |
20100076823 | Feldman et al. | Mar 2010 | A1 |
20100079380 | Nurmi | Apr 2010 | A1 |
20100134248 | Adams et al. | Jun 2010 | A1 |
20100162180 | Dunnam et al. | Jun 2010 | A1 |
20100164684 | Sasa et al. | Jul 2010 | A1 |
20100164864 | Chou | Jul 2010 | A1 |
20100182125 | Abdallah et al. | Jul 2010 | A1 |
20100208953 | Gardner et al. | Aug 2010 | A1 |
20100225607 | Kim | Sep 2010 | A1 |
20100231356 | Kim | Sep 2010 | A1 |
20100235732 | Bergman | Sep 2010 | A1 |
20100237991 | Prabhu et al. | Sep 2010 | A1 |
20100240415 | Kim et al. | Sep 2010 | A1 |
20100245553 | Schuler et al. | Sep 2010 | A1 |
20100265204 | Tsuda | Oct 2010 | A1 |
20100302016 | Zaborowski | Dec 2010 | A1 |
20100306718 | Shim et al. | Dec 2010 | A1 |
20100313263 | Uchida et al. | Dec 2010 | A1 |
20110010672 | Hope | Jan 2011 | A1 |
20110013813 | Yamamoto et al. | Jan 2011 | A1 |
20110169743 | Oh et al. | Jul 2011 | A1 |
20110170750 | Kropp et al. | Jul 2011 | A1 |
20110175807 | Grover | Jul 2011 | A1 |
20110179387 | Shaffer et al. | Jul 2011 | A1 |
20110283241 | Miller et al. | Nov 2011 | A1 |
20110285648 | Simon | Nov 2011 | A1 |
20110300829 | Nurmi et al. | Dec 2011 | A1 |
20120009896 | Bandyopadhyay et al. | Jan 2012 | A1 |
20120021724 | Olsen et al. | Jan 2012 | A1 |
20120023458 | Chaudhri et al. | Jan 2012 | A1 |
20120047574 | Kim et al. | Feb 2012 | A1 |
20120081363 | Kang et al. | Apr 2012 | A1 |
20120105081 | Shaikh et al. | May 2012 | A1 |
20120182226 | Tuli | Jul 2012 | A1 |
20120182253 | Brosnan | Jul 2012 | A1 |
20120188206 | Sparf et al. | Jul 2012 | A1 |
20130201155 | Wu et al. | Aug 2013 | A1 |
20140112555 | Fadell et al. | Apr 2014 | A1 |
20140115695 | Fadell et al. | Apr 2014 | A1 |
20140304809 | Fadell et al. | Oct 2014 | A1 |
20140380465 | Fadell et al. | Dec 2014 | A1 |
20150095174 | Dua | Apr 2015 | A1 |
20150135108 | Pope et al. | May 2015 | A1 |
20150178548 | Abdallah et al. | Jun 2015 | A1 |
20160154956 | Fadell et al. | Jun 2016 | A1 |
20170199997 | Fadell et al. | Jul 2017 | A1 |
Number | Date | Country |
---|---|---|
1220433 | Jun 1999 | CN |
1685357 | Oct 2005 | CN |
1742252 | Mar 2006 | CN |
1801708 | Jul 2006 | CN |
1836397 | Sep 2006 | CN |
100999961 | Jul 2007 | CN |
101035335 | Sep 2007 | CN |
10153591 | May 2003 | DE |
0593386 | Apr 1994 | EP |
0923018 | Jun 1999 | EP |
1043698 | Oct 2000 | EP |
1257111 | Nov 2002 | EP |
1284450 | Feb 2003 | EP |
1422589 | May 2004 | EP |
1626330 | Feb 2006 | EP |
1736908 | Dec 2006 | EP |
2060970 | May 2009 | EP |
2388734 | Nov 2011 | EP |
2184576 | Jun 1987 | GB |
2312040 | Oct 1997 | GB |
2313460 | Nov 1997 | GB |
2360618 | Sep 2001 | GB |
60-171560 | Sep 1985 | JP |
2-249062 | Oct 1990 | JP |
4-158434 | Jun 1992 | JP |
5-127819 | May 1993 | JP |
6-214954 | Aug 1994 | JP |
7-84661 | Mar 1995 | JP |
7-234837 | Sep 1995 | JP |
8-263215 | Oct 1996 | JP |
9-018566 | Jan 1997 | JP |
10-011216 | Jan 1998 | JP |
10-63424 | Mar 1998 | JP |
10-63427 | Mar 1998 | JP |
11-185016 | Jul 1999 | JP |
11-203045 | Jul 1999 | JP |
2000-090052 | Mar 2000 | JP |
2000-250862 | Sep 2000 | JP |
2000-276245 | Oct 2000 | JP |
2000-293253 | Oct 2000 | JP |
2000-315118 | Nov 2000 | JP |
2000-322199 | Nov 2000 | JP |
2000-339097 | Dec 2000 | JP |
2000-349886 | Dec 2000 | JP |
2001-14051 | Jan 2001 | JP |
2001-092554 | Apr 2001 | JP |
2001-510579 | Jul 2001 | JP |
2002-159052 | May 2002 | JP |
2002-207525 | Jul 2002 | JP |
2002-525718 | Aug 2002 | JP |
2002-352234 | Dec 2002 | JP |
2002-358162 | Dec 2002 | JP |
2003-067343 | Mar 2003 | JP |
2003-085540 | Mar 2003 | JP |
2003-091370 | Mar 2003 | JP |
2003-143290 | May 2003 | JP |
2003-298689 | Oct 2003 | JP |
2004-157821 | Jun 2004 | JP |
2004-172851 | Jun 2004 | JP |
2004-252720 | Sep 2004 | JP |
2004-532477 | Oct 2004 | JP |
2004-313459 | Nov 2004 | JP |
2004-334788 | Nov 2004 | JP |
2004-348599 | Dec 2004 | JP |
2005-004490 | Jan 2005 | JP |
2005-056152 | Mar 2005 | JP |
2005-071008 | Mar 2005 | JP |
2005-071225 | Mar 2005 | JP |
2005-122700 | May 2005 | JP |
2005-167455 | Jun 2005 | JP |
2005175555 | Jun 2005 | JP |
2006-072872 | Mar 2006 | JP |
2006-085559 | Mar 2006 | JP |
2006-92428 | Apr 2006 | JP |
2006-115043 | Apr 2006 | JP |
2006-121334 | May 2006 | JP |
2006-146579 | Jun 2006 | JP |
2006-157154 | Jun 2006 | JP |
2006-202278 | Aug 2006 | JP |
2006-215705 | Aug 2006 | JP |
2006-301201 | Nov 2006 | JP |
2007-026011 | Feb 2007 | JP |
2007-097820 | Apr 2007 | JP |
2007-148801 | Jun 2007 | JP |
2007-293628 | Nov 2007 | JP |
2008-186320 | Aug 2008 | JP |
2009-171234 | Jul 2009 | JP |
2011-048523 | Mar 2011 | JP |
2011-059233 | Mar 2011 | JP |
10-2002-0087665 | Nov 2002 | KR |
10-2003-0005535 | Jan 2003 | KR |
10-2004-0025004 | Mar 2004 | KR |
10-2004-0076639 | Sep 2004 | KR |
10-2006-0003689 | Jan 2006 | KR |
10-0652624 | Dec 2006 | KR |
10-2007-0026808 | Mar 2007 | KR |
10-2010-0059698 | Jun 2010 | KR |
10-2010-0111121 | Oct 2010 | KR |
10-2011-0058525 | Jun 2011 | KR |
10-2011-0103598 | Sep 2011 | KR |
10-2012-0042684 | May 2012 | KR |
2005-29636 | Sep 2005 | TW |
2006-01176 | Jan 2006 | TW |
200-642408 | Dec 2006 | TW |
M317045 | Aug 2007 | TW |
9858346 | Dec 1998 | WO |
0016244 | Mar 2000 | WO |
0141032 | Jun 2001 | WO |
0159558 | Aug 2001 | WO |
0163386 | Aug 2001 | WO |
0177792 | Oct 2001 | WO |
0180017 | Oct 2001 | WO |
0233882 | Apr 2002 | WO |
03038569 | May 2003 | WO |
04001560 | Dec 2003 | WO |
2004021108 | Mar 2004 | WO |
2004029862 | Apr 2004 | WO |
2004109454 | Dec 2004 | WO |
2005008568 | Jan 2005 | WO |
2005020036 | Mar 2005 | WO |
2005041020 | May 2005 | WO |
2005106774 | Nov 2005 | WO |
2006051462 | May 2006 | WO |
2007060102 | May 2007 | WO |
2007070014 | Jun 2007 | WO |
2007072447 | Jun 2007 | WO |
2007076210 | Jul 2007 | WO |
2008008101 | Jan 2008 | WO |
2009085338 | Jul 2009 | WO |
2011099803 | Aug 2011 | WO |
2012054350 | Apr 2012 | WO |
Entry |
---|
Corrected Notice of Allowance received for U.S. Appl. No. 15/017,436, dated Sep. 2, 2016, 5 pages. |
Notice of Allowance received for Australian Patent Application No. 2015202397, dated Feb. 15, 2017, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2013-098406, dated Jan. 23, 2017, 18 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
Notice of Allowance received for Japanese Patent Application No. 2015-083696, dated Jan. 6, 2017, 3 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
Notice of Allowance received for Japanese Patent Application No. 2015-512913, dated Sep. 9, 2016, 3 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
Notice of Allowance received for Japanese Patent Application No. 2017-013383, dated Mar. 31, 2017, 3 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
Notice of Allowance received for Korean Patent Application No. 1020147035557, dated Dec. 21, 2016, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 15/017,436, dated May 27, 2016, 17 pages. |
Office Action received for Australian Patent Application No. 2012200716, dated Nov. 15, 2013, 3 pages. |
Office Action received for Australian Patent Application No. 2013262488, dated Aug. 28, 2015, 5 pages. |
Office Action received for Australian Patent Application No. 2016203896, dated Mar. 6, 2017, 3 Pages. |
Office Action received for Australian Patent Application No. 2016203898, dated Feb. 17, 2017, 3 Pages. |
Office Action received for Chinese Patent Application No. 201410407626.4, dated Oct. 31, 2016, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
Office Action received for European Patent Application No. 15168475,0, dated Dec. 19, 2016, 5 pages. |
Office Action received for Japanese Patent Application No. 2014-242264, dated Feb. 24, 2017, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2015-512913, dated Feb. 26, 2016, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2014-7035557, dated Feb. 16, 2016, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2015-7010262, dated Mar. 8, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
“Windows Mobile Protege G500/G900”, 2007, 4 pages. |
Advisory Action received for U.S. Appl. No. 12/207,374, dated Feb. 25, 2013, 3 pages. |
Advisory Action received for U.S. Appl. No. 12/207,374, dated May 15, 2014, 3 pages. |
Advisory Action received for U.S. Appl. No. 14/311,214, dated Feb. 10, 2015, 4 pages. |
Avatron, “Air Display”, available at <https://play.google.com/store/apps/details?id=com.avatron.airdisplay&feature-nay_result>, updated on Dec. 26, 2013, 2013, 2 pages. |
Bardram, Jakob E., “The Trouble with Login: on Usability and Computer Security in Ubiquitous Computing”, Journal Personal and Ubiquitous Computing, vol. 9, Jul. 23, 2005, pp. 357-367. |
Baudisch et al., “Phosphor: Explaining Transitions in the User Interface Using Afterglow Effects”, Proceedings of the 19th Annual ACM Symposium on User Interface Software and Technology, Oct. 15-18, 2006, pp. 169-178. |
Certificate of Grant received for Australian Patent Application No. 2011101192, Apr. 12, 2012, 1 page. |
Certificate of Grant received for Australian Patent Application No. 2011101193, Apr. 23, 2012, 1 page. |
Chang, “Fingerprint Spoof Detection Using Near Infrared Optical Analysis”, Department of Biomedical Engineering, University of Houston, 2011, 29 pages. |
Chen, Y., “Unlock Smartphone with a Quick Palm Scan”, Available online at <http://www.psfk.com/2012/10/unlock-smartphone-palm-scan.html#?Nlyhq>, 2012, 2 pages. |
Dailytech, “Analysis: Neonode Patented Swipe-to-Unlock 3 Years Before Apple”, available at <http://www.dailytech.com/Analysis+Neonode+Patented+SwipetoUnlock+3+Years+Before+Apple/article24046.htm>, Feb. 20, 2012, 4 pages. |
Decision from Intellectual Property Tribunal received for Korean Patent Application No. 10-2011-7023152, dated Feb. 17, 2015, 22 pages. |
Decision to Grant received for European Patent Application No. 04753978.8, dated Apr. 16, 2015, 2 pages. |
Decision to Grant received for the European Patent Application No. 12181538.5, dated Jul. 2, 2015, 1 page. |
Decision to Refusal received for Japanese Patent Application No. 2013-145795, dated Mar. 4, 2016, 8 pages. |
Decision to Refuse received for European Patent Application No. 08834386.8, dated Apr. 8, 2013, 8 pages. |
European Search Report received for European Patent Application No. 04753978.8, dated Feb. 22, 2010, 3 pages. |
Examination Report received for Australian Patent Application No. 2015202397, dated Feb. 29, 2016, 4 pages. |
Examiner Interview Summary received for U.S. Appl. No. 12/732,946, dated Jan. 26, 2015, 4 pages. |
Examiner's Pre-Review Report received for Japanese Patent Application No. 2013-098406, dated Oct. 8, 2015, 7 pages. |
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 13171145.9, dated Feb. 5, 2014, 6 pages. |
Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 15168475.0, dated Oct. 21, 2015, 6 pages. |
Extended European Search Report and Search opinion received for European Patent Application No. 09170574.9, dated Oct. 13, 2009, 8 pages. |
Extended European Search Report and Search Opinion received for European Patent Application No. 10194359.5, dated Feb. 7, 2011, 9 pages. |
Extended European Search Report received for European Patent Application No. 12181538.5, dated Oct. 23, 2012, 6 pages. |
Final Office Action received for U.S. Appl. No. 10/997,291, dated Jan. 2, 2008, 5 pages. |
Final Office Action received for U.S. Appl. No. 11/322,549, dated Mar. 23, 2009, 39 pages. |
Final Office Action received for U.S. Appl. No. 11/322,549, dated Sep. 26, 2008, 30 pages. |
Final Office Action received for U.S. Appl. No. 12/207,370, dated Dec. 13, 2011, 15 pages. |
Final Office Action received for U.S. Appl. No. 12/207,370, dated Feb. 15, 2013, 17 pages. |
Final Office Action received for U.S. Appl. No. 12/207,374, dated Jan. 31, 2014, 12 pages. |
Final Office Action received for U.S. Appl. No. 12/207,374, dated Nov. 6, 2012, 25 pages. |
Final Office Action received for U.S. Appl. No. 12/207,374, dated Oct. 21, 2011, 16 pages. |
Final Office Action received for U.S. Appl. No. 12/477,075, dated Sep. 17, 2010, 9 pages. |
Final Office Action received for U.S. Appl. No. 12/732,946, dated Oct. 9, 2014, 34 pages. |
Final Office Action received for U.S. Appl. No. 14/142,669, dated Jun. 12, 2015, 14 pages. |
Final Office Action received for U.S. Appl. No. 14/311,214, dated Jan. 8, 2015, 12 pages. |
Final Office Action received for U.S. Appl. No. 14/311,214, dated Sep. 24, 2015, 15 pages. |
Final Office Action received for U.S. Appl. No. 14/479,088, dated Mar. 11, 2015, 10 pages. |
Final Office Action received for U.S. Appl. No. 14/640,020, dated Jul. 16, 2015, 26 pages. |
Fitzpatrick et al., “Method for Access Control via Gestural Verification”, IBM Technical Disclosure Bulletin, vol. 36, No. 9B, Sep. 1993, pp. 487-488. |
Gridlock 1.32, “Graphical Security System for your Palm”, available at <http://gridlock.en.softonic.com/palm>, Oct. 8, 2003, 2 pages. |
Horry et al., “A Passive-Style Buttonless Mobile Terminal”, IEEE Transactions on Consumer Electronics, vol. 49, No. 3, Aug. 2003, pp. 530-535. |
HTC Europe Co. Ltd. vs Apple Inc., Nullity Reply Brief filed on Nov. 8, 2012, 17 pages. |
IBM, “Touch Pad Authentication”, Sep. 21, 2004, 2 pages. |
Idapps, “BioPhotos and Bio Secrets”, Available online at <http://www.idapps.com/index>, retrieved on Jan. 2011, 6 pages. |
Intention to Grant received for European Patent Application No. 04753978.8, dated Dec. 4, 2014, 5 pages. |
Intention to Grant received for European Patent Application No. 12181538.5, dated Feb. 20, 2015, 8 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2004/017270, dated Jul. 23, 2013, 3 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/075738, dated Jan. 28, 2010, 15 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/041868, dated Nov. 27, 2014, 6 pages. |
International Search Report and Written Opinion received for PCT Application No. PCT/US2006/061370, dated May 25, 2007, 9 pages. |
International Search Report and Written Opinion received for PCT Application No. PCT/US2006/061380, dated Apr. 23, 2007, 7 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2004/017270, dated Dec. 1, 2004, 6 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2008/075738, dated Jul. 2, 2009, 14 pages. |
Jansen, Wayne A., “Authenticating Users on Handheld Devices”, Contribution of the National Institute of Standards and Technology, 2003, 13 pages. |
Jermyn et al., “The Design and Analysis of Graphical Password”, Proceedings of the 8th USENIX Security Symposium, Aug. 23-26, 1999, 15 pages. |
Jgui Professional, “Touch Password Protection”, available at <http://www.jgui.net/touch/index.html>, retrieved on Dec. 30, 2005, 4 pages. |
Mclean et al., “Access/Control Icons (Icon Keys)”, IBM Technical Disclosure Bulletin, vol. 38, No. 4, Apr. 1995, pp. 407-409. |
Monrose, Newman F., “Towards Stronger User Authentication”, A Dissertation Submitted in Partial Fulfilment of the Requirements for the Degree of Doctor of Philosophy Department of Computer Science, New York University, May 1999, 130 pages. |
Najjar, Lawrence J., “Graphical Passwords”, International Technology Disclosures, vol. 10, No. 1, Jan. 25, 1992, 1 page. |
Neonode Inc., “Welcome to the N1 Guide”, available at <http://www.ebookspdf.com/gadget/2818/neonode-n1m-manual/>, Jul. 2004, pp. 1-42. |
Neonode.com, “N1 Quick Start Guide”, Version 0.5, Available at <http://www.instructionsmanuals.com/download/telefonos_movil/Neonode-N1-en.pdf>, Apr. 5, 2005, pp. 1-24. |
Ni et al,, “DiffUser: Differentiated User Access Control on Smartphones”, IEEE 6th International Conference on Mobile Adhoc and Sensor Systems, 2009, pp. 1012-1017. |
Non Final Office Action received for U.S. Appl. No. 11/322,549, dated Feb. 7, 2008, 28 pages. |
Non Final Office Action received for U.S. Appl. No. 12/207,374, dated Apr. 15, 2011, 13 pages. |
Non Final Office Action received for U.S. Appl. No. 12/207,374, dated Jun. 7, 2013, 22 pages. |
Non Final Office Action received for U.S. Appl. No. 12/207,374, dated May 24, 2012, 20 pages. |
Non Final Office Action received for U.S. Appl. No. 12/345,584, dated Jul. 24, 2009, 6 pages. |
Non Final Office Action received for U.S. Appl. No. 12/345,584, dated Nov. 16, 2009, 17 pages. |
Non Final Office Action received for U.S. Appl. No. 12/477,075, dated Feb. 7, 2011, 10 pages. |
Non Final Office Action received for U.S. Appl. No. 13/204,572, dated Jan. 6, 2012, 10 pages. |
Non Final Office Action received for U.S. Appl. No. 13/250,659, dated Nov. 25, 2011, 11 pages. |
Non Final Office Action received for U.S. Appl. No. 13/563,663, dated Nov. 19, 2012, 10 pages. |
Non Final Office Action received for U.S. Appl. No. 13/791,808, dated Sep. 11, 2013, 13 pages. |
Non Final Office Action received for U.S. Appl. No. 14/311,214, dated Apr. 10, 2015, 12 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/858,290, dated Nov. 24, 2004, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 10/997,291, dated Jul. 28, 2005, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/322,550, dated Apr. 21, 2008, 22 pages. |
Non-Final Office Action received for U.S. Appl. No. 11/322,550, dated Oct. 31, 2007, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/201,568, dated Oct. 2, 2008, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/207,370, dated Aug. 2, 2012, 16 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/207,370, dated May 6, 2011, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/207,370, dated Oct. 17, 2013, Oct. 17, 2013, 17 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/430,702, dated Jun. 24, 2009, 6 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/477,075, dated Jan. 29, 2010, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 12/732,946, dated Oct. 17, 2013, 25 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/142,669, dated Oct. 28, 2015, 14 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/142,669, dated Sep. 12, 2014, 11 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/311,214, dated Sep. 18, 2014, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/479,088, dated Jul. 6, 2015, 19 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/479,088, dated Nov. 18, 2014, 8 pages. |
Non-Final Office Action received for U.S. Appl. No. 14/640,020, dated Apr. 29, 2015, 18 pages. |
Notice of Acceptance received for Australian Patent Application No. 2008305338, dated Oct. 27, 2011, 1 page. |
Notice of Acceptance received for Australian Patent Application No. 2010200661, dated Aug. 2, 2012, 3 pages. |
Notice of Allowance received for Canadian Patent Application No. 2,527,829, dated Feb. 1, 2016, 1 page. |
Notice of Allowance received for Chinese Patent Application No. 200880108306.1, dated Oct. 28, 2014, 2 pages. |
Notice of Allowance received for Japanese Patent Application No. 2006-533547, dated May 15, 2015, 2 pages. |
Notice of Allowance received for Japanese Patent Application No. 2012-091352, dated May 24, 2013, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2013-007818, dated May 31, 2013, 4 pages. |
Notice of Allowance received for Japanese Patent Application No. 2013-101691, dated Jul. 5, 2013, 4 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2010- 7008899, dated Feb. 12, 2016, 3 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2014-7004771, dated Oct. 29, 2015, 3 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2014-7004772, dated Feb. 12, 2016, 4 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2014-7004773, dated Jan. 7, 2016, 3 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2014-7025441, dated Feb. 26, 2016, 3 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2015-7004548, dated Feb. 26, 2016, 3 pages. |
Notice of Allowance received for Taiwan Patent Application No. 097134592, dated Aug. 12, 2014, 3 pages. |
Notice of Allowance received for Taiwan Patent Application No. 101107082, dated Oct. 22, 2014, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 13/563,663, dated Dec. 13, 2013, 11 pages. |
Notice of Allowance received for U.S. Appl. No. 14/640,020, dated Dec. 15, 2015, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 10/997,291, dated Jun. 27, 2008, 16 pages. |
Notice of Allowance received for U.S. Appl. No. 11/322,549, dated Aug. 10, 2009, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 11/322,550, dated Sep. 19, 2008, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 12/201,568, dated Dec. 17, 2008, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 12/207,370, dated Jun. 7, 2013, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 12/207,370, dated Mar. 6, 2014, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 12/207,374, dated Aug. 29, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 12/207,374, dated Dec. 4, 2014, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 12/345,584, dated Jun. 3, 2010, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 12/430,702, dated Nov. 16, 2009, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 12/477,075, dated Aug. 10, 2011, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 12/604,814, dated Apr. 26, 2010, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 12/604,814, dated Aug. 5, 2010, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 12/604,814, dated Nov. 12, 2010, 4 pages. |
Notice of Allowance received for U.S. Appl. No. 12/842,899, dated May 2, 2013, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 13/204,572, dated Jun. 12, 2012, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 13/250,659, dated May 11, 2012, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 13/563,663, dated Aug. 15, 2013, 11 pages. |
Notice of Allowance received for U.S. Appl. No. 13/787,712, dated Jun. 25, 2013, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/787,716, dated Sep. 5, 2013, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/791,799, dated Jun. 17, 2013, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 13/791,799, dated Oct. 30, 2013, 11 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,657, dated Jan. 8, 2015, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,657, dated Jul. 23, 2015, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,657, dated Jun. 29, 2015, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,657, dated Sep. 10, 2014, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,661, dated Aug. 3, 2015, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,661, dated Sep. 28, 2015, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,669, dated Aug. 25, 2016, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,669, dated Jun. 14, 2016, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,669, dated Sep. 21, 2016, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,674, dated Feb. 18, 2015, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,674, dated Jan. 23, 2015, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,674, dated Sep. 26, 2014, 18 pages. |
Notice of Allowance received for U.S. Appl. No. 14/255,765, dated Jun. 12, 2014, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 14/479,088, dated Mar. 9, 2016, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/479,088, dated Nov. 12, 2015, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/661,796, dated Jul. 7, 2015, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 14/661,796, dated Jul. 23, 2015, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/311,214, dated Jan. 21, 2016, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 14/142,661, dated Dec. 3, 2015, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/479,088, dated Dec. 23, 2015, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 14/479,088, dated Jan. 11, 2016, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 14/873,023, dated Dec. 23, 2015, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 14/873,023, dated Jan. 14, 2016, 2 pages. |
Notice of Final Rejection received for Korean Patent Application No. 10-2014-7004773, dated Jun. 12, 2015, 6 pages. |
Notice of Preliminary Rejection received for Korean Patent Application No. 10-2014-7025441, dated Jun. 12, 2015, 9 pages. |
Notice of Preliminary Rejection received for Korean Patent Application No. 10-2015-7004548, dated Jun. 12, 2015, 8 pages. |
Notice of Preliminary Rejection received from Korean Patent Application No. 10-2015-7010262, dated Jun. 12, 2015, 5 pages. |
Office Action received for Australian Patent Application No. 2008305338, dated Mar. 21, 2011, 3 pages. |
Office Action received for Australian Patent Application No. 2008305338, dated Oct. 19, 2010, 3 pages. |
Office Action received for Australian Patent Application No. 2010200661, dated Jul. 20, 2011 , 2 pages. |
Office Action received for Australian Patent Application No. 2011101192, dated Oct. 26, 2011, 2 pages. |
Office Action received for Australian Patent Application No. 2011101193, dated Oct. 26, 2011, 2 pages. |
Office Action received for Australian Patent Application No. 2012200716, dated Jul. 16, 2014, 4 pages. |
Office Action received for Australian Patent Application No. 2012200716, dated Oct. 16, 2012, 4 pages. |
Office Action received for Australian Patent Application No. 2012254900, dated Nov. 28, 2013, 3 pages. |
Office Action received for Australian Patent Application No. 2014204462, dated May 8, 2015, 4 pages. |
Office Action received for Australian Patent Application No. 2014204462, dated Apr. 29, 2016, 3 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated Apr. 1, 2010, 4 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated Apr. 16, 2014, 3 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated Apr. 29, 2013, 3 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated Apr. 29, 2015, 6 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated Jun. 1, 2011, 3 pages. |
Office Action received for Canadian Patent Application No. 2,527,829, dated May 7, 2012, 4 pages. |
Office Action received for Chinese Patent Application No. 200680052770.4, dated Feb. 5, 2010, 4 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Aug. 9, 2012, 13 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Aug. 24, 2011, 10 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Jan. 15, 2013, 14 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Mar. 20, 2012, 8 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Mar. 27, 2014, 6 pages. |
Office Action received for Chinese Patent Application No. 200880108306.1, dated Sep. 5, 2013, 31 pages. |
Office Action received for Chinese Patent Application No. 200910175855.7, dated Jul. 26, 2011, 13 pages. |
Office Action received for Chinese Patent Application No. 200910175855.7, dated Jul. 4, 2012, 15 pages. |
Office Action received for European Patent Application No. 04753978.8, dated Jan. 31, 2013, 6 pages. |
Office Action received for European Patent Application No. 04753978.8, dated Mar. 27, 2012, 7 pages. |
Office Action received for European Patent Application No. 06846405.6, dated Mar. 25, 2009, 6 pages. |
Office Action received for European Patent Application No. 08834386.8, dated Aug. 23, 2010, 4 pages. |
Office Action received for European Patent Application No. 12181538.5, dated Dec. 16, 2013, 4 pages. |
Office Action Received for European Patent Application No. 13171145.9, dated Apr. 28, 2016, 5 pages. |
Office Action received for German Patent Application No. 112006003515.0, dated Dec. 7, 2009, 4 pages. |
Office Action received for German Patent Application No. 112006003515.0, dated Feb. 4, 2009, 6 pages. |
Office Action received for Japanese Patent Application No. 2006-533547, dated Aug. 14, 2008, 1 page. |
Office Action received for Japanese Patent Application No. 2006-533547, dated Mar. 22, 2011, 2 pages. |
Office Action received for Japanese Patent Application No. 2006-533547, dated Mar. 5, 2012, 13 pages. |
Office Action received for Japanese Patent Application No. 2006-533547, dated Nov. 25, 2009, 3 pages. |
Office Action received for Japanese Patent Application No. 2008-547675, dated Mar. 22, 2011, 5 pages. |
Office Action received for Japanese Patent Application No. 2008-547675, dated Nov. 4, 2011, 6 pages. |
Office Action received for Japanese Patent Application No. 2008-547675, dated Sep. 18, 2012, 4 pages. |
Office Action received for Japanese Patent Application No. 2010-525891, dated Jun. 12, 2012, 11 pages. |
Office Action received for Japanese Patent Application No. 2010-525891, dated Jan. 8, 2013, 4 pages. |
Office Action received for Japanese Patent Application No. 2013-007818, dated Mar. 11, 2013, 10 pages. |
Office Action received for Japanese Patent Application No. 2013-098406, dated Dec. 9, 2013, 12 pages. |
Office Action received for Japanese Patent Application No. 2013-098406, dated Dec. 15, 2014, 12 pages. |
Office Action received for Japanese Patent Application No. 2013-098406, dated Jul. 19, 2016, 10 pages. |
Office Action received for Japanese Patent Application No. 2013-145795, dated Jun. 13, 2014, 6 pages. |
Office Action received for Japanese Patent Application No. 2014-242264, dated Jul. 17, 2015, 6 pages. |
Office Action received for Japanese Patent Application No. 2014-242264, dated May 9, 2016, 10 pages. |
Office Action received for Japanese Patent Application No. 2015-083696, dated Jun. 17, 2016, 12 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated Aug. 17, 2014, 7 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated Feb. 3, 2015, 7 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated Jan. 28, 2013, 5 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated Jun. 12, 2015, 4 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated Mar. 29, 2012, 6 pages. |
Office Action received for Korean Patent Application No. 10-2010-7008899, dated May 30, 2011, 4 pages. |
Office Action received for Korean Patent Application No. 10-2011-7023152, dated Apr. 22, 2014, 6 pages. |
Office Action received for Korean Patent Application No. 10-2011-7023152, dated Sep. 23, 2013, 4 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004771, dated Apr. 22, 2014, 5 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004771, dated Jun. 12, 2015, 6 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004771, dated Oct. 21, 2014, 7 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004772, dated Apr. 22, 2014, 8 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004772, dated Oct. 21, 2014, 5 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004773, dated Apr. 22, 2014, 9 pages. |
Office Action received for Korean Patent Application No. 10-2014-7004773, dated Oct. 21, 2014, 9 pages. |
Office Action received for Korean Patent Application No. 10-2014-7025441, dated Oct. 21, 2014, 5 pages. |
Office Action received for Korean Patent Application No. 10-2015-7010262, dated May 24, 2016, 10 pages. |
Office Action received for Korean Patent Application No. 10-2008-7018109, dated Mar. 5, 2010, 5 pages. |
Office Action received for Taiwan Patent Application No. 103136545, dated May 25, 2016, 7 pages. |
Office Action received for Taiwan Patent Application No. 103136545, dated Nov. 2, 2015, 39 pages. |
Office Action received for Taiwan Patent Application No. 097134592, dated Apr. 12, 2013, 8 pages. |
Office Action received for Taiwan Patent Application No. 101107082, dated Jul. 7, 2014, 21 pages. |
Office Action received from Japanese Patent Application No. 2013-098406, dated May 8, 2015, 14 pages. |
Office Action received from Japanese Patent Application No. 2013-145795, dated May 8, 2015, 12 pages. |
Plaisant et al., “Touchscreen Toggle Design”, CHI'92, May 3-7, 1992, pp. 667-668. |
Plaisant et al., “Touchscreen Toggle Switches: Push or slide? Design Issues and Usability Study”, Technical Report CAR-TR-521, CS-TR-2557, Nov. 1990, pp. 1-10. |
Redfly, “ScreenSlider”, available at <https://play.google.com/store/apps/details?id=com.avatron.airdisplay&feature-nay_result#?t=W10>, updated on Jan. 10, 2012, 2 pages. |
Renaud et al., “My Password is Here! An investigation into Visuo-Spatial Authentication Mechanisms”, Interacting with Computers, vol. 16, 2004, pp. 1017-1041. |
Russell, David C. et al., “U.S. Appl. No. 60/474,750, filed May 30, 2003, titled “Secure Biornetric Identification Devices and Systems for Various Applications””, 87 pages. |
Samsung Electronics GmbH vs. Apple Inc., Supplement to the Cancellation Request against utility model DE 212006000081 U1, Mar. 1, 2013, Exhibits D26-D32, Mar. 1, 2013, 211 pages. |
Samsung Electronics GmbH vs. Apple, Inc., Nullity action against European Patent EP 1964022 B1 granted with effect in the Federeal Republic of Germany, Nov. 19, 2012, Exhibits D12-D21 and 125, Nov. 19, 2012, 269 pages. |
Samsung Response to the Court's Notification in the Matter of Samsung Electronics GmbH vs Apple, Inc., filed on Feb. 21, 2013, Feb. 21, 2013, 6 pages. |
Sepasian et al., “Vitality Detection in Fingerprint Identification”, Journal of WSEAS Transactions on Information Science and Applications, vol. 7, No. 4, Apr. 2010, pp. 498-507. |
Shape, “iDisplay”, available at <https://play.google.com/store/apps/details?id=com.idisplay.virtualscreen&feature=relatedapps>, updated on Dec. 27, 2012, 2 pages. |
Statement on the Preliminary Opinion in the Matter of Motorola Mobility Germany GmbH vs Apple Inc, Exhibits NK11-NK18, Feb. 21, 2013, 156 pages. |
Sugiura, “A User Interface using Fingerprint Recognition: Holding Commands and Data Objects on Fingers”, UIST '98 Proceedings of the 11th annual ACM symposium on User Interface Software and Technology, Nov. 1998, pp. 71-79. |
Summons to Attend Oral Proceedings received for European Patent Application No. 04753978.8, mailed on Jul. 3, 2014, 8 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 08834386.8, mailed on Aug. 24, 2012, 4 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 12/207,370, dated Aug. 8, 2013, 2 pages. |
Tanaka et al., “Innovative Mobile Device of Apple Finally Appeared, Mobile Phone + iPod + Internet Terminal, iPhone”, Mac Fan, vol. 15, No. 9, Japan, Nilainichi Communications Inc., Sep. 1, 2007, pp. 4-13. |
Third Party Observations received for European Patent Application No. 15168475.0, mailed on Jul. 19, 2016, 4 pages. |
Tokyo University, “Pinch: An Interface to Connect Displays Dynamically”, Tokyo University of Technology School of Media, available at <http://www2.teu.ac.jp/media/˜takashi/cmdeng/CmdEng/Pinch.html>, retrieved on Jan. 2013, 1 page. |
Translation of German Nullity Action Complaint against European Patent Application No. 1964022 (DE No. 602006012876.2), filed on Dec. 15, 2010, 37 pages. |
Uchida, K., “Fingerprint-Based Personal Identification Technology and its Application”, NEC, vol. 55, No. 3, 2002, 7 pages. |
Uchida, K., “Fingerprint-Based User Identification Using a Handy Mobile Terminal for Authentication and Enhanced User Interface”, Technical Report of IEICE, PRMU, vol. 99, No. 118, Aug. 1999, 7 pages. |
Uchida, K., “Fingerprint-Based User-Friendly Interface and Pocket-Pid for Mobile Authentication”, Proceedings of 15th International Conference on Pattern Recognition, Sep. 2000, pp. 205-209. |
Wiedenbeck et al., “PassPoints: Design and Longitudinal Evaluation of a Graphical Password System”, International Journal of Human-Computer Studies, vol. 63, 2005, pp. 102-127. |
Non Final Office Action received for U.S. Appl. No. 14/402,087, dated Jun. 8, 2017, 13 pages. |
Office Action received for Japanese Patent Application No. 2013-145795, dated Apr. 14, 2017, 18 pages (3 pages of English Translation and 15 pages of Official Copy). |
Office Action received for Australian Patent Application No. 2016219716, dated Jun. 9, 2017, 3 Pages. |
Office Action received for Korean Patent Application No. 10-2017-7015582, dated Jun. 12, 2017, 9 pages ( 4 pages of English Translation and 5 pages of Official copy). |
Non-Final Office Action received for U.S. Appl. No. 15/470,752, dated Jul. 28, 2017, 11 pages. |
Office Action received for Japanese Patent Application No. 2016-199379, dated Aug. 25, 2017, 9 pages (4 pages of English Translation and 5 pages of Official Copy Only). |
Notice of Allowance received for Taiwanese Patent Application No. 103136545, dated Nov. 27, 2017, 4 pages (1 page of English Translation of Search Report and 3 pages of Official Copy). |
Office Action received for Australian Patent Application No. 2016203898, dated Dec. 19, 2017, 4 pages. |
Office Action received for Australian Patent Application No. 2016203896, dated Jan. 19, 2018, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20170169204 A1 | Jun 2017 | US |
Number | Date | Country | |
---|---|---|---|
60995200 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14142669 | Dec 2013 | US |
Child | 15357873 | US | |
Parent | 12207374 | Sep 2008 | US |
Child | 14142669 | US |