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
Radio access network (RAN) insights is a feature of Azure Private 5G Core that allows you to view your RAN metric data in Azure Portal to make actionable insights. RAN Insights collects and displays a subset of metrics from the RAN vendor’s Element Management System (EMS) and displays them as standard metrics in Azure. The selected metrics are based on customer feedback and represent the most important KPIs used for health and troubleshooting. RAN insights provides you with a unified and simplified experience to monitor and troubleshoot your RAN across multiple vendors.
13
+
Radio access network (RAN) insights is a feature of Azure Private 5G Core that allows you to view your RAN metric data in Azure portal to make actionable insights. RAN Insights collects and displays a subset of metrics from the RAN vendor’s Element Management System (EMS) and displays them as standard metrics in Azure. The selected metrics are based on customer feedback and represent the most important KPIs used for health and troubleshooting. RAN insights provides you with a unified and simplified experience to monitor and troubleshoot your RAN across multiple vendors.
14
14
15
15
16
16
## Why use RAN insights?
@@ -19,27 +19,25 @@ RAN insights offers several benefits for managing your network, such as:
19
19
20
20
- Simple to manage – You can now utilize the Azure experience to easily view RAN metrics from multiple vendors, eliminating the need to switch between and learn various tools or dashboards. RAN insights provides a consistent and user-friendly experience that makes it easy to derive insights from metrics across your network.
21
21
- Consistent – You can customize how you group and display your RAN metrics according to your needs. For example, you can have one RAN insights resource representing multiple access points across multiple RAN vendors or have one RAN insights resource to represent access points for each RAN vendor.
22
-
- Actionable – You can use the metrics to troubleshoot problems on your network and take corrective actions. For example, if you see a large discrepancy in the handover correlated metric between core and RAN, a coverage gaps may exist and you may need to optimize your RF accordingly.
23
-
- Secure and compliant – RAN insights uses Azure Key Vault to securely transfer and store RAN metrics data, ensuring that your data is protected and encrypted. RAN insights also complies with the General Data Protection Regulation (GDPR) and is built on the basis of 3GPP metrics from our RAN partners.
22
+
- Actionable – You can use the metrics to troubleshoot problems on your network and take corrective actions. For example, if you see a large discrepancy in the handover correlated metric between core and RAN, a coverage gaps might exist and you might need to optimize your radio frequency (RF) accordingly.
23
+
- Secure and compliant – RAN insights use Azure Key Vault to securely transfer and store RAN metrics data, ensuring that your data is protected and encrypted. RAN insights also comply with the General Data Protection Regulation (GDPR) and is built from 3GPP metrics from our RAN partners.
RAN insights works by extending the RAN Element Management System (EMS) offered by the RAN partner to include a Microsoft compliant External Metrics Agent (EMA) that streams relevant RAN metrics to Azure. The RAN vendor and Microsoft agree on a common schema based on 3GPP standards. The EMA collects the RAN metrics from the EMS and sends them to Azure via Metrics Ingestion Endpoint (MIE).
28
-
29
-
This process is to be completed by the partner. All you need to do is enable the MIE while creating your RAN insights resource and use the generated connection string from key vault to establish the connection between EMA and Azure.
27
+
RAN insights works by extending the RAN Element Management System (EMS) offered by the RAN partner to include a Microsoft compliant External Metrics Agent (EMA) that streams relevant RAN metrics to Azure. The RAN vendor and Microsoft agree on a common schema based on 3GPP standards. The EMA collects the RAN metrics from the EMS and sends them to Azure via Metrics Ingestion Endpoint (MIE). This process is completed by the partner.
Radio access network (RAN) insights allows users to connect and view their third party RAN metrics to their private mobile networks in Azure. RAN insights extends the RAN Element Management System (EMS) offered by the RAN partner to include a Microsoft compliant metrics agent that streams relevant RAN metrics to Azure. The streamed metrics are stored and presented in a secure and compliant manner, in adherence to Microsoft’s security standards and policies.
15
15
16
-
Each RAN insights resource is associated with one physical site resource and is comprised of one or more access points which represent the radio unit (nodeB) instance connected. In this how-to guide, you’ll learn how to create a RAN insights resource in your private mobile network using Azure Portal.
16
+
Each RAN insights resource is associated with one physical site resource and is composed of one or more access points, which represent the radio unit (nodeB) instance connected. In this how-to guide, you'll learn how to create a RAN insights resource in your private mobile network using Azure portal.
- Active deployment of [Azure Private 5G Core](complete-private-mobile-network-prerequisites.md)
22
-
-A way to check if the network is ready is to verify that a device (UE) connected to the network through the RAN can transmit and receive data: if this does not work, fix any problems before trying to activate the RAN insights feature.
23
-
- Deploy a compatible version of the RAN EMS from the RAN partner. You will need to verify with your RAN partner that your RAN EMS contains a Microsoft-compatible External Metrics Agent (EMA) to send metrics to Azure. If not, your designated partner would need to install a metrics agent on the EMS you are using. Information on how and where to establish the connection between Azure and the EMS is specific to the particular RAN vendor, please reach out to them for more details.
22
+
-Check if the network is ready by verifying that a device / user equipment (UE) connected to the network through the RAN can transmit and receive data. if step doesn't work, fix any problems before trying to activate the RAN insights feature.
23
+
- Deploy a compatible version of the RAN EMS from the RAN partner. You'll need to verify with your RAN partner that your RAN EMS contains a Microsoft-compatible External Metrics Agent (EMA) to send metrics to Azure. If not, your designated partner would need to install a metrics agent on the EMS you're using. Information on how and where to establish the connection between Azure and the EMS is specific to the particular RAN vendor, reach out to them for more details.
24
24
- Access to RAN insights for your Azure Subscription. Contact your Microsoft representative and ask them to register your Azure subscription for access to RAN insights.
25
-
- Ensure you are registered with resource providers listed below. Follow [Resource providers and resource types](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types) for steps on how to register.
25
+
- Ensure you're registered with resource providers listed. Follow [Resource providers and resource types](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types) for steps on how to register.
26
26
- Microsoft.insights
27
27
- Microsoft.NetworkAnalytics
28
28
- Microsoft.KeyVault
@@ -36,9 +36,9 @@ Each RAN insights resource is associated with one physical site resource and is
36
36
1. Navigate to your site resource
37
37
1. On the **Physical Infrastructure** page, select **Radio access network insights** and press create
38
38
:::image type="content" source="media/ran-insights/RAN-Insights-Create-Resource.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
39
-
1. In the **Basics** configuration tab, fill in the needed information and select the checkbox to enable Metric Ingestion Endpoint (MIE) which processes RAN metrics streamed from the partner EMS and stores them in Azure Monitor. Please note your MIE instance will be deployed in East US or West EU regardless of your subscription’s region. You will have the option to enable the MIE later if you choose not to complete this step now. Then select **Next : Access Points >**.
39
+
1. In the **Basics** configuration tab, fill in the needed information and select the checkbox to enable Metric Ingestion Endpoint (MIE) which processes RAN metrics streamed from the partner EMS and stores them in Azure Monitor. Note your MIE instance is deployed in East US or West EU regardless of your subscription’s region. You'll have the option to enable the MIE later if you choose not to complete this step now. Then select **Next : Access Points >**.
40
40
:::image type="content" source="media/ran-insights/RAN-Insights-Basics-CREATE-Tab.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
41
-
1. In the **Access Points** section, you can enter in the latitude and longitude coordinates of your access points. If access points are already connected to your RAN EMS and turned on, the access point names will auto populate once the RAN insights resource set up and connection is complete.
41
+
1. In the **Access Points** section, you can enter in the latitude and longitude coordinates of your access points. If access points are turned on and connected to your RAN EMS, the access point names will auto populate once the RAN insights resource setup.
42
42
:::image type="content" source="media/ran-insights/RAN-Insights-AccessPoint-CREATE-Tab.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
43
43
1. Select **Review + create**
44
44
1. Azure will now validate the configuration values you've entered. Once your configuration has been validated, you can select **Create** to create the RAN insights resource. The Azure portal will display the following confirmation screen when the RAN insights resource has been created.
@@ -48,9 +48,9 @@ Each RAN insights resource is associated with one physical site resource and is
In the case the MIE was not enabled for the RAN insights resource during creation, then the RAN **Overview** page under the **MIE details** tab will show a message stating that MIE was not enabled.
51
+
In the case the MIE was not enabled for the RAN insights resource during creation, then the RAN **Overview** page under the **MIE details** tab shows a message stating that MIE was not enabled.
52
52
:::image type="content" source="media/ran-insights/RAN-Insights-MIE-notEnabled.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
53
-
The MIE resource is automatically deleted from the service if it is “Disabled” from the online service portal or if you choose to delete the RAN insights resource. If you disable the MIE resource you will still have access to your historical data for up to 30 days, but the RAN insights resource will stop reporting metrics.
53
+
The MIE resource is automatically deleted from the service if it is "Disabled" from the online service portal or if you choose to delete the RAN insights resource. If you disable the MIE resource you'll still have access to your historical data for up to 30 days, but the RAN insights resource will stop reporting metrics.
54
54
55
55
You can enable and disable your MIE under the Configuration blade:
56
56
:::image type="content" source="media/ran-insights/RAN-Insights-ConfigTab-MIE.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
@@ -64,12 +64,12 @@ Once your RAN insights resource is configured and set up, you can view additiona
64
64
65
65
This tab holds important details, such as:
66
66
- MIE name – name of the MIE
67
-
- MIE status – status of MIE, should be “Succeeded”
68
-
-EventHub url - URL for the event hub
67
+
- MIE status – status of MIE, should be "Succeeded"
68
+
-Eventhub url - URL for the event hub
69
69
- Eventhub name – name of the event hub
70
70
- Keyvault – URL for key vault containing connection string
71
71
72
-
Please note if you are unable to access the information in the MIE key vault URL then you may not have the correct credentials. If this is the case, you need to take the necessary steps to grant access for the required role. Refer to [Azure RBAC documentation | Microsoft Learn](https://learn.microsoft.com/en-us/azure/role-based-access-control/) for steps on how to do this.
72
+
Note if you're unable to access the information in the MIE key vault URL then you may not have the correct credentials. If so, you need to take the necessary steps to grant access for the required role. Refer to [Azure RBAC documentation | Microsoft Learn](https://learn.microsoft.com/en-us/azure/role-based-access-control/) for steps on how to do this.
73
73
:::image type="content" source="media/ran-insights/RAN-Insights-KeyVault-notWorking.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
74
74
75
75
@@ -90,7 +90,7 @@ To delete from your site resource:
90
90
:::image type="content" source="media/ran-insights/RAN-Insights-DELETE-fromSiteResource.png" alt-text="Screenshot of the Azure portal showing creating a RAN insight resource on the site resource.":::
91
91
92
92
93
-
## Next step
93
+
## Next steps
94
94
-[Monitor with RAN metrics](ran-insights-monitor-with-ran-metrics-concepts.md)
95
95
-[Monitor with geo maps](ran-insights-monitor-with-geo-maps-concepts.md)
96
96
-[Monitor with correlated metrics](ran-insights-monitor-with-correlated-metrics-concepts.md)
0 commit comments