diff --git a/Resources/ReleaseNotes/Open RAN SIM CE 3.0/Release-Notes-ORAN-SIM-CE-3.0.html b/Resources/ReleaseNotes/Open RAN SIM CE 3.0/Release-Notes-ORAN-SIM-CE-3.0.html
new file mode 100644
index 0000000..f57e302
--- /dev/null
+++ b/Resources/ReleaseNotes/Open RAN SIM CE 3.0/Release-Notes-ORAN-SIM-CE-3.0.html	
@@ -0,0 +1,930 @@
+<HTML>
+<TITLE>
+    Keysight Open RAN Simulators, Cloud Edition 3.0 - Software Release Notes : Build Number: 4.4.0-4310-569 (August 2024)
+</TITLE>
+<STYLE>
+    body {
+        font-family: Calibri, Serif;
+        padding-left: 40px;
+    }
+
+    table {
+        border-collapse: collapse;
+        margin: 12pt 0 18pt;
+    }
+
+    table th {
+        background-color: #badce6;
+    }
+
+    table,
+    td,
+    th {
+        border: 1px solid #bebebe;
+        padding: 1.5pt 2.5pt 2.5pt;
+    }
+
+    pre {
+        font-family: Calibri, Serif;
+    }
+
+    .knownIssuesListCssClass th {
+        background-color: #cfd4d8;
+        color: #000;
+    }
+
+    .whatsNewNoteCssClass th {
+        background-color: #37b0c9;
+        color: #fff;
+        padding: 4pt;
+    }
+
+    .whatsNewNoteCssClass td {
+        padding: 3pt;
+    }
+
+    .resolvedDefectsListCssClass th {
+        background-color: #81ab5d;
+        color: #fff;
+    }
+
+    .whatsNewNoteCssClass table {
+        width: 50%;
+    }
+
+    .resolvedDefectsListCssClass table {
+        width: 50%;
+    }
+
+    .knownIssuesListCssClass table {
+        width: 50%;
+    }
+
+    .knownIssuesListCssClass tt {
+        font-family: Calibri, Serif;
+    }
+
+    .whatsNewNoteCssClass tt {
+        font-family: Calibri, Serif;
+    }
+
+    .resolvedDefectsListCssClass tt {
+        font-family: Calibri, Serif;
+    }
+
+    .outerTable {
+        border: none;
+    }
+
+    .outerTable td {
+        border-bottom: none;
+        border-left: none;
+        border-right: none;
+        border-top: none;
+    }
+
+    .innerTable td {
+        border: 1px solid #bebebe;
+    }
+</STYLE>
+
+<BODY>
+    <CENTER>
+        <H1>
+		Keysight Open RAN Simulators, Cloud Edition 3.0 - Software Release Notes
+            <BR>
+            Build Number: 4.4.0-4310-569 (August 2024)
+        </H1>
+    </CENTER>
+
+    <UL>
+        <LI><A HREF="#About This Release">About This Release</A></LI>
+        <LI><A HREF="#What's New in This Release">What's New in This Release</A></LI>
+        <LI><A HREF="#Supported platforms">Supported platforms</A></LI>
+        <LI><A HREF="#Fixed in This Release">Fixed in This Release</A></LI>
+        <LI><A HREF="#Installation Notes">Installation Notes</A></LI>
+        <LI><A HREF="#Additional Documentation">Additional Documentation</A></LI>
+        <LI><A HREF="#Known Limitations">Known Limitations</A></LI>
+    </UL>
+    <BR>
+
+    <HR>
+    <H2><A NAME="About This Release">About This Release</A></H2>
+ORAN SIM CE 3.0 introduces new testing capabilties in the O-RAN space with the new RUSIM topology. It also brings significant enhancements across multiple components, including CoreSim, DUSim, LoadCore, CUSim, user plane, and infrastructure. CoreSim now supports Paging Storm for UEs, UE Trace, and multiple WiFi enhancements. DUSim adds new F1AP procedures and improves user plane performance. LoadCore integrates edge computing features, mutual TLS, and enhanced routing. CUSim supports stateless UDP traffic and enhanced licensing. User plane updates include security attack support, SIP, REST API, FTPS, and IMS enhancements.
+	<BR>
+
+
+    <BR><BR>
+
+    <HR>
+    <H2><A NAME="What's New in This Release">What's New in This Release</A></H2>
+    <div class="whatsNewNoteCssClass">
+
+
+        <H3>RUSim</H3>
+        <UL>
+		    <LI>New topology that simulates from a single session the RU ORAN node together with the 5G Core</LI>
+            <LI>Multiple UE support</LI>
+            <LI>Multiple DNN support</LI>
+            <LI>Support for parallel commands</LI>
+            <LI>Support for scenario definition</LI>
+            <LI>Support for advanced mobility management</LI>
+            <LI>Support for application traffic: 
+                <UL>
+                    <LI>Data</LI>
+                    <LI>Stateless UDP</LI>
+                    <LI>ngUDG</LI>
+                    <LI>Video</LI>
+                    <LI>Voice</LI>
+                </UL>
+            </LI>
+<br>
+    Note: The RUSim agent requires 24.0 Linux release (UeSIM-v24.0-122-LNX) and a traffic engine upgrade. Check RUSim deployment guide for more details.
+          
+        </UL>
+		
+		<H3>CoreSim</H3>
+        <UL>
+            <LI bugid="">The maximum test duration is now set to 120 hours</LI>
+            <LI bugid="">Paging Storm support for a group of UEs</LI>
+		    <LI bugid="">UE Trace support (as IE in Initial Context Setup or as standalone UE Trace message)</LI>
+		    <LI bugid="">5G CoreNetwork Assistance Information IE for Inactive</LI>
+		    <LI bugid="">5G Location Reporting</LI>
+		    <LI bugid="">4G Periodic TAU</LI>
+            <LI bugid="LOADCORE-3665">Identity procedure is initiated in case TMSI is unknown</LI>
+			<LI bugid="">Untrusted WiFi: Userplane support</LI>
+			<LI bugid="">Untrusted WiFi: Dedicated QoS flow support (both UE and Network Initiated)</LI>
+			<LI bugid="">Untrusted WiFi: NAT-T support</LI>
+			<LI bugid="">Untrusted WiFi: Support for Create/Delete PDU Session and Create/Delete QoS Flows secondary oobjectives</LI>
+			<LI>New fields for Public Warning System: Popup, Emergency User Alert, Data Coding Scheme, Warning Message Contents</LI>
+			<LI bugid="">Paging throttling option added for the case where paging is triggered by passthrough downlink traffic</LI>
+            <LI>Trigger Paging based on localy generated downlink traffic </LI>
+        </UL>
+
+        <H3>DUSim</H3>
+        <UL>	
+			<LI bugid="DUSIMA-193">F1AP DU initiated UE Context Modification Procedure</LI>
+			<LI bugid="DUSIMA-209">F1AP RRC Delivery Report Procedure</LI>
+			<LI bugid="DUSIMA-210">F1AP UE Inactivity Notification Procedure</LI>
+			<LI bugid="">F1AP PWS Failure and Cancel Procedures</LI>
+			<LI bugid="DUSIMA-195">F1 Removal Procedure</LI>
+			<LI bugid="NR5GX3K-72">RRC Resume</LI>
+			<LI bugid="">NRDC setup and release</LI>
+			<LI bugid="DUSIMA-212">MN initiated SN change procedure </LI>
+			<LI bugid="">User plane performance improvement</LI>
+			<LI bugid="DUSIMA-211">User plane optimized throughput per UE </LI>	
+        </UL>
+
+        <H3>LoadCore</H3>
+        <UL>
+			<LI bugid="">Edge computing - EASDF node added to Full Core topology</LI>
+			<LI bugid="">Edge computing - EAS Deployment support in Full Core topology</LI>
+			<LI bugid="">Edge computing - ULCL insertion in Full Core topology</LI>
+			<LI bugid="">Full Core SMF can communicate with EASDF (N88) and NEF (N29)for Edge Computing scenarios</LI>
+			<LI>Full Core topology: mutual TLS (mTLS) is supported on all SBA Nodes (including SEPP, SBI Fuzzer)</LI>
+			<LI>Full Core topology: Enhanced the distribution of simulated nodes over multiple agents</LI>
+			<LI>All topologies: Enhanced routing when running with Linux stack</LI>
+			<LI>Full Core topology: UPF support to register to NRF</LI>
+			<LI>Full Core topology: SMF support to discover UPF via NRF</LI>
+			<LI>Full Core topology: Network-initiated (PCF) QoS Flows can now be created also at PDU Session Establishment time 
+			<LI>Full Core topology: DNS Server to be included by SMF in ePCO IE can be configured per DNN in Global Settings.</LI>
+			<LI>SBA tester topology: AF node with N5 interface towards PCF support</LI>
+			<LI bugid="">gNodeB: Added option to always include 5G capabilities when doing 4G (regardless of mobility path)</LI>
+            <LI bugid="LOADCORE-5878">FullCore topology: Standalone MME simulation: Added configuration option to send Modify Access Bearers Request or Modify Bearer Request for Option 3x scenarios</LI>
+            <LI bugid="LOADCORE-6258">RAN: Added an option to not include SDF in PDI in case Application Identifier is present</LI>
+            <LI bugid="LOADCORE-6346">RAN: Added configuration option to change ENB-UE-S1AP-ID/GNB-UE-NGAP-ID after Service Request</LI>
+            <LI bugid="">Configurable T3412 timer on standalone MME </LI>
+            <LI bugid="">UPF Isolation topology: Paging throttling option added for the case where paging is triggered by passthrough DL traffic</LI>
+			<LI bugid="">UNAP: Userplane support</LI>
+			<LI bugid="">UNAP: Dedicated QoS flow support (both UE and Network Initiated)</LI>
+			<LI bugid="">UNAP: NAT-T support</LI>
+			<LI bugid="">UNAP: Support for Create/Delete PDU Session and Create/Delete QoS Flows secondary oobjectives</LI>
+        </UL>
+
+        <H3>CUSim</H3>
+        <UL>
+			<LI bugid="CUINT-48">Stateless UDP application traffic support</LI>
+			<LI bugid="">One CP instance and multiple UP instances</LI>
+			<LI bugid="CUINT-49">Licensing enhancement</LI>
+			<LI bugid="CUINT-45">R16 Spec Version support</LI>
+			<LI bugid="CUINT-50">PDCP encryption and integrity protection</LI>
+        </UL>
+
+        <H3>User plane</H3>
+        <UL>
+            <LI>Security attacks support</LI>
+            Note: A separate security packet containing the attacks and malware is necesary to be installed on top of ORAN SIM CE  for this feature
+            <LI>SIP editor</LI>
+            <LI>REST API Client</LI>
+            <LI>FTPS(FTP over TLS)</LI>
+            <LI>Publish TCP stats per Application Traffic objective</LI>
+            <LI>Enhanced TLS statistics dashboards</LI>
+            <LI>IMS support for Emergency VoNR/VoLTE calls</LI>
+            <LI bugid="LOADCORE-4812">RAN: Application traffic uses DNS Server from ePCO IE</LI>
+            <LI bugid="LOADCORE-5678">IMS: T1 and T2 retransmission timers are now configurable</LI>
+            <LI bugid="LOADCORE-5450">IMS: Accept SIP Register Refresh on existing IPsec SA without creating a new one</LI>
+            <LI bugid="LOADCORE-5451">IMS: A single IPSEC Tunnel (SA) can be used for SIP TCP IPsec calls</LI>
+            <LI>Jumbo frames support for IxStack Raw and IxStack DPDK </LI>
+            <LI>CoreSim: Trigger Paging based on locally generated downlink traffic </LI>
+            <LI>Video OTT support for TLS lite</LI>
+        </UL>
+
+        <H3>Next generation UDG protocol support - client(ngUUDG) and server(ngNUDG)</H3>
+        <UL>
+            <LI bugid="LOADCORE-5539"> Support for UDG KEEP ALIVE INDICATION</LI>
+        </UL>
+
+
+              
+    </div>
+    <HR>
+    <H2><A NAME="Supported Platforms">Supported Platforms</A></H2>
+    <H3>Virtual Environments</H3>
+    <table style="text-align: center">
+        <tr>
+            <th>Area</th>
+            <th>AliCloud</th>
+            <th>AWS</th>
+            <th>Azure</th>
+            <th>KVM</th>
+            <th>OpenStack</th>
+            <th>Oracle cloud</th>
+            <th>VMware ESX</th>
+        </tr>
+        <tr>
+            <td>Control Plane</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+        <tr>
+            <td>Stateless UDP</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+        <tr>
+            <td>Application Traffic</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+    </table>
+    <br>
+
+    <H3>Containerized Environments</H3>
+    <table style="text-align: center">
+        <tr>
+            <th>Area</th>
+			<th>AWS EKS</th>
+            <th>Azure AKS & AON</th>
+            <th>Container agent</th>
+            <th>Google Anthos</th>
+            <th>Kubernetes</th>
+            <th>OpenShift</th>
+            <th>Oracle OKE</th>
+        </tr>
+        <tr>
+            <td>Control Plane</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+        <tr>
+            <td>Stateless UDP</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+        <tr>
+            <td>Application Traffic</td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+            <td><span>&#9989;</span></td>
+        </tr>
+    </table>
+    <br>
+
+    <H2><A NAME="System Recommendations">System Recommendations</A></H2>
+    <H3>Virtual Environments</H3>
+    <table style="text-align: center">
+        <tr>
+            <th>Area</th>
+            <th>AliCloud</th>
+            <th>AWS</th>
+            <th>Azure</th>
+            <th>KVM</th>
+            <th>OpenStack</th>
+            <th>Oracle Cloud</th>
+            <th>VMware ESX</th>
+
+        </tr>
+        <tr>
+            <td>Agent (control plane)</td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD</td>
+            <td>t2.xlarge, c4.xlarge and c5.xlarge</td>
+            <td>Standard F8s (8 vCPUs, 16 GB RAM)</td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+        </tr>
+        <tr>
+            <td>Agent (application traffic)</td>
+            <td>8 vCPUs, 32 GB RAM, 20 GB SSD </td>
+            <td>c4.xlarge, c5.xlarge</span></td>
+        <td>8 vCPUs, 32 GB RAM, 20 GB SSD</td>
+            <td>8 vCPUs, 32 GB RAM, 20 GB SSD </td>
+            <td>8 vCPUs, 32 GB RAM, 20 GB SSD </td>
+		<td>8 vCPUs, 32 GB RAM, 20 GB SSD </td>
+            <td>8 vCPUs, 32 GB RAM, 20 GB SSD </td>
+        </tr>
+        <tr>
+            <td>Middleware</td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+            <td>m4.2xlarge, m5.2xlarge</td>
+            <td>Standard F8s (8 vCPUs, 16 GB RAM, 256 GB HDD)</td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+<td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD</td>
+        </tr>
+        <tr>
+            <td>Licensing</td>
+            <td>2 vCPUs, 8 GB RAM, 100 GB SSD</td>
+            <td>t2.medium</td>
+            <td>Standard F4s (4 vCPUs, 8 GB RAM)</td>
+            <td>2 vCPUs, 8 GB RAM, 100 GB SSD</td>
+            <td>2 vCPUs, 8 GB RAM, 100 GB SSD</td>
+<td>2 vCPUs, 8 GB RAM, 100 GB SSD</td>
+            <td>2 vCPUs, 8 GB RAM, 100 GB SSD</td>
+        </tr>
+    </table>
+
+    <H3>Containerized Environments</H3>
+    <table style="text-align: center">
+        <tr>
+            <th>Area</th>
+	    <th>AWS EKS</th>
+            <th>Azure AKS & AON</th>
+            <th>Container agent</th>
+            <th>Google Anthos</th>
+            <th>Kubernetes</th>
+            <th>OpenShift</th>
+            <th>Oracle OKE</th>
+        </tr>
+        <tr>
+            <td>Agent (control plane)</td>
+            <td>t2.xlarge, c4.xlarge, c5.xlarge (Ubuntu workers)</td>
+            <td>4 vCPUs, 8 GB RAM</td>
+            <td>4 vCPUs, 8 GB RAM</td>
+            <td>e2-standard-16</td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+            <td>4 vCPUs, 4 GB RAM, 20 GB SSD </td>
+        </tr>
+        <tr>
+            <td>Agent (application traffic)</td>
+            <td>c4.xlarge, c5.xlarge (Ubuntu workers)</td>
+            <td>12 vCPUs, 16 GB RAM</td>
+            <td>12 vCPUs, 16 GB RAM</td>
+            <td>12 vCPUs, 16 GB RAM</td>
+            <td>12 vCPUs, 16 GB RAM</td>
+            <td>12 vCPUs, 16 GB RAM</td>
+<td>12 vCPUs, 16 GB RAM</td>
+        </tr>
+        <tr>
+            <td>Middleware</td>
+            <td>c5.4xlarge (Ubuntu workers)</td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD</td>
+            <td>&#10060;</span></td>
+            <td>e2-standard-16</td>
+	<td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+            <td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+	<td>8 vCPUs, 16 GB RAM, 256 GB SSD </td>
+        </tr>
+    </table>
+
+    <BR>
+    <h3><a name="Supported Browsers">Supported Browsers</a></h3>
+    The LoadCore web user interface supports the following browsers:
+    <ul>
+        <li>Chrome v.89 (or later)</li>
+        <li>Firefox v.86 (or later)</li>
+        <li>Edge Chromium v.90 (or later)</li>
+        <li>Safari v.14 (or later)</li>
+    </ul>
+
+
+    <BR>
+    <H3>Supported NICs for Application Traffic</H3>
+    <UL>
+        <LI>Intel X710 10G</LI>
+        <LI>Intel XXV710 25G</LI>
+        <LI>Intel XL710 40G</LI>
+        <LI>Intel E810 25G</LI>
+        <LI>Intel E810 100G</LI>
+        <LI>Mellanox ConnectX-4/5 25G</LI>
+        <LI>Mellanox ConnectX-4/5 100G</LI>
+        <LI>Mellanox ConnectX-6 Dx 100G</LI>
+        <LI>VMWare ESXi Virtual NIC (vmxnet3)</LI>
+    </UL>
+    Please check manufacturer's web site for transceiver/cable compatibility.
+
+    <BR>
+
+    <H3>Supported drivers for Application Traffic</H3>
+    <UL>
+        <LI>vmxnet3</LI>
+        <LI>mlx4_core</LI>
+        <LI>mlx5_core</LI>
+        <LI>ixgbe</LI>
+        <LI>ixgbevf</LI>
+        <LI>i40</LI>
+        <LI>i40e</LI>
+        <LI>i40evf</LI>
+        <LI>iavf</LI>
+        <LI>ena</LI>
+	    <LI>virtio</LI>
+	    <LI>ice</LI>
+    </UL>
+
+    <H3>IxStack over raw sockets/DPDK nodes support:</H3>
+    The following applications and protocol interfaces can run on IxStack over raw sockets/DPDK:
+    <UL>
+        <LI>NG-RAN, CoreSim - N2 and N3</LI>
+        <LI>UPF - N3, N4, N6 and N9</LI>
+        <LI>N4-SMF simulation (SMF+RAN used in UPF isolation topology) - N3 and N4</LI>
+        <LI>DN - N6</LI>
+        <LI>IMS Media Function - N6</LI>
+        <LI>DU-UP F1-U</LI>
+        <LI>CU-UP F1-U</LI>
+    </UL>
+    These nodes also run on Linux stack.
+    <BR>
+    All other nodes run only on Linux stack.
+
+
+    <BR><BR>
+
+
+
+    <HR>
+    <H2><A NAME="Fixed in This Release">Fixed in This Release</A></H2>
+    <div class="resolvedDefectsListCssClass">
+        <UL>
+			<LI bugid="LOADCORE-6332">Fixed a problem where the same IP address was not allowed on 4G control plane and user plane</LI>
+			<LI bugid="LOADCORE-5866">Untrusted WiFi: Allow empty Local identification value (while Local identification type is set to ID_KEY_ID)</LI>
+			<LI bugid="LOADCORE-5502">Fixed an issue where capture file was not created if no packets were captured</LI>
+			<LI bugid="LOADCORE-5659">Fixed an issue where there was a SCTP timeout in configurations using Emulated Router and VLAN</LI>
+			<LI bugid="LOADCORE-6077">Fixed a crash that appeared when enabling Per UE Statistics</LI>
+			<LI bugid="LOADCORE-6272">Fixed an issue where relative URI was not allowed for AUSF to AMF communication</LI>
+			<LI bugid="LOADCORE-6437">Fixed SGW S5 behavior of not accepting SessionEstablishResponse from PGW S5 if Bearer Level QoS was not included.</LI>
+			<LI bugid="LOADCORE-6044">Default values for home network private and public keys were not working when using profile A</LI>
+			<LI bugid="LOADCORE-6018">Whenever the MME is standalone, DUT or not, the S1-U interface should be visible on all eNodeB ranges and configured on the agents.</LI>
+			<LI bugid="NR5GX0X-126">DUSim Authentication issue in UE registration </LI>
+			<LI bugid="NR5GX0X-129">DUSim gets GTP error with UDG traffic </LI>
+			<LI bugid="NR5GX0X-128">DUSim does not send our RRC Request when DU-UP enabled  </LI> 
+			<LI bugid="NR5GX0X-142">DUSim sending RRC Resume in middle of active session </LI>
+			<LI bugid="NR5GX0X-130">DUSim tstm error when running UP traffic on same agent and different port than CP </LI>
+			<LI bugid="NR5GX3K-75">DUSim sends INITIAL UL RRC MESSAGE TRANSFER message with the new C-RNTI </LI>      
+			<LI bugid="NR5GX3K-74">DUSim s-NSSAI not well configured in Xn HandoverRequest </LI>
+			<LI bugid="NR5GX3K-73">DUSim NRCGI IE is not good in InitialULRRCMessageTransfer triggered for RRC Reestablishment Procedure </LI>
+			<LI bugid="NR5GX3K-72">DUSim RRC Inactive -RRC Resume not Triggered </LI>
+			<LI bugid="NR5GX3K-70">DUSim Wrong nrModeInfo Config in XnSetupRequest </LI>
+			<LI bugid="NR5GX3K-69">DUSim Malformed XnAP Handover Request </LI>
+			<LI bugid="NR5GX3K-68">DUSim is not responding back for WriteReplaceWarningRequest & PWSCancelRequest  </LI>
+			<LI bugid="NR5GX3K-62">DUSim is not sending response to id-WriteReplaceWarning & PWSCancel </LI>
+			<LI bugid="NR5GX3K-57">DUSim DUconfig update receives error from O-CU </LI>
+			<LI bugid="NR5GX2N-12">DUSim missing optional IE servingCellConfigCommon in F1Setup Request </LI>
+			<LI bugid="NR5GX2N-11">DUSim SA handover case when the optional IE “radioBearerConfig” is not present in RRC reconfiguration sent from DUT </LI>
+			<LI bugid="NR5GX2N-13">DUSim No uplane traffic </LI>
+			<LI bugid="DUSIMA-172">DUSim explicitly mention PCI for cell id in GUI</LI>
+			<LI bugid="DUSIMA-187">DUSimUnable to assign 0 as CU/gNB Id in DUSIM GUI</LI>
+			<LI bugid="DUSIMA-213">DUSIM canot run IntraDU+InterDU in same config </LI>
+			<LI bugid="DUSIMA-214">DUSim XN userplane traffic ARP issue</LI>
+			<LI bugid="NR5GX0X-163">DUSim UE not including S-NSSAI in RRC Setup complete</LI>
+			<LI bugid=""></LI>
+        </UL>
+
+    </div>
+
+    <HR>
+    <H2><A NAME="Installation Notes">Installation Notes</A></H2>
+
+    ORAN SIM CE 3.0 provides a new middleware image and an upgrade file. Please also note that upgrading a setup from
+    pre-LC4.0 version to ORAN SIM CE 3.0 is not supported.
+    <BR>
+    ORAN SIM CE 3.0 also comes with new agent images, and upgrades.
+    <BR>
+    AWS and Azure images are not distributed on the product download page. AWS image can be found on the<a
+        href="https://aws.amazon.com/marketplace/seller-profile?id=e47b8c97-3fd9-4c39-bd75-9bbe50f3436c"
+        target="_blank"> AWS Marketplace</a>, and both (AWS and Azure) can be shared by request by the engineering team.
+    Please contact engineering at email <a href="loadcore-support@keysighttech.onmicrosoft.com">LoadCore-Support</a> to
+    request access to these images.
+    <BR>
+    <BR>
+    The REST API dashboards names have been changed. For automation users, in case your harness is checking the
+    statistics, please use the REST API stats migration script to automatically convert the old naming into the new one.
+    <BR>
+
+
+
+    Please follow these steps to create a setup for running the product:
+    <BR>
+    <H4>If ORAN SIM CE 2.0 setup is not yet deployed, please use the below steps to deploy ORAN SIM CE 3.0 and configure an account
+    </H4>
+    <OL>
+        <LI>Deploy the UI/middleware cluster OVA file</LI>
+        <LI>Deploy the licensing OVA file (optional)</LI>
+        <LI>After deployment you can access the UI using the MW machine IP and access it using a browser:
+            https://XX.XX.XX.XX. If shortly after deploying the MW the UI is not accessible, you need to wait a couple
+            of minutes for all the pods to start up.</LI>
+        <LI>To access the UI, you will be prompted for a username and password. You will need to register a new user and
+            then use it each time you log in.</LI>
+
+        <LI>Connect to the ORAN SIM CE with your account. If a ORAN SIM CE 3.0 setup is not already available please use the above steps
+            to deploy a new setup</LI>
+    </OL>
+    <H4>If ORAN SIM CE 2.0 setup is deployed, please use the below steps to upgrade (creating a backup of existing configs and raising memory to 24 GB RAM is recommended):</H4>
+    <OL>
+        <H4>Apply the patch using the UI: </H4>
+        <LI>After connecting to the ORAN SIM CE 2.0 setup, find the "Gear menu" in the upper right corner and click on it to bring
+            up the menu</LI>
+        <LI>Then, click on "Software Updates"</LI>
+        <LI>Click the "Browse" button and use the opened control to find the upgrade tar on the disk. If the ORAN SIM CE 2.0 environment is cloud (not on premise) please use the cloud tar.</LI>
+        <LI>Click on the "Start Update" button to apply the patch and wait for the procedure to end. </LI>
+        <LI>Refresh your ORAN SIM CE 2.0 page in the broswser</LI>
+        <LI>Access the same menu and check the version of the setup again to make sure that the patch has been applied
+            successfully.</LI>
+    </OL>
+    <OL>
+        <H4>Apply the patch using the KCOS CLI: </H4>
+        <LI>Connect to the ORAN SIM CE 2.0 setup with either SSH (on port 22: admin/admin user) or directly through the console
+            (console -> admin/admin user). This will make available the KCOS CLI.</LI>
+        <LI>Copy the update file to the MW using SCP. (admin/admin user). If the ORAN SIM CE 2.0 environment is cloud (not on premise) please use the cloud tar.</LI>
+        <LI>Give the following command in the KCOS CLI pointing to the update tar that was copied on the MW machine:
+            kcos deployment offline-install ./LoadCore-MDW-BUILD_VERSION.tar </LI>
+        <LI>Wait for the process to finish. This might take several minutes. </LI>
+        <LI>Refresh your LoadCore page in the broswser</LI>
+        <LI>Access the UI and check the version of the setup to make sure that the patch has been applied successfully.
+        </LI>
+    </OL>
+
+
+    <H4>For deploying the agents, please follow these steps:</H4>
+    <OL>
+        <LI>Deploy the agent OVA file</LI>
+        <LI>Add another NIC to the agent VM from the hypervisor configuration window. This will be the test NIC.</LI>
+        <LI>Log in to the agent VM and configure the management interface, if needed</LI>
+        <LI>Run the agent-setup.sh script and follow the steps in the interactive setup. This step is required to
+            connect the agent to the middleware/UI cluster.</LI>
+        <PRE>#  sudo ./agent-setup.sh</PRE>
+        <LI>At this point, you should be able to see the newly created agent in the UI</LI>
+    </OL>
+    Repeat these steps to deploy as many agents as required.
+	<H4>For upgrading the agents, please follow these steps:</H4>
+	<OL>
+		<LI>Apply the REST API command to update the agent (replace the IP and location of the .tgz as needed):</LI>
+curl -kX PUT https://XX.XX.XX.XX/api/v1/update --upload-file /home/ixia/LoadCore-Agent-Update-BUILD_VERSION.tgz
+	</OL>
+
+    <HR>
+    <H2><A NAME="Additional Documentation">Additional Documentation</A></H2>
+    Please refer to the <a href="https://github.com/Keysight/oran-sim-ce/tree/main/Resources/Open%20RAN%20SIM%20CE%203.0/User%20Guides">user guides</a> and
+    <a href="https://github.com/Keysight/oran-sim-ce/blob/main/Resources/Open%20RAN%20SIM%20CE%203.0/User%20Guides/ORAN_SIM_CE_DeploymentGuide.pdf">deployment guide</a></A>.
+    <BR><BR>
+
+    <HR>
+    <H2><A NAME="Known Limitations">Known Limitations</A></H2>
+    <div class="knownIssuesListCssClass">
+        <UL>
+
+            <H3> Application Infrastructure </H3>
+		<LI>LoadCore configuration files generated in versions older than 2.3.0 are no longer supported. In order to use such config files, the workaround is to import and export them into a LoadCore 2.3.0 or 3.0.0 instance.</LI>
+            <LI bugid="LOADCORE-1525">When checking license statistics, in the application column appears LoadCore N/A instead of LoadCore</LI>
+            <LI bugid="LOADCORE-1514">When taking licenses from SLUM, instead of username, it appears an hexa code</LI>
+            <LI bugid="LOADCORE-1590">Predefined flows are not working when the agent is connected to the MW without using the LoadBalancer public ip</LI>
+            <LI bugid="BUG1546716">On SRIOV setups using Intel NIC we can use a maximum of 4 cores</LI>
+            <LI bugid="">On SRIOV setups using Intel NIC, the recommendation is to use a MTU equal to 1480 when
+                configuring VLANs on the N3 interface</LI>
+            <LI>Deploying a new middleware, in rare occasions, fails because of the weavenet pod gives an error. The
+                workaround is to delete the weavenet pod which will trigger the pod to be recreated correctly</LI>
+            <LI bugid="BUG1558579"> Sometimes a test could fail to start with 'Lizard communication error' if the
+                required agents were rebooted from UI before starting the test. As a workaround the user should wait for
+                about a minute then start the test again.</LI>
+            <LI bugid="BUG1561108"> Sometimes the LC MW becomes unavailable after a reboot. Workaround: reboot the LC MW
+                again.</LI>
+            <LI bugid="LoadCore-778"> Sometimes the LC MW UI hangs while it gets updated. Workaround: wait several
+                minutes, refresh the UI and check the Keysight Load Core version.</LI>
+            <LI bugid="LOADCORE-814"> The Per-UE Statistics feature only works with Stateless UDP flow. The Per-UE
+                Statistics will show up as empty in UI if running an Application Traffic test. </LI>
+            <LI bugid="LOADCORE-511"> The Per-UE Statistics feature is currently only supported for the NG-RAN
+                application and will not generate CSVs for any other nodes when running a test with this feature. </LI>
+			<LI bugid="LOADCORE-1475">The Process of updating LoadCore MDW from Web UI in a cloud environment might not reach the end.
+                The workaround is to refresh the Web UI and check the new versions.</LI>
+            <LI bugid="LOADCORE-2286">Reserved subnets ( e.g 169.254.0.0) are not supported for management communication </LI>
+            <LI bugid="ISGAPPSEC2-24079">On License Server the search bar from license statistics is not working. The workaround is to manually search the strings </LI>
+
+            <H3> Control Plane</H3>
+			<!-- LC 4.4 -->
+			<LI bugid="LOADCORE-6066">NEF does not derive DNN and S-NSSAI from the AF Service Identifier, AF must specify them explicitly.</LI>
+			<LI bugid="LOADCORE-6593">Edge Computing Procedures such as EAS Deployment, EAS Discovery, etc allow an AF to interact with the 5G Core only via N33 (NEF).</LI>
+			<LI bugid="LOADCORE-6266">Edge Computing: No support for Baseline DNS Pattern Management or EDNS Client Subnet option information in EAS deployment and discovery procedures with EASDF.</LI>
+			<LI bugid="LOADCORE-6205">Edge Computing: The EAS discovery procedure with EASDF -> Neasdf_DNSContext_Create Request -> DnsQueryMdt / DnsRspMdt -> FQDN Pattern List is not used for matching.</LI>
+			<LI bugid="LOADCORE-6200">Edge Computing: The EAS discovery procedure with EASDF does not support Neasdf_DNSContext_Update or Neasdf_DNSContext_Notify described in TS 23548 "6.2.3.2.2 EAS Discovery Procedure with EASDF" steps 5-6, 8-9, 10-11.</LI>
+			<LI bugid=""> Full Core: Roaming with Home Routed traffic is supported onlyfor Register/Unregister andCreate/Delete PDU Session</LI>
+			<LI bugid="LOADCORE-6267">LoadCore NEF cannot register to NRF and cannot be discovered by other network functions</LI>
+			<LI bugid="LOADCORE-6961">Full Core topology: UE Range Settings - Paging Settings section is unavailable.</LI>
+
+			<!-- LC 4.3 -->
+            <LI bugid="LOADCORE-5055">'Additional Routes' configuration option is not present on 'DNS Server' application in 'Full Core' topology</LI>
+			<LI bugid="LOADCORE-5281">For network initiated PDU Session Modification, the current CoreSim design is that 5QI values up to 9 are allocated as non-dynamic while 10 or above are allocated as dynamic 5QI values.</LI>
+			<LI bugid="LOADCORE-3624">Location Services E-CID Measurements triggered by Change of Area are not initiated in case of idle mobilities (Idle intra-RAT, Idle IRAT, Idle EPS Fallback mobilities).</LI>
+			<LI bugid= "LOADCORE-4390">Having IPsec on N2/N3 and Untrusted WiFi in the same test is not supported </LI>
+			<LI bugid="">Agent REST API: For Untrusted WiFi simulations, retryCount and retryTimeout settings are ignored </LI>
+			<LI bugid="LOADCORE-5219">Option '320 hours' is missing from Extended T3412 values list</LI>
+			<LI bugid="LOADCORE-5216">T3412 timer is missing from mobility Tracking Area Update Accept messages </LI>
+			<LI bugid="LOADCORE-5214">MME ignores the T3412 value proposed by the eNodeB in Attach Request </LI>
+			<LI bugid="LOADCORE-3613">The Routing ID value in DOWNLINK / UPLINK UE ASSOCIATED NRPPA TRANSPORT is hardcoded to 0 </LI>
+			<LI bugid="LOADCORE-3612">Untrusted WiFi: No intra WiFi handover support; no MOBIKE support</LI>
+			<LI bugid="">Untrusted WiFi: No intra 5G handover support when handover between Untrusted WiFI and 5G is configured</LI>
+			<LI bugid="">Untrusted WiFi: No impairment support on NWu and Y2 interfaces</LI>
+			<LI bugid="">Untrusted WiFi: No N3IWF selection support – N3IWF will need to be configured with its IP</LI>
+			<LI bugid="">Untrusted WiFi: No support for Multiple-Access PDU. The PDU will either be in WiFi or in 5G</LI>
+			<LI bugid="">Untrusted WiFi: No support for multiple agents assigned to UNAP or N3IWF simulations</LI>
+			<LI bugid="">Untrusted WiFi: In scenarios with multiple QoS Flows the same SA is used for all </LI>
+			<LI bugid="LOADCORE-3958">Untrusted WiFi: No support for enter/exit idle scenarios. </LI>
+			<LI bugid="LOADCORE-3943">Untrusted WiFi: No support for emergency registration </LI>
+			<LI bugid="LOADCORE-4969">UE Radio Capability Replay is not supported in FullCore 4G topology</LI>
+			<LI bugid="LOADCORE-4913">CoreSim: Network inititated bearers in 4G work just for 1 DNN in this release</LI>
+			<LI bugid="LOADCORE-4880">Delay is not taken into account for network initiated Create/Delete QoS Flows secondary objective (4G and 5G)</LI>
+			<LI bugid="LOADCORE-4614">The iterations parameter is not taken into account for 4G UE initated dedicated bearers</LI>
+			<LI bugid="LOADCORE-4604">After successful deletion of a dedicated bearer for the 2nd DNN, downlink traffic still flows on that deleted TEID </LI>
+			<LI bugid="LOADCORE-4554">For 4G UE initiated dedicated bearer the value of Packet Evaluation Precedence from TFT -> Packet Filter is hardcoded to 1</LI>
+			<LI bugid="LOADCORE-4864">Full Core topology: AMF considers only the NSSAI with the lowest SST value it receives from UDM and ignores the rest. This may affect reroute scenarios</LI>
+			<LI bugid="LOADCORE-5387">When the UE holds a valid GUTI and the tracking area of the current cell is in the list of tracking areas that the UE previously registered in the MME during the NAS signalling connection establishment, during TAU the UE NAS does not provide the lower layers the S-TMSI as per specifications but the MME identifier part of the valid GUTI with an indication that the identifier is a native GUMMEI (TS24301 5.3.1.1 Establishment of the NAS signalling connection).</LI>
+			<LI bugid="LOADCORE-5279">CoreSim: The Network Initiated PDU Session Modification procedure cannot configure MBR values that are less than the GBR values.</LI>
+
+            <!-- LC 4.2-->
+            <LI bugid="LOADCORE-3701">Dual Registration is supported just on RAN and Core simulations, not on the other 5G core nodes</LI>
+            <LI bugid="LOADCORE-3471">Enter/Exit idle objective with 1 iteration executes twice for dual registration UEs</LI>
+            <LI bugid="LOADCORE-3600">5G Location Services: UE Measurement ID in E-CID MEASUREMENT messages doesn't support (1 ... 256) values, supporting (1 ... 15) instead.</LI>
+            <LI bugid="LOADCORE-3600">5G Location Services: Measurement Periodicity in E-CID MEASUREMENT messages doesn't support 20480ms, 40960ms values.</LI>
+            <LI bugid="LOADCORE-3120">Location Services: No support for Inter-RAT Measurement Quantities and WLAN Measurement Quantities </LI>
+            <LI bugid="LOADCORE-3244">SBA tester: UDM does not include subscription related information in procedure statistics</LI>
+            <LI bugid="LOADCORE-3249">SBA tester: UDM does not include SMS Management Subscription Notify statistics</LI>
+            <LI bugid="LOADCORE-3118">CoreSim: Location Services LPPa / NRPPa Transaction ID values per UE are ignored by MME / AMF</LI>
+            <LI bugid="">CoreSim UI does not expose the options for CN initiated deactivation / UE initiated reactivation of the User Plane connection of a PDU Session.</LI>
+            <LI bugid="LOADCORE-2968">When running only with server nodes enabled, the test duration is infinite. The test can be manually stopped by pressing the STOP or ABORT button.</LI>
+            
+			<!-- LC 4.0-->
+			<LI>SBI Fuzzer should not be used in scenarios with SEPP and SCP as it may cause routing problems</LI>
+			<LI>Multipart HTTP messages are not modified by SBI Fuzzer</LI>
+			<LI>The DNN reactivation timer is deactivated if an IRAT mobility occurs before the timer expires</LI>
+			<LI>TUAK supports only: K values of 128 bits, MAC-A values of 64 bits, MAC-S values of 64 bits, RES values of 64 bits, CK values of 128 bits and IK values of 128 bits </LI>
+			<LI>PWS/ETWS: Cannot configure subsequent WriteReplaceWarningRequests with different (Message Identifier IE and/or Serial Number IE) with/without Concurrent Warning Message Indicator IE</LI>
+			<LI>When running CoreSim with IxStack and SEG is enabled, each SEG range can protect just one IP </LI>
+			<LI bugid="LOADCORE-2472">NGRAN will reject IKE AUTH_RESPONSE messages that contain Traffic Selector payload with start address value different than end address value (NGRAN expects a host IP address in Traffic Selector i.e. a netmask of /32 or /128)</LI>
+			<LI bugid="LOADCORE-2608">When IPsec is enabled on either NGRAN or CoreSim, inner IPv4 and outer IPv6 is not supported (both IxStack and Linux stack)</LI>
+			<LI>The maximum size of the archive uploaded with certificates is 10MB</LI>
+			<LI>When running with IPsec on RAN, a maximum of 2048 gNodeBs on each range and a maximum of 127 ranges can be configured</LI>
+			<LI>When running with Linux stack only decrypt/encrypt errors stats are published (no statistics for ESP Packets/Bytes Tx/Rx)</LI>
+			<LI>On SEG side IPs are not reused after the IPsec tunnel is torn down</LI>
+			<LI>Rekey for phase2 fails if CREATE_CHILD_SA_REQUEST contains multiple Notifications Payloads and REKEY_SA is not the first payload</LI>
+			<LI>Sometimes an agent failure can happen in tests which have Dead Peer Detection and Rekey enabled</LI>
+			
+			<!-- newly added  in LC 3.4-->
+			<LI>When using Ethernet PDU Session and simulating UPF, only one PDU Session per UE is supported </LI>
+			<LI>All NEF services have support only for Release 16.</LI>
+			<LI bugid="LOADCORE-1693">Old Blocked / Greylisted Subscribers -> Start / End IMEI values should be manually modified to match UE IMEI</LI>
+			<LI bugid="LOADCORE-1747">No End Marker support on S1-u interface</LI>
+			<LI>Background Data Transfer service: Location is not supported</LI>
+			<LI>Background Data Transfer service: No support for Renegotiation and Notifications triggered by changes in the network</LI>
+			<LI>SEPP Isolation: SEPP cannot be used on N14 interface</LI>
+			<LI>PCF and SMF simulations from full core topology do not interact with the CHF node</LI>
+			<LI>Debug tools: The Logs archive is not in the same location as CSV results, so when running the csv_analysis tool for parsing the logs, use the -log argument and add manually the logs archives in CSV folder.</LI>
+			
+			<!-- present before LC 3.4-->
+            <LI bugid="LOADCORE-1369">Advanced stats for control plane latency don't increment when per UE stats are enabled</li>
+
+            <LI bugid="">When N14 is enabled, only 2 AMF ranges can be configured</li>
+            <LI bugid="">No support for scenarios where the source AMF changes the active KAMF (horizontal KAMF 
+                derivation)</li>
+            <LI bugid="">The N2 Handover Execution Phase messages might intercalate with the Mobility Registration
+                Update messages resulting in a different order than the one defined in TS23502 4.9.1.3.3</li>
+            <LI bugid="">AMF Distribution on multiple agents is not supported</li>
+            <LI bugid="">N2 handover tests with AMF change and active N14 interface in which one UE performs more than
+                one handover per second might result in handover failure</li>
+            <LI bugid="">Only one type of handover (N2HO with AMF change) is supported while N14 is enabled. N2 Handover
+                with N14 and 5GS to EPS / EPS to 5GS handover is supported with the condition that only one AMF is
+                involved in I-RAT handover and both AMFs have N26 enabled.</li>
+            <LI bugid="">Enter/Exit Idle or Paging are not supported while running with N14 interface enabled</li>
+            <LI bugid="">The DUT AMF must have the correct GUAMI value configured (it should match the one configured on
+                the actual AMF DUT). Otherwise, the N14 connection will not be established.</li>
+            <LI bugid="">For legacy configurations the NSSAI and TAI will be be empty lists. In N14 tests, NSSAI and TAI
+                configuration is mandatory. In order to have successful UE registrations, please make sure the NSSAIs
+                configured on the UE and AMF match.</li>
+            <LI bugid="">N14 interface is mandatory when running AMF nodes on different agents during N2 handover</li>
+            <LI bugid="">Increasing the number of HTTP connections on AMF and SMF does not improve performance</li>
+
+            <LI bugid="">No support for notifications from NEF in this release</LI>
+            <LI bugid="">On NEF for AF Session with QoS service the UE identification is done only based on UE IP</LI>
+            <LI bugid="">On NEF for Service Parameter service the UE identification is done only based on UE IP or GPSI
+            </LI>
+            <LI bugid="">On NEF for Device Triggering service the UE identification is done only based on MSISDN</LI>
+            <LI bugid="">On NEF the following API calls are not implemented:
+                /3gpp-as-session-with-qos/v1/{scsAsId}/subscriptions, /3gpp-service-parameter/v1/{afId}/subscriptions,
+                /3gpp-device-triggering/v1/{scsAsId}/transactions</LI>
+
+            <LI bugid="">No support for Routing Binding Indication on SCP</LI>
+            <LI bugid="">For next hop SCP, if SCP receives from NRF a port, it will use it, otherwise it will default to
+                80 (HTTP) or 443 (HTTPS) depending on the protocol used by SCP</LI>
+
+            <LI bugid="BUG1563489">On N26 interface the GTPv2 messages always contain the recovery IE</LI>
+            <LI bugid="BUG1564769">For idle mobility tests, in case of a race condition between the mobility event and
+                the exit idle event, only the mobility event will be executed</LI>
+            <LI bugid="BUG1547311">For gNodeb+eNodeB simulation, create/delete QoS flows objective is skipped when the
+                UE is attached in 4G</LI>
+            <LI bugid="BUG1563540">UL/DL data is sent only to one UPF while running with SSC mode 2 and SSC mode 3</LI>
+            <LI bugid="BUG1564573">Execution with 2 or more DNNs is not recommended while running with SSC mode 2 and
+                SSC mode 3</LI>
+            <LI bugid="BUG1565513">Port instability could be reported while running with high number of UEs on SSC mode
+                3</LI>
+            <LI bugid="BUG1565500">“PDU session release UE originating failed” could be incremented while running with
+                high number of UEs on SSC mode 2</LI>
+            <LI bugid="BUG1548431">Secondary objectives may not get a chance to start when the primary objective is set
+                to "subscribers per second" and the hold time value is set to one second. Set a longer hold time to
+                allow the secondary objectives to start</LI>
+            <LI bugid="BUG1549118">Test will not start if the connection start rate can't be reached and maintained</LI>
+            <LI>PCF initiated create/delete QoS flows objective should not be run together with other secondary
+                objectives</LI>
+            <LI bugid="BUG1547689">NSSF response to GET Network Slice Selection request doesn't contain configured NSSAI
+                when the requested NSSAI includes an S-NSSAI that is not valid in the serving PLMN.</LI>
+            <LI bugid="BUG1548984">Multiple registration messages for UDM are sent to NRF while the topology contains
+                two UE subscriber ranges</LI>
+            <LI>For N2 Handover with AMF change, the S-AMF does not send the update SM context request to SMF in case of
+                failure on T-AMF</LI>
+            <LI>For N2 Handover with AMF change testing, it is recommended to have only the handover as a secondary
+                objective</LI>
+            <LI>All SBA nodes running on the same agent use the same HTTP/HTTPS server ports (80/443)</LI>
+            <LI>Unexpected behavior can be encountered when using duplicate UE IP addresses</LI>
+            <LI>UPF does not respond to session deletion retries</LI>
+            <LI>Increment for RAND parameter does not work as expected when the value overflows</LI>
+            <LI>Use remote F-TEID allocation option needs to be set when running the SMF node from UPF isolation
+                topology on multiple agents</LI>
+            <LI>SMF simulation from full core topology responds with error cause 404 to UDM initiated notifications</LI>
+            <LI bugid="BUG1549394">Statistics for default QoS flow activation procedures represent initial session
+                establishment procedures and one procedure might activate more than one QoS flow.</LI>
+            <LI bugid="BUG1553725">UPF isolation: N4-SMF SLAAC message stats are not populated when their value is 0
+            </LI>
+            <LI bugid="ENH1551047">UPF isolation: No support for unsolicited RAs</LI>
+            <LI bugid="ENH1551047">UPF isolation: SLAAC is not supported in N9 or uplink classifier tests</LI>
+            <LI bugid="BUG1555343">UPF isolation: SLAAC is not supported on scenarios with HTTPS flows</LI>
+            <LI bugid="BUG1553615">UPF isolation: When running consecutive tests without and then with "use remote
+                F-TEID allocation", the test will no longer start because of error "Test Stopped: Agents for client not
+                configured within 1m0s". At a new run the test will then start.</LI>
+            <LI bugid="BUG1562621">Session report for 5G scenario works only for one QoS flow</LI>
+            <LI>Only one MME with N26 interface can be simulated in full core topology</LI>
+            <LI>gNodeB simulation: For network initiated QoS flow modification, none of the parameters changed by the
+                network initiated QoS flow modification will be enforced</LI>
+            <LI>gNodeB simulation: For network initiated QoS flow modification, the NG-RAN node supports handling the
+                QoS flow modification procedure only for one PDU session per procedure</LI>
+            <LI>gNodeB simulation: For network initiated QoS flow modification, the NG-RAN node supports handling the
+                QoS flow modification procedure containing only one type of action per procedure (create QoS flow/modify
+                existing QoS flow/release QoS flow)</LI>
+            <LI>gNodeB simulation: For network initiated QoS flow modification, for existing QoS flows in order to
+                ensure predictability, the interval between the creation and deletion of the QoS flow should be large
+                enough to support the successful finalization for the modification of the existing QoS flow</LI>
+            <LI>In SBA Tester, when having SMS and PCF primary objectives at the same time, the test will have an
+                undefined behavior.</LI>
+            <LI>In SBA Tester, when having SMS objective, only one IP address should be configured on the test
+                interface.</LI>
+            <LI>The SMS activation procedure in SBA Tester supports only the 3gpp-access access type.</LI>
+            <LI>SBA Tester is not doing any action when it receives SMS specific errors. SBA Tester will only verify the
+                validity of the SMS message.</LI>
+            <LI>SBA Tester will send error message when TI doesn’t match and will not wait for a message with correct
+                TI.</LI>
+            <LI>SBA Tester does not support STATUS-REPORT processing. Receiving this message will result in an error
+                response 400 and cause “SMS_PAYLOAD_ERROR”.</LI>
+            <LI>SBA Tester does not support two or more SMS procedures in the same time in a UE range (mobile originated
+                or mobile terminated).</LI>
+            <LI>SMSF node will originate SMS regardless of how many mobile originated SMS received.</LI>
+            <LI>In SBA Tester, when using ConvergedChargingSMF2CHF primary objective, only the first SMF simulated node
+                will generate requests even if more SMF nodes are configured.</LI>
+            <LI>NG-RAN does not support two or more SMS procedures at the same time on the same UE range (mobile
+                originated or mobile terminated).</LI>
+            <LI>NG-RAN does not support STATUS-REPORT processing. Receiving this message will automatically trigger
+                mobile terminated procedure or continue mobile originated procedure. </LI>
+            <LI>The only error process by NG-RAN is CP-ERROR and receiving this error results in the stop of the SMS
+                procedure.</LI>
+            <LI>On NG-RAN, when received TI that doesn’t match the expected one, the procedure will continue without
+                reporting this error.</LI>
+            <LI bugid="BUG1552930">AMF does not send PDU session establishment reject to UE if AMF failed to discover
+                SMF.</LI>
+            <LI bugid="BUG1552932">AMF node sends wrong AMF UE ID in UE context release in case of AMF failed to
+                discover UDM.</LI>
+            <LI bugid="BUG1551716">Only one query with target-nf-type set to SMF is executed by AMF (for first PDU
+                session) while running a test with two or more DNNs. There is only one SMF node supported per agent.
+            </LI>
+            <LI bugid="BUG1553123">The minimum number of queries (per type of discovery) is equal to the minimum between
+                UE count and CPU core count when requester-nf-type is PCF or AUSF, or minimum between UE count, HTTP
+                connection count and CPU core count when requester-nf-type is AMF or SMF.</LI>
+            <LI bugid="BUG1552933">The AMF node does not stop the current procedure (PDU session establishment or PDU
+                session modification) in case SMF fails to discover AMF.</LI>
+            <LI>IPv6 SLAAC is supported only on RAN node in full core topology. SMF node in full core topology does NOT
+                support IPv6 SLAAC</LI>
+            <LI bugid="BUG1560069"> UDM does not support authentication results for multiple registrations</LI>
+            <LI bugid="BUG1560062"> AUSF does not signal authentication result removal to UDM</LI>
+            <LI bugid="BUG1558982">If UEs are registered for emergency services and periodic registration update is
+                enabled, test might become unresponsive.</LI>
+			<LI bugid="">UDG traffic does not support Jumbo frame</LI>
+			<LI bugid="">DUSIM agents using 100% CPU when user plane traffic disabled or have Ixstack raw/linux stack </LI>
+			<LI bugid="">DUSIM agents does not expose separate agent Logging control for UP Agent </LI>
+			<LI bugid="DUSIMA-205"> DUSIM test does not show ramp Up duration and test duration in test overview MDW Web UI</LI>
+
+
+
+                <H3> User Plane</H3>
+
+                <H4> Infrastructure & Data</H4>
+
+		        <!--LC 4.4<-->
+                <LI bugid="LOADCORE-6219">Security attacks: the initiated current statistic from the client stats - S2C strikes also count the number of UEs</LI>
+                <LI bugid="LOADCORE-6219">Security attacks: the TCP server statistics are empty. Workaround: check the Application Traffic - TCP tab </LI>
+                <LI bugid="LOADCORE-6937">Security attacks: Strikes Blocked statistic could be incremented while running a basic test</LI>
+
+
+				<!--LC 4.3<-->
+				<LI bugid="LOADCORE-4236">ICMP flow is not supported on Linux stack</LI>
+
+				<!--LC 4.2<-->
+                    <LI bugid="LOADCORE-3437">When running on ixstack raw sockets, the received packets are captured without the outer vlan.</LI>
+                    <LI>Ethernet Mode for Capture Replay activity is not supported on IP Endpoints topology</LI>
+                    <LI bugid="LOADCORE-3464">If an unreachable gateway is configured between the client and server endpoints, the number of packets shown under "Application Traffic | Stateless UDP" dashboard is greater than the number of packets sent out by the client endpoint</LI>
+                    <LI>Application traffic needs different agents for initiator and terminator sides</LI>
+                    <LI bugid="BUG1542956">Running the whole topology with application traffic on a single agent is not supported</LI>
+                    <LI bugid="BUG1537764">Running a full core test with passthrough activated and VLAN set on the N6 UPF interface cause the connection between RAN and AMF to be lost</LI>
+                    <LI bugid="BUG1555179">UPF is not receiving traffic in case the RAN N3 interface is the 2nd test interface - UPF passthrough topology on container agent</LI>
+                    <LI bugid="BUG1554588">UPF passthrough is sending downlink traffic from DN on intervals</LI>
+                    <LI>Only one IP can be configured as gateway on NG-RAN and UPF passthrough settings</LI>
+                    <LI>Lost user plane packets may be encountered when running enter/exit idle or paging secondary objectives together with UPF passthrough</LI>
+                    <LI>DN UDP traffic ports are not configured unless at least a stateless UDP flow is configured with desired traffic ports </LI>
+                    <LI>All packets coming on the passthrough interface will be mapped on the default flow on N3 interface </LI>
+                    <LI bugid="LOADCORE-642">TCP resets are seen for the first iteration on single UE tests when running multiple times without service restart</LI>
+                    <LI bugid="">No QoS flow enforcement of rates (AMBR/MFBR) for traffic objective.</LI>
+                    <LI>FTP flows can only be used for upload and the data port for FTP flows is randomly chosen at run-time and cannot be configured</LI>
+                    <LI>Using large HTTP page sizes (e.g. 1GB) is not recommended</LI>
+                    <LI>When running single HTTP/HTTPS flow with persistent TCP connection option enabled, a lower number of UEs will be active for userplane traffic during the test duration as compared to the configured number of UEs. When running with Persistent TCP connection option disabled, all configured UEs will be active for userplane traffic.</LI>
+                    <LI>Enter/exit idle secondary objective is compatible with Application traffic data flows only. Paging is not supported in this case.</LI>
+            
+                <h4> Media </H4>
+                    <LI>Voice MO/MT activities are not supported on IP Endpoints topology</LI>
+                    <LI>In tests with Voice application traffic, only one agent is supported per node</LI>
+                    <LI>Voice application traffic is working only with the active subscribers primary objective</LI>
+                    <LI>Only create/delete QoS flows and handovers secondary objectives are working with Voice application traffic. Other objectives like idle and paging are not working.</LI>
+                    <LI>For tests with Voice application traffic, EVS full header is working with only one audio frame per RTP packet</LI>
+                    <LI bugid="BUG1561143">On EPS fallback, the first few RTP packets are sent on the default 5G QoS flow until the 4G bearer is created.</LI>
+                    <LI>H.264 is the only video codec supported for VoNR</LI> 
+                    <LI>MSRP is supported only with SIP TCP Transport protocol</LI>
+
+                <h4> RUSim </H4>
+                <LI>Single agent support for the RU node from the RUSim topology</LI>
+                <LI bugid="LOADCORE-6210">UL traffic always uses the default QoS flow</LI>
+                
+                
+
+
+
+        </UL>
+    </div>
+
+    <HR>
+
+</BODY>
+
+</HTML>
\ No newline at end of file

Area	AliCloud	AWS	Azure	KVM	OpenStack	Oracle cloud	VMware ESX
Control Plane	✅	✅	✅	✅	✅	✅	✅
Stateless UDP	✅	✅	✅	✅	✅	✅	✅
Application Traffic	✅	✅	✅	✅	✅	✅	✅
Area	AliCloud	AWS	Azure	KVM	OpenStack	Oracle Cloud	VMware ESX
Agent (control plane)	4 vCPUs, 4 GB RAM, 20 GB SSD	t2.xlarge, c4.xlarge and c5.xlarge	Standard F8s (8 vCPUs, 16 GB RAM)	4 vCPUs, 4 GB RAM, 20 GB SSD	4 vCPUs, 4 GB RAM, 20 GB SSD	4 vCPUs, 4 GB RAM, 20 GB SSD	4 vCPUs, 4 GB RAM, 20 GB SSD
Agent (application traffic)	8 vCPUs, 32 GB RAM, 20 GB SSD	c4.xlarge, c5.xlarge	8 vCPUs, 32 GB RAM, 20 GB SSD	8 vCPUs, 32 GB RAM, 20 GB SSD	8 vCPUs, 32 GB RAM, 20 GB SSD	8 vCPUs, 32 GB RAM, 20 GB SSD	8 vCPUs, 32 GB RAM, 20 GB SSD
Middleware	8 vCPUs, 16 GB RAM, 256 GB SSD	m4.2xlarge, m5.2xlarge	Standard F8s (8 vCPUs, 16 GB RAM, 256 GB HDD)	8 vCPUs, 16 GB RAM, 256 GB SSD	8 vCPUs, 16 GB RAM, 256 GB SSD	8 vCPUs, 16 GB RAM, 256 GB SSD	8 vCPUs, 16 GB RAM, 256 GB SSD
Licensing	2 vCPUs, 8 GB RAM, 100 GB SSD	t2.medium	Standard F4s (4 vCPUs, 8 GB RAM)	2 vCPUs, 8 GB RAM, 100 GB SSD	2 vCPUs, 8 GB RAM, 100 GB SSD	2 vCPUs, 8 GB RAM, 100 GB SSD	2 vCPUs, 8 GB RAM, 100 GB SSD
Area	AWS EKS	Azure AKS & AON	Container agent	Google Anthos	Kubernetes	OpenShift	Oracle OKE
Agent (control plane)	t2.xlarge, c4.xlarge, c5.xlarge (Ubuntu workers)	4 vCPUs, 8 GB RAM	4 vCPUs, 8 GB RAM	e2-standard-16	4 vCPUs, 4 GB RAM, 20 GB SSD	4 vCPUs, 4 GB RAM, 20 GB SSD	4 vCPUs, 4 GB RAM, 20 GB SSD
Agent (application traffic)	c4.xlarge, c5.xlarge (Ubuntu workers)	12 vCPUs, 16 GB RAM	12 vCPUs, 16 GB RAM	12 vCPUs, 16 GB RAM	12 vCPUs, 16 GB RAM	12 vCPUs, 16 GB RAM	12 vCPUs, 16 GB RAM
Middleware	c5.4xlarge (Ubuntu workers)	8 vCPUs, 16 GB RAM, 256 GB SSD	❌	e2-standard-16	8 vCPUs, 16 GB RAM, 256 GB SSD	8 vCPUs, 16 GB RAM, 256 GB SSD	8 vCPUs, 16 GB RAM, 256 GB SSD