You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/private-5g-core/whats-new.md
+41-28Lines changed: 41 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,27 @@ To help you stay up to date with the latest developments, this article covers:
20
20
- New features, improvements and fixes for the online service.
21
21
- New releases for the packet core, referencing the packet core release notes for further information.
22
22
23
-
This page is updated regularly with the latest developments in Azure Private 5G Core. <!-- TODO: maybe update with agreed update frequency -->
24
-
<!-- In future: If you're looking for items older than six months, you can find them in Archive for What's new in Azure Private 5G Core. -->
23
+
This page is updated regularly with the latest developments in Azure Private 5G Core.
25
24
26
25
## January 2023
27
26
28
-
### Multiple Network Slices
27
+
### Packet core 2301
29
28
30
-
**Type:** Feature
29
+
**Type:** New release
30
+
31
+
**Date available:** January 31, 2023
32
+
33
+
The 2301 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2301 release notes](azure-private-5g-core-release-notes-2301.md).
34
+
35
+
### Multiple network slices
36
+
37
+
**Type:** New feature
31
38
32
39
**Date available:** January 31, 2023
33
40
34
-
The Azure Private 5G Core now supports multiple network slices for 5G packet core deployments. Network slices allow customers to host multiple independent logical networks in the same Azure Private 5G Core deployment. Slices are assigned to SIM policies and static IP addresses, providing isolated end-to-end networks that can be customized for different bandwidth and latency requirements.
41
+
Azure Private 5G Core now supports multiple network slices for 5G packet core deployments. Network slices allow you to host multiple independent logical networks in the same Azure Private 5G Core deployment. Slices are assigned to SIM policies and static IP addresses, providing isolated end-to-end networks that can be customized for different bandwidth and latency requirements.
42
+
43
+
For more details, see [Create and manage network slices - Azure portal](create-manage-network-slices.md).
35
44
36
45
### Enhanced provisioning status reporting
37
46
@@ -41,64 +50,68 @@ The Azure Private 5G Core now supports multiple network slices for 5G packet cor
41
50
42
51
The Azure Private 5G Core online service now reports the provisioning status of SIMs per-site, on both the **SIM** and **Site** resource views, to allow you to accurately determine where individual SIMs have been provisioned.
43
52
44
-
### West Europe region
53
+
### Diagnostic package collection
45
54
46
-
**Type:** New Feature
55
+
**Type:** New feature
47
56
48
-
**Date available:** January 17, 2023
57
+
**Date available:** January 31, 2023
49
58
50
-
The Azure Private 5G Core service is now live in West Europe. It is now possible to deploy and manage AP5GC resources in West Europe.
59
+
You can now gather diagnostics for a site remotely using the Azure portal. Diagnostics packages will be collected from the edge site and uploaded to an Azure storage account, which can be shared as a SAS URI to AP5GC support or others for assistance with issues. Follow [Gather diagnostics using the Azure portal](gather-diagnostics.md) to gather a remote diagnostics package for an Azure Private 5G Core site using the Azure portal.
51
60
52
-
### Diagnostic Package Collection
61
+
### West Europe region
53
62
54
63
**Type:** New Feature
55
64
56
-
**Date available:**February 1, 2023
65
+
**Date available:**January 17, 2023
57
66
58
-
You can now gather gather diagnostics for a Site remotely using the Azure portal. Diagnostics packages will be collected from the edge site and uploaded to an Azure storage account, which can be shared as a SAS URI to AP5GC support or others for assistance with issues. Follow [Gather diagnostics using the Azure portal](gather-diagnostics.md) to gather a remote diagnostics package for an Azure Private 5G Core site using the Azure portal.
67
+
The Azure Private 5G Core service is now live in West Europe. It's now possible to deploy and manage AP5GC resources in West Europe.
59
68
60
69
### Diagnose and resolve problems
61
70
62
-
**Type:**Feature
71
+
**Type:**New feature
63
72
64
73
**Date available:** January 17, 2023
65
74
66
75
The **Diagnose and solve problems** option in the left content menu can now provide troubleshooting suggestions for your AP5GC resources.
67
76
68
77
## December 2022
69
78
70
-
### Packet Core Reinstallation
79
+
### Packet core reinstall
71
80
72
-
**Type:**Feature
81
+
**Type:**New feature
73
82
74
83
**Date available:** December 16, 2022
75
84
76
-
If you're experiencing issues with your packet core deployment, you can now re-install the packet core to return it to a known state. Re-installing the packet core deletes the existing packet core deployment and attempts to deploy the packet core at the edge with the existing site configurations. Already created **Site**dependent resources such as the **PacketCoreControlPlane**, **PacketCoreDataPlane** and **AttachedDataNetwork** will continue to be used in the deployment.
85
+
If you're experiencing issues with your packet core deployment, you can now reinstall the packet core to return it to a known state. Reinstalling the packet core deletes the existing packet core deployment and attempts to deploy the packet core at the edge with the existing site configuration. Already created **Site**-dependent resources such as the **Packet Core Control Plane**, **Packet Core Data Plane** and **Attached Data Network** will continue to be used in the deployment.
77
86
78
-
You can check the Installation state on the **Packet Core Control Plane overview**. Upon successful redeployment, the Installation state will change from **Reinstalling** to either **Installed** or **Failed**, depending on the outcome. You can re-install the packet core regardless if the **Installation state** is in either **Installed** or **Failed** status.
87
+
You can check the installation state on the **Packet Core Control Plane** resource's overview page. Upon successful redeployment, the installation state will change from **Reinstalling** to either **Installed** or **Failed**, depending on the outcome. You can reinstall the packet core if the installation state is **Installed** or **Failed**.
79
88
80
-
If re-install is attempted after upgrade, re-deployment would be attempted with the upgraded packet core version. The reinstallation is done using the latest packet core version currently defined in the ARM API version.
89
+
If you attempt a reinstall after an upgrade, redeployment will be attempted with the upgraded packet core version. The reinstall is done using the latest packet core version currently defined in the ARM API version.
81
90
82
91
This feature has the following limitations:
83
92
84
-
- The provisioning state of resources **PacketCoreControlPlane**, **PacketCoreDataPlane** and **AttachedDataNetwork** will not change with re-install.
93
+
- The provisioning state of resources **Packet Core Control Plane**, **Packet Core Data Plane** and **Attached Data Network** will not change with reinstall.
85
94
- The status of the reinstallation operation can tracked only via **Activity Logs**.
86
-
-Re-installing the packet core may take 45 minutes or more.
87
-
- Updated Installation states are only reflected when the **Packet Core Control Plane overview** page is refreshed.
95
+
-Reinstalling the packet core may take 45 minutes or more.
96
+
- Updated Installation states are only reflected when the **Packet Core Control Plane** resource's overview page is refreshed.
88
97
89
-
### HTTPS Certificates at the Edge
98
+
To reinstall your packet core instance, see [Reinstall the packet core instance in a site - Azure portal](reinstall-packet-core.md).
90
99
91
-
**Type:** Feature
100
+
### HTTPS certificates at the edge
101
+
102
+
**Type:** New feature
92
103
93
104
**Date available:** December 19, 2022
94
105
95
-
It is now possible to secure access to a site’s local monitoring tools with a custom, user-provided HTTPS certificate. Certificates can be uploaded to an Azure Key Vault and specified in the **Packet Core Control Plane****local access** configuration to be provisioned down to the edge.
106
+
It's now possible to secure access to a site’s local monitoring tools with a custom, user-provided HTTPS certificate. Certificates can be uploaded to an Azure Key Vault and specified in the **Packet Core Control Plane**'s local access configuration to be provisioned down to the edge.
96
107
97
108
This feature has the following limitations:
98
109
99
110
- Certificate deletion requires a pod restart to be reflected at the edge.
100
111
- User-assigned managed identities are not currently supported for certificate provisioning.
101
-
- Actions on KeyVaults/Certificates not involving a modification on the **Packet Core Control Plane** object can take up to an hour to be reflected at the edge.
112
+
- Actions on key vaults and certificates not involving a modification on the **Packet Core Control Plane** object can take up to an hour to be reflected at the edge.
113
+
114
+
You can add a custom certificate to secure access to your local monitoring tools during [site creation](collect-required-information-for-a-site.md#collect-local-monitoring-values). For existing sites, you can add a custom HTTPS certificate by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
102
115
103
116
## November 2022
104
117
@@ -243,7 +256,7 @@ The 2211 release for the Azure Private 5G Core packet core is now available. For
243
256
244
257
### Multiple data networks
245
258
246
-
**Type:**Feature
259
+
**Type:**New feature
247
260
248
261
**Date available:** December 5, 2022
249
262
@@ -265,15 +278,15 @@ To add data networks to an existing site, see [Modify the packet core instance i
265
278
266
279
### Easier site deletion
267
280
268
-
**Type:**Feature
281
+
**Type:**New feature
269
282
270
283
**Date available:** December 5, 2022
271
284
272
285
Previously, you had to delete all the ARM resources associated with a site before deleting the site resource. You can now delete a site and its associated resources in one step. See [Delete a site](delete-a-site.md).
0 commit comments