|
|
# How to use OAI to setup C-RAN -> NGFI RCC/RRU (*Experimental at the time of writing*)
|
|
|
# How to use OAI to setup C-RAN -> NGFI RCC/RRU (*Experimental*)
|
|
|
|
|
|
In this tutorial, we will describe how to connect a commercial off-the-shelf UE (i.e. smartphone and LTE dongle) with the C-RAN version of the OAI eNB. The OAI C-RAN architecture is described in detailed on this [whitepaper](http://www.openairinterface.org/?page_id=1695).
|
|
|
|
... | ... | @@ -79,29 +79,29 @@ __Notes:__ |
|
|
#### Step 1: Edit the RRU configuration file (`~/openairinterface5g/targets/PROJECTS/GENERIC-LTE-EPC/CONF/**rru_file**`)
|
|
|
|
|
|
The file is edited appropriately with respect to Figure 2:
|
|
|
* IP address of RRU towards RCC is `192.168.12.2` and Ethernet interface name is `eth0`
|
|
|
* IP address of RCC is `192.168.12.1`
|
|
|
* MAC address of RRU is `24:f5:aa:e1:46:01` and Ethernet interface name is `eth0`
|
|
|
* MAC address of RCC towards RRU is `24:f5:aa:e1:4e:0c`
|
|
|
* RRU will have a `USRPB210` attached to it
|
|
|
|
|
|
It is assumed that `NGFI_IF4.5` will be used with `UDP` ETHERNET transport. Using this information the configuration file of RRU is edited as follows:
|
|
|
It is assumed that `NGFI_IF4.5` will be used with `RAW` ETHERNET transport. Using this information the configuration file of RRU is edited as follows:
|
|
|
|
|
|
```
|
|
|
tracking_area_code = "1";
|
|
|
mobile_country_code = "208";
|
|
|
mobile_network_code = "93";
|
|
|
mobile_country_code = "901";
|
|
|
mobile_network_code = "70";
|
|
|
|
|
|
rrh_gw_config = (
|
|
|
{
|
|
|
local_if_name = "eth0";
|
|
|
remote_address = "192.168.12.1";
|
|
|
local_address = "192.168.12.2";
|
|
|
remote_address = "24:f5:aa:e1:4e:0c";
|
|
|
local_address = "24:f5:aa:e1:46:01";
|
|
|
local_port = 50000; # for raw option local port must be the same to remote
|
|
|
remote_port = 50000;
|
|
|
rrh_gw_active = "yes";
|
|
|
tr_preference = "udp_if4p5"; # replace based on choice of functional split
|
|
|
tr_preference = "raw_if4p5"; # replace based on choice of functional split
|
|
|
rf_preference = "usrp_b200";
|
|
|
iq_txshift = 4;
|
|
|
tx_sample_advance = 70;
|
|
|
tx_sample_advance = 80;
|
|
|
tx_scheduling_advance = 9;
|
|
|
}
|
|
|
);
|
... | ... | @@ -166,16 +166,16 @@ __Notes:__ |
|
|
The file is edited appropriately with respect to Figure 2:
|
|
|
* IP address of EPC/HSS is `192.168.12.4`
|
|
|
* IP address of RCC towards EPC/HSS is `192.168.12.3` and Ethernet interface name is `eth1`
|
|
|
* IP address of RCC towards RRU is `192.168.12.2` and Ethernet interface name is `eth0`
|
|
|
* IP address of RRU is `192.168.12.1`
|
|
|
* MAC address of RCC towards RRU is `24:f5:aa:e1:4e:0c` and Ethernet interface name is `eth0`
|
|
|
* MAC address of RRU is `24:f5:aa:e1:46:01`
|
|
|
* RRU will have a `USRPB210` attached to it
|
|
|
|
|
|
It is assumed that `NGFI_IF4.5` will be used with `UDP` ETHERNET transport. Using this information the configuration file of RCC is edited as follows:
|
|
|
It is assumed that `NGFI_IF4.5` will be used with `RAW` ETHERNET transport. Using this information the configuration file of RCC is edited as follows:
|
|
|
|
|
|
```
|
|
|
tracking_area_code = "1";
|
|
|
mobile_country_code = "208";
|
|
|
mobile_network_code = "93";
|
|
|
mobile_country_code = "901";
|
|
|
mobile_network_code = "70";
|
|
|
|
|
|
|
|
|
////////// MME parameters:
|
... | ... | @@ -189,15 +189,15 @@ mobile_network_code = "93"; |
|
|
rrh_gw_config = (
|
|
|
{
|
|
|
local_if_name = "eth0";
|
|
|
remote_address = "192.168.12.1";
|
|
|
local_address = "192.168.12.2";
|
|
|
remote_address = "24:f5:aa:e1:46:01";
|
|
|
local_address = "24:f5:aa:e1:4e:0c";
|
|
|
local_port = 50000; # for raw option local port must be the same to remote
|
|
|
remote_port = 50000;
|
|
|
rrh_gw_active = "yes";
|
|
|
tr_preference = "udp_if4p5"; # replace based on choice of functional split
|
|
|
tr_preference = "raw_if4p5"; # replace based on choice of functional split
|
|
|
rf_preference = "usrp_b200";
|
|
|
iq_txshift = 4;
|
|
|
tx_sample_advance = 70;
|
|
|
tx_sample_advance = 80;
|
|
|
tx_scheduling_advance = 9;
|
|
|
}
|
|
|
);
|
... | ... | |