-Add also a temporary artificial trigger just to be able to test with OAI UE
-Comment out most of the part of the UE context release command handler function at the DU in order to separate properly the RRC from F1AP functionality later.

Trigger dedicated RRC Reconfiguration after processing F1 UE context modification response at RRC layer of the CU

-Successful user-plane traffic over F1-U upon completion of UE context modification procedures

-Fix some indentations

Add handling of UE context modification request at RRC layer of the DU and trigger UE context modification response

-Next step: Proper generation of UE context modification response at F1AP layer

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

-Fix indentation in UE context modification request message generation function at the CU

Trigger UE context modification request at the CU upon reception of PDU Session Resource setup request from the AMF

-F1 message successfully encoded at the CU (including SRB2, DRB and F1-U tunnel configuration) and received from the DU.
-Next steps: handling of UE context modification request at the DU and triggering the UE context setup response towards the CU.

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

doc(release): Updating the 5F RF simulator documentation and docker-compose following the v1.2.0 release of OAI-CN5G
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

doc(release): Updating the 5F RF simulator documentation and docker-compose following the v1.2.0 release of OAI-CN5G
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Merge branch 'NR_F1C_F1U_extensions' of https://gitlab.eurecom.fr/oai/openairinterface5g into NR_F1C_F1U_extensions

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Additional corrections for non-mandatory presence of DRB,SRB setup lists in handling of F1AP UE ctxt setup request,response messages

Use the updates of the masterCellGroup configuration as input to UE context setup response, instead of the whole mastercellgroup configuration stored at the UE context of the DU.

-Deallocate memory for the updates on masterCellGroup config. after the information is encoded.

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

-Trigger UE context setup response at the DU and RRC Reconfiguration at the CU upon reception of UE context setup response.
-Pending: The DU should generate some updates on the master cell groupconfig based also on the received UE capabilities and add them in
 the UE context setup response message so that they can be included in the RRC Reconfiguration message sent from the CU. For the moment the
 corresponding function is empty.
-Next steps: trigger UE context modification procedures

MR !1272 : \[DOC\] NR feature set update  
MR !1244 : \[DOC\] Update SA tutorial  
MR !1269 : \[CI\] dashboard creds and executor change  
MR !1262 : \[CI\] jenkins pipe to write test results to mysql  
MR !1250 : NR_NSA_no_msg3_retransmission  
MR !1264 : NR_UE_IF_FREQ (IF frequency command line option at OAI UE)

-Include UE_Capability_RAT_container_list in UE context setup request so that it gets processed at the DU
-Next steps: DU should store and process the UE capabilities and generate updates in master cell group config
to be included in UE context setup response. Then upon reception of UE context setup response, the first RRC Reconfiguration
can be triggered at the CU with the updates on master cell group config.