Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | VCS Management |
| 6 | ============== |
| 7 | |
| 8 | A **VCS** (Virtual Cellular Service) is a slice of network access for a set of UEs with a defined set of |
| 9 | QOS parameters. |
| 10 | |
| 11 | To define a VCS requires it to be associated with: |
| 12 | |
| 13 | * one or more **Application** |
| 14 | * one or more **DeviceGroup** |
| 15 | * an **AccessPointList** |
| 16 | * a **UPF** |
| 17 | * a **TrafficClass** |
| 18 | |
| 19 | and must also be created with attributes like: |
| 20 | |
| 21 | * **SD** (slice differentiator) |
| 22 | * **SST** (slice/service type) |
| 23 | * **Uplink** (data rate in mbps) |
| 24 | * **Downlink** (data rate in mbps) |
| 25 | |
| 26 | Provisioning a new VCS |
| 27 | ---------------------- |
| 28 | |
| 29 | .. note:: |
| 30 | This section refers to a fully installed ROC GUI, properly secured and with Enterprises, Connectivity Services |
| 31 | Applications, and Sites already configured by a ROC Administrator. The examples shown below are taken from an example |
| 32 | configuration shipped with the ROC - the "MEGA Patch" (see :ref:`posting-the-mega-patch`) |
| 33 | |
| 34 | This procedure assumes you have already set up one or more DeviceGroups, containing |
| 35 | configuration for a number of UEs. Follow the procedure in :ref:`configure_device_group` |
| 36 | to configure DeviceGroups. |
| 37 | |
| 38 | To add a new VCS, click the **Add** button in the VCS List View. |
| 39 | |
| 40 | |VCS-LIST| |
| 41 | |
| 42 | In the resulting VCS edit page: |
| 43 | |
| 44 | #. enter a VCS ID (this must be unique across the whole system). |
| 45 | #. enter a Display Name (optional). |
| 46 | #. enter a Description (optional). |
| 47 | #. Choose a template |
| 48 | |
| 49 | * this will copy over values from that template, which may be edited individually at this create stage |
| 50 | * they will not be editable afterwards. |
| 51 | #. Choose an *Access Point List* from the drop down list. |
| 52 | #. Choose a *UPF* from the drop down list. |
| 53 | |
| 54 | .. image:: images/aether-roc-gui-add-vcs.png |
| 55 | :width: 500 |
| 56 | :alt: VCS Edit page adding a new VCS |
| 57 | |
| 58 | One or more Applications and or DeviceGroups can be associated with the VCS at this |
| 59 | stage or later, by clicking on the *+* icon. |
| 60 | |
| 61 | When chosen, they appear as a list in the VCS edit page, and are automatically enabled/allowed: |
| 62 | |
| 63 | .. image:: images/aether-roc-gui-vcs-edit-showing-app-dg.png |
| 64 | :width: 300 |
| 65 | :alt: VCS Edit showing Application and Device Group choice lists |
| 66 | |
| 67 | Click on the "Update" to add these changes to the *Basket*. |
| 68 | |
| 69 | Click the **Commit** in the *Basket View* to commit the changes. See :ref:`committing`. |
| 70 | |
| 71 | Editing an existing VCS |
| 72 | ----------------------- |
| 73 | When editing an existing VCS, it will not be possible to change: |
| 74 | |
| 75 | * the **id** |
| 76 | * the **template** or any of the parameters beneath it |
| 77 | |
| 78 | Existing *Applications* or *DeviceGroups* can be removed by clicking the *trash can* icon next to it. |
| 79 | |
| 80 | Alternatively existing *Applications* or *DeviceGroups* can be *disabled/disallowed* by clicking the slider |
| 81 | next to it. This will have the same effect as disabling it. |
| 82 | |
| 83 | If one of the *DeviceGroup*s or *Application*s, *Access Point List*, *Traffic Class* or *UPF* |
| 84 | itself is modified, then the changes on the VCS will take effect whenever changes to those |
| 85 | objects are committed. |
| 86 | |
| 87 | Removing a VCS |
| 88 | -------------- |
| 89 | Removing a VCS can be achieved by clicking the *trash can* icon next to the VCS in the |
| 90 | VCS List page |
| 91 | |
| 92 | |VCS-LIST| |
| 93 | |
| 94 | Monitoring a VCS |
| 95 | ---------------- |
| 96 | |
| 97 | The performance of a VCS can be monitored in many ways, by clicking its |monitor| (**monitor**) icon: |
| 98 | |
| 99 | * From the **Dashboard** page, which shows all VCS's belonging to an Enterprise. |
| 100 | * From the VCS List Page - click the |monitor| icon for the VCS. |
| 101 | * When editing an existing VCS - in the Edit page, the |monitor| is next to the *id* |
| 102 | |
| 103 | The *monitor* page itself shows: |
| 104 | |
| 105 | * A stacked bar graph of the Connectivity count of UEs over the last 15 minutes |
| 106 | |
| 107 | * This shows the count of UE in the 3 different states - Active, Inactive and Idle |
| 108 | * A line graph of the Throughput, Latency and Jitter of the VCS over the last 15 minutes |
| 109 | * The live Throughput, Latency and Jitter values |
| 110 | * Information panels for each sub-object of the VCS |
| 111 | |
| 112 | * Clicking on the down arrow expands each panel |
| 113 | |
| 114 | The DeviceGroup(s) associated with the VCS has itself a |monitor| button that allows |
| 115 | monitoring of each DeviceGroup. See :ref:`monitor_device_group`. |
| 116 | |
| 117 | .. image:: images/aether-roc-vcs-monitor.png |
| 118 | :width: 920 |
| 119 | :alt: VCS Monitor View with Connectivity and Performance Charts |
| 120 | |
| 121 | |
| 122 | .. |VCS-LIST| image:: images/aether-roc-gui-vcs-list.png |
| 123 | :width: 920 |
| 124 | :alt: VCS List View in Aether ROC GUI |
| 125 | |
| 126 | .. |monitor| image:: images/monitor-icon.png |
| 127 | :width: 28 |
| 128 | :alt: Monitor icon |