Cisco Cisco Packet Data Gateway (PDG)
HNB-GW Service Configuration Procedures
Information Required to Configure the System as an HNB-GW ▀
HNB-GW Administration Guide, StarOS Release 16 ▄
87
Required Information
Description
Public Land Mobile
Network (PLMN)
Identifiers
Network (PLMN)
Identifiers
Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999.
Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999.
Radio Network
Controller (RNC)
identifier
Controller (RNC)
identifier
Specify the RNC id which shall be provided to HNB during HNB-REGISTRATION procedure.
Depending upon the requirement the RNC-ID can be provided with the desired granularity in HNB-PS
networks or HNB-CS Network Configuration.
Depending upon the requirement the RNC-ID can be provided with the desired granularity in HNB-PS
networks or HNB-CS Network Configuration.
GTP-U service name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be
associated with HNB-GW system in HNB-GW service for GTP-U tunnel towards HNB access network
(HNB). It is pre-configured in Context configuration mode.
associated with HNB-GW system in HNB-GW service for GTP-U tunnel towards HNB access network
(HNB). It is pre-configured in Context configuration mode.
Multiple names are needed if multiple GTP-U services is used.
Important:
One GTP-U service can be associated with HNB-GW service instance to
provide GTP-U tunnel over Iuh interface towards HNB access network (HNB) and another
GTP-U service needs to be associated with PS network instance for GTP-U tunnel over IuPS
interface towards PS core network to GSNs.
GTP-U service needs to be associated with PS network instance for GTP-U tunnel over IuPS
interface towards PS core network to GSNs.
GTP-U Tunnel Innerves Configuration
GTP-U service name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service can be
associated with HNB-GW system for GTP-U tunnel towards HNB access network (HNB). Various control
parameters can be configured for GTP-U packet transmission.
associated with HNB-GW system for GTP-U tunnel towards HNB access network (HNB). Various control
parameters can be configured for GTP-U packet transmission.
Multiple names are needed if multiple GTP services is used.
GTP-U Tunnel
interface IP address
interface IP address
IPv4 addresses assigned to the interface as GTP-U bond address.
This address will be used for binding the GTP-U service (local bind address(es)) for sending/receiving
GTP-U packets from/to HNB using GTP-U tunnel.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
GTP-U packets from/to HNB using GTP-U tunnel.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
GTP-U Tunnel
interface Port
interface Port
The physical port to which the Iuh interface will be bound. The local GTP-U port used to communicate
with the HNB over GTP-U tunnel interface.
with the HNB over GTP-U tunnel interface.
Required Destination Context Configuration Information
The following table lists the information that is required to configure the destination context.
Table 4. Required Information for Destination Context Configuration
Required
Information
Information
Description
Destination
context name
context name
An identification string from 1 to 79 characters (alpha and/or numeric) by which the destination context will
be recognized by the system.
be recognized by the system.
Interface name
An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is
recognized by the system.
recognized by the system.
Multiple names are needed if multiple interfaces will be configured.