7 Commits (f99e841421b07d21eb397b59081e6670cd7285fb)

Author	SHA1	Message	Date
Ismael Gomez	d972fb368c	Some LGTM fixes (#3564) ... * Fix LGTM issues * ue: add logging to switch on function * Fix new LGTM issues	3 years ago
Ismael Gomez	1c77998df5	Stop PDCP for data bearers before initiating HO	3 years ago
Andre Puschmann	483a216bd5	ue,stack: refactor handling of radio bearears in UE stack ... this is a rather large commit that is hard to split because it touches quite a few components. It's a preparation patch for adding NR split bearers in the next step. We realized that managing RLC and PDCP bearers for both NR and LTE in the same entity doesn't work. This is because we use the LCID as a key for all accesses. With NR dual connectivity however we can have the same LCID active at the same time for both LTE and NR carriers. The patch solves that by creating a dedicated NR instance for RLC/PDCP in the stack. But then the question arises for UL traffic on, e.g. LCID 4 what PDCP instance the GW should use for pushing SDUs. It doesnt' know that. And in fact it doesn't need to. It just needs to know EPS bearer IDs. So the next change was to remove the knowledge of what LCIDs are from the GW. Make is agnostic and only work on EPS bearer IDs. The handling and mapping between EPS bearer IDs and LCIDs for LTE or NR (mainly PDCP for pushing data) is done in the Stack because it has access to both. The NAS also has a EPS bearer map but only knows about default and dedicated bearers. It doesn't know on which logical channels they are transmitted.	4 years ago
Andre Puschmann	598594c51a	all: bunch of pass by const& changes suggested by LGTM	4 years ago
David Rupprecht	6b41ae7e8b	Updated PDCP config struct for rat type	4 years ago
David Rupprecht	56e947bf27	Added functionality for releasing a NR bearer	4 years ago
Codebot	4523ee6087	rename srsLTE to srsRAN	4 years ago