Date:  


Participants

Swaminathan Seetharaman

@Arda Akman (O-RAN)

Ahila P

Andrei Kojukhov

Borislav Glozman

@Burcu Yargicoglu-Sahin (O-RAN)

@Emmanuel Sarris

Fei Zhang

Hanif Kukkalli

Kamel Idir

Naohito Taga

@Shinobu Nanba

Timo Perala


Agenda

  1. Overview of Slice Assurance use cases/work ongoing in O-RAN
  2. Proposal for decomposition of Slice Profile by ONAP before sending to Near-RT RICs
  3. AOB

Notes and Actions

  1. Burcu presented the Slice Assurance use case that is work-in-progress within O-RAN. It covered the foll. aspects:
    • RAN Slice SLA assurance related data is provided to the Non-RT RIC including RAN Slice SLA, topology, etc. This is then fetched by the Slice Assurance rApp in the SMO.
    • Relevant PM jobs are then created for collecting the PM data required for the Slice Assurance.
    • The required PM data is then (collected and) provided to the Slice Assurance rApp.
    • Slice Assurance rApp analyzes the data, and based on the insights/outcome of analysis (detection of (impending) SLA violation), triggers a preventive/corrective assurance action.
    • The assurance action is triggered to the Non-RT RIC, which then in turn, informs the RAN NFs. 2 possible scenarios exist for interacting with the RAN NFs, either of them, or both can be used depending on the use case.
      1. Over O1 interface: In this case, the Non-RT RIC may inform the Near-RT RIC of the updates, as well as the CUs/DUs directly also (over O1). This is typically used in case of slow Control Loops, as Non-RT RIC performs all the analysis and determines the exact actions to be carried out; Near-RT RIC has no real role to play in determining preventive/corrective actions.
      2. Over A1 interface: In this case, the Non-RT RIC may inform the Near-RT RIC of Policy creation/update/removal. This is typically used in case of faster Control Loops, as Non-RT RIC determines the actions to be carried out at a high level, and Near-RT RIC performs further analysis/optimization/... to determine fine-grained updates. It then initiates appropriate actions to RAN NFs over E2 interface.

Either or both options can be used, thereby giving greater flexibility in the realization of Assurance use cases involving RAN NFs.

    • In case A1 interface was used to initiate the actions in RAN, a Policy feedback is sent from Near-RT RIC to Slice Assurance rApp via Non-RT RIC. 

2. The mechanism of sending useful info in the feedback in case of SON use case was discussed.

3. It was agreed that for the ONAP E2E Network Slicing use case in Honolulu for the Intelligent Slicing scenario, O1 interface shall be used for sending the config updates (at cell level per S-NSSAI) from ONAP to Near-RT RIC. For the Intelligent Slicing scenario, O1 interface shall be used for sending the config updates (at Near-RT RIC level per S-NSSAI) from ONAP to Near-RT RIC.

4. A draft proposal for decomposition of the Slice Profile and sending the relevant info to Near-RT RIC is being prepared in E2E Network Slicing (Section 2). This will be sent for review to O-RAN folks.

5. There will be no more meetings in Dec 2020, and the next meeting will be on Jan 7, 2021.

Recording

The meeting was not recorded.

  • No labels