User Node


The User Node routes bearer plane traffic and can be used in 3GPP test cases when separation of control and user traffic is required or desired.

NOTE: Use the Next Hop IP Address in GGSN Node test case to override the static route and out bound port.

AMF Nodal / SMF Nodal / UPF Nodal (gNB User Node, Target gNB User Node, 4G gNB User Node)

MME Nodal when Dual Connectivity on the NAS Tab is selected. N3IWF Node Emulator test case when N3 to UPF is enabled named N3 to UPF User node.

Use Alternate User Address

Available on gNB User Node and Target gNB User Node tabs and selected by default. The 4G gNB user Node is available when Dual Connectivity is enabled on S1-MME NAS tab on AMF Nodal.

Tcl Parameter:  

GnbUserAddrEn GnbUserAddr EpcGnbUserAddr MobGnbUserAddrEn MobGnbUserAddr

 

When you select Use Alternate User Address, the Control and User Nodes use different IP Addresses and interface.

When you clear Use Alternate User Address (not selected):

  • The gNB User Node is not available for input.
  • The Control and User Nodes use the same IP Address (a single IP Address) and interface. That is, a single IPSec tunnel is created/used for control and user traffic encapsulation.

When a single IP Address is used both the Control and User traffic will be encapsulated into a single measurement tab eNodeB Node. When you Use Alternate IP Address two measurement tabs, gNodeB Node and gNodeB User Node tabs, report the Control and User traffic separately.

Cell Access Mode

CSG ID

MCC

MNC

Available on gNodeB User Node in MME Nodal when Dual Connectivity on the NAS Tab is selected.

Select Cell Access Mode. Options: Hybrid , Closed, and Open. Support for CSG (Closed subscriber Group) calls. if enabled by selecting either a closed or Hybrid Subscriber Group, then you must send the CSG Id.

Enter the CSG Id: Numerical field- Range from 0 (default) to 134217727. The CSG ID field is enabled when Cell Access Mode is not equal to Open.

Enter the MCC (Mobile Country Code - up to 3 digits) and MNC (Mobile Network Code - enter 2 or 3 digits)

Tcl Parameter:  

GnbCellAccessMode GnbCsgId GnbMcc GnbMnc

Num gNBs per AMF

Enable Target gNB

NR Cell ID

Tracking Area Code

Available on gNodeB User Node in SMF Nodal. NR Cell ID and Tracking Area Code are available in Target gNB User Node in SMF Nodal when Test Activity = Intra-AMF Mobility.

Enter Num gNBs per AMF.

Range : 1 to 1000

Default : 1

Select to Enable Target gNB. Always enabled for Handoff tests such as Intra-AMF. Not available for Capacity / Session Loading tests. Available for selection in Command Mode / Sequencer tests.

In Command Mode/Sequencer/ the Xn Handover / N2 handover ODC is available when either a) "Enable Target gNB" is checked or b) "Num gNBs per AMF" is > 1.
The range of Target Nodes for Register and Xn Handover / N2 Handover is calculated as follows:

 If "Enable Target gNB" is not checked, the upper limit is "AMF SBI Node/# of Nodes" * "gNB User Node/Num gNBs per AMF"
If "Enable Target gNB" is checked, the upper limit is "AMF SBI Node/# of Nodes" * "gNB User Node/Num gNBs per AMF" * 2.

Enter NR Cell ID.

  • "NR Cell ID" parameter is defined per NR Cell Identity (TS38.413 - 9.3.1.7). The leftmost bits of the NR Cell Identity IE correspond to the gNB ID. Landslide treats leftmost 32bit of the value of “NR Cell ID” as gNB ID (TS38.413 - 9.3.1.6) and the lower 4 bits as the Cell Identity (Cell ID).

  • "NR Cell ID" parameter supports a maximum of 687,194,476,735.

Range: 0 to 68719476735

Enter Tracking Area Code.

Range: 0 to 16777215, with optional auto-increment pattern #(nnnnnnnn) or #(nnnnnnnn C/I)

Default : 0

Tcl Parameter:  

NumGnbPerAmf GnbUserNodeTargetEn GnbNrCellId GnbTac
MobGnbNrCellId MobGnbTac    

NOTE: In release 19.4, the "User Location Information" panel on SMF Nodal's Namf tab has being removed. The "Tracking Area Code" and "NR Cell ID" values have been moved to the Network Devices/gNB User Node tab and receive a Tcl variable name change.

 

 

Secondary gNB User Node

Available in MME Nodal when Dual Connectivity and Enable Secondary gNB User Node are enabled on the NAS Tab. 

Available in AMF Nodal when Test Activity = Dual Connectivity or when Redundant gNB User Node (see below) is enabled (for Support URLLC). 

Tcl Parameter:  

SecGnbUserAddr
Redundant gNB User Node 

This checkbox is enabled only when the "Support URLLC" on AMF Nodal Test configuration tab is checked. Requires SM NAS-5G Version 16.5.0 or higher and SM NGAP Version 16.2.0 or higher.

Tcl Parameter:  

SecGnbUserAddrEn

gNB-DU User Node, gNB-CU User Node

Physical Interface 

Enter the Physical Interface details for gNB-CU User Node, gNB-DU User Node and gNB-S-DU User Node

The gNB-S-DU User Node is used for Secondary Node configuration on the gNB CU SA Nodal when MR-DC is enabled on the NAS-5G MM Tab. The Tcl parameters below start with "Sn".

Tcl Parameter:  

GnbDuUserAddrEn GnbDuUserAddr SnGnbDuUserAddr GnbCuUserAddr

 

 

NR-U

Available on gNB-DU User Node on the gNB CU NSA Nodal and gNB CU SA Nodal test cases.

Flow Control Function on gNB CU Nodal (NSA and SA ) test cases. The Flow Control function is applied when an E-RAB is configured for the split bearer option and only for DL i.e. the flow control information is provided only by the SeNB to the MeNB for the MeNB to control the downlink user data flow to the SeNB.

The flow control function is further described in TS 38.425. section 5.4.2 (Downlink Data Delivery Status). The packet loss handling at the DU per spec 38.425 section 5.4.1 Transfer of Downlink User Data.

The gNB-S-DU User Node is used for Secondary Node configuration on the gNB CU SA Nodal when MR-DC is enabled on the NAS-5G MM Tab. The Tcl parameters below start with "Sn".

 

RB Buffer Size

Enter the value of the desired buffer size reported by DU to CU.  For Landslide CU, it doesn't make a difference.  A real SUT-CU will ensure that data pending transmission at DU never exceeds the RB Buffer Size.

When “0” is entered in the GUI, the default value of 4,294,967,295 is sent; otherwise the value from the GUI is sent in DDDS. When 4,294,967,295 is sent, NR-U will  be disabled at DL User data at CU Node; when 4,294,967,294 is sent, NR-U will be enabled.

Range : 0 to 4294967295, 0 = Unlimited Buffer

Tcl Parameter: GnbDuUserRbBuffSize

Tcl Parameter: MobGnbDuUserRbBuffSize

Tcl Parameter: SnGnbDuUserRbBuffSize

RB Service Rate

Enter the RB Service Rate. The rate affects the way flow-control feedback works from DU to CU. When it is set to zero, F1-U data received at DU (or X2-U data at ENB) is deemed to be transmitted immediately. Thus, flow-control feedback indicates all packets been sent. When set to a non-zero value, DU adjusts its reporting of "Highest transmitted PDCP-SN" according to the bytes/second rate specified in this parameter.   Note : because data traffic is emulated, DMF data is not actually held back according to the service-rate.  Rather it's only the feedback about what got transmitted that get's affected by this parameter.

Range : 0 to 4294967295, 0 = Unlimited Data Rate

Tcl Parameter: GnbDuUserRbSvcRate

Tcl Parameter: MobGnbDuUserRbSvcRate

Tcl Parameter: SnGnbDuUserRbSvcRate

Lost Packet Wait Time (ms)

Enter Lost Packet Wait Time in milliseconds. When DU detects a gap in NR-U Sequence # in DL direction, it waits at least this amount of time before declaring the missing packet (s) as lost (for subsequent reporting of lost Sequence Number (s)). When it is set to zero, it means any gap in sequence numbers immediately leads to lost-packet declaration. Range : 0 to 10

Tcl Parameter: GnbDuUserLostPktWaitTime

Tcl Parameter: MobGnbDuUserLostPktWaitTime

Tcl Parameter: SnGnbDuUserLostPktWaitTime

Piggyback Wait Time (ms)

NR-U "Downlink Data Delivery Status" feedback to CU can be sent in two ways. Piggy-backing it along with UL Data NRU-PDCP packet towards CU. Or as a standalone NRU-only packet.  The first one is more economical. This time out value specifies how long DU will wait (when its needs to send NRU DDDS) for an opportunity to piggy-back NRU packet with UL data. After this time expires, the NRU DDDS will be sent as a standalone packet.

Range : 0 to 100 (0 value means DDDS is reported only when explicitly requested by CU or periodically)

Tcl Parameter: GnbDuUserLostPgbkWaitTime

Tcl Parameter: MobGnbDuUserLostPgbkWaitTime

Tcl Parameter: SnGnbDuUserLostPgbkWaitTime

Max DDDS Gap (ms)

It's a periodic timer that only kicks in if it has been this long since a DDDS was sent to CU.

0 means that this "periodic" timer is not used. DDDS are reported only when requested by CU or there is a lost packet.

Range : 0 to 10000 (0 means DDDS is driven by Report Polling)

Tcl Parameter: GnbDuUserMaxDddsGap

Tcl Parameter: MobGnbDuUserMaxDddsGap

LS-CU

For certain test configurations, standalone NR-U packet may not get routed to correct Data Thread on Landslide CU. By enabling LS-CU, a workaround will be invoked to allow multi-data-threaded Landslide CU to correctly receive standalone NR-U packets. Note : A real CU SUT should not encounter this issue.

Tcl Parameter: GnbDuUserLsCuEn

Tcl Parameter: MobGnbDuUserLsCuEn

Tcl Parameter: SnGnbDuUserLsCuEn

 

 

N2 to AMF

N3 to UPF

Available in gNB CU Node when SA Mode is enabled. N2 to AMF Node and N3 to UPF Node become available for input.

Tcl Parameter: GnbCuN2Addr

Tcl Parameter: GnbCuN3Addr

gNB CU Xn User Node

Available in gNB CU Node when Xn Interface is enabled. 

Tcl Parameter: GnbCuXnUserAddr

gNB CU-UP E1 Node

Available in gNB CU Node TC when E1 Interface to CU-CP is enabled. 

Enter gNB-CU-UP ID. 36bits, similar as gNB CU ID. 

gNB CU NSA/SA Nodal treats leftmost 22 bits as gNB ID (a range from 0 to 4194303),  and the left 14 bits as Cell ID (a range from 0 to 16383).

Range : 0 to 68719476735.

Default : 0

Select to enter the gNB CU-UP Name. Range : up to 50 characters

Select to enter the MCC (3 digits) / MNC (2 or 3 digits) of the gNB CU-UP E1 Node.

Select the Number of NSSAIs. Range : 1 to 8

Enter the NSSAI (Network Slice Selection Assistance Information).

The NSSAI contains two components: the SST (Slice / Service Type) and an optional SD (Slice Differentiator).

Range of SST : 0 to 255, default : 1

Range of SD : 1 to 6 Hex Characters

Tcl Parameter: GnbCuUpNameEn

Tcl Parameter: GnbCuUpName

Tcl Parameter: GnbCuUpMcc

Tcl Parameter: GnbCuUpMnc

Tcl Parameter: GnbCuUpE1Addr

Tcl Parameter: GnbCuUpNumNssai

Tcl Parameter: GnbCuUpNssai_1

 


GGSN Testing

GGSN Nodal

In the GGSN Nodal test case, the User Node is optional and it provides bearer plane interfaces for the emulated SGSNs.

When you select Test Activity as Command Mode on the Test Configuration tab, you may select Use Alternate User Address to enable the node and enter an alternate address for data traffic.

Enter the Number of RNCs/BSSs per SGSN.

Option: 1 - 1000.

Tcl Parameter: SgsnUsrNumRncsBss

GGSN Node

In GGSN Node test case, when you are using the mXP platform to run STC Data, the Default Routing and Next Hop IP Address parameters are available.

 


HSGW Nodal

In the HSGW Nodal test case, the User Node simulates one or more UEs that terminate the S1-MME interface.

In addition, when SGW Node Emulation is selected (on Test Configuration tab), Target SGW User Node provides configuration to test the SGW sessions from Target eNodeB User Node via Target MME SUT ending at the Local Mobility Anchor (LMA) SUT.


MGW CN User Node

In MGW Nodal test case, the CN User Node represents the User plane node on the core network side.

# of Nodes

Enter Number of Nodes.

Range: 1 to 1000

Default: 1

Tcl Parameter: CnUserNodeAddr

Starting RTP Port

Must be an even number. Auto increment by two per mobile subscriber.

Range: 1 to 65535

Default: 2000

Tcl Parameter: CnUserRtpPort


MME Testing

ENodeB User Node

In MME Nodal test case, User Node routes bearer plane traffic and separates control and user traffic.

NOTE: In the MME Nodal Test case, if MAC Address for the following nodes is configured, then MAC address per eNodeB will increment by 1 based on the configured MAC address. Target eNodeB Control Node, Target eNodeB Security Node, Target eNodeB User Node, eNodeB Control Node, eNodeB Security Node and eNodeB User Node.

NOTE: Starting User IP/Mask to include sequence number in GTP-U header and Next Hop Address us available only when your system is licensed for Landslide mX and you select Test Center Chassis on the Data Traffic tab.

IMPORTANT: In MME Nodal and Node test cases, to support alternative termination point for IPSec tunnel ensure the following settings/configuration:

  • Set the Payload Destination ID as 0.0.0.0 for Security GW Node.  
  • When using a Security Gateway in between the eNodeB and the MME, set the Next Hop address in eNodeB Control Node and eNodeB User Node to be the same as the Security Gateway address. (If you are not using a Security Gateway, use Default Routing).

  • When not using a Security Gateway in between the eNodeB and the MME, set the Payload Destination ID and Security Gw Address to be the same as the MME or SGW.

 

MME User Node (SGW Nodal), MME S11 Node and Target MME S11 Node (MME Node)

In MME Node and SGW Nodal test cases, User Node routes bearer plane traffic and separates control and user traffic.

Use Alternate User Address

Available on eNodeB User Node and Target eNodeB User Node tabs and selected by default.

Available on MME Node test case on MME S11 Node and Target MME S11 Node when CP-CIoT EPS Optimization Supported is enabled.

Available on SGW Nodal test case on MME User Node when CP-CIoT EPS Optimization Supported is enabled.

Tcl Parameter:  

EnbUserNodeUseControlAddr EnbHoUserNodeUseControlAddr
MmeUserAddrEn MobMmeUserAddrEn
EnbUserAddrEn MobEnbUserAddrEn
EnbUserAddr MobEnbUserAddr

 

When you select Use Alternate User Address, the Control and User Nodes use different IP Addresses and interface.

When you clear Use Alternate User Address (not selected):

  • The eNodeB User Node is not available for input.
  • The Control and User Nodes use the same IP Address (a single IP Address) and interface. That is, a single IPSec tunnel is created/used for control and user traffic encapsulation.

NOTE: Make sure to set the Payload Destination ID to 0.0.0.0 on S1 IPSec Tunnel settings pane (S1-MME | S1 IPSec) tab so all traffic can be routed through the IPSec tunnel correctly.

Also, when using a Security Gateway, make sure you set the Payload Destination ID to 0.0.0.0.

When a single IP Address is used both the Control and User traffic will be encapsulated into a single measurement tab eNodeB Node. When you Use Alternate IP Address two measurement tabs, eNodeB Node and eNodeB User Node tabs, report the Control and User traffic separately.

eNodeB User Node - gNB CU NSA Nodal

NR-U

Available on eNodeB User Node on the gNB CU NSA Nodal and gNB CU SA Nodal test cases.

Flow Control Function on gNB CU Nodal (NSA/SA) test cases,The Flow Control function is applied when an E-RAB is configured for the split bearer option and only for DL i.e. the flow control information is provided only by the SeNB to the MeNB for the MeNB to control the downlink user data flow to the SeNB.

The flow control function is further described in TS 38.425. section 5.4.2 (Downlink Data Delivery Status). The packet loss handling at the DU per spec 38.425 section 5.4.1 Transfer of Downlink User Data.

RB Buffer Size

Enter the value of the desired buffer size reported by DU to CU.  For Landslide CU, it doesn't make a difference.  A real SUT-CU will ensure that data pending transmission at DU never exceeds the RB Buffer Size.

Range : 0 to 4294967295, 0 = Unlimited Buffer

Tcl Parameter: EnbUserRbBuffSize

RB Service Rate

Enter the RB Service Rate. The rate affects the way flow-control feedback works from DU to CU. When it is set to zero, F1-U data received at DU (or X2-U data at ENB) is deemed to be transmitted immediately. Thus, flow-control feedback indicates all packets been sent. When set to a non-zero value, DU adjusts its reporting of "Highest transmitted PDCP-SN" according to the bytes/second rate specified in this parameter.   Note : because data traffic is emulated, DMF data is not actually held back according to the service-rate.  Rather it's only the feedback about what got transmitted that get's affected by this parameter.

Range : 0 to 4294967295, 0 = Unlimited Data Rate

Tcl Parameter: EnbUserRbSvcRate

Lost Packet Wait Time (ms)

Enter Lost Packet Wait Time in milliseconds. When DU detects a gap in NR-U Sequence # in DL direction, it waits at least this amount of time before declaring the missing packet (s) as lost (for subsequent reporting of lost Sequence Number (s)). When it is set to zero, it means any gap in sequence numbers immediately leads to lost-packet declaration. Range : 0 to 10 Tcl Parameter: EnbUserLostPktWaitTime

Piggyback Wait Time (ms)

NR-U "Downlink Data Delivery Status" feedback to CU can be sent in two ways. Piggy-backing it along with UL Data NRU-PDCP packet towards CU. Or as a standalone NRU-only packet.  The first one is more economical. This time out value specifies how long DU will wait (when its needs to send NRU DDDS) for an opportunity to piggy-back NRU packet with UL data. After this time expires, the NRU DDDS will be sent as a standalone packet.

Range : 0 to 100 (0 value means DDDS is reported only when explicitly requested by CU or periodically)

Tcl Parameter: EnbUserLostPgbkWaitTime

Max DDDS Gap (ms)

It's a periodic timer that only kicks in if it has been this long since a DDDS was sent to CU.

0 means that this "periodic" timer is not used. DDDS are reported only when requested by CU or there is a lost packet.

Range : 0 to 10000 (0 means DDDS is driven by Report Polling)

Tcl Parameter: EnbUserMaxDddsGap

LS-CU

For certain test configurations, standalone NR-U packet may not get routed to correct Data Thread on Landslide CU. By enabling LS-CU, a workaround will be invoked to allow multi-data-threaded Landslide CU to correctly receive standalone NR-U packets. Note : A real CU SUT should not encounter this issue.

Tcl Parameter: EnbUserLsCuEn

 

 

 

SGW User Node

In MME Nodal Node test case, SGW User Node is available to process User plane traffic when you select SGW/PGW Node Emulation  on the Test Configuration tab to decuple control and user plane traffic.

Target SGW User Node is available  to process User plane traffic during mobility testing when SGW Relocation and SGW/PGW Node Emulation  on the Test Configuration.

Dual Stack Support

Use Dual Stack to return both IPv4 and IPv6 addresses when requested. Dual Stack is available for your selection only when you select SGW/PGW Node Emulation or SGW Relocation and SGW/PGW Node Emulation on the Test Configuration tab.

Primary Node

Tcl Parameter:

SgwUserDualStackEn
MobSgwUserDualStackEn
SgwUserAddr

Alternate

Available when you select Dual Stack Support.  Select Alternate Node Address.

Alternate Node

Tcl Parameter:  

SgwUserAltAddr
MobSgwUserAltAddr

 

The Alternate Node Address you enter must be of IPv6 format if the Physical Interface address type you select for the node is an IPv4 address and vice versa.

 


PGW Testing

User Nodes are optional in PGW test cases and SMF Nodal, and can be enabled with the Use Alternate User Address checkbox on the User Node sub-tab.

Select Use Alternate User Address to select the test node settings.

NOTE: When Alternate User Address is not selected, you define same IP address for both GTP tunnels under S5/S8 interface, that is, SGW Control Node and SGW User Node use (the same IP address for both GTP-U and GTP-C).

 

Tcl Parameter:

SgwUsrAddrEn

SgwUserAddr

MobSgwUsrAddrEn MobSgwUsrAddr

PGW User Node

During PGW Node testing, PGW User Node allows you to directly connect PGW on user plane interface and is available only when you select  Mobility as Inter-Technology on the Emulator Configuration tab.

Tcl Parameter:

PdnGwUsrAddrEn

PdnGwUserAddr

Dual Stack Support

Use Dual Stack to return both IPv4 and IPv6 addresses when requested. The Alternate pane becomes available to enter IP address.

PdnGwUsrDualStackEn

PdnGwUsrAltAddr

Select Drop Malformed UL User Packets for PGW Node to drop malformed UL packets on SGi interface. 

PdnGwDropMalformedUlUserPktsEn

Sxb User Node and Sxb User GTP Node (CUPS - Control and User Plane Separation)

During PGW Node testing, Sxb User Node and Sxb User GTP Node allow you to directly connect PGW-U to UP function via the Sxa Control plane and the User plane interface and is available only when you select Sxb Interface to CP on the Emulator Configuration tab. The number of Peers becomes available is User Initiates Association is not selected on the PFCP Tab. Enter the number of peer associations allowed for each node. Enter Number of Peers (1 - 10).

Tcl Parameter:

SxbUserNodeAddr

SxbUserGtpUAddr

SxbUserPeers


SGW Testing

ENodeB User Node

In SGW test case, Num of eNodeBs Per MME is available when Test Activity is Capacity or Command Mode or Sequencer.

Range: 1 - 1000

Default: 1

Tcl Parameter: NumEnbPerMMe

The value you enter is used to determine the total number of eNodeB User Nodes.  

Total number of eNodeB User Nodes = Num eNodeB's per MME * # of Nodes (value from the MME Control Node.)

NOTES: IP addresses must be valid and not overlap (TAS at runtime checks for IP overlap). For example, if you have configured 2 MMEs and 3 eNodeBs Per MME, you much configure a total of 14 IP addresses for MMEs and eNodeBs:

  • 2 Ips for 2 MME Control Nodes (Auto Incrementing) (e.g. 10.0.0.1, 10.0.0.2)
  • 6 Ips for 6 eNodeB User Nodes (Auto Incrementing) (e.g. 10.0.0.3, ..., 10.0.0.8)
  • 6 Ips for 6 Target eNodeB User Nodes (Auto Incrementing) (e.g. 10.0.0.9, ..., 10.0.0.14)

gNodeB User Node

During SGW Nodal testing, the gNodeB User Node becomes available when Handoff Type = Dual Connectivity and Test Activity = "Intra-MME Mobility" or "Session Loading with Mobility" and Mobility Type= "Intra-MME". Indicates 4G to 5G dual connectivity - phase I. The SGW Nodal will handover between 4G eNodeB and 5G gNodeB. The gNodeB User Node becomes available in Network devices tab. The eNodeB User Node is not available for input.

During MME Nodal testing, the gNodeB User Node becomes available when Dual Connectivity (NAS Tab) is enabled and Test Activity = "Capacity" or " Session Loading Test", or "Intra-MME Mobility", or "Inter-MME Mobility" or "Session Loading with Mobility" and Mobility Type= "Intra-MME" or "Inter-MME" and X2 off. Indicates 4G to 5G dual connectivity - phase I. The SGW Nodal will handover between 4G eNodeB and 5G gNodeB. The gNB User Node becomes available in Network devices tab.  

During MME Nodal testing, the Target gNodeB User Node becomes available when Dual Connectivity - Enable Target gNB User Node (NAS Tab) is enabled and Test Activity = "Intra-MME" or "Inter-MME" or "Session Loading with Mobility" and Mobility Type= "Intra-MME" or "Inter-MME" and DC Option = 3x. Indicates support for handover between two dual connected 4G + 5G nodes.   

During UPF Nodal testing, the gNodeB User Node is available when Test Activity = "Capacity". The Target gNB User node becomes available on UPF Nodal test case when Test Activity = Mobility, Handoff Type = Xn and Vo5G is enabled. Cell ID, TAC, MCC and MNC are also available for input.

Tcl Parameter:

GnbUserAddr

MobGnbUserAddr

PDN GW User Node

During SGW Nodal testing, PDN GW User Node allows you to directly connect PGW on user plane interface and is available only when you select PGW Node Emulation on the Test Configuration tab.

Select Use Alternate User Address to select the test node settings.

Tcl Parameter:

PdnGwUsrAddrEn

PdnGwUserAddr

SGSN S6d Node

During SGW Nodal testing, SGSN S6d Node allows you to connect UE and HSS to the Serving Gateway and PDN GW on user plane interface and is available only when you select HSS Inteface on the Test Configuration tab.

SGW S5 User Node

During SGW Node testing, SGW S5 User Node settings allows you to test user plane tunneling between Serving GW and PDN GW and is available only when you select Separate S5 Interface on the Emulator Configuration tab.

Target ePDG User Node

Target ePDG User Node settings allows you to test user plane tunneling during handover of call flows between Serving GW and PDN GW and is available only when you select ePDG Node Emulation on the SGW Test Configuration tab or on the MME Nodal Test Configuration Tab.

Select Use Alternate User Address to select the test node settings.

Tcl Parameter:

TgtEpdgUserAddrEn

Dual Stack Support

Use Dual Stack to return both IPv4 and IPv6 addresses when requested. The Alternate pane becomes available to enter IP address.

TgtEpdgUserDualStackEn

TgtEpdgUserAddr

TgtEpdgUserAltAddr

SGW User Node

In SGW Node test case, the User Node routes bearer plane traffic and separates control and user traffic.

For SGW User and S5 SGW Control/User test nodes (Primary and Alternate), “the Outbound Traffic Port setting from SGW Control Node is used”.

Dual Stack Support

In SGW Node test case, use Dual Stack to return both IPv4 and IPv6 addresses when requested.

Tcl Parameter: SgwUserDualStackEn

Alternate Node Address

Available when you select Dual Stack Support.  

Tcl Parameter:  SgwUserAltAddr

The Alternate Node Address you enter must be of IPv6 format if the Physical Interface address type you select for the node is an IPv4 address and vice-versa.

Sxa User Node and Sxa User GTP Node (CUPS - Control and User Plane Separation)

During SGW Node testing, Sxa User Node and Sxa User GTP Node allow you to directly connect SGW-U to UP function via the Sxa Control plane and the User plane interface and is available only when you select Sxa Interface to CP on the Emulator Configuration tab. The number of Peers becomes available is User Initiates Association is not selected on the PFCP Tab. Enter the number of peer associations allowed for each node. Enter Number of Peers (1 - 10).

During SGW Node testing, Sxa+Sxb User Node and Sxa+Sxb User GTP Node allow you to directly connect SGW-U and PGW-U on Sxa+Sxb user plane via the combined Sxa/Sxb Control plane and the User plane interface  and is available only when you select Sxa +Sxa Interface to CP and PGW Node Emulation on the Emulator Configuration tab.

Tcl Parameter:

SxaUserNodeAddr

SxaUserGtpUAddr

SxaUserPeers

 


UMTS

In the UMTS test case, the User Node provides separate bearer plane interfaces for the emulated RNCs and the GGSN User Node provides a separate bearer plane interface for an emulated GGSN (optional).

Tcl Parameters:

PdnGwUserAddr

SgwUserAddr

GGSN User Node

During UMTS testing, the GGSN User Node is available only when you select GGSN Node Emulation on the Test Configuration tab.


UPF N4 Node and UPF N4 GTP Node (5G)

During UPF Node testing, SMF/UPF Node Emulation in the AMF Nodal test case and UPF Node Emulation in the AMF Node / SMF Nodal test cases, UPF N4 Node and UPF N4 GTP Node allow you to directly connect UPF (User Plane Function) through the N4 Interface. UPF N4 Node is used for N4 Control Plane while UPF N4 GTP Node is used for N4 User Plane.

The number of Peers becomes available if User Initiates Association is not selected on the PFCP Tab. Enter the number of peer associations allowed for each node. Enter Number of Peers (1 - 10).

Tcl Parameter:

N4UserNodeAddr

N4UserGtpUAddr

N4UserPeers


The main User Nodes are defined on the User Node sub-tab. Nodes used for mobility handoffs are defined on the Mobility User Node sub-tab when a mobility test is selected.

NOTES:

  • A Control Node/User Node pair must use the same type of physical layer.

  • When Data Traffic is included in the test, some packet loss may be reported as PDP contexts are deleted. Since the delete request is sent from a different source address (the Control Node) than the Data Traffic, a GGSN SUT may process a delete request prior to forwarding a data packet. Example:Example:If a TCP connection was in the process of being torn down prior to context deactivation, the MN would send an ACK in response to the FIN/ACK and follow that with a delete request towards the GGSN. If the GGSN processed the delete request first, the ACK would never be forwarded to the Network Host since the context no longer existed. Packet loss detection would then be triggered on the Network Host, and packet loss reported.

Ethernet Configuration

With an Ethernet User Node, you can define:

Related Measurements