System and method for protecting a facility

Abstract

A directional positioning system for use in a facility having rooms, hallways, and other areas can include a plurality of portable units carried or worn by selected users in the facility, a plurality of fixed units installed at each of a plurality of locations within the facility, and a management unit. At least one portable unit can include at least one button that, when pressed, sends a signal in the event of an emergency. At least one fixed unit can include a display for indicating a direction of movement during an emergency. The management unit can be configured to be monitored by a security personnel and can be configured to receive any signals sent from any of the plurality of portable units or any of the plurality of fixed units. The plurality of portable units, the plurality of fixed units, and the management unit can form a mesh network.

Description

[0001] Priority requirements

[0002] This application is the national phase application of PCT / US2020 / 042046, filed on July 15, 2020, claiming priority to U.S. Provisional Application No. 62 / 874,113, filed on July 15, 2019, both of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to security systems, and more specifically, to methods and systems for protecting facilities such as school buildings or any similar structures. Furthermore, embodiments of this disclosure relate to systems and methods for tracking the location of individuals for applications such as infection response, contact tracing, general security systems, and other similar situations. In some embodiments, the location may be indoors, outdoors, or a combination of both. Additionally, embodiments of this disclosure relate to methods for determining and assessing the level of exposure to and transmission of infectious diseases. Background Technology

[0004] In U.S. Patent Application Publication No. 2012 / 0212339, Goldblatt disclosed a concealed personal alarm device and method. In U.S. Patent Application Publication No. 2007 / 0077959, Newman et al. disclosed an electronic locator. In U.S. Patent No. 7,751,285, Cain disclosed a customizable and wearable device for electronic imaging. In U.S. Patent No. 7,880,610, Tanner et al. disclosed a system and method for providing emergency commands. In U.S. Patent No. 8,384,549, Lemmon disclosed an event communication system for providing user alerts. In U.S. Patent Application Publication No. 2007 / 0296575, Eisold et al. disclosed a disaster alarm device, system, and method. In U.S. Patent No. 6,822,568, Gehlot et al. disclosed a spatial area network. In U.S. Patent No. 3,694,579, McMurray disclosed a digital communication system for emergency reporting. In Canadian Patent No. CA2,308,577, Shamm Ahmad discloses a security and emergency alarm system. In WIPO International Publication No. WO2014 / 132272, Anand Sundararaj discloses a method and system for optimal emergency communication.

[0005] While these devices may be suitable for the purposes in which they were designed, they would not be suitable for the purposes of this disclosure as described below. As will be shown in the explanations and drawings, this disclosure is practiced in a novel manner and differs from related technologies. Summary of the Invention

[0006] According to one aspect of this disclosure, a directional positioning system for use in a facility having rooms, corridors, and other areas may include multiple portable units carried or worn by selected users within the facility; multiple fixed units installed at each of multiple locations within the facility; and a management unit. At least one portable unit may include at least one button for sending a signal for a specific type of emergency when pressed. At least one fixed unit may include a display for indicating direction of movement during an emergency. The management unit may be configured to be monitored by security personnel and may be configured to receive any signals transmitted from any of the multiple portable units or any of the multiple fixed units. The multiple portable units, the multiple fixed units, and the management unit may form a mesh network.

[0007] In some embodiments, each of the plurality of portable units, each of the plurality of fixed units, and the management unit may wirelessly communicate with all other units in the mesh network and may be configured to receive all signals. In some embodiments, each of the plurality of portable units, each of the plurality of fixed units, and the management unit may be configured to interact with all other units in the mesh network. In some embodiments, at least one portable unit may be a full-function unit. A full-function unit may include multiple buttons. Each button may be associated with a directional command.

[0008] In some embodiments, in response to a pressed button on a full-function unit, at least a portion of the plurality of fixed units may be configured to receive a signal associated with the button from the full-function unit; and to illuminate at least one light on a display based on a directional command associated with the button. In some embodiments, at least a portion of the plurality of portable units may be configured to broadcast information to a management unit at a first predefined frequency when fixed.

[0009] In some embodiments, at least a portion of the plurality of portable units may be configured to broadcast information to a management unit at a second predefined frequency in response to a button being pressed, wherein pressing the button sends a signal related to a specific type of emergency, and the second frequency is greater than a first frequency. In some embodiments, at least a portion of the plurality of portable units may be configured to broadcast information to a management unit at a first frequency in response to a deactivation signal from the management unit. In some embodiments, the information may include at least one ID associated with the portable unit; a location associated with the portable unit; a name associated with the portable unit; or a role associated with the portable unit. In some embodiments, at least one of the plurality of portable units may be configured to broadcast information to the management unit at a frequency higher than the first frequency while in motion.

[0010] According to another aspect of this disclosure, a location alarm system for use in a facility having rooms, corridors, and other areas may include a first plurality of portable units carried or worn by a first group of selected users in the facility; a second plurality of portable units carried or worn by a second group of selected users in the facility; a plurality of fixed units installed at each of a plurality of locations within the facility; and a management unit. Each of the first plurality of portable units may include a plurality of buttons and a plurality of LEDs associated with a plurality of emergency situations. Each of the second plurality of portable units may include a plurality of LEDs associated with a plurality of emergency situations. The management unit may be configured to be monitored by security personnel and may be configured to receive any signals transmitted from either the first or second plurality of portable units. The first and second plurality of portable units, the plurality of fixed units, and the management unit may form a mesh network.

[0011] In some embodiments, each of the first and second plurality of portable units, the plurality of fixed units, and the management unit can wirelessly communicate with all other units in the mesh network and can be configured to receive all signals. In some embodiments, each of the first and second plurality of portable units, each of the plurality of fixed units, and the management unit can be configured to interact with all other units in the mesh network. In some embodiments, at least a portion of the first and second plurality of portable units can be configured to broadcast information to the management unit at a first predefined frequency when fixed.

[0012] In some embodiments, at least a portion of the first and second plurality of portable units may be configured to broadcast information to a management unit at a second predefined frequency in response to a button being pressed on one of the first plurality of portable units, wherein a signal associated with a specific type of emergency is sent when the button is pressed. In some embodiments, the second frequency may be greater than the first frequency. In some embodiments, at least a portion of the first and second plurality of portable units may be configured to broadcast information to a management unit at a first frequency in response to a deactivation signal from the management unit.

[0013] In some embodiments, the information may include at least one ID associated with the portable unit; a location associated with the portable unit; a name associated with the portable unit; or a role associated with the portable unit. In some embodiments, at least one of the first and second plurality of portable units may be configured to broadcast information to the management unit at a frequency higher than a first frequency while in motion. In some embodiments, the second plurality of portable units may be configured to illuminate an emergency-associated LED in response to the pressing of an emergency-associated button on one of the first plurality of portable units until a deactivation signal is received from the management unit. In some embodiments, at least one of the first plurality of portable units may be configured to broadcast the location associated with at least one unit to the management unit in response to the pressing of an emergency-associated button on at least one of the first plurality of portable units.

[0014] According to another aspect of this disclosure, a method for tracking disease spread in a wireless mesh network within a site may include acquiring information associated with a portable unit worn or carried by a selected user in the wireless mesh network; identifying rooms within the site entered by the portable unit within a time range from the acquired information; calculating a room score for each identified room; identifying multiple other portable units worn or carried by multiple other selected users within the wireless mesh network that entered each identified room within the time range; calculating an exposure score for each of the multiple other portable units; and identifying a portable unit among the multiple other portable units that has an exposure score greater than a predefined threshold. The information may include location and time information within a predefined time range.

[0015] In some embodiments, the portable unit, each of a plurality of other portable units, and a plurality of fixed units can wirelessly communicate with all other units in the mesh network and can be configured to receive all signals. In some embodiments, the portable unit, each of a plurality of other portable units, and a plurality of fixed units can be configured to interact with all other units in the mesh network. In some embodiments, each room in the site can be geofenced within the mesh network. In some embodiments, the room score for each identified room can be time-related. In some embodiments, for each identified room, the room score can be calculated based on the duration spent by the portable unit in each room.

[0016] In some embodiments, an infection score may be associated with a portable unit, and for each identified room, calculating the room score may include increasing the room score by a percentage of the infection score. This percentage may be proportional to the duration the portable unit spends in the room. In some embodiments, for each identified room, calculating the room score may include decreasing the room score by a second percentage. This second percentage may be proportional to the duration since the portable unit left the room. In some embodiments, for each other identified portable unit, an exposure score may be calculated based on the duration spent in each identified room simultaneously with the portable unit; and the duration spent in each identified room at a different time than the portable unit.

[0017] In some embodiments, an infection score may be associated with a portable unit, and for each other identified portable unit, calculating an exposure score may include adding the exposure score as a percentage of the infection score and the room score. The percentage may be proportional to the duration that the portable unit and other portable units spend simultaneously in the identified room. In some embodiments, the location of a portable unit may be determined by analyzing multiple Received Signal Strength Indicators (RSSIs) from multiple fixed units.

[0018] According to another aspect of this disclosure, a method for managing area capacity may include configuring a geofence in a mesh network that can define areas within a site; establishing capacity associated with the area; analyzing the locations of multiple portable units worn or carried by multiple selected users within the mesh network; identifying multiple portable units located within the area; maintaining a current count of the number of portable units located within the area; and generating an alarm to a management unit in response to the current count exceeding the capacity. The management unit may be part of the mesh network.

[0019] In some embodiments, the mesh network may include a plurality of fixed units, wherein each of the plurality of portable units, each of the plurality of fixed units, and a management unit may wirelessly communicate with all other units in the mesh network and may be configured to receive all signals. In some embodiments, each of the plurality of portable units, each of the plurality of fixed units, and a management unit may be configured to interact with all other units in the mesh network. In some embodiments, the location of a portable unit may be determined by analyzing a plurality of Received Signal Strength Indicators (RSSIs) from the plurality of fixed units.

[0020] In some embodiments, at least a portion of the plurality of portable units may be configured to broadcast information to a management unit at a first predefined frequency when stationary. In some embodiments, at least one of the plurality of portable units may be configured to broadcast information to the management unit at a frequency higher than the first frequency when in motion. In some embodiments, the information may include at least one ID associated with the portable unit; a location associated with the portable unit; a name associated with the portable unit; or a role associated with the portable unit. In some embodiments, at least one of the plurality of portable units may include a plurality of buttons for sending signals to the management unit for a specific type of emergency. In some embodiments, a subset of the plurality of portable units may be configured to illuminate an emergency-associated LED in response to a button being pressed on at least one of the plurality of portable units until a deactivation signal is received from the management unit. Attached Figure Description

[0021] The accompanying drawings are incorporated in and form part of the specification and serve to further illustrate embodiments including the concepts of the claimed invention and to explain the various principles and advantages of these embodiments, wherein similar reference numerals in the drawings refer to the same or functionally similar elements in separate views and in the detailed description below.

[0022] Figure 1 This is a top view of an exemplary facility (e.g., a school building) showing an exemplary distribution of portable and fixed units according to this disclosure.

[0023] Figure 2 This is an enlarged view of a representative portable unit according to some embodiments of the present disclosure.

[0024] Figure 3 This is a schematic diagram of a portable unit worn by a user according to some embodiments of the present disclosure.

[0025] Figure 4 This is a block diagram of a portable unit worn by a teacher / security personnel according to some embodiments of the present disclosure.

[0026] Figure 5 This is a block diagram of a portable unit worn by a monitor (e.g., an employee of the facility) according to some embodiments of this disclosure.

[0027] Figure 6 This is a block diagram of a portable unit worn by a student according to some embodiments of the present disclosure.

[0028] Figure 7 This is a block diagram of a fixed unit installed in a room according to some embodiments of the present disclosure.

[0029] Figure 8This is a block diagram of a fixed unit installed in a passage such as a corridor, according to some embodiments of the present disclosure.

[0030] Figure 9 This is a block diagram of multiple units installed in communication with a management unit via a mesh network according to some embodiments of the present disclosure.

[0031] Figure 10 It is according to some embodiments of this disclosure for activating Figure 1 and Figure 9 An example procedure for an incident protocol executed within the system.

[0032] Figure 11 It is according to some embodiments of this disclosure for activating Figure 1 and Figure 9 An example procedure for an instruction protocol executed within the system.

[0033] Figure 12 These are example processes for contact tracing according to some embodiments of this disclosure.

[0034] Figure 13 This is an example process for monitoring room capacity according to some embodiments of the present disclosure.

[0035] Figure 14 These are example user interfaces based on some embodiments of this disclosure.

[0036] Those skilled in the art will understand that the elements in the accompanying drawings are for simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some elements in the drawings may be exaggerated relative to other elements to aid in understanding embodiments of this disclosure.

[0037] The structural components of the safety system are appropriately indicated by conventional symbols in the accompanying drawings, with only specific details shown that are relevant to understanding embodiments of this disclosure, so as not to obscure this disclosure with details that would be readily apparent to those skilled in the art who would benefit from the description herein. Detailed Implementation

[0038] This disclosure discloses a security system and method for communicating security threats or incidents to all users of a facility, such as a school building, office building, or any similar structure, via a full mesh network topology. The mesh network may include multiple portable units (or nodes) carried within the facility by users such as teachers, security personnel, monitors, and students, as well as multiple fixed units (or nodes) installed on walls in rooms and passageways such as corridors within the facility. At least some units may have multiple buttons, each designated for a specific type of problem, such as a medical emergency, a disturbance such as a fight, fire, or intruder. If a user presses one of the designated buttons, other members of the mesh network, including management units (or nodes) monitored by other security personnel or administrators, can be notified of the type and location of the threat within the facility. Users moving throughout the facility may wear portable units. Fixed units, also known as beacons, may be fixed in appropriate locations and strategically or selectively placed throughout the facility. For example, if an intruder is observed, a user may activate one of the buttons designated for the intruder on a portable or fixed unit, and all other units or nodes in the mesh network can be notified of the intrusion.

[0039] One object of this disclosure is to provide a rapid response system for emergencies related to facility security. Another object of this disclosure is to provide a security system that notifies security personnel of the type and specific location of the emergency. Another object of this disclosure is to provide a security system that can be used to notify users that there is no security problem in the facility, and, for example, that schoolchildren can be evacuated from the facility. Another object of this disclosure is to provide a security system that can be used to guide personnel safely out of the facility. Another object of this disclosure is to provide a security system that is easy for users to operate. Another object of this disclosure is to adequately position personnel within the facility to maintain the required security. Another object of this disclosure is to provide a security system that can be manufactured relatively easily and inexpensively.

[0040] Go to Figure 1 This illustration shows an exemplary layout of the basic components of a security system 10 in use and located in an exemplary facility or building 12 (e.g., a school building, office building, manufacturing complex, hotel, factory, or any similar structure). Building 12 may contain multiple rooms 24 defined by walls 32 and passageways such as corridors 26 and entrances / exits 30, and building 12 is for illustrative purposes only, as those skilled in the art will understand that system 10 can be used in all types of facilities and layouts. As used herein, the term corridor 26 is intended to encompass stairwells, fire escapes, elevators, and similar passageways.

[0041] Figure 1The system may include multiple portable units 14 disposed throughout facility 12, wherein the portable units 14 may be carried or worn around the neck, wrist, or clothing of teachers or security personnel, typically located in room 24, while security personnel may be located anywhere within facility 12. In some embodiments, the portable unit 14 may be referred to as a “full-function” unit. Each portable unit 14 may have a unique ID associated with it. The portable unit 14 may be configured to have a complete incident report (regarding...). Figure 10 Description) and indication functions (about Figure 10 (Description). In some embodiments, portable unit 14 may be configured to have repeater functionality, but this functionality may be switched (e.g., via management unit 28) to convert power and / or reduce data queuing time. In some embodiments, portable unit 14 may be configured to automatically report its associated ID and location (e.g., to management unit 28) at a preset period or preset frequency. In some embodiments, ID and location reporting may be performed in response to a query from management unit 28 (automatically or manually). In some embodiments, ID and location reporting may also include the name, job title, and role of the person associated with portable unit 14.

[0042] In some embodiments, the location of a portable unit (e.g., portable units 14, 16, and / or 18) can be determined by calculating the distances between portable units and multiple fixed units (e.g., fixed units 20, 22). For example, four fixed units can create a geofence (e.g., for a room), which can create a layout for a protected site. Portable units can use RSSI signals (described in detail later) to help determine their location. As portable units move between geofences, they can advertise themselves to discover new beacons. In some embodiments, when a new beacon is discovered, a portable unit can analyze the signal strength across four beacons and advertise its location to the nearest one.

[0043] Figure 1 The diagram also shows multiple portable units 16 that can be carried or worn on the neck, wrist, or clothing of a monitor, such as an employee (e.g., a guard working at the facility), who can also be located anywhere within the facility 12. Each portable unit 16 may also have a unique ID associated with it. In some embodiments, the portable unit 16 may have signaling functionality (e.g., LEDs illuminate to convey information, similar to the description of portable unit 14), but not incident reporting or dispatching functions. For example, during an ongoing incident (see reference... Figure 10(Described in more detail), portable unit 16 may be configured to illuminate associated LEDs, but cannot be configured to actually implement or report incidents. In some embodiments, portable unit 16 may be configured to have repeater functionality, but this functionality can be switched (e.g., via management unit 28) to convert power and / or reduce data queuing time. In some embodiments, portable unit 16 may be configured to automatically report its associated ID and location (e.g., to management unit 28) at a preset period or preset frequency. In some embodiments, ID and location reporting may be performed in response to a query from management unit 28 (automatically or manually). In some embodiments, ID and location reporting may also include the name, job title, and role of the person associated with portable unit 16.

[0044] Figure 1 The illustration also shows multiple portable units 18 that can be carried or worn around a student's neck, wrist, or clothing, typically in room 24. Each portable unit 18 may also have a unique ID associated with it. In some embodiments, the portable units 18 may not have any incident reporting, scheduling, or notification functions. In some embodiments, the portable units 18 may have no display other than a power status LED. In some embodiments, the portable units 18 may be configured to automatically report their associated ID and location (e.g., to management unit 28) at a preset period or frequency. In some embodiments, ID and location reporting may be performed in response to a query from management unit 28 (automatically or manually). In some embodiments, ID and location reporting may also include the name, job title, and role of the person associated with the portable unit 18. In some embodiments, the portable units 18 may be configured to have repeater functionality, but this functionality may be switched (e.g., via management unit 28) to convert power and / or reduce data queuing time.

[0045] As described above, each of portable units 14, 16, and 18 can automatically report its associated ID and location (e.g., to management unit 28). In some embodiments, this data broadcasting can occur at set intervals, and the interval time can be set by management unit 28 in the firmware of unit 28 or through an application under the control of management unit 28. In some embodiments, the interval time for broadcasting data to management unit 28 can be changed according to the current incident level. For example, during an “active incident,” portable nodes 14, 16, and 18 can continuously report their associated ID, location, name, and role every three seconds until the active incident is resolved. In another example, during an “inactive incident,” and when portable nodes 14, 16, and 18 move between fixed nodes 20 and 22, portable nodes 14, 16, and 18 can report their associated ID, location, name, and role every thirty seconds. Furthermore, during inactive incidents, and when portable nodes 14, 16, and 18 approach the same fixed nodes 20 and 22 as when the data was last reported, portable nodes 14, 16, and 18 may report their associated ID, location, name, and role every ten minutes. Note that the absolute frequencies described here are merely exemplary in nature; rather, portable nodes 14, 16, and 18 may generally be configured to report more frequently during active incidents than during inactive incidents, and more frequently when moving than when stationary. Note that, as used in this context, the term "stationary" may mean an area where the nearest stationary node remains unchanged (e.g., inside a classroom when a stationary node is installed near a classroom). In some embodiments, any "broadcast" of location data may also include a timestamp (e.g., date and time) associated with the current broadcast location. In some embodiments, information broadcast to management unit 28 may be stored in a database and indexed by ID (e.g., the ID of the associated portable node). In some embodiments, the database may be part of management unit 28, an external database, or a combination of both.

[0046] In some embodiments, portable nodes (e.g., portable nodes 14, 16, 18) can be configured to report their location via a Received Signal Strength Indication (RSSI) method. For example, broadcast data from a portable node is sent to fixed nodes (e.g., fixed nodes 20 and 22) located in close proximity to the portable node. The fixed node receiving the broadcast data can then send RSSI information back to the portable node. In response to receiving RSSI information, the portable node can publish its location to the fixed node generating the strongest RSSI signal.

[0047] Figure 1The diagram also shows multiple fixed units 20, which can be mounted (e.g., permanently mounted) on the wall 32 of room 24 of facility 12. In some embodiments, the fixed units 20 may have repeater functionality (e.g., configured to participate as part of a mesh network). Each fixed unit 20 may have a unique ID associated with it. In some embodiments, the battery of the fixed unit 20 may be rechargeable or continuously charged from a constant power source. In some embodiments, each fixed unit 20 may have a power status indicated by LEDs (e.g., green, orange, red, etc.). In some embodiments, the fixed units 20 may also be configured to utilize an emergency power duty cycle, making them available during power outages. In some embodiments, the fixed units 20 may report their ID and location only under the control of management unit 28.

[0048] In some embodiments, Figure 1 The system may also include multiple additional fixed units 22, which may be mounted on a wall 32 (e.g., permanently) and strategically located in passageways such as corridors 26 within facility 12. Similar to fixed unit 20, fixed unit 22 may also have repeater functionality and participate as part of a mesh network. In some embodiments, fixed unit 22 may also be configured to have status and direction signaling functionality. For example, fixed unit 22 may display LEDs for rapid response to various ongoing incidents (see reference). Figure 11 (Described in more detail). The anchoring unit 22 may also include an LED display to implement directional instructions. For example, the LED display may include a set of LEDs that can indicate a horizontal direction and another set of LEDs that can indicate a vertical direction. In some embodiments, the LED display of the anchoring unit 22 may be configured to indicate a direction for people to follow. Furthermore, each anchoring unit 22 may have a unique ID associated with it. In some embodiments, the battery of the anchoring unit 22 may be rechargeable or continuously charged from a constant power source. In some embodiments, each anchoring unit 22 may have a power status indicated by LEDs (e.g., green, orange, red, etc.). In some embodiments, the anchoring unit 22 may also be configured to utilize an emergency power duty cycle, making it available during power outages. In some embodiments, the anchoring unit 22 may report its ID and location only under the control of the management unit 28.

[0049] Figure 1The diagram also shows a management unit 28, which may be fixed and located in the management section of facility 12, such as the main office. In some embodiments, the management unit 28, which may include a computer, may be monitored by dedicated security personnel or by an administrator. The management unit 28 may also be portable and carried or worn by an administrator. For example, the management unit 28 may be integrated into a mobile phone. In some embodiments, the management unit 28 may include a control center and may be configured to control all other nodes (e.g., portable and fixed units) within the network. In some embodiments, the management unit 28 may display site maps, node / unit information, messages, and instructions. Furthermore, for example, using an application, an administrator can instruct any node or unit to enable or disable repeater functionality via the management unit 28. For example, switching repeater functionality can be used to save power and / or reduce data queuing time.

[0050] Furthermore, as mentioned earlier, all nodes (including portable and stationary ones) can be configured as... Figure 1 A portion of the mesh network participates. However, not all nodes are active. For example, fixed nodes 20 and 22 can be configured to operate in a continuous response mode; in other words, fixed nodes 20 and 22 can be configured to continuously act as repeaters, relaying mesh message data between each other and forwarding it to management unit 28. Portable nodes 14, 16, and 18 can be configured to switch or automatically perform their repeater functions. For example, in a switched version, portable nodes 14, 16, and / or 18 can operate using repeater functions in response to receiving an activation signal from management node 28. For automatic repeater functions, portable nodes 14, 16, and 18 can be configured to operate as repeaters as a protective measure. For example, if fixed node 20 or 22 is detected to be inoperable or non-functional within the system, an activation signal can be sent from management unit 28 to the portable node closest to the damaged fixed node.

[0051] Go to Figure 2The illustration shows typical portable units 14, 16, and 28, which can be worn by teachers / security personnel or administrators. Each unit 14, 16, and 28 may have multiple buttons, each of which can be associated with a different occurrence or event. For example, button 40 may be designated for a medical emergency; button 42 for a disturbance, such as a fight; button 44 for a fire; button 46 for an intruder; button 48 for a lock-down directive; button 50 for a lock-in directive; button 52 for a relocation directive; and button 54 for an emergency directive, such as evacuation. LEDs may be associated with each button. A power switch 58 is also shown. In some embodiments, when the power switch 58 is “turned on” or cycled on all nodes within the system (portable and / or stationary), a control unit (e.g., Figure 1 Unit tests are initiated under the control of the management unit 28. If everything goes "smoothly," a message such as "I'm okay" with ID and location data can be generated. Additionally, the power LED 56 can flash in a "handshake" motion to assure the user that the system is aware of their presence and can respond appropriately. This process can be performed at any time as needed by turning the power switch 58 "off" and then "on."

[0052] LED 56 can also monitor the unit's power status via its color (e.g., red, orange, green). In some embodiments, the power LED 56 may be red when the remaining power is less than 10%, orange when the remaining power is 10-60%, and green when the remaining power is 60-100%. Note that these values ​​are merely exemplary in nature and other values ​​and / or colors may be used. If one of the designated buttons is pressed, other members of the mesh network (including management unit 28 monitored by other security personnel or administrators) are immediately notified of the type and location of the threat within facility 12. Aside from the power switch 58 and the power monitor 56, the typical portable unit 18 or fixed unit 20 worn by students does not need to have any of these buttons.

[0053] Go to Figure 3 The illustration depicts a typical user wearing the portable unit around their neck, with the portable unit 14 suspended from a strap 60 as would be done by someone skilled in the art. The portable unit 14 can also be used as a photo ID. Other methods exist for carrying or otherwise attaching the portable unit 14 to the user. The portable unit can be approximately the size of a credit card and lightweight.

[0054] Figure 4-8 Block diagrams illustrating units 14, 16, 18, 20, and 22 according to some embodiments of this disclosure depict various functions performed by their respective onboard processors. Figure 4 In this embodiment, unit 14 may be fully functional. Portable unit 14 may include an interface 401 with a power button and a power LED, as well as specific emergency buttons, such as those for medical emergencies, riots, fires, and intruders, as described elsewhere in this disclosure. Interface 401 may also include buttons and LEDs to report and / or activate indication protocols, such as blockades, lockouts, relocations, and evacuations. Portable unit 14 may also include communication and computing functions 402 and a power supply 403. In some embodiments, portable unit 14 may include various subroutines 404a-404i, such as location determination (404a), ID maintenance (404b), transmitter / receiver (404c), charger (404d), reporting timer (404e), repeater function (404f), repeater function switching (404g), a function to report an "I'm fine" message (404h), and an incident reporting function (404i) when a button is pressed on interface 401.

[0055] Portable Unit 16 in Figure 5 As shown, it may lack an accident reporting function. In some embodiments, portable unit 16 may include an interface 501 similar to portable unit 14 but without an accident button. Note that in some embodiments, portable unit 16 may include the same accident reporting functionality as portable unit 14. Figure 4 The portable unit 16 includes similar communication and computing functions 502 and power supply 503 as the portable unit 14. Furthermore, in addition to incident reporting, the portable unit 16 may include many of the same subroutines (504a-504h) as the portable unit 14.

[0056] Portable unit 18 can Figure 6 As shown in the figure. In some embodiments, interface 601 may not have information about Figure 4 and 5 All the reporting buttons and LEDs described may be included, but a power button and power LED may still be included. In addition to incident reporting, the portable unit 18 may include similar communication and computing functions 602 and power supply 603, as well as similar subroutines (604a-604h).

[0057] Fixed unit 20 can be Figure 7As shown in the diagram. Fixed unit 20 may include an interface 701 without buttons and LEDs, except for a power LED and a power button. Fixed unit 20 may include similar communication and computing functions 702 and a power supply 703, although power supply 703 may also be hardwired to a more persistent power source. In some embodiments, fixed unit 20 may include subroutines 704a-704h, where incident reporting may not be included.

[0058] Fixed unit 22 can be Figure 8 As shown in the diagram. The fixed unit 22 may include an interface 801, which may not have a button for incident reporting but may include emergency-associated LEDs, a power button and a power LED, and directional LEDs for implementing indication protocols. The fixed unit 22 may include similar communication and computing functions 802 and a power supply 803 (although the power supply 803 may also be hardwired to a permanent power source). Furthermore, the fixed unit 22 may include features related to... Figure 4-7 The various subroutines mentioned (e.g., subroutines 804a-804h) are similar or identical. However, in some embodiments, the fixing unit 22 may also include an accident display 804i and a direction display 804j. In some embodiments, the direction display may include arrows (e.g., left, right, up, down, etc.) to indicate the direction of movement of an individual within the protected site.

[0059] In some embodiments, the management unit 28 may be powered by a rechargeable battery when configured as a mobile phone or laptop computer, and by a hardwired power supply when configured as a desktop computer.

[0060] Turning Figure 9 The diagram illustrates a conventional full-mesh wireless network topology with individual member units or nodes 20, 22 (also referred to as beacons) acting as repeaters in a mesh network 62, wherein previously disclosed units or nodes 14, 16, 18, 20, 22, 28 are also members of network 62. The mesh network is characterized by each unit / node communicating with every other unit / node, with communication lines shown by dashed lines 30, intended to illustrate the electronic, wireless means of communication between units / nodes in the mesh network, such as Bluetooth / Wi-Fi. For example, if a button or similar user activation mechanism on portable unit 14 is activated by a user, a signal will be wirelessly transmitted to every other unit / node in network 62. Each unit / node has a central processing unit capable of processing information necessary for the normal operation of network 62, including but not limited to information regarding the type or identification, location, time, and type of an emergency or security threat, as well as any other information necessary for the normal operation of network 62, as described below. System 10 is designed for use with networks 62 of any size, for example, with 100-200 or even more nodes.

[0061] As mentioned above, and as Figure 9 As shown, the management unit or node 28 is configured as a computer or mobile phone, either of which has a display showing a site map 64, node information 66, messages 68, and indicators 70. Management node 28 is the control center for controlling all other nodes. Therefore, administrators can easily view the displays and immediately determine the location and type of emergency within the facility, and can easily respond to the emergency.

[0062] Figure 10 It is according to some embodiments of this disclosure for activating Figure 1 and Figure 9 Example process 1000 of the incident protocol executed within the system. In some embodiments, process 1000 may be... Figure 1 The system executes within system 10 and can occur as a security protocol in response to incidents in protected locations such as schools or similar facilities. In block 1001, portable unit 14 (e.g., a full-function unit) can receive incident indications. For example, full-function unit 14 can be worn or carried by a teacher or security personnel within the protected location. In response to noticing that an incident has begun, the teacher or security personnel can press one of several buttons on full-function unit 14 (e.g., such as...). Figure 2 (One of buttons 40-46 described). For example, if a teacher notices a fire, they can press fire button 44 to activate the emergency indicator. Note that, as... Figure 2 Buttons 40-46 described herein are merely exemplary in nature; additional and / or different incidents may be reflected by their own buttons on the full-function unit 14.

[0063] In block 1002, in response to receiving an incident indication (e.g., from pressing an incident button), the fully functional unit 14, whose button has been pressed, can distribute the incident indication. In some embodiments, the fully functional unit 14 can distribute the incident indication to every other node within system 10, including portable units 16 and 18 (e.g., guards and students, respectively), other portable units 14 (e.g., other teachers and / or security personnel), stationary nodes 20 and 22, and management unit 28. In some embodiments, in response to receiving an incident indication by pressing a button (e.g., at the fully functional unit 14), the location of the fully functional unit 14 can also be immediately broadcast to management unit 28. This allows administrators to quickly know the location of an incident after it occurs.

[0064] In block 1003, in response to receiving an incident indication from the original full-function unit 14, each portable node that has received the incident indication can initiate broadcasting behavior based on active incidents. As previously described, active incident reporting causes portable units 14, 16, and 18 to broadcast information (e.g., location, name, ID, and role) to management unit 28 more frequently than during inactive incident migration protocols or during normal daily operations. For example, active incident reporting could involve portable units 14, 16, and 18 broadcasting once every three seconds.

[0065] In block 1004, in response to receiving an accident indication from the original full-function unit 14, portable nodes 14 and 16 and management unit 28 can initiate a semaphore protocol. In some embodiments, the semaphore protocol for each node may include illumination that causes the corresponding node's LED. (Return to Reference) Figure 2 Portable units 14 and 16 may include LEDs adjacent to each button 40-46. Therefore, in response to a pressed emergency button, if one full-function unit 14 activates an emergency protocol, other full-function units 14 may illuminate their corresponding LEDs. For example, if a teacher carrying a full-function unit 14 presses the fire button 44, an emergency indication will be sent from full-function unit 14 to other full-function units 14 and portable units 16 (and management unit 28) within the system, causing LEDs next to the fire buttons 44 on the other devices to also illuminate. In some embodiments, LED illumination may occur when the system successfully receives and acknowledges a signal (e.g., a "handshake"). In some embodiments, LED illumination in the signaling protocol may be constant (blinking or steady) until a deactivation signal is received from management unit 28. Note that management unit 28 may also include a signaling protocol and may illuminate the corresponding LEDs in response to receiving an emergency indication.

[0066] In block 1005, portable nodes 14, 16, and 18 (including the original full-function unit 14) can receive incident deactivation signals from management unit 28. For example, during incident degrading (e.g., fire extinguishing, personnel receiving medical attention, fight dispersed, etc.), the administrator can issue an incident deactivation signal from management unit 28. In block 1006, in response to receiving an incident deactivation signal, each portable unit 14, 16, and 18 can deactivate its associated incident protocol. For example, portable units 14, 16, and 18 can all revert to inactive incident reporting and begin broadcasting information to management unit 28 at a lower frequency (e.g., every thirty seconds). Furthermore, portable units 14, 16, and 18 can turn off their respective LEDs.

[0067] In some embodiments, incident reporting can be at various levels. For example, Level 1 incidents may include those that can be handled by on-site personnel (e.g., security personnel, teachers, and / or administrators). A Level 1 incident can be initiated by pressing one of the incident buttons (e.g., medical button 40 or riot button 42) on the full-function unit 14. Level 1 medical incidents may include cuts, bruises, and other injuries that do not require external assistance but can be handled by internal assistance (e.g., nurses or first-aid qualified personnel). Level 1 riots may include fights between students or staff that do not require external assistance from the police and can be handled by management and / or internal security. In some embodiments, Level 2 incidents may include incidents that require external assistance. Level 2 incidents can also be initiated by pressing a button on the full-function unit 14. In some embodiments, this can be achieved by simultaneously pressing an incident button (e.g., medical button 40 or riot button 42) and an emergency icon button (e.g., [button name missing]). Figure 2 Pressing button 54) activates a Level 2 incident. A Level 2 medical incident may include fractures, excessive bleeding, unconsciousness, and other events that may require emergency medical personnel. A Level 2 disturbance may include a serious fight or argument requiring police assistance. In some embodiments, a Level 3 incident may be associated with a higher level of emergency and requires a significant amount of immediate response. A Level 3 incident may include incidents such as fires or intruders. A Level 3 incident can be activated via the full-function device 14 by pressing button 44 or button 46. In some embodiments, a Level 3 incident may also include incidents related to... Figure 11 The described instructions.

[0068] Figure 11 It is according to some embodiments of this disclosure for activating Figure 1 and Figure 9 Example process 1100 of the instruction protocol executed within the system. In some embodiments, process 1100 may be... Figure 1 The instruction signaling protocol is executed within System 10. This protocol enables nodes within System 10 to broadcast instruction commands around the protected facility to assist personnel in moving within the facility.

[0069] In module 1101, portable unit 14 (e.g., full-function unit) can receive instruction instructions. For example, full-function unit 14 can be worn or carried by a teacher or security personnel in a protected location. In response to noticing a serious incident or an incident requiring instruction that has begun, the teacher or security personnel can press one of several buttons on full-function unit 14 (e.g., Figure 2(One of buttons 48-54 described herein). For example, button 48 may correspond to a blockade instruction procedure, button 50 may correspond to a lockout instruction procedure, button 52 may correspond to a relocation instruction procedure, and button 54 may correspond to an evacuation procedure. As described herein, a blockade procedure may be used to prevent threats from entering a building or external area and may instruct personnel to lock all doors and windows, barricade entrances, and hide in a pre-designated location. A lockout procedure may be used to instruct personnel within a protected facility to lock all doors and remain in place, but continue normal operations. A relocation procedure (e.g., shelter in place) may be used to direct personnel within a protected facility to a pre-designated shelter entity (e.g., in response to a weather event or an intruder on or near the facility) or another safe location (e.g., when a tornado moves from the south and changes direction to the west). An evacuation procedure may be used to instruct personnel to leave the facility immediately. It is important to note that the instructions described herein are merely exemplary and other and / or additional instructions may be implemented within the systems disclosed herein.

[0070] In block 1102, in response to receiving an instruction indication from a button press, full-function unit 14 can distribute the instruction indication to other nodes within system 10, including other portable nodes 14, 16, and 18; fixed node 22; and management unit 28. In some embodiments, in response to receiving an instruction indication, portable nodes 14 and 16 can be configured to illuminate an LED corresponding to a selected incident at the original full-function unit 14, such as regarding... Figure 10 As described. In block 1103, fixed node 22 can identify instructions (e.g., directional instructions) associated with received instruction indications. For example, fixed node 22 can identify the pattern to be displayed by pre-programmed LEDs according to specific instruction indications in order to provide appropriate direction. In the event of an evacuation incident, fixed node 22 can illuminate arrows pointing to the nearest exit or emergency exit. In the event of a relocation incident, fixed node 22 can illuminate arrows pointing to the nearest safe shelter. Note that since fixed node 22 can be located on the walls of corridors and passageways, this can be used to significantly indicate the direction of movement to people within the facility. In block 1104, fixed node 22 can illuminate the identified lighting pattern based on instruction indications. In some embodiments, fixed node 22 can remain illuminated until explicitly deactivated by management unit 28 at the end of the incident. In block 1105, management unit 28 can deactivate the incident protocol between fixed node 22 and portable units 14 and 16.

[0071] As mentioned earlier, the information broadcast to the management unit can be stored in a database and indexed by ID, and this information can include timestamp information and location information. Therefore, through Figure 1 and 9The information stored in the system allows for the tracking and analysis of the historical movement of various portable units; in other words, the system disclosed herein can also be used to perform contact tracing and various other tasks, processes, and / or calculations related to the analysis of historical location, movement, proximity, and duration. Due to its relation to... Figure 1 and 9 The mesh network setup described in the system allows for more accurate access to and tracking of locations (e.g., with accuracy down to the feet), enabling more accurate and effective contact tracing. Therefore, embodiments of this disclosure also relate to methods for contact tracing and monitoring room capacity.

[0072] Figure 12 This is an example process 1200 for contact tracing according to some embodiments of this disclosure. Because, as previously described, portable units (e.g., portable unit 14 for teachers, portable unit 16 for personnel such as guards, and portable unit 18 for students) can determine their location based on other members of the mesh network (e.g., other portable units and fixed units) and periodically broadcast information (e.g., location, timestamp information, ID, etc.) to a management unit 28 stored in a database, there is sufficient information to track the movement of a particular portable unit. In some embodiments, an individual identity can be associated with a portable unit (e.g., associating an individual's ID number with a portable unit ID number), which can allow for the selection and analysis of specific portable units to analyze individual movement. In some embodiments, the various steps in process 1200 can be performed by the management unit 28, an external server or computing device, or in a cloud computing environment (e.g., Amazon Web Services).

[0073] In block 1201, management unit 28 can receive an indication confirming infection. For example, by Figure 1 and 9Administrators of protected schools, hotels, or other similar sites may have been notified that staff, members, students, guests, or any other person associated with a portable unit on the site has tested positive for an infectious disease. Therefore, administrators can use management unit 28 to input an indication that an individual (e.g., John) has been confirmed infected. In block 1202, the server can obtain location information associated with the confirmed infection. In some embodiments, obtaining location information may include accessing a database storing information broadcast from all portable units within the site. For example, the server can query the database by ID (e.g., the portable unit ID associated with the confirmed infection) and extract location and associated timestamp information. In some embodiments, all historical information may be obtained, or historical information within a pre-specified time range may be obtained. In some embodiments, the time range may be selected based on the individual's illness. For example, if John has contracted an infectious disease, the administrator may want to obtain the location information of the confirmed infected person for the previous two weeks. In block 1203, the server can identify the room the confirmed infected person entered. In some embodiments, each room in the protected site (e.g., Figure 1 Room 24 in System 10 can be geofenced and has an associated room ID. For example, the server might identify that a confirmed infected person has entered three different rooms in the school in the past two weeks, such as a classroom, a restroom, and a teacher's office.

[0074] In block 1204, the server can calculate a room score for each room identified as having been entered by a confirmed infected person. The room score can reflect the room's exposure to the infectious disease and the likelihood that others in the room may also be infected. For example, a higher score may indicate that the room is more likely to be infected than a room with a lower score. In some embodiments, an infected individual may be assigned a standard score by the server (e.g., 10, 100, etc.), which may sometimes be used as a relative maximum for score calculation within the system, although this may only be used as the maximum room score. In some embodiments, for each time period an infected individual is detected in the room, the room may receive a percentage of the individual's score for that time period. For example, if John is identified as being in the classroom every ten minutes, the room may receive 10% of John's score. In an example where a confirmed case scores 10 points, if John is detected being in the classroom for 20 minutes, the classroom will receive 2 points. Note that the duration and percentage used for scoring may vary; 10 percent of ten minutes is merely exemplary in nature and may vary depending on the disease at hand. In some embodiments, a room score can be calculated for each room identified as having been entered by a confirmed case within the past two weeks, and the score can be associated with the room ID of each room.

[0075] In some embodiments, the room score may be reduced to reflect the reduction in exposure due to the infected individual leaving the room. In some embodiments, the room score may be reduced by a percentage for each time period during which the infected individual is not in the room. In some embodiments, the room score may be reduced by 10 percent for every 10 minutes the infected individual is not in the room. For example, if John enters the room at 2:00 p.m. and stays there for 100 minutes (e.g., one hour and forty minutes), then at 3:40 p.m., the room score might be 10. Assuming John leaves the room at 3:40 p.m., the room score would be 9 at 3:50 p.m., 8.1 at 4:00 p.m., and 7.3 at 4:10 p.m. Note that these values ​​are exemplary and other values ​​and percentages may be used depending on the specific disease or various other factors. Furthermore, this method of calculating room scores allows for the plotting of time-related graphs of room scores over a two-week period, which can be correlated with and used for analysis of other time-related graphs (e.g., motion, temperature, etc.) relevant to a specific individual.

[0076] In block 1205, the server can identify other individuals within the identified rooms. For example, since each portable unit can periodically broadcast location information, the server can access the historical movement of each portable device within the protected site from a specified time period and determine whether a unit entered each room identified in block 1203. In block 1206, the server can calculate the exposure score for each individual identified as having entered one of the rooms for which room scores are calculated. In some embodiments, an individual's (e.g., David's) exposure score can reflect exposure from being in an identified room simultaneously with a confirmed infected person and exposure from being in an identified room at a different time (e.g., it can be proportional to the time spent). For example, if David and John are in the same room simultaneously, David's exposure score can increase by 10 percent of the sum of the room score and John's score every ten minutes. If David entered a room before John but is no longer in it, David's score can increase by 10% of the room score. In some embodiments, an individual's exposure score can be a cumulative score over a period of time. For example, if David is detected entering three rooms within the problematic time period, David's exposure score would be a cumulative score reflecting the exposure level / risk of infection in all three rooms. In some embodiments, the exposure score may also have a maximum value that is the same as the maximum room score. Note that, similar to the previous description of room score calculation, the numbers and percentages are exemplary and can be changed to reflect various diseases or desired scoring principles. In block 1207, the server can analyze the exposure scores of all portable units within the site and identify exposure scores that exceed a certain predefined threshold. In some embodiments, the threshold may depend on various factors, such as the actual infectious disease, and may reflect the likelihood and / or probability of an individual with a calculated score contracting the disease. The threshold can be used to indicate who is most likely to contract the disease. One advantage of this approach is that, once an individual who has interacted in a public place is confirmed to be infected with an infectious disease, the most likely candidates to spread the disease can be identified, and further procedures such as testing, isolation, and / or treatment can be taken for these identified individuals.

[0077] Note that while the preceding description uses a server to describe process 1200 in detail, other similar structures, such as cloud computing platforms, can also be used. In some embodiments, information stored and analyzed in a cloud computing platform can be anonymized to protect the identities of individuals within the site from access in the event of a hacker intrusion.

[0078] Figure 13 This is an example process 1300 for monitoring room capacity according to some embodiments of the present disclosure. As in... Figure 12As described herein and in situations involving the spread of infectious diseases, limiting physical contact and close proximity between people can be important for preventing the spread of infectious diseases. This can typically be managed by enforcing capacity limits, for example, in bars or other locations. However, implementing capacity limits on a smaller scale within a location or site with multiple rooms can be difficult. Therefore, embodiments of this disclosure may relate to managing capacity on a room scale. In some embodiments, as described above, this can be used to treat and manage the spread of infectious diseases. However, in some embodiments, the methods described herein can be used to enforce room capacity for use in many other applications. Figure 1 and Figure 9 The described mesh network and system can provide tools for enforcing and managing such protocols.

[0079] In block 1301, the management unit (e.g., management unit 28) can configure a geofence associated with a region. In some embodiments, the region can be a room (e.g., Figure 1 The rooms 24 in System 10 can be, for example, classrooms, hotel rooms, conference rooms, etc., within the protected site. Geofencing can include virtual perimeters of real-world geographical areas; in other words, System 10 can define virtual perimeters for each room within the protected site. This allows for individual viewing of each room, and each room can have an associated room ID for analytical and tracking purposes.

[0080] In block 1302, an administrator (e.g., through management unit 28) can establish capacity associated with a specific area. For example, the administrator might want to set the capacity of a meeting room to ten people. The meeting room can then have a capacity limit of ten people within the system managed by management unit 28, defined by room ID. In block 1303, management unit 28 can identify portable units within an area (e.g., a meeting room). As previously described, portable units (e.g., portable units 14, 16, and 18) can be configured to periodically broadcast their location and other information to management unit 28. Based on a predefined geofence for the area, management unit 28 can identify portable units located within the area. In block 1304, management unit 28 can maintain a count of portable units currently in a predefined area. For example, if six portable units recently broadcast their information and location to the management unit (and that location is within the boundary of the area), then management unit 28 can maintain the current count for that area at 6. In some embodiments, management unit 28 can update the count and increment or decrement the count as portable units continuously broadcast their locations to reflect continuous updates. In block 1305, if the count exceeds the capacity defined in block 1302, the system can generate an alarm, which can be displayed on management unit 28. This notifies the administrators of management unit 28 that the room has exceeded its capacity and identifies which room it is.

[0081] Figure 14 This is an example user interface 1400 according to some embodiments of the present disclosure. In some embodiments, interface 1400 may be displayed on management unit 28 to an administrator or other user. Interface 1400 may be referred to as a dashboard and can help the administrator manage a protected site (e.g., by...). Figure 1 The system 10 protects the organization within the site. In some embodiments, interface 1400 may include a site roster 1401, which may include a list of all individuals being tracked within the site. Each individual may have a defined origin location and status (e.g., on-site or off-site) and may be associated with a portable unit. Note that the type of portable unit may depend on the role of the individual within the organization. In some embodiments, interface 1400 may include a room capacity violation list 1402. Room capacity violations can be identified through... Figure 13 The process 1300 determines this. Each room capacity violation in the list can include the room name and the time since the capacity violation occurred.

[0082] In some embodiments, interface 1400 may include an emergency report 1403. Emergency report 1403 may include an incident (e.g., caused by...) Figure 10The interface 1400 includes a list of incidents defined in process 1000 and various information associated with each incident, such as status, time, and the person from whom the incident originated. In some embodiments, the interface 1400 may include a contact tracing report 1404 for a specific person (e.g., Teresa Kendall as shown) selected from the site roster 1401. The contact tracing report 1404 may include a list of people contacted by the selected person and the duration of the contact. In some embodiments, the contact tracing report 1404 may include a drop-down menu 1405 that allows a user / administrator to select a desired time period to view contact statistics. In some embodiments, the interface 1400 may include a temperature log 1406. The temperature log 1406 for the selected person may plot the selected person's temperature as a function of time (e.g., daily). In some embodiments, temperatures may be received and stored using a QR code (e.g., QR code 1408). For example, assuming Teresa Kendall is a teacher at a school and has a portable unit 14 associated with her, her assigned portable unit 14 may include a QR code and be associated with her profile accessible by the management unit 28. Her temperature can be measured using a thermometer, and the temperature can be stored along with a profile using a QR code. In some embodiments, this can allow for tracking of a person's temperature over time, which can allow for more information to be obtained when performing contact tracing (e.g., as described with respect to process 1200). In some embodiments, temperature log 1406 may include drop-down menu 1407, in which users / administrators can use to change the time range that can be viewed.

[0083] Specific embodiments have been described in the foregoing specification. However, those skilled in the art will understand that various modifications and changes can be made without departing from the scope of the appended claims. For example, although this disclosure has been described and illustrated in connection with schools, it is not intended to be so limiting. In the case of an office, portable units 14, 16 may be associated with an office manager, and portable unit 18 may be associated with an employee. Therefore, the specification and drawings are to be considered illustrative rather than restrictive, and all such modifications are intended to be included within the scope of this teaching.

[0084] Benefits, advantages, solutions to problems, and any elements that may lead to or make any benefit, advantage, or solution more apparent shall not be construed as key, requirement, or essential features or elements of any or all claims.

[0085] The abstract provided is intended to allow the reader to quickly determine the nature of the technical disclosure. It is understood that this abstract is not to be construed as limiting the scope or meaning of the claims. Furthermore, as can be seen from the detailed description above, various features are combined in various embodiments to simplify this disclosure. This method of disclosure should not be construed as reflecting an intention that the claimed embodiments require more features than expressly listed in each claim. Rather, as reflected in the following claims, the inventive subject matter does not consist of all features of a single disclosed embodiment. Therefore, the following claims are incorporated herein by reference, each claim existing independently as a separate claimed subject matter.

[0086] It should be understood that the disclosed subject matter is not limited to its application of construction details and the arrangement of components set forth in the following description or shown in the accompanying drawings. The disclosed subject matter is capable of other embodiments and can be practiced and performed in various ways. Furthermore, it should be understood that the wording and terminology used herein are for descriptive purposes and should not be considered limiting. Therefore, those skilled in the art will understand that the concepts upon which this disclosure is based can readily be used as the basis for designing other structures, methods, and systems to achieve the various objectives of the disclosed subject matter. Therefore, it is important that the claims be considered to include such equivalent structures, provided they do not depart from the spirit and scope of the disclosed subject matter.

[0087] Although the disclosed subject matter has been described and illustrated in the foregoing illustrative embodiments, it should be understood that this disclosure is made by way of example only and many changes may be made without going into the implementation details of the disclosed subject matter that depart from the spirit and scope of the disclosed subject matter.

Claims

1. A method for managing area capacity, comprising: configuring a geo-fence in a mesh network that defines an area within a site; establishing a capacity associated with the area; analyzing locations of a plurality of portable units worn or carried by a plurality of selected users within the mesh network; identifying a plurality of portable units located within the area; maintaining a current count of the number of portable units located within the area; and generating an alert to an administrative unit in response to the current count exceeding the capacity, wherein the administrative unit is part of the mesh network; wherein at least one of the plurality of portable units includes a plurality of buttons for sending a signal to the administrative unit for a particular type of emergency; a subset of the plurality of portable units is configured to illuminate an LED associated with the emergency in response to a button on at least one of the plurality of portable units being pressed until a deactivation signal is received from the administrative unit. the mesh network includes a plurality of fixed units, wherein each of the plurality of portable units, each of the plurality of fixed units, and the administrative unit are in wireless communication with all other units in the mesh network and are configured to receive all signals.

2. The method of claim 1, wherein, each of the plurality of portable units, each of the plurality of fixed units, and the administrative unit are configured to interact with all other units in the mesh network.

3. The method of claim 2, wherein, locations of portable units are determined by analyzing a plurality of received signal strength indicators (RSSIs) from the plurality of fixed units.

4. The method of claim 2, wherein, at least a portion of the plurality of portable units are configured to broadcast information to the administrative unit at a first predefined frequency when stationary.

5. The method of claim 1, wherein, at least one of the plurality of portable units is configured to broadcast information to the administrative unit at a frequency higher than the first predefined frequency when mobile.

6. The method of claim 5, wherein, the information includes at least one of:

7. The method of claim 5, wherein, an ID associated with a portable unit; a location associated with the portable unit; a name associated with the portable unit; or a role associated with the portable unit. ​

Images