Versions Compared

Old Version 4

changes.mady.by.user Michela Bevilacqua

Saved on

compared with

New Version Current

changes.mady.by.user John Keeney

Saved on

Key

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

Use Case Name

A1 Adapter and Policy Management Extension (R8 Honolulu)

 John Keeney Michela Bevilacqua

Use Case Overview & Description

This requirement enhances the A1 interface capabilities provided in Rel 6 as part of  5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management.   O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. This requirement enhances the support for Managing and Mediating O-RAN A1 Policies in ONAP.  This extends work contributed in Rel 6 - Frankfurt (REQ-38) and Rel 7 - Guilin (REQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added.

Planned enhancements for Rel 8 include: support of new A1 interface version in alignment to O-RAN alliance and , common logging/audit. improved CSIT and OOM alignment, easier configuration, an improved NBI, and improved security cert management.

Use Case Key Information

Architecture infoInformation on the Architecture sub-committee presentation
TOPICDESCRIPTIONWIKI PAGEInformation
Requirements ProposalThis is a link to the requirements proposal made on the Requirements Sub-committee S/C Proposal: A1 Adapter and Policy Management Extension (ORAN/ONAP/3GPP Harmonization)
Project WIKI pageO-RAN A1 Policies in ONAP & This Page
Prior Project "Base" WikiLink to the "base" wiki for the Use Case, or work from a prior release.ONAP/3GPP & ORAN Alignment: A1 Adapter extensions (Guilin)
Meetings Register & Recordings

ONAP/O-RAN-SC/SMO Meetings

Requirements Ticket

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-457

Requirements Jira (REQ-###) TicketLink to the REQ Jira ticket for this use case

Key Use Case Leads & Contacts

USE CASE LEAD:

  @xyz

  John Keeney

USE KEY CONTACTS: Michela Bevilacqua

CCSDK Requirement/Epic

JIRA Ticket for Epic for A1 Policy Management in Honolulu

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCCSDK-2991

ONAP Arch Committee Review

JIRA Ticket for Review in ArchCom

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyONAPARC-642

2020-12-01 ONAP Architecture Subcommittee Meeting - Approved

Recording:

Meetings Register & RecordingsLink to Use Case Team meetings.

BUSINESS DRIVER

...

View file
nameA1PolicyFunctions_Honolulu_Archcom_20201201.mp4
height150

Slides: 

View file
name20201201 - ORAN-A1Extensions - ONAP ArchCom.pdf
height150

Function/Integration
Test environment
Demo of OSC NONRTRIC & ONAP A1 functions at LFN Developer & Testing Forum - Feb 2021
Slides & Video: 2021-02-03 - ONAP: Demo: O-RAN A1 Policy & Non-RealTime-RIC automated test/demo environment  
Integration Tests

JIRA Ticket for Epic for Integration Tests

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-626



BUSINESS DRIVER


Key Contacts : John Keeney, Michela Bevilacqua

Executive Summary: This requirement enhances the A1 interface capabilities provided in Rel 6 as part of  5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management.  

O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. This requirement enhances the support for Managing and Mediating O-RAN A1 Policies in ONAP.  This extends work contributed in Rel 6 - Frankfurt (REQ-38) and Rel 7 - Guilin (REQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added.

Planned enhancements for Rel 8 include: support of new A1 interface version in alignment to O-RAN alliance and , common logging/audit. improved CSIT and OOM alignment, easier configuration, an improved NBI, and improved security cert management.

Business Impact: Continuing the convergency convergence between ONAP and ORAN for A1 Policy interface to used by all service providers and avoid duplicate development efforts.

Business Markets: Enhanced A1 Policy capabilities, once developed, will be useable usable by any service provider deploying and using ONAP.

...

Organization Mgmt, Sales Strategies: There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.


Development Status

PROJECTPTLUser Story / EpicRequirement
A&AI

William Reehil

N/A


AAF

Jonathan Gathman

N/A
APPC

Takamune Cho

N/A


CLAMP

Gervais-Martial Ngueko

N/A
CC-SDK

Dan Timoney

Extend existing A1 Adapter and A1 Policy Management functionality in CCSDK

CCSDK-2991
DCAE

Vijay Venkatesh Kumar

N/A
DMaaP
Mandar Sawant
N/A
External API

Adrian OSullivan

N/A
HOLMES
Guangrong Fu
N/A
MODELING

Hui Deng

N/A

Multi-VIM /

Cloud

Bin Yang

N/A
OOF

krishna moorthy

N/A
OOM

Sylvain Desbureaux

N/A
POLICY

Jim Hahn

N/A
PORTAL

Sunder Tattavarada

N/A
SDN-C
Dan Timoney

Extend existing A1 Adapter and A1 Policy Management functionality in SDNC deployments


SDC

Christophe Closset

N/A
SO

Seshu Kumar Mudiganti

N/A
VID

Ikram Ikramullah

N/A
VF-C

Yuanhong Deng

N/A
VNFRQTS
Steven Wright
N/A
VNF-SDK
Weitao Gao
N/A
CDS

Yuriy Malakov

N/A

List of PTLs: Approved Projects

...

Use cases define how different users interact with a system under design.  Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).Use Case Diagram Example.pngImage Removed. 

Image Added


Enhancements for Honolulu Release

  • Add support for O-RAN Alliance A1-AP v2.1 specification (A1 Policy only)
  • Improve alignment with OOM deployment & configuration options
  • Improve alignment with CSIT way of working for function tests
  • New REST interface for configuration
  • New A1 Policy Management NBI (REST & DMaaP)
  • Improved security cert management
  • Stretch: Investigate if A1 Policy manipulation can be incorporated into other use cases (e.g. Slicing, OOF) - TBC

Synchronize A1 Policy Information in RAN

Image Added


A1 Policy Type / Instance Operations

Image Added

A1 Policy Instance Status Operations

Image Added

Other Impacts

Affected ONAP Functions:

  • SDNC / CCSDK only

Integration of bordering ONAP components:

  • TBC

Interfaces:

  • Northbound Interface
    • Add/Change CCSDK A1 Policy Management Service NBI for A1 Policy Management (REST & DMaaP)
    • The new version of the PMS REST API complies with the ONAP REST API and Zalando style guidelines and fixes some naming inconsistencies.
      • REST (New version)
      • DMaaP (New version)
      • Ref: CCSDK-3077
  • Configuration
    • File based, supports dynamic refresh - including K8s ConfigMap (existing)
    • CBS/Consul (existing)
    • REST (New)
  • Southbound Interfaces – See earlier section
    • OSC A1 v2.1 (Existing)
    • O-RAN A1 v1.1 (Existing)
    • O-RAN A1 v2.1 (New)

Usage outside ONAP:

  • Used in O-RAN-SC NONRTRIC Project (Downstream)
  • Southbound Interface: O-RAN A1 Interface + Information Model is specified and maintained by O-RAN Alliance

Modelling Impacts:

  • TBC

Other:

  • Update Documentation with A1 interface aspects
  • Update Integration & Existing Test requirements

Use Case Functional Definitions

The expected results of the execution of the Use Case

Includes description of Information ProducedDescription of any exceptions or special process that could occur during Use Case

Use Case Title

Title of the Use Case

A1 Adapter and Policy Management Extension

Actors (and System Components)

The list of Actors and System Components that participate in the Use Case

Description

Short overview of the Use Case

Points of Contact

Authors and maintainers of the Use Case.

Use Case Lead, Key Use Case members and code contributors.

Preconditions

A list of conditions that are assumed to be true before the Use Case is invoked

Includes description of Information Consumed

SDNC / CCSDK - A1 Adapter & A1 Policy Management Service

Description

O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. This requirement enhances the support for Managing and Mediating O-RAN A1 Policies in ONAP.  This extends work contributed in Rel 6 - Frankfurt (REQ-38) and Rel 7 - Guilin (REQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added. Planned enhancements for Rel 8 include: support of new A1 interface version in alignment to O-RAN alliance, common logging/audit. improved CSIT and OOM alignment, easier configuration, an improved NBI, and improved security cert management.

Points of Contact


John Keeney Michela Bevilacqua


Preconditions

N/A

Triggers / Begins when

N/A

Triggers / Begins when

Describes the trigger for beginning the Use Case

Steps / Flows (success)

Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes)

Interaction diagrams may be included or referenced


Post-conditions


Alternate / Exception Paths


Related Use Cases

List of the Use Cases referenced by this Use Case TBC

Assumptions

Describes any assumptions that are made for this use caseNone

Tools / References / Artifacts

List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability.

List of any associated diagrams or modelling artifacts associated with the Use Case

TESTING

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links
See additional information on this page

TESTING

  • Test use-cases:

    • Synchronize A1 Policy Information in RAN
    • A1 Policy Type / Instance Operations
    • A1 Policy Instance Status Operations

Current Status

  • None yet

End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 

Gliffy Diagram
macroIdc633e195-a625-4afd-a014-dfd1eb1a365a
nameUse Case Flow
pagePin1

Test Cases and Status

...

NOT YET TESTED

...

COMPLETE

  • Currently being defined

Test Cases and Status

  • Currently being defined

...