Proof of locality for guest access
A system using locality credentials from user and verification devices to manage resource access based on location determination addresses the complexity of guest access, ensuring secure and efficient access control.
Patent Information
- Application Number
- KR1020267033389
- Authority / Receiving Office
- KR · KR
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-04-07
- Filing Date
- 2025-04-08
- Publication Date
- 2026-11-17
AI Technical Summary
Existing methods for authorizing and revoking guest access to resources are complex and cumbersome, particularly when determining the location of the guest relative to the resource owner's resources.
A system that uses locality credentials generated by user devices and verification devices to determine the location of a user within a defined locality, enabling or disabling access to resources based on trusted locality credentials.
Provides efficient and accurate management of resource access by ensuring that users are within a trusted locality before granting access, reducing complexity and enhancing security.
Smart Images

Figure PCT00001_ABST
Abstract
Description
Technology Field
[0001] Cross-reference of related applications
[0002] This application claims the benefit and priority of U.S. Regular Application No. 19 / 171,767, filed April 7, 2025, which is a conversion of U.S. Provisional Application No. 63 / 631,411, filed April 8, 2024, and the contents of each of said application are incorporated herein by reference in their entirety for all purposes. Background Technology
[0003] Techniques exist for authorizing guests to access resources and revoking guest access to the resource owner's resources. For example, a resource owner (e.g., a homeowner) may provide a guest with a physical door key to authorize access to a specific location (e.g., a home). In another example, the resource owner may provide the guest with a Wi-Fi password to allow them to access devices on the owner's Wi-Fi network. In yet another example, the homeowner may remotely unlock the door for a guest when the homeowner expects the guest to be in the house, allowing the guest to enter. Authorizing and revoking access to specific resources belonging to the resource owner can be complex and cumbersome, both when guests can access resources and / or when they cannot. Brief explanation of the drawing
[0004] FIG. 1 is a simplified block diagram of an exemplary computer system according to some embodiments. FIG. 2 is a simplified block diagram illustrating at least some exemplary techniques for providing locality of a user device according to some embodiments. FIG. 3 is a simplified block diagram illustrating at least some exemplary techniques for providing locality of a user device according to some embodiments. FIG. 4 is a simplified block diagram illustrating access control management based on proof of locality of a user device according to some embodiments. FIG. 5 is a simplified block diagram illustrating an exemplary architecture of a system used to manage resource access based on proof of locality of a user device, according to some embodiments. FIG. 6 is a simplified flowchart illustrating an exemplary process performed by a user device to demonstrate locality according to some embodiments. FIG. 7 is a simplified flowchart illustrating an exemplary process performed by a resident device to manage access to resources based on proof of locality, according to some embodiments. FIG. 8 is a simplified flowchart illustrating an exemplary process performed by a verification device to verify locality according to some embodiments. Specific details for implementing the invention
[0005] In the following description, various examples will be described. For illustrative purposes, specific configurations and details are presented to provide a complete understanding of the examples. However, it will also be apparent to those skilled in the art that the examples can be practiced without specific details. Furthermore, known features may be omitted or simplified so as not to obscure the examples being described.
[0006] In one embodiment, the techniques include receiving a first locality credential indicating that the user device is within a first locality by a first device connected to a network from the user device. The techniques further include obtaining a second locality credential indicating that the user device is within a second locality by the first device. The techniques further include determining whether the first locality credential is trusted by the first device based at least partially on a comparison of the first locality and the second locality. Based on the determination that the first locality credential is trusted, the techniques further include enabling the user device to access the network associated with the first device by the first device. In some embodiments, the first locality credential is not trusted if the first locality is not the same locality as the second locality, and based on a second determination that the first locality credential is not trusted, the techniques further include disabling access to the network by the first device.
[0007] The method further includes the step of disabling access to the network by the first device based on a second determination that the first locality credential is not trusted.
[0008] Embodiments of the present disclosure may provide techniques for managing access to resources. Certain techniques described herein may enable a user to obtain access to resources based on the user's location. Resources may be tangible or intangible. For example, resources may be locations, items, files, networks, environment devices, and / or services. Before access to resources is granted, a determination may be made to check whether the user is within a locality. A locality may be a region. A locality may be defined by physical (e.g., walls) and / or intangible boundaries (e.g., geofences).
[0009] Determining whether a user is within a locality can be accomplished by using one or more devices within the locality (e.g., the user's device, camera, biometric sensor, beacon) to check if the user is within the locality. One or more components of each device and multiple devices (e.g., sensors) can be used to check if the user is within the locality. Using one or more components of one or more devices can increase the likelihood of accurately determining that the user is within the locality. Information from one or more components of one or more devices can be referred to as locality attributes and can be included in locality credentials. Locality credentials can be processed by a locality verification system to determine whether the locality credentials are trusted.
[0010] The resident device may include a locality verification system. When the locality verification system determines that the locality credential is trusted, the user associated with the locality credential may be granted access to the resource. In certain embodiments, granting access to the resource enables the user to control the environment device (e.g., a smart lock on a door). The resident device may be coupled to communicate with the resident device and may control the environment device through the communication coupling with the resident device. In a manner similar to that described above, certain techniques described herein may enable the user and / or user device to obtain access to the resource based on where the user and / or user device are located.
[0011] FIG. 1 is a simplified block diagram of an exemplary system (100) according to some embodiments. The system (100) includes a home environment (102), a first user (112) having a first user device (114), a second user (108) having a second user device (110), a resident device (104), an environment device (118), and a verification device (116).
[0012] In the system (100), the illustrated exemplary environment is a home environment (102). The home environment (102) may include one or more people who have a sense of belonging (e.g., family members, roommates, friends, business, etc.). In this example, the first user (112) and the second user (108) may represent associated users and may be associated with the first user device (114) and the second user device (110), respectively. Additionally, within the home environment (102), there may be a resident device (104) (e.g., a tablet, a smart home controller, a smart digital media player, a home automation device (e.g., which is part of a home automation system), etc.). The resident device (104) may be coupled to communicate with a verification device (116) (e.g., a camera) and / or an environment device (118) (e.g., a smart accessory (e.g., a television, an audio device, a lighting fixture, a garage door opener, a building cover, a camera, a lock, an alarm system, or an air conditioning unit)). The resident device (104) may receive a request from a first user device (114) to access the home environment (102). After the verification device (116) obtains information regarding the first user (112) and / or the first user device (114), the resident device (104) may receive a first locality credential from the verification device (116) indicating the locality of the first user (112) and / or the first user device (114). The resident device (104) trusts the verification device (116) and thus controls the environment device (118) to unlock it, and by causing the environment device (118) to unlock the door, it can allow the first user (112) to access resources such as the home.
[0013] In some embodiments, the resident device (104) receives locality credentials from the first user device (114) and / or from one or more verification devices (116) to determine a locality in which the first user device (114) and / or the first user (112) are trusted, and the locality indicates that the first user (112) and / or the first user device (114) are within a locality associated with the home environment (102) before the resident device (104) enables and / or controls one or more environment devices (118) (e.g., to unlock, to allow WIFI access, to open a door, to turn on lights, to turn off an alarm system, etc.).
[0014] In some embodiments, the user device (e.g., first user device (114), second user device (110)) may be any suitable computing device. In non-limiting examples, the user device may be a mobile phone, tablet, PC, laptop, etc. The user device may be able to communicate with the resident device (104), verification device (116), and / or environment device (118) (e.g., using a wired connection, using a wireless connection, or via a network connection). The user device may include one or more components that can be used to generate a second locality credential to prove the locality of the user device to the locality verification system (106) of the resident device (104).
[0015] The locality of a user device (e.g., a first user device (114)) and / or a user of the user device (e.g., a first user (112)) may be proven using a second locality credential comprising one or more locality credential attributes generated by one or more components of the user device. For example, the user device (e.g., a first user device (114)) may include a camera (e.g., embedded in the user device or otherwise connected (e.g., via a cable or wireless connection)), a speaker, a microphone, a display, an accelerometer, a gyroscope, a magnetometer, a barometer, a biometric sensor (e.g., a fingerprint scanner), a temperature sensor, a Bluetooth (e.g., low-energy Bluetooth) transmitter, a Bluetooth receiver, a near-field communication (NFC) antenna, a touchscreen, a radio antenna (e.g., for Wi-Fi communication, for out-of-band communication), and a global positioning system (GPS) receiver. Those skilled in the art who have an interest in the present disclosure will recognize other components that may be included in the user device.
[0016] The verification device (116) may be any suitable computing device. In non-limiting examples, the verification device (116) may be a mobile phone, tablet, PC, laptop, television, lock, appliance, speaker, etc. The verification device (116) may be able to communicate with the resident device (104), the first user device (114), and / or environment device (118) (e.g., using a wired connection, using a wireless connection, or via a network connection). The verification device (116) may include one or more components that can be used to generate a first locality credential comprising one or more locality credential attributes to prove the locality of the first user device (114) and / or the first user (112) to the resident device (104).
[0017] The verification device (116) may include one or more components such as a camera, a display, a touchscreen, a biometric sensor (e.g., a fingerprint scanner), a speaker, a microphone, a motion sensor, a barometer, a temperature sensor, a Bluetooth (e.g., low-energy Bluetooth) transmitter, a Bluetooth receiver, a near-field communication (NFC) antenna, a radio antenna (e.g., for Wi-Fi communication, for out-of-band communication), a global positioning system (GPS) receiver, etc. The locality of a user device (e.g., a first user device (114)) and / or a user (e.g., a first user (112)) may be proven using a first locality credential comprising one or more locality credential attributes generated by one or more components of the verification device (116).
[0018] In some embodiments, the resident device (104) may be any suitable computing device configured to reside in a specific environment and to control one or more operations and / or environment devices (e.g., environment device (118), accessories within a home environment (e.g., home environment (102)) (e.g., to provide control commands). In some non-limiting examples, the resident device (104) may be a smart speaker, a smart TV device, a tablet device, a smart digital media player (e.g., configured to provide streaming media to a TV), etc. In an example of the system (100), the resident device (104) may correspond to a smart speaker device. When the resident device (104) determines that the locality credentials received (e.g., from the first user device (114) and / or the verification device (116)) are trusted, the resident device (104) may communicate with one or more environment devices (e.g., using a wired connection, using a wireless connection, or through a network connection). After determining that the locality credentials are trusted, the resident device (104) may control one or more environment devices. The resident device (104) may control one or more environment devices based on the first user device (114) and / or commands from the first user (112) (e.g., input by the first user (112) through the user interface of the first user device (114) or environment device (118)).
[0019] A locality credential can be trusted based on one or more locality credential attributes analyzed by a locality verification system (106). The locality credential attributes may be information that can be used to identify a locality (e.g., an image, a sound file, an atmospheric pressure reading, a temperature reading, a GPS location, etc.).
[0020] For example, a locality credential asserting that a first user (112) and / or a first user device (114) is within a certain locality may be determined to be trusted by the locality verification system (106) if it is from the first user device (114) and includes one or more locality credential attributes indicating that the first user device (114) is within the locality (e.g., trust based on a single locality credential). A locality credential may be determined to be trusted by the locality verification system (106) if it is from the verification device (116) and includes one or more locality credential attributes indicating that the first user device (114) and / or the first user (112) is within the locality. For example, the verification device (116) may be a camera device within a locality, and thus when the verification device (116) captures an image of the first user (112), the first user (112) is proven to be within the locality through trust established by locality credentials from the verification device (116) (e.g., trust based on a single locality credential). The locality credential may be determined to be trusted by the locality verification system (106) if it is from the verification device (116) and includes one or more locality credential attributes indicating that the first user device (114) and / or the first user (112) are within the locality, and the second locality credential from the first user device (114) includes one or more locality credential attributes indicating that the first user device (114) is within the same locality (e.g., trust based on two locality credentials).
[0021] The locality verification system (106) may include one or more resource control settings (e.g., a profile management system). Resource control settings may be configured by the owner of the resident device (104), a network administrator, a second user (108), etc. Resource control settings may define which resources can be accessed after the locality credential is trusted. Resource control settings may define which users and / or user devices can control which resources (e.g., environment devices). Resource control settings may define dates and times when the locality credential can be used to access resources. Resource control settings may define dates and times when a specific user and / or user device corresponding to the locality credential can be trusted. Resource control settings may define how long the locality credential can be trusted. Resource control settings can define when to send notifications and what information is included in the sent notifications in response to locality credentials being trusted, a user device being detected in the locality, a user being detected in the locality, etc.
[0022] In some embodiments, after determining that the locality credentials are trusted, the resident device (104) may present and / or transmit a notification. For example, the notification may be presented by the resident device (104) using a display and / or sound. As an example, the resident device (104) may transmit a notification to the second user device (110) (e.g., on the same network as the resident device (104) associated with the resident device (104)) informing the second user (108) of the second user device (110) that the first user device (114) and / or the first user (112) have proven their locality to the resident device (104). The resident device (104) can transmit a notification to the second user device (110) that informs the second user (108) of the second user device (110) that the first user device (114) and / or the first user (112) has been granted access to a resource (e.g., home environment (102), control of one or more devices coupled to communicate with the resident device (104)).
[0023] It should be understood that notifications may be provided by the resident device (104) using any suitable channel and / or method depending, for example, the type of resident device, the type of user device, the surrounding environment, etc. For example, consider another embodiment in which the resident device (104) corresponds to a smart TV device (e.g., a digital media player connected to a TV). The smart TV device may be configured to present a graphical user interface (GUI) on the TV that may include a picture-in-picture (PIP) presentation. In this example, the resident device may provide notifications in the form of an audiovisual (AV) feed. For example, the resident device may display a video feed (e.g., received from a camera of a verification device) in the inset window of the TV.
[0024] In some embodiments, the resident device (104) may be configured to provide notifications based at least partially on a recognized person. For example, in one embodiment, the resident device (104) may receive a request from the second user device (110) (e.g., the owner of the resident device) to receive notifications only when a person who is not on the allow list or is on the block list is detected. This setting may be used, for example, when the second user (108) wants to be notified only when people not on contact access the home environment (102), but not when relatives access the home environment (102). In another embodiment, the resident device (104) may receive a request from the second user device (110) to receive notifications only when the first user device (114) is detected within the locality and is a contact associated with the second user device (110). In another embodiment, the resident device (104) may receive a request from the second user device (110) to receive notifications only when the resident device (104) determines that the locality credentials are trusted.
[0025] In another embodiment, the resident device (104) may be configured to provide a notification when any locality credential is received. It should be understood that the settings described above are merely representative, and any suitable types of settings may be used to configure the resident device (104). In some cases, a specific setting may increase the number of notifications provided by the resident device (104) (e.g., configuring the resident device (104) to notify the user whenever any person is detected). In some cases, a specific setting may result in a decrease in the number of notifications provided by the resident device (104) (e.g., configuring the resident device (104) to provide notifications only when a locality credential is determined to be trusted and it is at a specific time of day). In some embodiments, the notification may include the identification of the detected user device, the detected user, when the user device was detected, when the user was detected, which devices the user device controlled, etc.
[0026] Although the system (100) illustrates a home environment (102) situation in which the system detects a person within the same locality as the front door of the home, it should be understood that embodiments of the present disclosure may be performed in any suitable situation. For example, instead of having one or more locality credentials transmitted to the resident device (104), the first user (112) and / or the first user device (114) within a locality including a front door outside the home may be in a specific locality within the home. In this example, the system may warn a user (e.g., homeowner) within the home and / or other locality that another person (e.g., dog walker, caretaker) has entered a specific locality within the home. Embodiments may also be performed in a non-home environment situation. For example, a workplace can detect when certain visitors have arrived and when access to resources (e.g., network access, physical access) has been granted to certain visitors, or a public office can detect when there may be unauthorized access to a specific locality (e.g., area, location).
[0027] In some embodiments, the resident device (104) includes a verification device (116) and / or performs one or more functions of the verification device (116). In some embodiments, the environment device (118) includes a verification device (116) and / or performs one or more functions of the verification device (116).
[0028] FIG. 2 is a simplified block diagram of a system (200) illustrating at least some exemplary techniques for proving the locality of a user device (e.g., a first user device (114)) according to some embodiments. The system (200) includes a first user device (114), a verification device (116), a resident device (104), and an environment device (118). Each of the system components illustrated in the system (200) can perform functions as described above. The system (200) is an example of a method in which the verification device (116) can transmit one or more locality credentials to the resident device (104) for the control of resources such as the environment device (118). The verification device (116) can transmit locality credentials generated by the verification device (116) and / or a second locality credential generated by the first user device (114) to the resident device (104).
[0029] In some embodiments, the verification device (116) generates a first locality credential to be transmitted to the resident device (104). The first locality credential may be generated by the verification device (116) based on one or more components included in the verification device (116). The verification device (116) may include at least one of a camera, a display, a touchscreen, a biometric sensor (e.g., a fingerprint scanner), a speaker, a microphone, a motion sensor, a barometer, a temperature sensor, a Bluetooth transmitter (e.g., Low Energy Bluetooth), a Bluetooth receiver, a near-field communication (NFC) antenna, a radio antenna (e.g., for Wi-Fi communication, for out-of-band communication), a global positioning system (GPS) receiver, etc.
[0030] One or more components of the verification device (116) may be used to obtain locality attributes. Locality attributes may include information that can be used to identify the locality. In some embodiments, locality attributes may include any information obtained by the verification device (116). For example, locality attributes may include at least one of an image, a sound file, an atmospheric pressure reading, a temperature reading, a GPS location, coordinates, a device identifier (e.g., a globally unique device identifier), a user identifier (e.g., a username), a locality credential identifier, a password, a challenge response, information obtained from a device within the locality that can be managed by the resident device, a timestamp (e.g., when the locality attribute was created), an indication of the communication type (e.g., an indication that the device identifier was received via NFC), etc.
[0031] The resident device (104) may receive one or more locality credentials from one or more verification devices (116). Each locality credential may include one or more locality attributes, locality credential identifiers, a time to live, and / or a timestamp at the time the locality credential was created. The locality credentials may be used by the locality verification system (106) of the resident device (104) to determine whether the locality credential is trusted. If trusted, the resident device (104) may control one or more devices (e.g., one or more environment devices (118)) to enable the user to access the resource.
[0032] In certain embodiments, when trusted, the resident device (104) may transmit a notification to one or more devices coupled to the resident device (104) that are communicable with the resident device (104) (e.g., verification device (116), environment device (118), first user device (114), other user device coupled to the resident device (104), etc.). The notification may be used to present information that a trusted access credential has been received by the locality verification system (106), the device on which the locality credential was received (e.g., verification device (116)), the time on which the locality credential was received, the device that generated the locality credential (e.g., verification device (116)), the first user device (114) that has been granted access to a resource as a result of the trusted locality credential, and at least one of the user that has been granted access to a resource as a result of the trusted locality credential. In some embodiments, when locality credentials are trusted, the resident device (104) can be coupled to communicate with the first user device (114) (e.g., establishing a wireless connection with the first user device (114)).
[0033] In some embodiments, if a locality credential received by the locality verification system (106) is not determined to be trustworthy, a notification presenting information regarding the locality credential not being trustworthy may be transmitted to one or more devices. In some embodiments, if a locality credential received by the locality verification system (106) is not determined to be trustworthy, one or more environment devices may be controlled (e.g., to lock a door, to close a door, to sound an alarm, to emit a warning signal, to flash lights, etc.).
[0034] Some exemplary examples of locality attributes and how they can be processed (e.g., by the locality verification system (106)) are described in detail below. An example of a locality attribute may be an image of a user captured by a verification device (116). The image of the user may be processed by a resident device (104) to determine whether the image of the user includes a user who is allowed to access a resource managed by the resident device (104). If so, the resident device (104) may control one or more devices (e.g., an environment device (118)) to enable the user to access the resource.
[0035] An example in which the locality verification system (106) relies on multiple locality attributes may be a combination of a device identifier and a type of wireless communication used by the verification device (116). The device identifier of a nearby first user device (114) may be received by the verification device (116) from the nearby first user device (114) using short-range wireless communication (e.g., Bluetooth, NFC, etc.). Due to the short-range nature of the communication, the fact that the device identifier of the first user device (114) was communicated to the verification device (116) may be included in a locality credential containing locality attributes representing the type of wireless communication used and the first user device identifier. The verification device (116) may transmit a locality credential having locality attributes to a resident device to verify using the locality verification system (106). If the first user device identifier and / or the user associated with the first user device identifier is on the allow list and / or is not on the block list, the locality verification system (106) may determine that the locality credential received from the verification device (116) is trusted. If trusted, the resident device (104) may control one or more devices (e.g., environment device (118)) to enable the user of the first user device to access the resource.
[0036] In some embodiments, in addition to or as an alternative to the verification device (116) generating a first locality credential, the verification device (116) may receive a second locality credential from the first user device (114). The first user device (114) may include any of the components that the verification device (116) may include. For example, the first user device (114) may include at least one of a camera, a display, a touchscreen, a biometric sensor (e.g., a fingerprint scanner), a speaker, a microphone, a motion sensor, a barometer, a temperature sensor, a Bluetooth (e.g., Low Energy Bluetooth) transmitter, a Bluetooth receiver, a near-field communication (NFC) antenna, a radio antenna (e.g., for Wi-Fi communication), a global positioning system (GPS) receiver, etc.
[0037] The second locality credential received from the first user device (114) may include one or more locality attributes. In some embodiments, the locality attributes may include any information obtained by the first user device. For example, the locality attributes may include at least one of an image, a sound file, an atmospheric pressure reading, a temperature reading, a GPS location, a device identifier (e.g., a globally unique device identifier), a user identifier (e.g., a username), a password, a challenge response, and information obtained from a device within the locality that can be managed by the resident device (e.g., a beacon signal, network data).
[0038] In some embodiments, the verification device (116) may transmit a second locality credential received from the first user device (114) to the resident device (104) to be processed by the locality verification system (106). The locality verification system (106) may process the second locality credential generated by the first user device (114) and transmitted to the resident device (104) through the verification device (116) in a manner similar to how the locality credential generated by the verification device (116) can be processed as described above.
[0039] In certain embodiments, the locality verification system (106) may assign scores to locality attributes and / or locality credentials. Each locality attribute may be assigned a score based at least on how the attribute was acquired (e.g., the sensor used to acquire the locality attribute) when the attribute was acquired. Each locality credential may be assigned a score based at least on the device that generated the locality credential, how many locality attributes are included in the locality credential, the score of the locality attributes included in the locality credential, and / or when the locality credential was generated. The locality verification system (106) may determine whether the locality credential should be trusted by determining whether the score assigned to the locality credential exceeds a threshold score. By scoring the locality credentials and / or locality attributes, certain devices (e.g., the first user device (114), the verification device (116)) and / or locality attributes may be trusted more than others.
[0040] In certain embodiments, different resources associated with a first locality may require that a higher score threshold be satisfied before access to the resources associated with the first locality is permitted. In certain embodiments, different users may need to satisfy a higher score threshold before access to the resources associated with the locality is permitted.
[0041] In some embodiments, the first user device (114) may generate a first locality credential associated with the first user device (114) and / or the user of the first user device (114) and transmit the first locality credential to a verification device (116). In some embodiments, the verification device (116) may generate a second locality credential associated with the first user device (114) and / or the user of the first user device (114). The verification device (116) may transmit the first locality credential and / or the second locality credential to a resident device (104) to be input into a locality verification system (106) to determine whether the first locality credential and / or the second locality credential can be trusted. In some embodiments, when one of the first locality credential and the second locality credential is trusted, access to a resource controlled by the resident device (104) is permitted. In some embodiments, when both the first locality credential and the second locality credential are trusted, access to a resource controlled by a resident device is permitted.
[0042] In some embodiments, access to a resource controlled by a resident device (104) is permitted when the first locality credential is sufficiently similar to the second locality credential. For example, the first locality credential may include first locality attributes including a microphone reading, an atmospheric pressure reading, and a GPS location from a first user device (114), and the second locality credential may include second locality attributes including a microphone reading, an atmospheric pressure reading, and a GPS location from a verification device (116). The locality verification system (106) can determine that the sounds represented by the microphone readings, the atmospheric pressure represented by the atmospheric pressure readings, and the GPS location included in each of the first locality credential and the second locality credential are sufficiently similar (e.g., within a predefined range), and accordingly, the locality verification system (106) can be confident that the first user device (114) and the verification device (116) were in the same locality when information for generating each of the credentials is obtained. The locality verification system (106) may allow the resident device (104) to permit access to resources to the first user device (114) and / or the first user of the first user device (114), because the locality verification system (106) expects that the first user device (114) is in the same locality as the verification device (116) and that the verification device (116) is in a locality managed by the resident device (104).
[0043] In some embodiments, the verification device (116) includes a second locality verification system in addition to or as an alternative to the locality verification system (106) of the resident device (104). In an embodiment where the verification device (116) includes the second locality verification system, when it is determined that one or more locality credentials are trusted, the verification device (116) may transmit an indication of trust to the resident device (104) to allow the resident device (104) to permit access to one or more resources to the first user device (114) and / or the user of the first user device (114). In some embodiments, the verification device (116) may transmit information (e.g., network access information, device identifier) to the resident device (104) and / or the first user device (114) that enables the resident device (104) to establish a communication-enabled coupling with the first user device (114).
[0044] In some embodiments, the processing performed by the locality verification system (106) may be performed partially or entirely by a verification device (116) and / or a server (e.g., a remote server). In some embodiments, when a resident device (104) performs the locality verification system (106) function, the information used to determine whether locality credentials are trusted may be stored in fewer devices, and security may be improved and network traffic reduced compared to determining whether locality credentials are trusted in one or more verification devices. In some embodiments, when one or more verification devices perform the locality verification system (106) function, the processing performed to determine whether locality credentials are trusted may be distributed among one or more devices, and the computation resources used by the resident device (104) may be mitigated compared to determining whether locality credentials are trusted using the resident device (104). Such an embodiment may be beneficial when the processing capabilities of the resident device (104) are limited and / or when many user devices and / or users are causing locality credentials to be generated.
[0045] Next, exemplary examples of how the components of the system (200) can be configured to operate are described. In one example, the first user device (114) may be the first user's mobile phone and may be capable of transmitting NFC signals. The verification device (116) may be an NFC reader integrated into the smart lock of the door. The environment device (118) may include the smart lock of the door. Thus, in this example, the verification device (116) and the environment device (118) may be the same device. The resident device (104) may be a speaker inside a home on one side of the door. The resident device (104) may be configured to be coupled to communicate with the verification device (116) (e.g., using a Wi-Fi network connection). The resident device (104) may trust that the verification device (116) is within a locality managed by the resident device (104). The resident device (104) can trust the verification device (116) because the verification device (116) is located in a fixed location and / or is on the same local network as the resident device (104). A second user who manages the resident device (104), is the owner of the home, is the owner of the resident device (104), is the owner of the environment device (118), and / or manages resource access permissions may configure the first user device (114) to be a user device on the allowlist.
[0046] The first user of the first user device (114) may want the environment device (118) to have the door unlocked. When the first user device (114) is within the NFC communication range of the verification device (116), the verification device (116) may receive information identifying the first user device (114). The verification device (116) may transmit locality credentials containing locality attributes to the resident device (10). The locality attributes may include an indication that NFC was used and that NFC was performed between the verification device (116) and the first user device (114). The locality verification system (106) of the resident device (104) may receive the locality credentials and determine whether the locality credentials are trusted. The locality verification system (106) may determine that the locality credential is trusted because the first user device identifier is on the allowlist, short-range communication (e.g., NFC) is used between the verification device (116) and the first user device (114), and the locality of the verification device (116) is known and / or trusted.
[0047] When the locality verification system (106) determines that the locality credential is trusted, the resident device (104) can communicate with the environment device (118) (e.g., by using a network connection, by using Bluetooth, by using Wi-Fi, etc.) and allow the environment device (118) to be controlled. The environment device (118) can be controlled to unlock in response to the communication received from the resident device (104).
[0048] In the example, after the locality verification system (106) determines that the locality credentials are trusted, the resident device (104) may communicate with the verification device (116) and cause the verification device (116) to transmit information to the first user device (114). The information may include network credentials that enable the first user device (114) to access a network, and / or may include credentials that enable the first user device (114) to establish a wireless communication coupling with the resident device (104) (e.g., using Bluetooth, using Wi-Fi).
[0049] FIG. 3 is a simplified block diagram of a system (300) illustrating at least some exemplary techniques for proving the locality of a user device (e.g., a first user device (114)) according to some embodiments. The system (300) includes a first user device (114), a verification device (116), any number of other verification devices, a resident device (104), and an environment device (118). Each of the system components illustrated in the system (300) can perform functions as described above. The system (300) is an example of a method in which the verification device (116) and / or the first user device (114) can transmit one or more locality credentials to the resident device (104) for the control of resources such as the environment device (118). The verification device (116) can transmit a first locality credential generated by the verification device to the resident device (104). The first user device (114) can transmit the second locality credential generated by the first user device (114) to the resident device (104).
[0050] The verification device (116) and / or any number of other verification devices may generate locality credentials to be transmitted by the verification device (116) to the resident device (104). As described above, the first locality credentials may be generated by the verification device (116) based on one or more components included in the verification device (116). As described above, one or more components of the verification device (116) may be used to obtain locality attributes to be included in the locality credentials.
[0051] The first user device (114) can generate a second locality credential to be transmitted by the first user device (114) to the resident device (104). As described above, the second locality credential may be generated by the first user device (114) based on one or more components included by the first user device (114). As described above, one or more components of the first user device (114) may be used to obtain second locality attributes to be included in the second locality credential. The resident device (104) may receive the second locality credential from the first user device (114) and the first locality credential from the verification device (116).
[0052] In some embodiments, the locality verification system (106) compares the first locality credential with the second locality credential to determine whether both locality credentials are trusted. In some embodiments, the locality credential generated by the verification device (116) is always trusted because the verification device may be on the same network as the environment device (118) and / or the resident device (104). In some embodiments, the locality credential of the verification device (116) is always trusted because the verification device (116) may be in a fixed and trusted location.
[0053] In some embodiments, determining whether both locality credentials are trusted may include determining whether the second locality credential includes locality attributes that express the same locality as the locality attributes of the first locality credential. For example, a verification device (116) may measure atmospheric pressure and light intensity, and a first user device (114) may also measure atmospheric pressure and light intensity. If the verification device (116) generates atmospheric pressure and light intensity similar to the atmospheric pressure and light intensity measurements of the first user device (114) from its measurements, the second locality credential may be determined to be trusted by the locality verification system (106). The present example illustrates that, at least, the attributes may be compared to determine whether locality attributes of a similar type are within a defined similarity threshold.
[0054] In one example, the verification device (116) can measure atmospheric pressure and light intensity, and the first user device (114) can measure atmospheric pressure and light intensity and determine the GPS coordinates of the first user device (114). If the verification device (116) generates atmospheric pressure and light intensity similar to the atmospheric pressure and light intensity measurements of the first user device from its measurements, and the GPS coordinates are within a locality managed by the resident device (104), the second locality credential may be determined to be trusted by the locality verification system (106). This example illustrates that at least a first set of one or more locality attributes from the first device and a second set of one or more locality attributes from the second device may be used by the locality verification system (106) to determine whether one or both of the locality credentials are trusted.
[0055] In some embodiments, the locality verification system (106) may allow control of the environment device (118) even if only one of the first locality credential and the second locality credential is trusted. For example, the first locality credential received from the verification device (116) may have an associated trust score. The trust score may be based on the number of locality attributes included in the locality credential, which locality attributes are included, the verification device that generated the locality credential, when the locality credential was generated, etc. The locality verification system (106) may determine whether one or more locality credentials are trusted based on the summed trust score of each of the locality credentials. Accordingly, even if one locality credential is not determined to be trusted by the locality verification system (106) itself, the locality verification system (106) can still allow the environment device (118) to be controlled based on the trust of one or more other locality credentials (e.g., from one or more verification devices). Such embodiments may be useful because, even though the first user device (114) may have components that are not functioning properly, may have communication with the resident device (104) interrupted, may not be running a trusted software version, etc., access to resources may still be provided to the first user device (114) and / or the first user based on whether the first locality credential is trusted.
[0056] In some embodiments, the resident device (104) may receive locality credentials from more than one verification device. Multiple verification devices may be used to add redundancy and / or additional trust that the first user device (114) or the first user is within the locality. The verification devices may be devices of the same type as the other verification devices or different devices. For example, the first verification device may be a camera, and the second verification device may be an NFC reader. The locality verification system (106) may determine whether the locality credentials received from the first verification device and the second verification device, respectively, are trusted before controlling the environment device (118). The resident device (104) may additionally receive a second locality credential from the first user device (114). The locality verification system (106) can determine whether to control the environment device (118) by using any combination of locality credentials received from any combination of devices (e.g., verification devices and / or user devices).
[0057] In some embodiments, the resident device (104) may receive a second locality credential from the first user device (114) and may not receive a locality credential from the verification device (116). In such embodiments, the locality verification system (106) may determine whether to trust the credential and control the environment device (118) based on a single locality credential received from the first user device (114).
[0058] In some embodiments, the locality verification system (106) uses more than one locality credential received from the same device (e.g., the first user device (114)) to determine whether to control the environment device (118) (e.g., to permit access to resources). Such embodiments may provide additional assurance that the first user device (114) is within a locality managed by the resident device (104).
[0059] FIG. 4 is a simplified block diagram (400) illustrating access control management based on proof of locality of a user device (e.g., a first user device (114)) according to some embodiments.
[0060] In 402, the resident device (104) may generate one or more locality credentials. Locality credentials may be received from a first user device (114) through communication coupling with the resident device (104). Locality credentials may be received from a verification device (116) (e.g., an NFC scanner) that is communicably coupled with the resident device (104). In some embodiments, locality credentials are received from more than one verification device (e.g., an NFC scanner and a camera) and / or more than one user device (e.g., a smartphone and a smartwatch). Locality credentials may include one or more locality attributes that help the first user device (114) and / or the user prove the locality within. Further details regarding locality credentials, locality attributes, and devices have been described above.
[0061] In 404, the locality verification system (106) can determine whether the received locality credential is trusted. The locality verification system (106) in block diagram (400) is in a local state with respect to the resident device (104). In some embodiments, the locality verification system (106) is in a local state with respect to one or more devices (e.g., resident device (104), verification device (116), and / or server). In some embodiments, the locality verification system (106) is included in a server (e.g., a remote server). The server may be coupled to communicate with the resident device (104) and network in which the verification device (116) and / or resident device (104) are included.
[0062] A locality verification system (106) can determine whether a locality credential is trusted and allow access to a resource (e.g., allow an environment device (118) to be controlled) by using one or more locality attributes of one or more locality credentials. A locality verification system (106) can determine whether a locality credential is trusted and allow access to a resource by using scores associated with locality credentials and / or locality attributes.
[0063] In block diagram (400), if the locality verification system (106) determines that the locality credentials associated with the first user (112) and / or the first user device (114) are trusted, the resident device (104) may allow one or more devices (e.g., environment devices (118)) to be controlled. The environment device (118) may allow the first user device (114) and / or the first user (112) access to one or more resources.
[0064] In 406, resource access may be associated with a duration. That is to say, a locality credential associated with the first user (112) and / or the first user device (114) may enable the first user (112) and / or the first user device (114) to access the resource for a certain period of time before access is restricted or before a new locality credential is required to refresh the resource access permission. In some embodiments, the duration is predefined and / or may be based on a first user (112), a first user device (114), a device that generated the locality credential (e.g., a verification device (116)), the number of locality attributes included in the locality credential, the locality attributes included in the locality credential, the score of the locality credential, the score of the locality attributes, a resource that was allowed access, how many times the first user (112) and / or the first user device (114) was approved to access the resource (e.g., a resource), whether the first user (112) and / or the first user device (114) is on the allowlist, the time of day when the locality credential was generated, etc.
[0065] In 408, the duration may be extended or refreshed. When the first user (112) and / or the first user device (114) cause another locality credential to be generated and transmitted to the locality verification system (e.g., by the verification device (116) or by the first user device (114)), the duration may be extended or refreshed.
[0066] In 410, access to a resource may be restricted. Access to a resource may be restricted so that, before access to the resource is permitted, another user and / or user device may need to have locality credentials transmitted to a locality verification system (106) to determine if they are trustworthy. For example, a first user (112) may have locality credentials transmitted to a locality verification system (106), and a resident device (104) may unlock the door to allow the first user (112) to enter, and then lock the door after a set time so that a second user cannot enter through the door before having locality credentials transmitted to a locality verification system (106).
[0067] In another example, the first user (112) may allow locality credentials to be transmitted to the locality verification system (106), and the locality verification system (106) enables the user to access resources (e.g., control an environment device (e.g., a smart thermostat)). The first user (112) can have access periodically refreshed until the first user (112) leaves the locality (e.g., by causing the first user device (114) and / or verification device (116) to generate locality credentials determined to be trusted and transmit them to the locality verification system (106), and accordingly, the first user device (114) and / or verification device (116) cannot generate locality credentials and transmit them to the locality verification system (106) associated with the first user (112) which can be determined to be trusted (e.g., because the first user (112) is no longer within the locality).
[0068] FIG. 5 is a simplified block diagram illustrating an exemplary architecture of a system (500) used to manage resource access based on proof of locality of a user device according to some embodiments.
[0069] The system (500) includes a first user device (114), a verification device (116), an environment device (118), a resident device (104), a network (508), and a remote server (522). The first user device (114), the verification device (116), the environment device (118), and the resident device (104) may be similar to any of the user devices, verification devices, environment devices, and / or resident devices described herein. The remote server (522) may correspond to one or more server computers (e.g., a server cluster) of a cloud computing platform, as described herein.
[0070] The network (508) may include any suitable communication path or channel, such as, for example, wire or cable, optical fibers, telephone line, cellular link, radio frequency (RF) link, WAN or LAN network, the Internet, or any other suitable medium. The network (508) may include any network or combination thereof among many different types of networks, such as cable networks, the Internet, wireless networks, cellular networks, and other private and / or public networks. The network may use infrared, ultra-wideband (UWB), Apple Wireless Direct Link (AWDL), Bluetooth (BT), Bluetooth Low Energy (BTLE), Wi-Fi, and / or radio communication techniques.
[0071] Referring more closely to each element, the first user device (114) may be any suitable computing device (e.g., mobile phone, tablet, personal computer (PC), smart glasses, smart watch, etc.). The user device (502) has at least one memory (510), one or more processing units (or processor(s)) (514), a storage unit (516), a communication interface (518), and input / output (I / O) device(s) (520).
[0072] The processor(s) (514) may be implemented as hardware, computer-executable instructions, firmware, or a combination thereof, as appropriate. Computer-executable instruction or firmware implementations of the processor(s) (514) may include computer-executable or machine-executable instructions written in any suitable programming language to perform the various functions described.
[0073] Memory (510) can store program instructions that are loadable and executable on the processor(s) (514), as well as data generated during the execution of these programs. Depending on the configuration and type of the user device (502), memory (510) may be volatile (e.g., random access memory (RAM)) and / or non-volatile (e.g., read-only memory (ROM), flash memory, etc.). In some implementations, memory (510) may include a number of different types of memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), or ROM. The first user device (114) may also include additional storage (516), such as removable storage or non-removable storage, including but not limited to magnetic storage, optical discs, and / or tape storage. Disk drives and their associated computer-readable media can provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data to computing devices. In some embodiments, the storage (516) may be used to store a photo library containing one or more images on the first user device (114).
[0074] The first user device (114) may also include a communication interface (518) that enables the user device (502) to communicate with a verification device, a resident device, another computing device or server, user terminals, and / or other devices on the network(s) (508). The first user device (114) may also include I / O device(s) (520) for enabling connection with, for example, a keyboard, a mouse, a pen, a voice input device, a touch input device, a display, speakers, a printer, and / or other components that the first user device (114) may include.
[0075] The communication interface (518) and / or I / O device(s) (520) may include at least one of a camera, display, touchscreen, biometric sensor (e.g., fingerprint scanner), speaker, microphone, motion sensor, barometer, temperature sensor, Bluetooth (e.g., Low Energy Bluetooth) transmitter, Bluetooth receiver, near-field communication (NFC) antenna, radio antenna (e.g., for Wi-Fi communication), or global positioning system (GPS) receiver. The communication interface (518) and / or I / O device(s) (520) may enable the first user device (114) to acquire locality attributes.
[0076] Referring more closely to the contents of the memory (510), the memory (510) may include one or more application programs or services for implementing the features disclosed herein, including an operating system and a credential generation module (512). The credential generation module (512) may be responsible for generating locality credentials using one or more locality attributes. Locality credentials may be generated by the credential generation module (512) based on one or more components (e.g., I / O devices (520), communication interface (518)) included in the first user device (114).
[0077] One or more components of the first user device (114) may be used to obtain locality attributes to be used by the credential generation module (512) to generate locality credentials. Locality attributes may include information that can be used to identify a locality. In some embodiments, locality attributes may include any information obtained by the first user device (114). For example, locality attributes may include at least one of an image, a sound file, an atmospheric pressure reading, a temperature reading, a GPS location, a device identifier (e.g., a globally unique device identifier), a user identifier (e.g., a username), a password, a challenge response, or information obtained from a device within the locality that can be managed by the resident device (104).
[0078] It should be understood that one or more functions of the credential generation module (512) may be performed by a resident device (104), a remote server (522), and / or a verification device (116).
[0079] In some embodiments, the verification device (116) may be connected to the resident device (104) via a network (508). The verification device (116) may include itself among any number of components included in the first user device (114). For example, like the first user device (114), the verification device (116) may also include a memory including a credential generation module. The verification device (116) may also include processors, storage, communication interfaces, and / or I / O devices.
[0080] In some embodiments, the environment device (118) may be connected to the resident device (104) via a network (508). The environment device (118) may include itself any number of components included in the first user device (114). For example, like the first user device (114), the environment device (118) may also include memory including a credential generation module. The verification device (116) may also include processors, storage, communication interfaces, and / or I / O devices.
[0081] In some embodiments, as described above, the remote server (522) may correspond to a cloud computing platform. The remote server (522) may perform one or more functions, for example, including receiving locality credentials from a verification device (116), a first user device (114), and / or a resident device (104). The remote server (522) may include a locality verification system. The remote server (522) may include a credential generation module, I / O devices, and / or communication interfaces, etc.
[0082] Referring more specifically to the resident device (104), the resident device (104) may be a computer system comprising at least one memory (530), one or more processing units (or processor(s)) (546), a storage unit (548), a communication device (550), and an I / O device (552). In some embodiments, these elements may be implemented similarly (or differently) as described with reference to similar elements of the first user device (114). In some embodiments, the storage unit (408) may store an allow list (e.g., of users and / or devices), a block list (e.g., of users and / or devices), and / or permissions. The resident device (104) may be housed in any suitable unit (e.g., a smart TV, a smart speaker, etc.).
[0083] Referring more closely to the contents of the memory (530), the memory (530) may include one or more application programs or services for implementing the features disclosed in this specification, including an operating system (532), a communication module (534), an encryption module (536), a notification management module (538), a profile management module (540), a scoring module (542), and a locality verification system (132).
[0084] The communication module (534) may include code that causes the processor (546) to generate messages, forward messages, reformat messages, and / or otherwise communicate with other entities. For example, the communication module (534) may receive (and / or transmit) locality credentials from the first user device (114), the verification device (116), and / or the remote server (522). The communication module (534) may also be responsible for receiving requests to control resources (e.g., to control the environment device (118)). The communication module (534) may also be responsible for providing notifications. For example, the communication module (534) may transmit a notification message to the first user device (114) when the expiration time of the locality credentials associated with the first user device (114) and / or the user of the first user device (114) is set to expire. The communication module (534) may transmit a notification message indicating that access to a resource has been approved and / or restricted to the owner of the resident device (104), the administrator of the locality, or another user device that is communicably coupled with the resident device (104). In some embodiments, the communication module (534) may provide the notification using any suitable channel and / or to any suitable device. For example, the communication module (534) may provide an audible notification via a speaker I / O device (552) at a location within the home environment. In another example, the communication module (534) may provide an audiovisual notification to a smart TV within the home environment. For example, the smart TV's PIP display may display a video feed from the camera (504) (e.g., showing a user at the front door of the home). The smart TV may also notify / announce who is at the door or allow two-way communication via the speaker and / or microphone I / O devices of the resident device (506).
[0085] The encryption module (536) may include code that causes the processor (546) to encrypt and / or decrypt messages. For example, the encryption module (536) may receive encrypted data (e.g., locality credentials, locality attributes) from a first user device (114), a remote server (522), and / or a verification device (116). The encryption module (536) may include any suitable encryption algorithms for encrypting data. Suitable data encryption algorithms may include the Data Encryption Standard (DES), Triple DES, Advanced Encryption Standard (AES), etc. It may also store encryption keys (e.g., encryption and / or decryption keys) that can be used with such encryption algorithms (e.g., in a storage unit (548)). The encryption module (536) may utilize symmetric or asymmetric encryption techniques to encrypt and / or verify data. For example, the first user device (114), remote server (522), and / or verification device (116) may include codes and / or keys similar to a suitable encryption module (536) for encrypting / decrypting data communications with the resident device (and / or remote server (522)).
[0086] The notification management module (538) may include code that causes the processor (546) to store and manage settings for providing notifications. The notification management module (538) may also be responsible for generating notifications provided by the communication module (534). It should be understood that notifications may be presented in any suitable form (e.g., text, audio, video, and / or suitable combinations). In some embodiments, the notification management module (538) may be configured not to perform any action in certain settings (e.g., to be a "no-op"). For example, the resident device (104) may be configured to provide AV-based notifications to the user device (502) only when the received locality credential is not associated with a user and / or device on the allowlist. Accordingly, if the resident device (104) detects that the received locality credential is associated with a user and / or device on the allowlist, the notification management module (538) may decide not to perform any action (e.g., remain silent, log observations internally only, etc.). In some embodiments, the notification management module (538) may also determine whether to provide notifications based on the time of day and / or received locality attributes.
[0087] In some embodiments, the resident device (104) includes a credential generation module.
[0088] The profile management module (540) may include code that causes the processor (546) to maintain and store profiles of users and / or user devices. For example, the profile management module (540) may receive users and / or devices to be included in an allow list or a block list. Subsequently, the profile management module (540) may cross-reference locality credentials when they are received and associated with a user and / or user device. The profile management module (540) may also include information regarding which users and / or user devices have which permissions, when permissions are allowed (e.g., time of day, day of the week, predefined single period), whether a notification should be generated, etc.
[0089] The scoring module (542) may include code that causes the processor (546) to determine a score corresponding to locality credentials and / or one or more locality attributes. The scoring module (542) may determine whether the score of the locality credentials and / or the locality attributes included in the locality credentials exceeds a threshold score in determining whether the locality credentials will be trusted. The locality credentials and / or locality attributes may cause certain devices (e.g., user devices, verification devices), users, and / or locality attributes to be trusted more than others. The score may be based on the number of locality attributes included in the locality credentials, which locality attributes are included, the device that generated the locality credentials, when the locality credentials were generated, the software version that the device that generated the locality credentials was running, etc.
[0090] In certain embodiments, a score is associated with a locality credential before the locality credential is received by the locality verification system. For example, a verification device may compute a score to be associated with the locality credential so that when the resident device and / or the locality verification system receives the locality credential, processing to compute the score does not need to be performed. Such embodiments may distribute score processing among the devices.
[0091] The locality verification system (132) may include code that causes the processor (546) to determine whether the locality credential is trusted. Determining whether the locality credential is trusted may be performed by the scoring module (542). The operations of the locality verification system (132) are described in detail in this specification. The verification device (116), the remote server (522), and / or the resident device (104) may include the locality verification system (106).
[0092] The processing illustrated in FIGS. 6 through 8 and any other drawings may be implemented using hardware or a combination thereof, as software (e.g., code, instructions, programs) executed by one or more processing units (e.g., processors, cores) of each system. The software may be stored on a non-transient storage medium (e.g., a memory device). The method presented in FIGS. 6 through 8 and other drawings and described herein is intended to be exemplary and non-limiting. FIGS. 6 through 8 and other drawings illustrate various processing steps occurring in a specific sequence or order, but this is not intended to be limiting. In certain alternative embodiments, the processing may be performed in some different order, or some steps may also be performed in parallel. It should be understood that in alternative embodiments, the processing illustrated in FIGS. 6 through 8 and other drawings may include more or fewer steps than those illustrated in each drawing.
[0093] FIG. 6 is a simplified flowchart illustrating an exemplary process (600) performed by a user device to demonstrate locality according to some embodiments. The user device may perform the process (600) before access to a resource is granted in order to obtain access to a resource. The user device may additionally or alternatively perform the process (600) after access to a resource is granted in order to maintain access to a resource.
[0094] In 602, a user device may transmit locality credentials to a resident device. Locality credentials may be transmitted directly from the user device to the resident device (e.g., by using Bluetooth or Wi-Fi communication between the resident device and the user device). Locality credentials may be transmitted indirectly from the user device to the resident device (e.g., through a network connection to a server, or through a verification device). Locality credentials may include one or more locality attributes as described above.
[0095] In 604, the user device may send a control command to the resident device. The control command may request the resident device to control one or more environment devices (e.g., on behalf of the user device). The control command may be useful for allowing the resident device to act as a central hub and for not allowing the user device to directly control the environment devices. In this way, when the resident device is no longer communicably coupled with the user device, and when the resident device decides that it does not trust the locality of the user device and / or when the resident device decides that user device commands will no longer be executed, the resident device may control whether the environment devices can and are controlled by the user device's commands.
[0096] In 606, a user device may send a request to restrict control to a resident device. A user device may send a request when the user device has left or is leaving a locality. A user device may send a request to the user interface of the user device based on user input. A user device may send a request based on the user device's determination that the user device is no longer in a locality managed by a resident device.
[0097] The process (600) describes a resident device receiving locality credentials and managing environment devices (e.g., controlling them, restricting access thereto), but one or more other devices (e.g., resident devices, servers, verification devices) may be used to perform at least part of such functions.
[0098] FIG. 7 is a simplified flowchart illustrating an exemplary process (700) performed by a resident device to manage access to a resource based on proof of locality according to some embodiments. The resident device may perform the process (700) before access to the resource is granted to the user device and / or user. The resident device may additionally or alternatively perform the process (700) to ensure that access to the resource is maintained after the user device and / or user is granted access to the resource.
[0099] In 702, the resident device may receive a first locality credential. The resident device may receive the first locality credential directly or indirectly from the user device. In certain embodiments, the resident device receives the first locality credential regardless of whether the resident device includes a locality verification system. The first locality credential may have been generated by the user device as described herein.
[0100] In 704, in certain embodiments, it is illustrated that a resident device may receive a second locality credential directly or indirectly from a verification device. The resident device may receive a second locality credential directly or indirectly from a verification device in addition to, or as an alternative to, the resident device receiving a first locality credential directly or indirectly from a user device. The second locality credential may have been generated by the verification device or received by the verification device as described herein.
[0101] In 706, the resident may determine whether the first locality credential and / or the second locality credential is trusted. The resident device may determine whether the locality credential is trusted by using a locality verification system that the resident device may include or that another device (e.g., a server) may include. The locality verification system may determine whether the first locality credential and / or the second locality credential is trusted. Determining whether any number of locality credentials are trusted may be performed according to the techniques described herein. The techniques may rely on the use of locality attributes, scores, timestamps, allow lists, block lists, and other rules.
[0102] In 708, a resident device may grant access to one or more resources based on permissions associated with a device and / or user associated with a first locality credential and / or a second locality credential (e.g., enabling control of one or more devices (e.g., environment devices)). For example, a first user device may be associated with a user who wishes to acquire access to a resource and thus causes the first locality credential and / or the second locality credential to be generated and transmitted to a locality verification system. A user identifier may be associated with (e.g., included therein) the first locality credential and / or the second locality credential (e.g., the user may be identified using information included in the locality credential). A user identifier may be used to cross-reference a list of allowed resources that the user can access. For example, the user and / or user devices may have permission to unlock a first door but may not have permission to unlock a second door. A resident device may include permissions associated with one or more users and / or user devices. The resident device may be able to access permissions associated with one or more users and / or user devices (e.g., on a remote server). The resident device may access permissions associated with one or more users to determine whether to allow a user and / or user device to access one or more resources.
[0103] The resident device may transmit outgoing commands to one or more devices (e.g., environment devices) based on whether the user and / or user device has allowed trusted locality credentials to be provided to the locality verification system and whether the user and / or user device has permission to have commands executed. The resident device may act as a central command transmitter, ensuring that all command requests are received by the resident device and that all commands sent to the devices are transmitted by the resident device having permission to control the devices. Such a configuration may be useful for managing (e.g., permission, restriction) when resources (e.g., devices) can be accessed, which resources can be accessed, and who can access the resources.
[0104] In 710, the resident device and / or locality verification system may determine whether one or more locality credentials associated with the user and / or user device are still trusted. For example, trusted locality credentials may include and / or be associated with a shelf life. When the shelf life expires, one or more new locality credentials associated with the user are sent to the locality verification system, and until they are determined to be trusted, the user and / or user device associated with the locality credentials may restrict their access to resources.
[0105] In certain embodiments, the duration of a locality credential may be extended or refreshed while the duration remains unexpired. The duration may be expired or refreshed based on one or more locality credentials being transmitted to a locality verification system. In certain embodiments, the duration may be manually refreshed or extended by a resident device so that the duration is extended or refreshed after the resident device performs a command based on a request from a user device and / or user. A request from a user device and / or user may indicate that the user is still within the locality to which the locality credential is associated.
[0106] In 712, access to one or more resources may be restricted by a resident device. The resident device may restrict access to resources by a resource manager (e.g., homeowner, network administrator, security officer, etc.) based on receiving a restriction request from a user device and / or user to whom resource access is authorized, or based on the duration for which locality credentials expire. Access to resources may be restricted by one or more users and / or user devices until locality credentials are generated and transmitted to a locality verification system, and until the locality verification system determines that the locality verification credentials are trusted.
[0107] In certain embodiments, access to one or more resources may be restricted by a resident device after all devices and / or users associated with locality credentials have left the locality. In certain embodiments, access to one or more resources may be restricted by a resident device after all locality credentials trusted by the verification system have had an expired duration. Such embodiments may be useful when the resource being accessed is not specific to a certain user or user device. For example, the resource being accessed may be one that disables the alarm system. In such embodiments, the alarm system may remain disabled until all users have left the locality.
[0108] FIG. 8 is a simplified flowchart illustrating an exemplary process (800) performed by a verification device to verify locality according to some embodiments. The verification device may perform the process (800) before access to the resource is granted to the user device and / or user and before access to the resource is obtained. The verification device may additionally or alternatively perform the process (800) to ensure that access to the resource is maintained after access to the resource is granted to the user device and / or user.
[0109] In 802, a verification device may receive locality information. The verification device may receive locality information from one or more of the components included in the verification device. In certain embodiments, the verification device receives locality information using one or more components that are not coupled to communicate with the user device and / or do not rely on communication with the user device. For example, the verification device may receive locality information from a camera, microphone, or biometric sensor included in the verification device. Such embodiments may be useful when information regarding the user's locality is being collected.
[0110] In certain embodiments, the verification device receives locality information from the user device. For example, the user device may transmit an NFC signal to the verification device or a Bluetooth signal to the verification device. In one example, the user device may transmit locality credentials to the verification device. The locality credentials may include one or more locality attributes.
[0111] In 804, the verification device may transmit locality credentials to the locality verification system. The locality credentials may be locality credentials generated by the user device and received from the user device. The locality credentials may be generated by the verification system.
[0112] The resident device may include a locality verification system. In certain embodiments, the server, the verification device, and / or other verification device include a locality verification system. In certain embodiments, even if the locality verification system is not included in the resident device, the locality credential may be transmitted from the verification device to the resident device and forwarded to another device so that the locality credential can be transmitted to the locality verification system.
[0113] In 806, the verification device may receive a control request from the resident device. For example, the verification device may include an environment device that is controlled by the resident device after the locality credential is determined to be trusted by the locality verification system.
[0114] In some embodiments, the verification device is controlled by a resident device based on the determination that a locality credential is not trusted by the locality verification system. For example, the verification device may be controlled to emit a sound or display a message (e.g., "Not authorized to access").
[0115] In certain embodiments, the process (800) is performed partially or entirely by one or more other devices other than the verification device. For example, the verification device may include an environment device. In certain embodiments, the verification device is coupled to communicate with the resident device via wired and / or wireless connections. The verification device may be coupled to communicate directly (e.g., without any intermediate network hops) with the resident device and / or the locality verification system, and / or coupled to communicate indirectly (e.g., with one or more intermediate network hops) with the resident device and / or the locality verification system. In certain embodiments, the resident device does not include the locality verification system. In certain embodiments, the server includes the locality verification system.
[0116] Although specific embodiments have been described, various modifications, changes, alternative configurations, and equivalents are also included within the scope of this disclosure. The embodiments are not limited to operation within specific data processing environments but operate freely within a plurality of data processing environments. Additionally, although the embodiments have been described as using a specific series of transactions and steps, it will be apparent to those skilled in the art that the scope of this disclosure is not limited to the described series of transactions and steps. Various features and aspects of the aforementioned embodiments may be used individually or in combination.
[0117] Additionally, although the embodiments have been described using a specific combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of this disclosure. The embodiments may be implemented using hardware alone, software alone, or a combination thereof. The various processes described herein may be implemented on the same processor or on any combination of different processors. Thus, where components or services are described as being configured to perform certain operations, such configuration may be achieved, for example, by designing electronic circuits to perform the operations, by programming programmable electronic circuits (e.g., microprocessors) to perform the operations, or by any combination thereof. Processes may communicate using various techniques, including but not limited to conventional techniques for inter-process communication, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times.
[0118] Accordingly, the specification and drawings should be regarded as illustrative rather than restrictive. However, it will be apparent that additions, reductions, deletions, and other modifications and alterations may be made without departing from the broad spirit and scope as set forth in the claims. Accordingly, although embodiments of a particular disclosure have been described, they are not intended to be restrictive. Various modifications and equivalents fall within the scope of the following claims.
[0119] In describing the disclosed embodiments (particularly with respect to the claims below), the use of the terms “a,” “an,” and “the,” and similar referents, shall be interpreted to cover both the singular and plural forms, unless otherwise indicated herein or clearly contradicted by the context. The terms “comprising,” “having,” “including,” and “containing” shall be interpreted as open-ended terms (i.e., meaning “including but not limited thereto”) unless otherwise stated. The term “connected” shall be interpreted as being partially or wholly contained therein, attached thereto, or combined therewith, even if there is something interposed. The enumeration of ranges of values in this specification is intended to serve merely as a shorthand method for individually referring to each distinct value within the range, unless otherwise indicated in this specification, and each distinct value is included in this specification as if it were individually enumerated in this specification. All methods described in this specification may be performed in any suitable order unless otherwise indicated in this specification or otherwise clearly contradicted by the context. Any and all examples provided in this specification, or the use of exemplary language (e.g., “like”), are intended merely to clarify the embodiments and do not impose any limitation on the scope of this disclosure unless otherwise claimed. No expression in this specification should be interpreted as indicating any non-claimed element as essential to the practice of this disclosure.
[0120] Disjunctive language, such as the phrase “at least one of X, Y, or Z,” is intended to be understood in context as is commonly used to indicate that an item, term, etc. may be any one of X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z), unless specifically stated otherwise. As such, such disjunctive language is not intended, and should not be, to imply that certain embodiments generally require at least one of X, at least one of Y, or at least one of Z to be present, respectively.
[0121] Preferred embodiments of the present disclosure, including the best known mode for carrying out the present disclosure, are described herein. Variations of the preferred embodiments may become apparent to those skilled in the art upon reading the foregoing description. Those skilled in the art should be able to appropriately adopt such variations, and the present disclosure may be practiced differently from as specifically described herein. Accordingly, the present disclosure includes all modifications and equivalents of the subject matter enumerated in the claims appended to this specification, as permitted by applicable law. Furthermore, any combination of the elements in all possible variations of the elements described above is encompassed by the present disclosure unless otherwise indicated herein.
[0122] All references cited herein, including publications, patent applications, and patents, are thereby indicated as being incorporated by reference individually and specifically, to the same extent as if the entirety thereof were described herein.
[0123] In the foregoing specification, aspects of the present disclosure are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the present disclosure is not limited thereto. Various features and aspects of the foregoing disclosure may be used individually or together. Furthermore, embodiments may be used in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the present specification. Accordingly, the specification and drawings should be regarded as illustrative rather than restrictive.
Claims
Claim 1 A computer-implemented method comprising: receiving a first locality credential indicating that the user device is within a first locality by a first device connected to a network from a user device; obtaining a second locality credential indicating that the user device is within a second locality by the first device; determining by the first device whether the first locality credential is trusted based at least partially on a comparison of the first locality and the second locality; and enabling the user device to access the network associated with the first device by the first device in accordance with the determination that the first locality credential is trusted. Claim 2 A computer implementation method according to claim 1, wherein the first locality credential is trusted based on the first locality being in the same location as the second locality. Claim 3 A computer-implemented method according to claim 1, wherein the first locality credential is not trusted if the first locality is not the same locality as the second locality; and the method further comprises the step of disabling access to the network by the first device according to a second determination that the first locality credential is not trusted. Claim 4 A computer-implemented method according to claim 1, wherein the first device manages access to a third device connected to the network; the third device is accessed by the first device according to the determination that the first locality credential is trusted; and the second device is located in a known second locality indicated by the second locality credential. Claim 5 A computer implementation method according to claim 1, further comprising the step of determining whether the second locality credential is trusted by the first device and before the network is accessed by the user device through the network. Claim 6 The computer implementation method of claim 1 further comprises the step of receiving, by the first device, an indication that the user device has left the first locality; and, after receiving the indication that the user device has left the first locality, the step of disabling the user device's access to the network by the first device. Claim 7 The computer implementation method of claim 1 further comprises the step of setting a time to live based on determining that the first locality credential is trusted—the network is accessible until the time to live expires—; the step of receiving a third locality credential by the first device; and the step of adjusting the time to live. Claim 8 A computer-implemented method according to claim 1, wherein, in accordance with the determination that the first locality credential is trusted, the first device enables the user device to access the third device through the network, and the third device comprises a smart accessory configured as at least one of a television, an audio device, a lighting fixture, a garage door opener, a building cover, a camera, a lock, an alarm system, or an air conditioning unit. Claim 9 A computer-implemented method according to claim 1, wherein the first locality credential is associated with a score, and when the score exceeds a predefined threshold score, the first locality credential is trusted. Claim 10 A computer-implemented method according to claim 1, wherein the first locality credential or the second locality credential is received using infrared communication or radio communication. Claim 11 A first device comprising: a memory configured to store computer-executable instructions; and one or more processors configured to communicate with said memory, access said memory, and execute said computer-executable instructions, wherein said computer-executable instructions are at least: Receiving a first locality credential indicating that the user device is within a first locality from the first device connected to the network from the user device; By the first device, a second locality credential indicating that the user device is within the second locality is obtained; The first device determines whether the first locality credential is trusted based at least partially on a comparison of the first locality and the second locality; A first device for enabling the user device to access the network associated with the first device by the first device, based on a determination that the first locality credential is trusted. Claim 12 In paragraph 11, the first locality credential is a first device that is trusted based on the fact that the first locality is in the same location as the second locality. Claim 13 In paragraph 11, the first locality credential is not trusted if the first locality is not the same locality as the second locality; the one or more processors are further configured to access the memory and execute the computer-executable instructions, the computer-executable instructions being: a first device, wherein, in accordance with a second determination that the first locality credential is not trusted, the first device is configured to disable access to a third device connected to the network associated with the first device by the first device. Claim 14 In paragraph 11, the first device manages access to a third device connected to the network; the third device is accessed by the first device in accordance with the determination that the first locality credential is trusted; and the second device is located in a known second locality indicated by the second locality credential, the first device. Claim 15 In claim 11, the first device, wherein obtaining the second locality credential comprises executing computer-executable instructions for receiving the second locality credential from the second device by the first device. Claim 16 One or more computer-readable storage media comprising computer-executable instructions, wherein the computer-executable instructions, when executed by one or more processors of a device, cause the one or more processors to perform operations, the operations comprising: receiving a first locality credential indicating that the user device is in a first locality by a first device connected to a network from a user device; obtaining a second locality credential indicating that the user device is in a second locality by the first device; determining by the first device whether the first locality credential is trusted based at least partially on a comparison of the first locality and the second locality; and enabling the user device to access the network associated with the first device by the first device in accordance with the determination that the first locality credential is trusted. Claim 17 In paragraph 16, the first locality credential is one or more computer-readable storage media that are trusted based on the first locality being in the same location as the second locality. Claim 18 In paragraph 16, the first device manages the access to the network; and the second device is one or more computer-readable storage media located in a known second locality indicated by the second locality credential. Claim 19 A computer-implemented method according to claim 16, wherein the first locality credential comprises at least one of a first coordinate, a first image data, a first device identifier, a first locality credential identifier, a first user identifier, a first timestamp, a first indication of a communication type, or a first sound data, and the second locality credential comprises at least one of a second coordinate, a second image data, a second device identifier, a second locality credential identifier, a second user identifier, a second timestamp, a second indication of a communication type, or a second sound data. Claim 20 A computer-implemented method according to claim 16, wherein the first locality credential is received at least partially based on at least one of a near-field communication (NFC) signal, a password input, a personal identification number (PIN) input, a Bluetooth signal, a Wi-Fi signal, or an out-of-band signal.
