Figure 1.: OAI RRH GW, OAI eNB and OAI EPC+HSS on different hosts
At this point, we have to note that the OAI RRH GW in its simplest form is defaulted to a single RRH which in this tutorial is a USRP-B210-based RRH.
...
...
@@ -31,21 +34,25 @@ not contain the latest UHD. The OAI build script will try to download the latest
automated installation and compilation may fail due to the conflict or missing libraries. So
the simplest way is to uninstall GNURadio and outdated UHD libraries.
The tutorial set up is depicted once more in the following figure, this time containing interconnection information (i.e. IP addesses and Ethernet interface names) that will be used in certain configuration files.
Figure 2.: OAI RRH GW, OAI eNB and OAI EPC+HSS on different hosts (interface information included)
## 1. Installation and Configuration of OAI EPC + HSS
### 1.1 Installation
#### Step 1: Check out the Trunk
First, we will download source codes from the link below as an example. See [GetSources](GetSources).
We assume that you have following directory:
Download the source code from the appropriate Git repository (see [GetSources](GetSources)).We assume that you have following directory:
openair-cn : The location of openair-cn git repository
#### Step 2: Specify FQDN for EPC
Second, a fully qualified domain name (FQDN) needs to be set for the EPC (MME_GW) [\[1\]][1], before we use
A fully qualified domain name (FQDN) needs to be set for the EPC (MME_GW) [\[1\]][1], before we use
the automated script to build eNB, EPC and HSS all at once. An example is as follows. Assume the
hostname is "labuser". You may check it in `/etc/hostname`.
...
...
@@ -78,7 +85,15 @@ Look at [AutoBuild](AutoBuild) for more details.
#### Step 1: Edit the EPC configuration file: `~/openair-cn/BUILD/EPC/epc.conf.in`
Next, we explain the setup for running eNB and EPC+HSS on two different hosts. Assume the IP addresses of eNB and EPC+HSS are 192.168.100.102 and 192.168.100.103. Figure 2 is an example which specifies the network topology.
As depicted in Figure 2 the IP addresse of EPC+HSS is `192.168.12.4` and the Ethernet interface name is `eth0`. Also we assume that the UE that will be used will be configured with the following information ([SIMInfo](SIMInfo)):
* If you have previously build OAI on your host, please use -c or -C to remove existing compiled files.
* During the building process, you will be asked to set the password for MySQL "root" user. You are recommended to use "linux", since this is the default password used by OAI; otherwise, you will have to edit some configuration file so that HSS is able to access MySQL database.
Look at [AutoBuild](AutoBuild) for more details.
#### 2.2 Configuration and execution
RRH GW is configured via input arguements.
#### Step 1: Run RRH GW
All the required configuration for RRH GW is given via input arguments which will be adjusted with respect to the following:
* we assume that `UDP` will be used as the tarsport protocol in the link between RRH GW and eNB
* only `one` eNB will be connected to RRH GW (see Figure 1)
* RRH GW will have a radio front end equipment (USRPB210) attached to it, so there is `no emulation operation` (see Figure 1)
* the name of the Ethernet interface for RRH GW is `eth0` (see Figure 2).
You may print out the help message to see other options. A summary of the above options follows.
* -i: name of ethernet interface used
* -n: number of eNBs that will be connected to RRH GW (in this case is 1)
* -i: name of the RRH GW Ethernet interface (in this case the name is "eth0")
* -m: choose between UDP and RAW version of Ethernet (UDP:0 RAW:1)
* -t: periodically print round trip time measurements
* -x: choose between real time or emulated operation
* -x: choose between real time or emulated operation (in this case real time operation is used)
When OAI RRH GW is successfully connected, you should see something like the following on eNB terminal:
__Note__: some other options are very useful for debugging purposes, such as `-v`, which enables VCD and generates a log file (/tmp/openair_dump_rrh.vcd) with a lot of details and `-g9` which sets logging information to debug level. Finally, there is the option `-t`, which prints periodic round trip delay measurements between RRH GW and eNB. Since all three of them consume computing resources (e.g. VCD is heavy on file accesss), you are recommended to disable them for normal use.
When OAI RRH GW is up waiting for a connection from the eNB, you should see something like the following:
```
...
TYPE <CTRL-C> TO TERMINATE
[RRH][I]eth0: IP address: 192.168.12.1
[RRH][I]UDP mode selected for ethenet.
[ETHERNET]: Initializing openair0_device for RRH ...
[RRH] has loaded ETHERNET trasport protocol.
[RRH] local ip addr 192.168.12.1 port 50000
[RRH] binding mod_0 to 192.168.12.1:50000
```
## 3. Installation and Configuration of OAI eNB
...
...
@@ -204,10 +245,8 @@ TYPE <CTRL-C> TO TERMINATE
### 3.1 Installation
#### Step 1: Check out the Trunk
Download the source code from the appropriate Git repository (see [GetSources](GetSources)). We assume that you have following directory:
First, we will download source codes from the link below as an example. See [GetSources](GetSources).
We assume that you have following directory:
openairinterface5g: The location of openairinterface5g repository.
#### Step 2: Run automated build script (openairinterface5g)
...
...
@@ -216,9 +255,8 @@ openairinterface5g: The location of openairinterface5g repository.
During the building process, you will be asked to set the password for MySQL "root" user. You are recommended to use "linux", since this is the default password used by OAI; otherwise, you will have to edit some configuration file so that HSS is able to access MySQL database.
* If you have previously build OAI on your host, please use -c or -C to remove existing compiled files.
* During the building process, you will be asked to set the password for MySQL "root" user. You are recommended to use "linux", since this is the default password used by OAI; otherwise, you will have to edit some configuration file so that HSS is able to access MySQL database.
Look at [AutoBuild](AutoBuild) for more details.
### 3.2 Configuration and execution
#### Step 1: Edit the eNB configuration file (`~/openairinterface5g/targets/PROJECT/GENERIC-LTE-EPC/CONF/enb.band7.tm1.usrpb210.epc.remote.conf`),
#### Step 1: Edit the eNB configuration file (`~/openairinterface5g/targets/PROJECT/GENERIC-LTE-EPC/CONF/enb.band7.tm1.rrh.usrpb210.conf`),
The file is edited appropriately with respect to Figure 2:
* IP address of EPC/HSS is `192.168.12.4`
* IP address of eNB towards EPC/HSS is `192.168.12.3` and Ethernet interface name is `eth1`
* IP address of eNB towards RRH GW is `192.168.12.2` and Ethernet interface name is `eth0`
* IP address of RRH GW is `192.168.12.1`
* RRH GW will have a `USRPB210` attached to it
It is assumed that `UDP` ETHERNET communication will be used and finally, we again assume that the UE that will be used will be configured with the information mentioned in `Step 1: Edit the EPC configuration file`. Using this information the configuration file of eNB is edidted as follows:
```
tracking_area_code = "1";
...
...
@@ -246,24 +295,46 @@ mobile_network_code = "93";
////////// MME parameters:
mme_ip_address = ( { ipv4 = "192.168.100.103";
ipv6 = "192:168:30::17";
mme_ip_address = ( { ipv4 = "192.168.12.4";
ipv6 = "192:168:3::17";
active = "yes";
preference = "ipv4";
}
);
rrh_gw_config = (
{
local_if_name = "eth0";
remote_address = "192.168.12.1";
local_address = "192.168.12.2";
local_port = 50001; #for raw option local port must be the same to remote
where mme_ip_address is network interface's IP address of your EPC/HSS, and NETWORK_INTERFACE is your eNB related network interface information.
__Note__: Some notes on the following parameters:
* iq_txshift: corresponds to the value that will be used to shift the bits of I/Q samples in TX path and is dependent on the output fromat of the radio hardware target attached to RRH GW
* tx_sample_advance and tx_scheduling_advance are the parameters used for timestamp adjustment between the radio hardware target and its host
* tx_sample_advance-> fine-grain parameter - each unit corresponds to a sample
* tx_scheduling_advance-> coarse-grain parameter-each unit corresponds to one packet
#### Step 2: Run eNB
...
...
@@ -272,22 +343,16 @@ where mme_ip_address is network interface's IP address of your EPC/HSS, and NETW
You may print out the help message to see other options. A summary of the above options is given below.
You may print out the help message (`./lte-softmodem -h`) to see other options. A summary of the above options is given below.
* -O: configuration file
* -m: set the maximum downluink MCS
* -t: set the maximum uplink MCS
* -x: set the transmission mode, valid option: 1
* -W: enable L2 Wireshark messages on localhost
__Note__: some other options are very useful for debugging purposes, such as `-V`, which enables VCD and generates a log file (/tnp/openair_dump_eNB.vcd) with a lot of details, and `-d`, which enables software oscilloscope with interactive graphic interfaces. Since both consume a lot of computing resources (one is heavy on file access, the other one is heavy on graphics), you are recommended to disable them for normal use.
__Note__: some other options are very useful for debugging purposes, such as `-V`, which enables VCD and generates a log file (/tmp/openair_dump_eNB.vcd) with a lot of details, and `-d`, which enables software oscilloscope with interactive graphic interfaces. Since both consume a lot of computing resources (one is heavy on file access, the other one is heavy on graphics), you are recommended to disable them for normal use.
When OAI eNB is successfully connected, you should see something like the following on eNB terminal:
When eNB is successfully connected, you should see something like the following on eNB terminal:
```
...
...
...
@@ -299,141 +364,9 @@ TYPE <CTRL-C> TO TERMINATE
Entering ITTI signals handler
```
## 4. UE Configuration and User Registration on HSS Database
Now eNB, EPC and HSS are working properly, and we may move to the next stage. Assume
that the UE or USIM card has the following information ([Link](SIMInfo)):
You have to create a new APN profile in your smartphone according the one that
you will assign to the UE in the HSS database. So you have to go
__Settings->Mobile network settings->Access Point Names-> Add a new apn__.
Give a **name** to this apn profile (e.g. `eur`). At the **APN field** write
the name that exists on the HSS database (e.g. `oai.ipv4`). At the **Bearer** field check the option `LTE`.
Save the apn profile and then select it.
#### 4.2.3 LTE Dongle: Bandrich LTE Dongle C501
#### 4.2.4 LTE Dongle: Huawei E3372
For this LTE Dongle you don't have to give at commands in order to configure it but you can do it from the graphical interface that it is on the url 192.168.8.1. You have to go to Profile Management and add a new APN profile (see the picture below)
at /home/labuser/trunk/openair-cn/SGW-LITE/sgw_lite_handlers.c:897
```
If you see an error like this, insert `~/trunk/targets/bin/xt_GTPUSP.ko`:
```shell
sudo insmod ~/trunk/targets/bin/xt_GTPUSP.ko
```
At this point we have an operating base station and core network, so it is time to configure the COTS UE and use it (see Stage 2 of [HowToConnectCOTSUEwithOAIeNB](HowToConnectCOTSUEwithOAIeNB) tutorial).
