This design matches the requirements in the following USs:
We shall add a new proto message, named AdditionalCellInformation
:
message AdditionalCellInformation { float cell_latitude = 1; float cell_longitude = 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 Enb { EnbType enb_type = 1; repeated ServedCellInfo served_cells = 2; repeated string gu_group_ids = 3; } message ServedCellInfo { ... AdditionalCellInformation additional_cell_information = 16; } |
message Gnb { repeated ServedNRCell served_nr_cells = 1; repeated RanFunction ran_functions = 2; } message ServedNRCell { ServedNRCellInformation served_nr_cell_information = 1; repeated NrNeighbourInformation nr_neighbour_infos = 2; } message ServedNRCellInformation { ... AdditionalCellInformation additional_cell_information = 16; } |
Add a new configuration key to the yaml file.
Recently we've added:
stateChangeMessageChannel: RAN_CONNECTION_STATUS_CHANGE
Now we shall add a new channel for RAN changes:
ranManipulationMessageChannel: RAN_MANIPULATION
This key, as others, should be read to the app's configuration which is injected to various flows.
This key will be used by RnibWriter for adding/updating/deleting eNBs and updating gNBs. RnibWriter will trigger Sdl.SetAndPublish method, sending the RAN_MANIPULATION channel, and one of the following events:
|
SaveNodeb(nbIdentity *entities.NbIdentity, nodebInfo *entities.NodebInfo) error |
→ For Gnb type, we execute sdl's Set method.
→ For Enb type, we execute sdl's SetAndPublish method instead, sending RAN_MANIPULATION channel and <RAN_NAME>_ADDED event.
RemoveServedCells(inventoryName string, servedCells []*entities.ServedCellInfo) error UpdateEnb(nodebInfo *entities.NodebInfo, servedCells []*entities.ServedCellInfo) error DeleteEnb(nodebInfo *entities.NodebInfo) error |
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):
|
|
POST /v1/nodeb/enb
{ "ranName": "", "globalNbId": { plmnId: "", nbId: "" }, "ip": "", "port": 1234, "enb": { "enbType": "", "servedCells": [{}], "guGroupIds": [""] } } |
AddEnbRequestHandler
type AddEnbRequestHandler struct { logger *logger.Logger rnibDataService services.RNibDataService } |
Sequence Diagram
|
PUT /v1/nodeb/enb/<RAN_NAME> | PUT /v1/nodeb/gnb/<RAN_NAME> | ||
|
|
UpdateNodebHandler
Sequence Diagram
|
DELETE /v1/nodeb/enb/<RAN_NAME>
type DeleteEnbRequestHandler struct { logger *logger.Logger rnibDataService services.RNibDataService } |
Sequence Diagram