Introduction
Product Overview
IMPORTANT:
Platform Requirements
License Requirements
Network Deployments and Network Interfaces
Network Deployments
IMPORTANT:
IMPORTANT:
Network Interfaces
Feature Description
RADIUS AAA Support
Control and Data Interfaces
IMPORTANT:
IP Address Allocation
Network Layer Service Access Point Identifier Allocation
IMPORTANT:
Differentiated Services Code Point Marking
| GPRS QoS Class Identifier Value | UMTS QoS Parameters | ||||
|---|---|---|---|---|---|
| Traffic Class | THP | Signalling Indication | Source Statistics Descriptor | ||
|
1
|
Conversational
|
N/A
|
N/A
|
speech
|
|
|
2
|
Conversational
|
N/A
|
N/A
|
unknown
|
|
|
3
|
Streaming
|
N/A
|
N/A
|
speech
|
|
|
4
|
Streaming
|
N/A
|
N/A
|
unknown
|
|
|
5
|
Interactive
|
1
|
Yes
|
N/A
|
|
|
6
|
Interactive
|
1
|
No
|
N/A
|
|
|
7
|
Interactive
|
2
|
No
|
N/A
|
|
|
8
|
Interactive
|
3
|
No
|
N/A
|
|
|
9
|
Background
|
N/A
|
N/A
|
N/A
|
|
Access Point Name Selection
GGSN Selection
GGSN Failover Case
IMPORTANT:
Network Address Translation and Application Level Gateway Support
IMPORTANT:
Virtual APN Support
IMPORTANT:
UE Identity and Location Information Support
UE Identity Information Support
IMPORTANT:
IMPORTANT:
UE Location Information Support
IMPORTANT:
Bulk Statistics Support
IMPORTANT:
Threshold Crossing Alerts Support
IMPORTANT:
Congestion Control Support
IMPORTANT:
IMPORTANT:
Redundancy Support
IMPORTANT:
How it Works
Session Setup
| Step | Description |
|---|---|
|
1
|
The UE attaches to
the WLAN network using WLAN attach procedure by selecting SSID advertised
for 3G access.
|
|
2
|
The UE provides its
EAP-identity for authentication in 802.1x message.
|
|
3
|
The WLC forwards the
UE EAP-identity to the Wi-Fi AAA server in RADIUS
Access-Request message by encapsulating the EAP message
in it. This message also contains the WLAN UE’s
MAC Address and the WLAN Radio Network Identifier.
|
|
4
|
The Wi-Fi
AAA server proxies the Access-Request message to the 3GPP
AAA server.
|
|
5
|
The 3GPP AAA server
identifies the subscriber as a candidate for authentication with EAP-SIM/AKA
based on the received identity. It interacts with the HLR
to fetch the GSM/UMTS authentication vectors for EAP-SIM/AKA
authentication and other 3GPP-specific attributes like
IMSI, MSISDN, APN, and Charging Characteristics
from the subscriber’s profile.
|
|
6
|
The 3GPP AAA server
sends Access-Challenge-Request to the UE as part
of EAP-SIM/AKA authentication procedure to the
Wi-Fi AAA Proxy server.
|
|
7
|
The Wi-Fi
AAA proxies the Access-Challenge message back to the WLC.
|
|
8
|
The WLC sends the EAP-Challenge
message to the UE over 802.1x.
|
|
9
|
Similar EAP message
exchanges happen between the UE and 3GPP AAA as part of the authentication
procedure.
|
|
10
|
After successful authentication, the
3GPP AAA sends an Access-Accept message with 3GPP-specific
attributes like IMSI, MSISDN, Charging-Characteristics, APN, and
others.
|
|
11
|
The Wi-Fi
AAA server caches these 3GPP attributes in Access-Accept
message, which will be later used to enrich the RADIUS
accounting messages generated from WLC and sent to the eWAG.
|
|
12
|
The Wi-Fi
AAA proxies the Access-Accept message to the WLC.
|
|
13
|
The WLC sends the EAP-Success
message over 802.1x to the UE and completes the authentication
procedure.
|
|
14
|
The UE gets an IP address
allocated from the Wi-Fi domain using the DHCP exchanges
as per the normal WLAN procedure of allocating IP address.
Note that the DHCP
server allocating this IP address to the UE is part of the Wi-Fi
domain, and the IP address thus allocated is hereon referred
to as the Wi-Fi IP address.
|
|
15
|
After the IP address
is allocated to the attaching UE, the WLC initiates RADIUS accounting
for the UE session by sending a RADIUS Accounting-Start
message to the Wi-Fi AAA.
|
|
16
|
The Wi-Fi
AAA sends the Accounting-Response message back to the WLC
as acknowledgement.
|
|
17
|
The Wi-Fi
AAA server enriches the Accounting-Start message received
with 3GPP-specific attributes as mentioned in Step 11. This
modification of Accounting-Start message later helps the
eWAG in creating the PDP context with the GGSN, which requires
3G attributes like IMSI, MSISDN, APN, and
others.
|
|
18
|
The Wi-Fi
AAA server sends the Accounting-Start message enriched
with the 3GPP-specific attributes to the eWAG.
|
|
19
|
The eWAG creates a
new session based on this Accounting-Start message. It
assumes the default APN configured under eWAG service if it is not
available in the Accounting-Start message. It
also assigns a default QoS value for the eWAG session if not available
in the Accounting-Start message.
|
|
20
|
The eWAG identifies
the GGSN it needs to connect with using the same 3G procedure of identifying
GGSN from SGSN(/TTG) using DNS resolution. The
eWAG then sends the Create PDP Context Request message to the GGSN
to create the GTP tunnel.
|
|
21
|
The GGSN processes
the Create PDP Context Request and allocates the MPC IP address
in the Create PDP Context Response message. It also negotiates
the QoS to be used for this subscriber session and sends the same
in Create PDP Context Response message.
|
|
22
|
The eWAG processes
the Create PDP Context Response message, and creates the
binding between the Wi-Fi IP address and the MPC IP address
in the eWAG session.
|
|
23
|
The eWAG sends an Accounting-Response
message to the Wi-Fi AAA server to acknowledge the Accounting-Start
message.
|
|
24
|
The UE initiates data
transfer to the destination in APN network with Source IP set to
its Wi-Fi IP address. This packet gets routed
to the eWAG from the WLAN network.
|
|
25
|
The eWAG performs NAT
on this data packet (Layer 3 to Layer 7), from
Wi-Fi IP address to MPC IP address.
|
|
26
|
The eWAG sends the
NATd IP packet encapsulated over the GTP-U tunnel created
with the GGSN.
|
|
27
|
The GGSN decapsulates
the IP packet received over the GTP-U tunnel and sends
it to the destination APN network. Note that this IP packet
contains the source IP address set to the MPC IP address.
|
|
28
|
The data packet received
in the downlink direction from the APN network is processed by the
GGSN. This downlink packet contains the destination IP
address set to the MPC IP address.
|
|
29
|
The GGSN encapsulates
the IP packet over the GTP-U tunnel and sends it downlink
to the eWAG.
|
|
30
|
The eWAG performs reverse-NAT
on the downlink IP packet (received over the GTP-U tunnel
from the GGSN) and converts all MPC IP addresses to Wi-Fi
IP addresses from Layer 3 to Layer 7.
|
|
31
|
The eWAG sends the
plain IP packet downlink to the UE.
|
Session Setup using Accounting-Interim
| Step | Description |
|---|---|
|
1
|
The UE attaches to
the WLAN network using WLAN technology attach procedure by selecting
SSID advertised for 3G access.
|
|
2
|
The UE provides its
EAP-identity for authentication in 802.1x message.
|
|
3
|
The WLC forwards the
UE EAP-identity to the Wi-Fi AAA server through
RADIUS Access-Request message by encapsulating the EAP
message in it. This message also contains the WLAN UE MAC
Address and the WLAN Radio Network Identifier.
|
|
4
|
The Wi-Fi
AAA server proxies the Access-Request message to the 3GPP
AAA server.
|
|
5
|
The 3GPP AAA server
identifies the subscriber as a candidate for authentication with EAP-SIM/AKA
based on received identity. It interacts with the HLR to
fetch the GSM/UMTS authentication vectors for EAP-SIM/AKA
authentication and other 3GPP-specific attributes from
the subscriber profile, including IMSI, MSISDN, APN, and
Charging Characteristics.
|
|
6
|
The 3GPP AAA sends
the Access-Challenge-Request to the UE as part
of EAP-SIM/AKA authentication procedure to the
Wi-Fi AAA proxy server.
|
|
7
|
The Wi-Fi
AAA proxies the Access-Challenge message back to the WLC.
|
|
8
|
The WLC sends the EAP-Challenge
message to the UE over 802.1x.
|
|
9
|
Similar EAP message
exchanges happen between the UE and 3GPP AAA as part of authentication
procedure.
|
|
10
|
After successful authentication, the
3GPP AAA sends an Access-Accept message with 3GPP-specific
attributes including IMSI, MSISDN, Charging-Characterstics, APN, etc.
|
|
11
|
The Wi-Fi
AAA server caches the 3GPP attributes in the Access-Accept
message, which will be later used to enrich the RADIUS
accounting messages generated from WLC and sent to the eWAG.
|
|
12
|
The Wi-Fi
AAA proxies the Access-Accept message to the WLC.
|
|
13
|
The WLC sends the EAP-Success
message over 802.1x to the UE and completes the authentication
procedure.
|
|
14
|
The UE gets an IP address
allocated from the Wi-Fi domain using DHCP exchanges as
per the normal WLAN procedure of allocating the IP address.
Note that the DHCP
server allocating this IP address to the UE is part of Wi-Fi
domain and the IP address thus allocated is hereon referred to as
the Wi-Fi IP address.
|
|
15
|
After the IP address
is allocated to the attaching UE, the WLC initiates RADIUS accounting
for the UE session by sending RADIUS Accounting-Start message
to the Wi-Fi AAA.
|
|
16
|
The Wi-Fi
AAA server sends back the Accounting-Response to the WLC
as acknowledgement.
|
|
17
|
The Wi-Fi
AAA server sends the Accounting-Interim message enriched
with 3GPP-specific attributes to the eWAG. And, the
eWAG creates the session based on this message and establishes GTP
tunnel with the GGSN.
|
|
18
|
The eWAG creates new
session based on this Accounting-Interim message. It
assumes the default APN configured in the eWAG service if it is
not available in the Accounting-Interim message. It
also assigns a default QoS value for the eWAG session if not available
in the Accounting-Interim message.
|
|
19
|
The eWAG identifies
the GGSN to connect to using the same 3G procedure of identifying GGSN
from SGSN/TTG using DNS resolution. The eWAG then
sends the Create PDP Context Request message to the GGSN to create
the GTP tunnel.
|
|
20
|
The GGSN processes
the Create PDP Context Request and allocates the MPC IP address
in the Create PDP Context Response message. It also negotiates
the QoS to be used for the subscriber session and sends the same
in the Create PDP Context Response message.
|
|
21
|
The eWAG processes
the Create PDP Context Response message and creates the binding between
the Wi-Fi IP address and the MPC IP address in the eWAG
session.
|
|
22
|
The eWAG sends the
Accounting-Response message to the Wi-Fi AAA server
to acknowledge the Accounting-Interim message.
|
|
23
|
The UE initiates data
transfer to the destination in APN network with Source IP set to
its Wi-Fi IP address. This packet gets routed
to the eWAG from the WLAN network.
|
|
24
|
The eWAG performs NAT
on this data packet (Layer 3 to Layer 7), from
Wi-Fi IP address to MPC-IP address.
|
|
25
|
The eWAG sends the
NATd IP packet encapsulated over the GTP-U tunnel created
with the GGSN.
|
|
26
|
The GGSN decapsulates
the IP packet received over the GTP-U tunnel, and
sends it to the destination APN network. Note that this
IP packet contains the source IP address set to the MPC IP address.
|
|
27
|
The data packet received
in the downlink direction from the APN network is processed by the
GGSN. This downlink packet contains the destination IP
address set to the MPC IP address.
|
|
28
|
The GGSN encapsulates
the IP packet over the GTP-U tunnel and sends it downlink
to the eWAG.
|
|
29
|
The eWAG performs reverse-NAT
on the downlink IP packet received over the GTP-U tunnel
from the GGSN, and converts all MPC IP addresses to Wi-Fi
IP addresses from Layer 3 to Layer 7.
|
|
30
|
The eWAG sends the
plain IP packet downlink to the UE.
|
Session Replacement
IMPORTANT:
IMPORTANT:
Session Setup Failure
Mandatory AVP Missing / No Resource
Session Update
GGSN-initiated Update PDP Context
IMPORTANT:
IMPORTANT:
Dependencies and Limitations
eWAG + GGSN Combo Deployments
Virtual APN Configuration in eWAG + GGSN Combo Deployments
IMPORTANT:
eWAG + TTG Combo Deployments
SGTP Service Configuration in eWAG + TTG Combo Deployments
eWAG + TTG + GGSN Combo Deployments
IMPORTANT:
Mobility Setup Considerations
3G-eWAG-TTG Mobility using Proxy-MIP at GGSN