Merge pull request #271578 from PaulCarterMicrosoft/main

Add improved scaling to release notes

Author: prmerger-automator[bot]

articles/private-5g-core/azure-private-5g-core-release-notes-2403.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Private 5G Core 2403 release notes
-description: Discover what's new in the Azure Private 5G Core 2403 release
+description: Discover what's new in the Azure Private 5G Core 2403 release.
 author: paulcarter
 ms.author: paulcarter
 ms.service: private-5g-core
@@ -35,7 +35,23 @@ The following table shows the support status for different Packet Core releases
 
 ### TCP Maximum Segment Size (MSS) Clamping
 
-TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core will now automatically set this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core now automatically sets this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+
+### Improved Packet Core Scaling 
+
+In this release, the maximum supported limits for a range of parameters in an Azure Private 5G Core deployment increase. Testing confirms these limits, but other factors could affect what is achievable in a given scenario. 
+The following table lists the new maximum supported limits.
+
+| Element                | Maximum supported |
+|------------------------|-------------------|
+| PDU sessions           | Enterprise radios typically support up to 1000 simultaneous PDU sessions per radio |
+| Bandwidth              | Over 25 Gbps per ASE |
+| RAN nodes (eNB/gNB)    | 200 per packet core |
+| Active UEs             | 10,000 per deployment (all sites) |
+| SIMs                   | 20,000 per ASE |
+| SIM provisioning       | 10,000 per JSON file via Azure portal, 4 MB per REST API call  |
+
+For more information, see [Service Limits](azure-stack-edge-virtual-machine-sizing.md#service-limits).
 
 ## Issues fixed in the AP5GC 2403 release
 

articles/private-5g-core/whats-new.md

@@ -23,14 +23,33 @@ To help you stay up to date with the latest developments, this article covers:
 This page is updated regularly with the latest developments in Azure Private 5G Core.
 
 ## April 2024
+### Packet core 2403
+
+**Type:** New release
+
+**Date available:** April 4, 2024
+
+The 2403 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2403 release notes](azure-private-5g-core-release-notes-2403.md).
 
 ### TCP Maximum Segment Size (MSS) Clamping
 
-**Type:** New feature
+TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core now automatically sets this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+
+### Improved Packet Core Scaling 
+
+In this release, the maximum supported limits for a range of parameters in an Azure Private 5G Core deployment increase. Testing confirms these limits, but other factors could affect what is achievable in a given scenario. 
+The following table lists the new maximum supported limits.
 
-**Date available:** April 04, 2024
+| Element                | Maximum supported |
+|------------------------|-------------------|
+| PDU sessions           | Enterprise radios typically support up to 1000 simultaneous PDU sessions per radio |
+| Bandwidth              | Over 25 Gbps per ASE |
+| RAN nodes (eNB/gNB)    | 200 per packet core |
+| Active UEs             | 10,000 per deployment (all sites) |
+| SIMs                   | 20,000 per ASE |
+| SIM provisioning       | 10,000 per JSON file via Azure portal, 4 MB per REST API call  |
 
-TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. The packet core will now automatically set this value, where necessary, to ensure packets aren't too large for the core to transmit. This reduces packet loss due to oversized packets arriving at the core's interfaces, and reduces the need for fragmentation and reassembly, which are costly procedures.
+For more information, see [Service Limits](azure-stack-edge-virtual-machine-sizing.md#service-limits).
 
 ## March 2024