Date:
Participants
Agenda
- Discuss the role of Near RT RIC in particular for Network Slicing (instantiation, as well as closed-loop control)
- Discuss the updated scenario for Preparation Phase.
- Agree on 3GPP release, deployment scenario, etc. for ONAP Guilin release scope.
- Discuss the config and KPI aspects
Open Actions from previous meetings
S.No. | Action | Responsible(s) | Status |
|---|---|---|---|
| 20200310_3 | Prepare the list of assumptions for the first steps | Arda & Swami | Ongoing |
| 20200310_4 | Involve WG6 for the orchestration workflows, which would have to be prepared for ONAP <-> O-RAN interaction | Arda | Ongoing |
| 20200310_6 | Explain the proposed ONAP architecture with component mappings to CSMF, NSMF, NSSMF, and different deployment configurations | Swami | Ongoing, should be closed in the next call |
| 0200507_1 | Update the slides based on comments and inputs received, as well as elaborate some of the steps in more detail | Swami, Shankar & Arda | Ongoing, apart from Preparation, other procedures to be also elaborated |
| 20200507_2 | Finalize which deployment scenario (Scenario B or D) shall be taken as a first step (for ONAP Guilin release) | Swami & Shankar | Closed, for now, it is agreed to go ahead with Scenario B |
| 20200507_3 | Check and confirm the 3GPP spec version number to be used | Swami | Closed, 3GPP Rel. 16 shall be used |
| 20200507_4 | Explain Near RT-RIC's role in Network Slicing | Arda | Closed, Arda presented it in today's call |
Notes and Actions
- 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.
- Possible approaches for the cases where the O-RAN interface specs are not yet available were discussed.
- 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.
- The 3GPP specification versions (Rel. 16), and the deployment scenario of O-RAN (Scenario B) were agreed.
- 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.
- The next meeting shall first focus on the items for Guilin release - config items, interactions, etc.
- ORAN team shall also share the enhancements to TS 28.531 procedures related to slice subnet management.
S.No. | Action | Responsible(s) |
|---|---|---|
| 20200521_1 | Update the slides to include details of the config items, info models and interactions between ONAP and ORAN for further discussion | Swami, Shankar & Arda |
| 20200521_2 | Share details of the enhancements to the 3GPP TS 28.531 procedures | Arda |
| 20200521_3 | Discuss 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 & Arda |
| 20200507_4 | (Post meeting action) Discuss details of config, PM and Closed Loop Control of Fronthaul and Midhaul | Shankar, Arda & Swami |