|
PFCP Version
|
Select PFCP Version.
Options: 14.1.0/Sep2017 (default), 14.2.0/Dec2017, 14.5.0/Sep2018, 15.1.0/Mar2018 (default), 15.3.0/Sep2018, 15.4.0/Dec2018 , 15.6.0/Jun2019, 16.5.0/Sep2020, 17.9.0/Jun2023, (the 5G Test Cases version number starts with 15 or higher)
The differences between Release 14.2.0 and 14.1.0 are as follows:
|
NOTE: Reference Updates for version 15.6.0/Jun 2019
- C4-191393 CR0235 Release of F-TEID by the UP Function upon removal of PDR. The UP Function will release the F-TEID that was assigned to the removed PDR only if there is no more PDR assigned with the same F-TEID. Change applies to all versions.
- C4-191543 CR0243 Accurate Interface Type for Supporting Performance Measurement. On N4|PFCP|Session Parameters, added checkbox "3GPP Interface Type". If enabled, the 3GPP Interface Type IE will be reflected in corresponding PDRs and FARs. Change applies to PFCP version 15.6.0 or above and is currently supported only in PDRs and FARs on 5G test cases.
- C4-190425 CR0212 Policy and Charging Control. Change applies to all versions. Implementation:
1. Added support for uplink traffic verification on PGW / Combined SGW and PGW / UPF Node.
2. Added the "UE IP Address" IE in uplink PDRs for PGW / Combined SGW and PGW / UPF Node.
3. Added GUI configuration of "Gate Status" for 5G flow level QERs.
- In the 5G test cases with N4|PFCP, the Supported Features/FTUP option is required for PFCP Version 16.5.0 and higher. The GUI forces the option to be checked. For API users, Tcl validation will force it as a Tcl upgrade without setting an error.
The following 3GPP release CRs are currently supported or partially supported:
- C4-192381 / CR 0259 - UE IP addresses/prefixes allocation by UPF
- C4-193257 / CR 0280 - Essential Correction on Heartbeat procedure Added handling of Heartbeat Requests even if the PFCP association is not yet set up. Change applies to all Landslide PFCP versions and to both 4G and 5G.
- C4-193634 / CR 0283 - 3GPP Interface Type values - Already supported for 5G in Landslide PFCP version 15.6.0 or above ( N19 is not yet supported. ) Not yet supported for 4G.
- C4-195506 / CR 0335 - Cause No established PFCP Association - Added support for this error cause for the following messages: PFCP Association Update Request, PFCP Association Release Request and PFCP Session Establishment Request. Change applies to all Landslide PFCP versions and to both 4G and 5G.
- C4-201284 / CR 0374 - F-TEID allocation - In 5G and EPC, only UPF supports F-TEID allocation.
- C4-200515 / CR 0361 - The Source IP Address in Heartbeat Request message - Added support of this optional IE through GUI configuration. Change applies to Landslide PFCP version 16.5.0 or above.
- C4-200956 / CR 0366 - The Recovery Time Stamp in PFCP Session Establishment Request message - Added support of this optional IE through GUI configuration. Change applies to Landslide PFCP version 16.5.0 or above.
- C4-202471 / CR 0395 - New S-NSSAI IE - Added support of the S-NSSAI IE (if applicable) in the PFCP Session Establishment Request through GUI configuration. Change applies to Landslide PFCP version 16.5.0 or above and to AMF Node with SMF Emulation and SMF Node only.
- C4-200956 / CR 0366 - Interface Type of Traffic Endpoint - Added support to move the 3GPP Source Interface Type IE from PDR to Traffic Endpoint if PDIU is enabled. Change applies to Landslide PFCP version 16.5.0 or above.
|
Tcl Parameter: SxaControlSpecVer
Tcl Parameter: SxbUserSpecVer
Tcl Parameter: N4UserSpecVer
Tcl Parameter: N4ControlSpecVer
|
|
User Initiates Association
|
Select for User to initiate Association request. If checked, then the UP side will initiate the association otherwise the CP side will initiate the association.
When enabled in the UPF Node Test Case, the SMF N4 Node becomes available in Network Devices.
Tcl Parameter: SxaControlUserInitEn
Tcl Parameter: SxaUserUserInitEn
Tcl Parameter: SxbControlUserInitEn
Tcl Parameter: SxbUserUserInitEn
Tcl Parameter: N4UserUserInitEn
Tcl Parameter: N4ControlUserInitEn
|
|
Association Setup Time (s)
|
The association Setup Time in seconds is used as a delay in setting up the association.
Range: 0 — 65535
Default: 2
Tcl Parameter: SxaControlNodeSetupTime
Tcl Parameter: SxaUserNodeSetupTime
Tcl Parameter: SxbControlNodeSetupTime
Tcl Parameter: SxbUserNodeSetupTime
Tcl Parameter: N4UserNodeSetupTime
Tcl Parameter: N4ControlNodeSetupTime
|
|
Retries
|
The number of retries is used by the Node level messages.
Range: 0 — 65535
Default: 3
Tcl Parameter: SxaControlNodeRetries
Tcl Parameter: SxaUserNodeRetries
Tcl Parameter: SxbControlNodeRetries
Tcl Parameter: SxbUserNodeRetries
Tcl Parameter: N4UserNodeRetries
Tcl Parameter: N4ControlNodeRetries
|
|
Retry Time (s)
|
The Retry time in seconds is used by the Node level messages.
Range: 0 — 65535
Default: 5
Tcl Parameter: SxaControlNodeRetryInterval
Tcl Parameter: SxaUserNodeRetryInterval
Tcl Parameter: SxbControlNodeRetryInterval
Tcl Parameter: SxbUserNodeRetryInterval
Tcl Parameter: N4UserNodeRetryInterval
Tcl Parameter: N4ControlNodeRetryInterval
|
| Heartbeat Retries |
The number of Heartbeat retries between the CP and UP nodes.
Range: 0 — 65535
Default: 3
Tcl Parameter: SxaControlNodeHeartbeatRetries
Tcl Parameter: SxaUserNodeHeartbeatRetries
Tcl Parameter: SxbControlNodeHeartbeatRetries
Tcl Parameter: SxbUserNodeHeartbeatRetries
Tcl Parameter: N4UserNodeHeartbeatRetries
Tcl Parameter: N4ControlNodeHeartbeatRetries
|
| Heartbeat Retry Time (s) |
The Heartbeat Retry time in seconds between the CP and UP nodes.
Range: 0 — 65535
Default: 20
Tcl Parameter: SxaControlNodeHeartbeatInterval
Tcl Parameter: SxaUserNodeHeartbeatInterval
Tcl Parameter: SxbControlNodeHeartbeatInterval
Tcl Parameter: SxbUserNodeHeartbeatInterval
Tcl Parameter: N4UserNodeHeartbeatInterval
Tcl Parameter: N4ControlNodeHeartbeatInterval
|
| Source IP Address in Heartbeat Request |
Available in AMF Node (with SMF Emulation enabled), SMF Node and UPF Nodal /UPF Node when PFCP Version is 16.5.0 or higher.
Select to add Source IP Address in Heartbeat Request which is an optional IE.
Tcl Parameter: N4ControlSrcIpInHbReqEn
Tcl Parameter: N4UserSrcIpInHbReqEn
|
| Use FQDN As Node ID |
Select to enter a FQDN (Fully Qualified Domain Id). Node Id becomes available for input. It will be used as the Node Identifier for either the CP or UP Nodes. If this is not checked, the Sxa/Sxb Control Plane address will be used.
Tcl Parameter: SxaControlNodeIdFqdnEn
Tcl Parameter: SxaUserNodeIdFqdnEn
Tcl Parameter: SxbControlNodeIdFqdnEn
Tcl Parameter: SxbUserNodeIdFqdnEn
Tcl Parameter: N4UserNodeIdFqdnEn
Tcl Parameter: N4ControlNodeIdFqdnEn
|
| Support Standalone Session(s) |
Available in AMF Node (with SMF Emulation enabled), SMF Node and UPF Nodal.
Select to support standalone PFCP session (s). Default is to enable this checkbox.
When not selected, the standalone PFCP session is disabled.
Tcl Parameter: N4ControlSaSessEn
|
| Support Repeated Session Establishment Request |
Select to support repeated PDU Session Establishment Requests. Available in UPF Node test case.
When enabled, repeated PDU Session Establisment requests will receive a successful response.
Tcl Parameter: N4UserNodeHandleReSessEstReqEn
|
| Node ID |
Available when Use FQDN as Node ID is enabled. Enter a fully qualified unique domain name for each CP or UP Node. Auto-increment is available.
Default: Spirent.com
Tcl Parameter: SxaControlNodeIdFqdn
Tcl Parameter: SxaUserNodeIdFqdn
Tcl Parameter: SxbControlNodeIdFqdn
Tcl Parameter: SxbUserNodeIdFqdn
Tcl Parameter: N4UserNodeIdFqdn
Tcl Parameter: N4ControlNodeIdFqdn
|
| UE IPv6 Address Pool |
Available when UEIP is enabled. Enter valid IPv6 Prefix. Requires "[ipv6-address]/[prefix-length]".
Enter to add UE IP Pool in Session establishment Response message.
Available in UPF Node, AMF Nodal (with SMF/UPF simulated), SMF Nodal (with UPF Node Emulation).
Tcl Parameter: N4UserUserIpv6AddrPool
|
| UE IPv4 Address Pool |
Available when UEIP is enabled. Enter valid IPv4 Address pool without Mask.
Enter to add UE IP Pool in Session establishment Response message.
Available in UPF Node, AMF Nodal (with SMF/UPF simulated), SMF Nodal (with UPF Node Emulation):
Tcl Parameter: N4UserUserIpv4AddrPool
|
| Starting Local Sx GTP-U Teid Starting Local PFCP GTP-U Teid |
Enter starting local GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier). Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to UP is selected. Used as the local GTP-U TEID for the SX User Plane.
Available on N4 Interface in AMF Node Test Case, SMF Node and UPF Nodal test cases.
Range: 0 to 4294967295
Default: 30000
Enter starting local GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier). Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to CP is selected and FTUP is enabled.
Available on N4 Interface in UPF Node Test Case and FTUP is enabled.
Enter starting local PFCP GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier).
Range: 0 to 4294967295
Default: 40000
Tcl Parameter: SxaControlUTeid
Tcl Parameter: SxbControlUTeid
Tcl Parameter: SxaUserUTeid
Tcl Parameter: SxbUserUTeid
Tcl Parameter: N4UserUTeid
Tcl Parameter: N4ControlUTeid
|
| Starting Peer Sx GTP-U Teid Starting Peer PFCP GTP-U Teid |
Enter starting peer GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier). Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to UP is selected. Used as the remote GTP-U TEID for the SX User Plane .
Available on N4 Interface in AMF Node, SMF Node and UPF Nodal Test Cases. Default = 40000.
Range: 0 to 4294967295
Default: 30000
Tcl Parameter: SxaControlPeerUTeid
Tcl Parameter: SxbControlPeerUTeid
|
| Starting CP Seid |
Enter starting Control Plane SEID (Session Endpoint Identifier). Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to UP is selected. Used as the local SEID for the CP Node.
Available on N4 Interface in AMF Node, SMF Node and UPF Nodal Test Cases. Default = 10000.
Range: 0 to 18446744073709551615 or 0x0 to 0xFFFFFFFFFFFFFFFF (hex)
Default: 30000
Tcl Parameter: SxaControlCSeid
Tcl Parameter: SxbControlCSeid
Tcl Parameter: N4ControlCSeid
|
| Starting Uplink GTP-U Teid |
Available on N4 Interface in AMF Node Test Case, SMF Node and UPF Nodal test cases.
Range: 0 to 4294967295
Default: 2000000
Enter starting uplink GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier).
Tcl Parameter: N4ControlUplinkGtpuTeid
|
| Starting Downlink GTP-U Teid |
Available on N4 Interface in AMF Node Test Case, SMF Node and UPF Nodal test cases.
Range: 0 to 4294967295
Default: 4000000
Enter starting downlink GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier).
Tcl Parameter: N4ControlDownlinkGtpuTeid
|
| Graceful Association Release |
Select to enter a graceful association release. Enter Graceful Release Time in seconds below. Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to CP is selected. Available on N4 Interface in UPF Node Test Case.
Tcl Parameter: SxaUserGracefulReleaseEn
Tcl Parameter: SxbUserGracefulReleaseEn
Tcl Parameter: N4UserGracefulReleaseEn
|
| Graceful Release Time (s) |
Available when Graceful Association Release is selected. Enter wait time before release in seconds.
Range: 0 — 65535
Default: 5
Tcl Parameter: SxaUserGracefulReleaseTime
Tcl Parameter: SxbUserGracefulReleaseTime
Tcl Parameter: N4UserGracefulReleaseTime
|
| Starting UP Seid |
Enter starting User Plane SEID (Session Endpoint Identifier). Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to CP is selected. Used as the local SEID for the UP Node.
Available on N4 Interface in UPF Node Test Case.
Range: 0 to 18446744073709551615 or 0x0 to 0xFFFFFFFFFFFFFFFF (hex)
Default: 20000
Tcl Parameter: SxaUserCSeid
Tcl Parameter: SxbUserCSeid
Tcl Parameter: N4UserCSeid
|
| DDND |
This is an optional UP feature, indicating the UP function supports Downlink Data Notification Delay if enabled. Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) is enabled.
Tcl Parameter: SxaUserDdndEn
|
| FTUP |
Select to support UP assigned F-TEID. Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to CP is selected. Available on N4 Interface in AMF/SMF/UPF Test Cases.
In the 5G test cases with N4|PFCP, the Supported Features/FTUP option is required for PFCP Version 16.5.0 and higher. The GUI forces the option to be checked. For API users, Tcl validation will force it as a Tcl upgrade without setting an error.
When enabled, Starting Local Sx GTP-U TEID and Starting GTP-U Teid become available for input. If Separate S5 Interfaces is enabled on SGW Node, then Starting S5 GTP-U Teid becomes available for input.
Tcl Parameter: SxaUserFtupEn
Tcl Parameter: N4ControlFtupEn
Tcl Parameter: N4UserFtupEn
|
| EMPU |
Select to support End Marker in GTP-U for mobility scenario on N4 Interface in AMF/SMF/UPF Test Cases.
Available when Sxb Interface to CP is selected or when Sxb Interface to UP is selected on PGW Node Test case.
Available when (Sxa Interface to CP or Sxa+Sxb Interface to CP) is selected or when (Sxa Interface or Sxa+Sxb Interface to UP) is selected on SGW Node Test case.
PGW/SGW have been updated to include the PFCPSMReq-Flag (see 29.244) when sending the PFCP session Modification request for the UpdateFar. SNDEM (Send End Marker Packets) flag is part of PFCPSMReq-Flags.
The following two scenarios are supported:
1. In case of eNodeB relocation during handover procedure without SGW-U change, SGW-C indicates to the SGW-U to switch the S1 path(s) by sending an Sx session modification request message with the new F-TEID-u of eNodeB and* in addition, provide an indication to the SGW-U to send the end marker packet(s) on the old path.*
2. In case of SGW-U relocation during handover procedure, PGW-C indicate to the PGW-U to switch the S5/S8 path(s) by sending an Sx session modification request message (bearer ID, new F-TEID of SGW-U) and in addition, provide an indication to the PGW-U to send the end marker packet(s) on the old path.
End Marker Messages Nas 5g SM Measurements and UPF N3 Node Measurements.
Per 3GPP 23.501 sections 5.8.2.9 and 29.244 section 5.3.2.
Tcl Parameter: SxaControlEmpuEn
Tcl Parameter: SxaUserEmpuEn
Tcl Parameter: SxbControlEmpuEn
Tcl Parameter: SxbUserEmpuEn
Tcl Parameter: N4ControlEmpuEn
Tcl Parameter: N4UserEmpuEn
|
| PDIU |
Select to support PDI Optimization and Traffic Endpoint IE in N4 Interface. Available in N4 Interface in AMF/SMF/UPF Test Cases under Supported Features. On SMF Node test case, this adds usage of Traffic Endpoint IE for Uplink and Downlink PDRs if PDUI is enabled. Per 3GPP 29.244.
Available on SGW Node test case when Sxa+Sxb Interface to CP and PGW Node Emulation are enabled and on PGW Node test case when Sxb Interface to CP is enabled.
Tcl Parameter: N4ControlPdiuEn
Tcl Parameter: N4UserPdiuEn
Tcl Parameter: SxaUserPdiuEn
Tcl Parameter: SxbUserPdiuEn
|
| IP6PL |
Select to support IPV6PL in UP Function Features in N4 Interface. IP6PL indicates if UPF supports UE IPv6 address allocation with IPv6 prefix length other than default /64 (including allocating /128 individual IPv6 address). (Reference: TS29.244 (v16.5.0) - clause 8.2.25)
Available in AMF Node (with SMF Emulation enabled), SMF Node and UPF Node when PFCP Version is 16.5.0 or higher.
When enabled, UE DHCPv6 IP Address becomes available.
Tcl Parameter: N4ControlIp6plEn
Tcl Parameter: N4UserIp6plEn
|
| UEIP |
Select for UE IP IE to be added to Session establishment Response message from UP function and to be able to configure the UE UP addresses or prefixes. And in PFCP Association Setup Response message, adding UEIP feature flag in “UE Function Features IE”.
Available in AMF Nodal (with SMF/UPF Emulation enabled), AMF Node (with SMF Emulation enabled), SMF Nodal (with UPF Node Emulation), SMF Node and UPF Nodal / Node when PFCP Version is 16.5.0 or higher.
In UPF Node, AMF Nodal (with SMF/UPF simulated), SMF Nodal (with UPF Node Emulation) configure the UE IPv6 Address Pool and UE IPv4 Address Pool.
(Reference: TS29.244 (v16.5.0) - clause 5.21 - UP function feature is required for UE IP allocation through UPF.)
UEIP is not supported when PDU Type = Ethernet in NAS-5G SM.
Tcl Parameter: N4ControlUserIpEn
Tcl Parameter: N4UserUserIpEn
|
| ATSSS-LL |
Select for ATSSS (Access Traffic Steering, Switching, Splitting).
Per the 23.501 section 5.32, The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network. The multi-access PDU Connectivity Service is realized by establishing a Multi-Access PDU (MA PDU) Session, i.e. a PDU Session that may have user-plane resources on two access networks.
AMF Nodal support ATSSS Procedures when Non-roaming and Roaming with Local Breakout. According 23.502-gd0 -> 4.22.2.1
Available in UPF Nodal / SMF Node / AMF Node with SMF Emulation when when PFCP Version >= 16.5.0.
Tcl Parameter: N4ControlAtsssllEn
Tcl Parameter: N4UserAtsssllEn
|
| QFQM |
Select to set the QFQM feature flag in the Function Features IE if it supports per QoS flow per UE QoS
monitoring (see clause 8.2.25 in TS 129.244 V 16.4.0). If so, the SMF may request the UPF to perform the per QoS flow per UE QoS
monitoring during a PFCP session establishment or a PFCP session modification procedure.
Available when PFCP Version = > 16.5.0/Sep2020 for AMF /SMF / UPF Node test cases.
Tcl Parameter: N4ControlQfqmEn
|
| Starting GTP-U Teid |
Enter starting GTP-U Teid. Available when Sxa Interface to CP or Sxa+Sxb Interface to CP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to CP is selected and FTUP is enabled. Available on N4 Interface in UPF Node Test Case when FTUP is enabled.
Range: 0 to 4294967295
Default: 2000000
Tcl Parameter: SxaUserGtpuTeid
Tcl Parameter: SxbUserGtpuTeid
Tcl Parameter: N4UserGtpuTeid
|
| Starting S5 GTP-U Teid |
Enter starting S5 GTP-U Teid (GTP (GPRS Tunneling Protocol) - Unique Tunnel Endpoint Identifier). Available when Sxa Interface to CP and Separate S5 Interfaces is selected. Used as the local GTP-U TEID for the S5 interface.
Range: 0 to 4294967295
Default: 4000000
Tcl Parameter: SxaUserS5GtpuTeid
|
| Session Retries |
The number of Session retries for the session level messages.
Range: 0 — 65535
Default: 3
Tcl Parameter: SxaControlSessionRetries
Tcl Parameter: SxaUserSessionRetries
Tcl Parameter: SxbControlSessionRetries
Tcl Parameter: SxbUserSessionRetries
Tcl Parameter: N4UserSessionRetries
Tcl Parameter: N4ControlSessionRetries
|
| Session Retry Time |
The Session Retry time in seconds used for the session level messages.
Range: 0 — 65535
Default: 5
Tcl Parameter: SxaControlSessionRetryInterval
Tcl Parameter: SxaUserSessionRetryInterval
Tcl Parameter: SxbControlSessionRetryInterval
Tcl Parameter: SxbUserSessionRetryInterval
Tcl Parameter: N4UserSessionRetryInterval
Tcl Parameter: N4ControlSessionRetryInterval
|
| 3GPP Interface Type |
Available when PFCP Version > = 15.6.0/Jun2019. If enabled, the 3GPP Interface Type IE will be reflected in corresponding PDRs and FARs.
Currently supported only in PDRS and FARs on the 5G test cases.
Tcl Parameter: N4ControlThreeGppIntTypeEn
|
| Recovery Time Stamp in Session Establishment Request |
Available when PFCP Version > = 16.5.0/Sep2020 in AMF Node with SMF Emulation , SMF Node and UPF Nodal. Select to include Recovery Time Stamp IE in PFCP Session Establishment Request message.
Tcl Parameter: N4ControlRecoveryTimeStampEn
|
| S-NSSAI in Session Establishment Request |
Available when PFCP Version > = 16.5.0/Sep2020 in AMF Node with SMF Emulation and SMF Node. Select to include S-NSSAI IE in PFCP Session Establishment Request message.
Tcl Parameter: N4ControlSnssaiEn
|
| User ID in Session Establishment Request |
Available when PFCP Version > = 15.3.0/Sep2018 in AMF Node with SMF Emulation, SMF Node and UPF Nodal. Select to include User ID (USER-ID IE (IMSI + IMEI) in PFCP Session Establishment Request message.
Reference : 29.244 V15.2 page 74
Tcl Parameter: N4ControlUserIdEn
|
| QoS Monitoring Data |
Enter the Number of QoS Monitoring Data. Available on AMF / SMF Node test cases . If Qos Monitoring for URLLC is enabled and request configured (Support URLLC) in the AMF / SMF Node Test cases, QOS Monitoring Request is sent to RAN. DUSessionResourceModifyRequest message will include the Qos MonitoringRequest IE.
Per 23.503 section 4.3.3 PDU Session Modification>3b
Available when PFCP Version (29.244) >= 16.5.0/Sep2020
Range 0 to 8, Default : 1
Tcl Parameter: N4ControlQosMonDataCnt
| QM ID |
Enter the QoS Monitoring ID.
Enter a string.
Default : qmId1
Tcl Parameter: N4ControlQmId_1
|
| Report Threshold Downlink |
Select to enter the Report Threshold for DownLink for QoS Monitoring Data.
Range : 1 to 4294967295
Default : 0
Tcl Parameter: N4ControlRepThreshDlEn_1
Tcl Parameter: N4ControlRepThreshDl_1
|
| Report Threshold Uplink |
Select to enter the Report Threshold Uplink for QoS Monitoring Data.
Range : 1 to 4294967295
Default : 0
Tcl Parameter: N4ControlRepThreshUlEn_1
Tcl Parameter: N4ControlRepThreshUl_1
|
| Report Threshold Rp |
Select to enter the Report Threshold report for QoS Monitoring Data.
Range : 1 to 4294967295
Default : 0
Tcl Parameter: N4ControlRepThreshRpEn_1
Tcl Parameter: N4ControlRepThreshRp_1
|
| Wait Time (s) |
Select to enter the wait time in seconds for QoS Monitoring Data.
Range : 1 to 4294967295
Default : 1
Tcl Parameter: N4ControlWaitTimeEn_1
Tcl Parameter: N4ControlWaitTime_1
|
| Report Period (s) |
Select to enter the Report Period for QoS Monitoring Data.
Range : 1 to 4294967295
Default : 0
Tcl Parameter: N4ControlRepPeriodEn_1
Tcl Parameter: N4ControlRepPeriod_1
|
| Notify Correlation ID |
Select to enter the Notify Correlation ID for QoS Monitoring Data.
Enter a string value.
Tcl Parameter: N4ControlNotifCorreIdEn_1
Tcl Parameter: N4ControlNotifCorreId_1
|
| Number of QoS Monitoring Parameters |
Enter the Number of QoS Monitoring Parameters.
Raneg : 1 to 3
Default 1
For each QoS Monitoring Parameter, select the Request QOS Monitoring Parameter.
Options : DOWNLINK, UPLINK, ROUND_TRIP
Tcl Parameter: N4ControlReqQosMonParamCnt_1
Tcl Parameter: N4ControlReqQosMonParam_1_1
|
|
| Number of PDRs per Session |
Enter the number of PDRs (Packet Detection Rules) per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 33
Tcl Parameter: N4UserNumPdrsPerSession
|
| Number of FARs per Session |
Enter the number of FARs (Forwarding Action Rules) per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 2
Tcl Parameter: N4UserNumFarsPerSession
|
| Number of QERs per Session |
Enter the number of QERs (QoS Enhancement Rules) per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 16
Tcl Parameter: N4UserNumQersPerSession
|
| Number of BARs per Session |
Enter the number of BARs (Buffering Action Rules) per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 1
Tcl Parameter: N4UserNumBarsPerSession
|
| Number of SDF Filters per Session |
Enter the number of SDF (Service Data Flow) Filters per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 16
Tcl Parameter: N4UserNumSdfFiltersPerSession
|
| Number of URRs Per Session |
Enter the number of URRs (Usage Report Rules) per session. Available on N4 Interface in UPF Node Test Case and in AMF/SMF Nodal with UPF Node Emulation.
Range: 1 to 100
Default: 10
Tcl Parameter: N4UserNumUrrsPerSession
|
| Downlink Data Notification Delay (multiple of 50 ms) |
This is the delay the UP function shall apply between receiving a downlink data packet and notifying the CP function about the arrival of the packet if the UP function supports DDND.
Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) is enabled.
Enter a multiple of 50 milliseconds
Range: 0 — 525
Default: 0
Tcl Parameter: SxaControlDdbd
|
|
UPF Selection
|
Available on N4 Interface in AMF Node Test Case, SMF Node and UPF Nodal test cases when both "Number of SUTs" and "Multiple SUTs per N4 Node" are selected for "UPF N4 Node" under SUT. Select to Enable UPF Selection.
Choose either Location Based or Manual Configuration.
Tcl Parameter: N4ControlUpfSettingsEn
Location Based is available on AMF Node with SMF Emulation and on SMF Node test cases.
If "Location Based" UPF selection is enabled, each UPF SUT can be configured with a service area (i.e. a list of supported TAIs up to 16). This option can only be enabled when both "Number of SUTs" and "Multiple SUTs per N4 Node" under "Systems Under Test" are enabled.
Enter Number of TAIs. Based on "Number of SUTs" on UPF N4 Node. Enter MCC, MNC and TAC for each UPF.
The SMF will dynamically select a UPF SUT based on current UE location during PDU Session Establishment. If no match is found, the first available UPF SUT will be selected.
Tcl Parameter: N4ControlUpfLocationEn
Tcl Parameter: N4ControlUpfLocNumTai_1
Tcl Parameter: N4ControlUpfLocMcc_1_1
Tcl Parameter: N4ControlUpfLocMnc_1_1
Tcl Parameter: N4ControlUpfLocTac_1_1
Manual Configuration:
At the top of the UPF Selection panel, there's a tabbed pane for DNN's that follows the number of DNNS set by NAS-5G|SM/Number of Data Networks Names. At the top of each DNN tab, there's a table that starts out with a default UPF entry, named "UPF-<dnn#>. This table is used to select UPF's in order to display their settings panels individually, because the topology is going to evolve into a complex tree-like data structure. Each DNN's routing begins with the default UPF and can be modified by the addition of rules.
For each DNN, the maximum number of UPFs is equal to the Network Devices setting for the UPF N4 Node's "Number of SUTs". Each UPF (within a DNN) must be assigned a unique SUT Index. The SUT Index combo box displays the maximum number possible, but the invalid range (based on "Number of SUTs") is greyed out. The table at the top of the DNN tab displays the Name and SUT Index for each UPF as a quick reference.
UPF-<dnn>. e.g. UPF-2, UPF-8
DNN based QoS information is available on NAS-5G|SM tab. Each incoming PDU Session Establishment Request will pick up a set of pre-configured QoS information based on a search of DNN names. This feature allows you to pre-configure UPF routing information on N4|PFCP tab in a similar fashion.
Please note the UPF routing information applies on Single PDU Session basis. For a single PDU session, a UPF can serve as an intermediate UPF (I-UPF), a PDU Session Anchor (PSA) which directly connects to the data network (DN), or both. An I-UPF can be a simple I-UPF, an uplink classifier (ULCL) or a branching point (BP). A simple I-UPF relays all uplink and downlink traffic transparently. A ULCL diverts uplink traffic towards different PSAs based on different uplink rules such as the destination IP addresses. A BP diverts uplink traffic towards different PSAs based on different source IP addresses with IPv6 multi-homing. Therefore BP is only possible for PDU sessions with IPv6 or IPv4v6 PDU type. On the downlink side, a ULCL or BP merges all traffic from different PSAs towards the UE.
During run time, QoS information defined on NAS-5G|SM tab will be populated onto PSAs while routing rules defined for I-UPF on N4|PFCP tab will be populated onto I-UPFs.
Some scenarios that are currently supported:
1. Single DNN access point with no I-UPF. In this case there is only one UPF serving as the PSA. This is the same situation we supported before this feature except that you can define a SUT index based on DNN name.
2. Single DNN access point with a simple I-UPF. For simplicity's sake, simple I-UPF is also categorized as a special ULCL. To configure a simple I-UPF, you can add an uplink rule with no filters or with a matchall filter. The downlink rule for ULCL is automatically no filter (i.e. matchall).
3. Multiple DNN access points with an I-UPF serving as ULCL. The I-UPF itself is not a PSA. Normally, a ULCL diverts uplink traffic based on the destination IP addresses (i.e. Remote Address). But I have made it flexible so that you can define uplink rules with any combination of filters.
4. Multiple DNN access points with an I-UPF serving as ULCL and PSA. This scenario is same as 3 except the I-UPF also has local access to the same DN.
|
UPF SUT Index
|
Select the UPF SUT Index. The number of UPF SUT Index is equal to the Network Devices setting for the UPF N4 Node's "Number of SUTs".
Tcl Parameter: N4ControlUpfSutIndex_1
|
|
PDU Session Anchor
|
Select PDU Session Anchor (PSA) which directly connects to the data network (DN),
Tcl Parameter: N4ControlUpfPduSessAnchorEn_1
|
|
Intermediate UPF
|
An I-UPF can be a simple I-UPF, an uplink classifier (ULCL) or a branching point (BP). A simple I-UPF relays all uplink and downlink traffic transparently. A ULCL diverts uplink traffic towards different PSAs based on different uplink rules such as the destination IP addresses. A BP diverts uplink traffic towards different PSAs based on different source IP addresses with IPv6 multi-homing. Therefore BP is only possible for PDU sessions with IPv6 or IPv4v6 PDU type. On the downlink side, a ULCL or BP merges all traffic from different PSAs towards the UE.
Select Intermediate Type, Uplink Classifier or Branching Point.
When enabled, the Uplink Classifier pane becomes available for input.
Tcl Parameter: N4ControlUpfIntermediateEn_1
Tcl Parameter: N4ControlUpfIntermediateType_1
|
|
Uplink Classifier
|
Enter number of Uplink Rules.
Tcl Parameter: N4ControlUpfUplinkNumRules_1
|
|
Precedence
|
Enter Precedence.
Range: 0 to 255
Default: 255
Tcl Parameter: N4ControlUpfUplinkPreced_1_1
|
|
Number of Filters
|
Enter Number of Filters.
Range: 0 to 15
Default: 1
Tcl Parameter: N4ControlUpfUplinkNumFilters_1_1
|
|
Direction
|
Select Direction. Default: Uplink
Tcl Parameter: N4ControlUpfUplinkDirection_1_1_1
|
|
Match-all
|
Select for all remaining to match all parameters.
Tcl Parameter: N4ControlUpfUplinkMatchallEn_1_1_1
|
|
Protocol Number
|
Select to enter Protocol Number.
Range: 0 to 255
Tcl Parameter: N4ControlUpfUplinkProtoNumEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkProtoNum_1_1_1
|
|
Security Parameter Index
|
Select to enter Security Parameter Index.
Range: 0 to 255
Tcl Parameter: N4ControlUpfUplinkSpiEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkSpi_1_1_1
|
|
Starting Local Port
|
Select to enter the Starting Local Port.
Range: 0 to 65535
Tcl Parameter: N4ControlUpfUplinkStartLocalPortEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkStartLocalPort_1_1_1
|
|
Ending Local Port
|
Select to enter the Ending Local Port.
Range: 0 to 65535
Tcl Parameter: N4ControlUpfUplinkEndLocalPortEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkEndLocalPort_1_1_1
|
|
Remote Address
|
Select to enter a Remote Address.
Enter a valid IPv4 or IPv6 address.
Tcl Parameter: N4ControlUpfUplinkRemoteAddrEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkRemoteAddr_1_1_1
|
|
Type of Service
|
Select to enter Type of Service. When enabled, Enter the Mask.
Range: 0 to 255
Default : 0
Tcl Parameter: N4ControlUpfUplinkTosEn_1_1_1 Tcl Parameter: N4ControlUpfUplinkTos_1_1_1 Tcl Parameter: N4ControlUpfUplinkTosMask_1_1_1
|
|
Starting Remote Port
|
Select to enter the Starting Remote Port.
Range: 0 to 65535
Tcl Parameter: N4ControlUpfUplinkStartRemotePortEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkStartRemotePort_1_1_1
|
|
Ending Remote Port
|
Select to enter the Ending Remote Port.
Range: 0 to 65535
Tcl Parameter: N4ControlUpfUplinkEndRemotePortEn_1_1_1
Tcl Parameter: N4ControlUpfUplinkEndRemotePort_1_1_1
|
|
Flow Label
|
Select to enter the Flow label.
"For "flow label type", the descriptor component value field shall be encoded as three octets which specify the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label." - Per 3GPP TS 24.526 Version 15.0.0
Range: 0 to 1048575
Default: 0
Tcl Parameter: N4ControlUpfUplinkFlowLabelEn_1_1_1 Tcl Parameter: N4ControlUpfUplinkFlowLabel_1_1_1
|
|
Downlink Rules
Precedence
|
Enter Precedence.
Range: 0 to 255
Default: 255
Tcl Parameter: N4ControlUpfDownlinkPreced_1_1
|
DNAI - DN (Data Network) Access Identifiers
When N7 Interface and Traffic Steering are enabled in the SMF Node Test case and DNAI DN (Data Network) Access Identifiers are added to the NAS 5G SM tab, the data fields below become available for input. When the "DNAI " table on the NAS 5g SM tab is populated with DNAI names, for each DNAI, there is a sub-tab for each DNN under the N4 tab. Each DNAI tab can be configured with one PSA or one ULCL + one PSA. The purpose of this tab is to configure uplink traffic path for the DNAI. For example, if a DNAI is configured with ULCL 4 + PSA 2, then the uplink data traffic towards this DNAI will be routed through ULCL 4 and PSA 2.
Enter the DNAI and the SUT Index.
UPF
|
UPF SUT Index
|
Select the UPF SUT Index. The number of UPF SUT Index is equal to the Network Devices setting for the UPF N4 Node's "Number of SUTs".
Tcl Parameter: N4ControlDnaiUpfSutIndex_1
|
|
PDU Session Anchor
|
Select PDU Session Anchor (PSA) which directly connects to the data network (DN),
Tcl Parameter: N4ControlDnaiUpfPduSessAnchorEn_1
|
|
Intermediate UPF
|
An I-UPF can be a simple I-UPF, an uplink classifier (ULCL) or a branching point (BP). A simple I-UPF relays all uplink and downlink traffic transparently. A ULCL diverts uplink traffic towards different PSAs based on different uplink rules such as the destination IP addresses. A BP diverts uplink traffic towards different PSAs based on different source IP addresses with IPv6 multi-homing. Therefore BP is only possible for PDU sessions with IPv6 or IPv4v6 PDU type. On the downlink side, a ULCL or BP merges all traffic from different PSAs towards the UE.
Select Intermediate Type, Uplink Classifier or Branching Point.
When enabled, the Uplink Classifier pane becomes available for input.
Tcl Parameter: N4ControlDnaiUpfIntermediateEn_1
Tcl Parameter: N4ControlDnaiUpfIntermediateType_1
|
|
Uplink Classifier
|
Enter number of Uplink Rules.
Tcl Parameter: N4ControlDnaiUpfUplinkNumRules_1
|
|
Precedence
|
Enter Precedence.
Range: 0 to 255
Default: 255
Tcl Parameter: N4ControlDnaiUpfUplinkPreced_1_1
|
|
Number of Filters
|
Enter Number of Filters.
Range: 0 to 15
Default: 1
Tcl Parameter: N4ControlDnaiUpfUplinkNumFilters_1_1
|
|
Direction
|
Select Direction. Default: Uplink
Tcl Parameter: N4ControlDnaiUpfUplinkDirection_1_1_1
|
|
Match-all
|
Select for all remaining to match all parameters.
Tcl Parameter: N4ControlDnaiUpfUplinkMatchallEn_1_1_1
|
|
Protocol Number
|
Select to enter Protocol Number.
Range: 0 to 255
Tcl Parameter: N4ControlDnaiUpfUplinkProtoNumEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkProtoNum_1_1_1
|
|
Security Parameter Index
|
Select to enter Security Parameter Index.
Range: 0 to 255
Tcl Parameter: N4ControlDnaiUpfUplinkSpiEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkSpi_1_1_1
|
|
Starting Local Port
|
Select to enter the Starting Local Port.
Range: 0 to 65535
Tcl Parameter: N4ControlDnaiUpfUplinkStartLocalPortEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkStartLocalPort_1_1_1
|
|
Ending Local Port
|
Select to enter the Ending Local Port.
Range: 0 to 65535
Tcl Parameter: N4ControlDnaiUpfUplinkEndLocalPortEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkEndLocalPort_1_1_1
|
|
Remote Address
|
Select to enter a Remote Address.
Enter a valid IPv4 or IPv6 address.
Tcl Parameter: N4ControlDnaiUpfUplinkRemoteAddrEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkRemoteAddr_1_1_1
|
|
Type of Service
|
Select to enter Type of Service. When enabled, Enter the Mask.
Range: 0 to 255
Default : 0
Tcl Parameter: N4ControlDnaiUpfUplinkTosEn_1_1_1 Tcl Parameter: N4ControlUpfUplinkTos_1_1_1 Tcl Parameter: N4ControlDnaiUpfUplinkTosMask_1_1_1
|
|
Starting Remote Port
|
Select to enter the Starting Remote Port.
Range: 0 to 65535
Tcl Parameter: N4ControlDnaiUpfUplinkStartRemotePortEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkStartRemotePort_1_1_1
|
|
Ending Remote Port
|
Select to enter the Ending Remote Port.
Range: 0 to 65535
Tcl Parameter: N4ControlDnaiUpfUplinkEndRemotePortEn_1_1_1
Tcl Parameter: N4ControlDnaiUpfUplinkEndRemotePort_1_1_1
|
|
Flow Label
|
Select to enter the Flow label.
"For "flow label type", the descriptor component value field shall be encoded as three octets which specify the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label." - Per 3GPP TS 24.526 Version 15.0.0
Range: 0 to 1048575
Default: 0
Tcl Parameter: N4ControlDnaiUpfUplinkFlowLabelEn_1_1_1 Tcl Parameter: N4ControlUpfUplinkFlowLabel_1_1_1
|
|
Downlink Rules
Precedence
|
Enter Precedence.
Range: 0 to 255
Default: 255
Tcl Parameter: N4ControlDnaiUpfDownlinkPreced_1_1
|
|
| Lawful Intercept |
Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to UP is selected.
Enable for Lawful Intercept support for CUPS Control nodes. In the Target IMSIs table, define a set of IMSIs to be matched for Lawful Intercept.
Tcl Parameter: SxaControlLiEn
Tcl Parameter: SxbControlLiEn
| Start Time (s) |
For SGW/PGW CP Node, the Start / Stop Time applies to matched IMSI on a per bearer basis. The Start Time represents the delay between bearer establishment and the start of Lawful Intercept (LI). The Stop Time represents the delay between the start of Lawful Intercept (LI) and the stop of Lawful Intercept (LI). A Start Time of 0 means to start Lawful Intercept (LI) immediately after bearer establishment. A Stop Time of 0 means NO Lawful Intercept (LI) stop. Lawful Intercept (LI) will be automatically stopped when bearer enters idle state if it is not already stopped.
Enter the Start Time in seconds.
Range: 0 to 65535
Default : 10
Tcl Parameter: SxaControlLiStartTime
Tcl Parameter: SxbControlLiStartTime
|
| Stop Time (s) |
For SGW/PGW CP Node, the Start / Stop Time applies to matched IMSI on a per bearer basis. The Start Time represents the delay between bearer establishment and the start of Lawful Intercept (LI). The Stop Time represents the delay between the start of Lawful Intercept (LI) and the stop of Lawful Intercept (LI). A Start Time of 0 means to start Lawful Intercept (LI) immediately after bearer establishment. A Stop Time of 0 means NO Lawful Intercept (LI) stop. Lawful Intercept (LI) will be automatically stopped when bearer enters idle state if it is not already stopped.
Enter the Stop Time in seconds.
Range: 0 to 65535
Default : 10
Tcl Parameter: SxaControlLiStopTime
Tcl Parameter: SxbControlLiStopTime
|
|
Starting X3u Peer Teid
|
Enter Starting X3u Peer Teid. Available when Sxa Interface to UP or Sxa+Sxb Interface to UP (SGW Node Test Case) or Sxb Interface (PGW Node Test Case) to UP is selected and Enable Lawful Intercept is enabled.
Range: 0 to 4294967295
Default: 1000
Tcl Parameter: SxaControlX3uPeerTeid
Tcl Parameter: SxbControlX3uPeerTeid
|
| Sx3LIF Node Emulation |
Select to enable Sx3LIF Node Emulation. SX3LIF X3U Node becomes available for input.
If SX3LIF Node Emulation is enabled, a new OM "Lawful Intercept Packets Received" is introduced on the "SX3LIF GTP Node" tab in addition to normal OM counts for a GTP node. This OM will peg all valid Lawful Intercept packets received, i.e. packets with matching Teids that correspond to pre-defined IMSIs.
Tcl Parameter: Sx3lifNodeAddr
Tcl Parameter: SxaControlSx3lifEn
Tcl Parameter: SxbControlSx3lifEn
|
| Sx3LIF X3U Address |
Available when Sx3LIF Node Emulation is not enabled. Enter a valid IPv4 or IPv6 Address for Sx3LIF X3U node.
Tcl Parameter: SxaControlSx3lifNodeAddr
Tcl Parameter: SxbControlSx3lifNodeAddr
|
| Target IMSIs |
In the Target IMSIs table, you can define a set of IMSIs to be matched for LawfuI Intercept (LI). LI will apply to all active bearers with matched IMSI and to both uplink and downlink traffic. For SGW/PGW CP Node, eleven ( 11) X3u Peer Teids are reserved for each IMSI. Each bearer with matched IMSI will pick up the next available Teid when it exits idle state during run time.
Enter a Starting IMSI, Count and Increment. Each segment should be a 15 digit IMSI or a 15 digit IMSI in auto increment format #(imsi Count / Increment).
Default : 505024101215074 (Starting IMSI), 2 (Count), 1 (Increment)
Tcl Parameter: SxaControlLiImsiStr
Tcl Parameter: SxbControlLiImsiStr
|
|
| Usage Report Parameters |
Select to Enable Usage Reporting Rules for CUPS. Available in PGW and SGW Node Test cases when PFCP Version >= 14.5.0 and when "Sx<x> Interface to UP" is enabled. Also available in UPF Nodal, AMF Node (with SMF Simulation) and SMF Node test cases.
Per 3GPP TS 29.244 version 14.1.0 Section 5.2.2 Usage Reporting.
Reference is 3GPP TS 29.244 7.5.8 PFCP Session Report Request for N4.
Enter Number of Usage Report Rules.
Range : 1 to 10
Default: 1
Tcl Parameter: N4ControlUsageRptRulesEn
Tcl Parameter: SxaControlUsageRptRulesEn
Tcl Parameter: SxbControlUsageRptRulesEn
Tcl Parameter: N4ControlNumUsageRptRules
Tcl Parameter: SxaControlNumUsageRptRules
Tcl Parameter: SxbControlNumUsageRptRules
| Rule Name |
Enter Usage Reporting Rule Name.
Range: up to 63 Characters
Default : KeyName_1
Tcl Parameter: N4ControlRuleName_1
Tcl Parameter: SxaControlRuleName_1
Tcl Parameter: SxbControlRuleName_1
|
| Measurement Method |
Select the Measurement Method. Must select at least one or up to all three.
Options: Duration , Volume , Event
Tcl Parameter: N4ControlUsageRptDurationEn_1
Tcl Parameter: SxaControlUsageRptDurationEn_1
Tcl Parameter: SxbControlUsageRptDurationEn_1
Tcl Parameter: N4ControlUsageRptVolumeEn_1
Tcl Parameter: SxaControlUsageRptVolumeEn_1
Tcl Parameter: SxbControlUsageRptVolumeEn_1
Tcl Parameter: N4ControlUsageRptEventEn_1
Tcl Parameter: SxaControlUsageRptEventEn_1
Tcl Parameter: SxbControlUsageRptEventEn_1
|
|
Reporting Triggers
|
Select a Reporting Trigger. Must select at least one. You can select all triggers.
| Periodic |
Select for Periodic reporting trigger. Must enter a Measurement Period in Seconds.
Tcl Parameter: N4ControlUsageRptTrigPerioEn_1
Tcl Parameter: SxaControlUsageRptTrigPerioEn_1
Tcl Parameter: SxbControlUsageRptTrigPerioEn_1
|
| Volume Threshold |
Select for Volume Threshold reporting trigger. If the Measurement Method is Volume, then the Volume Threshold pane becomes available for input.
Tcl Parameter: N4ControlUsageRptTrigVolthEn_1
Tcl Parameter: SxaControlUsageRptTrigVolthEn_1
Tcl Parameter: SxbControlUsageRptTrigVolthEn_1
|
|
Time Threshold
|
Select for Time Threshold reporting trigger. If the Measurement Method is Duration, the Time Threshold in Seconds field becomes available for input to enter time threshold in seconds.
Tcl Parameter: N4ControlUsageRptTrigTimthEn_1
Tcl Parameter: SxaControlUsageRptTrigTimthEn_1
Tcl Parameter: SxbControlUsageRptTrigTimlthEn_1
|
| Quota Holding Time |
Select for Quota Holding Time reporting trigger. Quota Holding Time (s) becomes available for input to enter quota holding time in seconds.
Tcl Parameter: N4ControlUsageRptTrigQuhtiEn_1
Tcl Parameter: SxaControlUsageRptTrigQuhtiEn_1
Tcl Parameter: SxbControlUsageRptTrigQuhtiEn_1
|
| Start of Traffic |
Select for Start of Traffic reporting trigger.
Tcl Parameter: N4ControlUsageRptTrigStartEn_1
Tcl Parameter: SxaControlUsageRptTrigStartEn_1
Tcl Parameter: SxbControlUsageRptTrigStartEn_1
|
| Stop of Traffic |
Select for Stop of Traffic reporting trigger.
Tcl Parameter: N4ControlUsageRptTrigStopEn_1
Tcl Parameter: SxaControlUsageRptTrigStopEn_1
Tcl Parameter: SxbControlUsageRptTrigStopEn_1
|
| Dropped DL Traffic Threshold |
Select for the Dropped DL Traffic Threshold reporting trigger. If the Measurement Method is Volume, then the Dropped DL Threshold pane becomes available for input.
Tcl Parameter: N4ControlUsageRptTrigDrothEn_1
Tcl Parameter: SxaControlUsageRptTrigDrothEn_1
Tcl Parameter: SxbControlUsageRptTrigDrothEn_1
|
| Linked Usage |
Select for Linked Usage reporting trigger.
Tcl Parameter: N4ControlUsageRptTrigLiusaEn_1
Tcl Parameter: SxaControlUsageRptTrigLiusaEn_1
Tcl Parameter: SxbControlUsageRptTrigLiusaEn_1
|
| Volume Quota |
Select for Volume Quota reporting trigger. f the Measurement Method is Volume, then the Volume Quota pane becomes available for input.
Tcl Parameter: N4ControlUsageRptTrigVolquEn_1
Tcl Parameter: SxaControlUsageRptTrigVolquEn_1
Tcl Parameter: SxbControlUsageRptTrigVolquEn_1
|
| Time Quota |
Select for Time quota reporting trigger. If the Measurement Method is Duration, the Time Quota in Seconds field becomes available for input to enter time quota time in seconds.
Tcl Parameter: N4ControlUsageRptTrigTimquEn_1
Tcl Parameter: SxaControlUsageRptTrigTimquEn_1
Tcl Parameter: SxbControlUsageRptTrigTimquEn_1
|
| Envelope Closure |
Select for Envelope Closure reporting trigger.
Tcl Parameter: N4ControlUsageRptTrigEnvclEn_1
Tcl Parameter: SxaControlUsageRptTrigEnvclEn_1
Tcl Parameter: SxbControlUsageRptTrigEnvclEn_1
|
| Event Threshold |
Select for Event Threshold reporting trigger.
Tcl Parameter: N4ControlUsageRptTrigEvethEn_1
Tcl Parameter: SxaControlUsageRptTrigEvethEn_1
Tcl Parameter: SxbControlUsageRptTrigEvethEn_1
|
| MACAR |
Select for MACAR (MAC Addresses Reporting) reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigMacarEn_1
|
| Event Quota |
Select for Event Quota reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigEvequEn_1
|
| IPMJL |
Select for IPMJL (IP Multicast Join/Leave) reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigIpmjlEn_1
|
| QUVTI |
Select for QUVTO (Quota Validity Time) reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigQuvtiEn_1
|
| REEMR |
Select for REEMR (Report the End Marker Reception) reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigReemeEn_1
|
| UPINT |
Select for UPINT (User Plane Inactivity Timer) reporting trigger. Available when PFCP Version >= 17.9.0/Jun2023.
Spec 29.244 (17.9.0) 8.2.19
Tcl Parameter: N4ControlUsageRptTrigUpintEn_1
|
|
| Measurement Period (s) |
Enter the Measurement Period in seconds. Becomes available when Periodic Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptMeasPeriod_1
Tcl Parameter: SxaControlUsageRptMeasPeriod_1
Tcl Parameter: SxbControlUsageRptMeasPeriod_1
|
| Time Threshold (s) |
Enter the Time Threshold in seconds. Becomes available when Measurement Method is Duration and / or Time Threshold Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptTimth_1
Tcl Parameter: SxaControlUsageRptTimth_1
Tcl Parameter: SxbControlUsageRptTimth_1
|
| Time Quota (s) |
Enter the Time quota in seconds. Becomes available when Measurement Method is Duration and / or Time Quota Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptTimqu_1
Tcl Parameter: SxaControlUsageRptTimqu_1
Tcl Parameter: SxbControlUsageRptTimqu_1
|
| Quota Holding Time (s) |
Enter the Quota Holding Time in seconds. Becomes available and Quota Holding Time Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptQuhti_1
Tcl Parameter: SxaControlUsageRptQuhti_1
Tcl Parameter: SxbControlUsageRptQuhti_1
|
| Volume Threshold |
Enter the Volume Threshold - Total (bytes), Uplink (bytes) and Downlink (bytes). Becomes available when Measurement Method is Volume and Volume Threshold Reporting Trigger is selected.
Range: 0 to 18446744073709551615
Default: 1000000
Tcl Parameter: N4ControlUsageRptVolThTot_1
Tcl Parameter: SxaControlUsageRptVolThTot_1
Tcl Parameter: SxbControlUsageRptVolThTot_1
Tcl Parameter: N4ControlUsageRptVolthUl_1
Tcl Parameter: SxaControlUsageRptVolthUl_1
Tcl Parameter: SxbControlUsageRptVolthUl_1
Tcl Parameter: N4ControlUsageRptVolthDl_1
Tcl Parameter: SxaControlUsageRptVolthDl_1
Tcl Parameter: SxbControlUsageRptVolthDl_1
|
| Volume Quota |
Enter the Volume Quota - Total (bytes), Uplink (bytes) and Downlink (bytes). Becomes available when Measurement Method is Volume and/or Volume Quota Reporting Trigger is selected.
Range: 0 to 18446744073709551615
Default: 1000000
Tcl Parameter: N4ControlUsageRptVolquTot_1
Tcl Parameter: SxaControlUsageRptVolquTot_1
Tcl Parameter: SxbControlUsageRptVolquTot_1
Tcl Parameter: N4ControlUsageRptVolquUl_1
Tcl Parameter: SxaControlUsageRptVolquUl_1
Tcl Parameter: SxbControlUsageRptVolquUl_1
Tcl Parameter: N4ControlUsageRptVolquDl_1
Tcl Parameter: SxaControlUsageRptVolquDl_1
Tcl Parameter: SxbControlUsageRptVolquDl_1
|
| Dropped DL Threshold |
Enter the Dropped DL Threshold - DL Packets, DL (bytes). Becomes available when Measurement Method is Volume and Dropped DL Traffic Threshold Reporting Trigger is selected.
Range: 0 to 18446744073709551615
Default: 1000000
Tcl Parameter: N4ControlUsageRptDrothBytes_1
Tcl Parameter: SxaControlUsageRptDrothBytes_1
Tcl Parameter: SxbControlUsageRptDrothBytes_1
Tcl Parameter: N4ControlUsageRptDrothPkts_1
Tcl Parameter: SxaControlUsageRptDrothPkts_1
Tcl Parameter: SxbControlUsageRptDrothPkts_1
|
| Time Quota Mechanism |
Select to enter the Time Quota Mechanism (Base Time Interval Type and Base Time Interval (s)). Becomes available when Measurement Method is Duration and Time Quota Reporting Trigger is selected.
Select Base Time Interval Type. Options : CTP or DTP
Enter Base Time Interval in seconds.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptTimeQuMechEn_1
Tcl Parameter: SxaControlUsageRptTimeQuMechEn_1
Tcl Parameter: SxbControlUsageRptTimeQuMechEn_1
Tcl Parameter: N4ControlUsageRptBaTimeInType_1
Tcl Parameter: SxaControlUsageRptBaTimeInType_1
Tcl Parameter: SxbControlUsageRptBaTimeInType_1
Tcl Parameter: N4ControlUsageRptBaTimeInterval_1
Tcl Parameter: SxaControlUsageRptBaTimeInterval_1
Tcl Parameter: SxbControlUsageRptBaTimeInterval_1
|
| Monitoring Time |
Select to enable Monitor Time IE and the Subsequent IEs associated with the Monitoring Time IE. Available for all Measurement Methods. Enter Monitoring Time in seconds in UTC format.
Tcl Parameter: N4ControlUsageRptMoniTimeEn_1
Tcl Parameter: SxaControlUsageRptMoniTimeEn_1
Tcl Parameter: SxbControlUsageRptMoniTimeEn_1
Tcl Parameter: N4ControlUsageRptMoniTime_1
Tcl Parameter: SxaControlUsageRptMoniTime_1
Tcl Parameter: SxbControlUsageRptMoniTime_1
| Subsequent Volume Threshold |
Enter the Subsequent Volume Threshold - Total (bytes), Uplink (bytes) and Downlink (bytes). Becomes available when Measurement Method is Volume and Volume Threshold Reporting Trigger is selected.
Range: 0 to 18446744073709551615
Default: 1000000
Tcl Parameter: N4ControlUsageRptSuVolThTot_1
Tcl Parameter: SxaControlUsageRptSuVolThTot_1
Tcl Parameter: SxbControlUsageRptSuVolThTot_1
Tcl Parameter: N4ControlUsageRptSuVolthUl_1
Tcl Parameter: SxaControlUsageRptSuVolthUl_1
Tcl Parameter: SxbControlUsageRptSuVolthUl_1
Tcl Parameter: N4ControlUsageRptSuVolthDl_1
Tcl Parameter: SxaControlUsageRptSuVolthDl_1
Tcl Parameter: SxbControlUsageRptSuVolthDl_1
|
| Subsequent Volume Quota |
Enter the Subsequent Volume Quota - Total (bytes), Uplink (bytes) and Downlink (bytes). Becomes available when Measurement Method is Volume and Volume Quota Reporting Trigger is selected.
Range: 0 to 18446744073709551615
Default: 1000000
Tcl Parameter: N4ControlUsageRptSuVolquTot_1
Tcl Parameter: SxaControlUsageRptSuVolquTot_1
Tcl Parameter: SxbControlUsageRptSuVolquTot_1
Tcl Parameter: N4ControlUsageRptSuVolquUl_1
Tcl Parameter: SxaControlUsageRptSuVolquUl_1
Tcl Parameter: SxbControlUsageRptSuVolquUl_1
Tcl Parameter: N4ControlUsageRptSuVolquDl_1
Tcl Parameter: SxaControlUsageRptSuVolquDl_1
Tcl Parameter: SxbControlUsageRptSuVolquDl_1
|
| Subsequent Time Threshold (s) |
Enter the Subsequent Time Threshold in seconds. Becomes available when Measurement Method is Duration and Time Threshold Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptSubTimeTh_1
Tcl Parameter: SxaControlUsageRptSubTimeTh_1
Tcl Parameter: SxbControlUsageRptSubTimeTh_1
|
| Subsequent Time Quota (s) |
Enter the Time quota in seconds. Becomes available when Measurement Method is Duration and Time Quota Reporting Trigger is selected.
Range: 0 to 4294967295
Default: 0
Tcl Parameter: N4ControlUsageRptTimeQu_1
Tcl Parameter: SxaControlUsageRptTimeQu_1
Tcl Parameter: SxbControlUsageRptTimeQu_1
|
|
| Bearer Rule Assignments |
Select to Assign Rules to Bearers. Available when Enable Usage Report Rules is enabled,Default Bearers per Session = 1 or GTPv2 Bearer Quality of Service is in Per Bearer mode.
Select to Include Network Instance. Available on SGW Node test case when PGW Node Emulation is disabled and when Default Bearers per Session = 1 or GTPv2 Bearer Quality of Service is in Per Bearer mode.
A table of Bearer, Rule and Network Uplink/Downlink (Only when Include Network Instance is enabled) (up to 10) become available for input.
Tcl Parameter: SxaControlUsageRptAssignPerBearerEn
Tcl Parameter: SxbControlUsageRptAssignPerBearerEn
Tcl Parameter: SxaControlUsageRptAssignBearer_1
Tcl Parameter: SxbControlUsageRptAssignBearer_1
Tcl Parameter: SxaControlBearerLevelNwInstEn_1
Tcl Parameter: SxbControlBearerLevelNwInstUplink_1
Tcl Parameter: SxbControlBearerLevelNwInstDownlink_1
|
| Support Predefined URR IDs in UP |
Select to enable the handling of the session report request with predefined URR Id id from UPF.
When enabled, UPF Nodal will trigger URR update procedure to create URR and update URR of the predefined urr id included the session report request message from UPF.
The URR update procedure to create URR will be triggered when Session Report Request from UPF includes predefined urr id and START (Start of Traffic) of Usage Report Trigger is set.
The URR update procedure to update URR will be triggered when Session Report Request from UPF includes predefined urr id and LIUSA (Linked Usage Reporting) and/or VOLTH (Volume Threshold) of Usage Report Trigger are set.
Available in UPF Nodal test case when Enable Usage Report Rules is selected and Number of Usage Report Rules is 2 or more.
Enter the Number of Predefined URR Ids - Range : 1 to 500, default : 1. Number of Predefined URR Ids which each PDU can handle. For example, when this value is 1, if an PDU session receives Session Report Request of 2nd predefined URR id from UPF after receiving Session Report Request of 1st predefined URR Id, UPF Nodal will just send Session Report Response (Accept) but won’t trigger URR update procedure to create URR for 2nd predefined URR Id.
Note : If the single session report request message includes the several usage report IEs (more than 20 predefined URR Ids), it will require the jumbo message buffer. Thus, when you configure "Number of Predefined URR IDs" with more than 20, this test may experience the jumbo buffer exhaustion if a lot of messages are generated almost simultaneously. If it happens, please set "Traffic Start" to "When Session Established" and then retry it.
If it still happens, please decrease the total # of PDUs. In the system, the resource of Jumbo Message Buffer is very limited. So, for the stable test, we recommend 1000 PDUs configuration when you configure "Number of predefined URR IDs" with more than 20.
Select the Usage Report Rule for Predefined URR Ids - Range : 1 to 10, default : 2. Usage Report Rule which will used to Create URR/Update URR for predefined URR Ids.
Tcl Parameter: N4ControlPredefUrrIdsInUpEn
Tcl Parameter: N4ControlNumPredefUrrIds
Tcl Parameter: N4ControlPredefUrrIdUsageRptRule
|
|
| SDF Level Rule Assignments |
Available when Dedicated Bearers per Default > = 1.
| SDF Level QOS |
Available on SGW Node TC when Sxa+Sxb Interface to UP is enabled and PGW Node Emulation is enabled. Available on PGW Node when Sxb Interface to UP is enabled. If checked, the remaining fields in SDF Level Rule Assignments panel (Service Data Flow) becomes available to capture.
Options: On, Off (default)
Tcl Parameter: SxaControlUsageRptSdfLevelQosEn
Tcl Parameter: SxbControlUsageRptSdfLevelQosEn
|
| SDF Usage Report Rule |
Available when PFCP Version >= 14.5.0 and Enable Usage Report Rules is enabled and Assign Rules to Bearers is not enabled. Select SDF Usage Report Rule.
Tcl Parameter: SxaControlUsageRptSdfUrrEn
Tcl Parameter: SxbControlUsageRptSdfUrrEn
|
| Support SDF for Default Bearers |
Select for SDF support for default bearers.
Tcl Parameter: SxaControlUsageRptSdfDefaultBearer
Tcl Parameter: SxbControlUsageRptSdfDefaultBearer
|
| Number of SDFs |
Number of SDFs (Service Data Flows):
Range: 1 - 15
Tcl Parameter: SxaControlNumSdfs1
Tcl Parameter: SxbControlNumSdfs1
|
| Precedence |
Enter the Precedence.
Range: 1 - 4294967295
Tcl Parameter: SxaControlSdfPrecedence_1_1
Tcl Parameter: SxbControlSdfPrecedence_1_1
|
| Maximum Bit Rates Guaranteed Bit Rates Gate Status |
Define the IP flow Maximum Bit Rates and Guaranteed Bit Rates for UL and DL traffic and the Gates status of the Uplink/Downlink (on/off).
Range: 0 - 10000000000
Default: 1
Tcl Parameters :
| SxaControlSdfMaxUplink_1_1 |
SxaControlSdfMaxDownlink_1_1 |
SxaControlSdfGuaranteedUplink_1_1 |
| SxaControlSdfGuaranteedDownlink_1_1 |
SxaControlSdfGateStatusUplink_1_1 |
SxaControlSdfGateStatusDownlink_1_1 |
| SxbControlSdfMaxUplink_1_1 |
SxbControlSdfMaxDownlink_1_1 |
SxbControlSdfGuaranteedUplink_1_1 |
| SxbControlSdfGuaranteedDownlink_1_1 |
SxbControlSdfGateStatusUplink_1_1 |
SxbControlSdfGateStatusDownlink_1_1 |
|
| Application ID |
Select to include Application ID IE in PDI of Create PDR for Sxb and Sxa+Sxb, and to include Network Instance IE in PDI of Create PDR for Sxa. Enter up to 128 characters.
Available in PGW Node when Sxb interface to UP enabled and in SGW Node with PGW Node Emulation, and Sxa+Sxb Interface to UP enabled.
Limitation : This feature only provides a way in GUI to allow users to configure the Network Instance and Application ID in control plane as needed. There is no change in user plane which means no handling for the newly added Network Instance or Application ID IE.
Tcl Parameter: SxaControlSdfAppIdEn_1_1
Tcl Parameter: SxaControlSdfAppId_1_1
Tcl Parameter: SxbControlSdfAppIdEn_1_1
Tcl Parameter: SxbControlSdfAppId_1_1
|
| Activate Predefined Rule |
Select to include the Activate Predefined Rule IE in the PFCP Session Establishment Request message.
Activate Predefined Rules is a conditional IE in Create PDR IE within PFCP Session Establishment Request.
Available in PGW Node when Sxb interface to UP enabled and in SGW Node with PGW Node Emulation, and Sxa+Sxb Interface to UP enabled.
Limitation : This feature only provides a way in GUI to allow users to config the Activate Predefined Rule in control plane as needed. There is no change in user plane which means no handling for the newly added Activated Predefined Rules IE.
Enter a Printable-String REGEX that allows 1 to 128 characters.
Tcl Parameter: SxaControlSdfActPredefinedRuleEn_1_1
Tcl Parameter: SxaControlSdfActPredefinedRule_1_1
Tcl Parameter: SxbControlSdfActPredefinedRuleEn_1_1
Tcl Parameter: SxbControlSdfActPredefinedRule_1_1
|
| Network Instance |
Select to include the Network Instance IE under Create PDR, PDI IE.
Available in PGW Node when Sxb interface to UP enabled and in SGW Node with PGW Node Emulation, and Sxa+Sxb Interface to UP enabled.
Limitation : This feature only provides a way in GUI to allow users to config the Network Instance in control plane as needed. There is no change in user plane which means no handling for the newly added Network Instance IE.
Enter a Printable-String REGEX that allows 1 to 128 characters in Uplink and Downlink.
Tcl Parameter: SxaControlSdfNwInstEn_1_1
Tcl Parameter: SxaControlSdfNwInstUplink_1_1
Tcl Parameter: SxaControlSdfNwInstDownlink_1_1
Tcl Parameter: SxbControlSdfNwInstEn_1_1
Tcl Parameter: SxbControlSdfNwInstUplink_1_1
Tcl Parameter: SxbControlSdfNwInstDownlink_1_1
|
| SDF URR Rule Assignment |
Available when SDF Usage Report Rule is enabled and Assign Rules to Bearers is not enabled. Select the Rule.
Range: 1 - 10
Default: 1
Tcl Parameter: SxaControlSdfRule_1_1
Tcl Parameter: SxbControlSdfRule_1_1
|
|
| Custom Messages |
You can customize Landslide generated messages and or compose your proprietary messages to perform negative testing with invalid values or malformed messages or to add proprietary information. The Custom Message checkbox is available in PGW and SGW Node Test Cases for PFCP with appropriate License.
The Custom Message checkbox is available in SMF Nodal and and SMF Node, UPF Nodal and and UPF Node Test Cases for 5G PFCP with appropriate License.
Select the Custom Messages Checkbox, which makes available the New and Open buttons.
-
New: Click New to display the Message Editor window. See Message Editor for details of entering a new message.
-
Open: Click Open to display the Select Message Editor window. Select the library in which the message exists, select the message you wish to edit and then click the Edit button to display the Message Editor Window. See Message Editor for details of editing existing messages.
Tcl Parameter: PfcpCustomMsgEn
Tcl Parameter: PfcpCustomMsg
|