Merge pull request #188493 from MicrosoftDocs/release-preview-private-5g-core

merge release-preview-private-5g-core to main (OOB publish at 3:30PM of 2/27)

Author: huypub

articles/index.yml

@@ -1323,6 +1323,13 @@ productDirectory:
         - networking
       url: private-link/index.yml
     # Card
+    - title: Azure Private 5G Core (Preview)
+      summary: Rapidly deploy and manage private 5G networks at the enterprise edge
+      imageSrc: ./media/index/private-5g-core.svg
+      azureCategories:
+        - networking
+      url: private-5g-core/index.yml
+    # Card
     - title: Load Balancer
       summary: Deliver high availability and network performance to your applications
       imageSrc: https://static.docs.com/ui/media/product/azure/load-balancer.svg

articles/media/index/private-5g-core.svg

@@ -0,0 +1,38 @@
+---
+title: Activate SIMs
+titleSuffix: Azure Private 5G Core Preview
+description: This how-to guide shows how to activate SIMs used by user equipment so they can use your private mobile network. 
+author: djrmetaswitch
+ms.author: drichards
+ms.service: private-5g-core
+ms.topic: how-to
+ms.date: 01/17/2022
+ms.custom: template-how-to
+---
+
+# Activate SIMs for Azure Private 5G Core Preview
+
+SIM resources represent physical or eSIMs used by user equipment (UE). Activating a SIM resource allows the UE to use the corresponding physical or eSIM to access your private mobile network. In this how-to guide, you'll learn how to activate the SIMs you've provisioned. 
+
+## Prerequisites
+
+- Ensure you can sign in to the Azure portal using an account with access to the active subscription you identified in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).
+- Ensure you've provisioned and assigned a SIM policy to the SIMs you want to activate, as described in [Provision SIMs - Azure portal](provision-sims-azure-portal.md).
+- Get the name of the private mobile network containing the SIMs you want to activate.
+
+## Activate your chosen SIMs
+
+1. Sign in to the Azure portal at [https://aka.ms/AP5GCPortal](https://aka.ms/AP5GCPortal).
+1. Search for and select the Mobile Network resource representing the private mobile network for which you want to activate SIMs.
+
+    :::image type="content" source="media/mobile-network-search.png" alt-text="Screenshot of the Azure portal. It shows the results of a search for a mobile network resource.":::
+
+1. In the **Resource** menu, select **SIMs**.
+1. You're shown a list of provisioned SIMs in the private mobile network. Tick the checkbox next to the name of each SIM you want to activate. 
+3. In the **Command** bar, select **Activate**.
+4. In the pop-up that appears, select **Activate** to confirm that you want to activate your chosen SIMs.
+5. The activation process can take a few minutes. During this time, the value in the **Activation** status column for each SIM will display as **Activating**. Keep selecting **Refresh** in the command bar until the **Activation** status field for all of the relevant SIMs changes to **Activated**.
+
+## Next steps
+
+- [Learn more about policy control](policy-control.md)

articles/private-5g-core/activate-sims.md

@@ -0,0 +1,70 @@
+---
+title: Collect information for a site
+titleSuffix: Azure Private 5G Core Preview
+description: Learn about the information you'll need to create a site in an existing private mobile network using the Azure portal.
+author: djrmetaswitch
+ms.author: drichards
+ms.service: private-5g-core
+ms.topic: how-to 
+ms.date: 02/07/2022
+ms.custom: template-how-to
+---
+
+# Collect the required information for a site
+
+Azure Private 5G Core Preview private mobile networks include one or more sites. Each site represents a physical enterprise location (for example, Contoso Corporation's Chicago factory) containing an Azure Stack Edge device that hosts a packet core instance. This how-to guide takes you through the process of collecting the information you'll need to create a new site. You'll use this information to complete the steps in [Create a site](create-a-site.md).
+
+## Prerequisites
+
+You must have completed all of the steps in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and [Order and set up your Azure Stack Edge Pro device(s)](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices) for your new site.
+
+## Collect Mobile Network Site resource values
+
+Collect all the values in the following table for the Mobile Network Site resource that will represent your site.
+
+   |Value  |Field name in Azure portal  |
+   |---------|---------|
+   |The Azure subscription to use to create the Mobile Network Site resource. You must use the same subscription for all resources in your private mobile network deployment.                  |**Project details: Subscription**|
+   |The Azure resource group in which to create the Mobile Network Site resource. We recommend that you use the same resource group that already contains your private mobile network.                |**Project details: Resource group**|
+   |The name for the site.           |**Instance details: Name**|
+   |The region in which you’re creating the Mobile Network Site resource. We recommend that you use the East US region.                         |**Instance details: Region**|
+   |The private mobile network resource representing the network to which you’re adding the site. |**Instance details: Mobile network**|
+
+## Collect custom location information
+
+Collect the name of the custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site. You commissioned the AKS-HCI cluster as part of the steps in [Order and set up your Azure Stack Edge Pro device(s)](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices).
+
+
+## Collect access network values
+
+Collect all the values in the following table to define the packet core instance's connection to the access network over the N2 and N3 interfaces.
+
+> [!IMPORTANT]
+> Where noted, you must use the same values you used when deploying the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device for this site. You did this as part of the steps in [Order and set up your Azure Stack Edge Pro device(s)](complete-private-mobile-network-prerequisites.md#order-and-set-up-your-azure-stack-edge-pro-devices).
+
+   |Value  |Field name in Azure portal  |
+   |---------|---------|
+   | The IP address for the packet core instance N2 signaling interface. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                 |**N2 address (signaling)**
+   | The network address of the access subnet in Classless Inter-Domain Routing (CIDR) notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.          |**N2 subnet** and **N3 subnet**|
+   | The access subnet default gateway. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                        |**N2 gateway** and **N3 gateway**|
+
+## Collect data network values
+
+Collect all the values in the following table to define the packet core instance's connection to the data network over the N6 interface.
+
+> [!IMPORTANT]
+> Where noted, you must use the same values you used when deploying the AKS-HCI cluster on your Azure Stack Edge Pro device. You did this as part of the steps in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).
+
+   |Value  |Field name in Azure portal  |
+   |---------|---------|
+   |The name of the data network.                  |**Data network**|
+   |The network address of the data subnet in CIDR notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                  |**N6 subnet**|
+   |The data subnet default gateway. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                               |**N6 gateway**|
+   | The network address of the subnet from which IP addresses must be allocated to User Equipment (UEs), given in CIDR notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses). The following example shows the network address format. </br></br>`198.51.100.0/24` </br></br>Note that the UE subnets aren't related to the access subnet.    |**UE IP subnet**|
+   |Whether Network Address and Port Translation (NAPT) should be enabled for this data network. NAPT allows you to translate a large pool of private IP addresses for UEs to a small number of public IP addresses. The translation is performed at the point where traffic enters the core network, maximizing the utility of a limited supply of public IP addresses.    |**NAPT**|
+
+## Next steps
+
+You can now use the information you've collected to create the site.
+
+- [Create a site](create-a-site.md)

articles/private-5g-core/collect-required-information-for-a-site.md

@@ -0,0 +1,85 @@
+---
+title: Collect information for your private mobile network
+titleSuffix: Azure Private 5G Core Preview
+description: This how-to guide shows how to collect the information you need to deploy a private mobile network through Azure Private 5G Core Preview using the Azure portal.
+author: djrmetaswitch
+ms.author: drichards
+ms.service: private-5g-core
+ms.topic: how-to 
+ms.date: 12/31/2021
+ms.custom: template-how-to
+---
+
+# Collect the required information to deploy a private mobile network
+
+This how-to guide takes you through the process of collecting the information you'll need to deploy a private mobile network through Azure Private 5G Core Preview using the Azure portal. You'll use this information to complete the steps in [Deploy a private mobile network - Azure portal](how-to-guide-deploy-a-private-mobile-network-azure-portal.md).
+
+## Prerequisites
+
+You must have completed all of the steps in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).
+
+## Collect Mobile Network resource values
+
+Collect all of the following values for the Mobile Network resource that will represent your private mobile network.
+
+   |Value  |Field name in Azure portal  |
+   |---------|---------|
+   |The Azure subscription to use to deploy the Mobile Network resource. You must use the same subscription for all resources in your private mobile network deployment. This is the subscription you identified in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md).                 |**Project details: Subscription**
+   |The Azure resource group to use to deploy the Mobile Network resource. You should use a new resource group for this resource. It's useful to include the purpose of this resource group in its name for future identification (for example, *contoso-pmn-rg*).                |**Project details: Resource group**|
+   |The name for the private mobile network.           |**Instance details: Mobile network name**|
+   |The region in which you're deploying the private mobile network. We recommend you use the East US region.                         |**Instance details: Region**|
+   |The mobile country code for the private mobile network.     |**Network configuration: Mobile country code (MCC)**|
+   |The mobile network code for the private mobile network.     |**Network configuration: Mobile network code (MNC)**|
+
+## Collect SIM values
+
+Each SIM resource represents a physical SIM or eSIM that will be served by the private mobile network.
+
+As part of creating your private mobile network, you can provision one or more SIMs that will use it. If you decide not to provision SIMs at this point, you can do so after deploying your private mobile network using the instructions in [Provision SIMs](provision-sims-azure-portal.md).
+
+If you want to provision SIMs as part of deploying your private mobile network, you must choose one of the following provisioning methods:
+
+- Manually entering values for each SIM into fields in the Azure portal. This option is best when provisioning a small number of SIMs.
+- Importing a JSON file containing values for one or more SIM resources. This option is best when provisioning a large number of SIMs. The file format required for this JSON file is given in [Provision SIM resources through the Azure portal using a JSON file](#provision-sim-resources-through-the-azure-portal-using-a-json-file).
+
+You must then collect each of the values given in the following table for each SIM resource you want to provision.
+
+ |Value  |Field name in Azure portal  | JSON file parameter name |
+   |---------|---------|---------|
+   |The name for the SIM resource. This must only contain alphanumeric characters, dashes, and underscores. |**SIM name**|`simName`|
+   |The Integrated Circuit Card Identification Number (ICCID). This identifies a specific physical SIM or eSIM, and includes information on the SIM's country and issuer. This is a unique numerical value between 19 and 20 digits in length, beginning with 89. |**ICCID**|`integratedCircuitCardIdentifier`|
+   |The international mobile subscriber identity (IMSI). This is a unique number (usually 15 digits) identifying a device or user in a mobile network. |**IMSI**|`internationalMobileSubscriberIdentity`|
+   |The Authentication Key (Ki). This is a unique 128-bit value assigned to the SIM by an operator, and is used in conjunction with the derived operator code (OPc) to authenticate a user. This must be a 32-character string, containing hexadecimal characters only. |**Ki**|`authenticationKey`|
+   |The derived operator code (OPc). This is derived from the SIM's Ki and the network's operator code (OP), and is used by the packet core to authenticate a user using a standards-based algorithm. This must be a 32-character string, containing hexadecimal characters only. |**Opc**|`operatorKeyCode`|
+   |The type of device that is using this SIM. This is an optional, free-form string. You can use it as required to easily identify device types that are using the enterprise's mobile networks. |**Device type**|`deviceType`|
+
+### Provision SIM resources through the Azure portal using a JSON file
+
+The following example shows the file format you'll need if you want to provision your SIM resources using a JSON file. It contains the parameters required to provision two SIMs (SIM1 and SIM2).
+
+```json
+[
+ {
+  "simName": "SIM1",
+  "integratedCircuitCardIdentifier": "8912345678901234566",
+  "internationalMobileSubscriberIdentity": "001019990010001",
+  "authenticationKey": "00112233445566778899AABBCCDDEEFF",
+  "operatorKeyCode": "63bfa50ee6523365ff14c1f45f88737d",
+  "deviceType": "Cellphone"
+ },
+ {
+  "simName": "SIM2",
+  "integratedCircuitCardIdentifier": "8922345678901234567",
+  "internationalMobileSubscriberIdentity": "001019990010002",
+  "authenticationKey": "11112233445566778899AABBCCDDEEFF",
+  "operatorKeyCode": "63bfa50ee6523365ff14c1f45f88738d",
+  "deviceType": "Sensor"
+ }
+]
+```
+
+## Next steps
+
+You can now use the information you've collected to deploy your private mobile network.
+
+- [Deploy a private mobile network - Azure portal](how-to-guide-deploy-a-private-mobile-network-azure-portal.md)