-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
RICP_T1 Sprint C.P3
After long mail with all architects, here is the solution.
Introduction
- E2T sends us RAN Name which it generates by concatenate the following:
- RAN Name = <Antenna-Type>”:“< 3 MCC digits>”
“< 3 MNC digits>”“< Node ID> - Where: Antenna-Type – one of the following:
- gnb
- en-gnb
- ng-enB-macro
- ng-enB-shortmacro
- ng-enB-longmacro
- enB-macro
- enB-home
- enB-shortmacro
- enB-longmacro
Requirements
Setup Request from RAN
- E2M, when a valid Setup Request is coming, and this is a new RAN
- Today there are 4 ENB-Type (enB-macro, enB-home , enB-shortmacro , enB-longmacro), and there is no FNB-Type. Hila prefers that we will support instead one Antenna-Type with 9 values (gnb, en-gnb, ng-enB-macro, ng-enB-shortmacro , ng-enB-longmacro, enB-macro, enB-home , enB-shortmacro , enB-longmacro)
- (Note – since the REST API can create NodeB (only eNB but let’s be general), it can give different RAN Name to RAN ID – different from the way E2T calculates it. So – To force that at the end the RAN Name that E2T is the one we are saving
- If (RAN ID (from Setup) already exist in RNIB) BUT (RAN Name (from Setup) is different then the one in the RNIB
- Update the RAN Name (from Setup) in the existing RAN Object
- Update the RAN Name (from Setup) that will point on the existing RAN Object
- Null the old RAN Name that will NOT point on the existing RAN Object)
- Change also the the new RAN name in the List
- If the Antenna-Type (The string until the first “:” of the RAN Name) are “gnb” or “en-gnb”
- Sign this RAN as GNB (node Type)
- Sign its Antenna-Type
- Else
- If the Antenna- are ng-enB-macro, ng-enB-shortmacro , ng-enB-longmacro, enB-macro, enB-home , enB-shortmacro , enB-longmacro
- Sign this RAN as ENB (node Type)
- Sign its Antenna-Type
- Else (neither one of the 9) - Error
- If the Antenna- are ng-enB-macro, ng-enB-shortmacro , ng-enB-longmacro, enB-macro, enB-home , enB-shortmacro , enB-longmacro
- Set a new Field in the NodeB – Setup from NW = True. This field means REST API can’t delete it. Although REST API can only Insert eNB, this flag is general for any RAN
- Other fields (Function, Connection Status etc.) - BAU
- If (RAN ID (from Setup) already exist in RNIB) BUT (RAN Name (from Setup) is different then the one in the RNIB
Acceptance
- Simulate Setup Request with gnb, en-gnb, ng-enB-macro & enB-longmacro (4 from all 9). See they are sign with the right Node Type (eNB, gNB), with the right antenna type
- See if Insert eNB (US 584) create eNB with RAN ID N, and Ran Name A, and now there Setup Request from RAN ID N but RAN Name B, RAN Name A disappear from RNIB – it doesn’t point on anything and the RAN name is changed to B. See also in the List.
Test plan
Given | When | Then |
---|---|---|
No such RAN | Setup Request with gnb | gNB Nodeb is saved with gnb antennaType setupFromNetwork =true <RAN_NAME>_CONNECTED event is published on RAN_CONNECTION_STATUS_CHANGE channel |
No such RAN | Setup Request with en-gnb | gNB Nodeb is saved with en-gnb antennaType setupFromNetwork =true <RAN_NAME>_CONNECTED event is published on RAN_CONNECTION_STATUS_CHANGE channel |
No such RAN | Setup Request with ng-enB-macro | eNB Nodeb is saved with ng-enB-macro antennaType setupFromNetwork =true <RAN_NAME>_CONNECTED event is published on RAN_CONNECTION_STATUS_CHANGE channel |
No such RAN | Setup Request with enB-longmacro | eNB Nodeb is saved with enB-longmacro antennaType setupFromNetwork =true <RAN_NAME>_CONNECTED event is published on RAN_CONNECTION_STATUS_CHANGE channel |
eNB added via AddEnb HTTP | eNB Setup Request | eNB Nodeb is saved with correct antennaType setupFromNetwork =true <RAN_NAME>_CONNECTED event is published on RAN_CONNECTION_STATUS_CHANGE channel |
eNB added via Network | eNB Setup Request | eNB Nodeb is saved with correct antennaType setupFromNetwork =true Nothing is published |
- is cloned by
-
RIC-620 Setup eNB from RAN: RanName changed
- Done
1.
|
rNib - Update protos | Done | Unassigned |
|
||||||||
2.
|
rnibWriter - AddEnb (PUBLISHES), SaveNodeb (DOESN'T PUBLISH) | Done | Unassigned |
|
||||||||
3.
|
SetupHandler - Handle new RAN | Done | Unassigned |
|
||||||||
4.
|
SetupHandler - Handle existing ran: flow + unit tests | Done | Unassigned | |||||||||
5.
|
Code review | Done | Unassigned | |||||||||
6.
|
Automation tests for enb setup | Done | Unassigned |
|
||||||||
7.
|
Update Swagger with proto changes | Done | Unassigned |
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
4420,1 | [RIC-571] proto updates: enb_type, gnb_type, setupFromNetwork | master | ric-plt/nodeb-rnib | Status: MERGED | +2 | +1 |
4434,3 | [RIC-571] Setup request of new eNB | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4436,1 | [RIC-571] Fix non-deterministic unit-tests | master | ric-plt/e2mgr | Status: ABANDONED | 0 | -1 |
4441,1 | [RIC-571] Support new eNB setup request + fix non-deterministic unit tests | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4444,1 | [RIC-571] Swagger update + release version updated to 5.2.21 | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4454,1 | [RIC-571] Increment Swagger version to 5.2.21 | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4473,1 | [RIC-571] Add Automation tests + bug fix in Setup of existing eNB flow | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4474,1 | [RIC-571] Increment release-tag to 5.4.2 | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |
4494,1 | [RIC-571] Fix automation tests | master | ric-plt/e2mgr | Status: MERGED | +2 | +1 |