5g-team
/
srsRAN_4G
mirror of https://github.com/pvnis/srsRAN_4G.git
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
fix-cqi
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'bef3553586'
${ noResults }
srsRAN_4G/lib/include/srsran/interfaces/ue_pdcp_interfaces.h

76 lines
3.6 KiB
C
Raw Normal View History Unescape Escape

move ue pdcp interfaces to separate interfaces header file
4 years ago
/**
*
* \section COPYRIGHT
*
rename srsLTE to srsRAN
4 years ago
* Copyright 2013-2021 Software Radio Systems Limited
move ue pdcp interfaces to separate interfaces header file
4 years ago
*
* By using this file, you agree to the terms and conditions set
* forth in the LICENSE file which can be found at the top level of
* the distribution.
*
*/
rename srsLTE to srsRAN
4 years ago
#ifndef SRSRAN_UE_PDCP_INTERFACES_H
#define SRSRAN_UE_PDCP_INTERFACES_H
move ue pdcp interfaces to separate interfaces header file
4 years ago
#include "pdcp_interface_types.h"
rename srsLTE to srsRAN
4 years ago
#include "srsran/common/byte_buffer.h"
move ue pdcp interfaces to separate interfaces header file
4 years ago
namespace srsue {
class pdcp_interface_rrc
{
public:
virtual void reestablish() = 0;
virtual void reestablish(uint32_t lcid) = 0;
virtual void reset() = 0;
Stop PDCP for data bearers before initiating HO
3 years ago
virtual void set_enabled(uint32_t lcid, bool enabled) = 0;
rename srsLTE to srsRAN
4 years ago
virtual void write_sdu(uint32_t lcid, srsran::unique_byte_buffer_t sdu, int sn = -1) = 0;
Some LGTM fixes (#3564) * Fix LGTM issues * ue: add logging to switch on function * Fix new LGTM issues
3 years ago
virtual int add_bearer(uint32_t lcid, const srsran::pdcp_config_t& cnfg) = 0;
Added functionality for releasing a NR bearer
4 years ago
virtual void del_bearer(uint32_t lcid) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
virtual void change_lcid(uint32_t old_lcid, uint32_t new_lcid) = 0;
all: bunch of pass by const& changes suggested by LGTM
4 years ago
virtual void config_security(uint32_t lcid, const srsran::as_security_config_t& sec_cfg) = 0;
virtual void config_security_all(const srsran::as_security_config_t& sec_cfg) = 0;
rename srsLTE to srsRAN
4 years ago
virtual void enable_integrity(uint32_t lcid, srsran::srsran_direction_t direction) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
virtual void enable_encryption(uint32_t lcid,
rename srsLTE to srsRAN
4 years ago
srsran::srsran_direction_t direction = srsran::srsran_direction_t::DIRECTION_TXRX) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
virtual void send_status_report() = 0;
virtual void send_status_report(uint32_t lcid) = 0;
};
class pdcp_interface_rlc
{
public:
/* RLC calls PDCP to push a PDCP PDU. */
rename srsLTE to srsRAN
4 years ago
virtual void write_pdu(uint32_t lcid, srsran::unique_byte_buffer_t sdu) = 0;
virtual void write_pdu_bcch_bch(srsran::unique_byte_buffer_t sdu) = 0;
virtual void write_pdu_bcch_dlsch(srsran::unique_byte_buffer_t sdu) = 0;
virtual void write_pdu_pcch(srsran::unique_byte_buffer_t sdu) = 0;
virtual void write_pdu_mch(uint32_t lcid, srsran::unique_byte_buffer_t sdu) = 0;
virtual void notify_delivery(uint32_t lcid, const srsran::pdcp_sn_vector_t& pdcp_sn) = 0;
virtual void notify_failure(uint32_t lcid, const srsran::pdcp_sn_vector_t& pdcp_sn) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
};
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
// Data-plane interface for Stack after EPS bearer to LCID conversion
class pdcp_interface_stack
move ue pdcp interfaces to separate interfaces header file
4 years ago
{
public:
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
virtual void write_sdu(uint32_t lcid, srsran::unique_byte_buffer_t sdu, int sn = -1) = 0;
virtual bool is_lcid_enabled(uint32_t lcid) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
};
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
// STACK interface for GW (based on EPS-bearer IDs)
class stack_interface_gw
move ue pdcp interfaces to separate interfaces header file
4 years ago
{
public:
virtual bool is_registered() = 0;
virtual bool start_service_request() = 0;
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
virtual void write_sdu(uint32_t eps_bearer_id, srsran::unique_byte_buffer_t sdu) = 0;
///< Allow GW to query if a radio bearer for a given EPS bearer ID is currently active
virtual bool has_active_radio_bearer(uint32_t eps_bearer_id) = 0;
move ue pdcp interfaces to separate interfaces header file
4 years ago
};
} // namespace srsue
rename srsLTE to srsRAN
4 years ago
#endif // SRSRAN_UE_PDCP_INTERFACES_H