Jämförda versioner

Nyckel

  • Dessa rader lades till.
  • Denna rad togs bort.
  • Formateringen ändrades.

The OAM project focus on the following topics:

Provide complete implementation for OAM functions (FCAPS).

Specifications

The following Specifications needs to be considered for software updates:


O-RAN Operations and Maintenance Architecture 34.0 - April November 2020
O-RAN.WG1.OAM-Architecture-v03v04.00 00

O-RAN Operations and Maintenance Interface Version 34.0 - April November 2020
O-RAN.WG1.O1-Interface.0-v03v04.00

O-RAN Use Cases Detailed Specification 3Specification 4.0 - July November 2020
O-RAN.WG1.Use-Cases-Detailed-Specification-v03v04.00 00

O-RAN Management Plane Specification - YANG Models 45.0 - July November 2020
O-RAN.WG4.MP-YANGs-v04-v05.00

O-RAN O1 Interface for O-DU 1.0 - YANG Models - November 2020
O-RAN.WG5.MP.1-v01.00

VES JSON-Schemas

  • ONAP VES 7,2.1
  • 3GPP TS 28.532 V16.46.0
    • - A.1.2   JSON schema of ‘prov3gppFields’ for integration Annex B (Informative):
      Guidelines for the integration of 3GPP MnS notifications with ONAP VES
    • A.1.1 OpenAPI document "provMnS.yaml" (CM-Notify)  - (fallback polling)
    • A.2.1 OpenAPI document "faultMnS.yaml" (FM) - fallback: domain fault
    • A.4.2 OpenAPI document "perfMnS.yaml" (PM) - fallback domain perf3gpp)
    • A.5.1 OpenAPI document "heartbeatNtf.yaml - fallback domain heartbeat2   JSON schema of ‘fault3gppFields’ for integration with ONAP VES- A.5.2   Heartbeat for integration with ONAP VES

Yang Modules

New OAM related yang modules are available by 3GPP and O-RAN WG4 OpenFronthaul v4.0

  • 3GPP TS 28.541 v16.5.0- E.5 Modules
  • 3GPP TS 28.623 V16.4.0- D.2 Modules

    available gerrit scp/oam/modeling/data-model/yang/published/o-ran and by 3GPP. 


    Info

    For O-RAN Members only :/ - please follow the DM discussions:


    Function

    Source of Data model O-RAN-SC

    Status: 2020-10-07

    Fault3GPP: _3gpp-common-fm
    (Fallback from Bronze RFC8632: ietf-alarms)
    Configuration(see next lines)
    • interfaces and/or termination points

    O-RAN-FH: RFC8343: ietf-interfaces
    3GPP: 

    • synchronization

    (see next lines)

    -- Network Time Protocol

    RFC7317: ietf-system,yang

    -- Precision Time Protocol

    RFC8575: ietf-ptp,yang
    (check if new IEEE standard was adopted)
    • DCN
      • OAM IF

    • Ehternet OAM
    • Loopback config 
    • Link supervision
    • others
    to be updated based on SDO progress
    Accountingnot scope of O-RAN and O-RAN-SC - listed just for completeness of FCAPS
    Performance3GPP-xml, file, VES

    Security

    (see next lines)
    • Protocol TLS (for Rest, RestConf and NetConf)
    RFC8446: Transport Layer Security
    • User Management

    RFC7317: ietf-system,yang

    Open: o-ran-user-management

    Inventory (hardware)

    RFC8348: ietf-hardware,yang and iana-hardware.yang
    and of cause o-ran-hardware@2019-07-03.yang for the O-RAN identities.

    Open: only for O-RU and O-DU; O-DU anyhow optional

    Software Management

    Management interfaces:

    Use case:

    Start with and xRan-fronthaul radio unit and perform and upgrade to an o-ru with the OpenFronthaul M-plane and upgrade further to an O-RU with an O-RAN/3GPP common O1 management interface.

    Backup and restoreOpenROADM manifest file
    xApp onboarding (from O1 point of view)under development by WG2 and Near-RT-RIC project
    Subscription for VES


    Non-functional

    All this updates happens in ONAP CCSDK/SDNC and ONAP OOM project.

    • Switch to OpenDay version Aluminium
    • Update of JAVA artifacts addressing security issues
    • Logging of NetConf Call Home (WG4 OpenFronthaul, WG9 Transport)
    • https only support on all REST/RESTCONF interfaces 
      • O1-controller northbound
      • DMaaP
      • VES-Collector
    • full IPv6 support and integration tests on all SMO interfaces.