Explicitly include the mandatory IE cn_support in the E1 Setup Request

* this commit is making explicit the mandatory IE cn_support
  in the E1 Setup Request message
* also, init cn_support in E1 Setup Request initial message preparation
This commit is contained in:
Guido Casati
2025-01-20 13:45:29 +01:00
parent 0cd4aeee5b
commit c0db34077a
2 changed files with 10 additions and 0 deletions
+7
View File
@@ -72,6 +72,11 @@ typedef enum cell_group_id_e {
SCG,
} cell_group_id_t;
typedef enum CN_Support_e {
cn_support_EPC = 0,
cn_support_5GC,
} cn_Support_t;
typedef struct PLMN_ID_s {
int mcc;
int mnc;
@@ -97,6 +102,8 @@ typedef struct e1ap_setup_req_s {
char * gNB_cu_up_name;
uint64_t transac_id;
int supported_plmns;
// CN Support
cn_Support_t cn_support;
struct {
PLMN_ID_t id;
int supported_slices;
+3
View File
@@ -90,6 +90,9 @@ MessageDef *RCconfig_NR_CU_E1(const E1_t *entity)
if (*gnbParms[GNB_GNB_NAME_IDX].strptr)
e1Setup->gNB_cu_up_name = *(gnbParms[GNB_GNB_NAME_IDX].strptr);
// Only 5GC supported
e1Setup->cn_support = cn_support_5GC;
paramdef_t PLMNParams[] = GNBPLMNPARAMS_DESC;
paramlist_def_t PLMNParamList = {GNB_CONFIG_STRING_PLMN_LIST, NULL, 0};
/* map parameter checking array instances to parameter definition array instances */