Specialized Networks

Network as Code offers easy-to-use SDKs to control Specialized Networks and adapt the 5G network to a myriad of use cases. With Specialized Networks, you can ensure the logical separation and efficient use of network resources according to your current demand.

Think of a Slice (or specialized network) as a customizable part of a much larger network. Now, imagine you can change this specialized portion to meet the needs of each specific use-case. Let's say, when you need reliable connection for your business, streaming, gaming event or the endless possibilities a slice can be created for. Any time you need, at your own demand, a slice can be created to offer tailored network flexibility, speeds, and capacities to suit different needs.

Behind this technology, there is a lot of complexity that our SDK code abstracts for you. Like the partitioning of the network infrastructure, which enables the creation of different virtual network instances. The Specialized Networks SDK makes the link between the Network Operator and different devices or applications. So, you can allocate network resources to a given slice or unique QoD session that will guarantee network performance. While also being able to associate specific devices or applications with a particular network slice.

Terminology

Here are some terms you will often see throughout the Specialized Networks section:

• Token / application key: The application key that was created through the the API Management dashboard in the Getting Started steps. This information is used when you are creating a Network as Code client:

  The NetworkAsCodeClient is the entry-point to all the functionality Network as Code provides. Learn more about it.

  PythonTypeScript

  client = nac.NetworkAsCodeClient(token="<your-application-key-here>")

• Device ID: An email-like identifier for a device (or subscriber) into the network. It works as a device object created to manage a particular device on the network, for example: device@testcsp.net.

• Network Identifier: An ID used to identify the Network Operator and country when creating a slice. It will be composed of a Mobile Country Code (MCC) and Mobile Network Code (MNC).

  PLMN ID:

  MCC	MNC
  3 - digits	2 or 3 digits

  Good to know: MCC and MNC, together, form the Public Land Mobile Network (PLMN) ID. It is just used to identify which mobile network; a user or device is associated with. These codes are unique to each country depending on the mobile network operator. So, when using PLMN numbers, remember to modify them according to your country and Network Operator.

• Slice type: Defines the slice's purpose. It maps into the Single Network Slice Selection Assistance Information (S-NSSAI), determining a Slice/Service type (SST) and Slice Differentiator (SD).

  For example, if you use eMBB for SST and a value like 1000 for SD, an Enhanced Mobile Broadband (eMBB) slice type will be created, allowing 5G to provide devices with much faster data rates compared to 4G.

• Area of service: It defines a geographic area in which the Specialized Network will be used. This means that parameters, such as latitude and longitude can be informed.

• Slice Throughput: Optional parameters to indicate the amount of traffic that can go through the slice in one direction.