Skip to content

Commit 32c1727

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #271056 from PaulCarterMicrosoft/main
AP5GC2403 Release Note & associated changes
2 parents 861d0be + 4f78467 commit 32c1727

7 files changed

+90
-11
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The following table shows the support status for different Packet Core releases.
3030

3131
| Release | Support Status |
3232
|---------|----------------|
33-
| AP5GC 2308 | Supported until AP5GC 2401 released |
33+
| AP5GC 2308 | Supported until AP5GC 2403 released |
3434
| AP5GC 2307 | Supported until AP5GC 2310 released |
3535
| AP5GC 2306 and earlier | Out of Support |
3636

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 11/30/2023
1010

1111
# Azure Private 5G Core 2310 release notes
1212

13-
The following release notes identify the new features, critical open issues, and resolved issues for the 2308 release of Azure Private 5G Core (AP5GC). The release notes are continuously updated, with critical issues requiring a workaround added as they’re discovered. Before deploying this new version, review the information contained in these release notes.
13+
The following release notes identify the new features, critical open issues, and resolved issues for the 2310 release of Azure Private 5G Core (AP5GC). The release notes are continuously updated, with critical issues requiring a workaround added as they’re discovered. Before deploying this new version, review the information contained in these release notes.
1414

1515
This article applies to the AP5GC 2310 release (2310.0-8). This release is compatible with the Azure Stack Edge Pro 1 GPU and Azure Stack Edge Pro 2 running the ASE 2309 release and supports the 2023-09-01, 2023-06-01 and 2022-11-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions.
1616

@@ -26,8 +26,8 @@ The following table shows the support status for different Packet Core releases
2626

2727
| Release | Support Status |
2828
|---------|----------------|
29-
| AP5GC 2310 | Supported until AP5GC 2403 is released |
30-
| AP5GC 2308 | Supported until AP5GC 2401 is released |
29+
| AP5GC 2310 | Supported until AP5GC 2404 is released |
30+
| AP5GC 2308 | Supported until AP5GC 2403 is released |
3131
| AP5GC 2307 and earlier | Out of Support |
3232

3333
## What's new

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

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Azure Private 5G Core 2403 release notes
3+
description: Discover what's new in the Azure Private 5G Core 2403 release
4+
author: paulcarter
5+
ms.author: paulcarter
6+
ms.service: private-5g-core
7+
ms.topic: release-notes
8+
ms.date: 04/04/2023
9+
---
10+
11+
# Azure Private 5G Core 2403 release notes
12+
13+
The following release notes identify the new features, critical open issues, and resolved issues for the 2403 release of Azure Private 5G Core (AP5GC). The release notes are continuously updated, with critical issues requiring a workaround added as they’re discovered. Before deploying this new version, review the information contained in these release notes.
14+
15+
This article applies to the AP5GC 2403 release (2403.0-2). This release is compatible with the Azure Stack Edge (ASE) Pro 1 GPU and Azure Stack Edge Pro 2 running the ASE 2403 release and supports the 2023-09-01, 2023-06-01 and 2022-11-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions.
16+
17+
For more information about compatibility, see [Packet core and Azure Stack Edge compatibility](azure-stack-edge-packet-core-compatibility.md).
18+
19+
For more information about new features in Azure Private 5G Core, see [What's New Guide](whats-new.md).
20+
21+
## Support lifetime
22+
23+
Packet core versions are supported until two subsequent versions are released (unless otherwise noted). You should plan to upgrade your packet core in this time frame to avoid losing support.
24+
25+
### Currently supported packet core versions
26+
The following table shows the support status for different Packet Core releases and when they're expected to no longer be supported.
27+
28+
| Release | Support Status |
29+
|---------|----------------|
30+
| AP5GC 2403 | Supported until AP5GC 2407 is released |
31+
| AP5GC 2310 | Supported until AP5GC 2404 is released |
32+
| AP5GC 2308 and earlier | Out of Support |
33+
34+
## What's new
35+
36+
### TCP Maximum Segment Size (MSS) Clamping
37+
38+
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.
39+
40+
## Issues fixed in the AP5GC 2403 release
41+
42+
The following table provides a summary of issues fixed in this release.
43+
44+
|No. |Feature | Issue | SKU Fixed In |
45+
|-----|-----|-----|-----|----|
46+
| 1 | Local distributed tracing | In Multi PDN session establishment/Release call flows with different DNs, the distributed tracing web GUI fails to display some of 4G NAS messages (Activate/deactivate Default EPS Bearer Context Request) and some S1AP messages (ERAB request, ERAB Release). | 2403.0-2 |
47+
| 2 | Packet Forwarding | A slight(0.01%) increase in packet drops is observed in latest AP5GC release installed on ASE Platform Pro 2 with ASE-2309 for throughput higher than 3.0 Gbps. | 2403.0-2 |
48+
49+
## Known issues in the AP5GC 2403 release
50+
<!--**TO BE UPDATED**>
51+
|No. |Feature | Issue | Workaround/comments |
52+
|-----|-----|-----|-----|
53+
| 1 | | | |
54+
<-->
55+
56+
The following table provides a summary of known issues carried over from the previous releases.
57+
58+
|No. |Feature | Issue | Workaround/comments |
59+
|-----|-----|-----|-----|
60+
| 1 | Local distributed tracing | When a web proxy is enabled on the Azure Stack Edge appliance that the packet core is running on and Azure Active Directory is used to authenticate access to AP5GC Local Dashboards, the traffic to Azure Active Directory doesn't transmit via the web proxy. If there's a firewall blocking traffic that doesn't go via the web proxy then enabling Azure Active Directory causes the packet core install to fail. | Disable Azure Active Directory and use password based authentication to authenticate access to AP5GC Local Dashboards instead. |
61+
62+
## Next steps
63+
64+
- [Upgrade the packet core instance in a site - Azure portal](upgrade-packet-core-azure-portal.md)
65+
- [Upgrade the packet core instance in a site - ARM template](upgrade-packet-core-arm-template.md)

‎articles/private-5g-core/azure-stack-edge-packet-core-compatibility.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,8 @@ The following table provides information on which versions of the ASE device are
3030

3131
| Packet core version | ASE Pro GPU compatible versions | ASE Pro 2 compatible versions |
3232
|-----|-----|-----|
33-
! 2310 | 2309, 2312 | 2309, 2312 |
33+
| 2403 | 2403, 2405 | 2403, 2405 |
34+
| 2310 | 2309, 2312, 2403 | 2309, 2312, 2403 |
3435
| 2308 | 2303, 2309 | 2303, 2309 |
3536
| 2307 | 2303 | 2303 |
3637
| 2306 | 2303 | 2303 |

‎articles/private-5g-core/support-lifetime.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,6 @@ The following table shows the support status for different Packet Core releases
1919

2020
| Release | Support Status |
2121
|---------|----------------|
22-
| AP5GC 2310 | Supported until AP5GC 2403 is released |
23-
| AP5GC 2308 | Supported until AP5GC 2401 is released |
24-
| AP5GC 2307 and earlier | Out of Support |
22+
| AP5GC 2403 | Supported until AP5GC 2407 is released |
23+
| AP5GC 2310 | Supported until AP5GC 2404 is released |
24+
| AP5GC 2308 and earlier | Out of Support |

‎articles/private-5g-core/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,9 @@ items:
1010
href: whats-new.md
1111
- name: Packet core release notes
1212
items:
13-
- name: '2310 - Current'
13+
- name: '2403 - Current'
14+
href: azure-private-5g-core-release-notes-2403.md
15+
- name: '2310'
1416
href: azure-private-5g-core-release-notes-2310.md
1517
- name: '2308'
1618
href: azure-private-5g-core-release-notes-2308.md

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

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,23 @@ ms.date: 12/21/2023
1717

1818
To help you stay up to date with the latest developments, this article covers:
1919

20-
- New features, improvements and fixes for the online service.
20+
- New features, improvements, and fixes for the online service.
2121
- New releases for the packet core, referencing the packet core release notes for further information.
2222

2323
This page is updated regularly with the latest developments in Azure Private 5G Core.
2424

25+
## April 2024
26+
27+
### TCP Maximum Segment Size (MSS) Clamping
28+
29+
**Type:** New feature
30+
31+
**Date available:** April 04, 2024
32+
33+
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.
34+
2535
## March 2024
36+
2637
### Azure Policy support
2738

2839
**Type:** New feature
@@ -42,7 +53,7 @@ See [Azure Policy policy definitions for Azure Private 5G Core](azure-policy-ref
4253

4354
**Date available:** March 22, 2024
4455

45-
The SUPI (subscription permanent identifier) secret needs to be encrypted before being transmitted over the radio network as a SUCI (subscription concealed identifier). The concealment is performed by the UEs on registration, and deconcealment is performed by the packet core. You can now securely manage the required private keys through the Azure Portal and provision SIMs with public keys.
56+
The SUPI (subscription permanent identifier) secret needs to be encrypted before being transmitted over the radio network as a SUCI (subscription concealed identifier). The concealment is performed by the UEs on registration, and deconcealment is performed by the packet core. You can now securely manage the required private keys through the Azure portal and provision SIMs with public keys.
4657

4758
For more information, see [Enable SUPI concealment](supi-concealment.md).
4859

0 commit comments

Comments
 (0)