EasyManua.ls Logo

Ruckus Wireless Virtual SmartZone - Configuring the Captive Portal; Configuring the GGSN;PGW Service

Ruckus Wireless Virtual SmartZone
470 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
When the user accesses the controller's WLAN through the captive portal registration, it interfaces
with the AAA server to register the user device's MAC address. Upon successful authentication, the
captive portal disassociates the user and re-associates it with the controller's WLAN using the registered
device MAC address. This functionality is supported as part of the MAC bypass feature with Ruckus
Wireless APs.
When a user reconnects to a WLAN, the Ruckus Wireless AP triggers MAC-based authentication.
Upon a successful authentication, the AAA server returns the associated identifiers of IMSI and MSISDN
along with the flag (Ruckus VSA - see: Captive Portal Workflows and VSA on page 401) indicating that
the TTG tunnel is established. The controller returns the TTG session type to the AP used by the data
plane to trigger the TTG establishment when DHCP DISCOVER is received.
Configuring the Captive Portal
This section describes the configuration procedures required to set up the captive portal.
Configuring the GGSN/PGW Service
The controller has 3GPP-defined Tunnel Terminating Gateway (TTG) functionality, which enables
it to act as a gateway between the UE (southbound) and the telecom core (northbound) to tunnel
traffic between the UE (User Equipment, such as mobile phones) and controller gateway
terminates the tunnel and then transfers the data over to GGSN (Gateway GPRS Serving Node)
implementing the Gn interface via GTPv1 (Release 6).
The Gn interface is used in controlling the signal between controller and GGSN as well as for
tunneling end user data payload within the backbone network between both the nodes.
GPRS Tunneling Protocol (GTP) transmits user data packets and signaling between controller
and GGSN. GTP encapsulates traffic and creates GTP tunnels, which act as virtual data channels
for transmission of packet data between controller and GGSN. A GTP tunnel is established
between controller and GGSN for a data session initiated from UE.
A GTP tunnel is identified by a pair of IP addresses and a pair of GTP Tunnel End Point Identifiers
(TEIDs), where one IP address and TEID is for the SGSN and the other is for GGSN. TEID is a
session identifier used by GTP protocol entities in SGSN and GGSN.
GTP separates signaling from payload. Traffic is sorted onto a control plane (GTP-C) for signaling
and a user plane (GTP-U) for user data. GTP-C is a tunnel control and management protocol
and is used to create, modify and delete tunnels. GTP-U is a tunneling mechanism that provides
a service for carrying user data packets.
Clicking Configuration > Services & Profiles on the main menu displays a sidebar on the left
side of the page, which includes GGSN Services. Figure 247: The GGSN/PGW Services
configuration page on page 388 shows the GGSN Service configuration page.
SmartCell Gateway 200/Virtual SmartZone High-Scale for Release 3.4.1 Administrator Guide
387
Overview of the Captive Portal
Configuring the Captive Portal

Table of Contents

Related product manuals