The Home eNodeB GW Test Case
In the E-UTRAN architecture with the Home eNodeB and Home eNodeB GW, the S1 interface is defined as the interface:
- Between the Home eNodeB GW and the Core Network,
- Between the Home eNodeB and the Home eNodeB GW,
- Between the Home eNodeB and the Core Network,
- Between the eNodeB and the Core Network.
There are two architectural variants for control plane in Home eNodeB access network.
Home eNodeB connected to MME directly
Home eNodeB connected to MME via dedicated Home eNodeB GW
Home eNodeB connected to MME directly:
Home eNodeB connected to MME via dedicated Home eNodeB GW:
Home eNodeB GW serves as a concentrator for the C-Plane, specifically the S1-MME interface. The S1-U interface from the Home eNodeB may be terminated at the Home eNodeB GW, or a direct logical U-Plane connection between Home eNodeB and S-GW may be used.
Currently the Home eNodeB GW Node test case only supports S1 Setup on the node level. Other node level messages are not supported. During S1 Setup from Home eNodeB to Home eNodeB GW, the TAIs(TAI = MCC + MNC + TAC) used by Home eNodeB must be supported by Home eNodeB GW. Otherwise there will be an S1 Setup failure.
Do not currently support ENB Configuration update towards the MME. Supported TACs by Home eNodeB GW can be pre-configured in two ways:
- Use the "Starting TAC" and "Number of TACs" fields or
- Manually input a single TAC or comma separated TACs.
The Home eNodeB GW Node test case supports most intra LTE procedures including:
- Attach, detach, idle mode release, service request, paging and S1/X2/TAU handovers, etc. however, INTER-TECH HANDOVERS ARE NOT CURRENTLY SUPPORTED.
For paging, Home eNodeB GW Node will forward the paging message to all Home eNodeBs which support the same TAI as contained in the message.
For S1 handover, make sure TAIs supported by Home eNodeB GW do not overlap with those supported by other macro or Home eNodeBs directly connected to the MME.
The GW ENB Id is not necessarily the first 20 bits of its served Home eNodeBs. The target Id search on the MME will first be based on ENB Id and then TAI.
For X2 handover, please note there will be NO GUARD AGAINST DIFFERENT MME NODES. The MME Nodal testcase will automatically update an X2 handover to become an S1 handover based on the ip address of the MME and Target MME suts. This approach is no longer applicable if the sut is a Home eNodeB GW. If you try to do an X2 handover with different MMEs, the behavior is unpredictable and it will be considered a user error.
Two S1ap sessions are reserved for each mobile subscriber on Home eNodeB GW. One of them is for handover purpose.
Reference Documents:
|
Measurements
Measurements collected on the following tabs.
S1 Control Node to MME - Prefix "EnbNode"
SCTP to MME - Prefix "LteEnb"
S1-AP to MME - Prefix "LteEnb"
S1 Control Node to Home eNodeB - Prefix "Mme"
SCTP to Home eNodeB - Prefix "LteMme"
S1-AP to Home eNodeB - Prefix "LteMme"
S1-AP Session - Prefix "S1apHenbgw"