Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | Subscriber and Connectivity Management |
| 6 | ====================================== |
| 7 | |
| 8 | Subscriber management includes workflows associated with provisioning new subscribers, removing |
| 9 | existing subscribers, and associating subscribers with virtual connectivity services. |
| 10 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 11 | .. note:: |
| 12 | This section refers to a fully installed ROC GUI, properly secured and with Enterprises, Connectivity Services |
| 13 | and Sites already configured by a ROC Administrator. The examples shown below are taken from an example |
| 14 | configuration shipped with the ROC - the "MEGA Patch" (see :ref:`posting-the-mega-patch`) |
| 15 | |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 16 | Provisioning a new UE |
| 17 | --------------------- |
| 18 | |
| 19 | Before a UE can be granted connectivity service, it must first be provisioned. This step is normally |
| 20 | performed by Aether Operations. |
| 21 | |
| 22 | Each UE is assigned a PLMN and a set of security keys. Depending on the deployment scenario, these |
| 23 | keys might be shared by several UEs, or they might be unique to each UE. The allocation of PLMNs and |
| 24 | keys is currently performed manually by the Aether Operations team. This subscriber-related |
Andy Bavier | 212f640 | 2021-09-30 17:27:34 -0700 | [diff] [blame] | 25 | detail is configured via the SIM Management application, ``simapp``. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 26 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 27 | ``simapp.yaml`` needs to be adjusted to include the new UE IMSIs to the subscriber list. For example:: |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 28 | |
| 29 | # simapp.yaml |
| 30 | # ... |
| 31 | simapp.yaml: |
| 32 | info: |
| 33 | version: 1.0.0 |
| 34 | description: SIMAPP initial local configuration |
| 35 | logger: |
| 36 | # network function |
| 37 | APP: |
| 38 | debugLevel: info |
| 39 | ReportCaller: false |
| 40 | configuration: |
| 41 | provision-network-slice: false |
| 42 | subscribers: |
| 43 | - ueId-start: 123456789123458 |
| 44 | ueId-end: 123456789123458 |
| 45 | plmnId: 20893 |
| 46 | opc: 8e27b6af0e692e750f32667a3b14605d |
| 47 | key: 8baf473f2f8fd09487cccbd7097c6862 |
| 48 | sequenceNumber: 16f3b3f70fc2 |
| 49 | - ueId-start: 123456789123460 |
| 50 | ueId-end: 123456789123465 |
| 51 | plmnId: 20893 |
| 52 | opc: 8e27b6af0e692e750f32667a3b14605d |
| 53 | key: 8baf473f2f8fd09487cccbd7097c6862 |
| 54 | sequenceNumber: 16f3b3f70fc2 |
| 55 | |
Andy Bavier | 212f640 | 2021-09-30 17:27:34 -0700 | [diff] [blame] | 56 | The simapp configurations for all deployments are stored in the ``aether-app-configs`` repository: |
| 57 | |
| 58 | * Production deployment: ``apps/sd-core-4g/overlays/prd-acc-gcp1/values.yaml`` |
| 59 | * Staging deployment: ``apps/sd-core-4g/overlays/stg-acc-aws/values.yaml`` |
| 60 | |
| 61 | Fleet will automatically deploy changes to these files once they are merged. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 62 | |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 63 | .. _configure_device_group: |
| 64 | |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 65 | Configure Connectivity Service for a new UE |
| 66 | ------------------------------------------- |
| 67 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 68 | To receive connectivity service, a UE must be added to a DeviceGroup. An Enterprise is typically |
| 69 | organized into one or more Sites, each Site which may contain one or more DeviceGroups. Navigate |
| 70 | to the appropriate DeviceGroup which is associated with the Site you wish to deploy on, and add |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 71 | the UE's IMSI to the DeviceGroup. |
| 72 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 73 | The Site details can be seen by navigating to the Site list view. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 74 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 75 | .. image:: images/aether-roc-gui-sites-list.png |
| 76 | :width: 755 |
| 77 | :alt: Sites List View in Aether ROC GUI showing site details |
| 78 | |
| 79 | In the ROC GUI, navigate to the Device Groups list view, to see the list of |
| 80 | Device Groups and their association to Sites. |
| 81 | |
| 82 | |DEVICEGROUP-LIST| |
| 83 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 84 | In the DeviceGroup *New York POS* example above an IMSI Range **store** of |
| 85 | **70-73** will mean the set of IMSI IDs (when the *format* specifier of the |
| 86 | *starbucks-newyork* Site are applied to its *MCC*, *MNC* and *Enterprise*) of |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 87 | |
| 88 | * 021032002000070 (021-032-002-000070) |
| 89 | * 021032002000071 |
| 90 | * 021032002000072 |
| 91 | * 021032002000073 |
| 92 | |
| 93 | .. note:: |
| 94 | For 4G service, a UE may participate in at most one DeviceGroup, and that DeviceGroup may |
| 95 | participate in at most one VCS. For 5G service, a UE can participate in many DeviceGroups, and each |
| 96 | DeviceGroup may participate in many VCSes. |
| 97 | |
| 98 | Editing |
| 99 | ******* |
| 100 | Edit the DeviceGroup by clicking on the Edit icon, and in the Edit page, |
| 101 | adjust an existing range or create a new range (by clicking on the `+` icon). |
| 102 | |
| 103 | |DEVICEGROUP-EDIT| |
| 104 | |
| 105 | The following restrictions apply |
| 106 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 107 | #. The IMSI ID specified in "from" or "to" is relative to *MCC*, *MNC* and *Enterprise* of the Site. |
| 108 | #. The maximum value of an IMSI ID is defined by the number of **S** characters in the `format` specifier of the Site. |
| 109 | #. IMSI Ranges are contiguous ranges of IMSI IDs. To accommodate non contiguous IMSI IDs, add extra Ranges. |
| 110 | #. IMSI Ranges can have a maximum span of 100 between "from" and "to" IMSI IDs. Break bigger spans in to many ranges. |
| 111 | #. IMSI ranges within a DeviceGroup cannot not overlap. |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 112 | |
| 113 | When the entries on the DeviceGroup edit page are valid the **Update** will become available |
| 114 | |
| 115 | * Click this to add the changes to the **Basket** of configuration changes |
| 116 | * Observe that the **Basket** icon (2nd icon from top right) displays the number of changes |
| 117 | |
| 118 | .. note:: |
| 119 | The changes are not committed to **aether-config** until the **Basket** is committed. |
| 120 | This allows several changes to be gathered together in one transaction and checked before committing. |
| 121 | |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 122 | .. _committing: |
| 123 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 124 | Committing |
| 125 | ********** |
| 126 | To commit the changes |
| 127 | |
| 128 | #. click on the **Basket** icon (2nd icon from top right) to see the Basket view |
| 129 | #. inspect the changes to be committed (optional) |
| 130 | #. click **commit** to perform the commit |
| 131 | #. observe the response that's temporarily displayed that shows the success or failure of the commit |
| 132 | |
| 133 | .. image:: images/aether-roc-gui-basket-view-new-range.png |
| 134 | :width: 635 |
| 135 | :alt: Basket View with some changes ready to be committed |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 136 | |
| 137 | Remove Connectivity Service from an existing UE |
| 138 | ----------------------------------------------- |
| 139 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 140 | Using the ROC GUI, navigate to the DeviceGroup that contains the UE, |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 141 | then remove that UE's IMSI from the list. If you are removing a single UE, and the |
| 142 | DeviceGroup is configured with a range specifier that includes several IMSIs, |
| 143 | then it might be necessary to split that range into multiple ranges. |
| 144 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 145 | * If the UE to be removed has an IMSI ID in the middle of an existing IMSI Range: |
| 146 | click the *trash can* icon next to that *IMSI Range* and |
| 147 | use the *+* icon to add new Ranges for the remaining IMSI IDs. |
| 148 | * Alternatively if the UE to be removed has an IMSI ID at the start or end of an existing IMSI Range: |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 149 | then adjust the *from* or *to* value accordingly. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 150 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 151 | |DEVICEGROUP-EDIT| |
| 152 | |
| 153 | .. note:: |
| 154 | The UE may continue to have connectivity until its next detach/attach cycle. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 155 | |
| 156 | Create a new DeviceGroup |
| 157 | ------------------------ |
| 158 | |
| 159 | DeviceGroups allow UEs to be grouped and configured together. Each site comes preconfigured with |
| 160 | a default DeviceGroup, but additional DeviceGroups may be created. For example, placing all IP |
| 161 | Cameras in an my-site-ip-cameras DeviceGroup would allow you to group IP Cameras together. |
| 162 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 163 | To add a DeviceGroup, navigate to the list of DeviceGroups and click `Add` in the upper right. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 164 | (This may be grayed out if you do not have appropriate permissions). |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 165 | |
| 166 | * Specify a unique **id** for the DeviceGroup |
| 167 | 40 characters max and only alphanumeric and `-`, `_` and `.` allowed |
| 168 | * Choose a *Site* from the list of preconfigured list |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 169 | It will not be possible to add IMSI Ranges until the Site is chosen |
| 170 | * IMSI Ranges can be added at this stage or later |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 171 | |
| 172 | .. image:: images/aether-roc-gui-devicegroup-add.png |
| 173 | :width: 490 |
| 174 | :alt: Adding a new Device Group requires an *id* and choosing a Site |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 175 | |
| 176 | Delete a DeviceGroup |
| 177 | -------------------- |
| 178 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 179 | If a DeviceGroup is no longer needed, it can be deleted. Deleting a DeviceGroup will not cause |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 180 | the UEs participating in the group to automatically be moved elsewhere. |
| 181 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 182 | .. note:: |
| 183 | If a Device Group is being used by an existing VCS, then it cannot be removed. |
| 184 | Delete the VCS first, and then the DeviceGroup. |
| 185 | |
| 186 | A DeviceGroup can be deleted from the DeviceGroup list view, by clicking the *trash can* icon |
| 187 | next to it. The deletion is added to the **Basket** directly. Navigate to the *Basket View* |
| 188 | to commit the change. |
| 189 | |
| 190 | |DEVICEGROUP-LIST| |
| 191 | |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 192 | |
| 193 | Add a DeviceGroup to a Virtual Connectivity Service (VCS) |
| 194 | --------------------------------------------------------- |
| 195 | |
| 196 | In order to participate in the connectivity service, a DeviceGroup must be associated with |
| 197 | a Virtual Connectivity Service (VCS). |
| 198 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 199 | Navigate to the *VCS* list view to see the list of VCS's and their associations to DeviceGroups. |
| 200 | |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 201 | |VCS-LIST| |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 202 | |
| 203 | To edit a *VCS* click on the *edit* button next to it in this list. |
| 204 | |
| 205 | This brings up the VCS edit page where (among many other things) zero, one or many |
| 206 | DeviceGroups can be associated with it. |
| 207 | |
| 208 | * Click the *trash can* symbol to remove a DeviceGroup from the VCS |
| 209 | * Click the *+* icon to add a DeviceGroup |
| 210 | * Click the *Allow* slider to Allow or Disallow the DeviceGroup |
| 211 | This is a way of disabling or reenabling the DeviceGroup within a VCS without having to remove it |
| 212 | |
| 213 | .. image:: images/aether-roc-gui-vcs-edit.png |
| 214 | :width: 562 |
| 215 | :alt: VCS Edit View in Aether ROC GUI showing DeviceGroup association editing |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 216 | |
| 217 | Remove a DeviceGroup from a Virtual Connectivity Service (VCS) |
| 218 | -------------------------------------------------------------- |
| 219 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 220 | The procedure is covered in the above section. |
Scott Baker | e59540c | 2021-08-02 11:51:54 -0700 | [diff] [blame] | 221 | |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 222 | .. _monitor_device_group: |
| 223 | |
| 224 | Monitoring a DeviceGroup |
| 225 | ------------------------ |
| 226 | |
| 227 | The performance of a Device Group can be monitored in many ways, by clicking its |monitor| (**monitor**) icon: |
| 228 | |
| 229 | * From the *VCS Monitor* page, which shows all DeviceGroup's belonging to an VCS. |
| 230 | * From the DeviceGroup List Page - click the |monitor| icon for the DeviceGroup. |
| 231 | * When editing an existing DeviceGroup - in the Edit page, the |monitor| is next to the *id* |
| 232 | |
| 233 | The *monitor* page itself shows: |
| 234 | |
| 235 | * An information Panel for each *IMSI Range* in the *DeviceGroup* |
| 236 | |
| 237 | * Each UE has a |monitor| button that allows further drill down |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 238 | * Each UE is shown with its fully expanded IMSI number (a combination of *IMSI ID* and *Site* parameters) |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 239 | * An information panel for the *Site* and *IP Domain* of the *DeviceGroup* |
| 240 | |
| 241 | * Clicking on the down arrow expands each panel |
| 242 | |
| 243 | .. image:: images/aether-roc-gui-devicegroup-monitor.png |
| 244 | :width: 600 |
| 245 | :alt: DeviceGroup Monitor View with UE links and information panels |
| 246 | |
| 247 | The per UE Monitor panel contains: |
| 248 | |
| 249 | * a graph of the UE's Throughput and Latency over the last 15 minutes |
| 250 | * a graph of the UE's connectivity over the last 15 minutes |
| 251 | |
| 252 | .. image:: images/aether-roc-gui-ue-monitor.png |
| 253 | :width: 600 |
| 254 | :alt: DeviceGroup Monitor View with UE links and information panels |
| 255 | |
| 256 | |
| 257 | .. |monitor| image:: images/monitor-icon.png |
| 258 | :width: 28 |
| 259 | :alt: Monitor icon |
| 260 | |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 261 | .. |DEVICEGROUP-LIST| image:: images/aether-roc-gui-devicegroups-list.png |
| 262 | :width: 755 |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 263 | :alt: Device Groups List View in Aether ROC GUI showing Site association and IMSI Range of all DeviceGroups |
Sean Condon | f918f64 | 2021-08-04 14:32:53 +0100 | [diff] [blame] | 264 | |
| 265 | .. |DEVICEGROUP-EDIT| image:: images/aether-roc-gui-devicegroup-edit.png |
| 266 | :width: 755 |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 267 | :alt: Device Groups Edit View in Aether ROC GUI showing IMSI Range |
Sean Condon | 435be9a | 2021-08-06 14:28:37 +0100 | [diff] [blame] | 268 | |
| 269 | .. |VCS-LIST| image:: images/aether-roc-gui-vcs-list.png |
| 270 | :width: 920 |
| 271 | :alt: VCS List View in Aether ROC GUI showing DeviceGroup association |