NR SDAP gNB - Transparent Mode

added 5G-NR label

OAI RAN-CI-develop build (2027): Some Changed files in Merge Request DO NOT follow OAI Formatting Rules

OAI RAN-Container-Parent build (630): failed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/630/)

OAI RAN-CI-develop build (2027): passed (https://open5glab.eurecom.fr:8083/jenkins/job/RAN-CI-develop/2027/)

@angeloath_hhi I think you can consider to set the call back to sdap, and in this call back remove/process the sdap layer, then call pdcp_data_req() from the SDAP call back

If you confirm you want two call backs, please explain

@angeloath_hhi i think i made a mistake, as you said in today meeting

changed milestone to %REVIEW_IN_PROGRESS

requested review from @lthomas

assigned to @Cedric.Roux

added 198 commits

b5fdba70...de553cd1 - 197 commits from branch develop
3421481e - NR SDAP gNB - Transparent Mode

Compare with previous version

OAI RAN-CI-develop build (2096): Some Changed files in Merge Request DO NOT follow OAI Formatting Rules

OAI RAN-CI-develop build (2096): passed (https://open5glab.eurecom.fr:8083/jenkins/job/RAN-CI-develop/2096/)

OAI RAN-Container-Parent build (698): failed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/698/)

marked this merge request as draft

marked this merge request as ready

OAI RAN-Container-Parent build (700): failed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/700/)

Code Review by : Laurent THOMAS

IMPACT on FUNCTIONAL CODE
- The code change does NOT respect architecture/protocol split
- Abnormal exits are NOT properly handled
- Coding Style Issues
  - Added DEAD Code
  - Improper logging
  - Added useless debug code
  - Duplication of an existing function
  - Indentation is not respected
  - Insufficient in-code comments / code readability
  - Any other coding style issue
- A new tool/lib/package has been introduced (blocking, subject to negotiation)
TESTING (The Merge Request requires additional testing)
- Additional testing is present in the Merge Request (Best)
- The contributor provides a framework/hints for testing
- New testing means need to be developed
DOCUMENTATION (The Merge Request requires additional documentation)
- Feature Set documentation update needed
  - DONE
  - NOT DONE
- Wiki tutorial / in-repo usage documentation needed
  - DONE
  - NOT DONE
- Added/Modified/Removed script/build/runtime option(s)
  - Help UPDATED
  - Help NOT UPDATED