The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The system provides wireless carriers with a flexible solution for providing Security Gateway (SeGW) and Home-eNodeB Gateway (HeNB-GW) functionality for LTE Femtocell networks.
The system functioning as an HeNB-GW is capable of supporting the following types of subscriber sessions:
PS Session over S1AP: The subscriber is provided packet switch connection with different traffic class on PS session with P-GW in PS.
Network-initiated Sessions: Network-initiated session procedures include Paging, Dedicated Bearers, UE disconnections etc. from CN side on HeNB-GW for a specific subscriber session and in turn HeNB-GW initiates the required procedures with HeNBs and CNs.
Prior to connecting to the command line interface (CLI) and beginning the system's configuration, there are important things to understand about how the system supports these applications. This chapter provides terminology and background information that must be considered before attempting to configure the system.
This section defines some of the terms used in the chapters that follow.
A context is a logical grouping or mapping of configuration parameters that pertain to various physical ports, logical IP interfaces, and services. A context can be thought of as a virtual private network (VPN).
The system supports the configuration of multiple contexts. Each is configured and operates independently from the others. Once a context has been created, administrative users can then configure services, logical IP interfaces, subscribers, etc.for that context. Administrative users would then bind the logical interfaces to physical ports.
Contexts can also be assigned domain aliases, wherein if a subscriber's domain name matches one of the configured alias names for that context, then that context is used.
In HeNB-GW service implementation, the contexts can be classified into source or destination contexts. This is because GTP-U tunnels as well as HeNB-GW Access and Network services can be created over a single context.
The IP addresses as well as interfaces can also under the defined under the same context. These IP addresses are later used to bind with different services including GTP-U, MME and Interfaces including S1-MME for HeNB-GW Access service and Network service.
This section describes the logical interface supported on HeNB-GW.
Prior to allowing the flow of user data, the port must be associated with a virtual circuit or tunnel called a logical interface. A logical interface within the system is defined as the logical assignment of a virtual router instance that provides higher-layer protocol transport, such as Layer 3 IP addressing. Interfaces are configured as part of the VPN context and are independent from the physical port that will be used to bridge the virtual interfaces to the network.
Logical interfaces are assigned to IP addresses and are bound to a specific port during the configuration process. Logical interfaces are also associated with services through bindings. Services are bound to an IP address that is configured for a particular logical interface. When associated, the interface takes on the characteristics of the functions enabled by the service. For example, if an interface is bound to an HeNB-GW service, it will function as an S1-MME interface between the HeNB-GW/SeGW service and MME. Services are defined later in this section.
This is the interface used by the HeNB-GW to communicate with HeNBs on the same Femtocell Access Network. This interface serves as path for establishing and maintaining subscriber UE contexts.
Protocol stack architecture for the S1-MME interface has been described in the Protocol Architecture section of the Overview chapter of this guide.
The Stream Control Transmission Protocol (SCTP) guarantees the delivery of signalling messages between MME and eNodeB via HeNB-GW.
The HeNB-GW functions as a user-plane concentrator along with the control-plane concentration function. This allows the S-GW to view the cluster of femtocells as a single entity. The user-plane aggregation functionality provides support to GTP-U.
RADIUS/AAA is only applicable when SeGW is co-located with HeNB-GW.
In the roaming case, the 3GPP AAA Proxy can act as a stateful proxy between the SeGW and 3GPP AAA 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 DIAMETER protocol.
One or more RADIUS interfaces can be configured per system context.
One TR-069 interface can be configured per HeNB node.
A binding is an association between "elements" within the system. There are two types of bindings: static and dynamic.
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.
This section describes the services configured on HeNB-GW to support various functionality.
This service is bound to a local SCTP end-point address (IP address) to listen the incoming SCTP associations from HeNBs.
At least one logical eNodeB configuration is required to start the HeNB-GW Network service. Up to 8 logical eNodeBs can be configured per HeNB-GW Network service.
PLMN configuration is also required at the time of configuring Logical eNodeBs for the HeNB-GW Network service.
GTP-U service comes in picture specially when the S1-U Relay option is enabled. S1-U relay activation actually allows the data to flow through the GTP-U tunnel via HeNB-GW, otherwise it directly travels from HeNBs to S-GW.
S1-U Relay is disabled by default. Also when S1-U relay is enabled, both Access and Network GTP-U services need to be in STARTED state for the HeNB-GW access service to be STARTED.
Feedback