Updated for multiple UEs CBRA procedure.

See merge request aburger/openairinterface5g!86

This change allows multiple UEs to have a tunnel interface
brought up when connecting to the 5GCN

Also, adding two new config files for mutltiple UEs
to connect to the 5GCN

There are two queue.h files in this repository.

When we check if the pointer is NULL before CALLOCing,
then the gNB will crash. It seems that we are mostlikely
leaking memeory since the gNB only crashes with the old
change. By reverting these changes, the gNB does not crash.
We are seeing UE-to-UE IP traffic on this commit when
the tunnel interfaces are established (~50% of the time).

5G IP Traffic for SA mode

See merge request aburger/openairinterface5g!85

MR !1317 : Change variable types in statistics
When running gNB for a long time and transferring high amount of data, statistics become negative (and later in an arithmetic overflow) because they are too short for such amount of bytes. Example: UE 0: ulsch_total_bytes_scheduled -1804219593, ulsch_total_bytes_received -1804223769

MR !1315 : Using rnti to assign different pucch resource to different UE
This MR is to assign different pucch resource to different UE using rnti

MR !1305 : Fix various issues on ULSCH processing on UE
-add mutex to protect ul_config_pdu against race condition with multiple threads. Otherwise UE will crash as parameter of subsequent thread will be overwritten: Assertion (Nl>0) failed!In nr_get_E() openairinterface5g/openair1/PHY/NR_TRANSPORT/nr_tbs_tools.c:47
-Fix a logical error that sends obsolete buffer erroneously on UL and causes crash in gNB. In nr_process_mac_pdu: residual UL MAC PDU in 736.19 with length < 0!, pdu_len -69
-Fix a logical error that if FAPI_NR_UL_CONFIG_TYPE_PUSCH pdu is not of index 0 in ul_config->ul_config_list, the packet is not sent out.


MR !1321 : CI automatic un-deployment of RAN containers + fixes
-in main container pipeline, the post section in the docker-hub-push stage was incorrectly placed 
-when building images on develop pushes, the ran-build image was not built 
-iptables check is correct now (could not detect if in not ACCEPT 
-something is wrong, automatic un-deployment of RAN containers 
-added a "dummy" undeploy scenario just to be sure. 
-4g/5g RF simulation tests may fail due to lost socket on ue container. Repeat in case of failure

ci_bring_test_results_to_dashboard:
-RAN Status and Tests dashboards

cherry pick : nsa conf files, ulsch_max_frame_inactivity = 1;
-to reduce ping time

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

The filtering added in the nrue_procedures.c file
are already happening in the stub function so we
should be duplicating them in the NRUE MAC layer.

In this commit, we changed the UCI handling.
When the UL_TTI_REQ arrives at the NRUE it
has info related to how many UCIs we should
pull from the queue and send to the gNB. If
we do not have that many UCIs available (likely
becasue a DL_TTI_REQ is late), then we will
requeue the UL_TTI_REQ and wait until we have
all the UCI indications before multiplexing.
This change makes it easier to handle multiple
UCIs becasue previously we would send what we
had and then try again later which made keeping
track of the UL_TTI_REQ and second UCI more
difficult.

1. Added rnti filter for multiple UEs.
2. Adjusted mode offset for SA mode.

Also, we had two heap-buffer-overflow crashes while
filling the CRC_IND and RX_IND. The corrected CALLOC
command is included in this commit as well.

Lastly, we included a better fix for handling late
DL_TTI_REQs. If the number of active harqs is larger
than the number of UCIs we have built, this is a good
indicator that the DL_TTI_REQ is late. To mitigate
problems, we will requeue the UL_TTI_REQ to when the
late DL_TTI_REQ comes in, we can handle the late
UCI that is built from it.

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

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

Merge remote-tracking branch 'origin/ci_bring_test_results_to_dashboard' into integration_2021_wk46_c

The nr_rrc_ue_process_RadioBearerConfig() function
call in the RRC layer of the NRUE was removed when
it should not have been for NSA mode. This is now
added back in for NSA mode. Also, the call to
pdcp_run should only be when were NOT in NOS1 mode
and ARE in SA mode. This was fixed as well.

Ue-to-Ue IP traffic in NSA works, but eventually
the NSA UE will crash due to an incorrect PDCCH
configuration. This is a bug we will need to look
into. It doesnt always crash, only about 40% of
the time. And even when the NRUE does crash, it
happens towards the end of the simulation.