GSOC20235GUsability: Difference between revisions
Jump to navigation
Jump to search
(→Week 1) |
(→Week 1) |
||
| Line 19: | Line 19: | ||
* Read [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3191 3GPP TR 38.300] as an overview. In general, we will look to align with 3GPP terminology and specifications. | * Read [https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3191 3GPP TR 38.300] as an overview. In general, we will look to align with 3GPP terminology and specifications. | ||
* Start to document somewhere (Google doc, or Sphinx) the lifecycle of these UDP packets-- what are the interesting things that happen to each packet to get it through the RAN? | * Start to document somewhere (Google doc, or Sphinx) the lifecycle of these UDP packets-- what are the interesting things that happen to each packet to get it through the RAN? | ||
* Start to migrate LOG statements so that interesting logs are in NS_LOG_INFO and NS_LOG_WARN. See WifiHelper::EnableLogComponents()-- we should come up with a similar one for NrHelper::EnableLogComponents (level=INFO by default). | * Start to migrate LOG statements so that interesting logs are in NS_LOG_INFO and NS_LOG_WARN. See WifiHelper::EnableLogComponents()-- we should come up with a similar one for NrHelper::EnableLogComponents (level=INFO by default). Alternative is to place dedicated methods in the nr examples, tailored to logs of interest. | ||
* Enable traces: //nrHelper->EnableTraces(); perhaps controlled by a command line argument. How can these help the new user? | * Enable traces: //nrHelper->EnableTraces(); perhaps controlled by a command line argument. How can these help the new user? | ||
* Line 453 of cttc-nr-demo.cc states: // From here, it is standard NS3. In the future, we will create helpers for this part as well. Start to create such helpers, focusing first on application and TFT configuration. | * Line 453 of cttc-nr-demo.cc states: // From here, it is standard NS3. In the future, we will create helpers for this part as well. Start to create such helpers, focusing first on application and TFT configuration. | ||
* Start to experiment with the ConfigStore loading and saving of attributes and default values. | * Start to experiment with the ConfigStore loading and saving of attributes and default values. | ||
* Measuring latency within the NR RAN-- new trace sources at ingress and egress of NetDevice? Packet tags? | * Measuring latency within the NR RAN-- new trace sources at ingress and egress of NetDevice? Packet tags? | ||
Revision as of 14:53, 24 May 2023
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 2023 projects
Project Overview
- Project Name: IUNS-3 5G NR: Improving the Usability of ns-3's 5G NR Module
- Student: Giovanni Grieco
- Mentors: Tom Henderson, Katerina Koutlia, and Biljana Bojovic
- Google page: https://summerofcode.withgoogle.com/programs/2023/projects/oeDFknbT
- Project Goals:
- Repository:
- About Me:
Milestones
Week 1
- Read 3GPP TR 38.300 as an overview. In general, we will look to align with 3GPP terminology and specifications.
- Start to document somewhere (Google doc, or Sphinx) the lifecycle of these UDP packets-- what are the interesting things that happen to each packet to get it through the RAN?
- Start to migrate LOG statements so that interesting logs are in NS_LOG_INFO and NS_LOG_WARN. See WifiHelper::EnableLogComponents()-- we should come up with a similar one for NrHelper::EnableLogComponents (level=INFO by default). Alternative is to place dedicated methods in the nr examples, tailored to logs of interest.
- Enable traces: //nrHelper->EnableTraces(); perhaps controlled by a command line argument. How can these help the new user?
- Line 453 of cttc-nr-demo.cc states: // From here, it is standard NS3. In the future, we will create helpers for this part as well. Start to create such helpers, focusing first on application and TFT configuration.
- Start to experiment with the ConfigStore loading and saving of attributes and default values.
- Measuring latency within the NR RAN-- new trace sources at ingress and egress of NetDevice? Packet tags?