| Company | Functions/Components implemented by contribution | Running Platform/ Environment | Source code repos | Target Contribution Date | Status | ||||
|---|---|---|---|---|---|---|---|---|---|
repo name | Description | code license | committers | language | |||||
| Lenovo | Abstraction Adaptation Layer | OpenStack Hypervisor | aal/lib | Apache2 | liufeng24@lenovo.com, lujq1@lenovo.com | done | |||
| aal/logic | Apache2 | done | |||||||
| aal/mgmt | Apache2 | done | |||||||
| aal/virt | Apache2 | C/C++ | done | ||||||
| China Mobile | Integrated eNB | x86 Server | |||||||
| Inspur | Infrastructure monitoring | x86 Server | imp/metal | Host Configuration Management | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | |
| imp/metal-api | Host management interface | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | ||||
| imp/fm | Host Fault Monitoring, Detection and Recovery | Apache2 | gaosong.lc@inspur.com, liutao.lc01@inspur.com, qiaoxj@inspur.com | Python | requested 2019/06/11, LF Ticket #76725 | ||||
| Intel | DU layer 1 | x86 Server | o-du/phy | O-RAN DU Layer 1 | Apache 2 | zhimin.yuan@intel.com, vitaliy.zakharchenko@intel.com, nicolas.chautru@intel.com, luis.farias@intel.com | C/C++ | requested 2019/06/11, LF Ticket #76725 | |
| Radisys | DU layer 2 and layer 3 | x86 Server | o-du | O-RAN DU | Apache 2 | C | requested 2019/06/11, LF Ticket #76725 | ||
| o-du/l2 | O-RAN DU Layer 2 | Apache 2 | balaji.shankaran@radisys.com, somshekar.ydlapur@radisys.com | C | requested 2019/06/11, LF Ticket #76725 | ||||
2021
| Company | Functions/Components implemented by contribution | Running Platform/ Environment | Source code repos | Description | License | committers | Language | Target Contribution Date | Status |
| ORAN Alliance WG 6 | AAL FEC | x86 Server | aal_fec/profile | Why WG6 is considering splitting its AAL FEC specification into two portions to be published together in the July 2021 train – a) a formal specification document published through the normal O-RAN FRAND process that covers stage 1 and stage 2 specifications, and b) a stage 3 API document that covers data structures and programming language level details specific to open source implementations such as DPDK that would be published in ORAN OSC repo under a BSD license and referenced from the formal AAL FEC specification. The purpose is to enable easier ingestion of the ORAN FEC gaps identified by the ORAN community in upstream communities such as DPDK. What To facilitate this split, WG6 co-chairs would like to request an OSC repo titled aal_fec/profile to be created for the above purpose. The purpose of this repository would be to store stage 3 specification documents and in the future, header files as well as test artifacts for the AAL FEC profile. Releases from this repository will be aligned with ORAN specification release trains as we intend to publish the stage 3 specification updates conjointly with the main spec. License BSD – we would prefer a BSD license to be compatible with the upstream community (DPDK) with which the spec is to be aligned. | Exception request: BSD | niall.power@intel.com (PTL) | C/C++ | ToC consideration (June/30/21) |
Guidelines:
Seed code preparation:
...