message    repeated MbsfnSubframe mbsfn_subframe_infos = 9;Enb {
    stringEnbType csgenb_idtype = 101;
    repeated stringServedCellInfo mbms_service_area_identitiesserved_cells = 112;
    repeated uint32string multiband_infos = 12;
    FreqBandIndicatorPriority freq_band_indicator_prioritygu_group_ids = 13;
    BandwidthReducedSI bandwidth_reduced_si = 14;
    repeated NeighbourInformation neighbour_infos = 15;
}

message Gnb {
    repeated ServedNRCell served_nr_cells = 1;
	float cell_longitude    repeated RanFunction ran_functions = 2;
	float antenna_height = 3;
	float antenna_azimuth_direction = 4;
	float antenna_tilt_angle = 5;
	float antenna_max_transmit = 6;
	float antenna_max_gain = 7;
	uint32 sector_id = 8}

message ServedNRCell {
    ServedNRCellInformation served_nr_cell_information = 1;
    repeated NrNeighbourInformation nr_neighbour_infos = 2;
}

message ServedNRCellInformation {
	...
	AdditionalCellInformation additional_cell_information = 16;
}

I've already added the below method as part of the gNB update cells US (for a case we get an empty list from the client):

RemoveServedNrCells(inventoryName string, servedNrCells []*entities.ServedNRCell) error

• POST /v1/nodeb/enb is triggered, request body is validated
• Execute GetNodeb

type AddEnbRequestHandler struct {
	logger 				*logger.Logger		
	rnibDataService		services.RNibDataService
}

• DELETE /v1/nodeb/enb/<RAN_NAME> is triggered.
• Execute GetNodeb with RAN name coming from the request.
  • If we have a DB error or if it doesn't exist → error
  • If nodeb is of type gNB → error
• Execute RemoveEnb 
  • Remove cells from both Cell ID key & PCI key (call RemoveServedCells)
  • Remove nodeb from both RAN ID key & RAN NAME key
  • Remove nbIdentity
  • Execute sdl.SetAndPublish(data,"RAN_MANIPULATION", "<RAN_NAME>_DELETED")
• Return 

  Status
  colour Green title 204 No Content

   response.

type DeleteEnbRequestHandler struct {
	logger 				*logger.Logger		
	rnibDataService		services.RNibDataService
}