Versions Compared

Old Version 27

changes.mady.by.user user-165cf

Saved on

compared with

New Version 28

changes.mady.by.user Martin Skorupski

Saved on

Key

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

...

Operation and Maintenance (OAM)

Primary Goals:

  • updates of OAM related interface definitions based on
    • YANG from WG4 - O-RAN Management Plane Specification - YANG Models 5.0 - November 2020 (with dependencies to IETF data models)
      • status: done
    • YANG from WG5 - O-RAN O1 Interface for O-DU 1.0 - YANG Models - November 2020 (with dependencies to 3GPP data models) 
      • status: after feedback of WG5, related merge request was abandoned - instead a pipline will be establish with O-RAN bitbuckets.  
    • YANG from WG1 - O1-interface (November 2020 train)
      • status: not approved by O-RAN
    • VES from ONAP DCAE - VES 7.2
      • status: ongoing
    • Notification syntax from 3GPP TS 28.532 V16.6.0
  • support D-Release use case "O-RU recovery"
    • see Feature Scope below
  • handover SMO artifacts to new SMO project

D Feature Scope: 

  • Update to OpenDaylight Silicon
  • Support of Callhome via TLS
  • CallHome to VES:pnfRegistration 
  • o-ran-fm.yang/alarm-notif to VES:fault

PTL: Martin Skorupski

Status:

Jira: Count of Epics ( 15 issues ), User Stories, Tasks, and Issues:  166 issues

Release notes:

Demo of OAM use cases


O-RAN Central Unit (OCU)

Primary Goals: 
  • Source code includes RRC, Ng, E1, F1. Platform and OM are provided in  dependent libraries.
  • O-CU-CP is integrated with O-CU-UP, O-CU functions should be complete.

Cherry Feature Scope: 

PTL:

Jira: Count of Epics, User Stories, Tasks, and Issues:

OCU-1 - O-CU F1 interface for Release B TO DO   F1

OCU-2 - O-CU SDAP TO DO  SDAP

OCU-3 - O-CU PDCP TO DO  PDCP

OCU-4 - O-CU RRC TO DO  RRC

OCU-5 - O-CU Ng TO DO  Ng

OCU-6 - O-CU E1 TO DO  E1


...