Cisco Cisco Packet Data Gateway (PDG)
Understanding the Service Operation
▀ Terminology
▄ HNB-GW Administration Guide, StarOS Release 17
82
In the roaming case, the 3GPP AAA Proxy can act as a stateful proxy between the SeGW and 3GPP AAA
Server.
Server.
The AAA server is responsible for transfer of subscription and authentication data for
authenticating/authorizing user access and UE authentication. The SeGW communicates with the AAA on the
PLMN using RADIUS protocol.
authenticating/authorizing user access and UE authentication. The SeGW communicates with the AAA on the
PLMN using RADIUS protocol.
One or more RADIUS interfaces can be configured per system context.
TR-069: This interface is an application layer protocol which is used for remote configuration of terminal
devices, such as DSL modems, HNBs and STBs. TR-069 provides an auto configuration mechanism between
the HNB and a remote node in the service provider network termed the Auto Configuration Server. The
standard also uses a combination of security measures including IKEv2 (Internet Key Exchange v2) and IPsec
(IP Security) protocols to authenticate the operator and subscriber and then guarantee the privacy of the data
exchanged.
the HNB and a remote node in the service provider network termed the Auto Configuration Server. The
standard also uses a combination of security measures including IKEv2 (Internet Key Exchange v2) and IPsec
(IP Security) protocols to authenticate the operator and subscriber and then guarantee the privacy of the data
exchanged.
One TR-069 interface can be configured per HNB node.
DHCP: This is the interface used by the HNB-GW to communicate with a Dynamic Host Control Protocol
(DHCP) Server. The system can be configured to dynamically provide IP addresses for HNBs from the DHCP
server in HMS.
server in HMS.
One or more DHCP interface can be configured per system context.
Bindings
A binding is an association between “elements” within the system. There are two types of bindings: static and dynamic.
Static binding is accomplished through the configuration of the system. Static bindings are used to associate:
A specific logical interface (configured within a particular context) to a physical port. Once the interface is
bound to the physical port, traffic can flow through the context just as if it were any physically defined circuit.
Static bindings support any encapsulation method over any interface and port type.
Static bindings support any encapsulation method over any interface and port type.
A service to an IP address assigned to a logical interface within the same context. This allows the interface to
take on the characteristics (i.e., support the protocols) required by the service. For example, a GGSN service
bound to a logical interface will cause the logical interface to take on the characteristics of a Gn interface
within a GPRS/UMTS network.
bound to a logical interface will cause the logical interface to take on the characteristics of a Gn interface
within a GPRS/UMTS network.
Dynamic binding associates a subscriber to a specific egress context based on the configuration of their profile or
system parameters. This provides a higher degree of deployment flexibility as it allows a wireless carrier to support
multiple services and facilitates seamless connections to multiple networks.
system parameters. This provides a higher degree of deployment flexibility as it allows a wireless carrier to support
multiple services and facilitates seamless connections to multiple networks.
Services and Networks
This section describes the services configured on HNB-GW to support various functionality.
Services are configured within a context and enable certain functionality. The following services can be configured on
the system:
the system:
HNB-GW services: HNB-GW services are configured in Context configuration mode to support both mobile-
initiated and network-requested user contexts. The HNB-GW service must be bound to a logical interface
within the same context. Once bound, the interface takes on the characteristics of an IuH interface. Multiple
services can be bound to the same logical interface. Therefore, a single physical port can facilitate multiple IuH
interfaces.
within the same context. Once bound, the interface takes on the characteristics of an IuH interface. Multiple
services can be bound to the same logical interface. Therefore, a single physical port can facilitate multiple IuH
interfaces.