Date:  


Participants

Swaminathan Seetharaman

@Arda Akman (O-RAN)

Ahila P

Andrei Kojukhov

Borislav Glozman

@Burcu Yargicoglu-Sahin (O-RAN)

Fei Zhang

Kamel Idir

Timo Perala

Agenda

  1. Conclusion on A1 policy spec to be used
  2. RRM Policy determination for GNBCUUPFunction
  3. Status of ongoing work in O-RAN w.r.to Network Slicing (including modeling, role of Near-RT RIC), and any relevant use cases involving AI/ML and Network Slicing that we could consider.
  4. O2 specs availability timeline
  5. AOB

Notes and Actions

  1. It was agreed that ONAP will use an A1 policy based on the currently available spec from O-RAN with suitable updates to accommodate the Closed Loop scenario being implemented for E2E Network Slicing. Subsequently, when the new A1 spec becomes available, ONAP shall align to it. This is to enable progress in ONAP w.r.to completing the Closed Loop scenario flows.
  2. RRM Policy proposal for GNBCUUPFunction is a RAN-NSSMF internal aspect, so O-RAN does not have any official stand on it. So ONAP shall proceed with the current proposal, and will refine it subsequently based on feedback from the community.
  3. Arda informed that the objective of O-RAN is to complete the minimum specification work required to realize Network Slicing by July 2021. So, it will be available for reference and alignment towards the end of the 3rd quarter of 2021. This includes specs across all the relevant O-RAN WGs. Based on this, the foll. approach for ONAP was agreed:
    1. For the O1 interface to CUs and DUs, since the current models are based on 3GPP NRM, we will continue to use it.
    2. For the O1 interface to Near-RT RIC, we will share the current models which have been hand-crafted and seek offline feedback to ensure we are proceeding in the right direction
    3. The actual complete alignment with O-RAN for (a) and (b) will happen based on availability of O-RAN specs.
    4. For O2, we can wait for some time, as we have to first complete the service design of RAN and interactions with Transport for FH and MH. So we will initiate the discussions together with ONAP and O-RAN (including Transport folks) to get inputs and feedback.
    5. For A1, see (1).
  4. It was agreed to cancel next week's call (Feb 18), and have the call on Feb 25 together with the Transport folks.

Recording

RAN_Slicing_ORAN_ONAP_2021_02_11.mp4

  • No labels