Changes between Version 8 and Version 9 of Tutorials/k0SDR/Tutorial26


Ignore:
Timestamp:
Oct 3, 2019, 5:32:33 PM (5 years ago)
Author:
pnetalkar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/k0SDR/Tutorial26

    v8 v9  
    11== LTE Traffic Trace Collection ==
    2 This wiki page contains the tutorial to collect traffic traces for realtime application such as video, web, mail etc. at RLC, MAC and PDCP layer of LTE protocol stack in ORBIT testbed using OpenAirInterface (OAI).Users were connected over the air using b210 USRPs and data/logs recorded at eNodeB were extraced using standard linux tools. A high level system diagram is given below.
     2This wiki page contains the tutorial to collect traffic traces for realtime application such as video, web, mail services etc. at RLC, MAC and PDCP layer of LTE protocol stack in ORBIT testbed using OpenAirInterface (OAI) emulation platform. Users were connected over the air using b210 USRP and data/logs recorded at eNodeB were extraced using standard linux tools. A high level system diagram is given below.
    33
    44||||||Figure 1: System Diagram - Trace Collection||
     
    66
    77=== Description ===
    8 For this experiments we need UEs, eNB having b210s USRP, two other nodes for EPC and Server are also needed. We have used grid sandbox with node8-7 as eNB; node13-7, node13-14 and node8-14 as UEs; node2-2 as EPC; node3-2 as server. More UEs can be added but we have tested with just 3 users in this experiment. A detailed system diagram with list of all the interfaces is given below. This tutorial will cover following sections:
     8For this experiments we need UEs (User Equipment), eNB (eNodeB) having b210 USRP, two other nodes for EPC (Evolved Packet Core) and a server to test connectivity and bandwidth. We have used grid sandbox with node8-7 as eNB; node13-7, node13-14 and node8-14 as UEs; node2-2 as EPC; node3-2 as server. More users can be added but we have tested with just 3 users in this experiment. A detailed system diagram with list of all the attached interfaces is given below. This tutorial will cover following sections:
    99* Setup OAI emulation framework
    1010* Connecting UE to LTE network
     
    1313* Application Design
    1414* Trace collection and Evaluation
    15 * OAI script
     15* OAI run using scripts (github link)
    1616
    17 ||||||Figure 2: GRID OAI System Design Implementaion - Trace Collection||
     17||||||Figure 2: GRID OAI System Design Implementation for 3 users - Trace Collection||
    1818 || [[Image(topology.jpg, 650px)]] ||
    1919
     
    3535  Server: {{{omf load -i baseline.ndz -t node3-2}}}
    3636
    37 After loading the image turnon the nodes using command: {{{omf tell -a on -t node13-14,node13-7,node8-14,node8-7,node3-2,node2-2}}}
     37After loading the image turn on the nodes using command: {{{omf tell -a on -t node13-14,node13-7,node8-14,node8-7,node3-2,node2-2}}}
    3838
    39 2) Starting EPC : Run the following commands to enable eth0 interface and to start EPC components - HSS, MME and SPGW:
     392) Starting EPC : \\
     40Run the following commands to enable eth0 interface and to start EPC components - HSS, MME and SPGW:
    4041{{{
    4142ssh root@node2-2
     
    5455}}}
    5556
    56 4) Starting eNodeB
     574) Starting eNB:
    5758{{{
    5859ssh root@node8-7
     
    8081}}}
    8182
    82 The Tx and Rx gain have to adjusted based on physical distance between UE and eNB. Same procedure is repeated if you want to add UE2 and UE3 but the IP address will be different. IP address assignment by MME depends on when the UE is attached to network. If UE1, UE2 and UE3 are attached sequentially then their IP address will be {{{172.16.0.2, 172.16.0.4 and 172.16.0.6}}} respectively.
     83The Tx and Rx gain has to adjusted based on physical distance between UE and eNB. Same procedure is repeated if you want to add UE2 and UE3 but the IP address will be different. IP address assignment by MME depends on when the UE is attached to network. If UE1, UE2 and UE3 are attached sequentially then their IP address will be {{{172.16.0.2, 172.16.0.4 and 172.16.0.6}}} respectively. This IP assignment can be easily checked using {{{ifconfig}}}
    8384
    8485=== Connecting Multiple UEs ===
    85 More users can also be connected for a realistic LTE scenarnio. Apart from the nodes used above {{{node18-2, node18-19 and node3-19}}} has USRPb210s and can be used to emulate UEs. The same UE image can be used but we have to change IMSI and MSISDN for newly added UEs. The following procedure has to be followed to add multiple UE -
     86More users can also be connected for a realistic LTE scenario. Apart from the nodes used above {{{node18-2, node18-19 and node3-19}}} have USRPb210 and can be used to emulate UE. The same UE image can be used but we have to change IMSI and MSISDN for newly added UEs. The following procedure has to be followed to add multiple UE :
     87* Remove any existing UE with same IMSI from HSS database (remember IMSI).
    8688* IMEI should be different for different users. Take the same IMEI from HSS database, add it to config of UE but while adding in database (DB) again, make it null (IMP).
    87 * Remove any existing UE with same imsi from DB
    88 * Add in DB using the command below with IMSI, MSISDN
     89* Add in database using the command below with IMSI, MSISDN
    8990{{{
    9091ssh root@node2-2 (EPC)
     
    102103}}}
    103104
    104 === Running OAI logging Module ===
     105=== Enabling OAI logging Module ===
    105106To collect the trace we need to enable T tracer present in OAI before starting the application and eNB. The following command is used to obtain the trace at eNB:
    106 In a different terminal-
    107107{{{
    108108cd /root/openairinterface5g/common/utils/T/tracer;./textlog -d ../T_messages.txt -ip 0.0.0.0  -on MAC -on RLC -on PDCP -on RRC -no-gui >  /var/log/enbtracer.log 2> /var/log/enbtracer.log &
    109109}}}
    110110
     111With the above command, traces will be collected at MAC, RLC , PDCP and RRC layer which will be dumped in enbtracer.log file present at /var/log directory.
     112
     113=== Application Design ===
     1141) Test Application
     115   * Ping and Perf:
     116
     1172) Video Application
     118
     1193) Web Traffic Application
     120
     1214) Email Services
     122
     1235) Skype (Pending)