Versions Compared

Old Version 2

changes.mady.by.user Swaminathan Seetharaman

Saved on

compared with

New Version Current

changes.mady.by.user Swaminathan Seetharaman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date:  

Participants

Agenda

  1. Discuss the role of Near RT RIC in particular for Network Slicing (instantiation, as well as closed-loop control)
  2. Discuss the updated scenario for Preparation Phase.
  3. Agree on 3GPP release, deployment scenario, etc. for ONAP Guilin release scope.
  4. Discuss the config and KPI aspects

Open Actions from previous meetings

...

S.No.

...

Action

...

Responsible(s)

...

Status

...

Swaminathan Seetharaman

@Arda Akman (O-RAN)

@Burcu Yargicoglu Sahin (O-RAN)

Shankaranarayanan Puzhavakath Narayanan

Borislav Glozman

Andrei Kojukhov

@Shinobu Nanba

Ahila P

Erol Özcan

Fei Zhang

@Avi Chapnik

@Nebi Volkan Unlenen

Agenda

  1. Discuss on the scope of ONAP Guilin release

           - RAN slice sub-net allocation

           - Info models and config items

           - Slice specific configurations

           - RAN and transport interaction (FH and MH)

        2. Other topics - e.g., Preparation phase for Guilin release

Open Actions from previous meetings

Notes and Actions

  1. Arda presented an overview of the role of Near-RT RIC in the context of Network Slicing, covering its interaction with Non-RT RIC as well as other O-RAN components. He also described the various O-RAN interfaces and their use in the context of Network Slicing.
  2. Possible approaches for the cases where the O-RAN interface specs are not yet available were discussed.
  3. Arda briefly presented the Slice SLA assurance use case in ORAN, and it was agreed to collaborate between ONAP and ORAN folks where possible for this use case, as there seems to considerable overlap in the focus.
  4. The 3GPP specification versions (Rel. 16), and the deployment scenario of O-RAN (Scenario B) were agreed.
  5. The NRM in 3GPP TS 28.541 shall be used as of now, when O-RAN NRM is available, it shall be assessed if it shall be used for ONAP Guilin release or from the next release.
  6. The next meeting shall first focus on the items for Guilin release - config items, interactions, etc.
  7. ORAN team shall also share the enhancements to TS 28.531 procedures related to slice subnet management.

S.No.

Action

Responsible(s)

20200521_1Update the slides to include details of the config items, info models and interactions between ONAP and ORAN for further discussionSwami, Shankar & Arda20200521_2Share details of the enhancements to the 3GPP TS 28.531 proceduresArda20200521_3Discuss and prepare a proposal for Guilin release reg. the O1 and A1 interface aspects from ONAP to Near-RT RIC (Slice config, policies, ML models)Swami, Shankar & Arda20200507_4(Post meeting action) Discuss details of config, PM and Closed Loop Control of Fronthaul and MidhaulShankar, Arda & Swami

Status





























Notes and Actions

S.No.

Action

Responsible(s)













Slides

ONAP_RAN_Slicing_20200611.pptx


Recording

View file
nameRAN_Slicing_ORAN_ONAP_2020_06_11.mp4
height150