Uploaded image for project: 'Near Realtime RAN Intelligent Controller'
  1. Near Realtime RAN Intelligent Controller
  2. RIC-587

Setup from RAN: SDL Notification Manipulation (Updated) if already in Connected

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Cherry-R5
    • None
    • e2mgr
    • None

      Requirements

      Top be compliant with the table in https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20874584#E2ManagerR5InterfaceDesign(Draft)-SDLNotification -

      In case Setup from RAN (It will be mostly gNB since eNB has no Functions), and RAN is already Connected, and we plan to Insert the Functions in RNIB, SDL Notification (Channel = Manipulation, Updated)

       

      Refer also permutations table: https://jira.o-ran-sc.org/browse/RIC-414

      Acceptance

      • Setup from RAN with Functions  in payload and status = Connected: See SDL Notification (Channel = Manipulation, Updated) 
      • Setup from RAN without Functions  in payload (Probably eNB) and status = Connected: If we got No functions but in the RNIB there is Functions - See SDL Notification (Channel = Manipulation, Updated). But  if in the RNIB there is no functions - See NO SDL Notification at all.
      • Setup from RAN with or without Functions  in payload and status = Disconnected: See SDL Notification (Channel = Status Changed, Connected) 

       Test Plan

      Given When Then
      eNB added via AddEnb HTTP
      ConnectionStatus=DISCONNECTED
      E2 Setup Request triggered for eNB RAN 
      • <RAN_NAME>_CONNECTED event is PUBLISHED on RAN_CONNECTION_STATUS_CHANGE channel
      • <RAN_NAME>_UPDATED event is NOT published on RAN_MANIPULATION channel
      An existing eNB
      ConnectionStatus=CONNECTED;
      RM Succeeds
      E2 Setup Request triggered for eNB RAN
      • No event is published
      An existing gNB; ConnectionStatus=CONNECTED; 
      RM Succeeds
      E2 Setup Request triggered for gNB RAN with functions
      • <RAN_NAME>_UPDATED event is PUBLISHED on RAN_MANIPULATION channel
      • <RAN_NAME>_CONNECTED event is NOT published on RAN_CONNECTION_STATUS_CHANGE channel
      An existing gNB; ConnectionStatus=CONNECTED; 
      RM Fails
      E2 Setup Request triggered for gNB RAN with functions
      • <RAN_NAME>_DISCONNECTED event is PUBLISHED on RAN_CONNECTION_STATUS_CHANGE channel
      • <RAN_NAME>_UPDATED event is NOT published on RAN_MANIPULATION channel
      An existing gNB; ConnectionStatus=CONNECTED; E2 Setup Request triggered for gNB RAN without functions
      • No event is published
      gNB exists with ConnectionStatus=DISCONNECTED E2 Setup Request triggered for gNB RAN with functions
      • <RAN_NAME>_CONNECTED event is PUBLISHED on RAN_CONNECTION_STATUS_CHANGE channel
      • <RAN_NAME>_UPDATED event is NOT published on RAN_MANIPULATION channel

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

            Unassigned Unassigned
            avinoambernstein Avinoam Bernstein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 6 hours
                1d 6h