Patent Grant
10229548
The present application relates to operating access control devices, and more particularly granting guest access to a secured premises via operation of access control devices.
A variety of access control devices have been developed to allow visitors access to a secured area. In one example, the secured area can be a building having one or more tenants, such as apartments, condominiums, offices, or the like. Other secured areas can include a gated community or other collection of buildings having a common secured entrance.
One type of access control device configured to grant access to such secured areas includes a housing with a display, speaker, microphone, and a dedicated telephone connection to connect a visitor with a contact person within or in control of the secured area. The display shows a list of contacts within the secured area and corresponding contact codes so that a visitor can scroll through the list to find a desired person or company. The visitor then can use the keypad on the access control device to enter the contact code to call the desired contact. The visitor can then verify his/her identity via a conversation with the desired contact, and the contact can disengage a lock on a door or other movable barrier, such as through selection of an appropriate button on the desired contact's telephone. While this type of access control device provides secure entry for both owners and guests, it is costly, requiring installation and a dedicated phone line, not to mention maintenance. Also, such systems require that the display device be fully functional at all times.
Generally speaking, and pursuant to these various embodiments, a method, apparatus, and computer-readable medium are described that allow a guest to contact an owner or operator of a secured premises or area to gain access to the secured premises. A guest's communication device, such as a smart phone, tablet, laptop, or the like, can communicate with both an access control device and an owner communication device, and act as a gateway for communication between the owner communication device and the access control device. As such, the access control device can facilitate communication between the guest device and the owner device for the owner to confirm the guest's identity and the guest device can then forward an authorized control signal sent from the owner device to the access control device to grant the guest access to the secured premises.
More specifically, an access control device initiates contact with a guest device and provides a resource to contact an owner device. If the owner decides to grant access to the guest, the owner selects a suitable input on the owner device so that the owner device sends an authorized signal to the guest device. The guest device acts as a gateway and forwards the authorized signal to the access control device. The access control device operates in response to reception of the authorized signal to grant the guest access to the secured premises.
The access control device can output a signal that is visible on the guest device informing the guest of its existence and operation. Alternatively, guest device can initiate contact with the access control device, such as by following displayed instructions. In response to communication with the access control device, an interface then can appear on a display of the guest device providing the guest with a list of owners associated with the secured premises. The guest selects a desired owner entry to contact a communication device of the selected owner. After confirming the guest's identity, the owner can then provide an input in the owner device to send an authorized control signal to the guest device, which acts as a gateway and forwards the authorized control signal to the access control device. The access control device operates in response to reception of the authorized control signal and grants access to the guest. The access control device can move a movable barrier, unlock a door, or perform other access functions.
The embodiments described herein advantageously enable an owner to easily grant access to a secured premises without a dedicated communication line or hardwired communication system. The system also utilizes communication devices previously owned by the owner and guest avoiding costs associating with connecting the owner and guest. Additionally, the interface provided on the guest device can provide information in a more consumer-friendly format as compared to previous entry devices that can require repetitive scrolling and separate dialing functions.
The above needs are at least partially met through provision of the remote guest access approaches described in the following detailed description, particularly, when studied in conjunction with the drawings wherein:
Skilled artisans will appreciate the elements and the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help improve understanding of various embodiments. Also, common but well understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted to facilitate a less obstructive view of these various embodiments. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions and a person skilled in the technical field as set forth above, except where different specific meanings have otherwise been set forth herein.
Application software for a mobile device and/or a website hosted on one or more server devices can be utilized to gain access to a secured premises via communication with an owner or tenant of the secured premises. The application software utilizes a functionality of the guest's mobile device to determine a location and determine whether the location is within a predetermined area surrounding an access control device that controls access to the secured premises, such as through movement of a movable barrier, operation of a lock device, or the like. In response to determining that the guest's mobile device is located within the predetermined area, the application software can display identification information for owners or tenants of the secured premises. Upon receipt of a selection received from a user input of the guest's mobile device, the mobile device can communicate with a device of the owner over any suitable communication network to be granted access to the secured premises by operation of the access control device. Access can be granted via the mobile device's receiving credentials or a code to operate the access control device or the owner operating the access control device.
The following terms, which will be used throughout the disclosure herein, can have a variety of suitable meanings. For example, when used herein, an “owner” of a premises or secured area can refer to any person with the authority to authorize a guest to enter the premises or secured area. In a straightforward situation, the owner can personally own the premises, such as with a home or business, and has the authority to authorize access to a guest, such as an independent contractor, employee, customer, or personal acquaintance. The disclosure herein, however, works equally well with an example of a corporation or other business having any number of employees. In this situation, the owner would refer to a person in a position of authority, such as a CEO, president, vice-president, manager, security personnel, and the like. Without limitation, the disclosure herein can provide an owner of a premises having an access control device therein the ability to remotely grant a guest access to the premises or secured area. Similarly, “premises” can refer to a residential structure, commercial structure, industrial structure, or other secured area, or portion(s) thereof.
Details of the interacting components and structure of the system disclosed herein are shown in
As shown in
As shown in
By a second approach, the access control device 18 can be a separate gateway device capable of receiving the authorized control signal and translating the signal to a language understood by one of the specific secondary devices 40 as discussed above. For ease of description, however, all scenarios will be described as an access control device hereinafter.
The exchange of information between the guest and the owner can be facilitated via a software application (“application”) installed on operating on a mobile device, such as a smart telephone, tablet, or the like although aspects of the application may be executed in a network based server or other device on or near the premises in communication with the guest device. Alternatively, or in addition thereto, the communication can be facilitated through a web site. Each configuration will be discussed herein.
As discussed in the background, the issue arises when a guest approaches the secured premises 38 and needs to be granted access by the owner. In a first instance, a machine readable code 43, such as a QR code, barcode, or the like, is positioned in a visible area 44 adjacent to an access point 42 controlled by the access control device 18. Instructions can be posted along with the machine readable code instructing the guest to scan the code with the guest device 14 for gaining access to the secured premises 38. If necessary, the instructions can also include the name of an application that can read the code or provide the requirements for reading the code. Once scanned, the guest device 14 can decode the machine readable code and display the linked content on the display 32 of the guest device 14.
The linked content can take a variety of suitable forms. In one example, the linked content can be a hyperlink that, once selected, directs the guest device 14 to a website, directory, database, or the like. The website provides the ability to download the application onto the guest device 14 and/or provide information identifying and explaining the operation of the application. Once downloaded, the application is installed on the guest device 14 to run thereon and facilitate the guest gaining access to the secured premises 38, as described in more detail below.
In another example, the linked content provides identification information for the application that can include a name, a location for downloading the application, instructions for use, associated products, and the like. As such, the guest then enters a website address or identification information for the application in a browser or online store for downloading and installation.
Alternatively, rather than the machine readable code, application identification information, such as a website address, a name of the application, or the like, can be printed or posted in the visible area adjacent to the access point.
By another approach, the guest device 14 can connect to a WiFi network 46 surrounding or adjacent to the access control device 18. The WiFi network 46 can be generated by circuitry in the access control device 18 or by a separate device 47 (which may be located inside the secured premises 38 near the access point 42) as desired. In order to instruct a guest accordingly, an SSID of the WiFi network 46 can be identified and posted within the visible area with instructions to connect the guest device 14 to the WiFi network 46. In one form, after the guest device 14 connects to the WiFi network 46, the WiFi network 46 causes a browser to automatically be directed to a website. As such, when a guest opens a browser on the guest device 14, the browser is directed to a desired website for gaining access to the secured premises.
Location determination provides a unique security function for granting a guest device 14 access to a secured premises 18. More specifically, the location determination can be performed prior to enabling the guest device 14 to contact the owner, so that the owner is not disturbed before a guest is actually present in a location where access is necessary. Additionally, the location determination prevents a guest from attempting to get an owner to disable security when the guest device is not present. The location of the guest device 14 can be determined in a variety of suitable ways, as described below.
In a first approach, location can be determined using circuitry in the guest device 14 and signals with third party devices. In one form, the guest device 14 location is determined using the GPS circuitry 34 in the guest device 14 via communication with GPS satellites. In another form, location is determined via measurements of signals at cellular towers, such as angle of approach, reception time between multiple towers, signal strength between multiple towers, or the like. Using either form, the location of the guest device 14 can be determined to a sufficient accuracy for the application to confirm that it is near the access control device 18 within an access location area 48, as described in greater detail below.
In a second approach, the application can utilize near field communication to confirm the guest device's location within the application. Near field communication utilizes a relatively small antenna set to transmit at a radio frequency that limits the size of the generated electromagnetic field 46. The signal can advantageously be modulated to transmit a signal to another antenna that is within this field. This other antenna can be a powered device or can be an unpowered chip or tag. To determine the location of the guest device 14, an antenna generating the electromagnetic field 46 can be placed near or within the access control device 18. As such, when the guest brings the guest device 14 into the electromagnetic field 46, the application can utilize the signal to confirm that the guest device 14 is located near the access control device 18. Alternatively, the guest device 14 can generate the electromagnetic field 46 to communicate with an antenna 50 located within or near the access control device.
In a third approach, the application can utilize a Bluetooth communication protocol to confirm the guest device's location. As with the earlier approach using near field communication, a Bluetooth device near or within the access control device 18 can generate a Bluetooth signal creating a field 46 surrounding or next to the access control device 18. The guest device 14 can then pair with the Bluetooth device, such as with the aid of the application, or just confirm that the Bluetooth device is within the guest device's Bluetooth signal range. In this form, the application utilizes pairing or receiving the Bluetooth signal to confirm the location of the guest device 14.
In a fourth approach, the application can utilize a WiFi network 46 to confirm the guest device's location. More specifically, a WiFi device in or near the access control device 18 generates the WiFi network 16 around or near the access control device 18. The guest device 14 then connects to the WiFi network 46 or confirms that the WiFi network 46 is within the guest device's range so that the application can confirm the guest device's presence within the access location area 48.
The access location area 48 can be set within the application by the owner and/or automatically by the application after a location of the access control device 18 are inputted into the application. By one approach, the owner operates the application on the owner device 10 in order to identify and register the access control device 18 with the application. This can be done by inputting identification information, such as registration numbers, serial numbers, or the like into the application using the user input 22 on the owner device 10.
After the access control device 18 is registered, the owner then sets a desired location determination method, such as one of the options outlined above. Selection of the location determination method determines how the access location area 48 can be set. Each option will be described in turn below.
In the approach using location circuitry 34 in the guest device 14, such as GPS or signal triangulation, the owner inputs an installation location for the access control device 18. After the installation location is set, the application can optionally automatically set the access location area 48. The access location area 48 can be set as a predetermined area surrounding the access control device 18, an area outside of the secured premises 38 adjacent to the access control device 18, or the like. By a further or alternative approach, the owner can input into the application or revise a length already set in the application to set a radius for the access location area 48 surrounding the access control device 18, which in operation would create a disk-shaped access location area 48. By yet another approach, the application can utilize a map or other display of an area surrounding the access control device 18 to allow the owner to directly input the access location area 48 by drawing or highlighting a desired area. In this way, the owner can specify the access location area to only be within desirable areas, such as an area only outside the secured premises, an open area, a designated security area, or the like. This information defining the location area 48 can be stored with the application at the guest device 14 and/or in a networked storage or a storage device located at the secured premises 38.
In the approach using near field communication, the size of the broadcasting antenna determines the size of the electromagnetic field 46. In a first approach, the owner can place the broadcasting antenna 50 at a desired location in or near the access control device 18 to thereby place the electromagnetic field 46 therearound. In an alternative approach, the electromagnetic field 46 can be generated by the guest device 14. As such, an active or passive owner antenna 50 can then be placed or mounted within or near the access control device 18 so that the owner antenna receives a signal from the guest device 14 when the guest device 14 is brought close enough to the owner antenna 50. For instance, the application in the guest device 14 can transmit an identification over the near field communication to the owner device 10 or access device 18 which confirms the guest device's location within the access location area 48. Alternatively, the guest device 14 may receive a unique identification code or signal from the broadcasting antenna 50 that matches that stored in the application at the guest device 14, a network storage, or storage at the secured premises 38. In either approach, the match and confirmation that the guest device 14 is within the access location area 48 is communicated and processed prior to taking the next steps of granting access to the secured premises 38.
In the approach using Bluetooth communication, the Bluetooth generating antenna 50 can similarly be located within the access control device 18, or a Bluetooth device disposed near the access control device 18, as discussed above with respect to the near field communication approach. As such, the owner antenna 50 broadcasts a Bluetooth signal and the guest can manipulate the guest device 14 through a suitable user input 22 to pair the guest device 14 with the access control device 18. The application can facilitate this pairing via appropriate prompts on the display 32 to enter information as necessary. The application, after the guest device 14 has paired, either confirms the guest device's presence within the access location area 48 or sends the owner antenna's Bluetooth signal identification to another device to confirm the pairing. After confirmation, which effectively confirms the proximity of the guest device 14 to the access point 42, the guest device 14 begins taking the next steps of granting access to the secured premises 38 as described in greater detail below. Alternatively, the application can confirm the guest device's presence within the access location area 48 simply by determining that the Bluetooth signal can be received without fully pairing the devices and confirming that signal either locally at the guest device 14 or through communication over a network. By another approach, the Bluetooth signal can be broadcast from an antenna 26 of the guest device 14. So configured, the guest brings the guest device 14 into a suitable range to communicate with the Bluetooth antenna 50 in the access control device or separate and near thereto, whether passive or active. The application then confirms that the guest device 14 is within the access location area 48 via communication with the owner Bluetooth device 50.
As such, when the application is called on by the guest to gain access to the secured premises 38, the application automatically or manually determines a current location of the guest device 14 through the short range communication with one or more devices located at or near the access point 42 as described above. Additionally or alternatively, the application can use known mobile device location determination tools to determine the guest device's location to be compared with the access location area 48 corresponding to the access control device 18. The application can effect this comparison on the guest device 14 or by sending the guest device's location information to another device that effects the comparison to determine whether the guest device's current location is within the access location area 48. Alternatively, the application can determine whether the guest device 14 is within the access location area 48 after the guest has selected to contact an owner, set forth in more detail below.
To facilitate confirmation of the guest's identity to the owner, the guest can then be provided with a list of owners within the secured premises 38. If there are a sufficient number of owners, the application can provide a scrolling list of names or sequential pages, as desired. The owner list can be sorted, either automatically or via user input in the application, alphabetically, by location, or the like.
In one form, the list of owners maintains confidentiality by providing limited identification information for the owners. As such, one or more of the following information can be omitted from the list: location, such as floor, room number, or the like, contact information, such as telephone numbers, email addresses, usernames, or the like.
When used in a setting where there is more than one owner within the secured premises 38, the application can further provide an administrative status for editing the owner list, including adding new owners, removing owners, or editing owner information. Administrative status can be granted to a management company for the secured premises, a board of an association for the secured premises, or any of the owners, as desired. The application can preferably require a password, code, or other identification information in order to grant access to editing the owner list. When adding a new owner or editing a current owner, the owner or other administrator enter owner identification information, including name, location, and contact information for the owner device 10, so that the application can facilitate confidential communication between the guest device 14 and the owner device 10.
When a guest finds a desired owner, the guest can select the entry of the desired owner via the user input 22, such as a touch screen, button, or the like. With the selection, the application then provides a prompt asking the guest via the device display 32 whether the guest would like to contact the desired owner. This can be via a new window or screen displayed within the application, via a pop-up window, or within the original display. Alternatively, the application can automatically attempt to contact the owner after selection.
In one approach, the application sends guest information to the owner along with the contacting signal. The guest information can include a name, address, and contact information, such as one or more telephone numbers, email addresses, usernames, or the like. The guest can input the guest information into the application prior to use or can input the guest information into a prompt directed by the application prior to contacting the owner. As such, when the application contacts the owner, the owner will be presented with the guest information, which will provide the owner with information to make an entry decision and warn the owner of the identity of the guest for a subsequent conversation.
The application can initiate contact with the owner to inform the owner of the guest's presence within the access location area 48 and desire for entry into the secured premises 38 in any suitable way. In a first approach, the application causes a push notification to appear on the owner device 10 and produce an audible signal, such as a ring or tone through a speaker 52 of the owner device 10, and/or a tactile signal utilizing a vibration setting 52 of the owner device 10, as set by the owner. The push notification can be caused by any suitable message, including SMS messages, video messages, email messages, chat messages, or the like. The application can advantageously send messages confidentially so that the guest is not given contact information for the owner.
In another approach, the application calls the owner device 10 or initiates a video conference with the owner device 10 utilizing a camera device 54 and/or microphone in the guest device 14 (or otherwise mounted near the access point 42) and, if desired, a camera device 54 in the owner device 10. In the first instance, the owner confirms via a conversation with the guest the guest's identity to make an informed decision on whether to grant entry to the guest. In the second instance, seeing the guest via the video conference allows the owner to make an informed decision on whether to grant entry to the guest.
In order to be granted access to the secured premises 38, an authorized control signal is sent to the access control device 18. In one approach, the owner controls the operation of the access control device 18 via the user input 22 on the owner device 10. As such, after the owner has confirmed the identity of the guest and decides to grant access, the owner instructs the application to send the authorized control signal by selecting an appropriate input of the owner device 10 and identified by the application, which causes the owner device 10 to send the authorized control signal to the access control device 18 via any suitable communication network 20.
Alternatively, or in addition, the owner can grant access rights to the guest. In this form, the application utilizes access rights data that includes identification information of the access control device 18 and corresponding authorization information for access rights to the access control device 18. In other words, the access rights data includes credentials required by the access control device 18, a conditional requirement for allowing the credentials, and the identification information of the access control device 18. Advantageously, the application further grants the owner the ability to send the access rights data to one or more guest devices 14. In other words, upon instruction of the owner through the application, the application can transmit the access rights data or cause the access rights data to be transmitted to the guest device 14, which then provides the guest device 14 the ability to send an authorized control signal to the access control device 18, for example, through a wireless communication signal between the guest device 14 and one or more of the control device 18, wireless device 47, or other device. In another approach, the credentials may be a code that the guest reads from the guest device 14 and enters into the control device 18 through a keypad, speech, or other interaction to affect entry to the secured premises 38.
If desired, the application can cause the access rights data to be stored in the memory 28 of the owner device 10. This information can be manually entered by the owner through the user input 22 of the owner device 10, by download from the access control device 18, by retrieving or receiving the access rights data from a network device, or the application can have a learn mode similar to a learning transmitter known in the art so that the owner device 10 receives and stores the information from a transmission of an authorized transmitter. Thus, if desired, the application can provide the owner with transmitter functionality to send an authorized control signal to the access control device 18 with the owner device 10. So configured, after the application has determined that the guest device 14 is within the access location area 48, the application can then check for previously granted access rights and any restrictions on the access rights, if applicable. If there are no restrictions, the application can then automatically prompt the guest for input on the display 32 of the guest device 14 and send the authorized control signal to operate the access control device 18 in response to selection of the user input 22. In this case, the application can further send a message, place a call, or otherwise contact the owner device 10 to notify the owner that the guest is being granted access to the secured premises 38.
Upon reception of the access rights data from the owner device 10, the application running on the guest device 14 can then configure the guest device 14 to send an authorized control signal to the access control device 18 to allow the guest to thereby operate the access control device 18. In one approach, the guest can instruct the application running on the guest device 14 to be receptive to the access rights data, such as in a learning mode, download the access rights data, such as from a third party server device, and/or store the access rights data in the memory 28. In another approach, the application can automatically store the access rights data in the memory 28 of the guest device 14. Then, when the guest desires to operate the access control device 18, the guest can run the application on the guest device 14, which can retrieve the access rights data and transmit an authorized control signal through the guest device transmitter 26 to the access control device 18, such as through Bluetooth, a cellular network, the internet, or the like.
Advantageously, the application can also be used by the owner to restrict usage of the access rights sent to the guest device 14. Specifically, the application can allow the owner to enter restrictions on the access rights granted to the guest device, including, temporal restrictions, spatial restrictions, or combinations thereof. For example, if the access control device 18 controls the locking and unlocking of a door 42, the restrictions can prevent the guest device 14 from being able to unlock the door 42 during specified times, such as specified hours of a day, one or more days during a week, or combinations thereof. In another example, if the premises 38 includes a series of locked doors, the restrictions can prevent the guest device 14 from being able to unlock specified doors so that the guest can only access selected areas of the premises 38.
The owner can input these restrictions or conditions into the application prior to the access rights data being sent to the guest device 14 so that the access rights data is sent with the restrictions to the guest device 14. As such, the application running on the guest device 14 can restrict transmission of an authorized signal or can transmit the signal along with the restrictions configured to be interpreted by the access control device 18 to permit or deny the requested action based on analysis of the restrictions. Alternatively or in addition thereto, the owner can subsequently modify already granted access rights by inputting the restrictions into the owner device 10 and sending the restrictions or causing the restrictions to be sent to the guest device 14 via the application to alter the authorized access rights stored on the guest device 14. By another approach, the owner device 10 can send the restrictions or conditions directly to the access control device 18. As such, the access control device 18 can access restrictions upon reception of a signal from the guest device 14 and permit or deny the requested action based on the restrictions. By yet another approach, the owner device 10 can input the restrictions or conditions at an intermediary server 16 or send the restrictions thereto. As such, the intermediary server 16 then controls the conditions placed on the authorization of the guest device 14 to send signals to the access control device. This is useful if the control signal from the guest device 14 is routed through the intermediary server 16.
So configured, upon instruction to send the authorized control signal to the access control device 18 with the user input 22 of the guest device 14, the application determines whether any restrictions on the access rights are applicable. If there are no restrictions applicable, the application can cause the transmitter 26 of the guest device 14 to transmit the authorized control signal to the access control device 18. Alternatively, the application can prevent sending of the control signal due to restrictions being applicable. For example, the application can display a grayed-out state, crossed-out, or the like. Additionally, the application can display the restrictions alongside or within the window of the secured premises 38.
By another approach, the access rights can be sent to the guest device 14 without any authorization for use. As such, the owner can subsequently send allowed or authorized spatial or temporal zones to the guest device 14 or intermediary server 16, or identify the allowed or authorized spatial or temporal zones for subsequent sending by a third party.
Of course, the application also allows the owner to revoke the access rights, such as by sending a revocation transmission to the application on the guest device 14 or to a third party server device or service, which would then deactivate or delete the access rights data from the guest device 14.
The various options for transmitting the access rights from the owner device 10 to the guest device 14 are described below with reference to
In a first example, shown in
In another example, shown in
Turning now to
Other example communication configurations, as shown in
By other approaches, as shown in
In all of the above communication examples, the application can include a self-test operation. Specifically, the self-test operation can cause the guest device 14, upon reception of the access rights data, to send a test control signal to the access control device 18. The self-test operation can either do this automatically upon reception and storage, can require the application to transmit the test control signal within a specified time, or can require the application to transmit the test control signal prior to a first use. The test signal can result in the access control device 18 transmitting a confirmation signal in response to the test signal, which can be routed through the intermediary server 16. The confirmation signal can be transmitted to the guest device 14 and/or the owner device 10, as desired. Alternatively, operation of access control device 18 by the guest device 14 can confirm to both the owner and guest that the transmission of the access rights data was successful.
In some instances, the owner may want to create a list of guests that have been granted access or can be pre-screened to be granted access. As such, the application can provide a functionality for the owner to indicate whether the access rights sent to the guest device 14 should be permanently stored on the guest device 14 or permanently accessible by the guest device 14. The guest list can identify the allowed guests by name, telephone number, or other suitable identification information. Of course, the application can also provide editing functionalities to the owner so that the owner can edit the restrictions placed on the access rights of particular guests, remove guests, or add new guests. If desired, the application can prompt the owner to indicate whether a guest that has been granted access to the secured premises 38 should be added to the guest list.
Alternatively, for other instances requiring lower security, the guest list can be public, and guests can sign up through the application or via a website. As such, the guest inputs identification information and guest device identification information and, in response, the application operating on the guest device is granted access to the access rights data, which can be stored on a server device or the like. The public list can further include a functionality for an owner or administrator to remove or block specific guests and/or guest devices via their identification information.
Advantageously, the location determination can be used by applications of recognized guests for automatic entry. More specifically, after the application determines that the guest device 14 is within the access location area 48 in any of the ways discussed above, the application can then check for previously granted access rights and any restrictions on the access rights, if applicable. If there are no restrictions, the application can then automatically send the authorized control signal to operate the access control device 18 without further input from the guest. In this case, the application can further send a message, place a call, or otherwise contact the owner device 10 to notify the owner that the guest is being granted access to the secured premises 38.
Turning now to examples of operation of the interaction between the guest device 14 and the access control device 18 after the guest device 14 successfully receives the access rights data from the owner device 10, as shown in
In the most straightforward example, as shown in
In another example, as shown in
In the examples shown in
In a second example of
In another example of
Depending on the size of the access location area 48 and/or the area surrounding the access point 42, it may be difficult to actually find the access point 42. If desired, the application can help direct a guest to the access point 42. More specifically, the application can retrieve or receive a location of the access point 42 stored on a server device or requested from the owner device 10. Then, utilizing GPS circuitry 34 in the guest device 14, the application can display the location of the access point 42 and, optionally, provide a route for finding the access point 42. This is particularly helpful in a setting where there are several visible doors to gain access to the secured premises 38, but only one can be operated by the application.
In alternative forms, access codes utilizing a keypad or the like can be used in place of the authorized control signal discussed above. In this case, the owner device 10 instructs the application to send an access code to the guest device 14 after confirming the identity of the guest and the guest can then enter the access code to gain entry to the secured premises 38. If desired, the application can operate in conjunction with the access control device 18 to create access codes specific to individual ones of the guest devices 14. As such, the restrictions discussed above can be applied to the specific access codes as desired by the owner. Moreover, if the owner decides to rescind access rights to the guest, the owner can instruct the application to remove the access rights so that the access control device 18 will no longer recognize the rescinded access code.
An access control device as also described herein utilizes a guest device as a gateway for contacting an owner of a secured premises for a guest to gain access to the secured premises. The access control device outputs a signal that is visible on the guest device informing the guest of its existence and operation. The access control device, optionally in response to a user input in the guest device, causes an interface to appear on a display of the guest device so that the guest can select an entry corresponding to the owner. The selection causes the guest device to contact the owner so that the owner can confirm that the guest should be granted access to the secured premises. The owner can then provide an input in an owner device to send an authorization signal to the guest device. The guest device acts as a gateway to forward authorization signal to the access control device to thereby grant access to the guest. The access control device can move a movable barrier, unlock a door, or perform other access functions.
The following terms, which will be used throughout the disclosure herein, can have a variety of suitable meanings. For example, when used herein, an “owner” of a premises or secured area can refer to any person with the authority to authorize a guest to enter the premises or secured area. In a straightforward situation, the owner can personally own the premises, such as with a home or business, and has the authority to authorize access to a guest, such as an independent contractor, employee, customer, or personal acquaintance. The disclosure herein, however, works equally well with an example of a corporation or other business having any number of employees. In this situation, the owner would refer to a person in a position of authority, such as a CEO, president, vice-president, manager, security personnel, and the like. Without limitation, the disclosure herein can provide an owner of a premises having an access control device therein the ability to remotely grant a guest access to the premises or secured area. Similarly, “premises” can refer to a residential structure, commercial structure, industrial structure, or other secured area, or portion(s) thereof.
Details of the interacting components and structure of the system disclosed herein are shown in
As shown in
As shown in
By a first approach, the access control device 118 can be part of or integrated within the secondary device 140. For example, without limitation, the secondary device 140 can refer to a movable barrier operator, such as a garage door operator, door access control, gate operator, commercial door operator, and the like, a home automation system, an alarm system, a server device, a computing device, a network device, or the like. In this approach, the access control device 18 can directly receive the control signal from an authorized device to open or close a movable barrier, lock or unlock one or more doors, activate or deactivate an alarm, and the like so that the guest can gain access to the secured premises via an access point 142. As described below, the location of access control device 118 will be understood to include the location of the access point 142, although they can be separated as desired or needed for various configurations.
By a second approach, the access control device 118 can be a separate gateway device capable of receiving the authorized control signal and translating the signal to a language understood by one of the specific secondary devices 140 as discussed above. For ease of description, however, all scenarios will be described as an access control device hereinafter.
The access control device 118 continuously or periodically broadcasts an identification signal into a predetermined space surrounding the device. The identification signal is configured to identify the access control device 118 to receptive communication devices. So configured, when a guest enters the predetermined volume, the guest device 114 receives the identification signal and/or a uniform resource indicator (“URI”) associated with the access control device 118 appears on the display 132 of the guest device 114. In response to a selection of the URI via the user input 122 of the guest device 114, the resource identified by the URI is retrieved or received and displayed on the guest device display 132. Alternatively, the access control device 118 can cause the resource to be automatically displayed on the guest device 114 when the guest device enters the predetermined space. The resource can take any suitable form, including an electronic document, an image, a service, and a collection of other resources. By one approach, the resource is hosted by a network or server device. By another approach, the resource is hosted by the access control device 118 and sent to the guest device 114 directly therefrom. In one embodiment, the guest device being receptive to the signal or receiving the URI can be native to Bluetooth operation on the guest device.
In one form, the resource includes a list, table, or menu having one or more entries identifying owners associated with the secured premises 138. Any suitable configuration of displaying the entries can be utilized, such as a scrolling list, sequential pages, or the like. The owner list can be sorted, either automatically or via user input in the application, alphabetically, by location, or the like. In one form, the list of owners maintains confidentiality by providing limited identification information for the owners. As such, one or more of the following information can be omitted from the list: location, such as floor, room number, or the like, contact information, such as telephone numbers, email addresses, usernames, or the like.
When used in a setting where there is more than one owner within the secured premises 138, the resource can further provide an administrative status for editing the owner list, including adding new owners, removing owners, or editing owner information. Administrative status can be granted to a management company for the secured premises, a board of an association for the secured premises, or any of the owners, as desired. The resource can preferably require a password, code, or other identification information to grant access to editing the owner list. When adding a new owner or editing a current owner, the owner or other administrator enters owner identification information, including name, location, and contact information for the owner device 110, so that the resource can facilitate confidential communication between the guest device 114 and the owner device 110.
After a guest finds a desired owner, the guest can select the entry of the desired owner via the user input 122, such as a touch screen, button, or the like. With the selection, the resource then provides a prompt asking the guest via the device display 132 whether the guest would like to contact the desired owner. This can be via a new window or screen displayed within the application, via a pop-up window, or within the original display. The resource retrieves contact information for the selected owner, such as from a server device or the like, and attempts to contact the owner using the contact information. Alternatively, the application can automatically attempt to contact the owner device 110 after selection.
In one approach, the resource sends guest information to the owner device 110 along with the contacting signal. The guest information can include a name, address, and contact information, such as one or more telephone numbers, email addresses, usernames, or the like. The guest can input the guest information according to a prompt directed by the resource prior to contacting the owner. Alternatively, or in addition thereto, the guest can register with a service or software application, either prior to use or when needed. As such, when the resource contacts the owner device 110, the owner will be presented with the guest information, which will provide the owner with information to make an entry decision and warn the owner of the identity of the guest for a subsequent conversation.
The resource can initiate contact with the owner device 110 through the guest device 114 to inform the owner of the guest's desire for entry into the secured premises 138 in any suitable way. In one approach, the resource utilizes the guest device 114 to call the owner device 110 or initiate a video conference with the owner device 110 utilizing a camera device 154 and/or microphone in the guest device 114 (or otherwise mounted near the access point 142) and, if desired, a camera device 154 in the owner device 110. In the first instance, the owner confirms via a conversation with the guest the guest's identity to make an informed decision on whether to grant entry to the guest. In the second instance, seeing the guest via the video conference allows the owner to make an informed decision on whether to grant entry to the guest.
In another approach, the application causes a push notification to appear on the owner device 110 and produce an audible signal, such as a ring or tone through a speaker 152 of the owner device 110, and/or a tactile signal utilizing a vibration setting 152 of the owner device 110, as set by the owner. The push notification can be caused by any suitable message, including SMS messages, video messages, email messages, chat messages, or the like. The application can advantageously send messages confidentially so that the guest is not given contact information for the owner.
After the owner has confirmed the guest's identity and desires to grant the guest access to the secured premises 138, the owner can then select a suitable option with the user input 122, such as pressing a button on a numerical keypad, to send an authorized access signal to the guest device 114. If desired, the resource can require a passcode from the owner, such as a combination of numbers, symbols, letters, or combinations thereof, or biometric information, utilizing fingerprint recognition, face recognition, or other feature. In such an instance, the owner can enter the passcode to allow the guest to enter the secured premises.
In response to receiving the owner authorization, the authorized access signal is sent to the guest device 114. The resource operating on the guest device 114 causes the guest device 114 to act as a gateway and forward the authorized access signal to the access control device 118. The access control device 118 then operates to grant entry to the guest.
The communication between the owner device 110, the guest device 114, and the access control device 118 can operate over any suitable communication network 120 as stated above. Moreover, any of the above communications between these devices can be routed through an intermediary server or servers 116. In a first example shown in
In alternative forms, access codes utilizing a keypad or the like can be used in place of the authorized control signal discussed above. In this case, the owner device 110 sends an access code to the guest device 114 after confirming the identity of the guest and the guest can then enter the access code to gain entry to the secured premises 138. If desired, the resource can operate in conjunction with the access control device 118 to create access codes specific to individual ones of the guest devices 114. Moreover, if the owner decides to rescind access rights to the guest, the owner can instruct the resource and/or the access control device 118 to remove the specific access codes so that the access control device 118 will no longer recognize the rescinded access code.
The matter set forth in the foregoing description and accompanying drawings is offered by way of illustration only and not as a limitation. While particular embodiments have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made without departing from the broader aspects of applicants' contribution. The actual scope of the protection sought is intended to be defined in the following claims when viewed in their proper perspective based on the prior art.
This application is a continuation-in-part of U.S. application Ser. No. 14/525,924, filed Oct. 28, 2014, which issued as U.S. Pat. No. 9,396,598 on Jul. 19, 2016, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1446850 | Pone | Nov 1849 | A |
| 1076850 | Wedderburn | Oct 1913 | A |
| 1406850 | Hadaway | Feb 1922 | A |
| 2980827 | Hill | Apr 1961 | A |
| 3536836 | Pfeiffer | Oct 1970 | A |
| 4325146 | Lennington | Apr 1982 | A |
| 4360801 | Duhame | Nov 1982 | A |
| 4408251 | Kaplan | Oct 1983 | A |
| 4464651 | Duhame | Aug 1984 | A |
| 4533905 | Leivenzon | Aug 1985 | A |
| 4573046 | Pinnow | Feb 1986 | A |
| 4583081 | Schmitz | Apr 1986 | A |
| 4629874 | Pugsley | Dec 1986 | A |
| 4821024 | Bayha | Apr 1989 | A |
| 4881148 | Lambropoulos | Nov 1989 | A |
| 4922224 | Drori | May 1990 | A |
| 4987402 | Nykerk | Jan 1991 | A |
| 5003293 | Wu | Mar 1991 | A |
| 5047928 | Wiedemer | Sep 1991 | A |
| 5155680 | Wiedemer | Oct 1992 | A |
| 5191268 | Duhame | Mar 1993 | A |
| 5247440 | Capurka | Sep 1993 | A |
| 5255341 | Nakajima | Oct 1993 | A |
| 5278832 | Binzel | Jan 1994 | A |
| 5280527 | Gullman | Jan 1994 | A |
| 5283549 | Mehaffey | Feb 1994 | A |
| 5402105 | Doyle | Mar 1995 | A |
| 5444440 | Heydendahl | Aug 1995 | A |
| 5473318 | Martel | Dec 1995 | A |
| 5475377 | Lee | Dec 1995 | A |
| 5541585 | Duhame | Jul 1996 | A |
| 5565843 | Meyvis | Oct 1996 | A |
| 5565857 | Lee | Oct 1996 | A |
| 5596840 | Teich | Jan 1997 | A |
| 5608778 | Partridge, III | Mar 1997 | A |
| 5656900 | Michel | Aug 1997 | A |
| 5689236 | Kister | Nov 1997 | A |
| 5731756 | Roddy | Mar 1998 | A |
| 5780987 | Fitzgibbon | Jul 1998 | A |
| 5781107 | Ji | Jul 1998 | A |
| 5805064 | Yorkey | Sep 1998 | A |
| 5805082 | Hassett | Sep 1998 | A |
| 5883579 | Schreiner | Mar 1999 | A |
| 5886634 | Muhme | Mar 1999 | A |
| 5917405 | Joao | Jun 1999 | A |
| 5940000 | Dykema | Aug 1999 | A |
| 5969637 | Doppelt | Oct 1999 | A |
| 5990828 | King | Nov 1999 | A |
| 6002332 | King | Dec 1999 | A |
| 6011468 | Lee | Jan 2000 | A |
| 6026165 | Marino | Feb 2000 | A |
| 6028537 | Suman | Feb 2000 | A |
| 6070361 | Paterno | Jun 2000 | A |
| 6127740 | Roddy | Oct 2000 | A |
| 6131019 | King | Oct 2000 | A |
| 6154544 | Farris | Nov 2000 | A |
| 6161005 | Pinzon | Dec 2000 | A |
| 6166634 | Dean | Dec 2000 | A |
| 6184641 | Crimmins | Feb 2001 | B1 |
| 6192282 | Smith | Feb 2001 | B1 |
| 6223029 | Stenman | Apr 2001 | B1 |
| 6225903 | Soloway | May 2001 | B1 |
| 6266540 | Edgar, III | Jul 2001 | B1 |
| 6271765 | King | Aug 2001 | B1 |
| 6278249 | Fitzgibbon | Aug 2001 | B1 |
| 6310548 | Stephens, Jr. | Oct 2001 | B1 |
| 6326754 | Mullet | Dec 2001 | B1 |
| 6346889 | Moss | Feb 2002 | B1 |
| 6356868 | Yuschik | Mar 2002 | B1 |
| 6388559 | Cohen | May 2002 | B1 |
| 6400265 | Saylor | Jun 2002 | B1 |
| 6404337 | Van Till et al. | Jun 2002 | B1 |
| RE37784 | Fitzgibbon | Jul 2002 | E |
| 6427913 | Maloney | Aug 2002 | B1 |
| 6434158 | Harris | Aug 2002 | B1 |
| 6434408 | Heckel | Aug 2002 | B1 |
| 6448894 | Desai | Sep 2002 | B1 |
| 6476708 | Johnson | Nov 2002 | B1 |
| 6476732 | Stephan | Nov 2002 | B1 |
| 6484784 | Weik, III | Nov 2002 | B1 |
| 6525645 | King | Feb 2003 | B2 |
| 6553238 | Ginzel | Apr 2003 | B1 |
| 6553881 | Marmin | Apr 2003 | B2 |
| 6561255 | Mullet | May 2003 | B1 |
| 6563430 | Kemink | May 2003 | B1 |
| 6564056 | Fitzgerald | May 2003 | B1 |
| 6597291 | Tsui | Jul 2003 | B2 |
| 6616034 | Wu | Sep 2003 | B2 |
| 6634408 | Mays | Oct 2003 | B2 |
| 6661340 | Saylor et al. | Dec 2003 | B1 |
| 6686838 | Rezvani | Feb 2004 | B1 |
| 6717528 | Burleson | Apr 2004 | B1 |
| 6781516 | Reynard | Aug 2004 | B2 |
| 6782662 | McCartney | Aug 2004 | B2 |
| 6792083 | Dams | Sep 2004 | B2 |
| 6803851 | Kramer | Oct 2004 | B1 |
| 6803882 | Hoetzel | Oct 2004 | B2 |
| 6812849 | Ancel | Nov 2004 | B1 |
| 6822603 | Crimmins | Nov 2004 | B1 |
| 6823188 | Stern | Nov 2004 | B1 |
| 6833681 | Fitzgibbon | Dec 2004 | B2 |
| 6850163 | Adamczyk | Feb 2005 | B1 |
| 6891838 | Petite | May 2005 | B1 |
| 6903650 | Murray | Jun 2005 | B2 |
| 6919790 | Kanazawa | Jul 2005 | B2 |
| 6924727 | Nagaoka | Aug 2005 | B2 |
| 6933843 | Hom | Aug 2005 | B1 |
| 6960998 | Menard | Nov 2005 | B2 |
| 6975202 | Rodriguez | Dec 2005 | B1 |
| 6975226 | Reynard | Dec 2005 | B2 |
| 6980117 | Kirkland | Dec 2005 | B1 |
| 6980131 | Taylor | Dec 2005 | B1 |
| 6989760 | Dierking | Jan 2006 | B2 |
| 6998977 | Gregori | Feb 2006 | B2 |
| 7024819 | Irvin | Apr 2006 | B1 |
| 7038409 | Mullet | May 2006 | B1 |
| 7057494 | Fitzgibbon | Jun 2006 | B2 |
| 7071813 | Fitzgibbon | Jul 2006 | B2 |
| 7071850 | Fitzgibbon | Jul 2006 | B1 |
| 7091688 | Gioia | Aug 2006 | B2 |
| 7124943 | Quan | Oct 2006 | B2 |
| 7127847 | Fitzgibbon | Oct 2006 | B2 |
| 7142849 | Neuman | Nov 2006 | B2 |
| 7158007 | Kawamoto | Jan 2007 | B2 |
| 7161319 | Ergun | Jan 2007 | B2 |
| 7161466 | Chuey | Jan 2007 | B2 |
| 7167076 | Wilson | Jan 2007 | B2 |
| 7170998 | McLintock | Jan 2007 | B2 |
| 7190266 | Mullet | Mar 2007 | B2 |
| 7192278 | Cao | Mar 2007 | B2 |
| 7197278 | Harwood | Mar 2007 | B2 |
| 7205908 | Tsui | Apr 2007 | B2 |
| 7207142 | Mullet | Apr 2007 | B2 |
| 7221289 | Hom | May 2007 | B2 |
| 7227444 | Fitzgibbon | Jun 2007 | B2 |
| 7262683 | Maeda | Aug 2007 | B2 |
| 7266344 | Rodriguez | Sep 2007 | B2 |
| 7269416 | Guthrie | Sep 2007 | B2 |
| 7274300 | Duvernell | Sep 2007 | B2 |
| 7289014 | Mullet | Oct 2007 | B2 |
| 7298240 | Lamar | Nov 2007 | B2 |
| 7306145 | Sakai | Dec 2007 | B2 |
| 7310043 | Mamaloukas | Dec 2007 | B2 |
| 7323991 | Eckert | Jan 2008 | B1 |
| 7331144 | Parsadayan | Feb 2008 | B2 |
| 7332999 | Fitzgibbon | Feb 2008 | B2 |
| 7365634 | Brookbank | Apr 2008 | B2 |
| 7370074 | Alexander | May 2008 | B2 |
| 7380375 | Maly | Jun 2008 | B2 |
| 7392944 | Shieh | Jul 2008 | B2 |
| 7424733 | Kamiwada | Sep 2008 | B2 |
| 7446644 | Schaffzin | Nov 2008 | B2 |
| 7464403 | Hardman, Jr. | Dec 2008 | B2 |
| 7468676 | Styers | Dec 2008 | B2 |
| 7471199 | Zimmerman | Dec 2008 | B2 |
| 7482923 | Fitzgibbon | Jan 2009 | B2 |
| 7493726 | Fitzgibbon | Feb 2009 | B2 |
| 7498936 | Maeng | Mar 2009 | B2 |
| 7532965 | Robillard | May 2009 | B2 |
| 7561075 | Fitzgibbon | Jul 2009 | B2 |
| 7600550 | Mays | Oct 2009 | B2 |
| 7616090 | Baker | Nov 2009 | B2 |
| 7708048 | Mays | May 2010 | B2 |
| 7724687 | Autret | May 2010 | B2 |
| 7741951 | Fitzgibbon | Jun 2010 | B2 |
| 7750890 | Fitzgibbon | Jul 2010 | B2 |
| 7761186 | Keller | Jul 2010 | B2 |
| 7778604 | Bauman | Aug 2010 | B2 |
| 7783018 | Goldberg | Aug 2010 | B1 |
| 7852212 | Fitzgibbon | Dec 2010 | B2 |
| 7853221 | Rodriguez | Dec 2010 | B2 |
| 7856558 | Martin | Dec 2010 | B2 |
| 7876218 | Fitzgibbon | Jan 2011 | B2 |
| 7983160 | Gunatilake | Jul 2011 | B2 |
| 7983180 | Harrington | Jul 2011 | B2 |
| 7994896 | Fitzgibbon | Aug 2011 | B2 |
| 7995460 | Edgar, III | Aug 2011 | B2 |
| 8014528 | Bunte | Sep 2011 | B2 |
| 8040217 | Fitzgibbon | Oct 2011 | B2 |
| 8063592 | Shier | Nov 2011 | B2 |
| 8144011 | Fitzgibbon | Mar 2012 | B2 |
| 8175591 | Fitzgibbon | May 2012 | B2 |
| 8207818 | Keller, Jr. | Jun 2012 | B2 |
| 8239481 | Alexander | Aug 2012 | B2 |
| 8290515 | Staton | Oct 2012 | B2 |
| 8368509 | Fitzgibbon | Feb 2013 | B2 |
| 8416054 | Fitzgibbon | Apr 2013 | B2 |
| 8421591 | Karasek | Apr 2013 | B2 |
| 8423788 | Holtzman | Apr 2013 | B2 |
| 8544523 | Mays | Oct 2013 | B2 |
| 8561348 | Kurth | Oct 2013 | B2 |
| 8577392 | Pai | Nov 2013 | B1 |
| 8587404 | Laird | Nov 2013 | B2 |
| 8643465 | Fitzgibbon | Feb 2014 | B2 |
| 8797138 | Myers | Aug 2014 | B2 |
| 8868220 | Crucs | Oct 2014 | B2 |
| 9103149 | Skotty | Aug 2015 | B2 |
| 9122254 | Cate | Sep 2015 | B2 |
| 9141099 | Cate | Sep 2015 | B2 |
| 9317985 | Tehranchi | Apr 2016 | B2 |
| 9367978 | Sullivan | Jun 2016 | B2 |
| 9376851 | Cate | Jun 2016 | B2 |
| 9396598 | Daniel-Wayman | Jul 2016 | B2 |
| 9495815 | Fitzgibbon | Nov 2016 | B2 |
| 9644416 | Fitzgibbon | May 2017 | B2 |
| 9698997 | Arteaga-King | Jul 2017 | B2 |
| 9818243 | Fitzgibbon | Nov 2017 | B2 |
| 9896877 | Fitzgibbon | Feb 2018 | B2 |
| 20010011941 | King | Aug 2001 | A1 |
| 20010017483 | Frohberg | Aug 2001 | A1 |
| 20020014954 | Fitzgibbon | Feb 2002 | A1 |
| 20020033760 | Kobayashi | Mar 2002 | A1 |
| 20020067308 | Robertson | Jun 2002 | A1 |
| 20020162175 | Berglund | Nov 2002 | A1 |
| 20020178385 | Dent | Nov 2002 | A1 |
| 20020180582 | Nielsen | Dec 2002 | A1 |
| 20020180600 | Kirkland | Dec 2002 | A1 |
| 20020183008 | Menard | Dec 2002 | A1 |
| 20030016119 | Teich | Jan 2003 | A1 |
| 20030016139 | Teich | Jan 2003 | A1 |
| 20030018478 | Mays | Jan 2003 | A1 |
| 20030023881 | Fitzgibbon | Jan 2003 | A1 |
| 20030029579 | Mays | Feb 2003 | A1 |
| 20030043021 | Chung | Mar 2003 | A1 |
| 20030071590 | Roman | Apr 2003 | A1 |
| 20030097586 | Mok | May 2003 | A1 |
| 20030098778 | Taylor | May 2003 | A1 |
| 20030118187 | Fitzgibbon | Jun 2003 | A1 |
| 20030150164 | Mehalshick | Aug 2003 | A1 |
| 20030151493 | Straumann | Aug 2003 | A1 |
| 20030182132 | Niemoeller | Sep 2003 | A1 |
| 20030193388 | Ghabra | Oct 2003 | A1 |
| 20030216139 | Olson | Nov 2003 | A1 |
| 20030222754 | Cho | Dec 2003 | A1 |
| 20040012481 | Brusseaux | Jan 2004 | A1 |
| 20040012483 | Mays | Jan 2004 | A1 |
| 20040036573 | Fitzgibbon | Feb 2004 | A1 |
| 20040176107 | Chadha | Sep 2004 | A1 |
| 20040210327 | Robb | Oct 2004 | A1 |
| 20040212498 | Peterson | Oct 2004 | A1 |
| 20040229569 | Franz | Nov 2004 | A1 |
| 20040239482 | Fitzgibbon | Dec 2004 | A1 |
| 20040257189 | Chang | Dec 2004 | A1 |
| 20040257199 | Fitzgibbon | Dec 2004 | A1 |
| 20050012631 | Gregori | Jan 2005 | A1 |
| 20050030179 | Script | Feb 2005 | A1 |
| 20050033641 | Jha | Feb 2005 | A1 |
| 20050035873 | Kimura | Feb 2005 | A1 |
| 20050044906 | Spielman | Mar 2005 | A1 |
| 20050076242 | Breuer | Apr 2005 | A1 |
| 20050085248 | Ballay | Apr 2005 | A1 |
| 20050088281 | Rohrberg | Apr 2005 | A1 |
| 20050099299 | Tyroler | May 2005 | A1 |
| 20050110639 | Puzio | May 2005 | A1 |
| 20050113080 | Nishimura | May 2005 | A1 |
| 20050134426 | Mullet | Jun 2005 | A1 |
| 20050146417 | Sweatte | Jul 2005 | A1 |
| 20050170777 | Harwood | Aug 2005 | A1 |
| 20050174250 | Dierking | Aug 2005 | A1 |
| 20050195066 | Vandrunen | Sep 2005 | A1 |
| 20050206497 | Tsui | Sep 2005 | A1 |
| 20050242923 | Pearson | Nov 2005 | A1 |
| 20050245233 | Anderson | Nov 2005 | A1 |
| 20050258937 | Neuwirth | Nov 2005 | A1 |
| 20050272372 | Rodriguez | Dec 2005 | A1 |
| 20050273372 | Bowne | Dec 2005 | A1 |
| 20060038656 | Wilson | Feb 2006 | A1 |
| 20060056663 | Call | Mar 2006 | A1 |
| 20060077035 | Mamaloukas | Apr 2006 | A1 |
| 20060091998 | Fitzgibbon | May 2006 | A1 |
| 20060103503 | Rodriguez | May 2006 | A1 |
| 20060132284 | Murphy | Jun 2006 | A1 |
| 20060137261 | Maly | Jun 2006 | A1 |
| 20060145811 | Nantz | Jul 2006 | A1 |
| 20060147052 | Wikel | Jul 2006 | A1 |
| 20060153122 | Hinman | Jul 2006 | A1 |
| 20060158344 | Bambini | Jul 2006 | A1 |
| 20060164208 | Schaffzin | Jul 2006 | A1 |
| 20060170533 | Chioiu | Aug 2006 | A1 |
| 20060187034 | Styers | Aug 2006 | A1 |
| 20060214783 | Ratnakar | Sep 2006 | A1 |
| 20060220785 | Ferdman | Oct 2006 | A1 |
| 20060223518 | Haney | Oct 2006 | A1 |
| 20060261932 | Ando | Nov 2006 | A1 |
| 20060279399 | Chuey | Dec 2006 | A1 |
| 20060281008 | Mitani | Dec 2006 | A1 |
| 20070005605 | Hampton | Jan 2007 | A1 |
| 20070005806 | Fitzgibbon | Jan 2007 | A1 |
| 20070028339 | Carlson | Feb 2007 | A1 |
| 20070046428 | Mamaloukas | Mar 2007 | A1 |
| 20070058811 | Fitzgibbon | Mar 2007 | A1 |
| 20070116194 | Agapi | May 2007 | A1 |
| 20070146118 | Rodriguez | Jun 2007 | A1 |
| 20070159301 | Hirt | Jul 2007 | A1 |
| 20070171046 | Diem | Jul 2007 | A1 |
| 20070177740 | Nakajima | Aug 2007 | A1 |
| 20070183597 | Bellwood | Aug 2007 | A1 |
| 20070185597 | Bejean | Aug 2007 | A1 |
| 20070283339 | Hardman | Dec 2007 | A1 |
| 20070290792 | Tsuchimochi | Dec 2007 | A1 |
| 20080061926 | Strait | Mar 2008 | A1 |
| 20080092443 | Herman | Apr 2008 | A1 |
| 20080106370 | Perez | May 2008 | A1 |
| 20080108301 | Dorenbosch | May 2008 | A1 |
| 20080130791 | Fitzgibbon | Jun 2008 | A1 |
| 20080132220 | Fitzgibbon | Jun 2008 | A1 |
| 20080224886 | Rodriguez et al. | Sep 2008 | A1 |
| 20080303706 | Keller | Dec 2008 | A1 |
| 20090005080 | Forstall | Jan 2009 | A1 |
| 20090063293 | Mirrashidi | Mar 2009 | A1 |
| 20090064056 | Anderson | Mar 2009 | A1 |
| 20090102651 | Fitzgibbon | Apr 2009 | A1 |
| 20090160637 | Maeng | Jun 2009 | A1 |
| 20090273438 | Sultan | Nov 2009 | A1 |
| 20090302997 | Bronstein | Dec 2009 | A1 |
| 20090315751 | Bennie | Dec 2009 | A1 |
| 20100120450 | Herz | May 2010 | A1 |
| 20100141381 | Bliding | Jun 2010 | A1 |
| 20100141514 | Bell | Jun 2010 | A1 |
| 20100159846 | Witkowski | Jun 2010 | A1 |
| 20100242360 | Dyas | Sep 2010 | A1 |
| 20100242369 | Laird | Sep 2010 | A1 |
| 20100289661 | Styers | Nov 2010 | A1 |
| 20100297941 | Doan | Nov 2010 | A1 |
| 20100299517 | Jukic | Nov 2010 | A1 |
| 20110025456 | Bos | Feb 2011 | A1 |
| 20110032073 | Mullet | Feb 2011 | A1 |
| 20110055909 | Dowlatkhah | Mar 2011 | A1 |
| 20110084798 | Fitzgibbon | Apr 2011 | A1 |
| 20110109426 | Harel | May 2011 | A1 |
| 20110130134 | VanRysselberghe | Jun 2011 | A1 |
| 20110193700 | Fitzgibbon | Aug 2011 | A1 |
| 20110205013 | Karasek | Aug 2011 | A1 |
| 20110234367 | Murphy | Sep 2011 | A1 |
| 20110254685 | Karasek | Oct 2011 | A1 |
| 20110258076 | Muirbrook | Oct 2011 | A1 |
| 20110311052 | Myers | Dec 2011 | A1 |
| 20110316667 | Tran | Dec 2011 | A1 |
| 20120092125 | Farber | Apr 2012 | A1 |
| 20120098638 | Crawford | Apr 2012 | A1 |
| 20120188054 | Bongard | Jul 2012 | A1 |
| 20120249289 | Freese | Oct 2012 | A1 |
| 20120280783 | Gerhardt | Nov 2012 | A1 |
| 20120280789 | Gerhardt | Nov 2012 | A1 |
| 20120280790 | Gerhardt | Nov 2012 | A1 |
| 20130017812 | Foster | Jan 2013 | A1 |
| 20130057695 | Huisking | Mar 2013 | A1 |
| 20130060357 | Li | Mar 2013 | A1 |
| 20130060358 | Li | Mar 2013 | A1 |
| 20130086841 | Luper | Apr 2013 | A1 |
| 20130093563 | Adolfsson | Apr 2013 | A1 |
| 20130147600 | Murray | Jun 2013 | A1 |
| 20130151977 | Arteaga-King | Jun 2013 | A1 |
| 20130257589 | Mohiuddin | Oct 2013 | A1 |
| 20130290191 | Dischamp | Oct 2013 | A1 |
| 20130328663 | Ordaz | Dec 2013 | A1 |
| 20140021087 | Adler | Jan 2014 | A1 |
| 20140118111 | Saladin | May 2014 | A1 |
| 20140125499 | Cate | May 2014 | A1 |
| 20140184393 | Witkowski | Jul 2014 | A1 |
| 20140253285 | Menzel | Sep 2014 | A1 |
| 20140266573 | Sullivan | Sep 2014 | A1 |
| 20140365781 | Dmitrienko | Dec 2014 | A1 |
| 20150067792 | Benoit | Mar 2015 | A1 |
| 20150221147 | Daniel-Wayman | Aug 2015 | A1 |
| 20160010382 | Cate | Jan 2016 | A1 |
| 20170241189 | Fitzgibbon | Aug 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2013254889 | May 2014 | AU |
| 2831589 | May 2014 | CA |
| 19801119 | Sep 1999 | DE |
| 0422190 | Oct 1990 | EP |
| 846991 | Nov 1997 | EP |
| 0913979 | May 1999 | EP |
| 1151598 | Jun 2000 | EP |
| 1227027 | Jul 2002 | EP |
| 2989799 | Oct 2013 | FR |
| 2404765 | Feb 2005 | GB |
| 2002019548 | Jan 2002 | JP |
| 2004088774 | Mar 2004 | JP |
| 4864457 | Feb 2012 | JP |
| 2002032461 | May 2002 | KR |
| 9012411 | Oct 1990 | WO |
| 9515663 | Jun 1995 | WO |
| 9923614 | May 1999 | WO |
| 0036812 | Jun 2000 | WO |
| 0193220 | Dec 2001 | WO |
| 02075542 | Sep 2002 | WO |
| 2009088901 | Jul 2009 | WO |
| 2011055128 | May 2011 | WO |
| Entry |
|---|
| British Combined Search and Examination Report Under Section 17 and 18(3) from British Application No. GB0713690.6 dated Oct. 17, 2007. |
| British Search Report Under Section 17 dated Dec. 20, 2007 for Application No. GB0713690.6. |
| European Patent Application No. EP 1 280 109 A3; European Search Report dated Aug. 1, 2005. |
| International Search Report and Written Opinion for PCT/US2014/057405 dated Dec. 17, 2014. |
| James Y. Wilson and Jason A. Kronz; Inside Bluetooth Part II, Dr. Dobb's Portal; The World of Software Development; Dr. Dobb's Journal; Jul. 22, 2001; 9 pages. |
| Sensory, Inc. RSC-300/364 Data Book, Jan. 2001 (55 pages). |
| “Now You Can Close Your Garage Door With a Smartphone;” Copyright 2011 USA Today; http://content.usatoday.com/communities/driveon/post/2011/09/now-you-can-control-your-garage-door-from-your-smartphone. |
| 4Sight Internet Brochure; http://4sightsolution.4frontes.com/document/4CB-4S00-0809; Carrollton, TX; 2009; 5 pgs. |
| 4th Usenix; Windows Systems Symposium; Seattle, Washington USA; Aug. 3-4, 2000; A Toolkit for Building Dependable and Extensible Home Networking Applications; Yi-Min Wang, Wilf Russell and Anish Arora. |
| 6POWER, IPv6 and PLC for home automation; Terena 2004; Jordi Palet & Francisco Ortiz. |
| 828LM—LiftMaster Internet Gateway; http://www.liftmastercom/consumerweb/pages/accessoriesmodeldetaiLaspx? modelId=2407; printed Oct. 30, 2012. |
| ActieHome PC Home Automation System; http://www.x10.com/promotions/sw31a_activehome_hmp.html?WENTY11; accessed Sep. 2011. |
| Arrayent; White Paper: Six System Requirements for an Internet-Connected Product Line; Copyright 2010; http://arrayent.com/pdfs/SixSystemRequirementsforInternetConnectedProductsLine.pdf. |
| Authentication vs. Encryption; Be in Control with Control Networks; Feb. 10, 2004; http://www.buildings.com/DesktcpModulesIBB ArlicleMaxfArticleDeta I/BBArticleDetai lPrintaspx7ArlicleID=1740& Template=standm-d_Pri nt.ascx&sitelD= 1. |
| Automatic Garage Door Closer Manual—Protectrix 18A—Dated Mar. 31, 2009. |
| Big blue builds home network technology; McCune, Heather; http://search.proquest.com/docview/194229104?accountid=12492; Apr 2003. |
| Bill Peisel; “Designing the Next Step in Internet Applicances” Electronic Design/ Mar. 23, 1998. |
| Canadian Patent Application No. 2,533,795; Office Action dated Jan. 9, 2015. |
| Canadian Patent Application No. 2,533,795; Second Office Action dated Dec. 30, 2013. |
| Combined Search and Examination Report Cited in British Patent Application No. GB1025649.5 dated Aug. 8, 2012. |
| Controlling the Status Indicator Module of the Stanley Garage Door Opener Set; Rene Braeckman; Apr. 6, 2000. |
| Defendant's Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Mar. 17, 2015. |
| Defendant Invalidity Contentions regarding U.S. Pat. No. 6,998,977, Exhibit 16, Apr. 20, 2015. |
| Defendant Invalidity Contentions regarding U.S. Pat. No. 7,482,923, Exhibit 20, Apr. 20, 2015. |
| Defendant Invalidity Contentions regarding U.S. Pat. No. 7,852,212, Exhibit 18, Apr. 20, 2015. |
| Defendant Invalidity Contentions regarding U.S. Pat. No. 7,876,218, Exhibit 19, Apr. 20, 2015. |
| Defendant Invalidity Contentions regarding U.S. Pat. No. 8,144,011, Exhibit 17, Apr. 20, 2015. |
| Detroit Free Press Home Computing Column; Detroit Free; Newman, Heather; http ://search.proquest.com/docview/4632707 4 7?accountid=12492; Knight Ridder/Tribune Business News; © 2002, last updated Dec. 13, 2011. |
| Diomidis D. Spinellis; The information furnace: consolidated home control; Received: Jun. 1, 2002 / Accepted: Aug. 14, 2002; © Springer-Verlag London Limited 2003. |
| Doug Olenick; Motorola Broadens Home Automation Line; http ://search.proquest.com/docview/232255560?accountid=12492; vol. 20, © Jan. 6, 2005; last updated Sep. 1, 2011. |
| Examination Report from New Zealand Patent Application No. 599055 dated Apr. 3, 2012. |
| Examination Report Under Section 18(3) Cited in British Patent Application No. GB1205649.5 dated May 29, 2013. |
| Examination Report Under Section 18(3) for GB1205649.5 dated Feb. 12, 2014. |
| Examination Report Under Section 18(3) for GB1205649.5 dated Jun. 11, 2014. |
| EZSrve—Insteon/X10 Home Automation Gateway—Model #5010L; hap://www.simplehomenet.com/proddetail.asp?prod+9357342317, accessed Sep. 2011. |
| First Office Action dated Aug. 8, 2014 in related U.S. Appl. No. 13/671,602. |
| Fully-Loaded ActiveHome Pro PC Hom Automation System; http://www.x10.com/promotions/cm15a_loaded_ps.html ; accessed Sep. 2011. |
| George Lawton; “Dawn of the Internet Appliance” Computer, Industry Trends; Oct. 1, 1997. |
| Hassan A. Artail; “A Distributed System of Network-Enabled Microcontrollers for Controlling and Monitoring Home Devices” IEEE 2002. |
| Hawking Technologies HomeRemote Wireless Home Automation Gateway Pro Starter Kit; The HRGZ2 HomeRemote Gateway; Smart Home Systems, Inc.; http://www.smarthomeusa.com/ShopByManufacturer/Hawking-Technologies/Item/HRPS1/; Accessed Sep. 2011. |
| HomeRemote Wireless Home Automation Gateway—PracticallyNetworked.com; Review date Aug. 2007; http://222.practicallynetworked.com/review.asp?pid=690; Accessed Sep. 2011. |
| HomeSeer HS2—Home Automation Software; http://store.homeseer.com/store/HomeSeer-HS2-Home-Automation-Software-Download-P103.aspx; Accessed Sep. 2011. |
| How to Internet-Connect Your Low Cost Consumer Retail Embedded Design; How to Prototype an Internet Connect Product; Hershy Wanigasekara; Sep. 13, 2010; http://www.eetimes.com/design/embedded/4027637/Internet-Connect-your-low-cost-consumer-retail-embedded-design. |
| How to Internet-Connect Your Low Cost Consumer Retail Embedded Design; How to Prototype an Internet Connected Product; Hershy Wanigasekara; Sep. 13, 2010; http://www.eetimes.com/design/embedded/4027637/Internet-Connect-your-low-cost-consumer-retail-embedded-design. |
| How to Internet-Connect Your Low Cost Consumer Retail Embedded Design; Internet Connect Product Implementation Design Patterns; Hershy Wanigasekara; Sep. 13, 2010; http://www.eetimes.com/design/embedded/4027637/Internet-Connect-your-low-cost-consumer-retail-embedded-design. |
| Ian Bryant and Bill Rose; “Home Systems: Home Controls;” p. 1-322; © 2001 Parks Associates. |
| Infinias Mobile Credential App for Android DroidMill; Known and printed as early as Dec. 19, 2011; http://droidmill.com/infinias-mobile-credential-1364120.html. |
| Intelli-M eIDC32; Ethernet-Enabled Integrated Door Controller; www.infinias.com; Known and printed as early as Dec. 19, 2011. |
| International Conference on Sensors and Control Techniques (IeSC 2000); Desheng Jiang, Anbo Wang, Fume and Temperature Alarm and Intelligent Control System of the District for Fire-Proof, Jun. 19-21, 2000, Wuhan, China, vol. 4077. |
| Internet Connected Garage Door Opener; Open New Doors at Sears; http://www.sears.corri/shc/s/p_10153_12605_00930437000P?prdNo=I&blockNo=1&blockType=G1; printed Oct. 30, 2012. |
| K.K. Tan, Y.L. Lim and H.L. Goh; “Remote Adaptive Control and Monitoring” IEEE (c) 2002. |
| Kenmore Connect; http:/www.kenmore.com/shc/s/dap_10154_12604_DAP_Kenmore+Connect; 2010 Sears Brands, LLC. |
| Kurt Scherf, Michael Greeson and Tricia Parks; “Primary Perspectives: “E-Enabled” Home Security;” pp. 1-87; © 2003 Parks Associates. |
| LiftMaster; MyQ Enabled Accessory: LiftMaster Internet Gateway (Model 828); Known as of Dec. 19, 2011. |
| Liftmaster Debuts New Intelligence in Garage Door Openers at IDS 2011; New Generation of LiftMaster Models and Accessories Enabled by MyQ Technology; Elmhurst, IL; Jun. 7, 2011; http://www.liftmaster.com/NR/rdonlyres/0A903511-21AB-4F0A-BBCD-196D41503CF2/4305/LiftMasterUneilsMyQTechnologyIDA2011_Final.pdf. |
| LiftMaster Internet Gateway: Your Simple Solution to Home Control; http://www.liftmaster.com/consumerweb/products/IntroducingLiftMasterInternetGateway, printed Oct. 30, 2012. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit A; U.S. Pat. No. 6,998,977; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit B; U.S. Pat. No. 7,852,212; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit C; U.S. Pat. No. 8,144,011; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit D; U.S. Pat. No. 7,876,218; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit E; U.S. Pat. No. 7,482,923; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit F; U.S. Pat. No. 7,071,850; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit G; Dictionary of Computer and Internet Terms; Douglas Downing; Michael A. Covington and Melody Mauidin Covington; Barrons; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Exhibit G; Dictionary of Computer and Internet Terms; Douglas Downing; Michael A. Covington and Melody Mauldin Covington; Barrons; Mar. 17, 2015. |
| Memorandum in Support of Defendant\s Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; NDIL Case 14-cv-05197; Mar. 17, 2015. |
| MiCasa Verde.com—Vers2; http://www.micasaverde.com/vera.php; Accessed Sep. 2011. |
| Miele's Remote Vision Explained; http://www.miclensa.com/service/remote_vision/verify.aspx; Accessed Feb. 2012. |
| Net2 User Manual; Version 3; Paxton Access; “Date code: 281002”. |
| New Zealand Application No. 706180; First Examination Report dated Apr. 10, 2015. |
| Nortek Security & Control LLC's Notice of Supplemental Authority Relevant to Defendant's Motion to Dismiss Second Amended Complaint Due to Patent Invalidity Under 35 U.S.C. § 101; Chamberlain vs. Linear LLC and Nortek Security & Control LLC; Case No. 1:14-cv-05197; 3 pages, Dated Apr. 29, 2015. |
| Office Action dated May 19, 2013 in U.S. Appl. No. 14/010,143. |
| Opposition to Defendant's Motion to Dismiss Second Amended Complaint Due to Alleged Patent Invalidity Under 35 U.S.C. 101; Chamberlain vs. Linear LLC and Nortek Security & Control LLC; Case No. 1:14-cv-05197; 28 pages; Dated Apr. 7, 2015. |
| Peter M. Corcoran and Joe Desbonnet; “Browser-Style Interfaces to a Home Automation Network” Manuscript received Jun. 18, 1997, IEEE (c) 1997. |
| Plaintiff Chamberlain Group, Inc.'s Response to Defendant Nortek Security Control LLC's Notice of Supplemental Authority Relevant to Defendant's Motion to Disucss Second Amended Complaint Due to [Alleged] Patent Invalidity Under 35 U.S.C. § 101; Chamberlain vs. Linear LLC and Nortek Security & Control LLC; Case No. 1:14-cv-05197; 10 pages; Dated May 12, 2015. |
| Press Release; Kenmore Uneils Reolutionary Technology Enabling Laundry Applicances to ‘Talk’ to Customer Serice Experts; PR Newswire, pNA, Aug. 4, 2010. |
| Protectrix Wireless automatic Garage Door Closer Timer Opener Security Accessory; http://www.closethegarage.com; printed Oct. 30, 2012. |
| Reply in Support of Defendant's Motion to Dismiss Second Amended Complaint due to Patent Invalidity Under 35 U.S.C. § 101; Chamberlain vs. Linear LLC and Nortek Security & Control LLC; Case No. 1:14-cv-05197; 21 pages; Dated Apr. 21, 2015. |
| Search History; C:\APPS\EAST\workspaces\garage_door_status_indicator.wsp; p. 4, Apr. 25, 2005. |
| Secure Smart Homes using⋅ Jini and UIUC SESAME; Jalal Al-Muhtadi et al.; 1063-9527/00 © 2000 IEEE. |
| Security System Installation Manual; Caretaker and Custom Versions; Interactive Technologies, Inc.; Issue Date May 5, 1994. |
| Security System Installation Manual; Caretaker and Custom Versions; Interactive Technologies, Inc.; Text No. 46-908-01 Rev. A; 1995. |
| Smart Networks for Control; Reza S. Raji;IEEE Spectrum Jun. 1994. |
| Somfy's Slick Tahoma Z-Wire and RTS Home Automatation Gateway; Thomas Ricker; posted Janaury 4, 2011; http://www.engadget.com/2011/01/04/softys-tahoma-z-wave-and-rts-home-automation-gateway/. |
| Stephen Shankland; “Need to lend your key? E-Mail it, Frauhofer says” news.cnet.com/8301-1035_3-57572338-94/need-to-lend-your-key-e-mail-it-fraunhofer-says/; pp. 1-5; CNET News, Mar. 4, 2013. |
| Summary of Findings From Parks Associates\ Early Reports; pp. 9-13; Apr. 15, 2013 by Parks Associates. |
| Susan Cotterell, Frank Vahid, Walid Najjar, and Harry Hsieh; “First Results with eBlocks: Embedded Systems Building Blocks” University of California, Rkverside pp. 168-175; Codes+ISSS'03, Oct. 1-3, 2003. |
| Svein Anders Tunheim; Wireless Home Automation Systems Require Low Cost and Low Power RF-IC Solutions; Wireless Home Automation Systems (rev. 1.0) May 16, 2002; p. 1 of 8. |
| The Craftsman Brant Announces Garage Door Opener of the Future—PR Newswire; The Sacramento Bee; http://www.sac bee.com/2011/09/27/2941742/the-craftsman-brand-announces.html; Sep. 27, 2011. |
| The iDorm—a Practical Deployment of Grid Technology; Anthony Pounds-Cornish, Arran Holmes; Intelligent Interactive Environments Group, University of Essex, UK; Proceedings of the 2nd IEEE/ACM International Symposium on Cluster Computing and the Grid (CCGRIO'02) 0/7695-1582-7/02 © 2002 IEEE. |
| The Information Furnace: Consolidated Home Control; Diomidis D. SpinellisDepartment Management Science and Technology Athens University of Economics and Business; Personal and Ubiquitous Computing archive; vol. 7 Issue 1, May 2003. |
| The Information Furnace: User-friendly Home Control; Diomidis D. Spinellis, Department Management Science and Technology, Athens University of Economics and Business; SANE 2002; 3rd Intl Sys. Admin. and Networking Conf. Proc., pp. 145-175, May 2002. |
| The Intelli-M eIDC32; True IP Access Control; htto://www.infinias.com/main/Products/eIDCController.aspx; Known and printed as early as Dec. 19, 2011. |
| Towards Dependable Home Networking: An Experience Report; Yi-Min Wang, Wilf Russell, Anish Arora, JunXu, Rajesh K. Jagannathan, Apr. 18, 2000, Technical Report, MSR-TR-2000-26, Microsoft Research, Microsoft Corporation. |
| U.S. Office Action dated Aug. 8, 2014 from U.S. Appl. No. 13/671,602. |
| U.S. Office Action dated Sep. 24, 2014 from U.S. Appl. No. 12/971,374. |
| U.S. Office Action dated Sep. 24, 2014 in U.S. Appl. No. 13/921,584. |
| ULStandard for Safety for Door, Drapery, Gate, Louver, and Window Operators and Systems, UL 325 Fifth Edition, Dated Jun. 7, 2002; pp. 1-186. |
| U.S. Office Action dated Sep. 18, 2014 from U.S. Appl. No. 14/010,143. |
| Universal Devices—ISY-99i Series; http://www.universal-devices.com/99i.htm; Accessed Sep. 2011. |
| Wayne-Dalton Press Area—New Z-Wave enabled prodrive; http://www.wayne-dalton.com/newsitem98.asp; Printed Oct. 13, 2011. |
| Wireless Media Innovations LLC v. Maherterminals LLC (2015 WL 1810378 (D.N.J.) Apr. 20, 2015) Submitted as Document #60 in Chamberlain vs. Linear LLC and Nortek Security & Control LLC; Case No. 1:14-cv-05197, 11 Pages; Apr. 29, 2015. |
| www.brinkshomesecurity.com/home-security-systems-and-pricing/security-equipment/security-equipment.htm as printed on Feb. 11, 2009. |
| Xanboo Future Product; http://www.xanboo.com/xanproducts/newproducts.htm Feb. 2002, Xanboo Inc. |
| Xanboo XPC280 Wireless Universal Garage Door Control—Smarthome; http://www.smarthome.comf75066/Xanboo-XPC280-Wireless-Universal-Garage-Door-Control/p.aspx, printed Oct. 30, 2012. |
| XPress Access; Simple Personal Management; © 2001 Andover Controls Corporation BR-XPACCESS-A. |
| Bluetooth Special Interest Group; “Advertising URIs” New Work Proposal dated May 13, 2014; 8 pages. |
| Australian Patent Application No. 2013254889; Examination Report No. 1; dated Jan. 13, 2017, 5 pages. |
| Australian Patent Application No. 2017261560; Examination Report No. 1; dated Jun. 14, 2018, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150221147 A1 | Aug 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14525924 | Oct 2014 | US |
| Child | 14686047 | US |
