MicroSlicing policies are used to deliver predictable performance and network segmentation on the Celona private wireless network for Device Groups and Applications.
Device Groupa logical group of devices/users to apply Networking, Security & MicroSlicing QoS policies. This article describes how to create aDevice Group.Applicationconfiguration within the Celona Orchestrator focuses on identifying and classifying the wireless traffic on the Celona Access Points (AP).
Configuring Application classification definition
In order to configure new applications within the Celona Orchestrator for your site, follow the following steps:
Go to the Applications page in the Orchestrator, click
Create Application. Give your application aName, and specify at least one application parameter.Enter
Remote IP. For example, the IP address of the cloud server used by this Application.Enter
Remote Start / End Port. For example, a live RTMP video stream sends to remote port 485.Enter
Device Start / End Port. For example, IP cameras often serve their video feed using RTSP on port 554.Enter the
binary DSCP tagused by your application.Click
Addto save. Celona Edge will be able to detect and classify your application on the Celona wireless network within a few seconds.
With all of these elements now configured, we can now move on to setting policies for application performance using Celona MicroSlicing.
Configuring MicroSlicing
Access the MicroSlicing page via the left-hand menu and click Create, and give your policy a unique name.
Configure a MicroSlicing policy with Non-Guaranteed Bit Rate
This option is used to set traffic policy for device groups and applications that are not bit rate sensitive. For example, delivering the best performance for an RFID scanning application requires predictable latency and packet error rate.
Choose
Non-GBRSelect the
Quality of Service Classfrom the dropdown.
Non-GBR Support for 4G/5G
“QoS Category” in Orchestrator | Current QCI Support | 5G 5QI Support | 3GPP Use-cases |
Highest priority signaling – 4G | QCI = 5 Priority = 1 PDB = 100ms PER = 10-6 |
| Mission Critical delay sensitive signaling (e.g., MC-PTT signaling) |
Highest priority signaling – 5G only | N/A | 5QI = 69 Priority = 5 PDB = 60ms PER = 10-6 |
|
Internet & Email | QCI = 8 Priority = 8 PDB = 300ms PER=10-6 | 5QI = 8 Priority = 80 PDB = 300ms PER = 10-6 | TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video) Video (Buffered Streaming) |
Interactive multimedia | QCI = 7 Priority = 7 PDB = 100ms PER=10-3 | 5QI = 7 Priority = 70 PDB = 100ms PER – 10-3 | Interactive streaming |
Streaming video – 4G only | QCI = 6 Priority = 6 PDB=300ms PER=10-6 |
|
|
Configure a MicroSlicing policy with Guaranteed Bit Rate
This option is used to set traffic policy for device groups and applications that require specific bitrate for best performance. For example, ensuring adequate bandwidth available to receive real-time HD video from a remotely operated vehicle.
Choose
Guaranteed Bit Rate.Set bit rates that would be applied per individual device, or per application on each device. Set at least one.
Select the
Quality of Service Classfrom the dropdown.
GBR Support for 4G/5G
“QoS Category” in Orchestrator | Current QCI Support | 5G 5QI Support | 3GPP Use-cases |
Conversational voice | QCI = 1 Priority = 2 PDB = 100ms PER = 10-2 | 5QI = 1 Priority = 20 PDB = 100ms PER = 10-2 | Conversational Voice |
Process Automation (Real-time & control) | QCI = 3 Priority = 3 PDB = 50ms PER = 10-3 | 5QI = 3, Priority = 30 PDB = 50ms PER = 10-3 | Process Automation |
Streaming video – 4G only | QCI = 4 Priority = 5 PDB = 300ms PER=10-5 | N/A | Voice, Video (Live Streaming) |
Interactive video – 4G only | QCI = 2 Priority = 5 PDB = 150ms PER=10-3 | N/A |
|
Industrial automation – 5G only | N/A | 5QI = 82 Priority = 19 PDB = 10ms PER = 10-4 | Discrete Automation/Delay critical GBR |
Finalize MicroSlicing policy configuration
Select which device groups will be included in this policy, at least one is required. Next, choose
Permit All Applicationsor select from the list of Applications you created.Permit all Applicationsis used when the MicroSlicing policy should be applied to all traffic generated by devices in the selected device groups. A great option for single-purpose devices like Point of Sale terminals.Applying the policy by both Device Group and your customized Application list will provide even more granular control. A specific use case would be employee-owned smartphones that run both Enterprise and personal apps.
Click
Saveand your MicroSlicing policy configuration will automatically be made available on your Celona Edge Cluster.
You can review historical policy performance via the main dashboard of the Celona Orchestrator.
How is throughput calculated?
Uplink and downlink data received and transmitted on the relevant MicroSlicing policy over a specific time interval.
For 1-hour & 6-hour charts, the time interval per data point is 1 minute.
For 24-hour & 7-day charts, the time interval per data point is 5 minutes.
Within Celona Orchestrator,
Aggregate Chartconsiders traffic to/from all devices in the interval, andPer Device Chartshows the average throughput across devices in the interval.Note that,
Sessionsrepresent the number of unique devices that sent/received traffic on this MicroSlicing policy during a 5-minute interval.
How is latency calculated?
Round-trip times between Celona Edge and connected devices are estimated on an ongoing basis. The latency value reported would then be the median across all samples in a 5-minute interval.
Within Celona Orchestrator,
Aggregate Chartconsiders traffic from Celona Edge to all devices in the interval, andPer Device Chartshows the average latency across devices in the interval.