Merge pull request #4 from accelleran/2023.2.0

Updating RAN Operation Guide to Release 2023.2.0

docs/cu-configuration/index.md

@@ -39,4 +39,4 @@ The 5G CU-UP has a number of configuration parameters as seen below:
   <img src="../mocn-and-slicing/mocn_example_cu_up_config.png">
 </p>
 
-**IMPORTANT**  Do not attempt to modify slices and PLMNs unless you are aware of the target Scenario you want to achieve: slice configuration and multiple PLMN (MOCN) configurations are rather complex to handle and require that CU, DU and Core are configured coherently in order for such Scenarios to be functional. We recommend to consult the relative sections of this document and contact your Core Network Supplier and Accelleran to tailor a solution for your specific case. 
+**IMPORTANT**  Do not attempt to modify slices and PLMNs unless you are aware of the target Scenario you want to achieve: slice configuration and multiple PLMN (MOCN) configurations are rather complex to handle and require that CU, DU and Core are configured coherently in order for such scenarios to be functional. We recommend to consult the relative sections of this document and contact your Core Network Supplier and Accelleran to tailor a solution for your specific case. 

docs/index.md

@@ -7,25 +7,25 @@ This guide describes how to operate the Accelleran ORAN 5G  Platform and the dif
 
 This means that the installation and initial configuration of the System has been already made by Accelleran Customer Support and there is no need to worry about how to prepare the server, install and initialise the components.
 
-2023.1.0 release include Accelleran Cell Wrapper, which works as a layer on top of the DU and RU. This provides a common interface for configuration and controls over a cell. 
+2023.2.0 release includes Accelleran Cell Wrapper, which works as a layer on top of the DU and RU. This provides a common interface for configuration and control over a cell. 
 
-It monitors a DU and RU through periodic health checks and uses the control interface internally to attempt an automatic repair from failures. These health checks include checks for reachability, traffic, container status and checks on a set of log messages. 
+It monitors a DU and RU through periodic health checks and uses the control interface internally to attempt an automatic repair from failures. These health checks include checks for reachability of the servers, traffic thresholds, status of the applications and checks on a set of log messages. 
 
 
 ## 2. Releases
-This document is released together with the system release 2023.1.0. 
+This document is released together with the system release 2023.2.0. 
 This system release contains 
 
 | component    | version                        |
 |--------------|--------------------------------|
-| RIC          | 6.3.0                          |
-| CU CHART     | 5.3.0                          |
-| CU APP       | R4.1.0_jupiler                 |
+| RIC          | 6.5.2                          |
+| CU CHART     | 6.0.0                          |
+| CU APP       | R4.2.3_jupiler                 |
 | DU           | 2023-05-08-q1-patch-release-01 |
 | L1           | 8.7.4                          |
 | BNTL650      | 0.7.0                          |
 | BNTL550      | 0.5.2/0.6.0                    |
-| cell wrapper | 2.2.0                          |
+| cell wrapper | 2.3.0                          |
 | DU/RU        | 5.1.0.30736                    |
 
 ## 3. Dashboard
@@ -41,7 +41,7 @@ From the **Home** tab the cell status can be monitored and the UEs attached to i
 
 Furthermore, from the **Kubernetes Overview** tab, the status of the RIC/CU/CellWrapper pods and services can be monitored.
 
-The DRAX dashboard also uses grafana to view measurements and Counters.
+The DRAX dashboard also uses grafana to view measurements and counters.
 
 - This can be accessed via ```https://"RIC_CU_VM_IP":30300```
 - A number of reports will be readily available on this release for example:

docs/mocn-and-slicing/index.md

@@ -4,13 +4,13 @@
 
 ## 1. Multi Slice Configuration
 
-To enable multiple slices support for a cell, the different components of the network must be configured to support them.
+To enable support for multiple slices in a cell, the different components of the network must be configured correctly to support them.
 
-As an example, Assuming we want to configure three slices: (SST:1), (SST:1,SD:1), (SST2)
+As an example, assuming we want to configure three slices: (SST:1), (SST:1,SD:1), (SST2)
 
 ### 1.1. CU-UP Multi Slice Configuration
 
-Here, the CU UP must be configured with all the Slices that the Core and the Cell will be configured with to support.
+Here, the CU UP must be configured with all the slices so that it can offer user plane support for all the slices:
 
 - From the dashboard go to **RAN Overview** then **5G**
 - From the **CU-UP List**, click on configuration.
@@ -25,7 +25,7 @@ Here, the CU UP must be configured with all the Slices that the Core and the Cel
 
 ### 1.2. DU Multi Slice Configuration
 
-Similar to the CU UP, the DU must be configured with the slices that it needs to support.
+Similar to the CU UP, the DU must be configured with the slices that it needs to support:
 
 - From the dashboard go to **RAN Overview** then **5G**
 - From the **DU/RU List**, click on configuration.
@@ -37,17 +37,15 @@ Similar to the CU UP, the DU must be configured with the slices that it needs to
   <img src="slicing_example_du_config.png">
 </p>
 
-### 1.3. Core MOCN Configuration 
+### 1.3. Core multi slice Configuration 
 
 The core connected should support the slices enabled on the cell. In our example the core should be configured with (SST:1), (SST:1,SD:1), (SST2).
 
-As core configuration would be done differently based on which core vendor is used. It wouldn't be part of this document. Please contact Accelleran with the details of the core used to provide support if possible. 
+The 5G core configuration depends on the vendor chose and is out of the scope of this document.  Please contact Accelleran with the details of the 5G core used to provide support if possible. 
 
-## 2. MOCN Configuration
+## 2. Multi-Operator Core Network (MOCN) Configuration
 
-To configure the Cell to support MOCN (Multi-Operator Core Network) scenarios 
-
-In order to obtain a working setup with MOCN, it is essential that all the network components are aligned and configured coherently to serve the same list of PLMNIDs.
+In order to obtain a working setup with MOCN, it is essential that all the network components are aligned and configured coherently to serve the same list of PLMNIDs and slices.
 
 As an example, this section will show how to configure the below scenario, where one cell will broadcast two PLMNIDs so that UE1 will connect to Core1 and UE2 will connect to Core2.
 
@@ -98,4 +96,4 @@ Similar to the CU UP, the DU must be configured with the PLMN IDs and slices tha
 
 The cores connected should support the PLMN IDs. In our example core1 should be configured with PLMNID 00101, and core2 with PLMNID 00102. 
 
-As core configuration would be done differently based on which core vendor is used. It wouldn't be part of this document. Please contact Accelleran with the details of the core used to provide support if possible. 
+The 5G core configuration depends on the vendor chose and is out of the scope of this document. Please contact Accelleran with the details of the core used to provide support if possible. 

docs/modifying-ran650-or-ran550/index.md

@@ -1,36 +1,33 @@
 # DU/RU Configuration
 
-This section is exclusively applicable to the user/customer that intends to use the Benetel RAN550 or RAN650 Radio End with our Accellleran 5G end to end solution, if you do not have such radio end the informations included in this section may be misleading and bring to undefined error scenarios. Please contact Accelleran if your Radio End is not included in any section of this user guide
+This section is exclusively applicable to the user/customer that intends to use the Benetel RAN550 or RAN650 Radio End with our Accellleran 5G end to end solution, if you do not have such radio end the informations included in this section may be misleading and bring to undefined error scenarios. Please contact Accelleran if your Radio End is not included in any section of this user guide.
 
 ## 1. Parameter Configuration
 
 ### 1.1. Configuring Center Frequency
 
-Take into account that if system release 2022.4.0 is used, adjusting the center frequency will require applying the change on the RU and on the DU (extra step shown below).
-
-
 #### 1.1.1. Finding a Proper Frequency
 
 There are several limitations on the Frequencies that can be selected:
 
 - The selected frequency should be within the band supported by the hardware (RAN650/RAN550) used. 
-- The selected frequency must be devisable by 3.84
+- The selected frequency must be divisible by 3.84
 - Subcarrier Spacing = 30KHz
-- Bandwidth = 40MHz
+- Bandwidth = 40MHz or 100MHz
 - The K_ssb must be 0
 - The offset to point A must be 6
 
 Let's proceed with an example:
 
-To set a center frequency of 3750 MHz, this is not devisable by 3.84, the nearest frequencies that meet this condition are 3747.84MHz (976*3.84) 3751.68MHz (977*3.84) so let's consider first 3747,84 MHz and verify the conditions on the K_ssb and Offset to Point A with this online tool (link at:  (https://www.sqimway.com/nr_refA.php) ) 
+To set a center frequency of 3750 MHz, this is not divisible by 3.84, the nearest frequencies that meet this condition are 3747.84MHz (976*3.84) 3751.68MHz (977*3.84) so let's consider first 3747,84 MHz and verify the conditions on the K_ssb and Offset to Point A with this online tool (link at:  (https://www.sqimway.com/nr_refA.php) ).
 
 - On the tool set the Band to 78, SCS to 30KHz, the Bandwidth to 40MHz and the ARFCN of the center frequency 3747,84 which is 649856 and when we hit the **RUN** button we obtain:
 
 <p align="center">
   <img width="600" height="800" src="Freq3747dot84.png">
 </p>
 
-This Frequency, however does not meet the **GSCN Synchronisation requirements** as in fact the Offset to Point A of the first channel is 2 and the K_ssb is 16, this will cause the UE to listen on the wrong channel so the SIBs will never be seen and therefore the cell is "invisible"
+This Frequency, however does not meet the **GSCN Synchronisation requirements** as in fact the Offset to Point A of the first channel is 2 and the K_ssb is 16, this will cause the UE to listen on the wrong channel so the SIBs will never be seen and therefore the cell is "invisible".
 
 - We then repeat the exercise with the higher center frequency 3751.68MHz, which yelds a center frequency ARFCN of 650112 and a point A ARFCN of 648840 and giving another run we will see that now the K_ssb and the Offset to Point A are correct.
 
@@ -50,47 +47,6 @@ This Frequency, however does not meet the **GSCN Synchronisation requirements**
   <img src="Changing_Frequency.png">
 </p>
 
-**Apply below on the RU, only when using system release 2022.4.0**
-
-- Create a file change_freq.sh with below content in the RU
-```bash
-#!/bin/bash
-if [ -z "$1" ]; then
-  echo "Please provide frequency in MHz in with the format XXXX.XXX as an argument"
-  exit 1
-fi
-registercontrol -w 0xC036B -x 0x88000088
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x174:0x01:0x3$(echo $1 | cut -c1)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x175:0x01:0x3$(echo $1 | cut -c2)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x176:0x01:0x3$(echo $1 | cut -c3)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x177:0x01:0x3$(echo $1 | cut -c4)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x178:0x01:0x2E
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x179:0x01:0x3$(echo $1 | cut -c6)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17A:0x01:0x3$(echo $1 | cut -c7)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17B:0x01:0x3$(echo $1 | cut -c8)                    
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17C:0x01:0x3$(echo $1 | cut -c1)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17D:0x01:0x3$(echo $1 | cut -c2)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17E:0x01:0x3$(echo $1 | cut -c3)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x17F:0x01:0x3$(echo $1 | cut -c4)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x180:0x01:0x2E
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x181:0x01:0x3$(echo $1 | cut -c6)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x182:0x01:0x3$(echo $1 | cut -c7)
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x183:0x01:0x3$(echo $1 | cut -c8)
-registercontrol -w 0xC036B -x 0x88000488
-```
-- For our example where the center frequency required is 3751.68MHz, run the script by:
-```
-./change_freq.sh 3751.680
-```
-- To validate the command is successful run below:
-```bash
-eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 372:8
-```
-- reboot RU
-```bash
-reboot
-```
-
 
 ### 1.2. Configuring Cell TX Power
 
@@ -107,36 +63,9 @@ By default RAN650 is configured with 35dBm and RAN550 is configured with 25dBm.
   <img src="Changing_Power.png">
 </p>
 
-**Apply below on the RU, only when using system release 2022.4.0**
-
-- To adjust the power of the RU the attenuation settings on the RU would need to be changed: To increase the power the attenuation must be reduced and to decreasing the power, the attenuation must be increased.
-- Important: The the current attenuation values on the RU must be saved as they are unit specific and used to make sure that the unit is transmitting on the needed power. (Please note these are in mdB)
-For ANT1: ```eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 780:5```
-For ANT3: ```eeprog_cp60 -q -f -16 /dev/i2c-0 0x57 -r 1060:5```
-- Assuming as an example the RAN650 unit had for ANT1 16000 anf for ANT3 15730 and we want to reduce the output power by 10dB.
-- Then the new attenuation values for ANT1 and ANT3 must be 26000 and 25730 respectivily.
-- Modify the below script with the last digit of each value and run it on the RU.
-```bash
-registercontrol -w 0xC036B -x 0x88000088
-#ANT1
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30C:0x01:0x32
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30D:0x01:0x36
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30E:0x01:0x30
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x30F:0x01:0x30
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x311:0x01:0x30
-#ANT3
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x424:0x01:0x32
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x425:0x01:0x35
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x426:0x01:0x37
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x427:0x01:0x33
-eeprog_cp60 -f -x -16 /dev/i2c-0 0x57 -w 0x428:0x01:0x30
-registercontrol -w 0xC036B -x 0x88000488
-```
-
-
 ## 2. Checking RU Status
 
-After applying actions on the RU to change the frequency or the power. A reboot of the RU would be necessary and will be applied via the cell wrapper when clicking **submit** on when configuring the cell parameters. (Unless advanced settings was toggled and reboot RU was unchecked).
+After applying actions on the RU to change the frequency or the power. A reboot of the RU is necessary and will be applied via the cell wrapper when clicking **submit**.
 
 Below are some useful checks to confirm the status of the RU after the reboot.
 

docs/nodeh-du-ru-operation/index.md

@@ -2,8 +2,6 @@
 
 This section is exclusively applicable to the user/customer that intends to use the Node-H DU with Askey RU or T&W RU with our Accellleran 5G end to end solution, if you do not have such radio end the informations included in this section may be misleading and bring to undefined error scenarios. Please contact Accelleran if your Radio End is not included in any section of this user guide.
 
-Please note, on this system release 2022.4.0 the cell wrapper is yet to be intgerated with the split 2 solution. So cell operation and configuration must be done from the DU/RU unit itself. This won't be the same with the next system release.
-
 ## 1. Start/Stop Cell
 
 ssh into the DU/RU unit and run below command to start the cell.
@@ -24,7 +22,7 @@ The cell configuration file is located in ```/var/lib/nodeh/data/fap_config_si.j
 
 ### 2.1. Frequency Modification
 
-Simply use the center frequency ARFCN, and make sure it is within the n78 band e.g: 
+Use the center frequency ARFCN, and make sure it is within the n78 band e.g: 
 ```bash
 "General":{"ChannelNrArfcn": 651648}
 ```

mkdocs.yml

@@ -1,4 +1,4 @@
-site_name: Accelleran 5G O-RAN System - 2023.1.0 release
+site_name: Accelleran 5G O-RAN System - 2023.2.0 release
 
 site_url: https://accelleran.github.io/ran-operation-guide/
 theme: