1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
7 This is the user guide for Cherry release of O-DU/l2.
8 Follow installation-guide to get all the dependencies ready.
18 I. Execution - On locally compiling O-DU High Source Code
19 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
21 1. Assign virtual IP addresses as follows:
23 a. ifconfig <interface name>:ODU "192.168.130.81"
24 b. ifconfig <interface name>:CU_STUB "192.168.130.82"
25 c. ifconfig <interface name>:RIC_STUB "192.168.130.80"
29 a. Navigate to CU execution folder
31 - cd <O-DU High Directory>/l2/bin/cu_stub
39 a. Navigate to RIC execution folder
41 - cd <O-DU High Directory>/l2/bin/ric_stub
43 b. Run RIC Stub binary
49 a. Navigate to ODU execution folder
51 - cd <O-DU High Directory>/l2/bin/odu
57 PS: CU stub and RIC stub must be run (in no particular sequence) before ODU
59 II. Execution - Using Docker Images
60 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
62 The call flow between O-DU High and CU Stub can be achieved by executing docker containers.
64 - Pull the last built docker images:
65 - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:3.0.1
66 - docker pull nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:3.0.1
69 - docker run -it --privileged --net=host --entrypoint bash
70 nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2-cu-stub:3.0.1
74 - docker run -it --privileged --net=host --entrypoint bash
75 nexus3.o-ran-sc.org:10004/o-ran-sc/o-du-l2:3.0.1
79 B. Pairwise testing with Intel O-DU Low:
80 -----------------------------------------
82 This section describes the changes required in compilation and execution of O-DU High binaries to successfully integrate
83 with Intel O-DU Low in timer mode.
89 1. Install O-DU High as per installation-guide .
91 2. Clone O-DU Low code in <O-DU Low Directory> from
93 a. https://gerrit.o-ran-sc.org/r/admin/repos/o-du/phy and,
95 b. https://github.com/intel/FlexRAN
97 3. Install O-DU Low as per https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-phy/en/latest/index.html .
105 a. Create folder <O-DU High Directory>/l2/src/wls_lib. Copy wls_lib.h from <O-DU Low Directory>/phy/wls_lib/ to
106 <O-DU High Directory>/l2/src/wls_lib.
108 b. Create folder <O-DU High Directory>/l2/src/dpdk_lib. Copy following files from
109 <O-DU Low Directory>/dpdk-19.11/x86_64-native-linuxapp-gcc/include/ to <O-DU High Directory>/l2/src/dpdk_lib.
111 - rte_branch_prediction.h
116 - rte_pci_dev_feature_defs.h
124 c. Navigate to build folder
126 - cd <O-DU High Directory>/l2/build/odu
130 - make odu PHY=INTEL_L1 PHY_MODE=TIMER MACHINE=BIT64 MODE=FDD
138 a. Setup environment:
140 - cd <O-DU Low Directory>/phy/
141 - source ./setupenv.sh
143 b. Run O-DU Low binary :
145 - cd <O-DU Low Directory>/FlexRAN/l1/bin/nr5g/gnb/l1
146 - To run in timer mode : ./l1.sh -e
147 - L1 is up when following prints are seen on console:
149 | Non BBU threads in application
150 | \==================================================================
151 | nr5g_gnb_phy2mac_api_proc_stats_thread: [PID: 8659] binding on [CPU 0] [PRIO: 0] [POLICY: 1]
152 | wls_rx_handler (non-rt): [PID: 8663] binding on [CPU 0]
153 | \==================================================================
155 PHY>welcome to application console
157 2. Execute FAPI Translator:
159 a. Setup environment:
161 - cd <O-DU Low Directory>/phy/
162 - source ./setupenv.sh
164 b. Run FAPI translator binary:
166 - cd <O-DU Low Directory>/phy/fapi_5g/bin/
167 - ./oran_5g_fapi --cfg=oran_5g_fapi.cfg
169 3. Execute CU Stub and RIC Stub:
171 a. Run steps in sections A.I.1 through A.I.3 .
175 a. DU execution folder
177 - cd <O-DU High Directory>/l2/bin/odu
179 b. Export WLS library path
181 - export LD_LIBRARY_PATH=<O-DU Low Directory>/phy/wls_lib/lib:$LD_LIBRARY_PATH
191 O-DU High opens WLS interface during bring up. Message exchanges can begin once the interface is ready.
192 Following diagram shows P5 messages exchanged with O-DU Low in timer mode.
194 .. figure:: O-DU_High_Low_Flow.jpg
196 :alt: Figure 1 O-DU High - O-DU Low Message Flow Diagram
198 Figure 5 - O-DU High - O-DU Low Message Flow Diagram
200 Note: UL IQ-Sample request and response are needed by Intel O-DU Low in timer mode(testing mode) only. Code changes for
201 these are guarded under INTEL_TIMER_MODE flag which can be enabled using compilation option "PHY_MODE=TIMER", as
202 mentioned in section B.I.1.d .