Requirements

We want to enlarge the RAN in the Response of Get All Nodeb States

1. The End Point URL is changed - GET http://localhost:3800/v1/nodeb/states
2. We will build one Handler to update state
3. We will handle one handler (Ran List Handler) which is the only one who updates it.

1. The Flow of the calls that also update Redis:

• • Lock (Between mutual call to this Handler)
  • Read RAN List to memory
  • Update the memory
  • Update the Redis
  • Unlock 
    Since we don't support 2 E2Ms running in parallel, no need to Lock the DB

1. Note that the following should call it, and only once  ( ! ) :

• Setup From RAN
• Lost connection
• Red Button
• Insert eNB
• Delete eNB
• E2T Initialize
• Keep Alive 

In other words - everyone who change RAN Status OR Add / Delete RAN !

1. The REST API Get All Nodeb States will read from handler, just from memory.
2. The Query RNIB - no change - continue to read directly from RNIB.

Acceptance

• Assuming there are already RAN 1 & RAN 2, with their Node (Name & ID) and Status.
• See in case new Setup from RAN 3 - the stat is added
• See in case Lost Connection from RAN 3 - the stat is updated
• See in case another Setup from RAN 3 - the stat is updated
• See in case KA "kills" E2 Instance - the stat is updated
• See in case connected and E2 Instance initialized - the stat is updated
• See in case Red Button, all 3 RANs are shutting down, assuming 2 got Lost connection - these 2 moved to Shutdown. At the end of the timer - also the 3rd is Shut down.
• Insert new eNB 
• Delete existing eNB
  *

Test plan