GSOC2014LteFFR - Revision history

Pgawlowicz: week12

2014-08-11T12:21:19Z

week12

← Older revision		Revision as of 12:21, 11 August 2014
Line 325:		Line 325:

	=== Week 12 (August 11, 2014 - August 17, 2014) ===		=== Week 12 (August 11, 2014 - August 17, 2014) ===
			In summary, this week has delivered the following:
			*applied comments form code review
			*created tests for FR schemes with Uplink Power Control
			*created test for FR algorithms with Uplink Power Control + test documentation
			*created examples to show FR algorithms functionality (extended lena-dual-stripe, one simple example for Hard FR, Strict FR, Soft FR, Soft FFR and Enhanced FFR schemes, one simple example for Distributed FFR)
			*updated RadioEnvironmentMapHelper to collect values from Data/Control channel and from specified RbId
			*added RadioEnvironmentMapHelper to example
			*added Spectrum Analyzer to example
			*refactored FfrCellId -> FrCellTypeId
			*made Uplink Power Control in Accumulated Mode enabled by default
			*extended SIB2 with referenceSignalPower and removed attribute to configure it manually in UePowerControl

			During next week I will:
			*create/update user documentation about FR examples
			*update RELEASE NOTES and CHANGES.html
			*make FR to be reconfigurable at any time (now is configured once before simulation start)

Pgawlowicz: week11

2014-08-11T12:17:50Z

week11

← Older revision		Revision as of 12:17, 11 August 2014
Line 305:		Line 305:
	*write test documentation for distributed FFR scheme		*write test documentation for distributed FFR scheme
	*write design, user and test documentation for Uplink Power Control		*write design, user and test documentation for Uplink Power Control

			=== Week 11 (July 28, 2014 - August 10, 2014) ===
			In summary, this week has delivered the following:
			*Started process of final code review
			*Connected Uplink Power Control with Frequency Reuse schemes
			*Created tests for FR algorithms with PF, PSS, CQA, TD-TBFQ, FD-TBFQ
			*Created test documentation for distributed FFR scheme
			*Created design, user and test documentation for Uplink Power Control
			*Found and fixed next HARQ bug
			*Fixed errors and warnings occured in documentation generation
			*Fixed valgring errors

			During next week I will:
			*create test for FR algorithms with Uplink Power Control + test documentation
			*create example scenario to show FR algorithms functionality (probably dual-stripe scenario will be extended) + user documentation
			*create Radio Environment Maps for different FR schemes, RadioEnvironmentMapHelper needs to be updated, to collect values only for 1 RB
			*create traces with Spectrum Analyzer for different FR schemes
			*apply comments from code review

			=== Week 12 (August 11, 2014 - August 17, 2014) ===

Pgawlowicz: week10

2014-07-28T21:42:20Z

week10

@@ Line 276: / Line 276: @@
-=== Week 9 (July 21, 2014 - July 27, 2014) ===
+=== Week 9 (July 14, 2014 - July 20, 2014) ===
 In summary, this week has delivered the following:
 *Implemented distributed frequency reuse algorithm (finally we decided to implement algorithm described in [4], which fits LTE standards more)
@@ Line 290: / Line 290: @@
 *write tests for all supported schedulers
 *start working on UL POWER CONTROL

Pgawlowicz: week9

2014-07-21T22:07:36Z

week9

← Older revision		Revision as of 22:07, 21 July 2014
Line 274:		Line 274:
	*write test (if there will be enough time)		*write test (if there will be enough time)
	*update design and user documentation (if there will be enough time)		*update design and user documentation (if there will be enough time)


			=== Week 9 (July 21, 2014 - July 27, 2014) ===
			In summary, this week has delivered the following:
			*Implemented distributed frequency reuse algorithm (finally we decided to implement algorithm described in [4], which fits LTE standards more)
			*Updated design and user documentation
			*Connected FR algorithms with PSS, CQA, TBFQ Schedulers

			Firstly, I wanted to implement Multi-Sector Gradient FR algorithm, but it turned out, that it does not fit LTE standards, (expanded X2-interface is needed, moreover MGR requires downlink power allocation to be continous but there are only 8 quantized P_a values). On Thursday, I found distributed FFR algorithm [4], that utilizes available X2-interface messages (i.e. RNTP).
			I have tried to fix bug with HARQ, which occurs with EFFR algorithm, but I did not manage to it. It needs more investigation, as this problem do not appear always.

			During next week I will:
			*try to fix HARQ bug
			*write test for distributed FFR scheme
			*write tests for all supported schedulers
			*start working on UL POWER CONTROL

Pgawlowicz at 12:20, 14 July 2014

2014-07-14T12:20:44Z

← Older revision		Revision as of 12:20, 14 July 2014
Line 256:		Line 256:
	*update design and user documentation		*update design and user documentation
	*start working on distributed FR schemes		*start working on distributed FR schemes


			=== Week 8 (July 7, 2014 - July 13, 2014) ===
			In summary, this week has delivered the following:
			*Created tests for EFFR
			*Created tests for CQI generation
			*Updated design and user documentation
			*Tried to fix HARQ bug, which appeard when EFFR algorithm is used
			*Started working on distributed frequency reuse algorithm (checked X2 communication between two FR entities)

			During last discussion with my mentors we were talking on distributed frequency reuse algorithm. It turned out, that algorithm (Multi-Sector Gradient, MGR [4]) I have planned to implement needs X2-interface to be expanded. I was afraid that it can not be simply expanded, because current LTE standards do not provide description on this topic. We agreed that firstly we will try to find different distributed FR algorithm which is using messages available in X2-Interface (i.e. Relative Narrowband Transmit Power, RNTP), and if we will not manage this, we will expand X2-interface with VendorSpecific fields and implement MGR algorithm.

			During next week I will:
			*try to fix HARQ bug
			*connect FR algorithms with different MAC Schedulers (at least with PSS, CQA, TBFQ)
			*implement distributed frequency reuse algorithm (MGR or different)
			*write test (if there will be enough time)
			*update design and user documentation (if there will be enough time)

Pgawlowicz: week7

2014-07-07T15:45:48Z

week7

← Older revision		Revision as of 15:45, 7 July 2014
Line 240:		Line 240:
	*finish EFFR algorithm and write test for it		*finish EFFR algorithm and write test for it
	*update design and user documentation		*update design and user documentation

			=== Week 7 (June 30, 2014 - July 6, 2014) ===
			In summary, this week has delivered the following:
			*Review Krishna Teja Mid-Term code
			*Extended SAP to pass CQI from scheduler to FR algorithm
			*Implementation of new CQI generation approach
			*Implementation of EFFR algorithm
			Code refactoring of LteSinrChunkProcessor (renamed to LteChunkProcessor, removed Lte**ChunkProcessors classes, added callback list)

			I did not created tests during last week, because I spend more time on CQI generation. I implemented one solution, but after discussion with my mentors, we decided it should be changed and I spend more time to implement it once again in different way. Moreover, I refactored code of LteSinrChunkProcessor (which was not planned), but there was bug and some LTE test were crushing. Fortunately I fixed this.

			During next week I will:
			*write test for EFFR
			*write test for new CQI generation
			*update design and user documentation
			*start working on distributed FR schemes

Pgawlowicz: week6

2014-06-30T15:39:44Z

week6

← Older revision		Revision as of 15:39, 30 June 2014
Line 236:		Line 236:

	During next week I will:		During next week I will:
	*~~Review~~ Krishna Teja Mid-Term code		*review Krishna Teja Mid-Term code
	*finish CQI implementation and write test for it		*finish CQI implementation and write test for it
	*finish EFFR algorithm and write test for it		*finish EFFR algorithm and write test for it
	*update design and user documentation		*update design and user documentation

Pgawlowicz at 15:39, 30 June 2014

2014-06-30T15:39:10Z

← Older revision		Revision as of 15:39, 30 June 2014
Line 225:		Line 225:
	* ./test.py -s lte-frequency-reuse		* ./test.py -s lte-frequency-reuse
	* ./test.py -s lte-interference-fr		* ./test.py -s lte-interference-fr

			=== Week 6 (June 23, 2014 - June 29, 2014) ===
			In summary, this week has delivered the following:
			*Addressed the comments on the mid-term code review
			*Removed additional bandwidth configuration in FR algorithms, now it is configured durign cell configuraiton
			*Added Doxygen descriptions
			*Added automatic configuration for 15 RB bandwidth
			*During last discussion with my mentors, we agreed solution for CQI generation and I started to implement it
			*Started implementing Enhanced Fractional Frequency Reuse algorithm

			During next week I will:
			*Review Krishna Teja Mid-Term code
			*finish CQI implementation and write test for it
			*finish EFFR algorithm and write test for it
			*update design and user documentation

Pgawlowicz: mid-term code review

2014-06-23T17:15:37Z

mid-term code review

← Older revision		Revision as of 17:15, 23 June 2014
Line 191:		Line 191:
	=== Mid-term Code Review (June 23, 2014 - June 27, 2014) ===		=== Mid-term Code Review (June 23, 2014 - June 27, 2014) ===
	Mid-term code review starts at the beginning of this week.		Mid-term code review starts at the beginning of this week.

			The code to be reviewed can be found in Rietveld issue 110020049.
			https://codereview.appspot.com/110020049/
			The review covers all the changes from the beginning of the project, so patch contains:
			*FfrAlgorithm abstract class
			*Two SAPs FfrSchedulerSap and FfrRrcSap
			*Updated all schedulers and eNB RRC with new SAPs
			*Updated LteHelper
			*Downlink Power Control
			*Updated RrcAsn1Header with PdschConfigDedicated structure
			*Frequency Reuse Algorithms:
			**Trivial FR algorithm
			**Hard FR algorithm
			**Strict FR algorithm
			**Soft FR algorithm
			**Soft FFR algorithm
			*Tests:
			**lte-downlink-power-control to check correctness of Downlink Power Control
			**lte-frequency-reuse to check if scheduler is not using forbidden RBGs, and if UE is served with proper power and RBGs in downlink according to FFR algorithm policy
			**lte-interference-fr checks interference level with Hard and Strict FR algorithms
			*Design and test documentation
			*Automatic Frequency Reuse configuration in DL and UL (cell can be configured with only 1 attribute)
			*Fixed problem with uplink scheduling with frequency reuse algorithm
			*Examples (in scratch directory) show how FR algorithms can be configured:
			**lena-fr-simple
			**lena-hard-fr
			**lena-strict-fr
			**lena-soft-fr
			**lena-soft-ffr

			There are 3 test suites of interest, which can be run as follows:
			* ./test.py -s lte-downlink-power-control
			* ./test.py -s lte-frequency-reuse
			* ./test.py -s lte-interference-fr

Pgawlowicz at 20:40, 22 June 2014

2014-06-22T20:40:27Z

← Older revision		Revision as of 20:40, 22 June 2014
Line 189:		Line 189:
	Fractional Frequency Reuse algorithm and tests.		Fractional Frequency Reuse algorithm and tests.

	=== Mid-term Code Review (June 23, 2014 - June 30, 2014) ===		=== Mid-term Code Review (June 23, 2014 - June 27, 2014) ===
	Mid-term code review starts at the beginning of this week.		Mid-term code review starts at the beginning of this week.