Cisco Cisco Packet Data Interworking Function (PDIF)
HeNB-GW Service Configuration Procedures
Information Required to Configure the System as an HeNB-GW ▀
HeNB-GW Administration Guide, StarOS Release 18 ▄
47
Table 2. Required Information for Source Context Configuration
Required
Information
Description
Source context
name
name
An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is
recognized by the system.Generally it is identified as source context.
recognized by the system.Generally it is identified as source context.
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.
IP address and
subnet
subnet
IPv4 addresses assigned to the interface.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
Physical port
number
number
The physical port to which the interface will be bound. Ports are identified by the chassis slot number where
the line card resides followed by the number of the physical connector on the card. For example, port 17/1
identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
the line card resides followed by the number of the physical connector on the card. For example, port 17/1
identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
Gateway IP
address
address
Used when configuring static IP routes from the management interface(s) to a specific network.
Ingress and Egress GTP-U Services
Ingress GTP-U
service Name
service Name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the Ingress GTP-U service
can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled,
the Ingress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access
Service. It is also called access-side GTP-U service for the HeNB-GW ACCESS service.
can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled,
the Ingress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access
Service. It is also called access-side GTP-U service for the HeNB-GW ACCESS service.
Egress GTP-U
service Name
service Name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the Egress GTP-U service
can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled,
the Egress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access
Service. It is also called network-side GTP-U service for the HeNB-GW ACCESS service.
can be identified on the system. It is configured in Context Configuration Mode. When S1-U Relay is enabled,
the Egress GTP-U service configuration is critical as it has to be associated with the HeNB-GW Access
Service. It is also called network-side GTP-U service for the HeNB-GW ACCESS service.
GTP-U Tunnel
interface IP
address
interface IP
address
IP 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 HeNB using GTP-U tunnel.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
This address will be used for binding the GTP-U service (local bind address(es)) for sending/receiving GTP-U
packets from/to HeNB using GTP-U tunnel.
Multiple addresses and subnets are needed if multiple interfaces will be configured.
S1-AP Configuration (To/from Home-eNodeB)
HeNB-GW
access service
Name
access service
Name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Access
service can be identified on the system. It is configured in Context Configuration Mode. At a time, only one
HeNB-GW Access Service can be configured per system.
service can be identified on the system. It is configured in Context Configuration Mode. At a time, only one
HeNB-GW Access Service can be configured per system.
HeNB-GW
Network service
Name
Network service
Name
An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Network
service can be identified on the system. It is also configured in Context Configuration Mode. At a time, only
one HeNB-GW Network Service can be configured per system and therefore there is 1:1 mapping between
HeNB-GW Access and Network services.
service can be identified on the system. It is also configured in Context Configuration Mode. At a time, only
one HeNB-GW Network Service can be configured per system and therefore there is 1:1 mapping between
HeNB-GW Access and Network services.
Required Destination Context Configuration Information
The following table lists the information that is required to configure the destination context.