DOC: fix some formatting issues
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>
This commit is contained in:
@@ -1,10 +1,10 @@
|
|||||||
# OpenAirInterface for SystemX
|
# OpenAirInterface for SystemX
|
||||||
|
|
||||||
#Terminology
|
# Terminology
|
||||||
|
|
||||||
****This document use the 5G terminology****
|
****This document use the 5G terminology****
|
||||||
|
|
||||||
**Central Unit (CU): **It is a logical node that includes the gNB
|
**Central Unit (CU):** It is a logical node that includes the gNB
|
||||||
functions like Transfer of user data, Mobility control, Radio access
|
functions like Transfer of user data, Mobility control, Radio access
|
||||||
network sharing, Positioning, Session Management etc., except those
|
network sharing, Positioning, Session Management etc., except those
|
||||||
functions allocated exclusively to the DU. CU controls the operation of
|
functions allocated exclusively to the DU. CU controls the operation of
|
||||||
@@ -19,7 +19,9 @@ names like RRH/RRU/RE/RU/PNF.
|
|||||||
In OpenAir code, the terminology is often RU and BBU.
|
In OpenAir code, the terminology is often RU and BBU.
|
||||||
|
|
||||||
# OpenAirUsage
|
# OpenAirUsage
|
||||||
##EPC and general environment
|
|
||||||
|
## EPC and general environment
|
||||||
|
|
||||||
### OAI EPC
|
### OAI EPC
|
||||||
|
|
||||||
Use the stable OAI EPC, that can run in one machine (VM or standalone)
|
Use the stable OAI EPC, that can run in one machine (VM or standalone)
|
||||||
@@ -27,9 +29,10 @@ Use the stable OAI EPC, that can run in one machine (VM or standalone)
|
|||||||
Draft description:
|
Draft description:
|
||||||
<https://open-cells.com/index.php/2017/08/22/all-in-one-openairinterface-august-22nd/>
|
<https://open-cells.com/index.php/2017/08/22/all-in-one-openairinterface-august-22nd/>
|
||||||
|
|
||||||
##Standalone 4G
|
## Standalone 4G
|
||||||
|
|
||||||
EPC+eNB on one machine, the UE can be commercial or OAI UE.
|
EPC+eNB on one machine, the UE can be commercial or OAI UE.
|
||||||
|
|
||||||
### USRP B210
|
### USRP B210
|
||||||
|
|
||||||
Main current issue: traffic is good only on coaxial link between UE and
|
Main current issue: traffic is good only on coaxial link between UE and
|
||||||
@@ -55,7 +58,8 @@ the same IP tunnel end point as the UE.
|
|||||||
|
|
||||||
So, we have to create a network namespace for the UE and to route data
|
So, we have to create a network namespace for the UE and to route data
|
||||||
in/out of the namespace.
|
in/out of the namespace.
|
||||||
``` bash
|
|
||||||
|
```bash
|
||||||
ip netns delete aNameSpace 2> /dev/null
|
ip netns delete aNameSpace 2> /dev/null
|
||||||
|
|
||||||
ip link delete v-eth1 2> /dev/null
|
ip link delete v-eth1 2> /dev/null
|
||||||
@@ -70,7 +74,7 @@ ip addr add 10.200.1.1/24 dev v-eth1
|
|||||||
|
|
||||||
ip link set v-eth1 up
|
ip link set v-eth1 up
|
||||||
|
|
||||||
iptables -t nat -A POSTROUTING -s 10.200.1.0/255.255.255.0 -o enp0s31f6
|
iptables -t nat -A POSTROUTING -s 10.200.1.0/255.255.255.0 -o enp0s31f6 \
|
||||||
-j MASQUERADE
|
-j MASQUERADE
|
||||||
|
|
||||||
iptables -A FORWARD -i enp0s31f6 -o v-eth1 -j ACCEPT
|
iptables -A FORWARD -i enp0s31f6 -o v-eth1 -j ACCEPT
|
||||||
@@ -92,13 +96,15 @@ to run the UE.
|
|||||||
To make user plan traffic, the traffic generator has to run in the same
|
To make user plan traffic, the traffic generator has to run in the same
|
||||||
namespace
|
namespace
|
||||||
|
|
||||||
`ip netns exec aNameSpace bash
|
```bash
|
||||||
`
|
ip netns exec aNameSpace bash
|
||||||
|
```
|
||||||
|
|
||||||
The traffic genenrator has to specify the interface:
|
The traffic genenrator has to specify the interface:
|
||||||
|
|
||||||
`route add default oaitun_ue1
|
```bash
|
||||||
`
|
route add default oaitun_ue1
|
||||||
|
```
|
||||||
|
|
||||||
or specify the outgoing route in the traffic generator (like option “-I”
|
or specify the outgoing route in the traffic generator (like option “-I”
|
||||||
in ping command).
|
in ping command).
|
||||||
@@ -111,6 +117,7 @@ is this work the downlink “functional split 6”.
|
|||||||
The customer required after signature to develop also the uplink
|
The customer required after signature to develop also the uplink
|
||||||
functional split 6. This is accepted, as long as the whole work is
|
functional split 6. This is accepted, as long as the whole work is
|
||||||
research with no delivery completeness warranty.
|
research with no delivery completeness warranty.
|
||||||
|
|
||||||
### Simulation
|
### Simulation
|
||||||
|
|
||||||
To be able to verify the new features and to help in all future
|
To be able to verify the new features and to help in all future
|
||||||
@@ -119,11 +126,12 @@ during this contract.
|
|||||||
|
|
||||||
We added the channel modeling simulation, that offer to simulate various
|
We added the channel modeling simulation, that offer to simulate various
|
||||||
3GPP defined channels.
|
3GPP defined channels.
|
||||||
|
|
||||||
### Main loop
|
### Main loop
|
||||||
|
|
||||||
The main log is in RF simulator is in
|
The main log is in RF simulator is in
|
||||||
|
|
||||||
targets/RT/USER/lte-ru.c and targets/RT/USER/lte-enb.c
|
`targets/RT/USER/lte-ru.c and targets/RT/USER/lte-enb.c`
|
||||||
|
|
||||||
As this piece of SW is very complex and doesn’t meet our goals
|
As this piece of SW is very complex and doesn’t meet our goals
|
||||||
(functional split 6), a cleaned version replaces these 2 files in
|
(functional split 6), a cleaned version replaces these 2 files in
|
||||||
@@ -142,8 +150,8 @@ The reworked main loop take care of a uniq variable that comes directly from har
|
|||||||
|
|
||||||
To use OAI, we need to set all OAI variables that derivates from this timestamp value. The function setAllfromTS() implements this.
|
To use OAI, we need to set all OAI variables that derivates from this timestamp value. The function setAllfromTS() implements this.
|
||||||
|
|
||||||
|
|
||||||
### Splitted main level
|
### Splitted main level
|
||||||
|
|
||||||
When FS6 is actived, a main loop for DU (du_fs6()) a main loop for CU case replaces the uniq eNB main loop.
|
When FS6 is actived, a main loop for DU (du_fs6()) a main loop for CU case replaces the uniq eNB main loop.
|
||||||
|
|
||||||
Each of these main loops calls initialization of OAI LTE data and the FS6 transport layer initialization.
|
Each of these main loops calls initialization of OAI LTE data and the FS6 transport layer initialization.
|
||||||
@@ -262,29 +270,36 @@ The end line option “--split73” enables the fs6 (also called split 7.3) mode
|
|||||||
|
|
||||||
Example:
|
Example:
|
||||||
|
|
||||||
|
```bash
|
||||||
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 cu:127.0.0.1
|
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 cu:127.0.0.1
|
||||||
`
|
```
|
||||||
|
|
||||||
Run the CU init of the split 6 eNB, that will call du on 127.0.0.1 address
|
Run the CU init of the split 6 eNB, that will call du on 127.0.0.1 address
|
||||||
|
|
||||||
|
```bash
|
||||||
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 du:127.0.0.1
|
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 du:127.0.0.1
|
||||||
|
```
|
||||||
|
|
||||||
will run the du, calling the cu on 127.0.0.1
|
will run the du, calling the cu on 127.0.0.1
|
||||||
`
|
|
||||||
If the CU and the DU are not on the same machine, the remote address of each side need to be specified as per this example
|
If the CU and the DU are not on the same machine, the remote address of each side need to be specified as per this example
|
||||||
|
|
||||||
|
```bash
|
||||||
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 du:192.168.1.55
|
./ocp-softmodem -O $OPENAIR_DIR/enb.fs6.example.conf --rfsim --log_config.phy_log_level debug --split73 du:192.168.1.55
|
||||||
`
|
```
|
||||||
|
|
||||||
runs the functional split 6 DU
|
runs the functional split 6 DU
|
||||||
|
|
||||||
`./lte-uesoftmodem -C 2685000000 -r 50 --rfsim --rfsimulator.serveraddr 192.168.1.1 -d
|
```bash
|
||||||
`
|
./lte-uesoftmodem -C 2685000000 -r 50 --rfsim --rfsimulator.serveraddr 192.168.1.1 -d
|
||||||
|
```
|
||||||
|
|
||||||
Runs the UE (to have the UE signal scope, compile it with make uescope)
|
Runs the UE (to have the UE signal scope, compile it with make uescope)
|
||||||
|
|
||||||
CU+DU+UE can run with option --noS1 to avoid to use a EPC and/or with --rfsim to simulate RF board
|
CU+DU+UE can run with option `--noS1` to avoid to use a EPC and/or with `--rfsim` to simulate RF board
|
||||||
|
|
||||||
|
|
||||||
##5G and F1
|
## 5G and F1
|
||||||
|
|
||||||
Today 5G achievement is limited to physical layer.
|
Today 5G achievement is limited to physical layer.
|
||||||
|
|
||||||
@@ -305,13 +320,17 @@ frames).
|
|||||||
|
|
||||||
Usage with RFsimulator:
|
Usage with RFsimulator:
|
||||||
|
|
||||||
gNB
|
**gNB**
|
||||||
|
|
||||||
`sudo RFSIMULATOR=server ./nr-softmodem -O
|
```bash
|
||||||
../../../targets/PROJECTS/GENERIC-LTE-EPC/CONF/gnb.band78.tm1.106PRB.usrpn300.conf
|
sudo RFSIMULATOR=server ./nr-softmodem -O \
|
||||||
--parallel-config PARALLEL\_SINGLE\_THREAD`
|
../../../targets/PROJECTS/GENERIC-LTE-EPC/CONF/gnb.band78.tm1.106PRB.usrpn300.conf \
|
||||||
|
--parallel-config PARALLEL\_SINGLE\_THREAD
|
||||||
|
```
|
||||||
|
|
||||||
nrUE
|
**nrUE**
|
||||||
|
|
||||||
`sudo RFSIMULATOR=127.0.0.1 ./nr-uesoftmodem --numerology 1 -r 106 -C
|
```bash
|
||||||
3510000000 -d`
|
sudo RFSIMULATOR=127.0.0.1 ./nr-uesoftmodem --numerology 1 -r 106 -C \
|
||||||
|
3510000000 -d
|
||||||
|
```
|
||||||
|
|||||||
Reference in New Issue
Block a user