The timing advance field could be abstracted in
the proxy gNB. Currently we are not abstracting
this value.

Attempting to manually cherry-pick this commit:
30c14c2f

nfapi.c: Add on_error()

See merge request aburger/openairinterface5g!96

If we dont have this break we are trying to queue
the UL_TTI_REQ we just queued

We have gotten rid of filling the ACK/NACK with
the DLSCH and now only fill with the PUCCH. This
assumes that the MAC layer is properly decoding the
dl_tti_req and tx_data_req and allows us to
simply use the MAC layers scheduled SNF/Slot
to return the ACK NACK. There are some hacks added
in this commit which ensure that the PDCP packet
has the correct header (1st byte = 80) and now with
15Mbps we are seeing about 20% packet loss and
a gNB bug on the edge case (current frame is 1023
and the gNB schduler wants an ACK in frame 0 but the
scheduled UL_TTI_REQ has a frame of 1023).

Several of these changes were made previously and
lost in the merge.

This now matches the develop branch as well.

We should be setting the queued UCI indication slot
based on the SCHEDULED slot, not the current slot.

Added NR to NUM_MCS for nr channel modeling.

See merge request aburger/openairinterface5g!109

Removed strange characters in the first line.

See merge request aburger/openairinterface5g!108

Added logs for timing analysis.

See merge request aburger/openairinterface5g!106

Downlink SISO modeling

See merge request aburger/openairinterface5g!104

It seems that the RA procedure in the gNB was modified so
the RAR is sent in a single tx_data_req. The emualted mode
was not previously handling this. We now only process the
PDU in the rx_ind that has a matching preamble. If any
other PDUs exist, we ignore them and only build Msg3 based
on this single matching RAR PDU.

Also, two bug fixes applied here in the emulate-l1 mode.

integration_2022_wk06

See merge request oai/openairinterface5g!1433

This struct is used to store the uplink 5G nFAPI
messages between the proxy and the gNB MAC layer.
The original OAI implementation utilizes a similarly
named variable (UL_info) to store the uplink 5G nFAPI
messages between the PHY and MAC layer. This commit
will utilize the original UL_info variable prior to
calling the handle functions. These changes allow us
to make minimal changes to the nFAPI handle functions
and modifies the NR_UL_Indication parent function instead.

Merge remote-tracking branch 'origin/lte-ue-fix-EpsNetworkFeatureSupport' into integration_2022_wk06

Integration 2022 wk05 b

See merge request oai/openairinterface5g!1430

This partially reverts commit bac8bc56
and fixes nr_dlschsim, which did not compile without this commit.

We have to eat all the bytes, not only one.
We have to get the bit we want from the right buffer position.

Note: only one bit is supported from this "EPS network feature support",
not sure how to properly deal with it, so let's keep the code as it is.

This commit was made because the MAGMA MME sends "EPS network feature
support" to the UE in the NAS message "Attach Accept". OAI MME does not
send this. So the bug about size was not seen.