Versions Compared

Old Version 100

changes.mady.by.user Mahesh Jethanandani

Saved on

compared with

New Version Current

changes.mady.by.user user-30c9d

Saved on

Key

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

...

Non-Real-time RIC (A1 Interface) (NONRTRIC)

Primary Goals:
  • The primary goal of Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the near-RT RIC function so that the RAN can optimize, e.g., RRM under certain conditions.
  • It can also perform intelligent radio resource management function in non-real-time interval (i.e., greater than 1 second).
  • Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes.
  • Non-RT-RIC will define and coordinate rApps (Non-RT-RIC applications) to perform Non-RT-RIC tasks.
  • Non-RT-RIC will also host the new R1 interface (between rApps and SMO/NONRTRIC services)

D Feature Scope:

  • NONRTRIC Functions: (NONRTRIC Release D Wiki)
    • Integrated A1 Adapter from ONAP (controller – mediation)
    • Integrated A1 Policy Management Service from ONAP (controller – A1 policies)
    • OSC A1 Enrichment Information Coordinator (controller – A1 EI Job management)
    • OSC Non-RT-RIC Control Panel (GUI – for A1-P & A1-EI Job management)
    • OSC A1 Simulator (a stateful test stub to simulate near-RT-RIC end of A1 interface – A1-P & A1-EI)
    • OSC (initial) APP catalog (for registering/querying APPs)
    • Initial K8S Helm Chart LCM Manager - for APP µServices etc. (ONAP & OSC) (new)
    • Initial Service Exposure Function (new)
  • In D Release: (NONRTRIC Release D Wiki)
    • Improved A1-PMS NBI (REST & DMaaP) (Rest style alignment)
    • Runtime configuration API (REST) for A1 Policy Management Service (e.g. add/remove adapters, near-rt-rics, security certs, etc)
    • Deployment – Continued improvements for Docker & Kubernetes
    • Extended/Easier deployment options with OSC IT/DEP project (SMO/NONRTRIC deployment)
    • Improving CI/CD to support include A1 Policy controller dependencies from ONAP
    • Multi-version support ( O-RAN A1-AP v1.1, v2.0, v2.1,v3.0 & OSC pre-spec A1)
    • Improved status monitoring/notification of A1-EI Jobs
    • Further improvement in security cert management (All interfaces can now be secured using TLS)
    • Re-architect & improve usability of Non-RT-RIC Control Panel (GUI)
    • Extend NONRTRIC Control Panel to edit/create A1 Enrichment Types/Jobs
    • Extend NONRTRIC Control Panel to configure A1 Policy Management Service
    • Configurable Service Exposure function – Extends/Replaces static exposure gateway in OSC Cherry
    • K8S Helm Chart LCM function for App µServices
    • Update NONRTRIC demo/test environment (one-click tests/use-cases, docker & single/multi-node K8s env)
    • OSC e2e integration use case – O-RU-FH-HelloWorld recovery
      • App to instigate O-RU-FH connection recovery after failure – via O-DU
        • Multiple implementation options – standalone µService and/or deployable ONAP-PF policy script
    • CII badging – Already achieved Bronze/Passing Grade
More detail:

PTL: 

Jira:

D release source code, container images and deployment instructions

TODO


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: done
    • 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

D release source code, container images and deployment instructions (and status)

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

Source Code:

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: done
    • 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

D release source code, container images and deployment instructions (and status)

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

Integration:

Release notes:

Please see:  Use Case Flow tests for D-Release

...

O-DU High

Primary Goals: 

  • O-DU high integration in Radio mode
  • Initial access and Attach procedure testing in Radio mode
  • DL and UL data path in FDD, 20 MHZ with 256 QAM and 64 QAM respectively
  • Static TDD mode support with Numerology =1
  • O1 enhancement
  • Closed Loop Automation Use case support

D Feature Scope: 

. 1. Achieve UL and DL data flow using FDD mode on 20 MHz Bandwidth, Numerology = 0

 2.Support for static TDD mode with pattern “DDDDDDDSUU” on 100 MHz Bandwidth, Numerology = 1

  • Evolve scheduler to support UL and DL scheduling of signaling and data messages on single spectrum in TDD mode
  • Expand scheduler to support Frame structure according to numerology = 1
  • Updates to cell broadcast for TDD and numerology = 1

3.Development activity for Closed Loop Automation use-case

  • Support for cell stop and restart within O-DU High layers
  • Support for cell stop and restart towards O-DU Low
  • F1AP Enhancements towards O-CU indicating cell stop and restart

4.Integration

  • Integration with O-DU Low in Radio mode
  • Integration with CU

5.End to end testing support (O-RU<->O-DU-LOW<->O-DU-HIGH<->RSYS CU<->Viavi 5G Core )

6.O1 enhancements - by HCL

  • Re-structure O1 module to run as a thread in ODU-High
  • CM Support - IP and Port configuration for DU, CU stub and RIC stub via Netconf interface
  • Support for Closed Loop Automation use-case

PTL: Sachin Srivastava

Status:

Updated:  7th July 2021

JIRA: Epics Status below:

  • https://jira.o-ran-sc.org/browse/ODUHIGH-184 - Done
    • As an O-DU L2 developer, I want to implement single UE DL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-185 - Done
    • As an O-DU L2 developer, I want to implement single UE UL data path and bench-marking
  • https://jira.o-ran-sc.org/browse/ODUHIGH-186 - Done
    • As an O-DU L2 developer, I want to add support for 64QAM modulation scheme in DL
      • Basic code changes complete. Testing in progress for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-187 - Done
    • As an O-DU L2 developer, I want to add support for 16QAM modulation scheme in UL
      • Basic code changes complete. Testing to be done for data path
  • https://jira.o-ran-sc.org/browse/ODUHIGH-264 - Done
    • As an O-DU L2 developer, I want to add support for Mu1
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress
  • https://jira.o-ran-sc.org/browse/ODUHIGH-265 - Done
    • As an O-DU L2 developer, I want to add support for 100 MHz Bandwidth
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release
  • https://jira.o-ran-sc.org/browse/ODUHIGH-266 - Done
    • As an O-DU L2 developer, I want to add support for TDD mode
      • Code changes at DU APP completed.
      • Resource allocation for SSB to msg5 completed
      • Code changes for UE registration flow in progress
      • Updates to k0, k1, k2 in progress will be continued in E release (Irrespective of FDD or TDD stack)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-299 - Done
    • As an O-DU L2 developer, I want to develop O-DU High Layers to support Closed Loop Automation Use-case
      • Yang modules to be supported by O-DU to ensure the end-to-end functionality of the use case "Closed loop" is in progress. Basic configuration is agreed to support CLA use case.
      • Internal call flow/message sequence between O-CU and O-DU for cell activation and deactivation is clarified. Call flow updated at 

        https://wiki.o-ran-sc.org/display/RSAC/Closed+Loop+Automation+Call+Flow+-+O-DU+High+APIs.

      • UE delete functionality complete
      • Cell delete functionality complete
      • Issue with mis-coordination between cell delete and DL RRC message, resolved.
      • Code changes for CU Interaction is completed
      • Code changes for Config update over F1 interface is completed
      • O1 Integration for O-DU  for CLA is completed ( Cell stop and Cell restart)
      • Blocker : code segmentation is observed, analysis is going on (code optimization is required to be scoped in E release)
  • https://jira.o-ran-sc.org/browse/ODUHIGH-267 - Done
    • As an O-DU L2 developer, I want to integrate O-DU High with O-DU Low in Radio Mode
      • SSB transmission successful
      • Debugging issue with Sib1 transmission , PDCCH is received but no PDSCH seen at O-DU low.
      • PDSCH for SIB1 is detected at L1 but L1 does not process it. Pointer is to check the PDSCH PDU parameters
      • Further debug sessions needed to close the ongoing issues.
      • There is no breakthrough even after several debug sessions with O-DU Low
      • SIB1 detection at L1 is successful. PHY.XML is updated with removing the hardware accelerator (<dpdkBasebandFecMode> from 1 to 0 to force the SW encoder)
      • For the CLA usecase, Cell stop request is received from O-DU high to low but O-DU low sends stop indication multiple times. This issue is fixed in L1 later binary 20.08. This binary update will happen in D-maintenance phase. 
  • https://jira.o-ran-sc.org/browse/ODUHIGH-268 - Done
    • As an O-DU L2 developer, I want to integrate O-DU High with O-CU
      • Using Radisys commercial CU as a test fixture
      • New VM configured as per H/W and S/W requirements of Radisys CU
      • The Network interfaces and CentOS version needs to be revisited for the CU machine. This is achieved with limited OSC lab setup.
  • https://jira.o-ran-sc.org/browse/ODUHIGH-269 - Done
    • As an O-DU L2 developer, I want to support End to End testing scenarios
      • Testing of broadcast messages at O-RU emulator set to begin
      • Viavi confirmed receiving at O-RU. Needs verification from UE sim.
      • Debug session is planned on 23rd June to achieve SSB and SIB1 transmission till UE simulator and then follow with RACH procedure.
      • Latest issue: the eCPRI packets differentiation between control plane and user plane through vlan id is supported by Intel, however O-RU support the packet differentiation based on eCPRI packet type. hence the fronthaul transmission validation is blocked.
      • Intel shall update the L1 package supporting C/U plane differentiation using eCPRI packet type in the D-release maintenance phase.

Updates from HCL:

Dependency/Blockers:

  • O1 configuration for day-1 shall need to be completed to start with CLA. However basic configuration e.g. cell state/operational state/admin state shall be supported initially. Use admin state as unlocked to validate the RU link failure.
  • Server(VM) configuration (H/W and S/W) to mount Radisys CU as a test fixture. 
  • Unable to use valgrind with Intel libraries. Debugging must be carried out with Alternate methods.
  • Intel/Viavi to confirm successful decoding of SSB/SIB1 at UE sim (TM500).


D release source code, container images and deployment instructionsTODO

Release-Notes — o-du-l2 master documentation (o-ran-sc.org)


O-DU Low

Primary Goals:  

—Continue O-DU low and O-DU high pairwise test.

—FAPI P7 massage integration -> Ongoing

—Continue O-DU Low and O-RU emulator test.

—Further CU plane testing -> Ongoing

—Continue E2E test with UE simulator.

—Support the UE attachment test

—Development activity for Closed Loop Automation use-case

—Support and test for cell stop and restart within O-DU High layers


D Release Feature Scope: 

PTL: @Zhimin Yuan

  • Status

D release source code, container images and deployment instructions

TODO

...

Simulators (SIM)

Primary Goals:

  • Support rapid prototyping by providing simulated interfaces

D Feature Scope:

  • Enable "Closed Loop Use Case" demonstration by providing O1 interface Simulators for:
    • O-DU (containing o-du-hello-world YANG model)
    • O-RU (containing O-RAN-RU-FH November 2020 train YANG models)
  • O1 Simulator improvements:
    • "Blank" simulator, which allows dynamically loading any YANG models of interest, for simulating a NETCONF/YANG interface 

PTL: Alex Stancu

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

Status:

  • O-DU O1 Simulator docker image available in Nexus (version 1.3.3) 
  • O-RU O1 Simulator docker image available in Nexus (version 1.3.3)
  • Blank O1 Simulator docker image available in Nexus (version 1.3.3)

D release source code, container images and deployment instructions

Docker container images are described here.

Each repository has a branch named "dawn" that can be accessed using git: "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/sim/o1-interface". Make sure to replace the URL with correct repositories. Note that this branch is in maintenance and all new development is done in branch "master". The complete list of repositories belonging to the SIM project is here.

Deployment instructions here.

Please see:  Use Case Flow tests for D-Release


Release Note:

Infrastructure (INF)

Primary Goals: 

  • Implement the O-Cloud reference design, provide the real time performance to allow the O-DU and other components running on top of it.
  • Provide interaction capabilities with other components.

D release Feature Scope:  

  • Enabe the 2 AIO severs with additional worker nodes deployment scenario
  • Major components upgrade
  • Implement the O2 interface as the MVP (will defer to next release)

PTL: Xiaohua ZhangJackie Huang

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

Update at 04 Jul   

  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyINF-172
  • Jira
    serverORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyINF-214

Test:

Getting Start (Cherry
  • ORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyINF-214

Test:

Release Note:

D release source code, container images and deployment instructions

D release source code, container images and deployment instructions

TODO



Integration and Test (INT)

Primary Goals: To support OSC project CI pipeline. To test and validate the components and use cases

Cherry Feature Scope: 

  • Automated CLM and SonarQube Scanning CI Jobs
  • Improve CI for OSC projects
  • Validate and and Test platform and use cases 


PTL:  Zhe Huang

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


D release source code, container images and deployment instructions

not applicable

...

Service Management and Orchestration  (SMO)

Primary Goals: The primary goal of the SMO project is to integrate different software artifacts of existing open-source projects creating a fully functional open-source Service Management and Orchestration (SMO). 

D Feature Scope:

  • Support for O1 interface
    • Implementation of NETCONF client in SMO
    • Reference implementation of a NETCONF server that O-RAN Network Functions, e.g. Near-RT RIC, CU, DU and RU can use. The code can be found at https://github.com/CESNET/netopeer2
    • A minimal set of YANG models that demonstrate the capability of the O1 interface while satisfying the closed-loop automation use-case.
  • Support for O1/VES interface
    • Demonstrate the capability to receive VES events, collect them in a dB, and display them in a dashboard.

PTL: Mahesh Jethanandani 

Status:  

  • An implementation of the O1 interface has been checked into Gerrit. Check out this repo. It has been tested on Ubuntu Linux version 20.04. Feedback is appreciated on other versions and operating systems. Note, this commit is not feature compatible with the O1 interface in other implementations. Some of those features have been identified and marked as enhancements in either this or the next release.
  • An implementation of the VES interface based on schema version 7.2.1, with backward compatibility to 7.0, has been submitted for Gerrit review, and review comments have been provided. Author has updated the commit based on the comments. Waiting on more reviews. Again, the commit is not feature compatible with VES interface in other implementations. Some of those features have been identified and will be added in this or the next release.

Jira: Count of Epics ( 0 issues ), User Stories, Tasks, and Issues:  6 issues

D release source code, container images and deployment instructions

Docker image and instruction on how to install SMO O1 interface can be found here.

Docker image for instructions on how to install SMO O1/VES interface can be found here.

The repository has a branch named "dawn" that can be accessed using git. For the O1 interface the repository can be found at "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smo/so1mo/o1", whereas the O1/VES repository can be had by "git clone --branch dawn "https://gerrit.o-ran-sc.org/r/smosmo/ves"