Requirements

After US 571 creates the RAN

Rest API

• Insert eNB – take care that new Field in the NodeB – Setup from NW = False.
• Insert eNB – reject if antenna-type = ng-enB-macro, ng-enB-shortmacro , ng-enB-longmacro
• Delete eNB – if Setup from NW =True – Reject with 400 and 402
• Update eNB - if Setup from NW = True – ignore the eNB type from REST (REST can’t change enb-type that it doesn’t create)
• Update eNB – reject if antenna-type in RNIB = ng-enB-macro, ng-enB-shortmacro , ng-enB-longmacro - Reject with 400 and 402
• Add the new fields GNB-type, Setup from NW – in the Query RNIB and in Get NodeB Response

Acceptance

• See Insert eNB, when create a new RAN, signed as Setup from NW =False
• See Insert eNB, when create a new RAN, can’t create a en-gnb* family.
• See Update eNB, can’t update any one from a en-gnb* family.
• See Update eNB, don’t influence on antenna-type when Setup from NW =True.
• See Delete eNB, is rejected when Setup from NW =True (400 with 402) 

Test Plan

Note: Changes to RAN name key are not taken into consideration in this test plan- only setupFromNW & antennaType