US20230074312A1 - Automatic physical access - Google Patents
Automatic physical access Download PDFInfo
- Publication number
- US20230074312A1 US20230074312A1 US17/982,576 US202217982576A US2023074312A1 US 20230074312 A1 US20230074312 A1 US 20230074312A1 US 202217982576 A US202217982576 A US 202217982576A US 2023074312 A1 US2023074312 A1 US 2023074312A1
- Authority
- US
- United States
- Prior art keywords
- wireless
- smartphone
- wireless device
- network
- database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/20—Individual registration on entry or exit involving the use of a pass
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00309—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C2009/00753—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by active electrical keys
- G07C2009/00769—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by active electrical keys with data transmission performed by wireless means
Definitions
- FIGS. 1 - 7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented
- FIGS. 8 - 10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments.
- FIGS. 11 - 12 are schematics illustrating a database of meetings, according to exemplary embodiments.
- FIGS. 13 - 18 are schematics illustrating locational tracking, according to exemplary embodiments.
- FIGS. 19 - 22 are schematics illustrating building services, according to exemplary embodiments.
- FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments.
- FIGS. 24 - 25 are schematics further illustrating a database of calendars, according to exemplary embodiments.
- FIGS. 26 - 29 are schematics illustrating historical network tracking, according to exemplary embodiments.
- FIG. 30 is a schematic illustrating network tracking, according to exemplary embodiments.
- FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments.
- FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments.
- FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments.
- FIGS. 34 - 35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments.
- FIGS. 36 - 37 depict still more operating environments for additional aspects of the exemplary embodiments.
- first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device without departing from the teachings of the disclosure.
- FIGS. 1 - 7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented.
- FIG. 1 illustrates a human user 20 in a lobby 22 of a building 24 .
- the human user 20 may be an employee working within the building 24 , or the human may be visiting someone within the building 24 .
- the human user 20 in short, may be an employee, a visitor, a contractor, a tenant, or a guest requesting entry into the building 24 .
- the human user 20 will mainly be described as a visitor.
- the visitor 20 wishes to enter an elevator 26 and proceed into secure areas of the building 24 , the visitor 20 usually must check-in with a security guard.
- exemplary embodiments detect the wireless presence of the visitor's mobile device 30 , such as her smartphone 32 . That is, if the visitor's smartphone 32 is recognized, then exemplary embodiments may permit entry of the visitor 20 to the secure areas within the building 24 . However, if the visitor's smartphone 32 is unrecognized, then exemplary embodiments may require more authentication credentials or additional measures, as later paragraphs will explain.
- FIG. 2 illustrates wireless presence.
- the visitor's smartphone 32 may attempt to access a wireless network 40 serving the lobby 22 .
- a wireless network 40 serving the lobby 22 .
- many people carry a smartphone that interfaces with wireless networks. So, when the visitor's smartphone 32 enters the lobby 22 , the smartphone 32 may establish wireless communication with the wireless network 40 serving the lobby 22 .
- the smartphone 32 may request access or permission to a local area wireless fidelity (or WI-FI®) network serving the lobby 22 or any other area.
- WI-FI® wireless fidelity
- a security server 42 may be consulted. Once the wireless network 40 detects the radio presence of the visitor's smartphone 32 , the security server 42 may determine whether the visitor 20 is authorized for entry, based on the wireless presence of the visitor's smartphone 32 . For example, the security server 42 may consult a database 44 of personnel.
- the database 44 of personnel may store names, addresses, and/or other information for personnel who are authorized to enter the secure area of the building 24 .
- the database 44 of personnel may be arranged according to mobile devices. That is, the database 44 of personnel may store database associations between different names or identities of people and different unique identifiers of their mobile devices.
- FIG. 3 further illustrates secure access.
- the smartphone 32 is not matched to the database 44 of personnel, the visitor may still be granted access for legitimate purposes.
- the visitor may be a supplier or contractor attending a meeting within the building 24 .
- the security server 42 may consult a database 46 of meetings.
- the database 46 of meetings stores different meetings that are scheduled or calendared within the building 24 .
- Each meeting may have an associated list 48 of invitees who are authorized to attend the meeting.
- Each invitee may be identified according to his or her mobile device 30 . That is, each invitee may be identified by a unique cellular identifier associated with, or assigned to, their cellular mobile device (such as the smartphone 32 ).
- the database 46 of meetings may thus store database associations between different scheduled meetings and different unique identifiers of the invitees' mobile devices 30 . If an entry in the database 46 of meetings matches the unique identifier of the visitor's smartphone 32 , then the corresponding human visitor may be authorized for entry to attend the corresponding meeting. Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of their smartphones 32 .
- FIG. 4 further illustrates the database 46 of meetings.
- invitees may be more limited in the dates and times of their access.
- each meeting 50 may also be associated with a date 52 , a start time 54 , and a duration 56 .
- the visitor's smartphone 32 may be matched as an invitee to the meeting 50 , the visitor may still be denied access.
- a current date and time 58 may be time stamped. If the current date and time 58 does not match the scheduled date 52 of the meeting 50 , then entry may be denied.
- the smartphone 32 requests wireless access (to the wireless network 40 ) too early or too late for the scheduled meeting 50 , then entry may be denied.
- the scheduled meeting 50 may thus have a window 60 of arrival, before or after which the visitor may not enter. So, even though a supplier or contractor is authorized for entry, admittance may be limited to nearly the scheduled date 52 and start time 54 of the meeting 50 .
- the user of the smartphone 32 may thus be authorized for physical entry, but exemplary embodiments may require that the user wait until the window 60 of arrival is satisfied.
- the meeting 50 ends perhaps at a stop time calculated using the duration 56
- the visitor's smartphone 32 may not linger. Exemplary embodiments may thus continue tracking the smartphone 32 (as later paragraphs will explain) during and after the meeting 50 to ensure the visitor does not afterwards linger too long. If the attending visitor lingers too long after the meeting 50 , exemplary embodiments may deny exit from the building, as a security precaution.
- FIG. 5 illustrates a database 70 of calendars.
- the visitor's smartphone 32 may be matched to an individual's electronic calendar 72 .
- the database 70 of calendars stores different electronic calendars for different users (such as the employees and/or tenants in the building 24 ).
- the security server 42 may query the database 70 of calendars for the unique identifier of the smartphone 32 . If a matching calendar entry is determined, then the smartphone 32 is calendared to meet an employee or tenant inside the building 24 . Exemplary embodiment may thus authorize entry, based on wireless network recognition of the visitor's smartphone 32 .
- FIG. 6 illustrates notification.
- the security server 42 may thus generate and send one or more electronic messages 80 to destination devices 82 associated with different destination addresses 84 , thus alerting of the visitor's entry into the building 24 .
- An employee for example, may be alerted to the visitor's arrival.
- Other meeting invitees may also be notified, using the unique identifier assigned to their respective smartphones.
- FIG. 7 illustrates entry.
- the security server 42 may thus generate an electronic entry instruction 86 to allow physical entry.
- the entry instruction 86 is then sent as packets of data to any destination device.
- FIG. 7 illustrates the entry instruction 86 routing to a network address assigned to a lock controller 88 .
- the lock controller 88 manages an electronic lock 90 securing some door or gate.
- the entry instruction 86 instructs the lock controller 88 to activate or unlock the electronic lock 90 , thus allowing the visitor to physically enter the building 24 and/or some floor within the building 22 .
- the security server 42 may further instruct an elevator controller 92 to summon an elevator 94 , thus lifting the visitor to some floor or level, as later paragraphs will explain.
- the security server 42 may also monitor or track the movement of the visitor's smartphone 32 to prevent frolic or unauthorized detours (as later paragraphs will also explain).
- Exemplary embodiments thus synchronize entry with wireless detection.
- Wireless detection of any mobile device 30 may thus be used to authorize entry to secure areas.
- FIGS. 1 - 7 primarily illustrate the visitor's smartphone 32
- exemplary embodiments may utilize any wired or wireless device (as later paragraphs will explain). Indeed, badges, watches, and other wearable smart devices may be wirelessly detected to permit access. Integration with personnel directories and calendaring systems further defines permissible locations of visitors.
- FIGS. 8 - 10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments.
- FIG. 8 illustrates presence detection of the visitor's smartphone 32 .
- the smartphone 32 may establish wireless communication with the wireless network 40 serving the area.
- the smartphone 32 may request access or permission to a local area wireless fidelity (or WI-FI®) network, wide area cellular network, or any other network.
- the wireless network 40 may only recognize, or transmit/receive, using a particular frequency or band.
- the smartphone 32 may thus instruct its transceiver (not shown for simplicity) to wirelessly request access permission using the electromagnetic frequency band required by the wireless network 40 .
- the security server 42 may be notified.
- the wireless network 40 detects the smartphone 32
- exemplary embodiments may inform the security server 42 . That is, the smartphone 32 may send an access request to an access device 100 serving the wireless network 40 .
- FIG. 8 illustrates the access device 100 as a wireless router 102 , which commonly serves many residential and business WI-FI® networks.
- the access device 100 may be any network interface to an access network, such as a gateway, cable modem, or DSL modem.
- the smartphone 32 broadcasts a request that seeks access permission to the wireless network 40 .
- the access device 100 may send a packetized access notification 104 into a communications network 106 for routing and delivery to a network address associated with the security server 42 .
- the wireless router 102 may store or execute code or programming that forces or commands the access notification 104 when any device attempts to access the wireless network 40 .
- the access notification 104 may thus alert the security server 42 to the radio frequency presence of the visitor's smartphone 32 .
- the access notification 104 may further include information that uniquely identifies the smartphone 32 , such as data representing a cellular identifier 110 . While any alphanumeric combination may uniquely identify the smartphone 32 , FIG. 8 illustrates the smartphone's cellular telephone number (or “CTN”) 112 , International Mobile Subscriber Identity (or “IMSI”) 114 , or Mobile Station International Subscriber Directory Number (“MSISDN”) 116 . Whenever the mobile smartphone 32 sends messages or information, the smartphone 32 may include or self-report its CTN 112 , IMSI 114 , and/or its MSISDN 116 .
- CTN cellular telephone number
- IMSI International Mobile Subscriber Identity
- MSISDN Mobile Station International Subscriber Directory Number
- the security server 42 may authorize the smartphone 32 .
- the security server 42 has a processor 120 (e.g., “ ⁇ LP”), application specific integrated circuit (ASIC), or other component that executes a security algorithm 122 stored in a local memory 124 .
- the security algorithm 122 instructs the processor 120 to perform operations, such as receiving and processing information received from a network interface to the communications network 106 .
- the information may be received as packets of data according to a packet protocol (such as any of the Internet Protocols).
- the packets of data contain bits or bytes of data describing the contents, or payload, of a message.
- a header of each packet of data may contain routing information identifying an origination address and/or a destination address.
- the security algorithm 122 may instruct the processor 120 to inspect the packetized access notification 104 for the cellular identifier 110 associated with the visitor's smartphone 32 requesting access to the wireless network 40 .
- FIG. 9 illustrates the database 44 of personnel.
- the database 44 of personnel may store names, addresses, images, and/or other information for personnel who are authorized to enter any area.
- the database 44 of personnel is illustrated as a table 130 that electronically maps, relates, or associates different employees or tenants 132 to their corresponding personal information.
- an entry may associate each person's name 134 , address 136 , and/or employee number 138 to the cellular identifier 110 associated with the person's personal wireless device (such as the smartphone 32 illustrated in FIGS. 1 - 8 ).
- FIG. 9 illustrates the cellular identifier 110 as the cellular telephone number (“CTN”) 112 , the IMSI 114 , and/or the MSISDN 116 .
- CDN cellular telephone number
- Each person's wireless device may be additionally or alternatively uniquely identified by a network address, a manufacturer's serial number, or any other alphanumeric combination.
- the database 44 of personnel may further associate a digital image file 140 to the cellular identifier 110 , thus allowing retrieval, recognition, and/or analysis of a facial image.
- the database 44 of personnel is illustrated as being locally stored in the memory 124 of the security server 42 , but some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 8 ). While FIG. 9 only illustrates a few entries, in practice the database 44 of personnel may contain many entries for hundreds or thousands of people.
- the security server 42 may query the database 44 of personnel.
- the security algorithm 122 causes the processor 120 to query for entries that match the query search term(s) detailed or described in the electronic access notification 104 . If the database 44 of personnel contains a matching entry, then the security server 42 may authorize the smartphone 32 (and thus the corresponding user or visitor) to enter. The security server 42 thus recognizes the smartphone 32 as belonging to one of the personnel authorized to enter the building (illustrated as reference numeral 24 in FIGS. 1 - 7 ). As an example, if the CTN 112 , the IMSI 114 , and/or the MSISDN 116 matches an entry in the database 44 of personnel, then the security server 42 may conclude that the corresponding user of the smartphone 32 is authorized to enter.
- FIG. 10 illustrates the entry instruction 86 .
- the security server 42 may automatically authorize entry.
- the security algorithm 122 may thus instruct the processor 120 to generate the entry instruction 86 to allow physical entry.
- the entry instruction 86 may contain any information that confirms the smartphone 32 is authorized to enter the secure area.
- FIG. 10 illustrates the entry instruction 86 routing to the network address assigned to the lock controller 88 .
- the entry instruction 86 instructs the lock controller 88 to activate or unlock the electronic lock 90 .
- the security server 42 may thus unlock a door, gate, or turnstile that permits physical entry of the corresponding user of the smartphone 32 . An employee or tenant thus enters based on the wireless recognition of the smartphone 32 .
- Exemplary embodiments thus present an elegant solution.
- people may be uniquely identified by their mobile devices (such as the smartphone 32 ).
- Employees, tenants, and visitors may thus be personally identified merely by carrying their smartphones.
- Exemplary embodiments may thus permit authorized entry to secure areas, simply by recognizing wireless transmissions from their mobile devices. No phone calls are needed, and labor expenses are reduced.
- Exemplary embodiments may be applied regardless of networking environment. Exemplary embodiments may be easily adapted to stationary or mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH® capability. Exemplary embodiments may be applied to mobile devices utilizing any portion of the electromagnetic spectrum and any signaling standard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band). Exemplary embodiments, however, may be applied to any processor-controlled device operating in the radio-frequency domain and/or the Internet Protocol (IP) domain.
- IP Internet Protocol
- Exemplary embodiments may be applied to any processor-controlled device utilizing a distributed computing network, such as the Internet (sometimes alternatively known as the “World Wide Web”), an intranet, a local-area network (LAN), and/or a wide-area network (WAN).
- Exemplary embodiments may be applied to any processor-controlled device utilizing power line technologies, in which signals are communicated via electrical wiring. Indeed, exemplary embodiments may be applied regardless of physical componentry, physical configuration, or communications standard(s).
- Exemplary embodiments may utilize any processing component, configuration, or system.
- Any processor could be multiple processors, which could include distributed processors or parallel processors in a single machine or multiple machines.
- the processor can be used in supporting a virtual processing environment.
- the processor could include a state machine, application specific integrated circuit (ASIC), programmable gate array (PGA) including a Field PGA, or state machine.
- ASIC application specific integrated circuit
- PGA programmable gate array
- any of the processors execute instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.
- FIGS. 11 - 12 are schematics further illustrating the database 46 of meetings, according to exemplary embodiments.
- the smartphone 32 may be an invitee to a meeting within some secure area.
- the access device 100 sends the access notification 105 to the security server 42 .
- the packetized access notification 104 may include data describing the cellular identifier 110 (e.g., the CTN 112 , the IMSI 114 , and/or the MSISDN 116 ).
- the security server 42 may then query the database 46 of meetings to determine if the smartphone 32 matches the list 48 of invitees to any scheduled meeting 50 .
- FIG. 12 illustrates the database 46 of meetings.
- FIG. 12 illustrates the database 46 of meetings being locally stored in the memory 124 of the security server 42 .
- some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 11 ).
- FIG. 12 only illustrates a few entries, in practice the database 46 of meetings may contain many entries for hundreds or thousands of different meetings or gatherings.
- the database 46 of meetings is illustrated as a table 150 that maps, relates, or associates different scheduled meetings 50 to the corresponding list 48 of invitees.
- each invitee 48 may be identified by their name, here exemplary embodiments identify each invitee 48 according to his or her mobile device identifier.
- each invitee 48 may be identified by the unique cellular identifier 110 associated with, or assigned to, their cellular device (such as the smartphone 32 ).
- FIG. 12 thus illustrates database associations between a meeting 50 , an organizer or inviter 152 , and the different invitees 48 .
- Each party to the meeting 50 may thus be uniquely identified by their respective CTN 112 , IMSI 114 , and/or MSISDN 116 .
- the security server 42 may thus authorize entry, such as by generating the entry instruction 86 (as illustrated with reference to FIG. 10 ). Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of their smartphones.
- FIGS. 13 - 18 are schematics illustrating locational tracking, according to exemplary embodiments.
- exemplary embodiments may monitor the movements of the smartphone 32 . If the visitor's smartphone 32 strays or frolics, a security concern may develop. Exemplary embodiments, then, may track the smartphone 32 to ensure the user stays on route to the meeting 50 .
- FIG. 13 illustrates room assignments.
- the database 46 of meetings may also associate a meeting location 154 to each meeting 50 .
- conference rooms, offices, beverage rooms, and auditoriums may be uniquely identified by some name and/or location. So, when the meeting 50 is scheduled or logged in the database 46 of meetings, exemplary embodiments may further store an electronic database association with the corresponding meeting location 154 .
- FIG. 14 illustrates security routings.
- the security server 42 may query a database 160 of routings.
- the database 160 of routings stores predetermined building routes 162 from some beginning location (such as a point of entry 164 ) to the destination at the meeting location 154 .
- the database 160 of routings may store different routes 162 from the lobby of the building (illustrated, respectively, as reference numerals 22 and 24 in FIG. 1 ) to the meeting location 154 of the scheduled meeting 50 .
- FIG. 1 illustrates security routings.
- FIG. 14 illustrates the database 160 of routings as being locally stored in the security server 42 , but some or all of the electronic database entries may be remotely maintained at some other server or location in the communications network (illustrated as reference numeral 106 in FIG. 11 ).
- a particular conference room for example, may have a route 162 along which the visitor is only permitted to walk or navigate. That is, only certain paths along particular halls and/or through particular doors are available to the visitor.
- the database 160 of routings may thus store approved routes 162 along which employees, tenants, and/or visitors may move from any point (such as the entry 164 ) to the final destination at the meeting location 154 .
- FIG. 15 illustrates GPS tracking. After the visitor's smartphone 32 is authorized for entry, the visitor should walk or travel along the predetermined route 162 to the destination meeting location 154 . After all, confining the visitor to the predetermined route 162 may help prevent rogue access to unauthorized locations. Exemplary embodiments, then, may track the visitor's position or progress along the predetermined route 162 .
- FIG. 15 thus illustrates GPS waypoints 170 along which the smartphone 32 may or must report. That is, the predetermined route 162 may be defined as a series of global positioning system information. As the visitor walks the corridors of the building, the visitor's smartphone 32 may continually, periodically, and/or randomly report its current location 172 .
- FIG. 15 illustrates GPS tracking. After the visitor's smartphone 32 is authorized for entry, the visitor should walk or travel along the predetermined route 162 to the destination meeting location 154 . After all, confining the visitor to the predetermined route 162 may help prevent rogue access to unauthorized locations. Exemplary embodiments, then, may track
- the security server 42 may compare the current location 172 to the GPS waypoints 170 associated with the meeting location 154 . If the current location 172 matches one of the GPS waypoints (perhaps within a locational tolerance), then the security algorithm 122 may conclude that the visitor's smartphone 32 is on track and proceeding as authorized.
- the security algorithm 122 may generate a security notification 174 .
- the security notification 174 may be any electronic message that warns the visitor to resume the predetermined route 162 to the destination meeting location 154 .
- the security notification 174 may route back to the access device 100 for transmission to the network address assigned to the smartphone 32 .
- the security notification 174 may be a short message service (SMS) text message that is sent to the unique cellular identifier 110 of the visitor's smartphone 32 .
- SMS short message service
- the security notification 174 may further include a correction 176 that puts the visitor back on the predetermined route 162 to the destination meeting location 154 .
- the security server 42 may also copy or forward the security notification 174 to a device associated with a security guard for nearly immediate human intervention.
- FIG. 16 illustrates network tracking.
- exemplary embodiments may infer the location of the visitor's smartphone 32 using network recognition. As the reader may understand, GPS signals are sometimes not received in indoor environments. Exemplary embodiments, then, may additionally or alternatively infer the location of the visitor's smartphone 32 using network identifiers.
- FIG. 16 thus illustrates network waypoints 180 along which the smartphone 32 must request access permission. That is, the predetermined route 162 may be defined as a series of network identifiers. For example, as the visitor walks the corridors of the building, the visitor's smartphone 32 may wirelessly encounter different wireless fidelity (WI-FI®) networks serving the different floors, hallways, and/or rooms.
- WI-FI® wireless fidelity
- the visitor's smartphone 32 may also detect other identifiers of other networks (such as different cellular network cells). Regardless, the smartphone 32 may request access permission to each wireless network 40 .
- the corresponding access device 100 may thus notify the security server 42 using the access notification 104 (above explained with reference to FIG. 8 ).
- FIG. 16 illustrates the network waypoints 180 as a series 182 of service set identifiers.
- Each individual service set identifier (or “SSID”) 184 uniquely identifiers a different WI-FI® network serving some portion of the predetermined route 162 to the destination meeting location 154 .
- the security server 42 receives each access notification 104 , the access notification 104 may identify the corresponding SSID 184 .
- the security server 42 may thus compare the SSID 184 to the network waypoints 180 associated with the meeting location 154 . If the SSID 184 matches one of the network waypoints 180 , then the security algorithm 122 may conclude that the visitor's smartphone 32 is on track and proceeding as authorized. However, if the SSID 184 fails to match one or any of the network waypoints 180 , the security algorithm 122 may generate the security notification 174 with the correction 176 (as earlier explained).
- FIG. 17 illustrates a strict comparison.
- the security server 42 may require a strict sequential match with the network waypoints 180 .
- the visitor's smartphone 32 in other words, may be required to traverse the network waypoints 180 in sequential order, from a first entry SSID 190 to a final destination SSID 192 serving the destination meeting location 154 . If the visitor's smartphone 32 strays from the predetermined route 162 , one of the access notifications 184 will identify an SSID 184 not matching the approved route 162 .
- the smartphone 32 in other words, is requesting wireless access to an unauthorized network, thus revealing a frolic or detour.
- the security algorithm 122 may thus alert security (as earlier explained).
- FIG. 18 illustrates timing requirements.
- each network waypoint 180 may also have a corresponding timing parameter 200 .
- FIG. 18 thus illustrates each network waypoint 180 as an SSID/time pairing. That is, each network waypoint 180 may be a network/timing pair of values associated with each successive wireless network 40 .
- the security server 42 may monitor a speed or time of movement.
- Each access notification 104 may have a timestamp 202 that marks a time of requested access to the wireless network 40 (as identified by the SSID 184 ).
- the security server 42 may also require strict adherence to each corresponding timing parameter 200 .
- the security server 42 may initialize a timer 204 with receipt of the access notification 104 .
- the timer 204 counts up or down to a final value at a receipt of a next access notification 104 associated with the same smartphone 32 (e.g., the cellular identifier 110 ).
- the timer 204 may thus count a time in seconds or minutes between successive access notifications 104 sent from different access devices 100 along the predetermined route 162 . So, not only must each sequential SSID 184 match the network waypoints 180 , but exemplary embodiments may also require timing compliance between the successive network waypoints 180 .
- the security server 42 may thus compare a current value of the timer 204 to the timing parameter 200 associated with a next corresponding network waypoint 182 along the predetermined route 162 . If the current value of the timer 204 is less than or equal to the timing parameter 200 , then the security algorithm 122 may conclude that the visitor's smartphone 32 is on the approved route 162 and on track to arrive on time at the final meeting destination location 154 . However, if the current value of the timer 204 exceeds the timing parameter 200 , the security algorithm 122 may conclude that the visitor's smartphone 32 has strayed from the predetermined route 162 . The security algorithm 122 may thus alert security (as earlier explained).
- FIGS. 19 - 22 are schematics illustrating building services, according to exemplary embodiments.
- exemplary embodiments may coordinate or time various building services with respect to the location of the smartphone 32 .
- the security server 42 may thus order up or coordinate various building services at appropriate times and locations.
- FIG. 19 illustrates a database 210 of services.
- the database 210 of services is illustrated as a table 212 that associates different locations 214 to different services 216 .
- one of the services 216 may be lighting requirements 218 for each different location 214 .
- the security server 42 may query the database 210 of services for the corresponding lighting requirements 218 .
- Lights may thus be defined.
- the database 210 of services may thus store electronic database associations for the lights that illuminate the different locations 214 .
- Each wireless network 40 may be mapped to the light fixtures 220 and/or lighting loads 222 (such as individual electrical circuits) illuminating its wireless service area.
- the security server 42 may thus query for the SSID 184 and retrieve the lighting requirements 218 for its wireless service area.
- electronic database associations may be defined for any GPS coordinates or waypoints along the route 162 .
- the lights may be activated.
- the security server 42 may send a lighting command 230 into the communications network 106 for delivery to the network address associated with a lighting controller 232 .
- the lighting controller 232 responds by activating, or turning on, the corresponding physical light fixture 234 and/or the physical electrical load 236 .
- the security server 42 may thus coordinate the lights along the predetermined route 162 for safety and security. Lights may then be deactivated when no mobile device requests wireless access to the corresponding wireless service area. Lights may also be deactivated after some passage of time.
- FIG. 21 illustrates HVAC services.
- exemplary embodiments may also coordinate heat or air conditioning with respect to the location 214 along the approved route 162 .
- the security server 42 may heat or cool the corresponding physical space or area. Indeed, the security server 42 may even order up an ambient temperature within the destination meeting location (illustrated as reference numeral 154 in FIGS. 15 - 16 ).
- the database 210 of services may thus include entries for HVAC settings 240 associated with the location 214 along the approved route 162 .
- the security server 42 may thus query the database 210 of services for the SSID 184 and retrieve the corresponding HVAC settings 240 (such as a temperature 242 and/or humidity 244 ) associated with the corresponding physical space or area. The security server 42 may then send an HVAC command 246 into the communications network 106 for delivery to the network address associated with an HVAC system 248 . The security server 42 may even receive weather data 249 to further analyze and satisfy the HVAC settings 240 desired for the corresponding physical space or area.
- the corresponding HVAC settings 240 such as a temperature 242 and/or humidity 244
- FIG. 22 illustrates other services. Exemplary embodiments may also coordinate many other services for the comfort and convenience of the invitees/attendees.
- the database 210 of services may also have entries for other services, such as network access 250 , equipment 252 , and vending 254 .
- the security server 42 may query the database 210 of services for the SSID 184 of the meeting location 154 . The security server 42 may thus retrieve the corresponding services 216 defined for that meeting location 214 . The security server 42 may then generate an electronic, packetized service order 256 that routes to a network address of a service provider system 258 .
- the security server 42 may arrange or prearrange wireless network access 250 for each attendee's mobile wireless device.
- the security server 42 knows the SSID 184 of the WI-FI® network serving the destination conference room, along with the unique cellular identifier 110 of each attendee's wireless device (as explained with reference to FIGS. 11 - 14 ).
- the security server 42 may thus pre-authorize each attendee's wireless device for wireless service in the destination conference room. Any wireless access point, in other words, may be instructed to recognize the unique cellular identifier 110 of each attendee's wireless device.
- Each attendee's device thus has immediate access to wireless services.
- the equipment 252 may also be ordered. Computers, projectors, conference phone set-up, pens, and whiteboards are just some of the equipment 252 that may be pre-ordered, based on the location 214 .
- the meeting organizer (illustrated as reference numeral 152 in FIG. 12 ) may thus enter any data or description of the equipment 252 desired for the meeting.
- the security server 42 may thus pre-arrange arrival and set-up of the equipment 252 . As the attendees enter the destination meeting location 154 , the equipment 252 they need is automatically ordered and waiting for use.
- Vending 254 may also be pre-arranged.
- the meeting organizer may thus enter or request any food and drink for the meeting.
- the security server 42 may thus issue orders or commands for on-time delivery of food and drink from some identified vendor. As the attendees enter the destination meeting location 154 , the requested food and drink is automatically ordered and waiting for consumption.
- FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments.
- the smartphone 32 moves along the pre-approved route 162 to the destination meeting location 154 .
- Exemplary embodiments may thus track the smartphone's movement and generate elevator commands at appropriate moments in time or location.
- FIG. 23 illustrates an elevator command 270 as a data triplet 271 inserted into one of the network waypoints 180 .
- the elevator command 270 identifies which elevator (elevator number or identifier) is summoned for vertical travel from an entry floor to an exit floor. If a building only has one elevator, then perhaps the elevator command 270 may be simplified to a pair of data values. But many buildings may have multiple elevators, perhaps serving different floors.
- the opposite elevator command ( 3 , 22 , 1 ) would call “Elevator # 3 ” to “Floor # 22 ” for descend service to “Floor # 1 .”
- Each elevator command 270 may thus be generated for insertion into the pre-determined sequential network waypoints 180 .
- the security server 42 may summon the corresponding elevator in the sequence.
- the security algorithm 122 may further initialize the timer 204 to count up or down until the summons.
- Exemplary embodiments may insert the elevator command 270 at appropriate positions and/or times in the sequential network waypoints 180 and/or the sequential GPS waypoints (illustrated as reference numeral 170 in FIG. 15 ).
- the security server 42 may thus read, retrieve, and/or execute the elevator command 270 as one of the sequential steps.
- the security server 42 may thus generate an elevator instruction 272 that is sent into the communications network 106 for delivery to the network address associated with the elevator controller 92 . Elevator service may thus be summoned to coincide with the current location of the smartphone 32 .
- FIGS. 24 - 25 are schematics further illustrating the database 70 of calendars, according to exemplary embodiments.
- the access device 100 sends the access notification 104 (as earlier explained).
- the security server 42 may then query the database 70 of calendars for a matching entry.
- the database 70 of calendars stores different electronic calendars for the different employees and/or tenants in the building.
- FIG. 25 illustrates the database 70 of calendars as a table 280 that maps, relates, or associates different electronic calendars 72 to different invitees 282 .
- the database 70 of calendars may store a memory pointer or network address to an individual person's electronic calendar 72 .
- FIG. 25 illustrates the database 70 of calendars storing electronic database associations between electronic calendar entries 72 and their respective invitees 282 .
- the invitee may be uniquely identified by his or her unique cellular identifier 110 .
- An appointment in an electronic calendar in other words, may be arranged or associated with the CTN 112 , the IMSI 114 , and/or the MSISDN 116 of a participant 282 .
- the security server 42 may authorize entry. Referring back to FIG. 24 , when the security server 42 receives the access notification 104 , the security server 42 may query the database 70 of calendars for the visitor's unique cellular identifier 110 . If a matching entry is determined, the security server 42 may permit physical entry, as the visitor is scheduled for an appointment with an employee or tenant. Moreover, if the database 70 of calendars identifies the meeting location 154 , the security server 42 may further retrieve and monitor the predetermine route 162 to the meeting location 154 (as this disclosure explains with reference to FIGS. 14 - 18 and 23 ).
- FIGS. 26 - 29 are schematics illustrating historical network tracking, according to exemplary embodiments.
- historical observances of wireless detections may be used to infer future actions. That is, a user's habitual usage of the smartphone 32 may be used to predict where she will move, and/or what she will do, based on her past movements and wireless network access.
- exemplary embodiments may make recommendations and assumptions, based on habitual observance of its network usage.
- exemplary embodiments may match that detection to some past occurrence. In other words, most people are creatures of habit, so exemplary embodiments may predict our future movements and actions based on our historical behaviors.
- FIG. 26 illustrates a database 300 of usage.
- the database 300 of usage tracks historical usage of any user's wireless device 30 (such as the smartphone 32 ).
- the database 300 of usage may store entries related to usage at different times of days and/or at different locations.
- exemplary embodiments may query the database 300 of usage for historical usage at that same location.
- the database 300 of usage may thus log each current location 172 reported by the smartphone 32 .
- the smartphone 32 may repeatedly send its current location 172 (such as GPS information) to the security server 42 .
- the security server 42 may then log these locational reports in the database 300 of usage.
- the database 300 of usage is illustrated as being locally stored within the security server 42 , but any of the database entries may be remotely maintained at other network-accessible locations or servers.
- FIG. 26 illustrates the database 300 of usage as a table 302 that electronically maps, relates, or associates the cellular identifier 110 to different location reports. That is, each time the smartphone 32 reports its current location 172 , the database 300 of usage may add an entry for the unique cellular identifier 110 , the reported current location 172 , and a date and time 304 of the report. Over time, then, the database 300 of usage may store long-term records of the movements of the smartphone 32 within the building 24 .
- FIG. 27 illustrates historical network usage.
- the corresponding access device 100 sends the packetized access notification 104 to alert the security server 42 (as this disclosure earlier explained).
- the security server 42 may thus instruct the database 300 of usage to log the access notification 104 , perhaps also with the date and time 304 . That is, each time the smartphone 32 requests wireless access to the wireless network 40 , the database 300 of usage may add an entry for the unique cellular identifier 110 , the service set identifier (“SSID”) 184 of the wireless fidelity (“WI-FI®”) network 40 , and the date and time 304 of the request.
- SSID service set identifier
- WI-FI® wireless fidelity
- the database 300 of usage may merely log the timestamp 202 reported in the access notification 104 , or the database 300 of usage may log some other measure of time (such as receipt of the access notification 104 ). Regardless, over time the database 300 of usage reveals a comprehensive long-term central repository of network access requested by the smartphone 32 .
- the security server 42 may thus infer future entries from the historical information.
- the security server 42 may query the database 300 of usage for any search terms and retrieve matching historical entries.
- the security server 42 may query for historical entries associated with the cellular identifier 110 .
- the security server 42 may thus retrieve historical locations or networks logged in the database 300 of usage. Indeed, the security server 42 may even query for historical entries having the same or approximate date and time 304 .
- the security server 42 may thus retrieve historical entries that match the same or similar day, time, current location 172 , or network SSID 184 .
- FIG. 28 illustrates locational prediction.
- the security server 42 may predict or infer a future location 310 .
- the security server 42 may query for a series or sequence of entries having about the same location 172 and/or the same date and time 304 .
- the security algorithm 122 may infer that the smartphone 32 is moving along a path historically observed. That is, the smartphone 32 is being carried along a familiar route to a historical destination previously logged in the database 300 of usage.
- the security algorithm 122 may conclude that the smartphone 32 is traveling along the same route to the same destination. If the smartphone 32 reports the same current locations 172 within a ten minute (10 min.) window of time as historically seen, the security server 42 may thus predict or infer that the smartphone 32 will have the future location 310 that matches at least one of the historical entries in the same series. As one example, if the smartphone's most recent five (5) location reports match some historical observance in the database 300 of usage, then the security server 42 may predict the smartphone's future location 310 will match the next historical sixth (6 th ) entry in the same historical sequence. The security server 42 may thus query for any search terms and retrieve one or multiple historical entries that match recent locational reports. As most people are creatures of habit, the security server 42 may thus predict the future location 310 of the smartphone 32 based on historical observances.
- FIG. 29 illustrates network prediction.
- the security algorithm 122 may predict the smartphone's access request to a wireless fidelity (“WI-FI®”) network, based on the historical entries in the database 300 of usage.
- the security server 42 may query for a series or sequence of entries having one or more matching SSID 184 entries and/or about the same date and time 304 . For example, if one or more of the recent access notifications 104 match one or more historical entries, then the security algorithm 122 may infer that the smartphone 32 is requesting access permissions along a path historically observed.
- WI-FI® wireless fidelity
- the security algorithm 122 may conclude that the smartphone 32 is requesting wireless access as historically seen. If a string or sequence 314 of the access notifications 104 match historical entries within a ten minute (10 min.) window 316 of time, the security server 42 may thus predict or infer that the smartphone 32 will request access to a next entry historically observed in the same series. As FIG.
- the security algorithm 122 may retrieve the next entry in the same sequence 314 and predict that the smartphone 32 will next request access to “SSID9.”
- the security algorithm 122 in other words, infers the future network 312 as the next entry in the matching sequence 314 .
- the security algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction.
- FIG. 30 is another schematic illustrating network tracking, according to exemplary embodiments.
- exemplary embodiments may track usage or access requests to any networking environment.
- the access notification 104 may report the networking details.
- the access notification 104 may report a radio frequency 320 and/or bitrate 322 of communication between the smartphone 32 and some other device (such as the access device 100 ).
- the timestamp 202 may be further added.
- the security server 42 receives the access notification 104
- the security algorithm 122 may thus log these details in the database 300 of usage.
- the radio frequency 320 and/or bitrate 322 may allow the security algorithm 122 to log whether the wireless network 40 operates at cellular frequencies or WI-FI® frequencies.
- the radio frequency 320 and/or the bitrate 322 may reveal near-field communications (“NFC”) and/or radio frequency identification (“RFID”) communications.
- NFC near-field communications
- RFID radio frequency identification
- the access notification 104 may additionally or alternatively report an initiator device 324 and a target device 326 .
- the access notification 104 may also detail unique radio frequency identification tags and readers.
- the security algorithm 122 may thus log these details in the database 300 of usage. Over time, then, the database 300 of usage contains historical entries detailing the NFC and RFID transactions involving the smartphone 32 . If any current transaction matches some historical entry, the security algorithm 122 may predict or infer future actions and/or locations, based on the match. The security algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction.
- FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments.
- the security server 42 may access any of the databases (illustrated as reference numerals 44 , 46 , 70 , 160 , 210 , and 300 ) to authorize access, to coordinate services, and to predict actions, as this disclosure explains.
- the databases may be individually maintained or grouped together, depending on networking, processing, and storage capabilities.
- FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments.
- the security server 42 may have authorized access, coordinated services, and/or predicted actions, sometimes cancelations are determined. For example, a meeting organizer may simply cancel a scheduled meeting in the database 46 of meetings. This cancelation 340 may then trickle down and affect access, services, and predictions. For example, if the cancelation 340 is determined in the database 46 of meetings, the security server 42 may disperse that cancelation 340 . The invitees' devices to the now-canceled meeting may be notified (perhaps using the notification message 80 illustrated in FIG. 6 ). Entry authorization for the invitees' devices may be canceled by removal from the database 46 of meetings and/or removal from the database 70 of calendars.
- the entry instruction (illustrated as reference numeral 86 in FIG. 7 ) may be canceled, thus stopping or ceasing any entry process.
- the elevator instruction (illustrated as reference numeral 272 in FIG. 23 ) may be canceled, thus removing any summons for elevators.
- any retrieval and/or analysis of routes in the database 160 of routings may be canceled or aborted.
- Any retrieval and/or electronic order of services in the database 210 of services may also be canceled or aborted.
- electronic notifications of the cancelation 340 may be sent to service providers (such as contractors and vendors). Any historical analysis of entries in the database 300 of usage may be halted or aborted.
- the cancelation 340 may thus electronically cancel any reservation for a conference room, HVAC needs, and lighting requirements.
- FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments.
- exemplary embodiments may arrange and set-up a teleconference call and/or a telepresence video call between the visitor's smartphone 32 and other participants.
- the security server 42 may thus use the unique cellular identifier 110 to retrieve any meeting entries in the database 46 of meetings and/or in the database 70 of calendars.
- the security server 42 may arrange a conference room and/or an office or desk for the visitor, in response to a matching entry.
- the security server 42 may also automatically set-up a teleconference call or a videoconference call to the meeting invitee devices retrieved from the database 46 of meetings and/or the database 70 of calendars.
- the security server 42 may also concomitantly arrange video cameras, whiteboards, beverages, lighting, and other services (perhaps revealed by the database 210 of services, as previously explained).
- FIGS. 34 - 35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments.
- a unique cellular identifier 110 is received (Block 350 ) and the security server 42 is notified (Block 352 ).
- a database is queried for the cellular identifier 110 (Block 354 ).
- Physical access to a secure area is granted, based on a matching entry in the database (Block 356 ).
- the electronic lock 90 may be activated to permit entry (Block 358 ).
- the electronic notification message 80 may be sent to a meeting organizer and/or other invitees, thus alerting to the arrival and access of the user associated with the cellular identifier (Block 360 ).
- the location 154 of the meeting may also be determined (Block 362 ).
- the flowchart continues with FIG. 35 .
- the corresponding route 162 retrieved (Block 364 ).
- the elevator 94 may be summoned (Block 366 ).
- the corresponding services 216 may also be retrieved (Block 368 ).
- Historical usage associated with the cellular identifier 110 is retrieved (Block 370 ).
- the future location 310 (Block 372 ) and/or the future network 312 (Block 374 ) may be predicted. Physical facilities are allocated based on the cellular identifier 110 (Block 376 ).
- FIG. 36 is a schematic illustrating still more exemplary embodiments.
- FIG. 36 is a more detailed diagram illustrating a processor-controlled device 400 .
- exemplary embodiments may partially or entirely operate in any mobile or stationary processor-controlled device.
- FIG. 36 illustrates the security algorithm 122 stored in a memory subsystem of the processor-controlled device 400 .
- One or more processors communicate with the memory subsystem and execute either, some, or all applications. Because the processor-controlled device 400 is well known to those of ordinary skill in the art, no further explanation is needed.
- FIG. 37 depicts other possible operating environments for additional aspects of the exemplary embodiments.
- FIG. 37 illustrates the security algorithm 122 operating within various other processor-controlled devices 400 .
- FIG. 37 illustrates that the security algorithm 122 may entirely or partially operate within a set-top box (“STB”) ( 402 ), a personal/digital video recorder (PVR/DVR) 404 , a Global Positioning System (GPS) device 408 , an interactive television 410 , a tablet computer 412 , or any computer system, communications device, or processor-controlled device utilizing the processor and/or a digital signal processor (DP/DSP) 414 .
- STB set-top box
- PVR/DVR personal/digital video recorder
- GPS Global Positioning System
- DP/DSP digital signal processor
- the device 400 may also include watches, radios, vehicle electronics, clocks, printers, gateways, mobile/implantable medical devices, and other apparatuses and systems. Because the architecture and operating principles of the various devices 400 are well known, the hardware and software componentry of the various devices 400 are not further shown and described.
- Exemplary embodiments may be physically embodied on or in a computer-readable storage medium.
- This computer-readable medium may include CD-ROM, DVD, tape, cassette, floppy disk, optical disk, memory card, memory drive, and large-capacity disks.
- This computer-readable medium, or media could be distributed to end-subscribers, licensees, and assignees.
- a computer program product comprises processor-executable instructions for automatic secure access, as the above paragraphs explained.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Telephonic Communication Services (AREA)
Abstract
Physical access to secure areas is automatically performed based on presence or detection of a wireless device. A unique identifier of a wireless cellular device, for example, may be pre-authorized for occupants, employees, and tenants of a building. Contractors and vendors may also have their wireless cellular devices pre-approved for access. When the wireless cellular device is detected by a network serving the secure area, its unique identifier may be compared to databases or lists of approved cellular devices. Physical access may thus be automatically granted, based on possession of a recognized cellular device.
Description
- This application is a continuation of U.S. application Ser. No. 17/069,362 filed Oct. 13, 2020, which is a continuation of U.S. application Ser. No. 15/951,217 filed Apr. 12, 2018 and since issued as U.S. Pat. No. 10,861,266, which is a continuation of U.S. application Ser. No. 14/666,356 filed Mar. 24, 2015 and since issued as U.S. Pat. No. 9,972,144. All sections of the aforementioned application(s) and/or patent(s) are incorporated herein by reference in their entirety.
- Secure physical access is important to homes and businesses. Much money and time are devoted to reducing rogue, criminal entry into homes and businesses.
- The features, aspects, and advantages of the exemplary embodiments are understood when the following Detailed Description is read with reference to the accompanying drawings, wherein:
-
FIGS. 1-7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented; -
FIGS. 8-10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments; -
FIGS. 11-12 are schematics illustrating a database of meetings, according to exemplary embodiments; -
FIGS. 13-18 are schematics illustrating locational tracking, according to exemplary embodiments; -
FIGS. 19-22 are schematics illustrating building services, according to exemplary embodiments; -
FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments; -
FIGS. 24-25 are schematics further illustrating a database of calendars, according to exemplary embodiments; -
FIGS. 26-29 are schematics illustrating historical network tracking, according to exemplary embodiments; -
FIG. 30 is a schematic illustrating network tracking, according to exemplary embodiments; -
FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments; -
FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments; -
FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments; -
FIGS. 34-35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments; and -
FIGS. 36-37 depict still more operating environments for additional aspects of the exemplary embodiments. - The exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the exemplary embodiments to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).
- Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating the exemplary embodiments. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.
- As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “comprises,” “including,” 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, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
- It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device without departing from the teachings of the disclosure.
-
FIGS. 1-7 are simplified schematics illustrating an environment in which exemplary embodiments may be implemented.FIG. 1 illustrates ahuman user 20 in alobby 22 of abuilding 24. Thehuman user 20 may be an employee working within thebuilding 24, or the human may be visiting someone within thebuilding 24. Thehuman user 20, in short, may be an employee, a visitor, a contractor, a tenant, or a guest requesting entry into thebuilding 24. For simplicity, thehuman user 20 will mainly be described as a visitor. When thevisitor 20 wishes to enter anelevator 26 and proceed into secure areas of thebuilding 24, thevisitor 20 usually must check-in with a security guard. Here, though, exemplary embodiments detect the wireless presence of the visitor'smobile device 30, such as hersmartphone 32. That is, if the visitor'ssmartphone 32 is recognized, then exemplary embodiments may permit entry of thevisitor 20 to the secure areas within thebuilding 24. However, if the visitor'ssmartphone 32 is unrecognized, then exemplary embodiments may require more authentication credentials or additional measures, as later paragraphs will explain. -
FIG. 2 illustrates wireless presence. When the visitor enters some area (such as thelobby 22 or other area of the building 24), the visitor'ssmartphone 32 may attempt to access awireless network 40 serving thelobby 22. As the reader likely understands, many people carry a smartphone that interfaces with wireless networks. So, when the visitor'ssmartphone 32 enters thelobby 22, thesmartphone 32 may establish wireless communication with thewireless network 40 serving thelobby 22. Thesmartphone 32, for example, may request access or permission to a local area wireless fidelity (or WI-FI®) network serving thelobby 22 or any other area. - A
security server 42 may be consulted. Once thewireless network 40 detects the radio presence of the visitor'ssmartphone 32, thesecurity server 42 may determine whether thevisitor 20 is authorized for entry, based on the wireless presence of the visitor'ssmartphone 32. For example, thesecurity server 42 may consult adatabase 44 of personnel. Thedatabase 44 of personnel may store names, addresses, and/or other information for personnel who are authorized to enter the secure area of thebuilding 24. Thedatabase 44 of personnel, however, may be arranged according to mobile devices. That is, thedatabase 44 of personnel may store database associations between different names or identities of people and different unique identifiers of their mobile devices. If an entry in thedatabase 44 of personnel matches the unique identifier of the visitor'ssmartphone 32, then thecorresponding visitor 20 is authorized to enter thebuilding 24. Employees and tenants may thus quickly and easily enter thebuilding 24, merely based on wireless recognition of theirmobile devices 30. -
FIG. 3 further illustrates secure access. If thesmartphone 32 is not matched to thedatabase 44 of personnel, the visitor may still be granted access for legitimate purposes. For example, the visitor may be a supplier or contractor attending a meeting within thebuilding 24. When thewireless network 40 detects the frequency presence of the visitor'ssmartphone 32, thesecurity server 42 may consult adatabase 46 of meetings. Thedatabase 46 of meetings stores different meetings that are scheduled or calendared within thebuilding 24. Each meeting may have an associatedlist 48 of invitees who are authorized to attend the meeting. Each invitee, however, may be identified according to his or hermobile device 30. That is, each invitee may be identified by a unique cellular identifier associated with, or assigned to, their cellular mobile device (such as the smartphone 32). Thedatabase 46 of meetings may thus store database associations between different scheduled meetings and different unique identifiers of the invitees'mobile devices 30. If an entry in thedatabase 46 of meetings matches the unique identifier of the visitor'ssmartphone 32, then the corresponding human visitor may be authorized for entry to attend the corresponding meeting. Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of theirsmartphones 32. -
FIG. 4 further illustrates thedatabase 46 of meetings. Here invitees may be more limited in the dates and times of their access. AsFIG. 4 illustrates, eachmeeting 50 may also be associated with adate 52, astart time 54, and aduration 56. Even though the visitor'ssmartphone 32 may be matched as an invitee to themeeting 50, the visitor may still be denied access. For example, when the visitor'ssmartphone 32 requests access to thewireless network 40, a current date andtime 58 may be time stamped. If the current date andtime 58 does not match the scheduleddate 52 of themeeting 50, then entry may be denied. Furthermore, if thesmartphone 32 requests wireless access (to the wireless network 40) too early or too late for the scheduledmeeting 50, then entry may be denied. The scheduledmeeting 50 may thus have awindow 60 of arrival, before or after which the visitor may not enter. So, even though a supplier or contractor is authorized for entry, admittance may be limited to nearly the scheduleddate 52 and starttime 54 of themeeting 50. The user of thesmartphone 32 may thus be authorized for physical entry, but exemplary embodiments may require that the user wait until thewindow 60 of arrival is satisfied. Similarly, when themeeting 50 ends (perhaps at a stop time calculated using the duration 56), the visitor'ssmartphone 32 may not linger. Exemplary embodiments may thus continue tracking the smartphone 32 (as later paragraphs will explain) during and after themeeting 50 to ensure the visitor does not afterwards linger too long. If the attending visitor lingers too long after themeeting 50, exemplary embodiments may deny exit from the building, as a security precaution. -
FIG. 5 illustrates adatabase 70 of calendars. Here the visitor'ssmartphone 32 may be matched to an individual'selectronic calendar 72. As the reader likely understands, many people maintain their electronic calendars in a central location (such as an enterprise server database). Thedatabase 70 of calendars, in other words, stores different electronic calendars for different users (such as the employees and/or tenants in the building 24). When thewireless network 40 detects the radio presence of thesmartphone 32, thesecurity server 42 may query thedatabase 70 of calendars for the unique identifier of thesmartphone 32. If a matching calendar entry is determined, then thesmartphone 32 is calendared to meet an employee or tenant inside thebuilding 24. Exemplary embodiment may thus authorize entry, based on wireless network recognition of the visitor'ssmartphone 32. -
FIG. 6 illustrates notification. Once thesecurity server 42 authorizes the visitor'ssmartphone 32, electronic notifications may be sent. Thesecurity server 42 may thus generate and send one or moreelectronic messages 80 todestination devices 82 associated with different destination addresses 84, thus alerting of the visitor's entry into thebuilding 24. An employee, for example, may be alerted to the visitor's arrival. Other meeting invitees may also be notified, using the unique identifier assigned to their respective smartphones. -
FIG. 7 illustrates entry. Once thesecurity server 42 authorizes the visitor'ssmartphone 32, the corresponding visitor may enter the secure area. Thesecurity server 42 may thus generate anelectronic entry instruction 86 to allow physical entry. Theentry instruction 86 is then sent as packets of data to any destination device.FIG. 7 , for example, illustrates theentry instruction 86 routing to a network address assigned to alock controller 88. Thelock controller 88 manages anelectronic lock 90 securing some door or gate. Theentry instruction 86 instructs thelock controller 88 to activate or unlock theelectronic lock 90, thus allowing the visitor to physically enter thebuilding 24 and/or some floor within thebuilding 22. Thesecurity server 42 may further instruct anelevator controller 92 to summon anelevator 94, thus lifting the visitor to some floor or level, as later paragraphs will explain. Thesecurity server 42 may also monitor or track the movement of the visitor'ssmartphone 32 to prevent frolic or unauthorized detours (as later paragraphs will also explain). - Exemplary embodiments thus synchronize entry with wireless detection. Wireless detection of any
mobile device 30 may thus be used to authorize entry to secure areas. Even thoughFIGS. 1-7 primarily illustrate the visitor'ssmartphone 32, exemplary embodiments may utilize any wired or wireless device (as later paragraphs will explain). Indeed, badges, watches, and other wearable smart devices may be wirelessly detected to permit access. Integration with personnel directories and calendaring systems further defines permissible locations of visitors. -
FIGS. 8-10 are more detailed block diagrams illustrating the operating environment, according to exemplary embodiments.FIG. 8 illustrates presence detection of the visitor'ssmartphone 32. When thesmartphone 32 enters any area, thesmartphone 32 may establish wireless communication with thewireless network 40 serving the area. Thesmartphone 32, for example, may request access or permission to a local area wireless fidelity (or WI-FI®) network, wide area cellular network, or any other network. Thewireless network 40 may only recognize, or transmit/receive, using a particular frequency or band. Thesmartphone 32 may thus instruct its transceiver (not shown for simplicity) to wirelessly request access permission using the electromagnetic frequency band required by thewireless network 40. - The
security server 42 may be notified. When thewireless network 40 detects thesmartphone 32, exemplary embodiments may inform thesecurity server 42. That is, thesmartphone 32 may send an access request to anaccess device 100 serving thewireless network 40.FIG. 8 illustrates theaccess device 100 as awireless router 102, which commonly serves many residential and business WI-FI® networks. However, theaccess device 100 may be any network interface to an access network, such as a gateway, cable modem, or DSL modem. Regardless, thesmartphone 32 broadcasts a request that seeks access permission to thewireless network 40. When theaccess device 100 receives the access request, theaccess device 100 may send apacketized access notification 104 into acommunications network 106 for routing and delivery to a network address associated with thesecurity server 42. Thewireless router 102, for example, may store or execute code or programming that forces or commands theaccess notification 104 when any device attempts to access thewireless network 40. Theaccess notification 104 may thus alert thesecurity server 42 to the radio frequency presence of the visitor'ssmartphone 32. Theaccess notification 104 may further include information that uniquely identifies thesmartphone 32, such as data representing acellular identifier 110. While any alphanumeric combination may uniquely identify thesmartphone 32,FIG. 8 illustrates the smartphone's cellular telephone number (or “CTN”) 112, International Mobile Subscriber Identity (or “IMSI”) 114, or Mobile Station International Subscriber Directory Number (“MSISDN”) 116. Whenever themobile smartphone 32 sends messages or information, thesmartphone 32 may include or self-report itsCTN 112,IMSI 114, and/or itsMSISDN 116. - The
security server 42 may authorize thesmartphone 32. Thesecurity server 42 has a processor 120 (e.g., “μLP”), application specific integrated circuit (ASIC), or other component that executes asecurity algorithm 122 stored in alocal memory 124. Thesecurity algorithm 122 instructs theprocessor 120 to perform operations, such as receiving and processing information received from a network interface to thecommunications network 106. The information may be received as packets of data according to a packet protocol (such as any of the Internet Protocols). The packets of data contain bits or bytes of data describing the contents, or payload, of a message. A header of each packet of data may contain routing information identifying an origination address and/or a destination address. Thesecurity algorithm 122, for example, may instruct theprocessor 120 to inspect thepacketized access notification 104 for thecellular identifier 110 associated with the visitor'ssmartphone 32 requesting access to thewireless network 40. -
FIG. 9 illustrates thedatabase 44 of personnel. Thedatabase 44 of personnel may store names, addresses, images, and/or other information for personnel who are authorized to enter any area. For simplicity thedatabase 44 of personnel is illustrated as a table 130 that electronically maps, relates, or associates different employees ortenants 132 to their corresponding personal information. For example, an entry may associate each person'sname 134,address 136, and/oremployee number 138 to thecellular identifier 110 associated with the person's personal wireless device (such as thesmartphone 32 illustrated inFIGS. 1-8 ).FIG. 9 illustrates thecellular identifier 110 as the cellular telephone number (“CTN”) 112, theIMSI 114, and/or theMSISDN 116. Each person's wireless device, however, may be additionally or alternatively uniquely identified by a network address, a manufacturer's serial number, or any other alphanumeric combination. Moreover, thedatabase 44 of personnel may further associate adigital image file 140 to thecellular identifier 110, thus allowing retrieval, recognition, and/or analysis of a facial image. Thedatabase 44 of personnel is illustrated as being locally stored in thememory 124 of thesecurity server 42, but some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated asreference numeral 106 inFIG. 8 ). WhileFIG. 9 only illustrates a few entries, in practice thedatabase 44 of personnel may contain many entries for hundreds or thousands of people. - The
security server 42 may query thedatabase 44 of personnel. Returning toFIG. 8 , when thesecurity server 42 receives theaccess notification 104, thesecurity algorithm 122 causes theprocessor 120 to query for entries that match the query search term(s) detailed or described in theelectronic access notification 104. If thedatabase 44 of personnel contains a matching entry, then thesecurity server 42 may authorize the smartphone 32 (and thus the corresponding user or visitor) to enter. Thesecurity server 42 thus recognizes thesmartphone 32 as belonging to one of the personnel authorized to enter the building (illustrated asreference numeral 24 inFIGS. 1-7 ). As an example, if theCTN 112, theIMSI 114, and/or theMSISDN 116 matches an entry in thedatabase 44 of personnel, then thesecurity server 42 may conclude that the corresponding user of thesmartphone 32 is authorized to enter. -
FIG. 10 illustrates theentry instruction 86. When the visitor'ssmartphone 32 is recognized, thesecurity server 42 may automatically authorize entry. Thesecurity algorithm 122 may thus instruct theprocessor 120 to generate theentry instruction 86 to allow physical entry. Theentry instruction 86 may contain any information that confirms thesmartphone 32 is authorized to enter the secure area.FIG. 10 illustrates theentry instruction 86 routing to the network address assigned to thelock controller 88. Theentry instruction 86 instructs thelock controller 88 to activate or unlock theelectronic lock 90. Thesecurity server 42 may thus unlock a door, gate, or turnstile that permits physical entry of the corresponding user of thesmartphone 32. An employee or tenant thus enters based on the wireless recognition of thesmartphone 32. - Exemplary embodiments thus present an elegant solution. In today's mobile environment, people may be uniquely identified by their mobile devices (such as the smartphone 32). Employees, tenants, and visitors may thus be personally identified merely by carrying their smartphones. Exemplary embodiments may thus permit authorized entry to secure areas, simply by recognizing wireless transmissions from their mobile devices. No phone calls are needed, and labor expenses are reduced.
- Exemplary embodiments may be applied regardless of networking environment. Exemplary embodiments may be easily adapted to stationary or mobile devices having cellular, WI-FI®, near field, and/or BLUETOOTH® capability. Exemplary embodiments may be applied to mobile devices utilizing any portion of the electromagnetic spectrum and any signaling standard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band). Exemplary embodiments, however, may be applied to any processor-controlled device operating in the radio-frequency domain and/or the Internet Protocol (IP) domain. Exemplary embodiments may be applied to any processor-controlled device utilizing a distributed computing network, such as the Internet (sometimes alternatively known as the “World Wide Web”), an intranet, a local-area network (LAN), and/or a wide-area network (WAN). Exemplary embodiments may be applied to any processor-controlled device utilizing power line technologies, in which signals are communicated via electrical wiring. Indeed, exemplary embodiments may be applied regardless of physical componentry, physical configuration, or communications standard(s).
- Exemplary embodiments may utilize any processing component, configuration, or system. Any processor could be multiple processors, which could include distributed processors or parallel processors in a single machine or multiple machines. The processor can be used in supporting a virtual processing environment. The processor could include a state machine, application specific integrated circuit (ASIC), programmable gate array (PGA) including a Field PGA, or state machine. When any of the processors execute instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.
-
FIGS. 11-12 are schematics further illustrating thedatabase 46 of meetings, according to exemplary embodiments. Here thesmartphone 32 may be an invitee to a meeting within some secure area. When thewireless network 40 detects the radio presence of the visitor'ssmartphone 32, theaccess device 100 sends theaccess notification 105 to thesecurity server 42. Thepacketized access notification 104 may include data describing the cellular identifier 110 (e.g., theCTN 112, theIMSI 114, and/or the MSISDN 116). Thesecurity server 42 may then query thedatabase 46 of meetings to determine if thesmartphone 32 matches thelist 48 of invitees to any scheduledmeeting 50. -
FIG. 12 illustrates thedatabase 46 of meetings. For simplicity,FIG. 12 illustrates thedatabase 46 of meetings being locally stored in thememory 124 of thesecurity server 42. However, some or all of the database entries may be remotely maintained at some other server or location in the communications network (illustrated asreference numeral 106 inFIG. 11 ). WhileFIG. 12 only illustrates a few entries, in practice thedatabase 46 of meetings may contain many entries for hundreds or thousands of different meetings or gatherings. Thedatabase 46 of meetings is illustrated as a table 150 that maps, relates, or associates different scheduledmeetings 50 to thecorresponding list 48 of invitees. While eachinvitee 48 may be identified by their name, here exemplary embodiments identify eachinvitee 48 according to his or her mobile device identifier. That is, eachinvitee 48 may be identified by the uniquecellular identifier 110 associated with, or assigned to, their cellular device (such as the smartphone 32).FIG. 12 thus illustrates database associations between ameeting 50, an organizer orinviter 152, and thedifferent invitees 48. Each party to themeeting 50 may thus be uniquely identified by theirrespective CTN 112,IMSI 114, and/orMSISDN 116. Referring back toFIG. 11 , if an entry in thedatabase 46 of meetings matches the uniquecellular identifier 110 associated with thesmartphone 32, then the corresponding user may be authorized for entry to attend thecorresponding meeting 50. Thesecurity server 42 may thus authorize entry, such as by generating the entry instruction 86 (as illustrated with reference toFIG. 10 ). Supplier personnel, contractors, and other invitees may thus quickly and easily enter the building, based on wireless recognition of their smartphones. -
FIGS. 13-18 are schematics illustrating locational tracking, according to exemplary embodiments. Once thesmartphone 32 is authorized for entry, exemplary embodiments may monitor the movements of thesmartphone 32. If the visitor'ssmartphone 32 strays or frolics, a security concern may develop. Exemplary embodiments, then, may track thesmartphone 32 to ensure the user stays on route to themeeting 50. -
FIG. 13 , for example, illustrates room assignments. Here thedatabase 46 of meetings may also associate ameeting location 154 to eachmeeting 50. As the reader may realize, conference rooms, offices, beverage rooms, and auditoriums may be uniquely identified by some name and/or location. So, when themeeting 50 is scheduled or logged in thedatabase 46 of meetings, exemplary embodiments may further store an electronic database association with thecorresponding meeting location 154. -
FIG. 14 illustrates security routings. Once thelocation 154 of themeeting 50 is determined (from thedatabase 46 of meetings), thesecurity server 42 may query adatabase 160 of routings. Thedatabase 160 of routings storespredetermined building routes 162 from some beginning location (such as a point of entry 164) to the destination at themeeting location 154. Thedatabase 160 of routings, for example, may storedifferent routes 162 from the lobby of the building (illustrated, respectively, asreference numerals FIG. 1 ) to themeeting location 154 of the scheduledmeeting 50.FIG. 14 illustrates thedatabase 160 of routings as being locally stored in thesecurity server 42, but some or all of the electronic database entries may be remotely maintained at some other server or location in the communications network (illustrated asreference numeral 106 inFIG. 11 ). A particular conference room, for example, may have aroute 162 along which the visitor is only permitted to walk or navigate. That is, only certain paths along particular halls and/or through particular doors are available to the visitor. Thedatabase 160 of routings may thus store approvedroutes 162 along which employees, tenants, and/or visitors may move from any point (such as the entry 164) to the final destination at themeeting location 154. -
FIG. 15 illustrates GPS tracking. After the visitor'ssmartphone 32 is authorized for entry, the visitor should walk or travel along thepredetermined route 162 to thedestination meeting location 154. After all, confining the visitor to thepredetermined route 162 may help prevent rogue access to unauthorized locations. Exemplary embodiments, then, may track the visitor's position or progress along thepredetermined route 162.FIG. 15 thus illustratesGPS waypoints 170 along which thesmartphone 32 may or must report. That is, thepredetermined route 162 may be defined as a series of global positioning system information. As the visitor walks the corridors of the building, the visitor'ssmartphone 32 may continually, periodically, and/or randomly report itscurrent location 172.FIG. 15 illustrates thesmartphone 32 reporting itscurrent location 172 into thewireless network 40, which theaccess device 100 may forward to thesecurity server 42. Thecurrent location 172, however, may be routed into a cellular network for delivery to the network address associated with thesecurity server 42. Regardless, when thesecurity server 42 receives thecurrent location 172, thesecurity server 42 may compare thecurrent location 172 to theGPS waypoints 170 associated with themeeting location 154. If thecurrent location 172 matches one of the GPS waypoints (perhaps within a locational tolerance), then thesecurity algorithm 122 may conclude that the visitor'ssmartphone 32 is on track and proceeding as authorized. However, if thecurrent location 172 reported by the visitor'ssmartphone 32 fails to match one or any of theGPS waypoints 170, thesecurity algorithm 122 may generate asecurity notification 174. Thesecurity notification 174 may be any electronic message that warns the visitor to resume thepredetermined route 162 to thedestination meeting location 154. Thesecurity notification 174 may route back to theaccess device 100 for transmission to the network address assigned to thesmartphone 32. However, thesecurity notification 174 may be a short message service (SMS) text message that is sent to the uniquecellular identifier 110 of the visitor'ssmartphone 32. Thesecurity notification 174 may further include acorrection 176 that puts the visitor back on thepredetermined route 162 to thedestination meeting location 154. Moreover, thesecurity server 42 may also copy or forward thesecurity notification 174 to a device associated with a security guard for nearly immediate human intervention. -
FIG. 16 illustrates network tracking. Here exemplary embodiments may infer the location of the visitor'ssmartphone 32 using network recognition. As the reader may understand, GPS signals are sometimes not received in indoor environments. Exemplary embodiments, then, may additionally or alternatively infer the location of the visitor'ssmartphone 32 using network identifiers.FIG. 16 thus illustratesnetwork waypoints 180 along which thesmartphone 32 must request access permission. That is, thepredetermined route 162 may be defined as a series of network identifiers. For example, as the visitor walks the corridors of the building, the visitor'ssmartphone 32 may wirelessly encounter different wireless fidelity (WI-FI®) networks serving the different floors, hallways, and/or rooms. The visitor'ssmartphone 32 may also detect other identifiers of other networks (such as different cellular network cells). Regardless, thesmartphone 32 may request access permission to eachwireless network 40. Thecorresponding access device 100 may thus notify thesecurity server 42 using the access notification 104 (above explained with reference toFIG. 8 ).FIG. 16 , for simplicity, illustrates thenetwork waypoints 180 as aseries 182 of service set identifiers. Each individual service set identifier (or “SSID”) 184 uniquely identifiers a different WI-FI® network serving some portion of thepredetermined route 162 to thedestination meeting location 154. When thesecurity server 42 receives eachaccess notification 104, theaccess notification 104 may identify thecorresponding SSID 184. Thesecurity server 42 may thus compare theSSID 184 to thenetwork waypoints 180 associated with themeeting location 154. If theSSID 184 matches one of thenetwork waypoints 180, then thesecurity algorithm 122 may conclude that the visitor'ssmartphone 32 is on track and proceeding as authorized. However, if theSSID 184 fails to match one or any of thenetwork waypoints 180, thesecurity algorithm 122 may generate thesecurity notification 174 with the correction 176 (as earlier explained). -
FIG. 17 illustrates a strict comparison. As thesecurity server 42 receives eachaccess notification 104, thesecurity server 42 may require a strict sequential match with thenetwork waypoints 180. The visitor'ssmartphone 32, in other words, may be required to traverse thenetwork waypoints 180 in sequential order, from afirst entry SSID 190 to afinal destination SSID 192 serving thedestination meeting location 154. If the visitor'ssmartphone 32 strays from thepredetermined route 162, one of theaccess notifications 184 will identify anSSID 184 not matching the approvedroute 162. Thesmartphone 32, in other words, is requesting wireless access to an unauthorized network, thus revealing a frolic or detour. Thesecurity algorithm 122 may thus alert security (as earlier explained). -
FIG. 18 illustrates timing requirements. Here eachnetwork waypoint 180 may also have acorresponding timing parameter 200.FIG. 18 thus illustrates eachnetwork waypoint 180 as an SSID/time pairing. That is, eachnetwork waypoint 180 may be a network/timing pair of values associated with eachsuccessive wireless network 40. As the visitor'ssmartphone 32 travels along thepredetermined route 162, thesecurity server 42 may monitor a speed or time of movement. Eachaccess notification 104 may have atimestamp 202 that marks a time of requested access to the wireless network 40 (as identified by the SSID 184). As thesecurity server 42 sequentially compares theSSID 184 to thenetwork waypoints 180, thesecurity server 42 may also require strict adherence to eachcorresponding timing parameter 200. Thesecurity server 42, in other words, may initialize atimer 204 with receipt of theaccess notification 104. Thetimer 204 counts up or down to a final value at a receipt of anext access notification 104 associated with the same smartphone 32 (e.g., the cellular identifier 110). Thetimer 204, for example, may thus count a time in seconds or minutes betweensuccessive access notifications 104 sent fromdifferent access devices 100 along thepredetermined route 162. So, not only must eachsequential SSID 184 match thenetwork waypoints 180, but exemplary embodiments may also require timing compliance between thesuccessive network waypoints 180. Thesecurity server 42 may thus compare a current value of thetimer 204 to thetiming parameter 200 associated with a nextcorresponding network waypoint 182 along thepredetermined route 162. If the current value of thetimer 204 is less than or equal to thetiming parameter 200, then thesecurity algorithm 122 may conclude that the visitor'ssmartphone 32 is on the approvedroute 162 and on track to arrive on time at the finalmeeting destination location 154. However, if the current value of thetimer 204 exceeds thetiming parameter 200, thesecurity algorithm 122 may conclude that the visitor'ssmartphone 32 has strayed from thepredetermined route 162. Thesecurity algorithm 122 may thus alert security (as earlier explained). -
FIGS. 19-22 are schematics illustrating building services, according to exemplary embodiments. Here exemplary embodiments may coordinate or time various building services with respect to the location of thesmartphone 32. As thesmartphone 32 travels along the predetermined route 162 (as represented by the GPScurrent location 172, any of theGPS waypoints 170, theSSID 184, and/or any of the network waypoints 180), thesecurity server 42 may thus order up or coordinate various building services at appropriate times and locations.FIG. 19 , for example, illustrates adatabase 210 of services. Thedatabase 210 of services is illustrated as a table 212 that associatesdifferent locations 214 todifferent services 216. As the reader may understand, one of theservices 216 may belighting requirements 218 for eachdifferent location 214. As the user carries thesmartphone 32 through hallways and other areas, lights may need to be activated. So, as thesecurity server 42 is informed of the smartphone'slocation 214 along theroute 162, thesecurity server 42 may query thedatabase 210 of services for thecorresponding lighting requirements 218. - Lights may thus be defined. The
database 210 of services may thus store electronic database associations for the lights that illuminate thedifferent locations 214. Eachwireless network 40, for example, may be mapped to thelight fixtures 220 and/or lighting loads 222 (such as individual electrical circuits) illuminating its wireless service area. Whenever thesecurity server 42 receives theaccess notification 104, thesecurity server 42 may thus query for theSSID 184 and retrieve thelighting requirements 218 for its wireless service area. AsFIG. 19 further illustrates, electronic database associations may be defined for any GPS coordinates or waypoints along theroute 162. - As
FIG. 20 illustrates, the lights may be activated. Once thesecurity server 42 knows thelighting requirements 218 for thelocation 214, thesecurity server 42 may send alighting command 230 into thecommunications network 106 for delivery to the network address associated with alighting controller 232. Thelighting controller 232 responds by activating, or turning on, the correspondingphysical light fixture 234 and/or the physicalelectrical load 236. Thesecurity server 42 may thus coordinate the lights along thepredetermined route 162 for safety and security. Lights may then be deactivated when no mobile device requests wireless access to the corresponding wireless service area. Lights may also be deactivated after some passage of time. -
FIG. 21 illustrates HVAC services. Here exemplary embodiments may also coordinate heat or air conditioning with respect to thelocation 214 along the approvedroute 162. As the reader likely understands, as the user or visitor travels along the predetermined route 162 (as represented by the GPScurrent location 172, any of theGPS waypoints 170, theSSID 184, and/or any of the network waypoints 180), thesecurity server 42 may heat or cool the corresponding physical space or area. Indeed, thesecurity server 42 may even order up an ambient temperature within the destination meeting location (illustrated asreference numeral 154 inFIGS. 15-16 ). Thedatabase 210 of services may thus include entries forHVAC settings 240 associated with thelocation 214 along the approvedroute 162. For example, thesecurity server 42 may thus query thedatabase 210 of services for theSSID 184 and retrieve the corresponding HVAC settings 240 (such as atemperature 242 and/or humidity 244) associated with the corresponding physical space or area. Thesecurity server 42 may then send anHVAC command 246 into thecommunications network 106 for delivery to the network address associated with anHVAC system 248. Thesecurity server 42 may even receiveweather data 249 to further analyze and satisfy theHVAC settings 240 desired for the corresponding physical space or area. -
FIG. 22 illustrates other services. Exemplary embodiments may also coordinate many other services for the comfort and convenience of the invitees/attendees. Thedatabase 210 of services, for example, may also have entries for other services, such asnetwork access 250,equipment 252, andvending 254. Continuing with the above examples, thesecurity server 42 may query thedatabase 210 of services for theSSID 184 of themeeting location 154. Thesecurity server 42 may thus retrieve thecorresponding services 216 defined for thatmeeting location 214. Thesecurity server 42 may then generate an electronic, packetizedservice order 256 that routes to a network address of aservice provider system 258. For example, when each invitee arrives at thedestination meeting location 154, thesecurity server 42 may arrange or prearrangewireless network access 250 for each attendee's mobile wireless device. Thesecurity server 42, for example, knows theSSID 184 of the WI-FI® network serving the destination conference room, along with the uniquecellular identifier 110 of each attendee's wireless device (as explained with reference toFIGS. 11-14 ). Thesecurity server 42 may thus pre-authorize each attendee's wireless device for wireless service in the destination conference room. Any wireless access point, in other words, may be instructed to recognize the uniquecellular identifier 110 of each attendee's wireless device. Each attendee's device thus has immediate access to wireless services. - The
equipment 252 may also be ordered. Computers, projectors, conference phone set-up, pens, and whiteboards are just some of theequipment 252 that may be pre-ordered, based on thelocation 214. The meeting organizer (illustrated asreference numeral 152 inFIG. 12 ) may thus enter any data or description of theequipment 252 desired for the meeting. Thesecurity server 42 may thus pre-arrange arrival and set-up of theequipment 252. As the attendees enter thedestination meeting location 154, theequipment 252 they need is automatically ordered and waiting for use. - Vending 254 may also be pre-arranged. The meeting organizer may thus enter or request any food and drink for the meeting. The
security server 42 may thus issue orders or commands for on-time delivery of food and drink from some identified vendor. As the attendees enter thedestination meeting location 154, the requested food and drink is automatically ordered and waiting for consumption. -
FIG. 23 is a schematic illustrating elevator summons, according to exemplary embodiments. As thesmartphone 32 moves along thepre-approved route 162 to thedestination meeting location 154, at some point elevator service may be required. Exemplary embodiments may thus track the smartphone's movement and generate elevator commands at appropriate moments in time or location.FIG. 23 , for example, illustrates anelevator command 270 as adata triplet 271 inserted into one of thenetwork waypoints 180. Theelevator command 270 identifies which elevator (elevator number or identifier) is summoned for vertical travel from an entry floor to an exit floor. If a building only has one elevator, then perhaps theelevator command 270 may be simplified to a pair of data values. But many buildings may have multiple elevators, perhaps serving different floors. The elevator command (3, 1, 22), for example, may call or summon “Elevator # 3” to “Floor # 1” for lift service to “Floor # 22.” The opposite elevator command (3, 22, 1) would call “Elevator # 3” to “Floor # 22” for descend service to “Floor # 1.” Eachelevator command 270 may thus be generated for insertion into the pre-determinedsequential network waypoints 180. As thesmartphone 32 satisfied eachsequential network waypoint 180, thesecurity server 42 may summon the corresponding elevator in the sequence. Thesecurity algorithm 122 may further initialize thetimer 204 to count up or down until the summons. Exemplary embodiments, then, may insert theelevator command 270 at appropriate positions and/or times in thesequential network waypoints 180 and/or the sequential GPS waypoints (illustrated asreference numeral 170 inFIG. 15 ). As thesecurity server 42 tracks thesmartphone 32, thesecurity server 42 may thus read, retrieve, and/or execute theelevator command 270 as one of the sequential steps. Thesecurity server 42 may thus generate anelevator instruction 272 that is sent into thecommunications network 106 for delivery to the network address associated with theelevator controller 92. Elevator service may thus be summoned to coincide with the current location of thesmartphone 32. -
FIGS. 24-25 are schematics further illustrating thedatabase 70 of calendars, according to exemplary embodiments. When thewireless network 40 detects the radio presence of the visitor'ssmartphone 32, theaccess device 100 sends the access notification 104 (as earlier explained). Thesecurity server 42 may then query thedatabase 70 of calendars for a matching entry. Thedatabase 70 of calendars stores different electronic calendars for the different employees and/or tenants in the building.FIG. 25 , for example, illustrates thedatabase 70 of calendars as a table 280 that maps, relates, or associates differentelectronic calendars 72 todifferent invitees 282. As there may be hundreds of employees or tenants, thedatabase 70 of calendars may store a memory pointer or network address to an individual person'selectronic calendar 72. Regardless, when the visitor'ssmartphone 32 requests access to thewireless network 40, thedatabase 70 of calendars may be searched or queried for a matching entry. For example,FIG. 25 illustrates thedatabase 70 of calendars storing electronic database associations betweenelectronic calendar entries 72 and theirrespective invitees 282. Whenever a person schedules a meeting or telephone call, for example, the invitee may be uniquely identified by his or her uniquecellular identifier 110. An appointment in an electronic calendar, in other words, may be arranged or associated with theCTN 112, theIMSI 114, and/or theMSISDN 116 of aparticipant 282. - The
security server 42 may authorize entry. Referring back toFIG. 24 , when thesecurity server 42 receives theaccess notification 104, thesecurity server 42 may query thedatabase 70 of calendars for the visitor's uniquecellular identifier 110. If a matching entry is determined, thesecurity server 42 may permit physical entry, as the visitor is scheduled for an appointment with an employee or tenant. Moreover, if thedatabase 70 of calendars identifies themeeting location 154, thesecurity server 42 may further retrieve and monitor thepredetermine route 162 to the meeting location 154 (as this disclosure explains with reference toFIGS. 14-18 and 23 ). -
FIGS. 26-29 are schematics illustrating historical network tracking, according to exemplary embodiments. Here, historical observances of wireless detections may be used to infer future actions. That is, a user's habitual usage of thesmartphone 32 may be used to predict where she will move, and/or what she will do, based on her past movements and wireless network access. For example, as thesmartphone 32 repeatedly moves within thebuilding 24, over time exemplary embodiments may make recommendations and assumptions, based on habitual observance of its network usage. Whenever thesmartphone 32 is detected at some location or requesting access to any network, exemplary embodiments may match that detection to some past occurrence. In other words, most people are creatures of habit, so exemplary embodiments may predict our future movements and actions based on our historical behaviors. -
FIG. 26 illustrates adatabase 300 of usage. Thedatabase 300 of usage tracks historical usage of any user's wireless device 30 (such as the smartphone 32). Thedatabase 300 of usage may store entries related to usage at different times of days and/or at different locations. Whenever thesmartphone 32 reports its GPScurrent location 172, for example, exemplary embodiments may query thedatabase 300 of usage for historical usage at that same location. Thedatabase 300 of usage may thus log eachcurrent location 172 reported by thesmartphone 32. As thesmartphone 32 moves within thebuilding 24, thesmartphone 32 may repeatedly send its current location 172 (such as GPS information) to thesecurity server 42. Thesecurity server 42 may then log these locational reports in thedatabase 300 of usage. Thedatabase 300 of usage is illustrated as being locally stored within thesecurity server 42, but any of the database entries may be remotely maintained at other network-accessible locations or servers.FIG. 26 illustrates thedatabase 300 of usage as a table 302 that electronically maps, relates, or associates thecellular identifier 110 to different location reports. That is, each time thesmartphone 32 reports itscurrent location 172, thedatabase 300 of usage may add an entry for the uniquecellular identifier 110, the reportedcurrent location 172, and a date andtime 304 of the report. Over time, then, thedatabase 300 of usage may store long-term records of the movements of thesmartphone 32 within thebuilding 24. -
FIG. 27 illustrates historical network usage. Each time thesmartphone 32 requests access to thewireless network 40, thecorresponding access device 100 sends thepacketized access notification 104 to alert the security server 42 (as this disclosure earlier explained). Thesecurity server 42 may thus instruct thedatabase 300 of usage to log theaccess notification 104, perhaps also with the date andtime 304. That is, each time thesmartphone 32 requests wireless access to thewireless network 40, thedatabase 300 of usage may add an entry for the uniquecellular identifier 110, the service set identifier (“SSID”) 184 of the wireless fidelity (“WI-FI®”)network 40, and the date andtime 304 of the request. AsFIG. 27 illustrates, thedatabase 300 of usage may merely log thetimestamp 202 reported in theaccess notification 104, or thedatabase 300 of usage may log some other measure of time (such as receipt of the access notification 104). Regardless, over time thedatabase 300 of usage reveals a comprehensive long-term central repository of network access requested by thesmartphone 32. - The
security server 42 may thus infer future entries from the historical information. Thesecurity server 42, for example, may query thedatabase 300 of usage for any search terms and retrieve matching historical entries. Thesecurity server 42, as an example, may query for historical entries associated with thecellular identifier 110. Thesecurity server 42 may thus retrieve historical locations or networks logged in thedatabase 300 of usage. Indeed, thesecurity server 42 may even query for historical entries having the same or approximate date andtime 304. Thesecurity server 42 may thus retrieve historical entries that match the same or similar day, time,current location 172, ornetwork SSID 184. -
FIG. 28 illustrates locational prediction. Whenever thesmartphone 32 reports itscurrent location 172, thesecurity server 42 may predict or infer afuture location 310. For example, thesecurity server 42 may query for a series or sequence of entries having about thesame location 172 and/or the same date andtime 304. For example, if one or more of the smartphone's recent locational reports match one or more historical entries, then thesecurity algorithm 122 may infer that thesmartphone 32 is moving along a path historically observed. That is, thesmartphone 32 is being carried along a familiar route to a historical destination previously logged in thedatabase 300 of usage. In other words, if a recent string or sequence of locational reports matches some sequence of historical entries, then thesecurity algorithm 122 may conclude that thesmartphone 32 is traveling along the same route to the same destination. If thesmartphone 32 reports the samecurrent locations 172 within a ten minute (10 min.) window of time as historically seen, thesecurity server 42 may thus predict or infer that thesmartphone 32 will have thefuture location 310 that matches at least one of the historical entries in the same series. As one example, if the smartphone's most recent five (5) location reports match some historical observance in thedatabase 300 of usage, then thesecurity server 42 may predict the smartphone'sfuture location 310 will match the next historical sixth (6th) entry in the same historical sequence. Thesecurity server 42 may thus query for any search terms and retrieve one or multiple historical entries that match recent locational reports. As most people are creatures of habit, thesecurity server 42 may thus predict thefuture location 310 of thesmartphone 32 based on historical observances. -
FIG. 29 illustrates network prediction. As thedatabase 300 of usage may also log historical network requests, exemplary embodiments may predict or infer afuture network 312. For example, thesecurity algorithm 122 may predict the smartphone's access request to a wireless fidelity (“WI-FI®”) network, based on the historical entries in thedatabase 300 of usage. Thesecurity server 42 may query for a series or sequence of entries having one ormore matching SSID 184 entries and/or about the same date andtime 304. For example, if one or more of therecent access notifications 104 match one or more historical entries, then thesecurity algorithm 122 may infer that thesmartphone 32 is requesting access permissions along a path historically observed. In other words, if a recent string or sequence ofaccess notifications 104 matches some sequence of historical entries, then thesecurity algorithm 122 may conclude that thesmartphone 32 is requesting wireless access as historically seen. If a string orsequence 314 of theaccess notifications 104 match historical entries within a ten minute (10 min.)window 316 of time, thesecurity server 42 may thus predict or infer that thesmartphone 32 will request access to a next entry historically observed in the same series. AsFIG. 29 illustrates, if therecent access notifications 104 report thesequence 314 “SSID2, SSID3, SSID4, SSID3,” then thesecurity algorithm 122 may retrieve the next entry in thesame sequence 314 and predict that thesmartphone 32 will next request access to “SSID9.” Thesecurity algorithm 122, in other words, infers thefuture network 312 as the next entry in thematching sequence 314. Thesecurity algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction. -
FIG. 30 is another schematic illustrating network tracking, according to exemplary embodiments. Here exemplary embodiments may track usage or access requests to any networking environment. AsFIG. 30 illustrates, whenever thesmartphone 32 requests access to anywireless network 40, theaccess notification 104 may report the networking details. Theaccess notification 104, for example, may report aradio frequency 320 and/orbitrate 322 of communication between thesmartphone 32 and some other device (such as the access device 100). Thetimestamp 202 may be further added. When thesecurity server 42 receives theaccess notification 104, thesecurity algorithm 122 may thus log these details in thedatabase 300 of usage. For example, theradio frequency 320 and/orbitrate 322 may allow thesecurity algorithm 122 to log whether thewireless network 40 operates at cellular frequencies or WI-FI® frequencies. - Other networking environments may also be tracked. When the
security server 42 receives theaccess notification 104, theradio frequency 320 and/or thebitrate 322 may reveal near-field communications (“NFC”) and/or radio frequency identification (“RFID”) communications. For example, when thesmartphone 32 participates in near-field communication, theaccess notification 104 may additionally or alternatively report aninitiator device 324 and atarget device 326. Likewise, theaccess notification 104 may also detail unique radio frequency identification tags and readers. When thesecurity server 42 receives theaccess notification 104, thesecurity algorithm 122 may thus log these details in thedatabase 300 of usage. Over time, then, thedatabase 300 of usage contains historical entries detailing the NFC and RFID transactions involving thesmartphone 32. If any current transaction matches some historical entry, thesecurity algorithm 122 may predict or infer future actions and/or locations, based on the match. Thesecurity algorithm 122 may thus pre-arrange wireless access, elevator service, lighting, and other services based on this prediction. -
FIG. 31 is a schematic illustrating an overall database scheme, according to exemplary embodiments. Here thesecurity server 42 may access any of the databases (illustrated asreference numerals -
FIG. 32 is a schematic illustrating cancelations, according to exemplary embodiments. Even though thesecurity server 42 may have authorized access, coordinated services, and/or predicted actions, sometimes cancelations are determined. For example, a meeting organizer may simply cancel a scheduled meeting in thedatabase 46 of meetings. Thiscancelation 340 may then trickle down and affect access, services, and predictions. For example, if thecancelation 340 is determined in thedatabase 46 of meetings, thesecurity server 42 may disperse thatcancelation 340. The invitees' devices to the now-canceled meeting may be notified (perhaps using thenotification message 80 illustrated inFIG. 6 ). Entry authorization for the invitees' devices may be canceled by removal from thedatabase 46 of meetings and/or removal from thedatabase 70 of calendars. The entry instruction (illustrated asreference numeral 86 inFIG. 7 ) may be canceled, thus stopping or ceasing any entry process. The elevator instruction (illustrated asreference numeral 272 inFIG. 23 ) may be canceled, thus removing any summons for elevators. Likewise, any retrieval and/or analysis of routes in thedatabase 160 of routings may be canceled or aborted. Any retrieval and/or electronic order of services in thedatabase 210 of services may also be canceled or aborted. Moreover, electronic notifications of thecancelation 340 may be sent to service providers (such as contractors and vendors). Any historical analysis of entries in thedatabase 300 of usage may be halted or aborted. Thecancelation 340 may thus electronically cancel any reservation for a conference room, HVAC needs, and lighting requirements. -
FIG. 33 is a schematic illustrating conferencing activities, according to exemplary embodiments. Here exemplary embodiments may arrange and set-up a teleconference call and/or a telepresence video call between the visitor'ssmartphone 32 and other participants. When the visitor arrives, the visitor'ssmartphone 32 requests wireless access (as earlier explained). Thesecurity server 42 may thus use the uniquecellular identifier 110 to retrieve any meeting entries in thedatabase 46 of meetings and/or in thedatabase 70 of calendars. Thesecurity server 42 may arrange a conference room and/or an office or desk for the visitor, in response to a matching entry. Thesecurity server 42 may also automatically set-up a teleconference call or a videoconference call to the meeting invitee devices retrieved from thedatabase 46 of meetings and/or thedatabase 70 of calendars. Thesecurity server 42 may also concomitantly arrange video cameras, whiteboards, beverages, lighting, and other services (perhaps revealed by thedatabase 210 of services, as previously explained). -
FIGS. 34-35 are flowcharts illustrating an algorithm for access authorization, according to exemplary embodiments. A uniquecellular identifier 110 is received (Block 350) and thesecurity server 42 is notified (Block 352). A database is queried for the cellular identifier 110 (Block 354). Physical access to a secure area is granted, based on a matching entry in the database (Block 356). Theelectronic lock 90 may be activated to permit entry (Block 358). Theelectronic notification message 80 may be sent to a meeting organizer and/or other invitees, thus alerting to the arrival and access of the user associated with the cellular identifier (Block 360). Thelocation 154 of the meeting may also be determined (Block 362). - The flowchart continues with
FIG. 35 . Once thelocation 154 is known, the correspondingroute 162 retrieved (Block 364). Theelevator 94 may be summoned (Block 366). The correspondingservices 216 may also be retrieved (Block 368). Historical usage associated with thecellular identifier 110 is retrieved (Block 370). The future location 310 (Block 372) and/or the future network 312 (Block 374) may be predicted. Physical facilities are allocated based on the cellular identifier 110 (Block 376). -
FIG. 36 is a schematic illustrating still more exemplary embodiments.FIG. 36 is a more detailed diagram illustrating a processor-controlleddevice 400. As earlier paragraphs explained, exemplary embodiments may partially or entirely operate in any mobile or stationary processor-controlled device.FIG. 36 , then, illustrates thesecurity algorithm 122 stored in a memory subsystem of the processor-controlleddevice 400. One or more processors communicate with the memory subsystem and execute either, some, or all applications. Because the processor-controlleddevice 400 is well known to those of ordinary skill in the art, no further explanation is needed. -
FIG. 37 depicts other possible operating environments for additional aspects of the exemplary embodiments.FIG. 37 illustrates thesecurity algorithm 122 operating within various other processor-controlleddevices 400.FIG. 37 , for example, illustrates that thesecurity algorithm 122 may entirely or partially operate within a set-top box (“STB”) (402), a personal/digital video recorder (PVR/DVR) 404, a Global Positioning System (GPS)device 408, aninteractive television 410, atablet computer 412, or any computer system, communications device, or processor-controlled device utilizing the processor and/or a digital signal processor (DP/DSP) 414. Thedevice 400 may also include watches, radios, vehicle electronics, clocks, printers, gateways, mobile/implantable medical devices, and other apparatuses and systems. Because the architecture and operating principles of thevarious devices 400 are well known, the hardware and software componentry of thevarious devices 400 are not further shown and described. - Exemplary embodiments may be physically embodied on or in a computer-readable storage medium. This computer-readable medium, for example, may include CD-ROM, DVD, tape, cassette, floppy disk, optical disk, memory card, memory drive, and large-capacity disks. This computer-readable medium, or media, could be distributed to end-subscribers, licensees, and assignees. A computer program product comprises processor-executable instructions for automatic secure access, as the above paragraphs explained.
- While the exemplary embodiments have been described with respect to various features, aspects, and embodiments, those skilled and unskilled in the art will recognize the exemplary embodiments are not so limited. Other variations, modifications, and alternative embodiments may be made without departing from the spirit and scope of the exemplary embodiments.
Claims (20)
1. A method, comprising:
identifying, by a server, wireless waypoints along a group of authorized paths to be followed by a user of a wireless device to a destination within a secured area;
monitoring, by the server, communications of the wireless device; and
in response to any of the communications indicating that the wireless device is outside a distance threshold associated with the wireless waypoints along the group of authorized paths, generating, by the server, a security notification indicating the wireless device has strayed from the group of authorized paths.
2. The method of claim 1 , further comprising receiving, by the server, an access notification specifying at least one of the wireless waypoints.
3. The method of claim 1 , further comprising determining, by the server, a user associated with the wireless device.
4. The method of claim 1 , further comprising determining, by the server, a date associated with a destination network.
5. The method of claim 1 , further comprising determining, by the server, a time associated with a destination network.
6. The method of claim 1 , further comprising determining by the server, a calendar associated with the wireless device.
7. The method of claim 1 , further comprising sending, by the server, a notification associated with a destination network.
8. A system, comprising:
a processing system including a processor; and
a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising:
identifying wireless waypoints along a group of authorized paths to be followed by a user of a wireless device to a destination within a secured area, wherein the destination is served by a destination network;
monitoring communications of the wireless device; and
in response to any of the communications indicating that the wireless device is outside a distance threshold associated with the wireless waypoints along the group of authorized paths, generating a security notification indicating the wireless device has strayed from the group of authorized paths.
9. The system of claim 8 , wherein the operations further comprise:
identifying service set identifiers corresponding to the wireless waypoints; and
receiving a request to access a wireless network associated with one of the service set identifiers.
10. The system of claim 8 , wherein the operations further comprise determining a user associated with the wireless device.
11. The system of claim 8 , wherein the operations further comprise determining a date associated with the destination network.
12. The system of claim 8 , wherein the operations further comprise determining a time associated with the destination network.
13. The system of claim 8 , wherein the operations further comprise determining a calendar associated with the wireless device.
14. The system of claim 8 , wherein the operations further comprise sending an instruction to an electronic lock associated with the destination.
15. A non-transitory, machine-readable storage medium comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, the operations comprising:
identifying wireless waypoints along a group of authorized paths to be followed by a user of a wireless device to a destination within a secured area, wherein the destination is served by a destination network;
monitoring communications of the wireless device;
in response to any of the communications indicating that the wireless device is outside a distance threshold associated with the wireless waypoints along the group of authorized paths, generating a security notification indicating the wireless device has strayed from the group of authorized paths; and
providing an unlock instruction to an electronic lock associated with the destination network.
16. The non-transitory, machine-readable storage medium of claim 15 , wherein the operations further comprise:
identifying service set identifiers corresponding to the wireless waypoints; and
receiving a request to access a wireless network associated with one of the service set identifiers.
17. The non-transitory, machine-readable storage medium of claim 15 , wherein the operations further comprise determining a user associated with the wireless device.
18. The non-transitory, machine-readable storage medium of claim 15 , wherein the operations further comprise determining a date associated with the destination network.
19. The non-transitory, machine-readable storage medium of claim 15 , wherein the operations further comprise determining a time associated with the destination network.
20. The non-transitory, machine-readable storage medium of claim 15 , wherein the operations further comprise determining a calendar associated with the wireless device.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/982,576 US20230074312A1 (en) | 2015-03-24 | 2022-11-08 | Automatic physical access |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/666,356 US9972144B2 (en) | 2015-03-24 | 2015-03-24 | Automatic physical access |
US15/951,217 US10861266B2 (en) | 2015-03-24 | 2018-04-12 | Automatic physical access |
US17/069,362 US11521446B2 (en) | 2015-03-24 | 2020-10-13 | Automatic physical access |
US17/982,576 US20230074312A1 (en) | 2015-03-24 | 2022-11-08 | Automatic physical access |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/069,362 Continuation US11521446B2 (en) | 2015-03-24 | 2020-10-13 | Automatic physical access |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230074312A1 true US20230074312A1 (en) | 2023-03-09 |
Family
ID=56974243
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/666,356 Active 2035-05-02 US9972144B2 (en) | 2015-03-24 | 2015-03-24 | Automatic physical access |
US15/951,217 Active US10861266B2 (en) | 2015-03-24 | 2018-04-12 | Automatic physical access |
US17/069,362 Active 2035-06-17 US11521446B2 (en) | 2015-03-24 | 2020-10-13 | Automatic physical access |
US17/982,576 Abandoned US20230074312A1 (en) | 2015-03-24 | 2022-11-08 | Automatic physical access |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/666,356 Active 2035-05-02 US9972144B2 (en) | 2015-03-24 | 2015-03-24 | Automatic physical access |
US15/951,217 Active US10861266B2 (en) | 2015-03-24 | 2018-04-12 | Automatic physical access |
US17/069,362 Active 2035-06-17 US11521446B2 (en) | 2015-03-24 | 2020-10-13 | Automatic physical access |
Country Status (1)
Country | Link |
---|---|
US (4) | US9972144B2 (en) |
Families Citing this family (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9049176B2 (en) * | 2011-06-22 | 2015-06-02 | Dropbox, Inc. | File sharing via link generation |
EP2984529B1 (en) * | 2013-04-12 | 2020-08-12 | KONE Corporation | Building automation system control apparatus, method and computer program for providing control signalling |
US10296851B2 (en) | 2015-04-11 | 2019-05-21 | At&T Intellectual Property I, L.P. | Automatic allocation of physical facilities for maximum collaboration |
US9582841B2 (en) | 2015-03-24 | 2017-02-28 | At&T Intellectual Property I, L.P. | Location based emergency management plans |
US9972144B2 (en) | 2015-03-24 | 2018-05-15 | At&T Intellectual Property I, L.P. | Automatic physical access |
US9824515B2 (en) * | 2015-03-24 | 2017-11-21 | At&T Intellectual Property I, L.P. | Automatic calendric physical access |
CN108027991B (en) * | 2015-09-07 | 2022-01-14 | 通力股份公司 | Method and system for controlling access in an environment |
US10217306B2 (en) * | 2015-10-13 | 2019-02-26 | Sears Brands, L.L.C. | Smart home delivery services |
US20170214802A1 (en) * | 2016-01-22 | 2017-07-27 | DropBy, Inc. | Door entry systems and methods |
US20170249793A1 (en) * | 2016-02-25 | 2017-08-31 | Dean Drako | Unattended physical delivery access method and control system |
CA3040171A1 (en) | 2016-10-19 | 2018-04-26 | Dormakaba Usa Inc. | Electro-mechanical lock core |
US10075838B2 (en) * | 2016-11-28 | 2018-09-11 | Microsoft Technology Licensing, Llc | Smart discovery of wireless receivers |
US10486937B2 (en) | 2017-03-31 | 2019-11-26 | Otis Elevator Company | User management of door and elevator access control |
JP6919280B2 (en) * | 2017-03-31 | 2021-08-18 | 富士通株式会社 | Function management system and function management method |
US10157512B2 (en) | 2017-03-31 | 2018-12-18 | Otis Elevator Company | Group access management for visitor control |
US10665047B1 (en) | 2017-04-28 | 2020-05-26 | 1 Micro, LLC | Methods and apparatus for accessing secured physical assets |
CN110869984A (en) * | 2017-07-14 | 2020-03-06 | 开利公司 | Intent-driven building occupancy path and system interaction optimization |
CN111213186B (en) * | 2017-08-18 | 2022-11-15 | 开利公司 | Method for creating building paths for building occupants based on historical information |
ES2927419T3 (en) | 2017-09-08 | 2022-11-07 | Dormakaba Usa Inc | Electromechanical lock cylinder |
US10417846B1 (en) * | 2017-11-08 | 2019-09-17 | Securus Technologies, Inc. | Controlled environment facility visitation system using personal devices |
CN112752891B (en) | 2018-04-13 | 2022-08-05 | 多玛卡巴美国公司 | Electromechanical lock core |
US11466473B2 (en) | 2018-04-13 | 2022-10-11 | Dormakaba Usa Inc | Electro-mechanical lock core |
US20190325677A1 (en) * | 2018-04-24 | 2019-10-24 | Carrier Corporation | Home security system with automatic authorization functionality |
US11184453B2 (en) * | 2020-04-13 | 2021-11-23 | Synamedia Limited | Systems and methods for managing content in a network |
US11128636B1 (en) | 2020-05-13 | 2021-09-21 | Science House LLC | Systems, methods, and apparatus for enhanced headsets |
CN113129498A (en) * | 2021-06-16 | 2021-07-16 | 湖南中惠旅智能科技有限责任公司 | Face recognition method and system based on intelligent scenic spot |
CN113689603A (en) * | 2021-08-20 | 2021-11-23 | 青岛海信智慧生活科技股份有限公司 | Access control authority management method and device |
US11935349B2 (en) * | 2021-10-29 | 2024-03-19 | Ricoh Company, Ltd. | Managing access to physical areas based on captured digital data and a database |
US11749042B2 (en) * | 2021-11-15 | 2023-09-05 | Kevin DeMattio | Access control smart system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070247366A1 (en) * | 2003-10-22 | 2007-10-25 | Smith Derek M | Wireless postion location and tracking system |
US20090027165A1 (en) * | 2007-07-27 | 2009-01-29 | Lucomm Technologies, Inc. | Systems and methods for object localization and path identification based on rfid sensing |
US9563991B2 (en) * | 2013-03-05 | 2017-02-07 | Apple Inc. | Dynamically authorizing access to restricted areas |
Family Cites Families (110)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6819933B1 (en) | 1997-01-15 | 2004-11-16 | Sbc Technology Resources, Inc. | Communications system having pre-defined calling group |
JP4064521B2 (en) | 1998-04-07 | 2008-03-19 | 東芝ソリューション株式会社 | Iriyama management system |
US20020169539A1 (en) | 2001-03-28 | 2002-11-14 | Menard Raymond J. | Method and system for wireless tracking |
US6666582B2 (en) | 2000-01-03 | 2003-12-23 | Gkn Sinter Metals, Inc. | Siamese bolt holes in powder metal components |
US7366522B2 (en) | 2000-02-28 | 2008-04-29 | Thomas C Douglass | Method and system for location tracking |
US7035650B1 (en) | 2000-06-14 | 2006-04-25 | International Business Machines Corporation | System and method for providing directions |
US7315949B1 (en) | 2000-06-24 | 2008-01-01 | Palm, Inc. | Method and system for providing a personal identification security feature to a portable computing device |
US20020164993A1 (en) * | 2000-12-12 | 2002-11-07 | Elliot Nicolas F. | Method and system for locating and tracking a mobile device |
US7130630B1 (en) | 2000-12-19 | 2006-10-31 | Bellsouth Intellectual Property Corporation | Location query service for wireless networks |
US7308263B2 (en) | 2001-02-26 | 2007-12-11 | Kineto Wireless, Inc. | Apparatus for supporting the handover of a telecommunication session between a licensed wireless system and an unlicensed wireless system |
MXPA04003609A (en) | 2001-10-17 | 2004-07-27 | Nokia Corp | Method for the provision of location information. |
US20030103075A1 (en) | 2001-12-03 | 2003-06-05 | Rosselot Robert Charles | System and method for control of conference facilities and equipment |
JP4199475B2 (en) | 2002-04-11 | 2008-12-17 | 日本電気株式会社 | Positioning gateway device, terminal location information request processing method and program |
US8611919B2 (en) * | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
JP2004127142A (en) | 2002-10-07 | 2004-04-22 | Hitachi Ltd | Authentication method and system and entrance/exit management method and system using the method and system |
WO2004028121A2 (en) * | 2002-09-23 | 2004-04-01 | Wimetrics Corporation | System and method for wireless local area network monitoring and intrusion detection |
US6721652B1 (en) * | 2002-11-22 | 2004-04-13 | Electronic Data Systems Corporation (EDS) | Implementing geo-fencing on mobile devices |
US7493140B2 (en) * | 2003-01-22 | 2009-02-17 | Johnson Controls Technology Company | System, method and device for providing communication between a vehicle and a plurality of wireless devices having different communication standards |
US7151939B2 (en) | 2003-02-18 | 2006-12-19 | Qualcomm Incorporated | Method, apparatus, and machine-readable medium for providing indication of location service availability and the quality of available location services |
US7154379B2 (en) | 2003-03-13 | 2006-12-26 | Reed David L | Premise evacuation system |
JP2007526445A (en) | 2003-06-06 | 2007-09-13 | メッシュネットワークス インコーポレイテッド | System and method for identifying floor number with firefighter in need of rescue using received signal strength indication and signal propagation time |
EP1513290B1 (en) | 2003-09-03 | 2006-07-12 | Alcatel | Mobile terminal location in a WLAN through access point registration |
US7016693B2 (en) | 2004-01-06 | 2006-03-21 | Nokia Corporation | Method and apparatus for reporting location of a mobile terminal |
US8836580B2 (en) | 2005-05-09 | 2014-09-16 | Ehud Mendelson | RF proximity tags providing indoor and outdoor navigation and method of use |
US7245900B1 (en) | 2005-08-24 | 2007-07-17 | Sprint Spectrum L.P. | Method and system for using basic service set identifiers (BSSIDs) for emergency services routing |
JP2007060370A (en) | 2005-08-25 | 2007-03-08 | Sumitomo Electric Ind Ltd | Portable communication terminal, evacuation route display system, and danger broadcast device |
CN1925667B (en) | 2005-08-29 | 2011-04-20 | 国际商业机器公司 | Wireless planning method and equipment for ascertaining arrangement mode of base station in indoor environment |
KR101085700B1 (en) | 2005-09-16 | 2011-11-22 | 삼성전자주식회사 | Method for providing location information service in lbs provider and method for receiving location information service in requester terminal |
US8874145B2 (en) | 2006-08-02 | 2014-10-28 | Telecommunication Systems, Inc. | Personal location code broker |
US8040216B2 (en) | 2006-09-21 | 2011-10-18 | Ubiquity Holdings, Inc. | Virtual entry assistant using automated greeter |
US7917155B2 (en) | 2006-10-27 | 2011-03-29 | Roundtrip Llc | Location of cooperative tags with personal electronic device |
US9135612B1 (en) | 2011-04-17 | 2015-09-15 | Proctor Consulting, LLC | Proximity detection, virtual detection, or location based triggering of the exchange of value and information |
GB2446421B (en) * | 2007-02-09 | 2011-06-22 | Proctor & Stevenson Ltd | Tracking web server |
US7898419B2 (en) | 2007-07-27 | 2011-03-01 | Lucomm Technologies, Inc. | Systems and methods for object localization and path identification based on RFID sensing |
US8422987B2 (en) | 2007-12-28 | 2013-04-16 | Motorola Solutions, Inc. | Prompting and directing users to safety during emergency situations |
US20090177336A1 (en) * | 2008-01-07 | 2009-07-09 | Mcclellan Scott | System and Method for Triggering Vehicle Functions |
JP5063408B2 (en) | 2008-02-26 | 2012-10-31 | キヤノン株式会社 | Management device, control method and program |
US8190118B2 (en) | 2008-03-26 | 2012-05-29 | At&T Mobility Ii Llc | Integration of emergency alert information |
DE202008005467U1 (en) | 2008-04-18 | 2009-08-27 | Rittal Gmbh & Co. Kg | Position monitoring device for persons |
JP4601684B2 (en) | 2008-04-25 | 2010-12-22 | シャープ株式会社 | Evacuation route acquisition system, portable terminal device, evacuation route acquisition method, evacuation route acquisition program, computer-readable recording medium |
US20100069086A1 (en) | 2008-09-17 | 2010-03-18 | Sony Ericsson Mobile Communications Ab | Mobile Terminals Providing Network-Based Location Data, and Methods and Computer Program Product for Operating the Same |
US8126450B2 (en) * | 2008-09-24 | 2012-02-28 | Embarq Holdings Company Llc | System and method for key free access to a vehicle |
US8787871B2 (en) | 2008-12-02 | 2014-07-22 | International Business Machines Corporation | System and method for calculating and disseminating intelligent evacuation routes based on location awareness and integrated analytics |
US8749392B2 (en) | 2008-12-30 | 2014-06-10 | Oneevent Technologies, Inc. | Evacuation system |
EP2237234A1 (en) | 2009-04-03 | 2010-10-06 | Inventio AG | Method and device for access control |
JP5531461B2 (en) | 2009-06-19 | 2014-06-25 | 富士ゼロックス株式会社 | Document processing apparatus, document processing program, and document flow system |
HU227600B1 (en) | 2009-06-23 | 2011-09-28 | Attila Angyal | Wireless method of tracking and registering mobile units moving in definite zones |
GB2474007A (en) | 2009-08-27 | 2011-04-06 | Simon R Daniel | Communication in and monitoring of a disaster area, optionally including a disaster medical pack |
JP5258865B2 (en) | 2009-11-05 | 2013-08-07 | サムソン エスディーエス カンパニー リミテッド | Wireless device location tracking system and method using wireless LANAP |
US8401514B2 (en) | 2009-12-03 | 2013-03-19 | Osocad Remote Limited Liability Company | System and method for controlling an emergency event in a region of interest |
NZ601156A (en) | 2010-01-19 | 2014-09-26 | Synaptic Wireless Llc | Electronic locking system with wireless update and cascade lock control |
US8559979B2 (en) | 2010-04-01 | 2013-10-15 | Sony Corporation | Mobile terminal, location-based service server, and information providing system |
EP2586269B1 (en) | 2010-04-22 | 2019-05-15 | Zipit Wireless, Inc. | System and method for administration and operation of one or more mobile electronic communications devices |
CN103119470B (en) | 2010-07-21 | 2015-09-16 | 韩国贸易信息通信株式会社 | Carry out the system and method for the position-based service of indoor navigation |
CN102058939A (en) | 2010-08-18 | 2011-05-18 | 清华大学 | Method and system for evaluating building fire situation and instructing evacuation |
US8922433B2 (en) | 2010-08-27 | 2014-12-30 | Alcatel Lucent | Unsupervised learning and location systems for tracking in wireless communication systems |
US8669844B2 (en) | 2010-09-23 | 2014-03-11 | Blackberry Limited | Radio frequency identification (RFID) system providing meeting room reservation and scheduling features and related methods |
US8670752B2 (en) | 2010-09-24 | 2014-03-11 | At&T Intellectual Property I, L.P. | Providing integrated service-entity premium communication services |
KR101076050B1 (en) | 2010-09-29 | 2011-10-26 | 주식회사 세나테크놀로지 | Helmet for bluetooth headset with function of intercom |
JP2012087462A (en) | 2010-10-15 | 2012-05-10 | Miwa Lock Co Ltd | Entrance management system |
US8504062B2 (en) | 2010-11-01 | 2013-08-06 | Wavemarket, Inc. | System and method for aggregating and associating mobile device location data |
US20140002236A1 (en) * | 2010-12-02 | 2014-01-02 | Viscount Security Systems Inc. | Door Lock, System and Method for Remotely Controlled Access |
US8509807B2 (en) | 2010-12-15 | 2013-08-13 | At&T Mobility Ii Llc | Location reporting responsive to transitions in motional state of wireless equipment |
US8519845B2 (en) | 2010-12-16 | 2013-08-27 | King Fahd University Of Petroleum And Minerals | System and method for tracking people |
MX2013011116A (en) | 2011-03-29 | 2013-10-17 | Inventio Ag | Distribution of premises access information. |
US8320939B1 (en) * | 2011-04-21 | 2012-11-27 | Google Inc. | Crowd-sourced information for interior localization and navigation |
US20120280789A1 (en) | 2011-05-02 | 2012-11-08 | Apigy Inc. | Systems and methods for controlling a locking mechanism using a portable electronic device |
JP5755523B2 (en) | 2011-07-11 | 2015-07-29 | 株式会社Nttドコモ | Mobile communication terminal and information providing method |
CN103918285A (en) | 2011-11-14 | 2014-07-09 | 汤姆逊许可公司 | Dynamic evacuation information delivery to mobile devices |
EP2783497A1 (en) | 2011-11-24 | 2014-10-01 | Telefonaktiebolaget LM Ericsson (Publ) | System and method for maintaining location information in a database |
US9875590B2 (en) | 2011-12-30 | 2018-01-23 | Consumer 2.0, Inc. | Automated entry |
WO2013130032A1 (en) | 2012-02-27 | 2013-09-06 | Otis Elevator Company | Elevator control system |
US20130262223A1 (en) | 2012-03-28 | 2013-10-03 | Informat Innovative Technologies Ltd. | Indoor navigation system |
US9578115B2 (en) | 2012-06-15 | 2017-02-21 | Qualcomm Incorporated | Indoor location server provision and discovery |
KR101272357B1 (en) | 2012-09-24 | 2013-06-07 | 이한승 | System for providing multi-service by using smart terminal at hotel |
US9363214B2 (en) | 2012-11-29 | 2016-06-07 | Ricoh Company, Ltd. | Network appliance architecture for unified communication services |
CN103068039B (en) | 2012-12-17 | 2015-04-22 | 华南理工大学 | Wireless fidelity (WIFI) signal-based locating method for received signal strength indicator (RSSI) values |
US20140222562A1 (en) | 2013-02-04 | 2014-08-07 | Qualcomm Incorporated | Location based dynamic coupons |
DE102013201873B4 (en) | 2013-02-05 | 2017-09-21 | Siemens Schweiz Ag | Dynamic emergency assistance |
US20140235266A1 (en) | 2013-02-16 | 2014-08-21 | Qualcomm Incorporated | Focused assistance data for WiFi access points and femtocells |
US9171450B2 (en) | 2013-03-08 | 2015-10-27 | Qualcomm Incorporated | Emergency handling system using informative alarm sound |
US9226125B2 (en) | 2013-03-14 | 2015-12-29 | Google Technology Holdings LLC | Method and apparatus for alert message reception |
EP2779117A1 (en) | 2013-03-15 | 2014-09-17 | Inventio AG | Access control for areas with multiple doors |
US8989776B2 (en) | 2013-03-22 | 2015-03-24 | Alcatel Lucent | Location aggregation system |
FR3009159B1 (en) | 2013-07-26 | 2017-06-23 | Inst Mines Telecom | METHOD FOR PROCESSING GEOLOCATION DATA |
US20150045054A1 (en) | 2013-08-09 | 2015-02-12 | Qualcomm Incorporated | Systems and Methods for Floor Determination of Access Points in Indoor Positioning Systems |
US9763086B2 (en) | 2013-08-27 | 2017-09-12 | Qualcomm Incorporated | Owner access point to control the unlocking of an entry |
US9332476B2 (en) | 2013-10-04 | 2016-05-03 | Blackberry Limited | Method and apparatus to correct indoor positioning by utilizing Wi-Fi handovers |
WO2015059259A1 (en) | 2013-10-25 | 2015-04-30 | Koninklijke Philips N.V. | Task assignment method, computer program product and task assignment system |
US9813992B2 (en) | 2013-12-06 | 2017-11-07 | Mcp Llc | Tracking systems and methods for remotely tracking a location of a person on a map of a monitored premise |
US9717065B2 (en) | 2013-12-20 | 2017-07-25 | Apple Inc. | Indoor remote triggered location scanning |
US20150179012A1 (en) | 2013-12-24 | 2015-06-25 | Pathway IP SARL | Room access control system |
US9754443B2 (en) | 2014-02-13 | 2017-09-05 | Bally Gaming, Inc. | System and method for remote control gaming sessions using a mobile device |
DE102014002736A1 (en) * | 2014-03-04 | 2015-09-10 | Ecos Systems Gmbh | Access and monitoring system and procedures |
CN103780867B (en) | 2014-03-03 | 2018-03-23 | 深圳卓虹通讯电子有限公司 | Building gate access inter-speaking and advertising device and system |
EP2924944B1 (en) | 2014-03-25 | 2018-03-14 | Telia Company AB | Network authentication |
US20150327039A1 (en) | 2014-05-07 | 2015-11-12 | Verizon Patent And Licensing Inc. | Method and apparatus for providing event investigation through witness devices |
GB2526157A (en) | 2014-05-17 | 2015-11-18 | John Christian Scott | Monitoring system and method |
US20150350848A1 (en) * | 2014-05-30 | 2015-12-03 | Ebay Inc. | Remote monitoring of users at a home location |
US9532166B2 (en) | 2014-08-06 | 2016-12-27 | International Business Machines Corporation | Transaction based temporary and secure access |
US9468020B2 (en) | 2014-09-19 | 2016-10-11 | Cable Television Laboratories, Inc. | Network traffic prioritization |
US9530304B2 (en) | 2014-10-30 | 2016-12-27 | International Business Machines Corporation | Distributed sensor network |
US9565541B2 (en) | 2014-12-29 | 2017-02-07 | Iridium Satellite Llc | Emergency communications from a local area network hotspot |
JP2016130899A (en) | 2015-01-13 | 2016-07-21 | 株式会社リコー | Information processing apparatus, information processing system, and program |
US9972144B2 (en) | 2015-03-24 | 2018-05-15 | At&T Intellectual Property I, L.P. | Automatic physical access |
US9824515B2 (en) | 2015-03-24 | 2017-11-21 | At&T Intellectual Property I, L.P. | Automatic calendric physical access |
US10296851B2 (en) | 2015-04-11 | 2019-05-21 | At&T Intellectual Property I, L.P. | Automatic allocation of physical facilities for maximum collaboration |
US9582841B2 (en) | 2015-03-24 | 2017-02-28 | At&T Intellectual Property I, L.P. | Location based emergency management plans |
US20170019755A1 (en) | 2015-07-16 | 2017-01-19 | WhereibleGPS | Self-Adjusting Environmental Behavioral System for GPS/Cellular Locator |
KR102488461B1 (en) | 2015-11-24 | 2023-01-13 | 엘지전자 주식회사 | Flexible display device and operating method thereof |
-
2015
- 2015-03-24 US US14/666,356 patent/US9972144B2/en active Active
-
2018
- 2018-04-12 US US15/951,217 patent/US10861266B2/en active Active
-
2020
- 2020-10-13 US US17/069,362 patent/US11521446B2/en active Active
-
2022
- 2022-11-08 US US17/982,576 patent/US20230074312A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070247366A1 (en) * | 2003-10-22 | 2007-10-25 | Smith Derek M | Wireless postion location and tracking system |
US20090027165A1 (en) * | 2007-07-27 | 2009-01-29 | Lucomm Technologies, Inc. | Systems and methods for object localization and path identification based on rfid sensing |
US9563991B2 (en) * | 2013-03-05 | 2017-02-07 | Apple Inc. | Dynamically authorizing access to restricted areas |
Also Published As
Publication number | Publication date |
---|---|
US10861266B2 (en) | 2020-12-08 |
US20160284139A1 (en) | 2016-09-29 |
US9972144B2 (en) | 2018-05-15 |
US11521446B2 (en) | 2022-12-06 |
US20210027561A1 (en) | 2021-01-28 |
US20180232972A1 (en) | 2018-08-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11521446B2 (en) | Automatic physical access | |
US10269195B2 (en) | Automatic physical access | |
US20210304085A1 (en) | Automatic allocation of physical facilities | |
US10959079B2 (en) | Route management | |
US11775938B2 (en) | Lobby management system | |
US10490000B2 (en) | Methods and systems for access control and awareness management | |
KR102494560B1 (en) | Method for providing a visitor controlled access into a building | |
US9424699B2 (en) | Electronic access control and location tracking system | |
US9437063B2 (en) | Methods and systems for multi-unit real estate management | |
US12027000B2 (en) | Electronic access control and location tracking system | |
US20220327438A1 (en) | Hot-desking station and system | |
EP3510566A1 (en) | Methods and systems for access control and awareness management | |
US20200226550A1 (en) | Method to determine optimal meeting location and time | |
US10832508B2 (en) | Intent driven building occupant path and system interaction optimization | |
CN114868163A (en) | Building system for private user communication |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HARP, GREGORY O.;KLEIN, CRAIG ARTHUR;SINEATH, JOSEPH ERIC;SIGNING DATES FROM 20150323 TO 20150324;REEL/FRAME:061836/0830 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |