# Patent

## Title
System and method for verified admission through access controlled locations using a mobile device

## Abstract

A system and method for verifying entry credentials and activating/deactivating an access control system via use of the native capabilities of a mobile device is disclosed herein. Particularly, the system and method include an embedded local control device attached or communicative with an electronic gate or lock. The control device is communicative with a remote access control management system, which is structured to receive, track and manage access tokens that can be used to control access to a gated community or other secured location. Notifications that an access token has been generated can be communicated to the guest(s) by way of text message, short message service (SMS), email, social media, for example. Each notification may contain a unique link to a webpage employing the access token. While in the geographic vicinity of the secured location, the guest may actuate the access token and open the gate.

## Background
CLAIM OF PRIORITY/CROSS REFERENCE TO RELATED APPLICATIONS
The present application is a Continuation-In-Part patent application of previously-filed, currently-pending U.S. patent application Ser. No. 14/677,451, filed on Apr. 2, 2015, the contents of which are incorporated herein in their entirety.


FIELD OF THE INVENTION
The present invention is directed to a system and method for verifying entry credentials and activating/deactivating an access control system via use of a mobile device in order to permit ingress or egress there through. The access control system may include a gate, such as a vehicle gate positioned at an entrance/exit of a residential community, parking garage, etc. Other embodiments of the access control system may include locked doors, entryways, walkways, lobby doors, electronic door strikes, parking lots, parking garages, real estate agent access, lock box access, gym access, storage facilities, etc. Furthermore, certain embodiments of the present invention may be implemented using only the native applications or capabilities of a guest's device or smartphone, such as the native messaging services (text messages, SMS, email), native web browser, global positioning system, etc., such that additional software, application(s), or third-party program(s) need not be downloaded or installed on the guest device.
BACKGROUND OF THE INVENTION
A number of residential and commercial communities throughout the United States and Worldwide employ secure access gates, for example, at the entrance thereof. For instance, many of these communities include manned security or an electric gate to limit access or entry to the residents and their guests. Particularly, guests typically enter a gated or secured community by interacting with a security guard who confirms the guest is allowed entry, e.g., via a precompiled list of authorized guests or by contacting the resident and confirming the guest is authorized for entry. Another manner in which guests may typically enter a gated or secured community may be by using an electronic device positioned at or near the gate which can call the resident or home owner, who then signals using, for example, dual-tone multi-frequency (DTMF) signaling that the gate should open.
These approaches have some significant drawbacks. For example, in the situation with the guard, it takes time for each resident to interact with the guard, potentially increasing the wait time for the guests. In addition, the guard must confirm that the driver is the intended guest, for example, by checking identification or other documents that could potentially be forged or fictitious.
With regard to the electronic systems, when a household has multiple residents, the system oftentimes does not work or function as intended, as each resident will typically have their own mobile phone number, and there is no guarantee that the number programmed in the electronic device or “call box” is accurate, up-to-date, or will reach the intended recipient. Some systems may even require that the household include a dedicated plain old telephone service (POTS) line. Furthermore, the call boxes and electronic systems often have poor audio quality and performance rates. Additionally, the driver or guest must open his or her vehicle window to interact with the system, thereby exposing himself or herself to the outer elements, often an inconvenience during inclement weather.
Moreover, advanced cellular telephones, often referred to as smartphones, with inherent or native global positioning system (GPS) capabilities, are ubiquitous in society today. Thus, it is contemplated that smartphones may be used in the process of validating guests and providing access to guests into secured locations, such as through vehicle gates at residential communities. However, systems that may require guests and/or residents to download and install third-party or non-native applications, programs, or other software on the smartphone will likely cause the system to be less universal, more complicated in its use, and therefore, more likely to fail.
There is thus a need in the art for a system and method that can operate to manage invitations or access tokens corresponding to a guest or a guest's smartphone, for example. A website or webpage accessible by the guest's native smartphone web browser may be provided to authorize a guest to enter the community. Particularly, once an invitation is generated, an SMS or email may be communicated to the guest's smartphone with a unique link to a webpage. When the guest is within a proximate location or defined vicinity of the community (as determined by the native GPS capabilities of the smartphone), the guest can open the webpage and activate and open the gate.
Advantageously, the link or webpage may also include driving directions or a map (e.g., using Google MapsTM or Apple MapsTM), as well as resident contact information (e.g., phone number, email address, etc. relating to the resident). A remote access control management system may store a detailed log of exactly when the gate was opened and for which resident(s). The resident(s) does not have to be home or in the vicinity for the guest to activate or open the gate. Furthermore, the access token or invitation, initiated via the SMS or email, may include a time parameter or time window of validity. Certain parties or entities (e.g., maintenance crew, management, delivery services such as UPS, FedEx, USPS, maids, pool cleaning crew, lawn care crew, etc.) may be provided access tokens which can be allowed for specific times of the day, certain days, and can be revoked at any time.
Additionally, the guest may forward the invitation or notification (SMS or email) to another device, for example, if the guest's plans change. Other embodiments may only validate the access token if activated by a particular authorized smartphone, phone number, or device. In addition, at least one embodiment of the present invention may include a one-time pass, meaning that the token or invitation may only be activated a single time. The one-time pass or one-time token may still include a time parameter, although once the token is activated by the guest, it can no longer be activated again. This prevents the guest from opening the gate or lock multiple times throughout the time parameter or time window, for example, in order to let other, non-authorized vehicles or parties through the gate. Of course, other implementations may include a frequency parameter greater than one, meaning that the resident, or other party who creates the token, can specify how many times the token can be activated within the particular time parameter(s).
Other advantages include reduced man power and expense for guest entry in that guard personnel workload is significantly reduced, and guests need not open the car window and expose themselves to the outer elements to gain access to the community.
SUMMARY OF THE INVENTION
As described herein, the present invention is directed to a system and method for verifying entry credentials and activating/deactivating an access control system via use of a mobile device in order to permit ingress or egress into a gated community or locked door, for example. Certain embodiments include an embedded computer system or control device that is structured and configured to actuate an electronic gate or lock (e.g., by way of a dry contact relay). The control device is capable of utilizing a secure Internet (TCP/IP) or other network connection, such as SMS, to communicate with and receive commands from a remote access control management system, such as one or more web servers with one or more databases or other storage capabilities.
The remote access control management system of the various embodiments is structured to receive, track and manage invitations or access tokens that can be used to control access to the gated community or other secured area. Notifications that an access token has been generated can be generated and communicated to the guest(s) by way of text message, short message service (SMS), or email, for example. As described herein, the notifications may be communicated directly to the guest or guest device by the remote access control management system, or indirectly communicated to the guest or guest device, for example, by communicating the notification from the remote access control management system back to the requesting device or browser for delivery to the guest or guest device.
Each notification may contain a unique or entropic link or uniform resource locator (URL) to a webpage or website containing information related to the access token. The information may include, for example, specific time parameters within which the access token is valid, location parameters (e.g., the location of the gate or community), instructions on how to access or enter the community, contact information for the resident who initiated the invitation, etc. In addition, a map may be provided to show the location of the gate and/or the guest's current location.
When the guest is within the vicinity of the gate or community, for example, as determined by the native GPS capabilities of the smartphone, and if the time is within the specific time parameters of the access token, the guest may activate the access token to open the gate. Upon doing so, the remote access control management system will communicate an access command to the local control unit or device and log the activity. In certain embodiments, the smartphone or guest device will not communicate directly with the local control unit or computer system. Rather, the gate will only open when the remote access control management system sends an appropriate command. It should be noted, however, that the system and method may be implemented in order to allow direct communication between the guest device and the local control unit.
Furthermore, some embodiments may also generate and/or communicate a notification to the resident (or other authorized party) in order to indicate when the token is activated, for example, when the guest activates the token to open the gate and gain entry to the community. The notification may be via SMS, email, push notification, etc.
It should also be noted that certain embodiments of the present invention may be implemented using only the native applications or capabilities of a guest's device or smartphone, such as the native messaging services (text messages, SMS, email), native web browser, global positioning system, etc., such that additional software, application(s), or third-party program(s) need not be downloaded or installed on the guest device.
These and other objects, features and advantages of the present invention will become more apparent when the drawings as well as the detailed description are taken into consideration.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1A is a schematic representation of the system as disclosed in accordance with at least one embodiment of the present invention implemented in connection with an exemplary vehicle gate.
FIG. 1B is a schematic representation of the system as disclosed in accordance with another embodiment of the present invention implemented in connection with an exemplary door lock.
FIG. 2 is a block diagram of the remote access control management system and at least some of the components thereof as provided in accordance with at least one embodiment of the present invention.
FIG. 3 is a schematic diagram illustrating the system of at least one embodiment and the creation of an invitation or access token.
FIG. 4A is an exemplary schematic screenshot of the system of the present invention wherein a resident may initiate or create an invitation or access token.
FIG. 4B is a schematic representation of an access token as disclosed in accordance with at least one embodiment of the present invention.
FIG. 5 is a high level flow chart illustrating the method as disclosed in accordance with at least one embodiment of the present invention.
FIG. 6A is an exemplary illustration showing a notification received by the guest device in the form of an SMS message.
FIG. 6B is an exemplary illustration showing a notification received by the requesting device in the form of a social networking activation window.
FIG. 7A is an exemplary screenshot illustrating the display of information corresponding to an access token as disclosed in accordance with at least one embodiment of the present invention.
FIG. 7B is an exemplary screenshot illustrating the display of further information corresponding an access token as disclosed herein.
FIG. 7C is an exemplary screenshot illustrating the display of yet additional information corresponding to an access token as disclosed herein.
FIG. 8 is another high level flow chart illustrating the method as disclosed in accordance with at least one embodiment of the present invention.
FIG. 9A is a high level flow chart of yet another embodiment of the method disclosed herein.
FIG. 9B is a high level flow chart illustrating the perspective of a guest device as disclose din accordance with the method provided in FIG. 9A.



Like reference numerals refer to like parts throughout the several views of the drawings provided herein.
DETAILED DESCRIPTION OF THE INVENTION
As shown in the accompanying drawings, the present invention is directed to a system 100 and method 200 for verifying admission through an access controlled location 2, including, but in no way limited to a vehicle gate (FIG. 1A), doorway (FIG. 1B), parking lot, parking garage, real estate agent access, lock box access, gym access, storage facility, etc. Briefly, a resident or other authorized party, including, in some embodiments, a representative of the community or location, may initiate the creation of an invitation or access token for a particular guest. The access token or invitation of certain embodiments may specify a guest or guest device and other access credentials or verification parameters such as a date, time, and location. The guest may retrieve or activate the access token, prior to or upon arrival at the location, for example, via the guest device (e.g., smartphone or tablet). Upon verification of the access token, including the verification parameters (e.g., location and time), the guest may be granted access into the location.
Specifically, the various embodiments of the present invention include an access control management system, generally referenced as 20, which, as described herein, is structured and configured to receive requests for creating access tokens, generate and store access tokens, and, in some embodiments, communicate with the guest device(s) 12, requesting device(s) 40 and a gate, lock or other control device 30 for providing access to the location 2. Furthermore, in certain embodiments, the access control management system 20 may be positioned remotely from the location 2 wherein communication between the guest device 12, requesting device 40, and/or the control device 30 may be conducted via a communication network 15, including, but in no way limited to the TCP/IP, World Wide Web, Internet, Wide Area Network, cellular or telecommunication network(s) such as 3G, 4G, LTE, SMS, etc. It is contemplated, however, that in certain embodiments, the access control management system 20 may be disposed locally to the location 2, such that communication with the control device 30 or gate, lock, etc. may be provided by short range communication channels, Bluetooth, WiFi, local area networks, NFC, etc.
Further, referring to the schematic of FIG. 2, the access control management system 20 of at least one embodiment of the present invention may include a computer processor 22, data storage device 24, memory 26, one or more communication devices or hardware 28 (e.g., network device(s), web server(s), etc.) Particularly, the access control management system 20 and/or processing device of at least one embodiment of the present invention comprises one or more web servers or data servers, including software and hardware to receive requests and to communicate data, information, media, web pages, applications, commands, SMS messages, text messages, email messages, etc. via the network 15 in accordance with the present invention.
More in particular, the computer processor 22 may include, for example, any device cooperatively structured to execute or implement computer instructions, software, etc. The data storage device 24, as used herein, may include one or more internal, external or removable hard disk drives, CD/DVD, USB drives, solid state drives, virtual drives, could-based storage drives, or other types of volatile or non-volatile memory. A relational or other database may be implemented on or within the one or more storage devices 24 of the present invention, for example, in order to store and retrieve various information or data corresponding to access tokens as described herein. Further, the memory device 26, may include but is not limited to random access memory (RAM) or other like devices configured to implement the present invention in the intended manner, for example, by at least temporarily storing and assisting with the execution of one or more applications or computer programs capable of implementing the system 100 and method 200 described herein. Moreover, the communication device 28 may include a network communication hardware/software component or module structured to facilitate communication between the guest device(s) 12, control device 30, and/or a resident or other authorized device (not shown), for example, in order to receive a request to create an invitation or access token.
Referring now to FIG. 3, and as generally referenced at 40, the system 100 and/or method may be initiated, for example, when an initiating party, such as a resident, security personnel, or other authorized party requests that an invitation or access token be generated. Accordingly, the system 100 of at least one embodiment comprises a token generating module, generally referenced as 21 in FIG. 2, for receiving a request to create a guest access token and for generating the guest access token. The token generating module 21 may comprise a computer program, application, software or series of computer instructions cooperatively configured to receive information corresponding to the access token and for generating the access token, as provided herein. Certain embodiments of the token generating module 21 may also or instead include one or more hardware components, including, for example, a random number generator (RNG) device.
Particularly, in at least one embodiment, a resident or other authorized party may provide various invitation information 42 (e.g., as shown in FIG. 4A) corresponding to the particular guest access token to be generated. In certain embodiments, the initiating party may need to be pre-registered with the system 100 or method 200 of the present invention such that the party's authorization to request guest access tokens in accordance with the present invention may be verified. For example, as a resident, management personnel, security officer, etc. of a cooperating community, building, or other location 2, the party may be verified to provide or request guest access tokens. In this regard, the party may, in some implementations, need to pre-register with the system 100 or method 200 or otherwise sign up for or generate a user profile.
In order to request a guest access token or invitation, in at least one embodiment of the present invention, the initiating or requesting party may visit a webpage, for example, via a web browser on a computer, laptop, smartphone, mobile device, tablet, or other requesting device 40. Other embodiments may include an application, software or other program, whether installed on the party's device (e.g., computer, laptop, smartphone, mobile device, tablet, etc.) or accessible thereby, which may be used to submit a request to generate an access token.
FIG. 4A represents an exemplary schematic of a webpage, application or other request form which the resident or other authorized party may access, for example, via a requesting device, in order to submit a request for generating an access token. For instance, the invitation information 42 that can be submitted as part of the request may include, but is not limited to, the guest's name or identification information, a phone number or mobile directory number (MDN) corresponding to the guest's phone or device, an email address associated with the guest, etc. For instance, the phone number, MDN, etc. may be used as an SMS identifier in that the notification or access token presented herein may be communicated to the guest via the SMS identifier, such as the phone number or MDN.
Still referring to FIG. 4A, the invitation information 42 may further include a time element or parameter 43, a location element or parameter 44, and/or a method or mode of delivering the access token to the guest 45. For instance, the time element 43 may be defined by one or more of an arrival time, a departure time, and/or a range or time window. Specifically, as described herein, the access tokens as provided in accordance with certain embodiments of the present invention include a time parameter wherein the access token is only active during the particular or defined time parameter. The time parameter may be defined by the time element 43 specified by the requesting party, for example, the arrival time, departure time, or range or time window. Other embodiments may define the time parameter of the access token as comprising a range or buffer (e.g., three (3), five (5), ten (10), etc.) minutes before and/or after the specified time element. As an example, the requesting party may identify an arrival time as ten o'clock (10:00). While some embodiments may define the time parameter of the access token in this example as ten o'clock (10:00), other embodiments may define the time parameter with a buffer allowing the access token to be active between 9:57 and 10:03, or between 9:55 and 10:05, for example.
Moreover, the location element 44 may be used to define the location parameter of the access token. In some embodiments, the location elements 44 and/or parameter may be predefined, for example, based upon the resident's or requesting party's profile. As an example, the requesting party may only have privileges to request an access token for a particular location, including, for example, the particular community in which the party belongs or lives. Accordingly, the location parameter may be predefined or preset based upon the requesting party's profile or access privileges. Other embodiments may allow the resident or requesting party to define the location element, for example, a particular vehicle gate, doorway, parking garage, etc. This may be particularly true when a single residential community has multiple vehicle gates, or when a single resident or profile has access privileges to multiple communities.
As shown at 45, certain embodiments may also allow the requesting or initiating party to specify the mode of delivering the access token or the mode of delivering a notification to the guest or visitor that an access token is available for viewing, retrieval or activation. While short message service (SMS), email and social media (e.g., Facebook, Twitter, Instagram, etc.) are shown as exemplary methods or modes of delivery at 45 in FIG. 4A, other modes of delivery may be contemplated within the full spirit and scope of the present invention.
Upon submitting a request to create an access token, the access control management system 20 will receive the request, for example, via the network 15, as shown at 202 in the method 200 of FIG. 5. Accordingly, as shown at 204, the token generating module 21 of at least one embodiment of the present invention will generate an access token based at least in part upon the invitation information 42 contained in or as part of the request. Particularly, in at least one embodiment, the access token comprises a collection of information corresponding to the invention, such as a location parameter and a time parameter corresponding to the location element and time element of the request, as provided herein. For instance, the access token 60 (e.g., as shown in FIGS. 7A through 7C), as used herein, comprises a compilation or set of information, data, and parameters, e.g., guest information 62 (guest name, invitation ID, device key, device key setting or flag, etc.), invitation information 63 (e.g., purpose of invitation, location parameter 64, time parameter 65, etc.) as well as a guest ID 66 and entropic password 67, URL), which, when verified by the system or method, can be used to gain access to the secure location. As provided herein, the access token may be stored in a database or other storage device and provided to the guest, for example, in the form of a dynamically generated HTML document. Particularly, FIG. 4B illustrates an exemplary schematic representation of the relational data tables that may be included as part of the access token 60 of at least one embodiment of the present invention.
Furthermore, generating the access token, as shown at block 204, in certain embodiments may also include generating a unique notification value or uniform resource locator (URL) 68 and associating the notification value or URL 68 with the access token 60 or saving the URL, portions of the URL and/or a decoded version of the URL, for instance, as part of the access token 60. For example, the notification value or URL 68 may be generated with random characters or with a certain amount or level of entropy such that the URL 68 cannot be easily guessed, replicated or reproduced. Systems and methods that are used to automate passwords, for example, may be used to generate at least a portion of the entropic or unique URL 68 of at least one embodiment. The access token 60 information, e.g., the location parameter, time parameter, and portions of the entropic or unique URL 68 may be stored in a database, as shown at 206, for subsequent retrieval and activation.
Particularly, in at least one embodiment of the present invention, the notification value 68 or entropic URL (e.g., the text of the URL itself) may be used to identify a guest and a password, or unique/entropic code, associated with that particular guest. For instance, the access information corresponding to a particular guest may be stored in a relational (or other) database and identified by a primary key. Along with certain access information (e.g., location parameter, time parameter, guest information, or resident information), a string or entry of random or entropic values 67 is also generated and stored. In this regard, in at least one embodiment, the notification value or entropic URL 68 may be generated by concatenating, intermixing, or otherwise combining the primary key (e.g., guest ID 66) associated with a guest and the entropic string or values (i.e. password 67). In order to provide further security or a greater perception of an entropic or random URL 68, a transposition on the buffer may also be executed.
For instance, an exemplary notification value or entropic URL 68 of at least one embodiment of the present invention may look like this: “https://open. gate/v?ZK9FyliaLoas1ltLg9ULdGgqfjhFBlae”. The “ZK9FyliaLoas1ltLg9ULdGgqfjhFBlae” portion of the exemplary URL includes the concatenated, intermixed or other combination of the primary key (guest ID 66) associated with the particular guest and the “password” (i.e., the entropic string or value 67 saved within the relational database and corresponding to the primary key entry.)
Thus, when the guest clicks on or activates the notification value, link or URL 68, the system and method of the present invention may be structured to decode or convert the entropic portion of the URL 68 into the guest ID 66 or primary key and the password/entropic value 67 or random values stored in the database along with the guest information and primary key. If the password or entropic value from the decoded URL or notification value matches the entropic value or password 67 that is saved in the database, then the system and method validates the URL 68 and the guest. Similarly, if the decoded entropic value from the URL 68 does not match the entropic value or password 67 corresponding to the decoded guest ID, then it is determined that the URL or notification value is not valid.
It should also be noted that the system 100 and method 200 of at least one embodiment may further generate a notification 50 (e.g., as shown in FIGS. 6A and 6B) corresponding to the guest access token wherein the notification 50 may contain the notification value or entropic/unique URL 68. In certain embodiments, as shown at 208 in FIG. 5, for example, the notification 50 may be communicated directly to the guest or guest device 12 from the management system 20, allowing the guest to selectively retrieve or otherwise view the access token 60, for example, by activating or clicking on the a link 52 corresponding to the notification value or URL 68.
For example, as shown in the exemplary schematic of FIG. 6A, the notification 50 (including the link 52 corresponding to the notification value or URL) may be communicated to the guest device via text message, short messaging service (SMS) or a specified third-party social media network (e.g., Facebook, Twitter, Instagram). This allows the guest device 12 to use the native capabilities, e.g., the native text messaging or SMS capabilities of a smartphone or tablet, to receive the notification 50. Other embodiments may include communicating the notification 50 via email, which may also allow the guest device 12 to utilize the native communication capabilities, e.g., email capabilities, of the smartphone, tablet, etc. to view the notification. Advantageously, this means that no additional software, program or application is needed, beyond the native and common text message, SMS or email capabilities of the smartphone, tablet or other guest device 12 in order to view the notification 50 identifying the access token has been generated. It should also be noted that in certain embodiments, information corresponding to the access token 60 may be communicated to the guest device 12, for example, via text message, SMS or email, instead of the notification 50 or link to the token 60 as just described.
As shown via reference character 209 and 211 in FIG. 5, in other embodiments, the notification 50 may be indirectly communicated to the guest or guest device by first communicating the notification 50 back to the requesting device 40 or the web browser or application used by the requesting device 40 to request the invitation. For example, once the management system 20 of the present invention creates the unique notification 50 corresponding to the particular guest access token, the notification 50 may be communicated back to the requesting device 40 for immediate or subsequent delivery to the guest or guest device.
In one example, the system and/or method 200 of the present invention may be configured to utilize the communication capabilities and/or network connectivity of the requesting device 40 in order to indirectly communicate the notification 50 to the guest or guest device. Specifically, once generated, the notification 50 may be sent or communicated back to the requesting device 40 for communication from the requesting device to the guest device via SMS, email, social media, etc. With regard to the SMS communication, the SMS capabilities of the requesting device 40 may be utilized to communicate the notification 50 to the guest or guest device. This indirect communication may be conducted automatically, e.g., without further input or action by the requesting user, or by first sending an SMS confirmation or authorization to the requesting device, and upon receipt of authorization, the SMS capabilities of the requesting device may be used to send the notification 50 to the guest or guest device.
Similarly, with regard to email communication, the system 100 and/or method 200 of the present invention may utilize the network or email capabilities of the requesting device 40 in order to indirectly communicate the notification 50 to the guest or guest device.
In another embodiment, the system 100 and/or method 200 of the present invention may be structured to generate and/or display a social networking or third-party activation window at the requesting device for facilitating communication of the notification 50 to the guest or guest device. For example, after generating the notification 50 or guest access token, the management system 20 may send the notification 50 (e.g, the entropic URL, notification value or other information) back to the requesting device 40 or the web browser or application used by the requesting device to request the invitation or guest access token. As shown, for example, in FIG. 6B, on the requesting device 40 a social networking activation window 55 may be generated and displayed on the requesting device 40. For instance, the social networking activation window 55 may be generated via JavaScript or other code or program on the web browser, application or requesting device 40. In the example shown, the notification 50 is automatically embedded as part of a social networking post, communication or message, which the requesting user (e.g., the resident) can send to the guest or guest device. The third-party social media networks as described herein may include, for example, but are certainly not limited to Facebook, Twitter, Instagram, etc.
In addition, certain embodiments of the present invention may generate a machine readable code, such as a quick response (QR) code, bar code, etc. with the notification 50 or unique URL embedded therein. The machine readable code may then be communicated directly or indirectly to the guest or guest device. For instance, the management system 20 of the present invention may communicate the code directly to the guest device 12, either via SMS, email, or other mode. Other embodiments, may facilitate indirect communication of the machine readable code to the guest device in that the machine readable code may be first communicated to the requesting device or user, who may then deliver the machine readable code or notification 50 to the guest or guest device, in any manner desired or selected. For instance, the resident or requesting user may print the QR code and include the QR code in a card or other letter, mailing, etc. delivered to one or more guests. The QR code may also be emailed, texted, sent via SMS, social media, etc. Upon receipt of the QR code or other machine readable code, the guest may scan the code, for example, via a phone or other guest device, in order to retrieve the details of the guest access token. For instance, in one embodiment, the unique or entropic URL may be embedded within the QR code, which when scanned or activated, will automatically direct the guest device to the guest access token, for example, via an application or web browser.
Still referring to the example illustrated in FIGS. 6A-B and 7A-C, and the flow chart of the method 200 illustrated in FIG. 8, when the guest wants to view or retrieve the details corresponding to the access token 60, he or she may click on, select or otherwise activate the URL 68, embedded link 52 or QR code, for instance, as contained in the notification 50 (e.g., SMS message), and as shown at step 212. Upon doing so, in at least one embodiment, dynamically generated content displaying information corresponding to the access token 60, for example, in the form of HTML or other web-based content, is generated and presented to the guest via the guest device 12. For instance, upon activation of the URL 68 or unique link 52, the access control management system 20 may retrieve the corresponding access token 60 from a database or other storage medium, for example, as described above via the primary key and password, and dynamically display information corresponding to the access token 60 via HTML or other web-based content. For example, using the primary key (or unique guest ID 66) and password 67 (entropic value saved with the guest ID), the system and method can query the database or otherwise obtain the guest access information 62 relative to the particular access token, such as what community the guest is visiting, which resident invited the guest, as well as invitation information 63 such as the location 64 and time 65 parameters, etc.
In this manner, the guest may view information corresponding to the access token 60 via the native capabilities of the guest device 12, for example, via a native or other web browser. Similar to viewing the notification 50, viewing the access token 60 of at least one embodiment does not require the use of or installation of additional, proprietary or third-party software, programs or applications. Rather, the guest may use the native or basic communication capabilities (e.g., text messaging or SMS capabilities, web browsing capabilities, etc.) of the device 12.
Particularly, for illustrative purposes only, FIGS. 7A, 7B and 7C show an exemplary embodiment displaying information corresponding to an access token 60 as disclosed in accordance with at least one embodiment of the present invention. For instance, as provided herein, information corresponding to the access token 60 may be presented to the guest or guest device via a web browser, although other methods of display are contemplated in certain embodiments. In particular, referring to the example shown in FIG. 7A, the access token 60 may include invitation details 63, such as the name of the resident and an occasion or purpose for the access token 60. In the example shown, John Smith is the name of the resident and the purpose of the access token 60 is to celebrate John's birthday, although, of course, other residents and virtually any occasion can be specified. Still referring to FIG. 7A, the invitation or access token 60 details may further include the time parameter 65, which specifies the time constraints relative to the access token 60, or otherwise, the time frame in which the access token 60 is valid.
If the access token information is provided on different or multiple web pages or displays, for example, as shown in FIGS. 7A through 7C, a navigation link 61 may be provided in order to allow the guest to navigate through the different portions or information relative to the access token 60. For instance, the guest may navigate between the invitation details, entry details and resident information via the navigation link 61. Other embodiments, however, may include all of the access token 60 information on a single webpage/display or different webpages/displays.
Referring now to FIG. 7B, exemplary entry details are shown. For instance, as provided herein, when the guest device is within the vicinity of the location parameter 64, such as via a predetermined algorithm, proximity function, or validation module, as provided herein, the guest may activate the button(s) and open the gate or unlock the door. Certain embodiments may provide multiple buttons 70, 70′, 70′′, one for a different location, gate, or entry point. As an example, an unavailable entry point may be defined as a gate or access location that is not included in the group of valid entry points associated with the particular access token 60. Unavailable entry points may be identified as unavailable, as shown as 70′, or left out all together in other embodiments. Other buttons 70′′ may indicate “out of range” or other equivalent to identify that the guest device is not close enough to the location parameter to activate the button 70′′. When the access device arrives within the vicinity, certain embodiments will automatically activate the button 70′′, for use by the guest, for example, as illustrated with reference to 70.
FIG. 7C illustrates further information associated with the invitation or access token 60, including, for example, the location parameter 64, such as, in the form of an address or a map. The map may be powered or provided by Google MapsTM, Apple MapsTM, or other external map API or service. Accordingly, the map of certain embodiments may not only show the destination location (or location parameter), but it may also identify the current location of the guest device. Resident information 69, such as the resident's email address and phone number may also be provided on the access token 60. In certain embodiments, the resident information 69 may be clicked on or activated in order to trigger native capabilities of the guest device (e.g., phone application to call the resident or email application to email the resident).
Referring back to FIGS. 6A and 6B, activation of the notification value, URL 68 or other link 52 may, in certain embodiments, trigger one or more verification modules or authentication steps. Particularly, in at least one embodiment, the system 100 and/or method 200 of the present invention may determine whether the access token 60 is valid, as shown at 213 in FIG. 8. For instance, the resident may have previously revoked the invitation or access token, or management or residential/building security may have declined the request to create the access token. Also, if an error occurred during the request, the access token 60 may be invalid. If, for whatever reason, the access token 60 is invalid, the method 200 will deny access to the secure location 2.
Other embodiments may also verify or determine whether the gate, lock or other device at the location 2 is operational, or determine whether the local control device 30 is operational, as shown at 215. If not, then the system 100 and/or method 200 may decline access or inform the guest to seek alternative forms of entry.
In any event, the system 100 includes one or more validation modules 23 structured to validate the time and/or location parameters associated with the access token, as generally illustrated in step 217 of FIG. 8. For instance, the time parameter may be validated or verified by analyzing or comparing the current time (as provided by the guest device 12 or as maintained by or for the access control management system 20, for example) with the time parameter associated with the access token 60. Specifically, as provided herein, in at least one embodiment, the access token 60 may only be valid during the particular time period defined by the associated time parameter. If the time parameter is not valid, for example, if the current time is outside of the time parameter associated with the access token, e.g., prior to or after the time parameter, then access will not be granted. The validation or verification of the time parameter in at least one embodiment may occur by a validation module 23 executed by or on the remote access control management system 20. This can minimize the potential for fraudulent or faked times that may be provided on the guest device. In order to maintain a level of security, the time indicated on the guest device 12 is not considered in some embodiments. Other, perhaps less secure embodiments may validate the time parameter on the device 12, itself, for example, via HTML, Java, JavaScript, C, C++ or other web-based code.
Furthermore, the various embodiments of the present invention include a validation module that is structured to determine or validate the current location of the guest or guest device 12 as compared to the location parameter of the access token 60. For example, in one embodiment, the location parameter validation module may be activated upon the guest clicking on or otherwise following the entropic or unique URL 68 or link 52 in the notification. As an example, doing so will not only display the access token 60 to the guest, such as via the native web browser and as shown in FIGS. 7A, 7B and 7C, but the method 200 of one embodiment will activate the native global positioning system (GPS) capabilities of the guest device 12 and, using the location parameter validation module, the system 100 and/or method 200 will determine the device's 12 proximity to the location 2.
For exemplary purposes only, in at least one embodiment, the location parameter validation module may be in the form of HTML and/or other code that is activated and processed on the device 12 itself upon selection of the URL 68. This maintains the location information of the device 12 on the device 12, meaning that the location information may not be communicated away from the device 12 in order for the system 100 and method 200 to determine whether the device is proximate the location 2. For instance, as provided below, the location parameter validation module of at least one embodiment may include or otherwise utilize the Haversine formula, as exemplified in the following code:















function toRad(d) {




  return d * Math.PI / 180; 




 }




 var EARTH_RADIUS = 6371009; // Meters. 




 function distance(coords, lat, lon) {




  var d_at = toRad(coords.latitude − lat), 




    d_lon = toRad(coords.longitude − ion), 




    x = 0.5 − Math.cos(d_lat) / 2.0, 




    y = Math.cos(toRad(lat)) * 




     Math.cos(toRad(coords.latitude)), 




    z = (1 − Math.cos(d_lon)) / 2.0, 




    a = x + y * z; 




   return (EARTH_RADIUS + coords.altitude) * 




2.0 * Math.asin(Math.sqrt(a)); 




 }









It should be noted, however, that other implementations of the location parameter validation module, whether processed on the device 12 or remotely, for example, by the remote access control management system 20, are contemplated within the full spirit and scope of the present invention. In any event, the location parameter of the various embodiments is validated or verified when it is determined by the system 100 and method 200 that the device 12 is within a predetermined proximity of the location 2.
In some embodiments, the location parameter validation module may validate the location of the guest or guest device 12 without the use of the GPS. For example, this may be particularly useful in the event the guest does not want to grant permission for the GPS location to be shared or accessed by the system 100 or method 200 of the present invention. Additionally, validating the location of the guest device 12 without GPS may be useful in areas with poor or limited network (e.g., 3G, 4G, LTE, or WiFi) connectivity or otherwise in areas with poor or limited GPS functionality, such as, for example, an underground parking garage or remote locations.
Particularly, in one embodiment, a display device, e.g., a monitor, LED display, 4 digit 7 segment LED display, etc. (not shown) may be disposed locally at the location 2 and communicative with the local control device 30 (e.g., via a direct connect HDMI or other connection) and/or the remote access control management system 20. For instance, the system 100 or method 200 may display a validation code locally on the display device, e.g., when prompted or randomly. The validation code may include a series of numbers, letters, characters, codes, pictures, graphics, etc. that can be used to validate the location of the guest or guest device 12.
More in particular, in order to prove his or her presence at the gate or location 2, the guest may view the validation code on the local display device, and input the validation code into a designated location on a web browser, guest web page, on the guest access token, or in an application, for example. The input will be communicated to and received by the remote access control management system 20 for comparing the input to the validation code displayed on the local display device. If the input matches the validation code, then the system 100 or method 200 of at least one embodiment may validate the location parameter of the guest access token without access the GPS location of the guest device 12.
In yet another embodiment, the system 100 and/or method 200 of the present invention may require that the guest originate his or her travels to the location 2 from a particular location, for example, in order to suggest or prove the identity of the guest. As an example, in one embodiment, the system 100 or method 200 may include a designated origination or check point(s), e.g., the guest's home or workplace, from which the guest must check into before beginning to travel to the location 2. If the guest checks into a different location or fails to check in, the system 100 or method 200 may deny access upon arrival to the location 2 under the premise that the user requesting access may not be the correct guest.
In any event, if the location parameter and the time parameter are validated or verified, then the system 100 and method 200 of at least one embodiment will grant access to the location 2. For instance, referring to the exemplary illustration displaying information corresponding to the access token 60 provided in FIGS. 7A, 7B and 7C, and step 218 of FIG. 8, when the location parameter and the time parameter are validated or verified, then an “Open Gate,” “Unlock Door” or other activation button, as generally referenced at 70 is presented, made visible, or able to be activated. Specifically, if the device 12 is proximate to the location 2, and the current time is within the time parameter of the access token 60, then at least one embodiment will present the activation button 70 to the guest. Some embodiments may always show the activation button 70, regardless of the time or location of the device 12, although activation will not be valid unless and until the location and time parameters are validated or verified.
Upon activation, for example, as shown at step 220 when the guest activates or clicks upon the activation button 70, a message is communicated from the device 12 to the remote access control management system 20 identifying the unique access token 60 and the desire to open the corresponding gate or unlock the corresponding door. Some embodiments will perform a check to determine that the access token 60 is valid (step 219) and that the gate or lock is operational (step 221). For instance, in certain embodiments, the remote access management system 20 may store or maintain records corresponding to each gate or lock, and the current status of each gate and/or lock in order to inform the guest when or if the gate/lock is inoperable or out of services.
In any event, upon activation of the button 70, and after performance of any intervening validation steps, the remote access control management system 20 is structured to communicate an access command to the local control device 30, for example, via network 15, as shown at step 222 in FIG. 8. Particularly, the local control device comprises a computer-based device interconnected or communicatively disposed relative to the gate or operational components of the gate, for example, an access control mechanism 3 (e.g., as shown in FIG. 1A) corresponding to the gate or lock. As an example, the access control mechanism 3 (e.g., as shown in FIG. 1A) may include necessary mechanical and/or electronic components that operate to open/close the gate (e.g., by pivoting the gate upward/downward or moving the gate along tracks) or to lock/unlock a door. Upon receipt of the access command from the remote access control management system 20, the control device 30 will operate to open the gate, unlock the door, etc.
For instance, many electronic or vehicle gates as well as electronic door strikes operate via leads that, when connected, will open the gate or unlock the door for example. The local control device 30 of at least one embodiment of the present invention may be configured to drive a relay or other mechanism that controls the lead(s) and actuates the gate. Of course, other gate structures are contemplated, for example, digital control mechanisms that may control the gate. In such a case, the control device 30 of the present invention may be an external or separate device that is configured to control the digital or other control mechanism that operate the function of the gate or door, such as opening, closing, locking, unlocking, etc.
In any event, the control device 30 may be triggered or activated by a command, for example, from the access control management system 20, via an SMS message or a secured TCP/IP communication channel, including, but not limited to a secure, persistent channel or socket, etc. Thus, the control device 30 may include an Ethernet, WiFi or cellular interface for communicating with the access control management system 20. In any case, it is important in some embodiments that the access control management system 20 know whether the local control device 30 is available or unavailable on the network or communication channel. This can be accomplished via a “heartbeat” message, ping message and/or a periodic message communicated from the control device 30 to the access control management system 20 notifying the access control management system 20 that the control unit is connected and operational, or otherwise identifying the operation status of the control device 30. Thus, if a heartbeat or ping message is not received, the access control management system 20 may conclude that the control unit is unavailable, for instance, in the event of a network or hardware failure.
Furthermore, because security is important in the various embodiments of the present invention (i.e., whether SMS, TCP/IP or other communication channel is implemented between the local control device 30 and the access control management system 20), the local control device 30 may be implemented to only respond to authorized commands. For instance, in the case of implementing a TCP/IP communication channel between the local control device 30 and the access control management system 20, SSL or SSL/TLS (secure sockets layer/transport layer security) with cryptographic authentication of the messages may be appropriate.
If SMS is used as the communication channel, validating the mobile originated (MO) device and providing an embedded “key” in the message may be appropriate. However, if the control device is triggered or at least partially controlled via SMS, then it may be desirable to prevent or minimize the ability for an intruder to learn the contents of the SMS and issuing it to the control device in order to unintentionally or maliciously open the gate. For instance, one approach may be to require the contents of the trigger SMS message to be dynamic. As an example, the control device and the server or management system may communicate a shared secret, code or string of characters. The secret or code may be passed through via a one-way hash function, as an example, with some changing value—e.g., the current time, current hour, current minute, date, etc. For instance, even without a TCP/IP connection, the control device may be able to obtain an accurate time stamp (e.g., via a cellular or other network). It can then compute the hash or algorithm for the shared code and validate the contents of the triggering SMS if it matches the locally computed value. This will make the contents of the triggering SMS message dynamic or not constant, thereby making it harder to forge. Particularly, a potential attacker must forge their originating number as well know the shared secret or code which is never transmitted via an communication mechanism.
Moreover, the control device 30 of at least one embodiment may be functioning as a server with the function of receiving commands from the access control management system 20 and opening the gate or unlocking the door, for instance, when directed to do so. In the case of a TCP/IP communication channel between the control device 30 and the access control management system 20, the control device 30 may be assigned a static IP address such that its network address or location on the network(s) is known to the access control management system 20. However, as this approach may be undesirable in many cases, the control device 30 may be configured to continually, persistently or periodically communicate an outbound connection or signal to the access control management system 20 (rather than receive an inbound connection). In such a case, the local control device 30 need not be assigned a static IP address in order to consistently communicate with the access control management system 20 and in order for the access control management system to know the network address or location of the local control device 20. The access control management system 20 can, therefore, store or park the connection received by the control device 30, allowing the access control management system 20 to use that established connection (provided from the control device 30) when necessary, for example, when the access control management system 20 is ready to send a command. The access control management system 20 may, in some implementations, include a static IP address, such that the local control device(s) 30 can always locate it on the network 15 and send the connection signal. Thus, the control device 30 and the access control management system 20 may communicate on the secure, persistent channel established or initiated via the local control device 30.
Furthermore, as mentioned herein, to detect a communications failure, network failure or hardware failure, the control device 30 may periodically attempt to send a heartbeat or ping message to the access control management system 20 in order to test the integrity of the connection. In certain embodiments, the heartbeat or ping message may include status information relative to the control device 30 (e.g., CPU or other temperature measurements and hardware health).
If the control device 30 does not receive or detect a response to the ping message, then it will continually attempt to connect to the access control management system 20. Because the access control management system 20 may include redundancy, this should only result in a short outage as the control device 30 attempts to reconnect.
The advantage to this is the ability for the system and method to operate on low bandwidth and without the need for a static IP at the control device 30, as well. Other firewall/NAT issues are overcome, as well.
This allows the access control management system 20 to keep track of, or otherwise maintain a steady and up-to-date status of the control device(s) 30, including temperature information and hardware health, for example, simply by receiving the ping message. If the connection is severed, or if the status of the control device 30 is poor, then the access control management system 20 can convey this information to the guest so that alternative means for entry may be sought. Additionally, in at least one embodiment, when the guest clicks on the URL to retrieve the access token, the access control management system 20 may already know the status of each of the control device(s) corresponding to the access token 60. Particularly, querying the status of the control device 30 does not need to be done at the time of activating the URL (which may result in a waste of bandwidth). Rather, the access control management system 20 of at least one embodiment is internally aware of the status of the control device(s) 30. This allows the access control management system 20 to mark certain gates or entry points as available or unavailable.
Furthermore, a single access control management system 20 or a single (set of) server(s) or computer(s), can service a plurality of gates or control devices 30 for a number of different communities. Particularly, rather than having a separate server or set of servers for each community, the present invention may be implemented with a common set of servers to manage a plurality of communities. In this manner, the access control management system 20 must have an understanding as to what guests are allowed access to what gates, which residents can invite guests through which gates, and the corresponding security barriers. For instance, a resident of community A should not be able to invite a guest into community B without being a resident of community B.
Moreover, the access token or webpage that displays the access token to the guest(s) may be customized for each community, for example. As provided above, the webpage or HTML content may be dynamically generated upon activation of the corresponding URL. Retrieving the information corresponding to the access token (e.g., guest information, location parameter, time parameter, resident information) may also include retrieval of customized community information relative to the look and feel of the webpage. The community information may thus include selected colors, names, logos, a particular layout, etc. This allows each community to customize the access tokens and web interface with their colors and logos, for example, despite sharing a server or set of servers with hundreds or even thousands of other communities.
In addition, certain control parameters, including, for example, a relay closure time parameter, may be stored on or by the remote access control management system 20 or otherwise provided by the remote access control management system 20 to the local control device 30. Particularly, oftentimes, various control parameters, such a relay closure time, are required to effectively operate the controlled opening and closing of the gate, and may vary depending on a particular gate or lock configuration. Accordingly, rather than storing certain control parameters locally on the control device 30, they may be stored on the access control management system 20 and communicated to the control device 30, for example, with the activation command. Specifically, with regard to the relay closure time, this allows the length of time in which the gate/door remains open or unlocked to be controlled by the remote access control management system 20. It also allows the system 100 and method 200 of the various embodiments to be implemented in a number of different applications, such as vehicle gates, vehicle garage gates, electronic door strikes, lobby doors, etc. Furthermore, the control device 30 does not need to be reconfigured if it is damaged, for example, and universal control devices 30 may be used to control vastly different gates, lock, etc. In addition, the control parameters can be changed remotely at any time, without requiring on-site servicing of the control device 30. Maintaining the control parameters on the access control management system 20 also allows the parameters to be easily backed-up—a failure in storage device, either by the control device 30 or the access control management system 20, therefore, does not mean all of the control parameters are lost.
In other embodiments, it may be desirable to keep the “open” or activation command that is sent from the remote access control management system 20 to the control device 30 as short or minimal as possible. Thus, in certain embodiments, the “open” or activation command may only hold or contain the gate number or other identifying or command signals. Other parameters (e.g., relay timing parameters) may be previously communicated to the control device 30, for example, when the secure connection between the remote access control management system 20 and the control device 30 is established (e.g., after the SSL/TLS socket is opened and a certificate, such as an X.509 certificate that identifies the control device is validated). The control device 30 can then receive these parameters (e.g., relay timing parameters) upon establishing a secure connection with the management system and store them locally for subsequent use, such as, when the “open” or activation commend is sent.
Further advantages of at least one embodiment of the present invention includes a hierarchically implemented database structure in which a group of guests can be managed by the resident as a single unit, which can be useful for parties, group gatherings, for instance. As an example, the database hierarchy of at least one embodiment may be implemented by defining a “community” that contains one or more “residents,” a “resident” owns zero or more invitations” or tokens, an “invitation” contains one or more “guests,” and a “guest” contains zero or more “records.” Thus, a single “community” may be defined as including a plurality of residents, each of which can manage invitations for guests. A single invitation may be assigned to a plurality of different guests. This is what allows the resident to easily define or manage group invitations. For instance, each defined guest may activate the invitation or access token during the defined time parameter and within the defined location parameter. The resident may thus define a single time and location parameter which may apply to a plurality of different guests.
It should be noted that while the system 100 and method 200 of the exemplary embodiments provided herein are at least partially implemented or accessed via native capabilities of a guest device (e.g., smartphone or tablet), certain embodiments may be implemented using a downloaded application structured and designed to operate the various steps and functionality of the present invention.
Further advantages of certain embodiments of the present invention include limiting access to a particular access token, and consequently, to the access controlled locations, to one or more associated devices (e.g., a guest's cellphone, tablet, computer, etc.) Particularly, in some embodiments, the requesting user may want to limit access to the location 2 to one or more people or guests, and prevent or minimize the guest(s) from sending the notification or invitation to another (unauthorized) individual. For instance, when the requesting user creates the invitation or otherwise provides information or instructions to the system/method of the present invention to generate an access token, for example, at 202, the requesting user may decide to also instruct the system/method to restrict the access token to one or more devices. This can be done, for example, via checking a box, entering a number of devices (e.g., 1, 2, 3, etc.) that can have access to the access token into the request form, or other manners.
Accordingly, in at least one embodiment, the method 300 may further include generating a unique device key that can be associated with one or more devices (e.g., a guest device), as shown at 302 in FIG. 9A. Specifically, as described herein, in certain embodiments, the device key must be validated by the system and method prior to allowing access to the location 2. For example, in one embodiment, the device key will be known to the system or method of the present invention and the one or more limited authorized or associated devices that are allowed to access the access token and enter the location or premises.
More in particular, in one embodiment, the device key may be generated by the system in a manner that provides or creates random or entropic characters that are not easily duplicated and are not common or known. Thus, the device key can be a block of characters (e.g., numbers, letters, symbols, etc.) that are unique to a particular access token 60. The device key, once generated, can then be associated with the access token 60, for example, by corresponding the device key with the particular access token 60 in a relational (or other) database, as shown in FIG. 4B, for example. The device key may also be incorporated into the access token 60, or otherwise be part of the block of database entries, data or information that define a particular access token 60, such as a guest ID 66, password 67, access time parameter 65, access location parameter 64, for example.
Referring to FIG. 9A, when the system or method 300 receives a request to access the access token 304 (e.g., a guest or other user clicks on or activates the notification), then the method may determine whether the access token is associated with a device key or otherwise requires a device key, as illustrated at 306. If there is not a device key associated with the access token 60, then the method will proceed as described above, by validating the access token (e.g., by validating the guest ID, password, time parameter, location parameter, etc.), as shown at 308. However, if there is a device key associated with the access token 60, then the system or method 300 will determine whether a device (e.g., a guest device) is associated with the access token 60 or whether the access token 60 must now be associated with the device 12 that is sending the request to access the access token 60.
In order to do so, in one embodiment, the method 300 may include a setting, entry or “flag” associated with the access token 60 to identify whether the access token 60 is configured to allow creating an association with a device 12. For instance, in one implementation, the access token 60 that includes a device key will be associated with the first device that requests access to the access token 60. Thus, the first device 12 will be locked as the only device that can subsequently access the access token 60, and consequently, have authorized entry to the location 2. In other embodiments, there may be more than one device associated with a single access token such that the first two, three, or more devices will be associated with the access token.
In any event, still referring to FIG. 9A, the method includes determining whether the access token should be associated with the guest device or other device that submitted the request to access the access token, as shown at 310. As above, this can be implemented with a setting, flag, etc. If the access token 60 is configured to allow creating an association with a device 12 (e.g., this is the first time the access token 60 is being accessed or retrieved), then the system or method 300 of one embodiment will return or communicate only the device key to the device 12, as shown at 312. Particularly, the other parameters or information associated with the access token 60 will not be communicated to the device 12. In this manner, the device 12 (e.g., the guest device) can then be configured to store the device key (e.g., directly on the device itself, or remotely for later access). In this regard, as will be described, the guest device 12 can then later present the device key to the server or system of the present invention for subsequent validation of the device key and for subsequent access to the access token 60. As just an example, in the case where an embodiment of the present invention is implemented in HTML and/or JavaScript, the window.localSotrage mechanism can be used to store the device key locally on the guest device 12 itself.
Once the device key is communicated and stored on the guest device 12, the access token 60 may be locked, as shown at 314, i.e., the flag or other setting may be set to identify that the corresponding access token 60 is now associated with a device 12. This will also identify that the access token 60 is not configured to allow creating an association with another device, meaning, subsequent requests to access the access token 60 can only be validated by the associated device 12 that has the device key.
Specifically, for subsequent requests to access the access token 60, the server or system of the present invention will receive the device key from the guest device 12, as shown at 316, for validation thereof. In particular, when the guest communicates the request to access the access token 60, the device 12 will send the device key to the server or system, which can then be compared to the device key stored in association with the access token 60, as shown at 318. If the device key is validated, the remaining aspects of the access token 60 can also be validated, as shown at 308, otherwise an error may be communicated to the device 12, for example, indicating that the access token 60 is locked and the particular device does not have access (i.e., it either does not have a device key stored or it has an incorrect device key).
To further exemplify this embodiment, FIG. 9B illustrates the method 300 from the perspective of the guest device. In particular, as shown at 301 and 303, when the guest activates the notification, or otherwise requests access to the access token, the method 300 may determine whether the guest device has a device key stored thereon for the particular access token. If there is a device key stored, that means that the guest device has already been associated with an access token, and, as shown at 305, the guest device will then communicate the device key to the server, along with the notification value (e.g., the entropic URL, guest ID, password, etc.) As above, upon receipt of the device key and notification value, the server or system will attempt to validate the device key and/or the access token.
Still referring to FIG. 9B, if the device does not have a device key for the access token, then the method will determine whether the access token is “locked,” or whether the access token is associated with a device or needs to be associated with a device. If neither, for instance, if the access token does not have a device key and is not associated with another device, then the method will proceed to validate the access token without a device key, as shown at 308.
If yes, for instance, if the access token has a device key associated with it, then, as shown at 309, the method will continue to determine whether the server or system returned a device key. If a device key is not returned or communicated by the server at this point, then it is determined that the access token is already associated with another device. Accordingly, as shown at 311, the method may continue at this point with an error message indicating that the access token is locked and cannot be accessed by this device.
However, as described above, in at least one embodiment, if a device key is communicated from the server or system to the guest device, then it may signify that this is the first access to the access token or that the access token is configured to allow association with the device. In that case, as shown at 313, the device will receive the device key and store the device key, for example, locally on the device itself or otherwise in a location that can be subsequently accessed. The device can then communicate the device key and the notification value back to the server for validation of the access token, as described herein, and as generally shown at 315 and 308. Accordingly, if there is a successful communication between the device and the system, for example, if the device successfully stores the device key and communicates it back to the system, the status of the access token may be automatically changed (for example, by setting a device lock flag). Subsequent communications with the system for that particular access token will therefore require the device key from the device.
To illustrate this embodiment with an example, assume a resident would like to provide access to the premises for a housekeeper, but does not want the housekeeper to send the invitation or notification to his/her relatives, friends or anyone. Accordingly, the resident creates the invitation via the system and method of at least one embodiment, noting that the invitation must be limited to one device. The access token is generated and a notification is sent to the guest or housekeeper.
When the guest or housekeeper first opens the notification and requests access to the access token, the server or system will only return or communicate the device key associated with the access token. No other information is communicated and access is not granted at this point.
The guest device (e.g., via a browser or application) may then present a confirmation screen noting that once the guest proceeds, the guest will only be able to use that particular device for subsequent access to the location or premises. The guest device (e.g., via a browser or application) receives the device key and stores it for subsequent retrieval. The device (e.g., via a browser or application) then sends the device key and the notification value (e.g., the entropic URL) back to the server proving that the device received the device key. The server or system will then change the status of the access token (e.g., via a setting or flag) so that subsequent accesses or requests will require the device key to be communicated by the device to gain access to the location.
In this manner, if the guest or housekeeper does send the notification or invitation to another person, subsequent attempts to retrieve the access token and gain access to the location via another device will fail without the unique device key.
It should be noted that other embodiments may utilize unique device identifier, SIM serial number, etc. as the device key. In such a case, the device key may be provided by the device itself (e.g., upon first retrieval of the access token), received by the server and stored in order to require the device key for subsequent retrievals.
This written description provides an illustrative explanation and/or account of the present invention. It may be possible to deliver equivalent benefits and insights using variations of the sequence, steps, specific embodiments and methods, without departing from the inventive concept. This description and these drawings, therefore, are to be regarded as illustrative and not restrictive.

## Claims

1. A method for verified admission through an access controlled location, the method comprising:
receiving a request at a remote access control management system from a requesting device to create a guest access token for admission through the controlled access location, the guest access token comprising location and time parameters, the remote access control management system comprising a computer processor, memory, a storage device and a communication module,
generating the guest access token and storing the guest access token at the remote access control management system,
associating a unique device key with the guest access token for limiting access to the guest access token to a predefined number of guest devices,
generating a unique notification corresponding to the guest access token, wherein initial selective activation of the guest access token causes association of the unique device key with at least one of the predefined number of guest devices, and wherein if the unique device key is associated with a guest device used to activate the unique notification, then selective activation of the notification via the guest device causes retrieval of the guest access token from the remote access control management system,
validating the time parameter and the location parameter of the guest access token prior to granting access to the access controlled location,
granting access to the access controlled location by communicating an access command from the remote access control management system to a control device at the access controlled location.

2. The method as recited in claim 1 further comprising communicating the unique notification directly to the guest device via the remote access control management system.

3. The method as recited in claim 1 further comprising communicating the unique notification to the requesting device for delivery to a guest.

4. The method as recited in claim 3 further comprising utilizing short messaging service (SMS) capabilities of the requesting device for communication of the unique notification to a guest device.

5. The method as recited in claim 3 further comprising utilizing network connectivity of the requesting device for communication of the unique notification to a guest device.

6. The method as recited in claim 5 further comprising displaying a social networking activation window at the requesting device for communicating the unique notification to the guest via a third-party social network.

7. The method as recited in claim 3 further comprising defining the notification for selective retrieval of the guest access token as comprising a unique uniform resource locator corresponding to the guest access token.

8. The method as recited in claim 7 wherein the unique uniform resource locator is embedded within a machine readable code.

9. The method as recited in claim 8 wherein the machine readable code comprises a quick response (QR) code.

10. The method as recited in claim 7 further comprising defining the unique uniform resource locator as comprising a combination of a guest ID and a uniquely generated entropic value, the uniquely generated entropic value being stored within a database and corresponding to the guest ID.

11. The method as recited in claim 10 further comprising, upon activation of the unique uniform resource locator, decoding the unique uniform resource locator to determine the guest ID and the uniquely generated entropic value for verifying and retrieving the access token.

12. The method as recited in claim 1 wherein validating the location parameter comprises establishing a GPS location of a guest device and comparing the GPS location of the guest device to the location parameter of the guest access token.

13. The method as recited in claim 1 wherein validating the location parameter of the guest access token comprises:
displaying a validation code locally at the access controlled location via a local display device,
receiving a validation input at the remote access control management system from the guest device, and
comparing the validation input to the validation code displayed locally at the access controlled location.

14. The method as recited in claim 1 further comprising upon validating the unique device key, the location parameter, and the time parameter, providing an activation link for activating admission through the access controlled location.

15. The method as recited in claim 14 further comprising upon receiving activation of the activation link via the guest device communicating the access command to the control device.

16. A system for verified admission through an access controlled location, said system comprising:
a local computer-based control device communicatively connected to an access control mechanism,
a remote access control management system comprising a computer processor, memory, storage device and communication module, said remote access control system being disposed in a communicative relation with a network for communication with a guest device and said local computer-based control device,
a token generating module at said remote access control management system for receiving a request to create a guest access token and for generating said guest access token, said guest access token comprising a location parameter, a time parameter, and a unique device key, said unique device key being structured to limit access to the access controlled location to a predefined number of guest devices,
at least one validation module for processing and validating said guest access token, wherein upon an initial request to access said guest access token from a guest device, said unique device key is associated with the guest device,
said remote access control management system being structured to communicate an access command to said local computer-based control device upon validation of said unique device key, said location parameter and said time parameter, and
said local computer-based control device being structured to activate the access control mechanism upon receipt of said access command from said remote access control management system for providing admission through the access controlled location.

17. The system as recited in claim 16 wherein said remote access control management system is structured to generate a notification corresponding to said guest access token, wherein, if said unique device key is validated, selective activation of said notification causes retrieval of said guest access token from said remote access control management system.

18. The system as recited in claim 16 wherein said remote access control management system is structured to communicate said notification directly to the guest device.

19. The system as recited in claim 16 wherein said remote access control management system is structured to communicate said notification to a requesting device for subsequent delivery to a guest.

20. A method for verified admission through an access controlled location, the method comprising:
receiving a request at a remote access control management system from a requesting device to create an access token for admission through the access controlled location, the access token comprising a location parameter and a time parameter, the remote access control management system comprising a computer processor, memory, a storage device and a communication module,
generating the access token and storing the access token at the remote access control management system,
generating a unique notification value corresponding to the access token, the unique notification value being uniquely associated with the access token for subsequent retrieval of the guest access token and for admission through the controlled access location, and
optionally creating a unique device key, wherein the unique device key is structured to limit access to the access token to at least one device, wherein the at least one device is associated with the unique device key.

21. The method as recited in claim 20 further comprising:
upon receipt of a request to access the access token by a guest device:
if the access token is configured to allow creating an association with a device, then: communicating the unique device key to the guest device for storage of the unique device key thereon,
else, if the access token is not configured to allow creating an association with a device, then: validating the unique device key by receiving the unique device key from the guest device and comparing the received unique device key with the unique device key associated with the access token.

22. The method as recited in claim 21 further comprising validating the time parameter and the location parameter of the access token.

23. The method as recited in claim 22 further comprising granting access to the access controlled location by communicating an access command from the remote access control management system to a control device at the access controlled location.

24. The method as recited in claim 21 further comprising defining the unique notification value as comprising a combination of a guest ID and a uniquely generated entropic value, wherein the uniquely generated entropic value is associated with the guest ID for retrieval of the access token.

25. The method as recited in claim 24 wherein retrieval of the access token comprises, upon receipt of the unique notification value, decoding the unique notification value to determine the guest ID and the uniquely generate entropic value.