Project Technical Lead: Paul Carver. Elected 1/17/19.
Project Committers detail:
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.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
...
Committer
...
Committer
Company
...
Committer
Contact Info
...
Self Nominate for PTL (Y/N)
...
Tapio Tallgren
...
Nokia
...
...
Gabor Szabo
...
Levente Kale
...
Baha Mesleh
...
Raghurama Mandru
...
Paul Carver
...
AT&T
...
pcarver@att.com
...
The
...
...
Mike Hunter
...
Intel
...
...
Presentation:
| View file | ||||
|---|---|---|---|---|
|
Use Case Details:
...
Attributes
...
Description
...
Informational
...
Type
...
New
...
Industry Sector
...
Telco networks
...
Business driver
...
Optimizing a radio network is a complex task considering that we want to
Use the available radio spectrum, front haul and back haul network capacity, and signaling capacity optimally
Provide optimal quality of experience considering the application type, user subscription, and user mobility
Be able to collect diagnostic data for fault analysis and performance optimization
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.
Radio Edge Cloud blueprint is member of the Telco Appliance blueprint family which is designed to provide a fully integration tested appliance tuned to meet the requirements of the RAN Intelligent Controller (RIC). When complete it will include automated configuration and integration testing from the below the OS up through RIC (from https://gerrit.oran-osc.org/r/#/admin/projects/). As a member of the Telco Appliance blueprint family it will share many hardware and software components, including installation, configuration management and APIs with other family members. Each family member will be a separate appliance with a close family resemblance to its siblings.
Key Attributes
- Specific hardware configuration that are automatically tested via continuous deployment automation. Multiple hardware variations may be tested in parallel, but each tested configuration will be fully specified and reproducible.
- Specific pre-boot software (e.g. firmware/BIOS) will be specified as part of the CD tested configuration
- Reproducible software installation and configuration - an opinionated deployer will allow deployment of large numbers of sites with versioning that is traceable back to automated CD testing
- Modular building blocks will be assembled and tested (via CD automation) to ensure a guaranteed level of performance of the target application (RAN Intelligent Controller) while allowing other members of the family to assemble and tune the same modular building blocks to other target applications
- May be extended in the future to integrate RIC+other application, but still in an appliance with tested/guaranteed performance of the combined application set
Child Pages
Children Display sort title
Original Proposal Presentation:
| View file | ||||
|---|---|---|---|---|
|
...
Business use cases
...
As an operator, I want to
Deploy an LTE/5G network as the components RRH, DU, CU, and RIC to leverage the benefits of standard hardware and software infrastructures at the edge of the network
Promote an ecosystem of interchangeable components in the RAN
Enable new machine-learning based algorithms for optimizing radio access
Some use cases that the RIC enables
Sampling Channel Quality Indicators to get a better understanding of the radio network quality in different locations
It supports collecting and storing detailed event logs for troubleshooting and performance optimization
Especially, the 5G network new radios allow fast-speed beamforming. Therefore, it is possible to use intelligent algorithms to guide beamforming with different parameters
There are also other tunable parameters in the radio network related to radio capacity allocation and power saving
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
lists as use cases:
per-UE controlled
Load balancing
RB Management (radio band?)
Interference detection
Interference mitigation
In addition, it enables
QoS management
Connectivity management
Seamless handover control
...
Business Cost - Initial Build Cost Target Objective
...
The RIC has different deployment models which have slightly different cost implications:
It can be co-located with the RAN CU
It can be co-located with the Orchestration&Automation system
- It can be a standalone system
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
...
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
...
Use Case
...
RIC
vRAN
...
Blueprint proposed Name
...
Initial POD Cost (capex)
...
Scale & Type
...
x86 OCP Open Edge servers x 6
...
Applications
...
Power Restrictions
...
Infrastructure orchestration
...
Airship
Redfish
ONAP
...
SDN
...
Workload Type
...
Additional Details
...