You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Welcome to the F release page for the O-RAN Software community.

The F release is being worked on and its source code is maintained within the master branch of each repo.

        


Near-Real-time RIC X-APPs (RICAPP)

Primary Goals: TODO

F release plan (<date>):

  • TODO

PTL: SUNIL SINGH  (former PTL still helping out: Matti Hiltunen)

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

F release highlights/accomplishments (<date>):

  • TODO

F release source code, container images and deployment instructions

TODO


Near-Real-time RAN Intelligent Controller Platform (E2 Interface) (RICPLT)

Mission: E2 updates with first E2APv2.0 support and improvements in subscription interface in xapp frameworks.

Original primary goals: TODO

Planned F release highlights

TODO

Status 2022-02-09: TODO

F release source code, container images and deployment instructions

TODO

Non-Real-time RIC (A1 & R1 Interfaces) (NONRTRIC)

Primary Goals:
  • TODO

E Feature Scope / Achievements:

  • TODO

Jira:

Operation and Maintenance (OAM)

Primary Goals:

  • TODO

F Feature Scope: 

  • TODO

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

TODO-udpate

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

Source Code:

Integration:

  • to be done

Release notes:

O-RAN Central Unit (OCU)

Primary Goals: 
  • In the absence of O-CU, Radisys commercial CU image to be used for E2E testing

D Release Feature Scope: 

  • Radisys Commercial CU being used as a test fixture for E2E testing
PTL:

Status:

Radisys Commercial CU being used as a test fixture.

H/W and S/W requirements have been shared and awaiting the same to be configured.

D release source code, container images and deployment instructions

not applicable

O-DU High

Primary Goals: 

O-DU new Feature Development

1.HARQ framework support and scheduler enhancement to prioritise retransmission

2.Enhancement of Scheduler

1.Multiple UEs/TTI

3.Mobility mode Support (Intra-CU handover)

4.Support for Idle Mode Paging

Feature verification

1.Closed Loop Automation

2.16QAM and 64 QAM (Spillover from D release)

End to end Integration support

1.TDD/Mu1/100MHz

2.FDD/Mu0/20MHz * (Spillover from D/E release)

Enhancement

1.E2 AP upgrade 2.0

F Feature Scope: 

  • HARQ framework support

  • Scheduler enhancement
  • Mobility (Inter-DU handover) support
  • Idle mode paging support
  • E2AP upgrade to v2.0
  • End to end integration support

Status on  

JIRA REFERENCE

1) Implementation of HARQ feature

https://jira.o-ran-sc.org/browse/ODUHIGH-402

Status: In progress

2) Scheduler enhancement to support multiple UEs per slot

https://jira.o-ran-sc.org/browse/ODUHIGH-403

Status: Todo

3) Support for E2AP version 2.0

https://jira.o-ran-sc.org/browse/ODUHIGH-404

Status: Completed

4) Intra CU Handover

https://jira.o-ran-sc.org/browse/ODUHIGH-405

Status: In progress

5) Idle mode paging

https://jira.o-ran-sc.org/browse/ODUHIGH-406

Status: In progress


Implementation of HARQ feature

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-410
https://jira.o-ran-sc.org/browse/ODUHIGH-417

Status

Completed

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-418
https://jira.o-ran-sc.org/browse/ODUHIGH-424

Status

In progress


Scheduler enhancement to support multiple UEs per slot

Jira:

Status

Todo

Support for E2AP version 2.0

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-409
https://jira.o-ran-sc.org/browse/ODUHIGH-416

Status

Completed


Intra CU Handover

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-407
https://jira.o-ran-sc.org/browse/ODUHIGH-420
https://jira.o-ran-sc.org/browse/ODUHIGH-414

Status

Completed

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-423
https://jira.o-ran-sc.org/browse/ODUHIGH-425

Status

In progress


Idle mode paging

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-408
https://jira.o-ran-sc.org/browse/ODUHIGH-415

Status

Completed

Jira:

https://jira.o-ran-sc.org/browse/ODUHIGH-419

Status

In progress

F release maintenance source code, container images, and deployment instructions

TODO


O-DU Low

Primary Goals:  

TODO


E Release Feature Scope: 


PTL: Luis Farias , Alternate: @Chenxi Yue
  • Status

E release source code, container images and deployment instructions

TODO

Simulators (SIM)

Primary Goals:

  • TODO

E Feature Scope:

  • TODO

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

Status: TODO

E release source code, container images and deployment instructions

Source code: https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fo1-interface.git;a=shortlog;h=refs%2Fheads%2Fe-release

Container images are described here: TODO

Instructions: Network Slicing Use Case TODO update

Infrastructure (INF)

Primary Goals: 

  • TODO

F release Feature Scope:  

  • TODO

F release highlights/accomplishments (<date>):

TODO

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

Update at <date>

TODO

Test status:

  • INF platform
    •  TODO
  • O2
    • TODO: update the test status

Release Note:

  • TODO

E release source code, images and deployment instructions


Integration and Test (INT)

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

Feature Scope: 

  • TODO


PTL: James Li

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


F release source code, container images and deployment instructions

not applicable

Documentation (DOC)

Primary Goals: TODO
Bronze Feature Scope: TODO

Jira: Count of Epics, User Stories, Tasks, and 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). 

F Feature:

  • TODO.

Status:  

Jira: Count of Epics ( 0 issues ), User Stories,

Tasks:

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

and Issues:  6 issues

F release source code, container images and deployment instructions

TODO-update

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

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

For the O1 interface the repository can be found at "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/o1mo/o1", whereas the O1/VES repository can be had by "git clone --branch e-release "https://gerrit.o-ran-sc.org/r/smo/ves"

  • No labels