Product Description
Qualified Platforms
Licenses
SaMOG Services
CGW Service
CGW Features and Functions
DSCP Marking—CGW
GTPUv1 Support toward the P-GW—CGW
GTPv2-based S2a Interface—CGW
GRE Tunnel Support—CGW
P-GW Selection for LTE-to-WiFi Mobility—CGW
Proxy MIP Support—CGW
MRME Service
MRME Features and Functions
(MRME) EAP Authentication over RADIUS
(MRME) EAP Identity of Decorated NAI Formats
(MRME) EAP Identity of Emergency NAI Formats
(MRME) EAP Identity of Root NAI Formats
(MRME) Diameter STa Interface Support
(MRME) Operator Policy Support (IMSI-based Server Selection)
(MRME) P-GW Selection
Static Selection
| Step | Description |
|---|---|
|
1.
|
The SaMOG Gateway’s
MRME service receives the P-GW FQDN or P-GW IP address from the
AAA server as part of the MIP-Home-Agent-Host AVP in the Diameter
EAP Answer message.
|
|
2.
|
If it receives a P-GW
FQDN, and if the FQDN starts with “topon”, the
MRME service removes the first two labels of the received FQDN to
obtain the Canonical Node Name (ID) of the P-GW. The MRME service
uses this P-GW ID to send an S-NAPTR query to the DNS.
|
|
3.
|
The MRME service receives
the results of the query and selects the replacement string (P-GW FQDN)
matching the Service Parameters of “x-3gpp-pgw:x-s2a-gtp”.
|
|
4.
|
The MRME service then
performs a DNS A/AAAA query with selected replacement string (P-GW
FQDN). The DNS returns the IP address of the P-GW.
|
Dynamic Selection
| Step | Description |
|---|---|
|
1.
|
The MRME service receives
an APN name from the 3GPP AAA server.
|
|
2.
|
The MRME service constructs
the APN FQDN from the received APN name and uses this as the query
string to send to the DNS.
|
|
3.
|
The APN FQDN query
returns NAPTR Resource Records (RRs) with an “s” flag.
|
|
4.
|
Result(s) from this operation
are fed to a filter where only RRs with service-parameter "x-3gpp-pgw:x-s2a-gtp"
are considered by the MRME service.
|
|
5.
|
Each of the resulting
NAPTR RRs for that record set will be resolved further by performing DNS
SRV queries using the replacement string pointed to by the NAPTR
RRs.
|
|
6.
|
The MRME service receives
a list of P-GW FQDNs from the DNS. After all the SRV queries are
completed, the MRME service builds a candidate list of P-GW host
names.
|
|
7.
|
The resulting P-GW entries
are compared against the configured MRME service FQDN and the longest
suffix-matching entry is chosen. If there are more than one pair
of MRME service/P-GW combinations with the same degree
of label match, attributes from the RR may be used to break the
tie. The attributes include priority, weight, and order. Load-balancing
of P-GWs occur based on weight, as per the procedure defined in
RFC 2782.
|
|
8.
|
The selected P-GW FQDN
is further resolved using a DNS A/AAAA query to resolve
to the IPv4/IPv6 address of the S2a interface on the P-GW.
|
|
9.
|
The DNS returns the
IP address of the P-GW.
|
Topology/Weight-based Selection
(MRME) RADIUS Accounting Proxy
(MRME) RADIUS Authentication Server
(MRME) RADIUS Disconnection
(MRME) Reauthorization Support
(MRME) RADIUS Client Authentication
Network Deployment and Interfaces
Deployment Scenarios
Network Elements
eNodeB
MME
S-GW
P-GW
3GPP AAA Server
Logical Network Interfaces
| Interface | Description |
|---|---|
|
WLAN Interface
|
The interface to the
WLCs and WLAN UEs in the trusted non-3GPP IP access network has
not yet been defined in the 3GPP standards. The SaMOG Gateway uses
Remote Access Dial In User Service (RADIUS) messages generated by
the IP access network to provide session information such as the
IP addresses of the WLAN UEs to the EPC network via the WLCs and
to set up the access side associations.
|
|
STa Interface
|
The interface from the
SaMOG Gateway’s MRME service to the 3GPP AAA server, the STa
interface is used for WLAN UE authentication. It supports the transport
of mobility parameters, tunnel authentication, and authorization
data. The EAP-AKA, EAP-SIM, and EAP-AKA’ methods are used
for authenticating the WLAN UEs over this interface.
|
|
S2a Interface
|
The interface from the
SaMOG Gateway’s CGW service to the P-GW,
the S2a interface runs the GTPv2
protocol to establish WLAN UE sessions with the P-GW.
|
Transport Combinations
| IP Address Allocated by the P-GW for the WLAN UEs | RADIUS Authentication and Accounting (between the WLCs and the SaMOG Gateway) | PMIPv6 Interface (between the WLCs and the SaMOG Gateway) | EoGRE Interface (between the WLCs and the SaMOG Gateway) | Is this Combination Supported for Deployment? |
|---|---|---|---|---|
|
IPv4
|
IPv4
|
IPv4
|
IPv4
|
Yes
|
Features and Functionality - Base Software
Bulk Statistics
IMPORTANT:
Ethernet over GRE (EoGRE)
IMPORTANT:
SaMOG as a Default Gateway
How the SaMOG Gateway Works
SaMOG Gateway Session Establishment
| Step | Description |
|---|---|
|
1.
|
An association between
the UE and WLC is established.
|
|
2.
|
The initial attach
procedure starts with the authenticator sending an EAP Request/Identity message
toward the supplicant.
|
|
3.
|
The UE responds to
the EAP Request/Identity message with an EAP Response/Identity message,
which contains the user credentials.
|
|
4.
|
These credentials are
enclosed in a RADIUS Access Request message by the WLC and sent
to the SaMOG Gateway’s MRME service.
|
|
5.
|
The MRME service, functioning
as an AAA proxy, sends a Diameter EAP Request (DER) message to the
HSS over the STa interface.
|
|
6.
|
The HSS returns a Diameter
EAP Answer (DEA) message, which contains an EAP Challenge.
|
|
7.
|
The MRME service converts
the message to RADIUS and sends a RADIUS Access Challenge message
to the WLC.
|
|
8.
|
The WLC sends an EAP
Request/Challenge message to the UE.
|
|
9.
|
The UE returns an EAP
Response/Challenge message to the WLC.
|
|
10.
|
The WLC sends a RADIUS
Access Request message to the MRME service.
|
|
11.
|
The MRME service,
functioning as an AAA proxy, sends a Diameter EAP Request (DER) message
to the HSS over the STa interface.
|
|
12.
|
The HSS returns a
Diameter EAP Answer (DEA) message in response.
|
|
13.
|
The MRME sends a RADIUS
Access Accept message to the WLC. The UE is now fully authenticated
and the SaMOG Gateway leg of the call is connected.
|
|
14.
|
The MRME initiates
a call creation trigger to the CGW service.
|
|
15.
|
The CGW service receives
a Proxy Binding Update (PBU) message from the WLC as part of the
user plane set-up.
|
|
16.
|
The CGW service sends
a Create Session Request message to the P-GW.
|
|
17.
|
The P-GW returns a
Create Session Response message to the CGW service.
|
|
18.
|
The CGW service sends
a Proxy Binding Acknowledgement message to the WLC with the status
of SUCCESS. The message carries the assigned IP address of the UE.
|
|
19. through 22.
|
The WLC conveys the
IP address of the UE as a part of the DHCP messaging between the WLC
and the UE.
|
P-GW Initiated Session Disconnection
| Step | Description |
|---|---|
|
1.
|
The P-GW sends a Delete
Bearer Request message to the SaMOG Gateway’s CGW service
as part of session deletion.
|
|
2.
|
The CGW service returns
a Delete Bearer Response message to the P-GW and marks the session
for deletion.
|
|
3.
|
The CGW service sends
a Binding Revocation Indication message to the WLC.
|
|
4.
|
The WLC sends a Binding
Revocation Acknowledgement message to the CGW service with applicable
cause codes. The CGW service marks the session as deleted upon receiving
the message.
|
|
5.
|
The CGW service signals
the MRME service to delete the call.
|
|
6.
|
The MRME service sends
a RADIUS Disconnect message to the WLC to initiate RADIUS Accounting
StopRelease.
|
|
7.
|
The WLC sends a RADIUS
Accounting Stop message to the MRME service.
|
|
8.
|
The MRME service, functioning
as an AAA proxy, sends a Session Termination Request (STR) message
over the STa interface to the HSS.
|
|
9.
|
The HSS acknowledges
the session termination by returning a Session Termination Answer (STA)
to the MRME service.
|
|
10.
|
The MRME service sends
a RADIUS Accounting Stop Response message to the WLC and clears
the call at the SaMOG Gateway.
|
WLC Initiated Session Disconnection
| Step | Description |
|---|---|
|
1.
|
For binding de-registration,
the WLC send a Proxy-MIP Binding Update (PBU) message to the SaMOG
Gateway’s CGW service with the lifetime value set to 0.
|
|
2.
|
The CGW service sends
a Proxy-MIP Binding Acknowledgement (PBA) message to the WLC.
|
|
3.
|
The CGW service triggers
a session deletion on the P-GW by sending a Delete Session Request
message over the S2a interface.
|
|
4.
|
The P-GW acknowledges the session deletion by sending a Delete Session Response message to the CGW service. |
|
5.
|
The CGW service triggers
a call deletion by the MRME service, which handles the subsequent call
clearing.
|
|
6.
|
The WLC sends a RADIUS
Accounting Stop message to the MRME service.
|
|
7.
|
The MRME service, functioning
as an AAA proxy, sends a Session Termination Request (STR) message
over the STa interface to the HSS.
|
|
8.
|
The HSS acknowledges
the session termination by returning a Session Termination Answer (STA)
to the MRME service.
|
|
9.
|
The MRME service sends
a RADIUS Accounting Stop Response message to the WLC and clears
the call at the SaMOG Gateway.
|
AAA Server Initiated Session Disconnection
| Step | Description |
|---|---|
|
1.
|
The AAA server sends
an Abort Session Request message to the SaMOG Gateway’s
MRME service over the STa interface.
|
|
2.
|
The MRME service returns
an Abort Session Response message to the HSS and begins call deletion,
|
|
3.
|
The MRME service sends
a RADIUS Disconnect Request message to the WLC to initiate RADIUS
Accounting Stop/Release.
|
|
4.
|
The WLC sends a RADIUS
Accounting Stop message to the MRME service.
|
|
5.
|
The MRME service sends
a RADIUS Accounting Stop Response message to the WLC and clears
the call at the SaMOG Gateway.
|
|
6.
|
The MRME service triggers
call deletion by the CGW service.
|
|
7.
|
The CGW service triggers
a session deletion on the P-GW by sending a Delete Session Request
message over the S2a interface.
|
|
8.
|
The P-GW acknowledges
the session deletion by sending a Delete Session Response message to
the CGW service.
|
|
9.
|
The CGW service sends
a Binding Revocation Indication message to the WLC.
|
|
10.
|
The WLC sends a Binding
Revocation Acknowledgement message to the CGW service with applicable
cause codes. The CGW service marks the session as deleted upon receiving
the message.
|
SaMOG Gateway Data Flow
| Step | Description |
|---|---|
|
1.
|
The UE sends the uplink
(UL) data to the WLC.
|
|
2.
|
The WLC sends the user
data to the SaMOG Gateway’s CGW service over the established
bi-directional GRE tunnel.
|
|
3.
|
The CGW service sends
the user data over a GTPU tunnel to the P-GW.
|
|
4.
|
The P-GW maps the downlink
(DL) data on the GTPU tunnel to a GRE tunnel to the WLC.
|
|
5.
|
The CGW service sends
the user data to the WLC over the GRE tunnel.
|
|
6.
|
The WLC sends the user
data to the UE.
|
Supported Standards
3GPP References
IETF References