Services are configured
within a context and enable certain functionality. The following
services can be configured on 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.
-
Radio Network PLMN:
The Radio Network PLMN is configured in HNB-GW service to associate
PLMNs with HNB-GW.
In StarOS 12.1 and
earlier, the PLMN specific configuration e.g. RNC id and association
of CS or PS network shall be configured under the HNB-Radio Network
PLMN configuration mode.
In StarOS Release
14.0 and later, the PLMN specific configuration e.g. RNC id and association
of CS or PS network shall be configured under the HNB-CS and HNB-PS configuration
mode respectively.
-
CS Network: CS
Network is a context independent configuration to define circuit switched
networks. This circuit switched network configuration provides parameters
for one or more MSCs where CS-domain Iu-connections shall be routed.
In a typical deployment HNB-GW is connected to only one MSC.
In StarOS 12.1 and
earlier, the CS network configured at the system level need to be associated
with a Radio Network PLMN configured within HNB-GW service with
desired granularity; PLMN level or location-area in that PLMN.
In StarOS Release
14.0 and later, the CS network configured at the system level need
to be associated with a SCCP Network configured at Gloal Configuration
mode.
-
PS Network: PS
Network is a context independent configuration to define packet switched
networks. This packet switched network configuration provides parameters
for one or more SGSN where PS-domain Iu-connections shall be routed.
In a typical deployment HNB-GW is connected to only one SGSN.
In StarOS Release
12.1 and earlier, the PS network configured at the system level
need to be associated with a Radio Network PLMN configured within
HNB-GW service with desired granularity.
In StarOS Release
14.0 and later, the PS network configured at the system level need
to be associated with a SCCP Network configured at Gloal Configuration
mode.
-
GTP-U services:
GTP-U services are configured in Context configuration mode in pair
of two services; one for GTP-U tunnel support towards HNB on IuH
interface and another for GTP-U tunnel support towards the core
network on IuPS interface to communicate with SGSN respectively.
The system supports
multiple GTP-U interface connections over this service. Although
this service can be configured in any independent context, but for
IuH interface it must be configured in the same context as HNB-GW;
i.e. source context.
Following figure illustrates
the relationship between services, interfaces, and contexts within the
HNB-GW system for HNB access 3G UMTS networks.
Figure 1. Service,
Interface, and Context Relationship Within the System
The source context
used to service a subscriber session is the same as the context
in which the HNB-GW service is configured. Each HNB-GW service is
bound to an IP address in a source context. The HNBs select which
IP address to use, typically by using DNS. Once a UE has established
a bearer context with an HNB-GW, the HNBs continue to use the same
context as the subscriber anchored to that HNB-GW.
The destination contexts
used to service a subscriber session to connect with CN.
The system determines
the configuration used in destination context based on the parameter contained
within the information received from HNB and also the configuration
in HNB-GW service. The AAA context or AAA configuration in source
context uses that context for subscriber authentication.