-
batuhan duyuler authored
- NeighbourCell and Measurement Configurations are prepared. NeighbourCell Configuration includes: - neighbour_gNB_ID (This is needed for AMF to identify gNB exists in it's context - neighbour_nr_cell_id (This is needed for target gNB) - neighbour_physical_cellId (This is needed for UE in the meas report) - neighbour_absoluteFrequencySSB (This is needed for UE in meas report) - neighbour_subcarrierSpacing (This is needed for UE in meas report) - neighbour_mnc (This is needed for AMF) - neighbour_mcc (This is needed for AMF) - neighbour_mnc_length (This is needed for AMF) - neighbour_tracking_area_code (This is needed for AMF) NR Measurement Event Configuration Includes: - enableA2 & enableA3 (gNB activates the event reporting according to these vars) - thresholdA2 & A2_TTT (configurable reporting parameters) - thresholdA3 & A3_Hysteresis & A3_TTT (configurable reporting parameters) - These parameters are read in the configuration parsing part and written under RRC structure - Event Based Measurement Configuration is prepared according to enableA3 parameter. - Measurement Configuration of UE is cloned under UE Context. When a measurement report comes, looping through the UE's meas config and matching the measIDs. With this measID, report configs extracted and processing in different ways.
607f192c