AS-LTE integration to lte module of ns-3

[Anshuman Sabath]

I tried to integrate the AS-LTE code into ns-3 lte module by following the instructions provided for its installation. But, when I tried to build ns-3 using waf, it gives errors of some sources missing. Is there some mistake in my method or should I contact the creatorof the module.

Here is the error message:

source not found: 'test/lte-test-sinr-chunk-processor.cc' in bld(features=['cxx', 'cxxstlib', 'ns3module', 'ns3testlib'], ns3_dir_location='src/lte', pcfilegen=bld(features='ns3pcfile', idx=4, meths=[], prec=defaultdict(<type 'list'>, {}), _name='', source='', module='ns3-lte-test', mappings={}, path=/media/anshuman/Windows/Storage/MyFolder/summer/ns3.26/ns-allinone-3.26/ns-3.26/src/lte, target='') in /media/anshuman/Windows/Storage/MyFolder/summer/ns3.26/ns-allinone-3.26/ns-3.26/src/lte, use=['ns3-lte'], mappings={}, uselib='', meths=['_add_test_code', 'process_rule', 'process_source', 'apply_link', 'process_use', 'propagate_uselib_vars', 'apply_incpaths_ns3testlib', 'apply_incpaths', 'collect_compilation_db_tasks', 'install_boost', 'set_macosx_deployment_target'], prec=defaultdict(<type 'list'>, {}), source=['test/lte-test-downlink-sinr.cc', 'test/lte-test-uplink-sinr.cc', 'test/lte-test-link-adaptation.cc', 'test/lte-test-interference.cc', 'test/lte-test-sinr-chunk-processor.cc', 'test/lte-test-ue-phy.cc', 'test/lte-test-rr-ff-mac-scheduler.cc', 'test/lte-test-pf-ff-mac-scheduler.cc', 'test/lte-test-fdmt-ff-mac-scheduler.cc', 'test/lte-test-tdmt-ff-mac-scheduler.cc', 'test/lte-test-tta-ff-mac-scheduler.cc', 'test/lte-test-fdbet-ff-mac-scheduler.cc', 'test/lte-test-tdbet-ff-mac-scheduler.cc', 'test/lte-test-fdtbfq-ff-mac-scheduler.cc', 'test/lte-test-tdtbfq-ff-mac-scheduler.cc', 'test/lte-test-pss-ff-mac-scheduler.cc', 'test/lte-test-cqa-ff-mac-scheduler.cc', 'test/lte-test-earfcn.cc', 'test/lte-test-spectrum-value-helper.cc', 'test/lte-test-pathloss-model.cc', 'test/lte-test-entities.cc', 'test/lte-simple-helper.cc', 'test/lte-simple-net-device.cc', 'test/lte-test-rlc-um-transmitter.cc', 'test/lte-test-rlc-am-transmitter.cc', 'test/lte-test-rlc-um-e2e.cc', 'test/lte-test-rlc-am-e2e.cc', 'test/epc-test-gtpu.cc', 'test/test-epc-tft-classifier.cc', 'test/epc-test-s1u-downlink.cc', 'test/epc-test-s1u-uplink.cc', 'test/test-lte-epc-e2e-data.cc', 'test/test-lte-antenna.cc', 'test/lte-test-phy-error-model.cc', 'test/lte-test-mimo.cc', 'test/lte-test-harq.cc', 'test/test-lte-rrc.cc', 'test/test-lte-x2-handover.cc', 'test/test-lte-x2-handover-measures.cc', 'test/test-asn1-encoding.cc', 'test/lte-test-ue-measurements.cc', 'test/lte-test-cell-selection.cc', 'test/test-lte-handover-delay.cc', 'test/test-lte-handover-target.cc', 'test/lte-test-deactivate-bearer.cc', 'test/lte-ffr-simple.cc', 'test/lte-test-downlink-power-control.cc', 'test/lte-test-uplink-power-control.cc', 'test/lte-test-frequency-reuse.cc', 'test/lte-test-interference-fr.cc', 'test/lte-test-cqi-generation.cc', 'test/lte-simple-spectrum-phy.cc'], test=True, install_path='${LIBDIR}', module_deps=['lte'], dependencies=['lte'], path=/media/anshuman/Windows/Storage/MyFolder/summer/ns3.26/ns-allinone-3.26/ns-3.26/src/lte, vnum=None, posted=True, is_static=True, target='../../ns3.26-lte-test-debug', idx=3, _name='ns3-lte-test', is_ns3_module_test_library=True, module_name='ns3-lte') in /media/anshuman/Windows/Storage/MyFolder/summer/ns3.26/ns-allinone-3.26/ns-3.26/src/lte

Here is a pic:

Here are the installation instructions from the readme file:

1. INSTALLATION

---------------

These are the AS-LTE instructions to guide you in the installation process to enable the extension of MOCN architectures for NS-3.

With this extension, users can implement MOCN infrastructures to emulate different scenarios, to do so, first of all you need to:

  1) Copy the file ASScenario.cc into ns-3.2X/scratch

  2) Copy the files available in the folder "helper" (.cc and .h) into ns-3.2X/src/lte/helper/

  3) Copy the files available in the foler "model" (.cc and .h) into ns-3.2X/src/lte/model/

  4) Copy the file wscript ns-3.2X/src/lte/ by replacing the existing one.

Then, you need to recompile NS-3 again in order to generate the MOCN extension. To do so, you can follow the steps available in NS-3 website. The only requirement is to add the flag --enable-static, the command would be something like that. 

./waf configure --enable-sudo --enable-examples --enable-tests --enable-static

2. RUNNING

----------

After the compilation of NS-3, the system is ready to be executed. To run the provided scenario "ASScenario", just you need to execute the following command. 

./waf --run ASScenario 

 The link for the download of the code is here:http://https//sourceforge.net/p/aslte/ . The paper that describes the function is here. http://www.sciencedirect.com/science/article/pii/S1084804516301916

[Konstantinos]

Hi,

The AS-LTE code is based on a previous ns-3 (in 2015) and the LTE module has been updated since.
The issue is primarily the wscript file as you are using the old (based on the 2015 ns-3 code) updated only with the AS-LTE code.
I would recommend to amend the wscript file of the ns-3 release you use by adding the files introduced in the helper and model folders for AS-LTE.

More details on how to add new modules in ns-3 or extend existing ones in the documentation

https://www.nsnam.org/docs/manual/html/support.html

Regards

K

[Anshuman Sabath]

Thanks for your reply. I tried what you had said. The ns3 can be built now, so, I think the wscript is fine. However, I am getting some other error in one of the class files, possibly due to an outdated class.

The error reads:

/src/lte/model/as-epc-enb-application.cc: In member function ‘void ns3::ASEpcEnbApplication::RecvFromLteSocket(ns3::Ptr<ns3::Socket>)’:

../src/lte/model/as-epc-enb-application.cc:324:3: error: ‘SocketAddressTag’ was not declared in this scope

   SocketAddressTag satag;

I think it is due to the removal/upgradation of the class in my present ns3 version. Could you tell me which other class/sub-class has taken up its functionality?

[Konstantinos]

Hi,

The SocketAddressTag has been removed from the codebase.

Particularly for the EnbApplication, this is reflected in this change 

http://code.nsnam.org/ns-3-dev/diff/6869e7e72137/src/lte/model/epc-enb-application.cc

As you can see, it was simply dropped, without a replacement.

I do not know how the AS-EnbApplication makes use of the tag. 

Regards

K