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
  • 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

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