Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Submitter | Committer Company | Committer Individual | Self Nominate (Y/N) | PTL |
Tapio Tallgren, Gerald Winsor Nokia | AT&T | |||
Nokia | ||||
Intel |
Attributes | Description | Informational |
Type | New |
|
Industry Sector | Telco networks |
|
Business driver | Optimizing a radio network is a complex task considering that we want to
To address these needs, the O-RAN Alliance is defining the Radio Intelligent Controller (RIC) and new interfaces towards the LTE/5G Radio Access Network (RAN). Especially, the RIC has the E2 interface towards the RAN Centralized Unit (CU), and the A1 interface towards an orchestration system such as ONAP. This allows for more intelligence in managing the radio resources. Especially, the RIC has a Radio Information Store database with generic information about radio resources, it supports third-party applications with access towards the RAN, and it has a high-speed, high-capacity message bus. |
|
Business use cases | As an operator, I want to
Some use cases that the RIC enables
All of these allow for more optimal resource allocation which will benefit the end users with better quality of service. The O-RAN: Towards an Open and Smart RAN. O-RAN Alliance White Paper. Available from https://www.o-ran.org per-UE controlled
In addition, it enables
|
|
Business Cost - Initial Build Cost Target Objective | The RIC has different deployment models which have slightly different cost implications:
In the first case, as the RIC will run on the same infrastructure as the RAN CU itself, it will meet all the performance requirements. In the second case, the RIC is some distance from the RAN. It is running on cheaper hardware in a datacenter, but since its performance requirements are stricter than that of the Orchestration system, it may require a different infrastructure layer. |
|
Business Cost – Target Operational Objective | For Example: 1.Edge Cloud deployable at Central offices with 7 servers in a single rack should incur low operational costs per year 2. In-place upgrade of the Edge cloud should be supported without impacting the availability of the edge applications 3. Edge Solution should have role based access controls, Single Pane of Glass control, administrative and User Based GUIs to manage all deployments. 4. The automation should also support zero touch provisioning and management tools to keep operational cost lower |
|
Security need | The Radio Edge Cloud should be resistant to physical tampering, but it can be dedicated as a single user system |
|
Regulations | The Edge cloud solution should meet all the industry regulations of data privacy, telco standards (NEBS), etc., |
|
Other restrictions | Consider the power restrictions of specific location in the design (example - Customer premise) |
|
Additional details |
|
Case Attributes | Description | Informational |
Type | New |
|
Blueprint Family - Proposed Name | RT Cloud |
|
Use Case | RIC vRAN |
|
Blueprint proposed Name | Radio Edge Cloud |
|
Initial POD Cost (capex) |
| |
Scale & Type | x86 OCP Open Edge servers x 6 |
|
Applications | RIC |
|
Power Restrictions |
| |
Infrastructure orchestration | Airship Redfish ONAP |
|
SDN | OVS-DPDK |
|
Workload Type | Containers |
|
Additional Details | Submitter to provide additional use case details |
|