GSOC2024Channels5G: Difference between revisions
Line 48: | Line 48: | ||
* Present a slide about the mmwave-helper class (modified to support nyu); start to define a plan for the first milestone and solve some doubts [https://docs.google.com/presentation/d/1BGEXbTVMReKGh5ArjglZxAwyePU5ITeq7Y5SyTmq3Os/edit?usp=sharing] | * Present a slide about the mmwave-helper class (modified to support nyu); start to define a plan for the first milestone and solve some doubts [https://docs.google.com/presentation/d/1BGEXbTVMReKGh5ArjglZxAwyePU5ITeq7Y5SyTmq3Os/edit?usp=sharing] | ||
== Week 3 [Jun 14 - Jun | == Week 3 [Jun 14 - Jun 20 ] == | ||
''' NOTE: ''' We are still discussing the non-su-mimo implementation. For a more detailed explanation, go to [https://docs.google.com/document/d/14K0tnTJRO1qb2mDguGr4FrFCDMu8VBJ6BZpPow2au2M/edit GSoC - Document Plan] | ''' NOTE: ''' We are still discussing the non-su-mimo implementation. For a more detailed explanation, go to [https://docs.google.com/document/d/14K0tnTJRO1qb2mDguGr4FrFCDMu8VBJ6BZpPow2au2M/edit GSoC - Document Plan] | ||
* The first approach for non-su-mimo channel model implementation, back to the 2.6 version [https://gitlab.com/Allbu/nr/-/tree/enable-no-su-mimo?ref_type=heads see] | * The first approach for non-su-mimo channel model implementation, back to the 2.6 version [https://gitlab.com/Allbu/nr/-/tree/enable-no-su-mimo?ref_type=heads see] |
Revision as of 13:26, 19 June 2024
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
Back to GSoC 2024 projects
Project Overview
- Project Name: 5G NR Module Benchmark and Analysis for Distinct Channel Models
- Student: Joao Albuquerque
- Mentors: Biljana Bojovic, Amir Ashtari, Gabriel Ferreira
- Google page: GSoC - Project
- Project Goals: Currently, ns-3 and the NR module provide an interface for using a channel model (3GPP). However, two other models have also been developed using the ns-3 environment: Two-ray and NYUSim. The project aims to integrate these two new models into NR module in a simplified and user-friendly manner. Furthermore, I will undertake additional tasks, such as testing the implemented code and creating an example that utilizes these implemented models.
- Repository: ns-3, NR
- About Me: I am an undergraduate student working at LASSE-UFPA, a telecommunications research laboratory, where I have been engaged in various projects using the ns-3 and nr. I have over a year and four months of experience working with ns-3 and the nr module, during which I developed applications, including a new ray-tracing module compatible with NR and the latest versions of ns-3. With this opportunity, I aim to make significant and definitive contributions to ns-3 and the NR module.
Milestones
You can track the project's plan by referring to this document: GSoC — Document Plan. The document will be constantly updated until the final submission.
Milestones for this project include updating the existing channel models in the ns-3, implementing a user-friendly interface via the nr module, and creating an example that utilizes all the added channel models within ns-3. The outline of these implementations will be separated into work packages (WPs) as follows:
WP 1 - NR interface for channel model usage (10 weeks)
- Task 1: Get familiar with BWP configuration, focusing on the channel model and how this configuration could be used from the NR helper class to initialize the BWPs. (0.5 week)
- Task 2: Get familiar with how the NYU channel model is being configured for the mmWave module in the NYU custom mmWave helper class. (0.5 week)
- Task 3: Prepare a refactoring plan for NR classes and check if the design will work for the three-channel models. (2 weeks)
- Task 4: Prepare 5G-Lena for different channel models that may not have spectrum channel matrix for su-MIMO and create a merge request to 5G-Lena. (4 weeks) [milestone 1]
- Task 5: Interface implementation for selecting the channel model via the NR helper class and creating a merge request for 5G-Lena. (3 weeks) [milestone 2]
- Create a conditional build depending on the NYU channel model available in ns-3 and create a merge request to 5G-Lena. [milestone 3]
- Extend NR helper to allow the configuration of 3GPP NTN channel models and create a merge request for 5G-Lena. [milestone 4]
WP 2 - Design and implement the benchmark scenario (8 weeks)
- Task 1: Identify and implement the appropriate scenario for all channel models. (1 week)
- Task 2: Prepare traces to be measured (e.g., entire simulation time, SINR, throughput, latency, etc.) and scripts for running and plotting based on the implemented example. (2 weeks)
- Task 3: Analyze, evaluate, and plot the results of the accomplished example. (3 weeks)
- Task 4: Extend the example to be used as a test and create a merge request of the implemented test to 5G-Lena; Write what was done in a blog post. [milestone 5] (2 weeks)
Weekly Report
Week 1 [May 31 - Jun 06 ]
- Finish the milestones
- Start to draft the desired implementation
- Start to study 5G-Lena and the modified MMwave helper classes
Week 2 [Jun 07 - Jun 13 ]
- Present a slide about BWP configuration and initialization [1]
- Create the first interface implementation (nr-helper) [scratch]
- Present a slide about the mmwave-helper class (modified to support nyu); start to define a plan for the first milestone and solve some doubts [2]
Week 3 [Jun 14 - Jun 20 ]
NOTE: We are still discussing the non-su-mimo implementation. For a more detailed explanation, go to GSoC - Document Plan
- The first approach for non-su-mimo channel model implementation, back to the 2.6 version see
- The second approach for implementing the non-su-mimo channel model involves creating a spectrum channel matrix for those without it see
- Start the interface implementation to enable the user to select distinct channel models using bandConf and initialization with nr-helper see
- Explain the NYUSIM channel model and compare it with 3GPP. Also, provide information about the interface implementation [3]