Configuration Guide
Following diagram shows the overall architecture of Amari Callbox. It shows various components of the Callbox Protocol stack and various configuration files for each components of the callbox software. One of the challenges to configure the callbox as per your requirement would be to figure out which configuration file you need to modify and which parameter you have to set in each of the configuration file. I hope this digram would give you a first level hints to figure out which configuration file you need to pick for your test requirement.
On gNB/eNB side, there are many different types of configuration file. It would be a little challenging to get the detailed understanding on all the details of each and every configuration file. If you are new to Amarisoft System, try to understand the configuration files in the following order. This order is the order in which most of the customer would most frequently changes for the testing. The file location in the list below is based on the assumption that you installed Amarisoft software in default location (/root)
- enb.cfg : located in /root/enb/config
- mme.cfg : located in /root/mme/config
- ims.cfg : located in /root/mme/config
- ue_db.cfg : located in /root/mme/config
- drb.cfg : located in /root/enb/config
- ots.cfg : located in /root/ots/config
enb.cfg -> myenb.cfg
To create the symbolic link as shown above. Run the following command within the corresponding directory.
ln -sf myenb.cfg enb.cfg
Table of Contents
- Configuration Guide
- Overview
- Data Path for Internet Access
- Core Component / Interfaces / Protocol / Port
- Structure of Full Stack Configuration
- Structure of RAN(eNB/gNB) Configuration
- Structure of NAS/Core Configuration
- Structure of IMS Configuration
- Structure of drb Configuration
- Structure of ue-db Configuration
- Structure of Single LTE Cell
- Structure of Single NR/SA Cell
- Structure of NR/NSA Cell (1 LTE + 1 NR)
- Structure of NB-IoT Cell
- Structure of LTE Carrier Aggregation
- Structure of LTE Handover
Overview
The configurations files shown in the diagram above are distributed into two directories as shown below. As shown below, enb directory carries configuration files for RAN side operation and mme directory carries configuration files for core network.
Data Path for Internet Access
Overall data path and components during internet access is illustrated as below.
Core Component / Interfaces / Protocol / Port
- S1AP messages over SCTP port 36412
- NGAP messages over SCTP port 38412
- X2AP messages over SCTP port 36422
- XnAP messages over SCTP port 38422
- GTP-U packets over UDP port 2152
- M2AP messages over SCTP port 36443
- S6, S13, Rx, Cx Diameter messages over SCTP port 3868
- SGsAP messages over SCTP port 29118
- SBcAP messages over SCTP port 29168
- LCsAP messages over SCTP port 9082
- N8 messages over TCP/HTTP2 port 5556
- N5 messages over TCP/HTTP2 port 5570
- N12 messages over TCP/HTTP2 port 5555
- N13 messages over TCP/HPPT2 port 5592
- N17 messages over TCP/HTTP2 port 5557
- N20 messages over TCP/HTTP2 port 5571
- N50 messages over TCP/HTTP2 port 6667
- NL1 messages over TCP/HTTP2 port 5559
- IKEv2 messages over UDP port 500 and 4500
- SIP messages over UDP/TCP port 5060
Structure of Full Stack Configuration
This shows the overall configuration file structure for the full stack configuration from RAN through Core Network/Application Layer, The purpose is not to show each and every detailed parameters for the full stack. This is just to show the overall structure of each configuration file for each component (i.e, RAN, Core network, Application layer etc)
Structure of RAN(eNB/gNB) Configuration
This configuration is the one pointed by (symbolically linked to) enb.cfg. This is to configure the full stack of RAN (eNB or gNB or Both) from PHY through RRC/PDCP.
|
{
},
{ /* RF port for the first cell */ }, { /* RF port for the second cell */ }, ],
{ mme_addr: /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ }, ],
{ amf_addr: /* address of AMF for NGAP connection. Must be modified if the AMF runs on a different host. */ }, ],
],
],
/* PHY Configurations */
mac_config: { /* MAC configuration (same for all UEs) */ },
srb_config: [ /* SRB configuration */ ],
drb_config: /* DRB configuration. Links to a separate file for drb configuration */ },
/* PHY Configurations */
mac_config: { /* MAC configuration (same for all UEs) */ },
srb_config: [ /* SRB configuration */ ],
drb_config: /* DRB configuration. Links to a separate file for drb configuration */ } |
Among the parameters in the RAN configuration file, there are a set of parameters that applies in common regardless of RAN type and there are a set of parameters that are specific to a specify type of RAN.
- logging related parameters
- log_options
- log_filename
- Remote API related parameter
- com_addr
- rf related parameters
- rf_driver
- tx_gain
- rx_gain
- rf_ports
- core network related parameters
- mme_list
- amf_list
- gtp_addr
The set of parameters that are specific to a specific types of RAN is summarized as follows. In this overall structure, I will put only a small portions of parameters that are most frequently changed by users. You may refer to lteenb documents for those parameters that are not mentioned here.
Structure of NAS/Core Configuration
This configuration is the one pointed by (symbolically linked to) mme.cfg. This is to configure NAS layer and Core network
|
{
],
},
],
]
} |
Structure of APN/QoS Configuration
APN/QoS configuration is done as a part of mme.cfg (NAS and Core configuration) and basic structure is as follows. You can configure as many as APN you want in pdn_list:[ ] Array.
|
{
{ pdn_type: ipv4, ipv6, ipv4v6, unstructured (default = ipv4). Select the PDN or PDU session type. access_point_name: the Access Point Name. Use dots (.) to separate the APN elements. first_ip_addr: first ip address of the ip address sets which are reserved for UE last_ip_addr: last ip address of the ip address sets which are reserved for UE ip_addr_shift: The gap in the last segment of IP address from the previous IP. The gap is applied with 2^ip_addr_shift, dns_addr: IPv4 or IPv6 addresses of the DNS servers.
{ qci: QoS Class Identifier of the E-RAB or 5G QoS Identifier of the QOS flow. priority_level: Priority level. pre_emption_capability: the ability of a particular type of traffic to displace other ongoing lower priority traffic when network resources are limited. pre_emption_vulnerability: the susceptibility of a particular type of traffic to being displaced by other traffic with higher priority and pre-emption capability. }, ], }, ]
} |
Structure of Network Slice Configuration
Network slices are configured in both gNB and Core network configuration file.
Network Slice Configuration on gNB Configuration file (enb.cfg) is as in the following structure. You can configure it in plmn_list[] object and put it in nr_cell_list[] or nr_cell_default: { } as shown below.
|
{ /* Enable remote API and Web interface */ com_addr: "0.0.0.0:9001",
rf_driver: {Define and Configure rf_driver. this is the part in which you can configure what kind of RF hardware you use (e.g, Amarisoft SDR Card or Remote Radio Header etc) ... },
amf_list: [This is the ip address of your 5Gcore network { ... }, ],
gtp_addr: "ip",This is the ip address of NIC that is connected to core network
en_dc_support: true,
rf_ports: [This is the configuration for the RF port of your hardware like frequency, sampling rate, number of antenna etc {
}, ],
/* list of cells */ cell_list: [],This is configuration for NR cell, but is set to be empty when RAT is NR SA single cell
nr_cell_list: [Configuration for NR Cells { rf_port: value, cell_id: value,
/* band, arfcn, SCS, SSB bitmap */ }, ], /* nr_cell_list */
{ tac: 100, plmn: "00101", reserved: false, { sst: Slice Service Type., sd: (Optional) Slice Differentiator. } ], }, ],
}, } |
Network Slice Configuration on Core Network Configuration (mme.cfg) is as in the following structure.
|
{ { sst: Slice Service Type., sd: Slice Differentiator. }, ],
{ ....
... },
{ snssai: { S-NSSAI value. sst: Slice Service Type., sd: (Optional) Slice Differentiator. }, qos_flows: [ Array of QoS flows. Each element of the array has the same structure as an element in erabs except that "5qi" shall be used instead of "qci". { "5qi": 5QI value priority_level: Priority level. pre_emption_capability: the ability of a particular type of traffic to displace other ongoing lower priority traffic when network resources are limited. pre_emption_vulnerability: the susceptibility of a particular type of traffic to being displaced by other traffic with higher priority and pre-emption capability. }, ], },
], ]
} |
Structure of IMS Configuration
This configuration is the one pointed by (symbolically linked to) ims.cfg. This is to configure IMS
|
{
... ],
... ],
} |
Structure of drb Configuration
This file is to configure drb (data radio bearer). This is not a major configuration file. It is a kind of subsidiary configuration file that are included in other major configuration file like enb.cfg.
|
[
{
}, */ },
}, restrict_to_ng_enb: If set to true, the nr_pdcp_config settings are only used for UEs connected to the ng-eNB },
},
}, ] |
Structure of ue-db Configuration
This file is to configure USIM / ISIM information. This is not a major configuration file. It is a kind of subsidiary configuration file that are included in other major configuration file like mme.cfg and ims.cfg.
|
{ { sim_algo: USIM authentication algorithm: xor, milenage or tuak imsi: IMSI value amf: Authentication Management Field sqn: Sequence Number K: K value
impi: IMS priviate user identity impu: IMS public user identity domain: Home Network Domain name authent_type: Athentication Algorithm }, |
Structure of Single LTE Cell
This shows the overall configuration file structure for Single LTE Cell. This is based on enb.default.cfg and you can refer to enb.default.cfg file for the example of detailed parameters.
The key points to note here are
- There are two main components - cell_list:[ ] array and cell_default:{ } object.
- cell_list:[] is an array that configures LTE cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- cell_list[] contains only one object { } in it indicating that only one cell is configured.
- cell_default:{ } is an object that applies the same configuration for all the cells configured in cell_list:[]
- If there is same parameter configured both in cell_list[] and cell_default:{ }, the parameter defined in cell_list[] is used
|
{ /* Enable remote API and Web interface */ com_addr: "ip", /* RF driver configuration. sdr card mapping is configured in the file : rf_driver/config.cfg */ include "rf_driver/config.cfg",
{ /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ mme_addr: "ip", }, ], /* GTP bind address (=address of the ethernet interface connected to the MME). Must be modified if the MME runs on a different host. */
/* high 20 bits of SIB1.cellIdentifier */ enb_id: 0x1A2D0,
/* list of cells */ { /* Broadcasted PLMN identities */ plmn_list: [ "mccmnc", ],
dl_earfcn: value,
/* cell ID */ /* RACH Config applicable only to this cell */ }, ], /* cell_list */
/* default cell parameters */
/* Number of Antenna for DL/UL and Bandwidth*/ n_antenna_dl: value, n_antenna_ul: value, n_rb_dl:
/* phich configuration */ /* SIB Configuration */ /* PDSCH dedicated config (currently same for all UEs) */ /* PRACH Config */ /* PUCCH dedicated config (currently same for all UEs) */ /* PUSCH dedicated config (currently same for all UEs) */ /* Scheduling request period (ms). Must be >= 40 for HD-FDD */ /* CQI report config */ /* RI reporting config */ /* transmission mode */ /* SRS dedicated config. */ /* MAC configuration (same for all UEs) */ /* CPU load limitation */ /* dynamic power control */ /* RRC/UP ciphering algorithm preference. EEA0 is always the last. */ /* RRC integrity algorithm preference. EIA0 is always the last. */ /* (in ms) send RRC connection release after this time of network inactivity */ /* SRB configuration */ /* DRB configuration */ }, |
Structure of Single NR/SA Cell
This shows the overall configuration file structure for Single NR/SA Cell. This is based on gnb-sa.cfg and you can refer to gnb-sa.cfg file for the example of detailed parameters.
The key points to note here are
- There are two main components - nr_cell_list:[ ] array and nr_cell_default:{ } object.
- nr_cell_list:[] is an array that configures NR cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- nr_cell_list[] contains only one object { } in it indicating that only one cell is configured.
- nr_cell_default:{ } is an object that applies the same configuration for all the cells configured in nr_cell_list:[]
- If there is same parameter configured both in nr_cell_list[] and nr_cell_default:{ }, the parameter defined in nr_cell_list[] is used
|
{ /* Enable remote API and Web interface */ com_addr: "0.0.0.0:9001",
name: "sdr", /* list of devices. 'dev0' is always the master. */ /* TDD: force the RX antenna on the RX connector */ /* synchronisation source: none, internal, gps, external (default = none) */ // sync: "gps", },
{ /* address of AMF for NGAP connection. Must be modified if the AMF runs on a different host. */ amf_addr: "ip", }, ],
/* GTP bind address (=address of the ethernet interface connected to the AMF). Must be modified if the AMF runs on a different host. */
en_dc_support: true,
{
}, ],
/* list of cells */
{ rf_port: value, cell_id: value,
/* band, arfcn, SCS, SSB bitmap */ band: dl_nr_arfcn: subcarrier_spacing: ssb_pos_bitmap: }, ], /* nr_cell_list */
/* number of antenna for DL, UL, CBW */ bandwidth: n_antenna_dl: value, n_antenna_ul: value, /* UL/DL Pattern (Applicable to TDD only) */ /* PLMN List */ /* SIB scheduling */ /* Basic MIB/SIB1 Parameters */ /* PRACH Params */ /* PDCCH Params */ /* PDSCH Params */ /* CSI-RS Params */ /* PUCCH Params */ /* SRS Params */ /* PUSCH Params */ /* MAC configuration */ /* Ciphering, Integrity Option */ /* DRB Config */ }, } |
Structure of NR/NSA Cell (1 LTE + 1 NR)
This shows the overall configuration file structure for NR/NSA Cell(1 LTE + 1NR). This is based on gnb-nsa.cfg and you can refer to gnb-nsa.cfg file for the example of detailed parameters.
The key points to note here are
- There are two main components - nr_cell_list:[ ] array and nr_cell_default:{ } object.
- cell_list[] is an array that configures LTE cell and nr_cell_list:[] is an array that configures NR cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- cell_list[] contains only one object { } in it indicating that only one LTE cell is configured.
- nr_cell_list[] contains only one object { } in it indicating that only one NR cell is configured.
- cell_default:{ } is an object that applies the same configuration for all the cells configured in cell_list:[]
- nr_cell_default:{ } is an object that applies the same configuration for all the cells configured in nr_cell_list:[]
- If there is same parameter configured both in cell_list[] and cell_default:{ }, the parameter defined in cell_list[] is used
- If there is same parameter configured both in nr_cell_list[] and nr_cell_default:{ }, the parameter defined in nr_cell_list[] is used
|
/* Enable remote API and Web interface */ com_addr: "0.0.0.0:9001",
name: "sdr",
/* list of devices. 'dev0' is always the master. */ /* TDD: force the RX antenna on the RX connector */ /* synchronisation source: none, internal, gps, external (default = none) */
},
{ /* RF port for the LTE cell */ }, { /* RF port for the NR cell */ }, ],
{ /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ }, ],
/* GTP bind address (=address of the ethernet interface connected to the MME). Must be modified if the MME runs on a different host. */
/* list of cells */ { rf_port: 0, /* Broadcasted PLMN identities */ plmn_list: [ "00101", ], /* Cell Frequency */ dl_earfcn: value, /* Cell ID - PCI, TAC */ /* PRACH Root Sequence */
{ cell_id: id_value } ], }, ], /* cell_list */
{ rf_port: 1, /* Cell ID */ /* Cell Frequency - ARFCN, SCS, SSB Position */ band: dl_nr_arfcn: subcarrier_spacing: ssb_pos_bitmap: }, ], /* nr_cell_list */
/* default cell parameters for LTE */ /* Number of DL / UL Antenna */ n_antenna_dl: , n_antenna_ul: ,
/* Number of DL RB */ n_rb_dl:
/* SIB1 */ /* SIB schedule for Other SIBs */#if N_RB_DL == 6 /* PDSCH dedicated config (currently same for all UEs) */ /* RACH Config */ /* PUCCH dedicated config (currently same for all UEs) */ /* PUSCH dedicated config (currently same for all UEs) */ /* MCS for Msg3 (=CCCH RRC Connection Request) */ /* this CQI value is assumed when none is received from the UE */ /* Scheduling request period (ms). Must be >= 40 for HD-FDD */ /* CQI report config */ /* RI reporting is done with a period of m_ri * cqi_period. m_ri = 0 (default) disables RI reporting. */ /* transmission mode */ /* SRS dedicated config. All UEs share these parameters. srs_config_index and freq_domain_position are allocated for each UE) */ /* MAC configuration (same for all UEs) */ /* CPU load limitation */ /* dynamic power control */ /* RRC/UP ciphering algorithm preference. EEA0 is always the last. */ /* RRC integrity algorithm preference. EIA0 is always the last. */ /* (in ms) send RRC connection release after this time of network inactivity */ /* SRB configuration */ /* measurement configuration */ /* DRB configuration */ },
/* default cell parameters for NR */ /* NR Bandwidth, Number of DL / UL Antenna */ bandwidth: n_antenna_dl: value, n_antenna_ul: value, /* force the timing TA offset (optional) */ /* TDD Pattern (Applicable only to TDD) */ /* SSB Period */ /* Cell ID (PCI) */ /* Scheduling request period (slots). */ /* DMRS A Pos */ /* RACH Config */ /* PDCCH Config - Both Common and Dedicated */ /* PDSCH Config */ /* CSI-RS Config */ /* PUCCH Config */ /* SRS Config */ /* PUSCH Config */ /* MAC configuration */ /* Ciphering / Integrity Config */ /* SRB Support - Enable/Disable */ /* DRB Config */ }, } |
Structure of NB-IoT Cell
This shows the overall configuration file structure for NB-IoT Cell. This is based on enb-nbiot.cfg and you can refer to enb-nbiot.cfg file for the example of detailed parameters. Basically the overall structure of NB-IoT cell configuration is same as LTE cell configuration because NB-IoT is also a type of LTE protocol. There are differences only in terms of detailed configurations
The key points to note here are
- There are two main components - nb_cell_list:[ ] array and nb_cell_default:{ } object in case of Standalone mode. If the operation mode is NOT standalone, you need to configure cell_list:[] as well.
- nb_cell_list:[] is an array that configures LTE cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- nb_cell_list[] contains only one object { } in it indicating that only one cell is configured.
- nb_cell_default:{ } is an object that applies the same configuration for all the cells configured in nb_cell_list:[]
- If there is same parameter configured both in nb_cell_list[] and nb_cell_default:{ }, the parameter defined in nb_cell_list[] is used
|
{ /* Enable remote API and Web interface */ com_addr: "ip", /* RF driver configuration. sdr card mapping is configured in the file : rf_driver/config.cfg */ include "rf_driver/config.cfg",
{ /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ mme_addr: "ip", }, ], /* GTP bind address (=address of the ethernet interface connected to the MME). Must be modified if the MME runs on a different host. */
/* high 20 bits of SIB1.cellIdentifier */ enb_id: 0x1A2D0,
/* list of cells */ { /* Broadcasted PLMN identities */ plmn_list: [ "mccmnc", ],
dl_earfcn: ,
/* cell ID */ /* RACH Config applicable only to this cell */ }, ], /* cell_list */
{ plmn_list: [ ], n_antenna_dl: , n_antenna_ul: , operation_mode: dl_prb: ul_prb: base_cell_id:, operation_mode: dl_earfcn: ,
non_anchor_list : [ { dl_prb: , ul_prb: , operation_mode: }, ],
}, ], /* nbcell_list */
/* default cell parameters */
{ /* RACH Configuration */ /* msg3 configuration */ /* Paging */ /* NPDCCH User Search Space */ /* NPDSCH config */ /* NPUSCH config */ }, ];
/* SIB Configuration */ /* SRB configuration */ },
|
Structure of LTE Carrier Aggregation
This shows the overall configuration file structure for Single LTE Cell. This is based on enb-3cc.cfg and you can refer to enb-3cc.cfg file for the example of detailed parameters.
The key points to note here are
- There are two main components - cell_list:[ ] array and cell_default:{ } object.
- cell_list:[] is an array that configures LTE cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- cell_list[] contains multiple object { } (usually two or more objects indicating PCC and SCC cells).
Keypoint is that each cell configuration has scell_list:[ ] to specify the list of SCC(Secondary Component Carrier). - cell_default:{ } is an object that applies the same configuration for all the cells configured in cell_list:[]
- If there is same parameter configured both in cell_list[] and cell_default:{ }, the parameter defined in cell_list[] is used
|
{ /* Enable remote API and Web interface */ com_addr: "ip", /* RF driver configuration. sdr card mapping is configured in the file : rf_driver/config.cfg */ include "rf_driver/config.cfg",
{ /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ mme_addr: "ip", }, ], /* GTP bind address (=address of the ethernet interface connected to the MME). Must be modified if the MME runs on a different host. */
/* high 20 bits of SIB1.cellIdentifier */ enb_id: 0x1A2D0,
/* list of cells */ { rf_port: , n_id_cell: ,
dl_earfcn: ,
{ cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, { cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, ], }, { rf_port: , n_id_cell: ,
dl_earfcn: ,
{ cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, { cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, ], }, { rf_port: , n_id_cell: ,
dl_earfcn: ,
{ cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, { cell_id: , cross_carrier_scheduling: , scheduling_cell_id: , ul_allowed, rrc_configuration ,
}, ], }, ], /* cell_list */
/* default cell parameters */
/* Number of Antenna for DL/UL and Bandwidth*/ n_antenna_dl: value, n_antenna_ul: value, n_rb_dl:
/* phich configuration */ /* SIB Configuration */ /* PDSCH dedicated config (currently same for all UEs) */ /* PRACH Config */ /* PUCCH dedicated config (currently same for all UEs) */ /* PUSCH dedicated config (currently same for all UEs) */ /* Scheduling request period (ms). Must be >= 40 for HD-FDD */ /* CQI report config */ /* RI reporting config */ /* transmission mode */ /* SRS dedicated config. */ /* MAC configuration (same for all UEs) */ /* CPU load limitation */ /* dynamic power control */ /* RRC/UP ciphering algorithm preference. EEA0 is always the last. */ /* RRC integrity algorithm preference. EIA0 is always the last. */ /* (in ms) send RRC connection release after this time of network inactivity */ /* SRB configuration */ /* DRB configuration */ }, |
Structure of LTE Handover
This shows the overall configuration file structure for Handover between LTE Cells. This is based on enb-2cell-ho.cfg and you can refer to enb-2cell-ho.cfg file for the example of detailed parameters.
The key points to note here are
- There are two main components - cell_list:[ ] array and cell_default:{ } object.
- cell_list:[] is an array that configures LTE cell (Ref : cell_list[] is for LTE cell configuration, nr_cell_list[] is for NR cell configuration)
- cell_list[] contains multiple object { } (usually two objects source and target cell).
Keypoint is that each cell configuration has ncell_list:[ ] to specify the destination for the handover. - cell_default:{ } is an object that applies the same configuration for all the cells configured in cell_list:[]
- If there is same parameter configured both in cell_list[] and cell_default:{ }, the parameter defined in cell_list[] is used
|
{ /* Enable remote API and Web interface */ com_addr: "ip", /* RF driver configuration. sdr card mapping is configured in the file : rf_driver/config.cfg */ include "rf_driver/config.cfg",
{ /* address of MME for S1AP connection. Must be modified if the MME runs on a different host. */ mme_addr: "ip", }, ], /* GTP bind address (=address of the ethernet interface connected to the MME). Must be modified if the MME runs on a different host. */
/* high 20 bits of SIB1.cellIdentifier */ enb_id: 0x1A2D0,
/* list of cells */ { rf_port: , n_id_cell: ,
dl_earfcn: ,
{ n_id_cell: , dl_earfcn: , }, ], }, { rf_port: , n_id_cell: ,
dl_earfcn: ,
ncell_list: [ { n_id_cell: , dl_earfcn: , }, ], }, ], /* cell_list */
/* default cell parameters */
/* Number of Antenna for DL/UL and Bandwidth*/ n_antenna_dl: value, n_antenna_ul: value, n_rb_dl:
/* phich configuration */ /* SIB Configuration */ /* PDSCH dedicated config (currently same for all UEs) */ /* PRACH Config */ /* PUCCH dedicated config (currently same for all UEs) */ /* PUSCH dedicated config (currently same for all UEs) */ /* Scheduling request period (ms). Must be >= 40 for HD-FDD */ /* CQI report config */ /* RI reporting config */ /* transmission mode */ /* SRS dedicated config. */ /* MAC configuration (same for all UEs) */ /* CPU load limitation */ /* dynamic power control */ /* RRC/UP ciphering algorithm preference. EEA0 is always the last. */ /* RRC integrity algorithm preference. EIA0 is always the last. */ /* (in ms) send RRC connection release after this time of network inactivity */ /* SRB configuration */ /* DRB configuration */
a1_report_type: , a1_rsrp: , a1_hysteresis: , a1_time_to_trigger: , a2_report_type: , a2_rsrp: , a2_hysteresis: , a2_time_to_trigger: , eutra_handover: { a3_report_type: , a3_offset: , hysteresis: , time_to_trigger: } },
}, |