Versions Compared

Key

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

...

@Avi Chapnik

krishna moorthy

Agenda

Open Actions from Previous

...

Meetings

S.No.

Action

Responsible(s)

Status

20200310_3Prepare the list of assumptions for the first stepsArda & SwamiOngoing
20200310_4Involve WG6 for the orchestration workflows, which would have to be prepared for ONAP <-> O-RAN interactionArdaOngoing, priority lowered
20200310_6Explain the proposed ONAP architecture with component mappings to CSMF, NSMF, NSSMF, and different deployment configurations (during next call)SwamiClosed, explained during the call on Apr 2
20200319_1

Step 41.b2 in "Procedure of Network Slice Subnet Instance Allocation" of 3GPP TS 28.531 to be elaborated. Consider instantiation vs configuration (considering preparation phase also).

Arda & Swami

Ongoing, for Guilin release, RAN elements are assumed to be already available, mainly slice related configuration to be done
20200319_2

Elaborate details of Preparation phase

Swami & Shankar

Closed, high-level view shared, details to be worked out (see follow-on action)
20200319_3

Feasibility check – check if ETSI provides any inputs on resource reservation aspects

Andrei

Open
20200319_4

Work further on ‘initial’ RAN configuration, and slice-specific configuration

Swami

Closed, high-level view shared, details to be worked out (see follow-on action)
20200319_5

Check further reg. the API specifications (3GPP)

Swami

Closed, 3GPP provides only functional view, and not as elaborate, e.g., as TMF (of course, one can infer the key API contents based on 3GPP NRM)

Notes and Actions

  1. An overview of E2E Network Slicing use case scope that is being implemented in Frankfurt release was shared.
  2. The high-level scope of Guilin release, i.e., selection of appropriate RAN NSSI - including creation of a new RAN NSSI involving only configuration of slice-specific aspects (assuming the xNFs are already available with basic configuration done), as well as reuse of an existing RAN NSSI was discussed.
  3. The preparation phase and initial configuration was discussed in brief, and needs to be elaborated with details of the steps, info models and interface impacts.
  4. The interaction between ONAP and near-real time RIC as well as the FM/PM data reported from RAN related to network slicing should be elaborated (aligning to 3GPP).
  5. The interaction of RAN and Transport Slicing for the Front haul and Mid haul, and solution approaches were discussed. It was agreed that Front haul and Mid haul shall be considered as part of RAN sub-net, and the RAN NSSMF shall interact with the Transport NSSMF for appropriate NSSI allocation within Front haul and Mid haul.

...


Recording

View file
nameRAN_Slicing_ORAN_ONAP_2020_04_02.mp4
height150