Comprendiendo RSSI y la Fuerza de la Señal para una Planificación Óptima de Canales

Esta guía ofrece un análisis técnico exhaustivo sobre RSSI, la Relación Señal/Ruido (SNR) y los principios de propagación de RF para una planificación óptima de canales. Proporciona a gerentes de TI, arquitectos de red y directores de operaciones de recintos estrategias accionables para mitigar la Interferencia Co-Canal y la Interferencia de Canal Adyacente, optimizar la ubicación de los AP y aprovechar la analítica para un impacto empresarial medible en entornos de hotelería, comercio minorista y sector público.

📖 9 min de lectura📝 2,009 palabras🔧 2 ejemplos resueltos❓ 3 preguntas de práctica📚 9 definiciones clave

Escucha esta guía

Ver transcripción del podcast

Understanding RSSI and Signal Strength for Optimal Channel Planning
A Purple WiFi Intelligence Briefing

[INTRODUCTION & CONTEXT — approximately 1 minute]

Welcome to the Purple WiFi Intelligence Briefing. I'm your host, and today we're getting into the fundamentals that underpin every high-performing wireless network: RSSI, signal strength, and how they drive optimal channel planning.

If you're an IT manager, network architect, or venue operations director, you've almost certainly encountered the frustration of a Wi-Fi network that looks fine on paper but performs poorly in practice. Guests complaining about dropped connections. Handheld scanners losing signal mid-transaction. Video calls breaking up in the boardroom. The root cause, more often than not, comes back to a misunderstanding of what RSSI actually tells you — and more importantly, what it doesn't.

In the next ten minutes, I want to give you a clear, practical framework for understanding these metrics and translating them into better channel planning decisions. This isn't academic theory. This is the kind of briefing I'd give a client before a major deployment.

Let's get into it.

[TECHNICAL DEEP-DIVE — approximately 5 minutes]

So, what is RSSI? RSSI stands for Received Signal Strength Indicator. It's a relative measurement of the power level of a radio frequency signal as received by a client device. It's expressed in negative decibels relative to a milliwatt — so negative dBm. The closer to zero, the stronger the signal. Minus 30 dBm is excellent. Minus 90 dBm is effectively unusable.

But here's the critical point that many deployments get wrong: RSSI alone does not tell you whether a connection is good. It tells you how loud the signal is. It does not tell you how clear it is.

That's where Signal-to-Noise Ratio — SNR — comes in. SNR is the difference in decibels between your received signal and the ambient noise floor. If your RSSI is minus 65 dBm and your noise floor is minus 90 dBm, your SNR is 25 dB. That's the minimum you need for the high-order modulation schemes — things like 256-QAM — that deliver real throughput in 802.11ac and 802.11ax networks.

Think of it this way. Imagine you're in a quiet library. Someone whispers to you from across the room. You can hear them clearly — that's a good SNR. Now imagine you're at a stadium during a match. Someone shouts at you from the same distance. The signal is louder, but the noise is also much higher. You might struggle to understand them. That's exactly what happens in a noisy RF environment.

Now, why does this matter for channel planning?

Wi-Fi is a shared medium. Every device on the same channel has to take turns transmitting, governed by a protocol called CSMA/CA — Carrier-Sense Multiple Access with Collision Avoidance. Before transmitting, every device listens to check if the channel is clear. If it hears another device, it backs off and waits.

Co-Channel Interference — CCI — occurs when multiple access points on the same channel can hear each other. They all back off. They all wait. Channel utilization goes through the roof, and latency spikes, even when actual client traffic is low. This is one of the most common performance killers in enterprise deployments, and it's entirely avoidable with proper channel planning.

Adjacent Channel Interference — ACI — is a different problem. In the 2.4 GHz band, channels are only 5 MHz apart but each channel is 22 MHz wide. So they overlap. If you put an AP on channel 3 next to an AP on channel 1, the RF energy from channel 3 bleeds into channel 1, raising the noise floor and degrading SNR. The solution in 2.4 GHz is to use only channels 1, 6, and 11 — the three non-overlapping channels.

In the 5 GHz band, you have far more spectrum to work with. You can use DFS channels — Dynamic Frequency Selection — to expand your available channel set, though you need to be aware that radar detection can force a channel change, which causes a brief disruption.

Now, a word on channel widths. There's a temptation to use wider channels — 40, 80, or even 160 MHz — because they offer higher theoretical throughput. And in a low-density environment, that's fine. But in a high-density venue — a hotel, a stadium, a conference centre — wider channels mean fewer non-overlapping options, which means more CCI. In those environments, 20 MHz channels in 2.4 GHz and 20 or 40 MHz in 5 GHz is almost always the right call.

Let me talk about AP placement and power tuning, because this is where I see the most mistakes in the field.

There's a common misconception that more transmit power equals better coverage equals better performance. It's wrong. Setting AP transmit power too high creates what we call an asymmetric link. The AP can shout loudly, and the client can hear it clearly from a long distance. But the client — a smartphone, a laptop, a handheld scanner — has a much weaker transmitter. It can't shout back with the same power. So the AP can't hear the client reliably.

This also creates the "sticky client" problem. A device in a far corner of the building can still hear the AP at minus 70 or minus 75 dBm. It decides the connection is acceptable and stays put, even when it moves physically closer to a different AP. The client doesn't roam. Performance degrades. The fix is to tune AP transmit power down — typically to 10 to 14 dBm — to match the client's capabilities, and to ensure sufficient AP density so that clients are always close to an AP.

To facilitate seamless roaming, you should implement the 802.11k, 802.11v, and 802.11r protocols. 802.11k provides clients with a neighbor report — a list of nearby APs they could roam to. 802.11v allows the network to suggest that a client roam to a better AP. And 802.11r enables fast BSS transition, dramatically reducing the time it takes to re-authenticate when roaming. Together, these protocols ensure that roaming decisions are driven by RSSI thresholds rather than client inertia.

[IMPLEMENTATION RECOMMENDATIONS & PITFALLS — approximately 2 minutes]

Right. Let's talk about implementation. Here are the key steps I'd walk through with any client.

First, define your requirements before you touch any hardware. What is the minimum RSSI you need to support your most demanding application? For voice over Wi-Fi, you need minus 65 dBm or better. For high-throughput data, minus 70 dBm. For basic connectivity, minus 75 dBm. And critically, identify your Least Capable, Most Important device — the device with the weakest radio that absolutely must work reliably. Design for that device.

Second, conduct a proper site survey. Not just a predictive survey using software, but an active survey with real hardware in the real environment. Measure RSSI and SNR. Use a spectrum analyser to identify non-Wi-Fi interference sources — microwave ovens, Bluetooth devices, DECT phones, even some industrial equipment. These raise the noise floor and degrade SNR without showing up on a standard Wi-Fi scan.

Third, plan your channels before you deploy. In 2.4 GHz, stick to 1, 6, and 11. In 5 GHz, create a channel reuse plan that maximises the physical separation between APs on the same channel. Use 20 MHz channels in dense environments.

Fourth, tune your transmit power down. Match it to your client devices. Ensure 15 to 20 percent cell overlap to support seamless roaming.

Fifth, set minimum mandatory data rates. Disable the legacy rates — 1, 2, 5.5, and 11 Mbps in 2.4 GHz. This forces clients to roam sooner when RSSI degrades, rather than clinging to a distant AP at a low data rate.

Now, the pitfalls. The most common one I see is over-reliance on automatic channel assignment. Most enterprise AP vendors offer automatic radio resource management — it sounds great in theory. In practice, in complex environments, it can make poor decisions. Always validate the channel plan manually after deployment.

The second pitfall is ignoring the noise floor. A network can look fine on an RSSI heatmap but perform terribly because the noise floor is elevated. Always measure SNR, not just RSSI.

The third pitfall is deploying a guest Wi-Fi solution without thinking about the RF implications. Captive portals, analytics platforms, and location services all depend on a well-architected RF environment. If the RF is broken, the analytics will be inaccurate and the guest experience will be poor.

[RAPID-FIRE Q&A — approximately 1 minute]

Let me run through a few quick questions I hear regularly.

What RSSI do I need for a reliable connection? Minus 65 dBm or better for primary coverage. Minus 70 dBm for roaming overlap zones.

Should I use 80 MHz channels in a stadium? Almost never. The reduction in available non-overlapping channels causes CCI that far outweighs the throughput benefit.

My site survey shows good RSSI but performance is still poor. What's wrong? Check your SNR. Check your channel utilization. Check for sticky clients. One of these three is almost certainly the culprit.

Is 2.4 GHz still worth deploying? Yes, for legacy device compatibility and penetration through walls. But limit it to channels 1, 6, and 11, and consider disabling it on every other AP in dense environments to reduce CCI.

[SUMMARY & NEXT STEPS — approximately 1 minute]

Let me wrap up with the key takeaways.

RSSI tells you signal strength. SNR tells you signal quality. Always optimise for SNR, not just RSSI.

Design for capacity, not coverage. More APs at lower power beats fewer APs at high power in any dense environment.

Use non-overlapping channels. In 2.4 GHz, that's channels 1, 6, and 11. In 5 GHz, build a proper channel reuse plan.

Implement 802.11k, v, and r to ensure roaming is driven by RF conditions, not client stubbornness.

Validate with a real active site survey. Software predictions are a starting point, not a final answer.

And finally, remember that your RF architecture is the foundation for everything else — your guest Wi-Fi experience, your analytics, your location services, your operational efficiency. Get the RF right, and everything else becomes much easier.

If you want to go deeper on channel width selection, check out the Purple guide on 20 MHz versus 40 MHz versus 80 MHz. And if you're looking at deploying guest Wi-Fi with analytics at scale, the Purple platform is hardware-agnostic and integrates with your existing infrastructure.

Thanks for listening. Until next time.

Puntos clave

✓RSSI measures signal strength in dBm; SNR measures signal clarity. Always target SNR > 25 dB, not just RSSI > -70 dBm.
✓Co-Channel Interference (CCI) is the primary performance killer in dense deployments — mitigate it through channel planning and power tuning, not just AP density.
✓In 2.4 GHz, use only channels 1, 6, and 11. No exceptions. Any other assignment causes Adjacent Channel Interference.
✓Design for capacity, not coverage: more APs at lower transmit power (10–14 dBm) outperforms fewer APs at maximum power in any high-density environment.
✓Implement 802.11k/v/r to enable intelligent, low-latency roaming — without these protocols, sticky clients will degrade performance regardless of AP density.
✓Identify the Least Capable, Most Important (LCMI) device before designing the RF architecture and use it as the design baseline.
✓RF architecture is the foundation for guest Wi-Fi, analytics, and location services — invest in a proper active site survey and ongoing monitoring to protect that foundation.

Resumen Ejecutivo

Para CTOs y arquitectos de red que supervisan recintos de alta densidad —ya sea en Hotelería , Comercio Minorista o grandes espacios públicos—, desplegar una infraestructura inalámbrica robusta es fundamental para la eficiencia operativa y la satisfacción del cliente. Esta guía técnica explora qué es RSSI y cómo funciona como una métrica crítica para una planificación óptima de canales. Al ir más allá de los mapas de cobertura básicos y comprender los matices de la propagación de RF, la Interferencia Co-Canal (CCI) y la Interferencia de Canal Adyacente (ACI), los líderes de TI pueden diseñar redes que soporten aplicaciones de alto rendimiento y baja latencia a escala. Examinamos cómo los umbrales precisos de RSSI impulsan las decisiones de roaming, cómo el ancho del canal impacta la eficiencia espectral y cómo el aprovechamiento de plataformas avanzadas de WiFi Analytics puede mitigar riesgos y ofrecer un ROI medible. La guía cubre los protocolos de roaming IEEE 802.11k/v/r, la optimización de SNR, la estrategia de ubicación de AP y escenarios de implementación reales de entornos de hotelería y comercio minorista.

Análisis Técnico Detallado

¿Qué es RSSI? Definición y Medición

El Indicador de Fuerza de Señal Recibida (RSSI) es una medida relativa del nivel de potencia de una señal de RF recibida por un dispositivo cliente. Medido en decibelios relativos a un milivatio (dBm), RSSI se expresa como un valor negativo —cuanto más cerca de cero, más fuerte es la señal. Un valor de -30 dBm representa una señal excepcionalmente fuerte (típicamente solo alcanzable a un metro del AP), mientras que -90 dBm está en el umbral de usabilidad. La siguiente tabla proporciona una referencia práctica para los umbrales de RSSI y su idoneidad de aplicación correspondiente:

RSSI (dBm)	Calidad de la Señal	Aplicaciones Adecuadas
-30 a -50	Excelente	Todas las aplicaciones, incluyendo streaming 4K y VoWiFi de alta densidad
-51 a -65	Buena	Datos de alto rendimiento, VoWiFi, analítica de ubicación
-66 a -70	Regular	Datos estándar, navegación web, correo electrónico
-71 a -80	Pobre	Solo conectividad básica; VoWiFi poco fiable
Por debajo de -80	Inutilizable	Desconexiones frecuentes; no apto para implementación empresarial

RSSI vs. Relación Señal/Ruido (SNR)

RSSI por sí solo es insuficiente para evaluar la calidad de la red. La Relación Señal/Ruido (SNR) proporciona una imagen más precisa de la calidad del enlace al comparar la fuerza de la señal recibida con el nivel de ruido ambiental. Un SNR de 25 dB o superior es típicamente requerido para esquemas de modulación de alto rendimiento como 256-QAM en 802.11ac/ax. Si el nivel de ruido es de -90 dBm y el RSSI es de -65 dBm, el SNR es de 25 dB —el umbral mínimo para una operación fiable de alto rendimiento.

La implicación práctica es significativa: una red puede mostrar excelentes valores de RSSI en un mapa de calor de cobertura y, sin embargo, funcionar mal porque el nivel de ruido se eleva por fuentes de interferencia que no son Wi-Fi (hornos microondas, teléfonos DECT, dispositivos Bluetooth o equipos industriales). Siempre se deben instrumentar tanto RSSI como SNR durante los estudios de sitio y el monitoreo continuo.

La Física de la Propagación y Atenuación de RF

En entornos complejos como hospitales ( Salud ) o centros de tránsito ( Transporte ), las señales de RF sufren atenuación al pasar a través de obstáculos físicos. Los arquitectos de red deben tener en cuenta estas pérdidas específicas de material al realizar estudios de sitio predictivos y definir los límites de las celdas:

Material	Atenuación Típica (dB)
Pladur / Cartón Yeso	3–4 dB
Vidrio (estándar)	2–3 dB
Ladrillo	8–12 dB
Hormigón	12–15 dB
Hormigón Armado / Acero	15–25+ dB
Estanterías Metálicas (comercio minorista)	10–20 dB

La naturaleza logarítmica de la escala de decibelios es fundamental de internalizar: una pérdida de 3 dB reduce a la mitad la potencia de la señal, mientras que una pérdida de 10 dB la reduce en un factor de diez. Una señal que pasa a través de dos paredes de ladrillo (aproximadamente 20 dB de atenuación) es, por lo tanto, 100 veces más débil que la señal transmitida.

Planificación de Canales: CCI y ACI

La planificación óptima de canales requiere mitigar dos tipos distintos de interferencia. La Interferencia Co-Canal (CCI) ocurre cuando los puntos de acceso que operan en el mismo canal pueden "escucharse" entre sí, lo que lleva a la contención del medio y a un aumento de la latencia debido al protocolo CSMA/CA (Acceso Múltiple con Detección de Portadora y Prevención de Colisiones). Cada dispositivo en el canal debe esperar su turno, y cuando múltiples APs están compitiendo simultáneamente, la utilización del canal se dispara incluso bajo una carga de cliente moderada.

La Interferencia de Canal Adyacente (ACI) ocurre cuando los APs operan en canales superpuestos, elevando el nivel de ruido y degradando el SNR. En la banda de 2.4 GHz, solo los canales 1, 6 y 11 no se superponen. Cualquier otra asignación de canal causará ACI con uno o ambos de sus vecinos. En la banda de 5 GHz, la utilización de canales de Selección Dinámica de Frecuencia (DFS) expande el espectro disponible, aunque los eventos de detección de radar pueden forzar cambios de canal, causando breves interrupciones de conectividad.

Al decidir sobre los anchos de canal, consulte 20MHz vs 40MHz vs 80MHz: ¿Qué Ancho de Canal Debería Usar? (o la versión en italiano: 20MHz vs 40MHz vs 80MHz: Quale larghezza di canale dovresti usare? ). El principio fundamental: los canales más anchos ofrecen un mayor rendimiento teórico, pero reducen el número de opciones sin superposición, lo que aumenta la CCI en implementaciones densas.

Guía de implementación

Paso 1: Definir los requisitos e identificar el dispositivo LCMI

Antes de implementar el hardware, defina el Área de Cobertura Primaria (PCA) y el Área de Cobertura Secundaria (SCA). Críticamente, identifique el dispositivo Menos Capaz, Más Importante (LCMI), es decir, el dispositivo con la radio más débil que debe funcionar de manera fiable. Esto suele ser un escáner de mano heredado en un almacén, un modelo específico de dispositivo médico en un hospital o un teléfono inteligente antiguo en un entorno de hostelería. Diseñe toda la arquitectura de RF para cumplir con los requisitos mínimos de RSSI de ese dispositivo, y todo lo demás funcionará mejor.

Paso 2: Realizar un estudio de sitio activo

Ejecute un estudio de sitio activo para medir el RSSI y el SNR en el mundo real, no solo un estudio predictivo utilizando software. Utilice herramientas de análisis de espectro para identificar fuentes de interferencia que no sean Wi-Fi. Asegúrese de que la cobertura primaria cumpla con el umbral de -65 dBm y la cobertura secundaria (para zonas de superposición de roaming) cumpla con -70 dBm. Documente el nivel de ruido en todas las áreas, ya que esto determinará el SNR alcanzable y las velocidades de datos máximas soportadas.

Paso 3: Ubicación del AP y ajuste de potencia

Evite la falacia de que "más fuerte es mejor". Configurar la potencia de transmisión del AP demasiado alta crea enlaces asimétricos donde el cliente puede escuchar el AP claramente, pero el AP no puede recibir de forma fiable las transmisiones más débiles del cliente. Esta es la causa raíz del problema del cliente pegajoso (sticky client): dispositivos que permanecen asociados a un AP distante a pesar de estar físicamente más cerca de otro. Ajuste la potencia de transmisión del AP a 10–14 dBm para que coincida con las capacidades del cliente y asegure una superposición de celda del 15–20% para facilitar el roaming sin interrupciones según IEEE 802.11k/v/r.

Paso 4: Imponer velocidades de datos mínimas obligatorias

Deshabilite las velocidades de datos heredadas (1, 2, 5.5 y 11 Mbps en 2.4 GHz; 6 y 9 Mbps en 5 GHz). Esto eleva el umbral mínimo de RSSI en el que un cliente considera que la conexión es aceptable, lo que fuerza decisiones de roaming más tempranas y evita que los clientes de baja velocidad consuman un tiempo de aire desproporcionado.

Paso 5: Integrar Guest WiFi y análisis

La implementación de una solución empresarial de Guest WiFi requiere una autenticación perfecta que no degrade la experiencia del usuario. Implemente 802.1X para dispositivos corporativos y portales cautivos seguros para invitados, con WPA3 donde la compatibilidad del dispositivo lo permita. Enfoques modernos como How a wi fi assistant Enables Passwordless Access in 2026 reducen la fricción de incorporación mientras mantienen el cumplimiento de los requisitos de PCI DSS y GDPR. La arquitectura de RF descrita en esta guía es el requisito previo para análisis y servicios de ubicación fiables; si la RF está mal diseñada, los datos serán inexactos.

Mejores prácticas

Diseñe para la capacidad, no para la cobertura. En entornos modernos de alta densidad, la limitación casi nunca es el alcance de la señal, sino la contención del tiempo de aire. Implemente más AP con menor potencia de transmisión en lugar de menos AP con alta potencia. Esto reduce la CCI, mejora el SNR y aumenta el número de clientes que pueden ser atendidos simultáneamente.

Estandarice los anchos de canal por entorno. Por defecto, use 20 MHz en 2.4 GHz universalmente. En 5 GHz, use 20 MHz en entornos de muy alta densidad (estadios, salas de conferencias) y 40 MHz en entornos de densidad moderada (hoteles, comercios). Reserve 80 MHz solo para escenarios de baja densidad y alto rendimiento.

Implemente la pila de protocolos de roaming. Habilite 802.11k (Medición de recursos de radio), 802.11v (Gestión de transición BSS) y 802.11r (Transición rápida BSS) en todos los AP. Esto asegura que las decisiones de roaming sean impulsadas por las condiciones de RF en lugar de la inercia del cliente, y reduce la latencia de reautenticación de cientos de milisegundos a menos de 50 ms.

Valide manualmente los canales asignados automáticamente. La mayoría de los proveedores de AP empresariales ofrecen Gestión Automática de Recursos de Radio (RRM). Si bien es útil como línea de base, el RRM puede tomar decisiones subóptimas en entornos complejos. Siempre audite el plan de canales después de la implementación y anule donde sea necesario.

Monitoree continuamente, no solo en la implementación. Los entornos de RF cambian con el tiempo: aparecen nuevas fuentes de interferencia, los patrones de ocupación cambian y las actualizaciones de firmware alteran el comportamiento de la radio. Utilice una plataforma de WiFi Analytics con monitoreo continuo de RF para detectar la degradación antes de que afecte a los usuarios.

Para estrategias más amplias sobre cómo aprovechar la infraestructura de red para obtener resultados comerciales, consulte How To Improve Guest Satisfaction: The Ultimate Playbook .

Solución de problemas y mitigación de riesgos

El problema del cliente pegajoso (Sticky Client)

Síntoma: Los dispositivos permanecen conectados a un AP distante con un RSSI deficiente (-80 dBm) a pesar de estar físicamente más cerca de otro AP con una señal fuerte.

Causa raíz: La potencia de transmisión del AP es demasiado alta, creando un enlace asimétrico. El cliente escucha bien el AP y no inicia un roaming. Alternativamente, los protocolos 802.11k/v están deshabilitados, dejando al cliente sin orientación sobre APs mejores disponibles.

Mitigación: Reduzca la potencia de transmisión del AP a 10–12 dBm. Habilite 802.11k/v/r. Establezca velocidades de datos mínimas obligatorias para forzar a los clientes a realizar roaming cuando el RSSI se degrade por debajo del umbral de velocidad mínima.

Alta interferencia cocanal

Síntoma: La utilización del canal supera consistentemente el 40–50% incluso bajo una carga de cliente moderada, lo que resulta en una latencia elevada y un rendimiento deficiente.

Causa raíz: Los AP en el mismo canal están colocados demasiado cerca entre sí, o los anchos de canal son demasiado amplios para la densidad de implementación.

Mitigación: Reduzca el ancho de canal a 20 MHz. Audite el plan de canales para maximizar la separación física entre los AP en el mismo canal. En 2.4 GHz, considere deshabilitar la radio en cada segundo AP en implementaciones muy densas.

Nivel de Ruido Elevado

Síntoma: Los valores de RSSI parecen aceptables en los mapas de calor, pero el rendimiento es deficiente y las conexiones son inestables.

Causa Raíz: Fuentes de interferencia no-Wi-Fi (hornos de microondas, teléfonos DECT, equipos industriales, Bluetooth) están elevando el nivel de ruido, degradando la SNR por debajo del umbral requerido para la modulación de alto orden.

Mitigación: Utilice un analizador de espectro para identificar y caracterizar las fuentes de interferencia. Migre los clientes afectados a 5 GHz cuando sea posible, ya que la mayoría de las interferencias no-Wi-Fi se concentran en 2.4 GHz. Si las fuentes de interferencia no pueden eliminarse, aumente la densidad de AP para mejorar el RSSI y así mantener una SNR adecuada a pesar del nivel de ruido elevado.

A medida que las redes se expanden a espacios municipales y públicos, la planificación estratégica se vuelve cada vez más crítica. Para obtener información sobre implementaciones en el sector público, lea cómo Purple nombra a Iain Fox como VP de Crecimiento – Sector Público para Impulsar la Inclusión Digital y la Innovación en Ciudades Inteligentes .

ROI e Impacto Comercial

Optimizar el RSSI y la planificación de canales impacta directamente en los resultados finales en múltiples dimensiones. La siguiente tabla resume los resultados comerciales clave asociados con una red inalámbrica bien diseñada:

Resultado Comercial	Mecanismo	Impacto Típico
Costos de soporte de TI reducidos	Menos quejas de conectividad; menos visitas al sitio	Reducción del 20-40% en tickets de soporte relacionados con Wi-Fi
Satisfacción del huésped mejorada	Conectividad confiable y de alta velocidad en todo el recinto	Mejora medible en NPS y puntuaciones de reseñas
Análisis de ubicación precisos	Densidad de AP y SNR suficientes para una trilateración confiable	Precisión de ubicación de menos de 3 metros para análisis de afluencia
Captura de datos de primera parte	Rendimiento confiable del Captive Portal	Mayores tasas de finalización en la incorporación de Wi-Fi para huéspedes
Eficiencia operativa	Conectividad confiable para dispositivos portátiles, sistemas POS, IoT	Reducción de fallas en transacciones y tiempo de inactividad operativa

Para los operadores de recintos, el Wi-Fi confiable ya no es un centro de costos, sino un facilitador de ingresos. Al garantizar una fuerza de señal consistente y una SNR alta, los recintos pueden implementar con confianza Captive Portals para capturar datos de primera parte, impulsando campañas de marketing personalizadas y aumentando el valor de vida del cliente. La inversión en un diseño de RF adecuado produce un ROI medible a través de la eficiencia operativa, un compromiso digital mejorado y la capacidad de implementar análisis avanzados y servicios de ubicación con confianza.

La plataforma agnóstica de hardware de Purple se integra con la infraestructura existente para proporcionar la capa de análisis sobre una base de RF bien diseñada, convirtiendo los datos de fuerza de señal en inteligencia comercial accionable en entornos de Hostelería , Comercio Minorista , Atención Médica y Transporte .

Definiciones clave

RSSI (Received Signal Strength Indicator)

A relative measurement of the power level of an RF signal received by a client device, expressed in negative dBm. The closer to zero, the stronger the signal.

Used to determine coverage boundaries, trigger roaming decisions, and assess basic signal availability. Not sufficient on its own to evaluate link quality.

SNR (Signal-to-Noise Ratio)

The difference in decibels (dB) between the received signal strength and the ambient noise floor. Calculated as: SNR (dB) = RSSI (dBm) − Noise Floor (dBm).

The primary determinant of achievable modulation scheme and data rate. An SNR of 25 dB is the minimum for 256-QAM (high-throughput) operation. Always measure alongside RSSI.

CCI (Co-Channel Interference)

Interference that occurs when multiple APs and clients operate on the same channel and can detect each other's transmissions, causing medium contention under the CSMA/CA protocol.

The most common cause of high channel utilisation and latency in enterprise deployments. Mitigated by proper channel planning, power tuning, and ensuring adequate physical separation between APs on the same channel.

ACI (Adjacent Channel Interference)

Interference caused by RF energy from one channel bleeding into an adjacent overlapping channel, raising the noise floor and degrading SNR.

Caused by using overlapping channels in the 2.4 GHz band (anything other than 1, 6, 11). Avoided by strict adherence to non-overlapping channel assignments.

DFS (Dynamic Frequency Selection)

A regulatory mechanism that allows Wi-Fi devices to share the 5 GHz spectrum with radar systems by monitoring for radar signals and vacating the channel if detected.

Expands the available 5 GHz channel set, but requires APs to change channels upon radar detection, causing a brief connectivity disruption. Must be accounted for in deployments near airports, military installations, or weather radar sites.

CSMA/CA (Carrier-Sense Multiple Access with Collision Avoidance)

The medium access protocol used by Wi-Fi, in which devices listen to the RF channel before transmitting and defer if the channel is busy.

The fundamental reason Wi-Fi is a half-duplex, shared medium. CCI forces multiple APs and clients to contend for the same channel, which is why channel planning is critical to performance.

Sticky Client

A client device that remains associated with an AP delivering a weak signal despite being physically closer to a different AP with a stronger signal.

Caused by asymmetric link budgets (AP transmit power too high) or absence of 802.11k/v roaming protocols. Results in poor throughput, high latency, and degraded user experience.

LCMI (Least Capable, Most Important) Device

The device in a deployment with the weakest radio capabilities that is nonetheless critical to business operations.

Used as the design baseline for RF architecture. Designing to meet the LCMI device's requirements ensures all other devices perform adequately.

802.11k/v/r

A suite of IEEE 802.11 amendments: 802.11k (Radio Resource Measurement), 802.11v (BSS Transition Management), and 802.11r (Fast BSS Transition).

Together, these protocols enable intelligent, low-latency client roaming. 802.11k provides neighbour reports, 802.11v enables network-directed roaming, and 802.11r reduces re-authentication time to under 50 ms.

Ejemplos resueltos

A 300-room hotel is experiencing poor Wi-Fi performance in guest rooms despite having an AP in every corridor. Guests report dropped connections and slow speeds, particularly in rooms furthest from the corridor APs. The existing APs are configured at maximum transmit power (23 dBm) on auto channel assignment.

The root cause is a combination of Co-Channel Interference (CCI) from corridor APs hearing each other down the long hallways, signal attenuation through guest room doors and walls, and the sticky client problem caused by excessively high transmit power. The recommended solution is to transition to an in-room AP deployment model using wall-plate APs (e.g., Cisco Catalyst 9105AXW or Aruba AP-303H). Configure each AP with a transmit power of 10–12 dBm. Disable 2.4 GHz on every other AP in the corridor to reduce CCI. Standardise on 20 MHz channels in 5 GHz with a manual channel plan assigning channels 36, 40, 44, 48, 52, 56, 60, 64 in a repeating pattern. Enable 802.11k/v/r on all APs. Set minimum mandatory data rates to 12 Mbps in 2.4 GHz and 24 Mbps in 5 GHz. Validate with a post-deployment active site survey targeting -65 dBm RSSI and 25 dB SNR in all guest rooms.

Comentario del examinador: This approach shifts the design from coverage-centric to capacity-centric. Placing the AP inside the room eliminates the primary attenuation source (the room door and wall) for the client, dramatically improving SNR. Lowering transmit power to 10–12 dBm contains the RF cell within the room, reducing CCI from adjacent rooms. The combination of 802.11k/v/r and minimum data rate enforcement eliminates the sticky client problem. The result is a network that supports VoWiFi reliably and enables accurate location analytics for the hotel's guest engagement platform.

A large retail chain operating 50,000 sq ft stores wants to deploy Wi-Fi location analytics to track customer footfall and dwell time by department. Initial data from the existing network shows location accuracy of ±15 metres, which is insufficient for department-level analysis. The existing infrastructure has APs mounted at 6-metre intervals along the central spine of the store.

Location analytics based on RSSI trilateration require a minimum of three APs to hear a client device simultaneously, with each AP receiving a signal of -75 dBm or better. The current linear AP layout means that in the outer departments, clients are only within range of one or two APs, making accurate trilateration impossible. The solution requires a redesigned AP layout using a staggered grid pattern with APs at the perimeter and interior of each department zone, ensuring that any point on the floor is within -75 dBm range of at least three APs. Reduce AP transmit power to 10 dBm to tighten RF cells and improve the differential between AP readings (which is what drives location accuracy). Enable 802.11k/v to ensure devices don't stick to distant APs, which skews location data. Integrate the AP infrastructure with Purple's WiFi Analytics platform to process RSSI data into footfall heatmaps and dwell time reports by department.

Comentario del examinador: Location analytics impose a fundamentally different RF design requirement than connectivity. For connectivity, you need adequate RSSI at the client. For location, you need adequate RSSI at multiple APs simultaneously, with sufficient angular diversity to enable accurate trilateration. The staggered grid ensures diverse angles of reception. Lower transmit power increases the gradient of RSSI change as a client moves, improving position resolution. The integration with an analytics platform transforms raw RSSI data into actionable retail intelligence — enabling the chain to optimise store layout, staffing, and promotional placement based on real customer behaviour data.

Preguntas de práctica

Q1. You are designing a Wi-Fi network for a 40,000-seat stadium. The venue operator wants maximum throughput for concurrent video streaming and social media uploads during events. You are considering using 80 MHz channels in the 5 GHz band to maximise per-client throughput. Is this the recommended approach, and what channel plan would you implement instead?

Sugerencia: Consider the number of non-overlapping 80 MHz channels available in the 5 GHz band versus 20 MHz channels, and the impact of Co-Channel Interference in an open, high-density environment.

Ver respuesta modelo

No. Using 80 MHz channels in a stadium is strongly contraindicated. In the standard 5 GHz UNII-1/2/2e bands, there are only a handful of non-overlapping 80 MHz channels, meaning that with the AP density required for 40,000 concurrent users, severe CCI is inevitable. The correct approach is to use 20 MHz channels throughout, which provides up to 24 non-overlapping channels in 5 GHz (including DFS), maximising channel reuse. Directional sector antennas should be used to tightly control RF cell coverage, pointing down into seating sections rather than radiating omnidirectionally. AP density should be calculated based on a target of no more than 30–50 clients per AP radio, with transmit power tuned to match the coverage area of each sector.

Q2. A warehouse deployment uses handheld barcode scanners that frequently drop connections when operators move between aisles. The APs are configured at maximum transmit power (23 dBm) to ensure full coverage. The scanners run a legacy WMS application that requires sub-100ms latency. What is the likely cause and what steps would you take to resolve it?

Sugerencia: Consider the transmit power capabilities of a small handheld scanner versus an enterprise AP, and the implications for the link budget in both directions.

Ver respuesta modelo

The likely cause is the sticky client problem resulting from an asymmetric link budget. The APs are transmitting at 23 dBm, so the scanners hear them well across the entire warehouse and do not initiate a roam. However, the scanners' internal radios typically transmit at only 15–17 dBm, meaning the AP cannot reliably receive the scanner's transmissions when it is far away. The solution is to lower AP transmit power to 10–12 dBm to match the scanners' capabilities, ensuring that the coverage cells are appropriately sized and that scanners roam when they move out of range. Enable 802.11k/v/r to facilitate fast roaming. Set minimum mandatory data rates to 12 Mbps to force earlier roaming decisions. Validate with an active site survey using the actual scanner hardware to confirm -65 dBm RSSI and 25 dB SNR throughout all aisles.

Q3. During a site survey for a new hospital wing, you measure an RSSI of -58 dBm from the primary AP throughout the target area. However, the noise floor measured by a spectrum analyser is consistently -72 dBm due to legacy medical monitoring equipment operating in the 2.4 GHz band. The hospital requires reliable VoWiFi for clinical communications. Will this network support VoWiFi, and what actions would you recommend?

Sugerencia: Calculate the SNR and evaluate it against the minimum requirement for VoWiFi. Consider which frequency band is affected and what mitigation options are available.

Ver respuesta modelo

No, this network will not reliably support VoWiFi in its current state. The SNR is calculated as -58 dBm - (-72 dBm) = 14 dB. This falls below the minimum 20 dB SNR required for VoWiFi and well below the 25 dB target for high-quality voice. Despite the strong RSSI of -58 dBm, the elevated noise floor from the medical equipment degrades the link quality to an unacceptable level. Recommended actions: First, migrate VoWiFi traffic to the 5 GHz band, which is largely unaffected by the legacy 2.4 GHz medical equipment. Second, increase AP density in the affected areas to improve RSSI to -50 dBm or better, which would yield an SNR of 22 dB even with the elevated noise floor — marginally acceptable for VoWiFi. Third, engage the biomedical engineering team to assess whether the legacy equipment can be replaced or shielded. Fourth, implement QoS (WMM) with voice traffic prioritisation to protect VoWiFi traffic from competing with data traffic during periods of congestion.