Epic
Highest General Requirements
Needed in case we have non-E2 termination for such RAN that does not use E2 at all.
This is a different item than RIC-176 (which was for gNBs that were added via E2).
This is needed in context of xApps that touch eNBs: so far I have seen this information to be added via REST. MOre to be discussed with Matti.
- Identity of the eNB and their cells (R-NIB)
- Cell neighbor information might be useful
Implementation Requirements
- Please look on the R5 AID - https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20874584
- The RAN will be inserted with Disconnected state. They might changed later to Shut Down by Shut Down command from Dashboard
- E2M will not update the Routing Manager with this RAN, since no E2T manages its connection
| Flow | RnibWriter Method | Node Type | New / Existing | Sdl Channel | Sdl Event | Notes |
| E2 SETUP | SaveNodeb (NO PUBLISH) + UpdateNodebOnConnectionStatusInversion (PUBLISH) | GNB/ENB | NEW | RAN_CONNECTION_STATUS_CHANGE | <RAN_NAME>_CONNECTED | Since SaveNodeb is called for eNB in E2 Setup as well, SaveNodeb WON’T publish anymore. The publish is called from UpdateNodebOnConnectionStatusInversion only (this already happens) |
| E2 SETUP RAN’s ConnectionStatus = !CONNECTED |
UpdateNodebInfo (NO PUBLISH) + UpdateNodebInfoOnConnectionStatusInversion (PUBLISH) | GNB/ENB | EXISTING | RAN_CONNECTION_STATUS_CHANGE | <RAN_NAME>_CONNECTED | |
| E2 SETUP RAN’s ConnectionStatus = CONNECTED No change in RAN’s functions |
UpdateNodebInfo (NO PUBLISH) | GNB/ENB | EXISTING | - | - | |
| E2 SETUP RAN’s ConnectionStatus = CONNECTED Update in RAN’s functions |
UpdateNodebInfoAndPublish (PUBLISH) | GNB/ENB | EXISTING | RAN_MANIPULATION | <RAN_NAME>_UPDATED | Until now we called for UpdateNodebInfo without PUBLISH. Now we’ll need to publish as well. |
| Add eNB REST API | AddEnb (PUBLISH) | ENB | NEW | RAN_MANIPULATION | <RAN_NAME>_ADDED | Until now, SaveNodeb published only for eNB RAN_MANIPULATION, ADDED. From now on, since SaveNodeb is called for eNB in E2 Setup as well, SaveNodeb WON’T publish anymore. We’ll call AddEnb instead which WILL publish. |
| Update eNB REST API | UpdateEnb (PUBLISH) | ENB | EXISTING | RAN_MANIPULATION | <RAN_NAME>_UPDATED | No changes here |
| Update gNB CELLS REST API | UpdateGnbCells (PUBLISH) | GNB | EXISTING | RAN_MANIPULATION | <RAN_NAME>_UPDATED | As part of |
| Delete eNB REST API | RemoveEnb (PUBLISH) | ENB | EXISTING | RAN_MANIPULATION | <RAN_NAME>_DELETED | No changes here |