Requirements

Setup Request from RAN

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

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.

Given	When	Then
eNB {ranId: xyz, ranName: RAN1} added via AddEnb HTTP	eNB Setup Request {ranId: xyz, ranName: RAN2}	RanName is updated in redis: setupFromNetwork =true 1. [RanId]nodeb - ranName is updated 2. [oldRanName]nodeb - deleted 3. [newRanName]nodeb - ranName is updated 4. cellPciKeys with old ranName - deleted 5. cellPciKeys with new ranName - created 6. nbIdentity with old ranName - deleted 7. nbIdentity with new ranName - created

clones

RIC-571 Setup from RAN: 9 Antenna Type - 2 GNBs & 7 ENBs

1.	Design (sequence diagram)	To Do	Unassigned
2.	rnibWriter - UpdateNodebRanName + cellPciKey + Unit tests	To Do	Unassigned
3.	RanListManager - UpdateRanName (memory, db: rnibWriter) + Unit tests	To Do	Unassigned
4.	rnib GetNodebInfoById	To Do	Unassigned

No reviews matched the request. Check your Options in the drop-down menu of this sections header.