RUCKUS AFC System Architecture

The Geolocation Service Server acts as a centralized hub for processing location data from APs at a venue. APs, through their respective AP Controllers, supply the Geolocation Service Server with raw positional data, which consists of RF-based observations about their neighboring APs. From its overarching view of the entire Wi-Fi network, the Geolocation Service Server collectively analyzes the raw positional data from all APs to infer the geolocation coordinates of each AP, formatted appropriately for AFC inquiries.

Geolocation Flow

To conduct an AFC available spectrum inquiry, a RUCKUS AP first determines its geolocation coordinates (latitude, longitude, height above ground level, lateral and vertical uncertainty) with the aid of the RUCKUS Geolocation Service Server. It then formulates the AFC inquiry, incorporating its geolocation coordinates, and forwards this inquiry to the RUCKUS AFC Proxy Server via its Controller. The AFC Proxy Server subsequently relays the AP AFC inquiry to an external AFC service provider’s server for processing and waits for the response, which is then sent back to the AP. Refer to AFC Inquiry Flow for a visual representation of these messaging paths.

The APs communicate with the AFC Proxy Server and Geolocation Service Server through their respective AP controllers, not directly. RUCKUS has the following types of AP controllers:

• SmartZone 144 is a hardware-based AP controller.
• Virtual SmartZone is a virtualized AP controller (distributed as a virtual machine).

AFC Inquiry Flow