Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
John KeeneyNon-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
Add O-RAN Distributed Unit Low (ODULOW) May 31st Bronze delivery request to the top of the agenda because we ran out of time last week.
Jack has copyright updates. It should be a part of the agenda. Action/ Farheen Cefalu add copyright updates to the agenda.
Jack as we approach Cherry I would like to ask other team members to bring up changes to the agenda to improve the Cherry release. I invite your ideas and recommendations of how we should adapt. For others please work with the RSAC committee to start planning Cherry. The more pre-work we can do it is better. It is important that we as a team participate on the planning of Cherry.
Release Votes and Approval
Marketing of the current release (WG, LF, PR)
Virtual Exhibition.
Jinri - I was absent last week.
The virtual exhibition has been opened. Action/ Farheen Cefalu add link to the website.
The demos once approved will be on the O-RAN website.
Jack: It is not quite time yet to release information on our Bronze release. Typically if we ask for companies to add statements it takes a little time. We want to gather the statements in advance of the press release. We should add this to the list. Action/ Farheen add reviewing Bronze release highlights
Action/ Farheen Add the O-RAN-SC logo request to the marketing agenda.
Nokia and AT&T will put something together for the plugfest. During the plugfest which is 9-21-2020 we will put the RIC.
Another idea we have to add here is the OSC logo. What is a good logo that covers what we want to do. If someone is interested in taking the lead. We should add it under the marketing piece. It is better to have a logo rather than text because other LF projects have logos. Looking for TOC member who wants to take the lead on the logo.
Status of Open Action Items (Old Business)
Action/ William DIEGO update on the coordination with the O-RAN test group
For the moment I just sent you the timeline for the ETE test focus group. We need to update the Cherry release timeline. I will continue to follow the test integration focus group.
Action/ user-d3360add the longer term test strategy to the agenda.
Action/ Farheen Cefaluadd the update on the copyright issue for us. This has been an ongoing decision for some time.
Jack got confirmation from the legal team on item 1. Each contributor retains the full copyrights...
O-RAN does not technically doesn't have possession of the copyright material. There is a gap in time. See the item 2.
The board has to grant permission to make the decisions. The intent is broad to cover all the items that we have requested in the specifications.
John-Paul: I interpret this to mean is OSC the A1 spec was worked on collaboratively we can go the executive committee to seek permission to use for specifications received by the Alliance. Jack: Once a spec is approved they will grant the use. There is a little gap in once the o-ran alliance approves the spec.
There is a third item that is being worked on for 3GPP. I will invite someone to talk about that once it is ready to be shared.
Standing Agenda Items (Brief Status of Ongoing Activities)
Rittwik: We started gathering the Cherry release items. For O-DU to be functional we need to agree on a specific format or minimal viable configuration (bandwidth, numerology). Implementation depends on our consensus. All upstream use cases will depend on this MVP. As a team we need to make progress. There will be issues if your infrastructure does not match the use case requirements.
Zhimin - We want to know what are our priority contributions.
Rittwik - In general how advanced does O-SC have to be? We need advice from the TOC of what is the minimal viable feature set the O-DU supports. OAI will also need this requirement also
Ganesh - I believe we will benefit in another focused meeting. It can be feature rich that can be built out. We need to have a roadmap done so we will see how it matures over the next three releases. From Radisys we can support this approach.
Jack - The minimal viable product set that we are coming up from an OSC standpoint is to demonstrate the interfaces of O1, E1, E2 interfaces and show a minimally viable functional stack. We need to define a scenario of three different radios that walk through a series of scenarios that run as a functioning stack. How to install, operate, setup, tear down, hand off a session. You need to demonstrate a working stack. That is our first vertical attempt. Then you start working horizontally adding and improving functionality based on features and capabilities. Without a stack in place with a very advanced CU or DU to talk to makes it a very fractured feature. This is my thought process. The integration test team has to demonstrate this minimal stack interfaces working together.
Two TOC meetings ago we continued the improving the test team process. We recommend starting from Cherry we will be putting out the messaging instead of enforcing during the gerrit review process. The recommendation was let us first come up with Best Practices then review how it was executed and then enforce the gerrit workflow changes.
there is no self merging. You have to get a +2 score from a reviewer who is not yourself. The other is not allowing a huge single submission.
Under Integration and Test Release Testing Plans we will have 3 use cases. Healthcheck, O-DU Integration, and the Traffic Steering Use case.
Team members review and make sure the flows are represented correctly Release Testing Plans
Traffic Steering use case layer is planned to be delivered later this week. I hope Matti's team can update the call flows so we can test.
O-DU integration presented a deck two weeks ago. They will deliver in the Bronze point release.
Jack: I look to the team to figure out a process to create a score card to track the progress of each process relative to the target requirements of each release. That summary score card is what we will share with others. No one will have a perfect score but we have to understand how each project will deliver.
Integration and testing status report
Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
John KeeneyNon-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
Jack will the O1 spec effect O-DU low or O-DU high? How the O1 will handle the split?
Zhimin No we are not discussing on O1.
Jack: Ganesh get to an agreement about the split.
Ganesh: The O-DU plain once it is out it will have a consistent interface. O-DU is one logical physical entity High and Low.
Fapi Interface development slide 2.
We have fronthaul interface
test mack stub will be stored in github repo.
Inside is the O-DU low project with the FAPI translator.
Jack Intel has submitted a license that the O-RAN legal team has accepted. We are working toward tomorrow morning US Eastern time. We have to get this on the TSC agenda. We have to get the OSFG vote. The goal is to approve using the Intel binary as a test fixture in this structure. O-RAN legal team has approved using it as a test fixture. The software will not appear on the LF repo but be on demand on the test assembly. We need to get approval from the OFSG members to vote and bring it to the TSC meeting. Hopefully by tomorrow we will have approval.
Zhimin: O-RAN Community B time line: Our target is May 31. The code will be available in both the osc repo. Can we be included in the Bronze release?
Jack: That leaves no time for test. We can make it available by the July time frame as a part of the Bronze maintenance release. Generally we don't release code unless we can pass some of the tests and use cases.
Zhimin: The binary license was agreed. We are now focussed on the process. We can start testing our software application in the lab. If we can pull in one week? Is that possible?
Jack: Lusheng can testing be completed by the end of May?
Lusheng: If everything works well and it's not too complicated. Another gap we have the integration with O-DU High. Ganesh?
Zhimin: For the Bronze release finished with O-DU High is not for Bronze but for Maintenance release. Can O-DU Low be a part of the Bronze release?
Lusheng: There is no integration test. We call it unit test. Jack I think Zhimin is asking for participation in normal release B and not as a part of the flow. The flow will be delivered by the maintenance release.
Jack the broader TOC needs to understand. We don't have to make a final decision this week. Let's take it up next week at the TOC level to see if we are OK with including O-DU Low as a part of the Bronze release with only unit testing. Let us take a vote on it next week on how we want to proceed. Is it a part of maintenance or Bronze.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
OAI purposed Meeting
OSC Logo
Planning for Next Meeting
Next Tuesday there is an OAI meeting. If you wish to participate please join the zoom meeting for next Tuesday. We will hear from the OAI group of what they are thinking about activities, coordination, and interest.
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
Votes:
he minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.