Managed Hotspot Client: How It Works
The Devicescape Easy Wi-Fi Managed Hotspot Client system is implemented with the combination of a small software agent running on mobile wireless devices, a web-based service that assists devices in connecting to Wi-Fi networks, and a website where device users manage their devices and networks. The agent can be downloaded onto a variety of device platforms or embedded by device manufacturers into their Wi-Fi enabled products. Both the web service and the consumer-facing website are hosted on a collection of highly-available Devicescape servers.
Initial Device Setup And Provisioning
Prior to first use at a hotspot, a device must have the Easy Wi-Fi agent installed and be registered with the Devicescape Server. Registration can be done either explicitly through the user creating a named account with a simple consumer-oriented website hosted by Devicescape, or anonymously by the device itself. During the registration process, the device is assigned a unique ID and is associated with a Devicescape account. The user either populates the account with the credentials for the providers they use, or the credentials can be automatically provided on behalf of the user (through backend integration between a service provider and Devicescape).
Once registered, initial provisioning of the device may be required. The device is setup to connect to all the SSIDs needed to automate network selection for the user's personal networks and those of any roaming and aggregation partnerships for providers in the user's account. Depending on the configuration of the client, the device may also be provisioned to connect to free and open hotspots.
Connecting to Public Wi-Fi Networks
The Hotspot Client and the Devicescape web service work together to automatically enable a device to login to public Wi-Fi networks. As illustrated in the figure below, whenever a device running the agent comes within range of a public Wi-Fi network, the device first detects the presence of the network, associates with the local access point, and gets an IP address. This initial set of actions triggers the Hotspot Client to see if the network is openly accessible without a login. If so, which may be the case in certain open hotspots, no further action is necessary. But if not the agent then sends a message to the Devicescape web service. The message contains the identity of the network and the unique identifier for the device.
The Devicescape web service receives this message and uses the contents to look up the access credentials (username & password) necessary to login to the public network. Since each public network service provider has a unique set of pages for their web login portals, the web service must also retrieve instructions on how to navigate these pages and submit the access credentials. The credentials to access the network would have been provided by the device owner (on the device UI, or using the Devicescape website) or can be provided by a service provider (through integration with the Devicescape Web Services API).
Once the access credentials and navigation instructions have been retrieved, this information is inserted into a return message sent back to the device. The device receives the message, extracts the access information, and uses this information to login to the public network. The Hotspot Client can navigate a wide variety of hotspot portal page schemes in order to locate the username and password entry fields and properly post the user’s credentials. The agent can also parse WISPr-compliant login portals.
Actual authentication of the device is done with the service provider’s standard Authentication, Authorization, and Accounting (AAA) infrastructure. Crucially, no browser is needed on the device to facilitate the login. Devices without browsers can now access all supported public networks. Additionally, devices which happen to have browsers will also enjoy easy and transparent access, without any need for user interaction.
Using a patent pending mechanism, the Hotspot Client is able to communicate with the Devicescape web service prior to authentication using standard networking protocols. Service providers do not need to re-configure their software or hardware, white-list the Devicescape servers or Easy Wi-Fi enabled devices, nor deploy any additional technology to enable this communication.
Learning More
Learn more about Easy Wi-Fi's Managed Hotspot Client in the detailed white paper.