15 Commits (9211ad7d51ec6f9b2b6ec85d91440e6df67eaddb)

Author	SHA1	Message	Date
Codebot	fb75a5ef0e	Merge branch 'next' into agpl_next	3 years ago
Fabian Eckermann	12cc7cb4d7	Add support for RRC redirect.	3 years ago
Codebot	585e3c51c1	Merge branch 'next' into agpl_next ... # Conflicts: # srsenb/hdr/phy/nr/cc_worker.h # srsenb/hdr/phy/nr/sf_worker.h # srsenb/src/phy/nr/cc_worker.cc # srsenb/src/phy/nr/sf_worker.cc # test/phy/nr_phy_test.cc	3 years ago
Andre Puschmann	4d11e5552a	rrc,ue: for RRC conn release, delay transition to RRC idle by 60ms as per TS 36.331 ... when receiving RRC connection release all actions shall be delayed by 60ms as per the standard	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.	3 years ago
Codebot	73a61b884e	Merge branch 'next' into agpl_next	3 years ago
Andre Puschmann	c0be8187c8	rlc interface: convert entire read_pdu() interface to return uint32_t ... we had it returning int but had a bug in using the return value properly, i.e. handling when -1 was returned in RLC TM. Thinking about it more, it doesn't make sense to have a negative return value here anyway. Either the RLC can return a PDU or not. If it can't the returned lenght is zero.	3 years ago
Xavier Arteaga	235a664120	SRSUE: Removed PUSCH-DMRS/SRS pregeneration methods	3 years ago
Codebot	77908eed1c	Merge branch 'next' into agpl_next	4 years ago
Andre Puschmann	598594c51a	all: bunch of pass by const& changes suggested by LGTM	4 years ago
Codebot	0a15eeb57a	Adding AGPL copyright to new files	4 years ago
Codebot	34dbee4c7d	Merge branch 'next' into agpl_next	4 years ago
Francisco	60896e30b5	implementation of time wheel-based timer handler, using a circular array and intrusive list	4 years ago
Codebot	24290dcae2	Adding AGPL copyright to new files	4 years ago
Codebot	4523ee6087	rename srsLTE to srsRAN	4 years ago