Choosing the Right LoRaWAN Gateway for Indoor Employee Badge Tracking and SOS Safety Systems
Selecting a gateway for an indoor employee badge project requires more than comparing coverage claims, channel quantity or product price. The LoRaWAN gateway is a critical communication bridge between personnel badges and the management platform. Its model, frequency plan, installation position, network backhaul and redundancy design directly affect location-data delivery, SOS response and overall system reliability.
In factories, warehouses, hospitals, mines, chemical plants and multi-floor buildings, walls, machinery, metal shelves and reinforced-concrete floors can change radio performance significantly. A gateway that performs well in an open office may not provide the same coverage inside an industrial building.
For this reason, gateway quantity should not be calculated from floor area alone. A reliable project requires a review of the complete indoor personnel tracking system, followed by radio planning and a field test under actual operating conditions.
Components of an Indoor Personnel Tracking System
A typical indoor personnel-tracking and worker-safety solution includes:
LoRaWAN employee tracking badges
BLE beacons or another indoor positioning infrastructure
Indoor or outdoor LoRaWAN gateways
A LoRaWAN network server
Cloud-based or privately deployed application servers
Digital building and floor maps
Web, Android and iOS management applications
SOS, geofence and abnormal-status alarm functions
APIs for integration with access control, attendance, EHS or dispatch systems
Each component performs a different role. BLE beacons help identify the room, corridor, floor or work zone. The personnel badge scans the surrounding beacon IDs and combines this information with employee identity, battery level, motion status and alarm events.
The badge then sends the collected data through LoRaWAN. The gateway receives the radio packets and forwards them to a network server through Ethernet, Wi-Fi or 4G. The lora8 management platform processes the information and displays the employee’s latest known zone, historical movement and safety status.
A LoRaWAN Gateway Is Not the Indoor Positioning Source
One common purchasing mistake is treating the LoRaWAN gateway as the device that directly calculates a worker’s indoor location. In most BLE and LoRaWAN fusion solutions, the gateway provides the communication channel but does not independently determine the room-level position.
Indoor accuracy mainly depends on:
The positioning technology used by the badge
BLE beacon placement and density
Signal-scanning rules
Building and floor identifiers
The positioning algorithm
Electronic-map calibration
Wall materials and room layout
Radio interference
The required location-update interval
A LoRaWAN indoor positioning badge can identify nearby BLE beacons and send the result through the LoRaWAN gateway. Therefore, beacon planning and gateway planning must be completed separately and then tested as one integrated system.
Six Factors That Determine Gateway Selection
1. Building structure and radio obstacles
Reinforced-concrete walls, fire doors, elevators, stairwells, pipelines, metal machines, high warehouse racks and stored products can attenuate or reflect radio signals. Underground rooms and enclosed production areas may require additional gateways even when their floor area is relatively small.
The engineering team should identify:
Thick walls and fire partitions
Elevator and ventilation shafts
Metal-processing areas
High-density storage racks
Electrical rooms
Basements and underground corridors
Hazardous working zones
Emergency exits and assembly points
Gateway positions should provide coverage for important work areas rather than merely producing the largest possible theoretical radius.
2. Floors and vertical coverage
A single gateway installed on the middle floor should not automatically be expected to cover an entire multi-floor building. Reinforced-concrete slabs can create substantial loss between floors, while elevator shafts may produce irregular signal behavior.
Each floor should be tested separately. For critical personnel-safety projects, installing independent gateways on major floors is normally more reliable than depending on vertical penetration from a single device.
If employees regularly move between buildings or floors, building IDs and floor IDs must also be configured correctly on the platform. This prevents the system from displaying a worker on the wrong floor when different areas contain similar BLE beacon signals.
3. Number of badges and reporting frequency
The customer should determine how many badges will operate within the project and how frequently they must upload data. A system with 50 badges reporting every several minutes creates a different network load from a project with thousands of badges reporting frequently.
SOS events, fall alarms and evacuation procedures may also cause many devices to transmit within a short period. Gateway planning should therefore consider both normal traffic and peak traffic.
Simply stating that a gateway can connect to a large number of nodes does not guarantee identical performance in every project. Payload size, spreading factor, reporting interval, retransmission settings and radio interference all affect practical capacity.
4. Regional LoRaWAN frequency plan
The personnel badges, gateways and network server must use compatible regional parameters. Common frequency plans include:
CN470
EU868
IN865
RU864
US915
AU915
KR920
AS923-1, AS923-2, AS923-3 and AS923-4
A 915 MHz product is not automatically suitable for every 915 MHz market. US915 and AU915 use different regional channel plans, while AS923 also contains regional variations.
The gateway frequency, end-device frequency, channel mask and network-server configuration must match. The project owner should confirm the country of deployment before ordering hardware or developing customized firmware.
5. Backhaul connection
After receiving LoRaWAN packets, the gateway must forward them to the server through an IP network. Common backhaul options include Ethernet, Wi-Fi and 4G.
Ethernet is generally preferred for permanent indoor deployment when a stable wired network is available. PoE can simplify installation by supplying data and power through the same cable.
Wi-Fi is useful for offices, demonstrations and temporary projects, but its stability depends on the local wireless network. Changes to passwords, access points or firewall rules may interrupt gateway connectivity.
A 4G backhaul is valuable for construction sites, independent warehouses, remote buildings and locations without fixed broadband. It can also be considered as a backup connection when alarm reliability is important.
The platform should monitor gateway online status and issue an alert if a gateway or its backhaul connection becomes unavailable.
6. Power supply and recovery
Gateway availability depends on both network access and power. The installation plan should confirm whether AC power, PoE or another supply method is available at each proposed position.
Hospitals, mines, chemical plants and other safety-critical environments may require UPS backup power. After a power or network interruption, the gateway should be able to restart and reconnect without requiring repeated manual intervention.
Gateway Selection: UG63, UG56 or UG67
UG63 for small indoor projects and pilot testing
The Milesight UG63 mini indoor LoRaWAN gateway is suitable for offices, laboratories, shops, small workshops, demonstration systems and initial proof-of-concept deployments.
Its compact design is useful where installation space and project cost must be controlled. It can also be used to verify badge communication, frequency settings and platform integration before a larger rollout.
However, buyers should not assume that one compact gateway will cover every room of a complex industrial building. A site test is still required.
UG56 for industrial indoor personnel tracking
The Milesight UG56 industrial LoRaWAN gateway can be considered for factories, warehouses, hospitals, schools, office buildings and multi-floor personnel-safety projects.
It supports Ethernet, Wi-Fi, optional 4G and PoE, providing greater flexibility when different buildings have different network conditions. Desktop, wall and DIN-rail installation options also make it suitable for control rooms and industrial cabinets.
For important indoor projects, multiple UG56 gateways can be arranged according to floors, production zones and radio obstacles.
UG67 for outdoor areas and mixed indoor-outdoor coverage
The Milesight UG67 outdoor LoRaWAN gateway uses an IP67-rated enclosure and is suitable for factory yards, industrial parks, construction sites and projects where employees move between indoor and outdoor areas.
Installing an outdoor gateway at a suitable height can improve open-area coverage. However, an outdoor gateway should not be expected to penetrate every internal wall, basement or equipment room. A mixed project may require UG67 coverage outdoors and UG56 or UG63 gateways inside the buildings.
How to Plan Gateway Locations
Gateway placement should begin with building drawings rather than product purchasing. The customer should mark:
Floors and building boundaries
Employee work zones
Hazardous and restricted areas
Corridors and stairways
Basements and equipment rooms
Loading areas and outdoor yards
Emergency exits
Evacuation assembly points
Available Ethernet and PoE ports
Locations with stable AC power
Areas where 4G signal is available
Gateways should normally be installed above major obstacles and away from enclosed metal cabinets. Antenna orientation, cable loss and nearby interference sources should also be checked.
Placing every gateway in a convenient IT room may simplify maintenance, but it may not provide the best radio coverage. Communication quality and maintenance access must be balanced.
SOS Reliability and Redundant Coverage
A normal positioning report and an emergency alarm do not have the same operational importance. A missed periodic report may only delay a map update, while a missed SOS alarm can affect emergency response.
A LoRaWAN SOS employee badge should be tested from every important working area, including isolated rooms, stairs, basements, machine areas and emergency assembly points.
Critical zones can use overlapping coverage so the same message may be received by more than one gateway. The system should also test:
Repeated SOS transmissions
Alarm acknowledgement
Escalation to supervisors
Audible and visual notifications
Mobile application notifications
Gateway-disconnection alarms
Server and Internet interruption
Alarm records and response timestamps
Redundancy should be designed according to actual safety requirements rather than added only after the project experiences communication failures.
Field Testing Before Mass Deployment
A field test should be completed before gateways and badges are purchased in volume. Testing should not be limited to an empty building.
Radio conditions may change when:
Machines are operating
Fire doors are closed
Warehouse racks are fully loaded
Vehicles enter loading areas
Many workers carry badges simultaneously
Elevators are moving
Wi-Fi networks are heavily used
Production lines create electromagnetic interference
The pilot deployment should test normal positioning reports, SOS alarms, low-battery messages, device-offline alerts, simultaneous transmissions and backhaul recovery.
The engineering team should record the gateway used, installation height, test location, RSSI, SNR, packet reception and alarm-delivery time. Based on these results, gateway quantity and placement can be adjusted before mass installation.
Jinshengchang Indoor Personnel Safety Solution
Shenzhen Jinshengchang Technology Co., Ltd. provides an integrated solution covering LoRaWAN personnel badges, BLE beacons, indoor and outdoor gateways, network integration and the self-developed lora8 IoT platform.
With 13 years of experience in GPS, LoRa, IoT hardware, firmware and positioning-platform development, Jinshengchang can support:
LoRaWAN employee badge development
SOS button and alarm-workflow customization
BLE, GNSS, Wi-Fi and LoRa integration
PCB and enclosure development
Regional frequency adaptation
Firmware and protocol customization
Android and iOS applications
Multilingual and white-label platforms
API, SDK and webhook integration
Cloud or private-server deployment
Gateway selection and coverage planning
Sample testing and mass production
To prepare an accurate gateway plan and quotation, customers should provide the deployment country, building drawings, number of floors, number of employees, required positioning accuracy, reporting interval, SOS procedure, available backhaul networks and third-party integration requirements.
Contact: Wang Tao / Ms. Hu
Mobile and WhatsApp: +86 13480881974 / +86 17722420256
Email: jietainana@gmail.com