SYSTEM AND METHOD FOR MONITORING AN ACCESS KEY FROM A KEY BOX

Abstract

Disclosed is a system for monitoring a location of a key relative to a keybox, configured to perform: (i) providing access to the key by: communicating over a personal area network with a first mobile-device for the first user as the first user approaches the keybox in an attempt to obtain the key, obtaining first credentials from the first mobile-device, determining whether the first credentials are valid or invalid, when the first credentials are valid: putting the keybox in an unlocked configuration, (ii) tracking a location of the key by: communicating over the personal area network with: the key and/or mobile-device to determine whether the key is being returned to the keybox, wherein upon a determination by the keybox or the mobile-device that the key is not being returned, an alert is provided by the mobile-device to the first user.

Claims

1. A method of determining a location of a key, comprising: a mobile-device receiving a request to locate the key; the mobile-device communicating mobile-device key location request data, including a request for the location of the key, over a wireless network with a central server; and the mobile-device receiving from the central server, key positioning data, identifying the location of the key.

2. The method of claim 1, including: the mobile-device displaying, on its screen, keybox positioning information defining a last known position of a keybox that houses the key.

3. The method of claim 1, including: the central server transmitting central server location request data over the wireless network to other mobile-devices operationally associated with the central server, wherein the central server location request data includes a request for location information and identifying information of keys respectively found by the other mobile devices, whereby the central server discriminates between received messages to locate the key.

4. The method of claim 3, including the central server: monitoring for a response for a predetermined period of time; receiving key location reply data, including the key positioning data, from one of the other mobile-devices, within the predetermined period of time; and transmitting central server reply data, including the key positioning data, to the mobile-device.

5. The method of claim 4, wherein: the central server reply data includes a map link to find the key; or the mobile device displays a map that includes the location of the key based on the data returned from the central server.

6. A system for determining a location of a key, comprising a mobile-device in communication with a central server over a wireless network, the mobile-device being configured to: receive a request to locate a key; communicate mobile-device key location request data, including a request for the location of the key, over the wireless network with the central server; and receive from the central server, key positioning data, identifying the location of the key.

7. The system of claim 6, wherein: the mobile-device is configured to display, on its screen, keybox positioning information defining a last known position of a keybox that houses the key.

8. The system of claim 6, wherein: the central server is configured to transmit central server location request data over the wireless network to other mobile-devices operationally associated with the central server, wherein the central server location request data includes a request for location information and identifying information of keys respectively found by the other mobile devices, whereby the central server discriminates between received messages to locate the key.

9. The system of claim 8, wherein the central server is configured to: monitor for a response for a predetermined period of time; receive key location reply data, including the key positioning data, from one of the other mobile-devices, within the predetermined period of time; and transmit central server reply data, including the key positioning data, to the mobile-device.

10. The system of claim 9, wherein: the central server reply data includes a map link to find the key; or the mobile device displays a map that includes the location of the key based on the data returned from the central server.

11. A method of determining a location of a keybox, comprising: a mobile-device receiving a request to locate the keybox; the mobile-device communicating mobile-device keybox location request data, including a request for the location of the keybox, over a wireless network with the central server; and the mobile-device receiving from the central server, keybox positioning data, identifying the location of the keybox.

12. The method of claim 11, including: the mobile-device displaying, on its screen, keybox positioning information defining a last known position of the keybox that houses the key.

13. The method of claim 11, including: the central server transmitting central server location request data over the wireless network to other mobile-devices operationally associated with the central server, wherein the central server location request data includes a request for location information with identifying information of keyboxes respectively found by the other mobile devices, whereby the central server discriminates between received messages to locate the keybox.

14. The method of claim 13, including the central server: monitoring for a response for a predetermined period of time; receiving keybox location reply data, including keybox positioning data, from one of the other mobile-devices, within the predetermined period of time; and transmitting central server reply data, including the keybox positioning data, to the mobile-device.

15. The method of claim 14, wherein: the central server reply data includes a map link to find the keybox; or the mobile device displays a map that includes the location of the keybox based on the data returned from the central server.

16. A system for determining a location of a keybox, comprising a mobile-device in communication with a central server over a wireless network, the mobile-device being configured to: receive a request to locate the keybox; communicate mobile-device keybox location request data, including a request for the location of the keybox, over the wireless network with the central server; and receive from the central server, keybox positioning data, identifying the location of the keybox.

17. The system of claim 16, wherein: the mobile-device is configured to display, on its screen, keybox positioning information defining a last known position of the keybox that houses the key.

18. The system of claim 16, wherein: the central server is configured to transmit central server location request data over the wireless network to other mobile-devices operationally associated with the central server, wherein the central server location request data includes a request for location information with identifying information of keyboxes respectively found by the other mobile devices, whereby the central server discriminates between received messages to locate the keybox.

19. The system of claim 18, wherein the central server is configured to: monitoring for a response for a predetermined period of time; receiving keybox location reply data, including the keybox positioning data, from one of the other mobile-devices, within the predetermined period of time; and transmitting central server reply data, including the keybox positioning data, to the mobile-device.

20. The system of claim 19, wherein: the central server reply data includes a map link to find the keybox; or the mobile device displays a map that includes the location of the keybox based on the data returned from the central server.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:

[0018] FIG. 1 illustrates features of an embodiment of the disclosure;

[0019] FIG. 2 illustrates features of an embodiment of the disclosure;

[0020] FIG. 3 illustrates a process according to embodiment of the disclosure;

[0021] FIG. 4 illustrates a process according to an embodiment of the disclosure;

[0022] FIG. 5 illustrates a process according to an embodiment of the disclosure;

[0023] FIGS. 6 and 6A illustrate a process according to an embodiment of the disclosure;

[0024] FIG. 7 illustrates a process according to an embodiment of the disclosure;

[0025] FIG. 8 is a block diagram showing a method of finding a key with a mobile-device according to an embodiment; and

[0026] FIG. 9 is a block diagram showing a method of method of finding a keybox with a mobile-device according to an embodiment.

DETAILED DESCRIPTION

[0027] A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.

[0028] FIGS. 1 and 2 illustrate environments in which the disclosed embodiments may be practiced. A user in the embodiments may be real estate agent 100 who may intend to access an available property 104 to display to a customer, that is, a potential buyer 108. A keybox 112 may be disposed proximate the property in which an access key 116 is maintained. The keybox may include an electronic controller 118 to control electro-mechanical functions of the keybox and to provide the keybox with telecommunication capabilities. Access to the key may be through a key container 120 in the keybox. The key container may be capable of being secured in an opened state by electro-mechanical control from the controller, during which time a key 116 may be removed and replaced in the keybox. In a locked or closed state the key 116 in the key container 120 may be locked within the keybox 112.

[0029] The keybox may be a first smart device that may communicate over a personal area network (PAN) 122 with a mobile-device 124, which may be a mobile phone that may be a second smart device and which may be in possession of the agent 100. PAN protocols may include, for example, NFC (near field communication), BlueTooth Low Energy (BLTE) or ZIGBEE. The mobile-device 124 may be equipped with an App 128, available from an App Store, providing program level communications between the keybox 112 and the mobile-device 124. The agent 100 may interact with the App 128 via a screen 130 on the mobile-device 124. In addition, using the APP 128, the mobile-device 124 may communicate over the Internet 132 with a central server 136. Moreover, the mobile-device may use a cellular network 140 for access to the Internet or the mobile-device may access the Internet by, for example, a connection over Wi-Fi 144 (trademark of the Wi-Fi Alliance).

[0030] Referring to FIG. 3, at step S50 the controller 118 may monitor a location of the access key 116. Under this step, the controller may perform a first step S54 of providing access to the key 116 within the keybox 112 while the keybox 112 is in the locked configuration, which is illustrated in greater detail in FIGS. 1 and 4. The controller may also perform a second step S58 of tracking a proximate, or near field, location of the key 116 to determine if the key is being returned to the keybox 112 by the agent, which is discussed in greater detail in FIGS. 1 and 5. The controller may also perform a third step S62 of tracking a distal, or far field, location of the key 116 relative to the keybox to prevent the agent 100 from potentially leaving with the key, which is illustrated in greater detail in FIGS. 2 and 6. The controller may also perform a fourth step S66 of tracking a duration the keybox is opened to identify if the key 116 is potentially lost by the agent, which is illustrated in greater detail in FIGS. 2 and 7.

[0031] Referring to FIGS. 1 and 4, as indicated, at step S54 the controller may execute the first step of providing access to the key 116 within the keybox 112 while the keybox 112 is in the locked configuration. Initially the key 116 may be in the keybox 112, the keybox 112 may be in a closed state. At step S104 the keybox controller 118 may communicate with the mobile-device 124 of the agent (using the App 128) when the agent seeks to obtain the access key 116. These communications occur, for example, using BTLE. At step S108 the controller 118 may obtain credentials from the mobile-device 124 which may represent the agent 100 credentials for accessing the key.

[0032] At step S112 the controller 118 may determine whether the credentials are valid. If the credentials are not valid then at step S116 the controller may not grant access to the key 116 by, for example, not unlocking the keybox 112. If the credentials are valid then at step S120 the controller 118 may record a first audit log entry in an audit log stored on the controller 118, where the first entry may include the credentials or at least an identifier of the agent 100 and may indicate that access to the key 116 is being provided. At step S124 the controller 118 using electromechanical controls may configure the keybox 112 to the unlocked or opened state to provide access to the key container 120 and hence the key 116. At step S126 the controller may secure the keybox in the unlocked state.

[0033] Referring to FIGS. 1 and 5, as indicated, at step S58 the controller may execute the second step of tracking a proximate, or near field, location of the key 116 to determine if the key is being returned to the keybox 112 by the agent 100. After showing the property to the customer 108, at step S128 the controller 118 may again communicate with the mobile-device 124 of the agent 100 as the agent attempts to return or replace the key 116. At step S132 the controller may instruct the mobile-device 124 to interactively engage the agent to determine whether the key 116 has been replaced in the keybox. For example the mobile-device may provide a visual query on the screen 130, responsive to which the mobile-device may receive a YES or NO using respective first and second radio buttons 150, 154.

[0034] At step S136 the controller 118 may receive data from the mobile-device 124 indicative of the response from the agent 100. At step S140 the controller 118 may record a second audit log entry indicator of the response of the agent 100. At step S144 the controller may transfer the audit log data to the mobile-device 124, which may transfer the audit data to the central server 136. The audit data may serve as a digital check to ensure that the agent 100 left the key 116 in the keybox. At step S148 the controller may determine whether the response from the agent indicated that the key 116 was being replaced in the box.

[0035] If the response was YES then at step S152 the controller may enable closing of the keybox by the agent, for example, by releasing the keybox from the unlocked state and allowing the key container 120 to latch into the keybox 112. If the response was NO then at step S156 the controller may again communicate with the mobile-device and cause the mobile-device to interactively engage the agent with an alert indicating that the key must be replaced.

[0036] On one embodiment, in addition to or instead of asking the agent at step S132 and S136 whether the key is being returned, the keybox 112 may directly detect whether the key 116 is being returned. For example, the key 116 could have a Bluetooth chip 115 on a key ring 117 (FIG. 1) that advertises periodically. Based on proximity, for example, whether the key 116 is inside the keybox 112, outside the keybox 112 but close in proximity to the keybox 112, or relatively far away from the keybox 112, the keybox 112 may determine whether and which key 116 is in the keybox 112. If other keys have similar technology implements, the keybox 112 could determine when a key belonging in another keybox is accidently placed in the keybox 112. When a key belonging in a different keybox is placed in the keybox 112, an alert may be sent to the agent which requests that the agent confirm the correct keys are being positioned in the keybox.

[0037] Alternatively, the key 116 could have a radio frequency identification (RFID) chip that may be on the same board as the Bluetooth chip 115 and that may be read by an RFID reader upon insertion of the key 116 into the keybox 112. The RFID reader may be part of the controller 118 within the keybox 112. Yet alternatively the key could have a chemical signature, a visual identifier (barcode, QR code, etc. that is scanned by the box when it is returned). Moreover, the sensor in the keybox could be a mechanical tamper spring, or a magnetic sensor such as a magnetic reed proximity switch. In one embodiment the presence or absence of the key container 120 can be determined by the keybox 112 to determine if the key 116 is present or absent respectively.

[0038] In one embodiment the keybox 112 determines at any time from one or more above disclosed features and/or steps that the key 116 has been returned. In such an instance, procedures disclosed herein which may subsequently create an alert may be aborted. This may avoid the controller 118 or mobile-device 124 from creating undue alerts.

[0039] Turning to FIGS. 1, 3 and 6, and as indicated, at step S62 the controller may execute a third step of tracking a distal, or far field, location of the key 116 relative to the keybox 112 to prevent the agent from potentially leaving with the key. At step S200 the controller 118 may periodically communicate 204 (FIG. 2) with the mobile-device 124 to determine a proximity 208 of the mobile-device to the keybox. At step S204 the controller may determine whether the mobile-device has moved beyond a predetermined distance threshold while the keybox is in the opened state. While the determination at step S204 is NO the controller may keep monitoring proximity to the mobile-device. If the determination is YES at step S204, then at step S206 the controller may cause the mobile-device to interactively communicate with the agent. This interaction may be in the form of an alert which may be a visual, audible and/or vibratory alert. The controller may then perform step S208 of determining whether the mobile-device has returned to a position that is within the threshold distance. So long as the determination at 5208 is NO the alert may stay active on the mobile-device of the agent. If the determination is YES then at step S212 the controller may cause the mobile-device to turn off the alert.

[0040] In one embodiment, the key 116 may be equipped with BTLE communication implements 115 as indicated above. In addition to or as an alternate to the features and steps performed in FIG. 6, tracking of proximity of the key 116 may be performed by communications between the keybox 112 and the key 116. Such tracking may be based on periodic BTLE advertisements from the key 116. The lock controller 118 may track the distance to the key 116 as compared with tracking the distance to the mobile-device 124. Alternatively, the mobile-device 124 may determine when it is proximate the key 116 using periodic BTLE advertisements from the key 116. If the key 116 is not in the keybox 112 and the key 116 is not proximate the mobile-device 124, the mobile-device 124, may be disposed to provide the agent with an alert to indicate that the key 116 has been left in an unsecure location. A determination to provide the alert, in this embodiment and in each embodiment provided herein, may be based on instructions from the controller or may be automatically created based on protocols in the App 128 on the mobile-device.

[0041] In one embodiment illustrated in FIG. 6A, in addition to or as an alternative of the features and steps disclosed under step S62 in FIG. 6, the mobile-device 124 may perform step S62A in FIG. 6A to determine whether the key 116 is accidentally being removed from the property by the agent 100. At step S200A the mobile-device 124 may listen to a BLTE advertisements from the keybox BTLE transceiver 118 so that the mobile-device may determine a distance to the keybox 112. As long as the mobile-device 124 is within a predetermined range of the keybox 112, and the mobile-device 124 receives the BTLE advertisement from the keybox 112, and the determination is yes at step S204A. As a result, no alert may be created by the mobile-device 124.

[0042] When the agent with the mobile-device 124 moves outside the range, the determination is no at step S204A. At step S205A, a timer may be triggered on the mobile-device 124 for allowing the agent to return within range. When the timer elapses, or if the agent leaves a geofence range around the keybox 112 or property 104, at step S206A the mobile-device 124 may remind the agent with an alert to return to the keybox 112 and return the key 116. If the keybox 112 advertisement indicates the key 116 has been returned or if the agent returns to the threshold zone at step S208A, then the mobile-device 124 may abort this reminder procedure at step S212A.

[0043] It is to be appreciated that in such embodiment the APP 128 on the mobile-device 124 may autonomously monitor a distance from itself to the keybox 112. In addition, then the mobile-device 124 may autonomously alert the agent if the agent has been out of range for too long or if the mobile-device 124 has moved too far away. That is, the mobile-device 124 may not need instructions from the keybox 112 in order to create an alert for the agent.

[0044] Referring to FIGS. 2 and 7, as indicated, at step S66 the controller may execute a fourth step of tracking a duration the keybox is opened to identify if the key is potentially lost by the agent. At step S250 the controller may monitor the duration of time, illustrated schematically as an hour glass 212, that the keybox has been in the opened state. At step S254 the controller may determine whether the duration is greater than a predetermined threshold. While the determination is NO at step S254, the controller may continue to track the duration of time the keybox is opened. If the determination becomes YES then at step S258 the controller may record a third audit log entry indicating that the keybox has been opened for a duration that is greater than the predetermined threshold, indicating the key may be lost by the agent.

[0045] At step S262 the controller may communicate with a second mobile-device for a second agent seeking to obtain the key from the keybox. At step S266 the controller may obtain second credentials from the second agent and at step S270 the controller may determine whether the second credentials are valid. If the determination is YES then at step S274 the controller may transfer the audit log to the second mobile-device for transferring to the audit log to the central server. If the determination is NO then the controller may wait to communicate with another mobile-device for another agent and cycle back to step S262.

[0046] The above disclosed embodiments may prompt the agent with a message such as an alert to determine whether a key is inside a keybox before the keybox is closed as the agent leaves the property. The disclosed embodiments may electronically transmit a message, an auditory, vibratory or other typical alert to the agent via the mobile-device for the agent, indicating whether the key is in the keybox. The disclosed embodiments may ensure that the key is replaced in the keybox. In addition, creation of the audit logs may enable tracking of the location of the key and who last used the key.

[0047] In addition to the above, FIG. 8 shows a block diagram illustrating a method of finding the key 116, by the agent 100, with the mobile-device 124. As shown in block 810, the method includes the mobile-device 124 receiving a request to locate the key 116.

[0048] The request may come from the agent 100 directly engaging the App 128 via the mobile-device 124. The agent 100 may only know the identity of the key 116 by inference: the key 116 is attached to a processor or chip 115 in a tag 117 that has a unique identifier (id) that is associated with a street address, an agent, and a keybox 112, for example. The request can specify the street address, for example, and by inference there can be a determination as to which key 116 is being requested also potentially which keybox 112 it is associated with/inside of, and what property/real estate listing this key 116 is for example.

[0049] As shown in block 820, the method includes the mobile-device 124 displaying, on its screen 130, keybox positioning information defining a last known position (e.g., GPS coordinates) of the key 116 or its keybox 112 That is, the last known position may be of the key 116 or the keybox 112 as both the key and the keybox are advertising a Bluetooth signal as indicated above. The key 116 and keybox 112 can be tracked independently of each other, though in association with each other. For example, if it is known that the key 116 is in the keybox 112, and if a location of the keybox 112 is known, then the location of the key 116 may be inferred. Alternatively, the key 116 and keybox 112 can be tracked separately. For example, if the last known location of the key 116 is known as determined by another mobile-device (using that other mobile-device's GPS at the same time that the other mobile-device received the last Bluetooth signal from the chip attached to the key 116), this last known location could be communicated to the mobile device 124 from the other mobile device or from the central server 136 prior to the request in step 810 or even as part of step 820 to display the last known position.

[0050] As shown in block 830, the method includes the mobile-device 124 communicating mobile-device key location request data, including a request for a location of the key 116, over a wireless network 140 with the central server 136. Other networks identified herein may be utilize for this communication.

[0051] For example, the mobile app is being used by a Real Estate agent. In the app is a list of listings (homes for sale) that the agent is managing. For each listing there is a keybox 112 and a housekey 116. The agent can select the key 116, or the keybox 112, via the mobile app and ask where is it. The app may have a location already based on the agent's own activity (i.e. the agent was recently near a keybox 112 or key 116). This location can be displayed, e.g. by indicating the key 116 and/or keybox 112 was at an identified location at an identified date/time.

[0052] The agent can select an option to ask the server (step 830) to identify who else has seen the key 116. The server can respond with any known location data from others. The agent can see data that identifies the last date/time that others were able to locate the key. The agent can then select to request to find the key at that time, e.g., dynamically. This is a request to the server that is transmitted to all the other agents' mobile-devices to search for the key 116. If the key 116 is found by any one of the respective other mobile-devices, a signal is returned to the server 136 by that other mobile-device, identifying that the specific key 116 is found. The server then sends a message back to the requesting agent's mobile-device 124, e.g., indicating that the key 116 is found at that time by another agent, via the other agent's mobile-device. Otherwise, after waiting a predetermined period of time, the server transmits to the agent's mobile-device 124 that the location of the key 116 is not yet known.

[0053] Thus, as shown in block 840, the method includes the central server 136 transmitting central server location request data over a wireless network 140 to the mobile-devices operationally associated with it, e.g., due to having the app uploaded to it. Any of the networks identified herein may be used for this communication. The mobile-devices will scan for Bluetooth advertisements from the key 116. If the mobile-devices find keys, then they respond back to the server with their current location and the specific keys they respectively identified.

[0054] As shown in block 850, the method includes the central server 136 monitoring for a response from the mobile devices for a predetermined period of time. That is, the central server 136 is monitoring for responses coming back from the mobile-devices with information about the specific keys they have individually found. In one embodiment, the predetermined period of time is 5 minutes.

[0055] As shown in block 860, the method includes the central server 136 receiving key location reply data, including key positioning data, from the mobile-device, within the predetermined period of time. In one embodiment the key positioning data is global positioning data.

[0056] As shown in block 870, the method includes the central server 136 transmitting central server reply data, including the key positioning data, to the mobile-device 124. In one embodiment, the central server reply data includes a map link to find the key 116. Alternatively, the mobile-device 124 displays a map that includes the location of the key 116 based on the data returned from the central server 136.

[0057] With the above embodiments, an agent is looking for potentially misplaced housekeys used during, e.g., multiple showings of a property, would be able to locate the housekeys by means of the mobile APP 128.

[0058] In addition to the above, FIG. 9 shows a block diagram illustrating a method of finding the keybox 112 that houses the key 116, by the agent 100, with the mobile-device 124. As shown in block 910, the method includes the mobile-device 124 receiving a request to locate the keybox 112.

[0059] The request may come from the agent 100 directly engaging the App 128 via the mobile-device 124. The agent 100 may only know the identity of the keybox 112 by inference: the key 116, normally stored in the keybox 112, is attached to a processor or chip 115 in a tag 117 that has a unique identifier (id) that is associated with a street address, an agent, and the keybox 112, for example. The request can specify the street address, for example, and by inference there can be a determination as to which keybox 112 is being requested also potentially which key 116 it is associated with/carrying, and what property/real estate listing this keybox 112 is for, example.

[0060] As shown in block 920, the method includes the mobile-device 124 displaying, on its screen 130, keybox positioning information defining a last known position (e.g., GPS coordinates) of the keybox 112 that houses the key 116, or the key 116. That is, the last known position may be of the key 116 or the keybox 112 as both the key and the keybox are advertising a Bluetooth signal as indicated above. The key 116 and keybox 112 can be tracked independently of each other, though in association with each other. For example, if it is known that the key 116 is in the keybox 112, and if a location of the key 116 is known, then the location of the keybox 112 may be inferred. Alternatively, the key 116 and keybox 112 can be tracked separately. For example, if the last known location of the keybox 112 is known, as determined by another mobile-device (using that other mobile-device's GPS at the same time that the other mobile-device received the last Bluetooth signal from the key 112), this last known location could be communicated to the mobile device 124 from the other mobile device or from the central server 136 prior to the request in step 810 or even as part of step 820 to display the last known position.

[0061] As shown in block 930, the method includes the mobile-device 124 communicating mobile-device keybox location request data, including a request for the location of the keybox 112, over a wireless network 140 with the central server 136. Any of the networks identified herein may be utilize for this communication.

[0062] For example, the mobile app is being used by a Real Estate agent. In the app is a list of listings (homes for sale) that the agent is managing. For each listing there is a keybox 112 and a housekey 116. The agent can select the key 116, or the keybox 112, via the mobile app and ask where is it. The app may have a location already based on the agent's own activity (i.e. the agent was recently near a keybox 112 or key 116). This location can be displayed, e.g. by indicating the key 116 and/or keybox 112 was at an identified location at an identified date/time.

[0063] The agent can select an option to ask the server (step 930) to identify who else has seen the keybox 112. The server can respond with any known location data from others. The agent can see data that identifies the last date/time that others were able to locate the keybox 112. The agent can then select to request to find the keybox 112 at that time, e.g., dynamically. This is a request to the server that is transmitted to all the other agents' mobile-devices to search for the keybox 112. If the keybox 112 is found by any of the respective other mobile-devices, a signal is returned to the server from that other mobile-device, identifying that the specific keybox 112 is found. The server then sends a message back to the requesting agent's mobile-device, e.g., indicating that the keybox 112 is found at that time by another agent, via the other agent's mobile-device. Otherwise, after waiting a predetermined period of time, the server transmits to the agent's mobile-device that the location of the keybox 112 is not yet known.

[0064] Thus, as shown in block 940, the method includes the central server 136 transmitting central server location request data over a wireless network 140 to the mobile-devices associated with it, e.g., due to having the app uploaded to it. The mobile-devices will scan for Bluetooth advertisements from the keybox 112. If the mobile-devices find keyboxes, then they respond back to the server with their current location and the specific keyboxes they respectively identified.

[0065] As shown in block 950, the method includes the central server 136 monitoring for a response from the mobile devices for a predetermined period of time. In one embodiment, the predetermined period of time is 5 minutes. That is, the central server 136 is monitoring for responses coming back from the mobile-devices with information about the specific keyboxes they have individually found.

[0066] As shown in block 960, the method includes the central server 136 receiving keybox location reply data, including keybox positioning data, from the mobile-devices, within the predetermined period of time. In one embodiment the keybox positioning data is global positioning data.

[0067] As shown in block 970, the method includes the central server 136 transmitting central server reply data, including the keybox positioning data, to the mobile-device 124. In one embodiment, the central server reply data includes a map link to find the keybox 112. Alternatively, the mobile-device 124 displays a map that includes the location of the keybox 112 based on the data returned from the central server 136.

[0068] With the above embodiments, an agent is looking for potentially misplaced keybox 112 used during, e.g., multiple showings of a property, would be able to locate the keybox 112 by means of the mobile APP 128.

[0069] The term about is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms a, an and the are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms comprises and/or comprising, when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.

[0070] While the present disclosure has been described with reference to an exemplary embodiment or embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the essential scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this present disclosure, but that the present disclosure will include all embodiments falling within the scope of the claims.