Building entry using mobile devices

Abstract

The present invention is entitled "Building Access Using a Mobile Device". The present invention discloses a method and system for unlocking entry points to a facility using a mobile device. Permissions and locations of entry points to a facility accessible to a user of a particular mobile device may be downloaded, and the location of the particular mobile device may be determined. The mobile device may identify one or more entry points to a facility accessible to a user of the mobile device based on the location of the mobile device and the downloaded permissions and locations of the entry points to the facility. The method may include: displaying a notification of entry points identified by the mobile device on the mobile device; receiving a selection of one of the displayed entry points from the user via a user interface of the mobile device; sending a command from the mobile device to unlock the selected entry point; and unlocking the selected entry point.

Description

Technical Field

[0001] The present disclosure relates to providing building access via mobile devices. Background Art

[0002] Physical access control systems are designed to allow access to buildings and / or specific areas of buildings to individuals who are authorized to enter such areas, and to deny access to buildings and / or specific areas of buildings to individuals who are not authorized to enter such areas. For example, certain individuals may be authorized to enter secure areas of a building, while other individuals may not be allowed to enter secure areas. In another example, certain individuals may be authorized to enter a first building, but not a second building, while other individuals may not be allowed to enter either building. In some cases, access may be granted only during certain times.

[0003] Current methods of physical access control systems typically rely on users (e.g., employees) to carry physical access cards (e.g., physical badges) to gain access to building areas. For example, a user may swipe a physical access card in an access card reader at a security door to gain access to building areas. However, issuing and managing physical access cards can be time consuming, cumbersome, and prone to error. A system that allows a user's mobile device to serve as an access credential for current building access systems is desired. Summary of the invention

[0004] The present disclosure relates to providing and / or managing access control, and more particularly, to methods and systems for using a user's mobile device as an access credential to gain access to one or more authorized areas.

[0005] An example method for managing access to a facility may include selecting a debug mode in an application running on a mobile device. While in the debug mode, displaying a list of entry points associated with the facility via a user interface of the mobile device, receiving a selection of an entry point from the list of entry points via the user interface of the mobile device, physically placing the mobile device near the selected entry point, capturing and storing a current location of the mobile device and thus the location of the selected entry point, associating the captured location of the mobile device with the selected entry point, repeating the receiving, placing, capturing, and associating steps for each of two or more entry points in the list of entry points, and uploading the associations between the captured location of the mobile device and each of the two or more entry points. These associations may be used to control access to the facility.

[0006] In some cases, the method may include: subsequently receiving a registration request from a user via a user interface of a user mobile device; associating the user and the user mobile device with one or more entry points in a list of entry points based on one or more user permissions; displaying at least some of the one or more entry points associated with the user based on the one or more user permissions on the user mobile device; selecting to unlock one of the displayed entry points via the user interface of the user mobile device; and sending a request to unlock the selected entry point.

[0007] In some cases, the method may include: determining a current location of the user mobile device; and determining a distance between the current location of the user mobile device and a location captured in debug mode and associated with each of the two or more entry points. The entry points displayed on the user interface of the user mobile device may be entry points within a threshold distance of the current location of the user mobile device.

[0008] In another example, a method for unlocking an entry point of a facility may include: downloading permissions and locations of entry points of the facility accessible to a user of a specific mobile device; and receiving the location of the specific mobile device. The specific mobile device may determine one or more entry points of the facility based on the location of the specific mobile device and the download permissions and locations of the entry points of the facility. The method may also include: displaying a notification of one or more entry points determined by the specific mobile device on the specific mobile device; receiving a selection of one of the displayed entry points from the user via a user interface of the specific mobile device; sending a command to unlock the selected entry point from the specific mobile device; and unlocking the selected entry point. Before unlocking the selected entry point, the method may also include verifying one or more entry credentials of the user.

[0009] In some cases, the notification of one or more entry points may identify entry points within a predetermined distance from a particular mobile device and may not include entry points that are not within the predetermined distance from the particular mobile device. Alternatively, the notification of one or more entry points may include all entry points in a facility accessible to the user.

[0010] In another example, a non-transitory computer-readable medium having stored thereon instructions that, when executed by a mobile device, may be configured to: receive user credentials from a user via a user interface of the mobile device to verify the identity of the user; verify the received user credentials of the user; receive a current location of the mobile device from a location service of the mobile device; determine a distance between the current location of the mobile device and each of one or more entry points of a facility; and display one or more of the entry points of the facility on the user interface of the mobile device. The one or more entry points displayed may be one or more entry points that are accessible to the user based on one or more entry point permissions associated with the user and, in some cases, are within a threshold distance from the current location of the mobile device. The user interface of the mobile device may receive a selection to unlock one of the displayed entry points, and the mobile device may send a request to an access control system of the building to unlock the selected entry point.

[0011] The above summary is provided to facilitate understanding of some features of the present disclosure, but is not intended to be a complete description. A comprehensive understanding of the present disclosure can be obtained by taking the entire specification, claims, drawings and abstract as a whole. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The present disclosure may be more fully understood upon consideration of the following detailed description of various embodiments in conjunction with the accompanying drawings, in which:

[0013] Figure 1 is a schematic diagram of an illustrative access control system for accessing a plurality of buildings via a mobile device;

[0014] Figure 2 is a flow chart of an illustrative method for commissioning an access control system;

[0015] Figures 3 to 5 is an illustrative screen shot of an application for use by installers to commission an entry control system;

[0016] Figure 6 is a flow chart of an illustrative method of entering a building using a user's mobile device;

[0017] Figure 7 is a descriptive setup portal for access control systems for use by administrators;

[0018] Figure 8 is a flow chart of another illustrative method of entering a building using a user's mobile device; and

[0019] Figures 9 to 12 is an illustrative screenshot of an application running on a user's mobile device to enter a building.

[0020] Although the present disclosure is subject to various modifications and alternative forms, the details thereof have been shown by way of example in the accompanying drawings and will be described in detail. However, it should be understood that it is not intended to limit the aspects of the present disclosure to the specific embodiments described. On the contrary, it is intended to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the present disclosure. DETAILED DESCRIPTION

[0021] For the following defined terms, these definitions shall prevail unless a different definition is given in the claims or elsewhere in this specification.

[0022] Whether or not explicitly indicated, all numerical values ​​are assumed herein to be modified by the term "about". The term "about" generally refers to a range of numbers that one skilled in the art would consider equivalent to the recited value (i.e., having the same function or result). In many cases, the term "about" may be indicated to include numbers rounded to the nearest significant figure.

[0023] The recitation of numerical ranges by endpoints includes all numbers within that range (eg, 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).

[0024] While some suitable sizes, ranges and / or values ​​are disclosed in connection with various components, features and / or specifications, those skilled in the art to which this disclosure refers will appreciate that the desired sizes, ranges and / or values ​​may deviate from those explicitly disclosed.

[0025] As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term "or" is generally employed in its sense including "and / or" unless the content clearly dictates otherwise.

[0026] The following description should be read with reference to the accompanying drawings, in which similar elements in different drawings are numbered in the same manner. The accompanying drawings show, by way of example, the manner in which one or more embodiments of the present disclosure may be practiced. The exemplary embodiments shown are intended to be exemplary only. Unless expressly stated to the contrary, selected features of any exemplary embodiment may be incorporated into another embodiment.

[0027] The user's interaction with the access control system can be streamlined using the capabilities provided by the mobile device. For example, in some embodiments, the global positioning system (GPS), WiFi, Bluetooth, and / or other location functionality provided by the mobile device can allow for automatic determination of the user's location (e.g., without user input). Therefore, in some cases, instead of physically presenting a card (or other device) for entering an area or facility, the user can simply move within a specific distance of the door and be automatically presented with the option of unlocking the door. Embodiments of the present disclosure allow the user's mobile device to perform the functionality of an access card instead of using a "card reader." It is contemplated that embodiments of the present disclosure can be used with a variety of entry systems. In some cases, embodiments of the present disclosure can be used with systems having access control card readers (with and / or without Alternatively or in addition, embodiments of the present disclosure may be used with a system that includes only an actuable locking mechanism (e.g., without a card reader).

[0028] The present disclosure generally relates to methods and systems for allowing secure access to one or more entry points using a mobile device. It is contemplated that the system may allow a user to use the same mobile device to enter two different buildings with two different access control vendors. In some cases, the buildings may belong to the same entity (e.g., a business and a company), or the buildings may belong to different entities, as may be the case where personnel service certain building equipment that is used in many buildings. Typically, the entry points may be marked with a geographic location (e.g., latitude, longitude, and / or altitude) and a door name. These entry points may be selectively provided to the user via the user's mobile device. Actuation of an unlock button on the mobile device may result in unlocking of the door.

[0029] Embodiments of the present disclosure may reduce the need to issue physical badges to each location or facility that a person (e.g., employee, contractor, maintenance worker, etc.) needs to enter. Embodiments of the present disclosure may be retrofitted to existing access control systems with and / or without smart reader systems without having to add additional hardware. Furthermore, embodiments of the present disclosure may streamline or facilitate access requests to facilities and / or locations.

[0030] Figure 1is a schematic diagram of an illustrative access control system 10 for multiple buildings 20, 30 via a user's mobile device 40. As used herein, a facility or building may refer to one or more buildings, businesses, homes, factories, hospitals, refineries, etc. A facility may include indoor and / or outdoor areas. The illustrative system 10 may include a first facility 20, a second facility 30, a mobile device 40, a first access control system (ACS) 50 that optionally includes at least one card reader 51 and communicates with one or more relay stations 22a, 22b (collectively referred to as 22), and a second access control system (ACS) 60 that optionally includes at least one card reader 61 and communicates with one or more relay stations 32a, 32b (collectively referred to as 32). Although the illustrative system 10 includes a first facility 20 and a second facility 30, it should be understood that the system 10 can be applied to less than two facilities or more than two facilities, such as but not limited to three or more, 10 or more, 20 or more, 50 or more, etc. Similarly, although the illustrative system 10 is shown with a first access system 50 and a second access system 60, it should be understood that the system 10 can be applied to fewer than, more than, or more than two access systems. In some cases, the number of access systems can correspond to the number of facilities in the system 10. Although the access control systems 50, 60 are described as door access control systems, the access control systems 50, 60 can control other means of access to a building or area, including but not limited to turnstiles or flap doors, revolving doors, gates, etc.

[0031] Despite Figure 1 In the illustrated example, the first ACS 50 is shown as being outside the first facility 20 (e.g., remote relative to the first facility 20), and the second ACS 60 is shown as being outside the second facility 30 (e.g., remote relative to the second facility 30), but embodiments of the present disclosure are not limited thereto. In some cases, the first ACS 50 and / or the second ACS 60 are inside the first facility 20 (e.g., local relative to the first facility 20) and / or the second facility 30 (e.g., local relative to the second facility 30), respectively.

[0032] The mobile device 40 may be a client device carried or worn by a user. It should be understood that more than one mobile device 40 may be used with the access control system 10. For example, each user may have his or her own specific or unique mobile device 40. The mobile device 40 may be a phone (e.g., a smart phone), a personal digital assistant (PDA), a tablet computer, and / or a wearable device (e.g., a wristband, a watch, a necklace, etc.). These are just examples. The mobile device 40 may include a user interface including a display and a device for receiving user input (e.g., a touch screen, a button, a keyboard, etc.). The mobile device 40 may also have location services. For example, the mobile device 40 may use a built-in global positioning system (GPS) in combination with GPS satellites to accurately determine the location of the mobile device 40. In other cases, the location of the mobile device 40 may be estimated based on the direction of the signal and the distance from one or more cell towers. The mobile device 40 may include one or more software applications (e.g., applications) 46 stored in the memory 42 of the mobile device 40, which may define and / or control the communication between the mobile device, the first ACS 50, the second ACS 60, and / or other devices. In some cases, the mobile device 40 may communicate with the first ACS 50, the second ACS 60, and / or other devices via a remote or cloud server 70, as will be described in greater detail herein. For example, the application 46 may be received by the mobile device 40 from the first ACS 50 and / or the second ACS 60, although this is not required. In other embodiments, the application 46 may be downloaded from an application store, such as, but not limited to, or GOOGLE Or go to the website of the control service provider.

[0033] In some embodiments, the application 46 may be an integrated security platform that may include access control and security system components. The user may manage the access control system and / or security system from the application 46 and / or via a web browser as desired. In some cases, the application 46 may present different features based on the user's login credentials. It is contemplated that the amount and type of information visible to users of the application 46 may be based at least in part on the permissions assigned to a particular user. For example, members of the security team may have access to security system components that regular building users may not. In addition, some users may be able to access a debug mode that other users may not. In some cases, different applications 46 may be used for regular employees and visitors.

[0034] Application 46 may be initiated by the user and / or in response to some other condition (e.g., interaction between mobile device 40 and a device within the access control system (such as a controller or relay station), or when the location service of the mobile device detects that the mobile device is located near a facility that the user has registered to enter). In some embodiments, application 46 may be executed as a background application. As used herein, at least one of application 46 includes a digital identifier. In some cases, the digital identifier may be a identifier generated by the phone operating system (e.g., Android TM (Android is a trademark of Google LLC), (IOS is a trademark of Cisco and used with permission by Apple), etc.) to provide a unique device identifier to uniquely identify a mobile device. In other cases, the digital identifier may include, but is not limited to, a telephone number and / or an International Mobile Equipment Identity (IMEI) code. In some cases, at least one of the applications 46 may include more than one digital identifier.

[0035] In the example shown, the relay stations 22, 32 can be actuated by a change in the condition of one or more circuits. In some examples, the relay stations 22, 32 can be locking devices (e.g., for doors). In some examples, the relay stations 22, 32 can include one or more actuating mechanisms. The relay stations 22, 32 can be associated with one or more controlled functionalities. As used herein, "controlled functionality" refers to functionality under the control of the first ACS 50 and / or the second ACS 60. For example, an electronic door lock may include a relay station that is controlled by the first ACS 50 and / or the second ACS 60 to lock / unlock a door.

[0036] The relay stations 22a, 32a can be associated with the entry points (e.g., exterior doors) of the respective facilities 20, 30, and / or the relay stations 22b, 32b can be associated with specific areas 24, 34 of the respective facilities 20, 30. As mentioned herein, an area can be a part of a facility. In some embodiments, the area 24, 34 can be a room, a plurality of rooms, a wing, a building, a plurality of buildings, a campus, etc. In some embodiments, the area 24, 34 can be defined by physical boundaries (e.g., walls, doors, etc.). In some embodiments, the area 24, 34 can be defined by logical and / or geographic boundaries (e.g., geo-fences). The area 24, 34 can be defined by a user through a building information model (BIM) associated with the respective facilities 20, 30, by a first ACS 50 and / or a second ACS 60, and / or in any other suitable manner.

[0037] The first ACS 50 and / or the second ACS 60 can control (e.g., manage) access to multiple areas (e.g., areas 24, 34) and / or the number of entry points to the respective facilities 20, 30. As previously discussed, the first ACS 50 and / or the second ACS 60 can be remote relative to the facilities 20, 30 and / or local relative to the facilities 20, 30. In some embodiments, the first ACS 50 and / or the second ACS 60 can be cloud-based. In some embodiments, the first ACS 50 and / or the second ACS 60 can manage access to one or more areas across multiple facilities. It is further contemplated that the first ACS 50 and the second ACS 60 can be configured to accept different credentials and / or can have different connectivity, although this is not required.

[0038] For example, the mobile device 40 can communicate (e.g., exchange data) with the first ACS 50 and / or the second ACS 60 via wired and / or wireless connection. In some cases, communication can occur via a cloud server 70. For example, the mobile device 40 can transmit information to the cloud server 70, and the cloud server 70 can process information and then transmit commands to appropriate ACS 50, ACS 60. In some embodiments, the mobile device 40 can use one or more communication modules (e.g., cellular, WiFi, etc.) to communicate. For example, the first ACS 50 and / or the second ACS 60 can communicate with the relay station 22,32 via wired and / or wireless connection. The communication between various devices herein can be carried out on a wireless and / or wired network. As used herein, a wireless network can include WiFi, Bluetooth, cellular or any other suitable means to wirelessly transmit and / or receive information.

[0039] The illustrative mobile device 40 includes a memory 42 and a processor 44. The processor 44 is configured to execute executable instructions stored in the memory 42 to perform various tasks. Data may also be stored in the memory 42 for executing the instructions. For example, in some embodiments, the memory 42 stores instructions executable by the processor 44 to provide data in the form of a specific user identity assigned to the mobile device to the access control system. The memory 42 may be any type of non-transitory storage medium that can be accessed by the processor 44 to perform various examples of the present disclosure. For example, the memory 42 may be a non-transitory computer-readable medium having computer-readable instructions (e.g., computer program instructions) executable by the processor 44 stored thereon. The execution of the computer-readable instructions may result in the actuation of the relay station 22, 32, which in turn allows access to the facility 20, 30 and / or the area 24, 34 of the facility 20, 30.

[0040] The memory 42 may be a volatile or non-volatile memory. The memory 42 may also be a removable (e.g., portable) memory or a non-removable (e.g., internal) memory. For example, the memory 42 may be a random access memory (RAM) (e.g., a dynamic random access memory (DRAM) and / or a phase change random access memory (PCRAM)), a read-only memory (ROM) (e.g., an electrically erasable programmable read-only memory (EEPROM) and / or a compact disc read-only memory (CD-ROM)), a flash memory, a laser disc, a digital versatile disc (DVD) or other optical storage device, and / or a magnetic medium such as a cassette, a tape or a disk, among other types of memory.

[0041] In addition to or in lieu of executing executable instructions, various functions of the present disclosure may be performed via one or more devices (e.g., one or more controllers) having logic. As used herein, "logic" is an alternative or additional processing resource that performs the actions and / or functions described herein, etc., including hardware (e.g., various forms of transistor logic, application specific integrated circuits (ASICs), etc.), rather than computer executable instructions (e.g., software, firmware, etc.) stored in memory and executable by a processor. It is assumed that the logic similarly executes instructions for the purposes of the embodiments of the present disclosure.

[0042] In some cases, the memory 42 may store data in the form of a digital identifier associated with an application 46 also stored in the memory 42 on the mobile device 40. The memory 42 may also include instructions executable by the processor 44 to provide this information to the access control system when the application 46 is in use and the user has satisfied certain conditions that enable the user to request that the digital identifier be sent to the access control system. In some cases, before the application 46 will initiate any sending of the identifier and / or unlocking command, the user must authenticate himself to the mobile device by entering a password or fingerprint scan to unlock the mobile device 40 and / or the application 46.

[0043] Figure 246 is a flowchart of an illustrative method 100 for debugging an access control system (such as, but not limited to, ACS 50 and / or ACS 60) used with a mobile device 40 and an application 46. Although one or more access control systems 50, 60 can be debugged using the same application or by the same person, for the sake of brevity, a description of the debugging procedure will be described for a single access control system 50. In some cases, the method 100 for debugging an access control system can be performed by an installer or other designated person. However, this is not required. Initially, a user can select a debug mode in an application (e.g., application 46) running on a mobile device 40, wherein the mobile device includes both a user interface and a location service. Prior to entering the debug mode or once in the debug mode, the application can be configured to display the available systems of the facility (e.g., access control system, security system, etc.) to the user. In some cases, the debug mode can be entered after a specific system is selected. Figure 3 200 is an illustrative screen shot of a summary screen that may be displayed on a mobile device 40 via an application 46 for a particular building (e.g., facility 20) when a supervising user or installer has entered their user credentials (e.g., username and password, facial recognition, fingerprint recognition, etc.). The application 46 may be configured to display a status 202 of the security system, a number 204 of entry points connected to the entry control system 50, cameras or other devices 206 associated with the security system, a number of people in the facility 208, and / or an overview 210 of activity. These are just examples. Some information may be omitted or additional information may be included as desired. In some cases, the summary screen 200 may be based on user-defined settings or preferences.

[0044] return Figure 2 In the debug mode, a list of entry points associated with the facility may be displayed on a user interface of the mobile device 40 , as shown in block 104 . Figure 4 is an illustrative screen shot 220 of a list of entry points 222 associated with a facility 30. Figure 3 This screen 220 is reached by entering point 204 on screen 200. Return Figure 2 A selection of an entry point from the list of entry points may be received via a user interface of the mobile device 40, as shown in block 106. The entry point need not display a card reader. For example, any entry point capable of having a remotely actuated locking mechanism may be displayed. Figure 5 is an illustrative screen shot 230 of the details of a selected entry point. In the illustrative embodiment, from Figure 4 220 of the screen shot 220. In the illustrated embodiment, the user has the option of selecting an "action" button 232 or selecting a "mark location" button 234. Return Figure 2 , the mobile device 40 may be carried and physically placed near the selected entry point, as shown in block 108. In some cases, the user may need to travel to the selected entry point in order to place the mobile device 40 adjacent thereto. It is contemplated that the entry point list 222 may be dynamically updated as the installer moves through the facility 20 to display only the entry points that are proximate to the installer, although this is not required. In some cases, the entry point list 222 may display all of the entry points in the facility 20.

[0045] Once the mobile device 40 is proximate to the selected entry point, the current location of the mobile device 40 and therefore the location of the selected entry point may be captured and stored, as shown in block 110. In some cases, this may be performed by selecting a mark location button 234 on a user interface of the mobile device 40. Using a location service of the mobile device 40, the location of the mobile device 40 may be determined using the GPS location of the mobile device 40. The GPS location may include latitude, longitude, and altitude, such as Figure 5 The captured location of the mobile device 40 may be associated with the selected entry point, such as Figure 2 As shown in block 112 of FIG. In some cases, the capture location may be stored with the selected entry point in a database in the cloud server 70. In other cases, the capture location may be stored locally within the facility 20 and / or any other suitable location.

[0046] Next, it may be determined whether a location has been captured and stored for each entry point to the facility 20 that is desired to be accessible via the mobile device, such as Figure 2 If not all entry points are captured, then the following steps may be repeated for each entry point that is desired to be accessible via mobile device 40: receiving a selection of an entry point 106; placing mobile device 40 near the selected entry point 108; capturing and storing the location of mobile device 40 110; and associating the captured location of mobile device 40 with the selected entry point 112. In some cases, Figure 4 The receiving 106, placing 108, capturing 110, and associating 112 steps are repeated for each of two or more entry points in the entry point list shown in FIG.

[0047] The association between the captured location of the mobile device 40 and each of the entry points may then be uploaded, as shown in block 116. In some cases, the captured location of the mobile device and each of the entry points may be uploaded to a remote cloud server 70. In other cases, the captured location of the mobile device and each of the entry points may be uploaded to a server or storage device located locally at the facility. Once the associations are stored, they may be used to control access to and within the facility 20, as shown in block 118.

[0048] In some cases, the user may then need to register with the access control system 50 to use the mobile device 40 to enter the facility 20 or an area 24 within the facility 20 . Figure 6 300 is an illustrative flow chart of a method for registering a user to an ACS 60 and entering an entry point. Initially, a registration request may be received from a user, as shown in block 302. In some cases, a user may initiate a user registration request for entering one or more entry points in a facility 20 via an application 46. In other cases, a user may initiate a user registration request via a web browser, email, or any other suitable mechanism. In some cases, a supervisory user may initiate a registration request on behalf of a user. Once a user request is received, the user and the user's mobile device 40 may be associated with one or more entry points, as shown in block 304. It is contemplated that the number of entry points or which particular entry point may be associated with a user may be determined based at least in part on the user's employment status and / or hierarchy level. For example, a regular employee may have the ability to enter more entry points than a contract employee, who in turn may have the ability to enter more entry points than a visitor. This is just one example.

[0049] In some cases, the registration process can be performed by a supervisory or administrative user. For example, an administrative user can utilize a mobile device access setup portal to associate a user and / or a user's mobile device with access permissions. Figure 7 is a screen shot of an illustrative mobile device access setup portal 350 for use by an administrator. The setup portal 350 may include a list or menu 352 of selectable options. For example, the menu 352 may allow a supervisory user to view detailed information related to a building site 20, 30 and / or its access control system 50, 60. In some cases, the menu 352 may include an option for allowing a supervisory user to view and / or edit a "person" 354 associated with the organization (among other options). Figure 7 In the illustrative embodiment of , a person 354 has been selected and detailed information about the person associated with the organization is displayed. For example, the setup portal 350 includes a list of people 356. The list may include an image 358 and an employment status 360 (e.g., visitor, permanent employee, contract employee, temporary employee, etc.) for each particular person. This list 356 may also include access credentials 362 associated with the particular person. Selection of a particular person may allow the administrative user to edit information and / or permissions associated with the particular person.

[0050] exist Figure 7 In the illustrative embodiment of , a new user is added in area 364 of the screen. The administrative user can create a profile for the new user by selecting the Profile tab 366 and can add permissions by selecting the Permissions tab 368. Figure 7In the illustrative embodiment of , the permissions tab 368 has been selected. The supervisory user can add a card-based access credential 370 assigned to the new user, although this is not required. The supervisory user can also add information that associates a specific mobile device 40 with the new user, such as, but not limited to, a unique device identifier 372 of the user's mobile device and / or a mobile device phone number 374. In some cases, the unique device identifier 372 can be automatically detected via the application 46 and transmitted by user request. The supervisory user can also assign the user to a permission group 376, which determines which entry point or entry point group the user is authorized to enter using the mobile device 40 (and / or access card). For example, a user and a user mobile device 40 can be associated with one or more entry points from the entry point list 376 based on one or more user permissions. In some cases, the user may not be granted access. In other cases, a custom permission group can be assigned to the user. The administrative user can also select an activation date 378 and / or an expiration date 380 to further customize the user's access permissions. It is further contemplated that the supervisory user can assign a time window in which the user can utilize the entry point. For example, the user can be allowed to use the entry point during predetermined hours and / or predetermined days.

[0051] In some cases, a visitor to the facility 20 may be able to submit an entry request for pre-approval. It is contemplated that when a visitor request is approved and credentials are assigned, the visitor may receive an email or text message with a link to download the application 46 and registration credential information. In other cases, the visitor may use the application 46 to register or submit a visit request. This may facilitate visitor entry during high volume hours.

[0052] return Figure 6Once the user and the user mobile device have been associated with one or more entry points, the user can begin to use the mobile device 40 to open one or more entry points. Typically, the user can open the application 46 on the mobile device 40 to display at least some of the entry points available to the user on the user mobile device 40, as shown in box 306. It is contemplated that not all entry points available to the user are displayed at the same time (based on user permissions). For example, the current location of the user mobile device 40 can be used to select a subset of the available entry points to be displayed. The distance between the current location of the user mobile device 40 (as determined by the location service of the user mobile device 40) and the location of the entry point (and associated entry points) captured in the debug mode can be determined. Entry points within a threshold distance of the current location of the user mobile device 40 can be displayed on the user interface of the user mobile device 40. It is contemplated that the threshold distance is programmable. This can facilitate the location of the entry point desired to be opened by reducing the number of entry points visible to the user. The user can then select one of the displayed entry points to unlock, as shown in box 308. In some cases, a request to unlock the entry point can be sent to the ACS 60 via the intermediate cloud server 70, as shown in box 310. In some cases, the user may receive confirmation on the user mobile device 40 that the access point has been unlocked.

[0053] Figure 8400 is a flow chart of another illustrative method 400 for entering a building using a user's mobile device 40. It should be understood that the actions performed at the mobile device 40 are implemented by the processor 44 executing executable instructions stored in the memory 42 of the mobile device 40 and / or the logic of the mobile device 40. Initially, the permissions and locations of the entry points of the facility accessible to the user of the particular mobile device 40 are downloaded to the particular mobile device 40, as shown in block 402. It is contemplated that this step may not be required every time the user accesses the application 46. The user may present the user credentials to the application 46 via the user interface of the mobile device 40 in order to authenticate to the application 46 to verify the user's identity. This may include providing a username and password and / or using biometrics, such as, but not limited to, fingerprint recognition and / or facial recognition. In some cases, the user credentials may be verified by comparing the provided credentials with the credentials stored at the mobile device 40 or at the cloud server 70 as needed. Once the user is authenticated, the permissions and locations of the entry points in the facility accessible to the user (e.g., as defined in the setup portal) may be downloaded (e.g., from the cloud server 70 or local facility storage) to the user's mobile device 40 and stored in its memory 42. This may allow for faster response times during use of the application 46, but may not be required. For example, the application 46 may access permissions and locations stored remotely, such as at a cloud server 70. Access permissions and locations may include, but are not limited to, which entry points are available to the user, the GPS location of the entry point, the user's employment status, entry time windows, etc.

[0054] As shown in box 404, the location of the specific mobile device 40 can be received or determined. For example, the application 46 can receive the GPS location of the mobile device from the location service of the mobile device 40. In some cases, the mobile device 40 can be configured to recognize the error metric of the current location of the mobile device 40. In some cases, the specific mobile device 40 can then determine one or more entry points of the facility to be displayed to the user based on the location of the specific mobile device, the download permissions, and the location of the entry points of the facility, as shown in box 406. For example, the specific mobile device 40 can determine which entry point the user can enter (based on the assigned permissions) and / or which entry point is within a predetermined threshold distance of the user. It is contemplated that the threshold distance can take into account the error metric that may occur when locating the location of the mobile device 40. For example, the threshold distance can be based at least in part on the identification error metric in the current location of the mobile device. In some cases, the mobile device 40 can be configured to determine the distance between the current location of the mobile device 40 and each of the one or more entry points of the facility. The notification of the one or more entry points determined by the specific mobile device can be displayed on the specific mobile device, as shown in box 408.

[0055] In some cases, the notification may identify those entry points that are within a predetermined distance from a particular mobile device 40 and exclude those entry points that are not within a predetermined distance from a particular mobile device 40. In some embodiments, the notification identifies or includes all entry points in the facility accessible to the user. In some cases, the entry points displayed on the user interface of the user device 40 may be entry points that are accessible to the user based on one or more entry point permissions associated with the user and that are within a threshold distance from the current location of the mobile device 40. It is contemplated that the displayed entry points may be continuously or repeatedly updated based on the current location of the mobile device 40. For example, when the mobile device 40 moves away from a particular entry point, the particular entry point may be removed from the notification, and additional entry points may be added when the mobile device 40 enters within the threshold distance.

[0056] Fig. 9 It is a screenshot 450 of a notification or list 452 of available entry points that can be displayed to a user on a specific mobile device. The list 452 of available entry points can vary with the user based on user location and / or user permissions. In some cases, a specific mobile device 40 can also display the current GPS location 454 of the mobile device 40, as shown in the figure. It is conceivable that each entry point in the list 452 of available entry points can include an optional button 456 configured to transmit an unlock or lock request, as will be described in more detail herein. It is conceivable that the list 452 of available entry points can be based at least in part on the permissions assigned, including but not limited to the current time or the employment status of the user falling within one or more entry time windows assigned to the user. In some embodiments, some entry points that are unavailable to the user can be displayed. In such cases, selectable button 460 can be omitted or grayed out and unselectable.

[0057] In some cases, the notification may be a pop-up alert about an identified entry point. An identified entry point may be an entry point that is accessible to the user and within a threshold distance of mobile device 40. Fig.10 5 is a screenshot 500 of a mobile device 40 including a pop-up alert 502. In the illustrative example, the user interface of the mobile device 40 also displays a list 504 of access points available to the user and a GPS location 506 of the user's mobile device. However, this is not required.

[0058] It is contemplated that a notification or list 452 of available entry points may be automatically displayed as the user approaches an entry point, without user input. In some cases, the displayed available entry points 452 may be sorted, with the closest entry point placed at the top of the list (if more than one entry point is listed). When so provided, the user does not have to click through various menus of the application to identify a button to open a particular door. Instead, the application may automatically present the user with the appropriate button to unlock the door as the user approaches the door.

[0059] Return to Figure 8 , a selection of one of the displayed entry points may be received from a user via a user interface of a particular mobile device, as shown in block 410. For example, a user may select an "unlock" button 460 adjacent to door B 458, as shown in block 410. Fig. 9 Alternatively, the user can select Fig.10 Pop-up notification 502 is shown. This may cause the mobile device 40 to display the door that has been found. Fig.11 5 is an illustrative screenshot 510 of the mobile device 40 when the pop-up notification 502 is selected (e.g., clicked). The mobile device 40 can be configured to display a "discovered" or nearby door 512 and an optional unlock button 514. Fig.11 , the user may select unlock button 514 associated with door B. In some cases, unlock buttons 460, 514 are not selectable until mobile device 40 is within a threshold distance of the entry point to prevent unauthorized users from entering if the unlock button is selected before the user is ready to enter the entry point.

[0060] Return again Figure 8 , after selecting to unlock (e.g., selecting unlock button 460 or unlock button 514) an entry point, the mobile device may send a command for unlocking the selected entry point, as shown in box 412. The mobile device 40 may transmit a command to the cloud server 70, although this is not required. In some cases, the cloud server 70 may verify the authority of the mobile device 40 that made the unlock request. For example, the cloud server 70 may compare the mobile device identifier with a list of identifiers that are allowed to enter the selected entry point. This may also include verifying that the identifier can use the entry point at the current time. In response to the command for unlocking the selected entry point, the selected entry point may be unlocked, as shown in box 414. For example, after verifying the mobile device 40, the cloud server 70 may transmit a command to the ACS 50 to actuate a relay station associated with the selected entry point. It is conceivable that a user may use the mobile device 40 to lock an entry point that cannot be automatically fixed in a manner similar to the unlocking procedure. In some cases, the mobile device 40 may be configured to receive and display a notification or confirmation that the selected entry point has been unlocked. Fig.12 5 is an illustrative screenshot 520 of a mobile device 40 displaying a pop-up notification 522 indicating that an access point has been unlocked. It is contemplated that the ACS 50 may transmit a message to the cloud server 70 that the selected access point has been unlocked. The cloud server 70 may relay this message to the mobile device 40 where it is received and displayed to the user via a user interface.

[0061] Those skilled in the art will recognize that the present disclosure may be embodied in various forms other than the specific embodiments described and contemplated herein. Therefore, changes in form and details may be made without departing from the scope and spirit of the present disclosure as described in the appended claims.

Claims

1. A method for unlocking an access point to a facility, the method comprising: the authority and geographic location of the access points to said facility accessible to users who download the specific mobile device; receiving a current location of a specific mobile device from a location service of the specific mobile device; the particular mobile device determining, based on the current location of the particular mobile device and the downloaded geographic locations of the entry points to the facility, one or more entry points to the facility that are within a predetermined threshold distance of the particular mobile device; the specific mobile device identifying which of the one or more entry points of the facility determined to be within the predetermined threshold distance of the specific mobile device are accessible to the user of the specific mobile device based on download permissions for the entry points of the facility; displaying, on the particular mobile device, a notification of the one or more entry points identified by the particular mobile device as being within the predetermined threshold distance of the particular mobile device and accessible to the user of the particular mobile device; receiving, from the user via a user interface of the particular mobile device, a selection of one of the displayed entry points; sending a command from the particular mobile device to a cloud server, wherein in response, the cloud server sends an unlock command to the selected access point to unlock the selected access point; as well as The selected entry point is unlocked.

2. The method of claim 1, wherein prior to unlocking the selected access point, one or more access credentials of the user are verified.

3. The method of claim 2, further comprising displaying a confirmation on the particular mobile device that the selected access point has been unlocked.

4. The method of claim 1, wherein one or more of the download permissions include an employment status of the user, and wherein the one or more entry points included in the notification are based at least in part on the employment status of the user.

5. A method according to claim 1, wherein one or more of the download permissions include one or more entry time windows for at least some of the entry points to the facility, and the one or more entry points included in the notification are based at least in part on a current time falling within the one or more entry time windows.

6. A non-transitory computer-readable medium having stored thereon instructions that, when executed by a mobile device, are configured to: receiving user credentials from a user via a user interface of the mobile device to verify the identity of the user; verifying the received user credentials of the user; downloading authority for each of the one or more entry points of the facility from the remote server; downloading from the remote server the location of each of the one or more entry points to the facility; receiving a current location of the mobile device from a location service of the mobile device; determining a distance between the current location of the mobile device and the location of each of one or more entry points to the facility; determining one or more entry points to the facility that are within a threshold distance from the current location of the mobile device; Displaying one or more of the entry points of the facility on the user interface of the mobile device, wherein the one or more entry points displayed: The user may access the entry point based on one or more entry point permissions associated with the user; the entry point being within the threshold distance from the current location of the mobile device; receiving, via the user interface of the mobile device, a selection to unlock one of the displayed access points; and Sends a request to unlock the selected entry point.

7. A non-transitory computer-readable medium according to claim 6, wherein one or more of the entry point permissions include one or more entry time windows for at least some of the entry points to the facility, and wherein the one or more entry points included in the one or more displayed entry points are based at least in part on a current time falling within the one or more entry time windows.

8. The non-transitory computer readable medium of claim 6, further configured to: receiving confirmation that the selected access point has been unlocked; and A notification is displayed on the user interface of the mobile device that the selected access point has been unlocked.

9. The non-transitory computer-readable medium of claim 6, wherein the one or more entry points displayed on the user interface of the mobile device are repeatedly updated based at least in part on the current location of the mobile device.

10. The non-transitory computer-readable medium of claim 6, further comprising: identifying an error metric in the current position of the mobile device; and Wherein the threshold distance is based at least in part on the identified error metric in the current location of the mobile device.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 5.

Images