Tracy: Ericsson, Nokia, Samsung and Comscope with AT&T person as a moderator. We submitted a request for a panel discussion. Will discuss lessons learned and cross activities. Proposal references O-RAN SC.
Jinri - Companies who are had demonstrations MWC can submit their demos to the website. Action / Jinri Huang work with Farheen to add to events.
Jinri - We had planned lots of items for discussion. We only scheduled two days plus one joint session with WG1. We have a lot of items to discuss. the original plan is to do this week. We want to hold it off until next week.
project report from each PTL lasting 10 - 20 minutes.
Collaboration discussion from OAI.
Can we take next Tuesday, Thursday, and Friday the same time as TOC? We don't expect too much participation with O-RAN WGs. 8:30 - 9 EST.
If we have our regular meeting on a Wednesday we will have to use 4 days in a row. Instead let's dedicate this time slot.
Lusheng - Demonstrations have to be scheduled.
Jack - Let's use next week to address the critical items. We will skip the TOC for one meeting. Let's get the most productive items in the time frame rather than have too many meetings in one week. Let us figure out the most effective way.
Rittwik - You can use the RSAC timeslot.
John Keeney is considering an Ericsson for a brief non real time RIC demo. Tracy will share the details.
Status of Open Action Items (Old Business)
Action/ Rittwik and Viavi.
contributions for the test and emulator lab. After checking internally with the team they will report back next week. Licensing and cost. Jack or Jinri viewpoints?
Jack - Funding is an option but we'll have to ask for additional funding. The question is how much and whats the value to us. Whatever we invest in is effectively used by the community. They want it set up in a community friendly cloud. Could it be a yearly agreement hosted in the cloud and managed by the integration and test team. Let's see what the best terms and conditions we can get for the software community to accomplish our goals. We should ask everyone to comment. Action/ user-59b16 start an email chain .
Rittwik - slides are on the RSAC meetings page.
Tracy - Not sure if O-RAN SC and O-RAN testing labs will share lab facilities.
Jinri wants to discuss F2F.
Action / Farheen Cefalu update the Events page with the updated virtual meetings.
Action / Jinri Huang wants to discuss the Open Data Set .
Big data will be useful for Ai/ML and test. O-RAN TSC set up a project to open data set. LF open data set has 3 projects set up regarding opening of data. What is the mechanism to open data? LF has already developed an agreement specifying the regulations that we need to comply. Community data license agreement has been created.
This CDLA has been written into our SC charter. We can open projects using the CDLA in the O-RAN SC.
China Mobile wants to propose opening the CDLA. This is a brief introduction. Action/ Jinri Huang will shared slides to set up projects using the SC.
Jack - we need to form a working activity to spend time talking and thinking it through. The data is always a rich place for discussions. The TOC doesn't have enough time to work it out. We need to report back to TSC what our plans and goals are starting this new effort. We should go through a process and talk to people and we're doing it right.
Jinri will provide materials and seek comments.
We should form a spot here of where to put the materials and have the discussion. Create the TOC on the left side of the tree to give the community a time to participate.
Jinri will use RSAC time to review.
Action/ user-59b16 update TSC with the short/long term UE emulator support.
Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
David (DT) will reach out to someone he knows and let the TOC know next week.
4 timeslots for this focus group and they are working on different documentations. I didn't have time last week to introduce myself. This afternoon I will introduce myself and be part of a link.
Lusheng - we have software called OTF open test framework. We are using it for the ETE flows for the health-check.
Jack - Let us figure out how to collaborate. We'll leave it to you and David.
Zhimin Yuan raised a concern about the ODU Low and test. Jack instructed Zhimin to work with Lusheng to address their hardware requirements needs.
Lusheng - Zhimin's ask is beyond test but also the building on the platform.
Actually it is software.
Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
Raised issue with aligning.
Jinri - we conveyed this information twice during WG and TSC sessions. The WG co-chairs have taken this message. One is WG2 and WG3 we adjusted the timeline with Cherry and D release.
Action/ Jack update the timeline and capturing the information. Jack will start generating Cherry for his release.
Action/ user-a934b work with Lusheng to create the test cases.
Community asked for a release manager.
We have a request out to the LF for some support on this. Trishan - will have a discussion with David Mc Bride. Action/ Trishan de Lanerolle set up a call with Jack and David.
Action/ PTLs be prepared to discuss Bronze development sprint 1 demos.
Lusheng will organize the end of sprint demos.
Jack after ever sprint we have demos to reflect the items completed.
Lusheng - We have a review process and only the committers can merge to master. In open source community we are having contributors who are committers and merging. Contributors should not merge.
Trishan - There is a +2 process.
Lusheng we want to have the +2 process an not allow the contributor to merge.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
(proposed by Thoralf): Any update (compared to last week) on ASN.1 availability from O-RAN (for E2AP) and from 3GPP?
Jack most projects are under Apache but the documentation is under Creative Common 4. As part of the charter we are an LLC under a series of LLC. Jack will respond to them.
Thoralf E2AP is the most needed.
Jinri - tomorrow there will be an E2 call. We can bring this there.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
O-RAN Alliance spec license restriction for ASN.1 spec (raised by Thoralf)
Jack has been talking to Stephan (O-RAN Alliance lawyer) to address the O-RAN Specification copyright in the O-RAN SC. There are discussions going on an alliance with TIP and with TMC.
From 3GPP we have submitted several requests about copyright usage. We've submitted requests twice and they've come back for more clarification. We are working through the standards groups to get done.
O-RAN Alliance spec license restriction for Yang model (raised by Martin)
Jack: Is it a copyright issue?
Martin: Yes, not clear how to use 3GPP data models
3GPP models are broken from syntax and how can we fix them? By working group 1 license statement. Latest ask by 3GPP is still not addressing our needs. Next version coming out in March is not useful and I can'tuse them in the Bronze.
Are you using them as a baseline?
We have modified once and found we are not allowed to modify.
We demonstrated at one event but I can not share the modeified ones with the public.
Likelihood high that all has to be modified and tested.
Clear statement that O-RAN Alliance should use and influence 3GPP but 3GPP is not used in the software community.
Any comments or thoughts?
Tracy: Thinks this topic will be discussed during WG1 modeling discussion at 5PM EST today. The goal is to getting this resolved but it's organizationally complicated across 3GPP and the O-RAN Alliance.
Martin: I am careful in selecting to avoid future issues.
Jack: There needs to be an abstraction layer. Once solved every time there is a change to the system doesn't it have to cascade through these layers.
Martin: The model was supposed to be the abstraction layer you will have a model on a model with a 1:1 relationship.
Jack: We're running into problems because we're tying to specifications that were never validated.
Martin: That is why I am selecting young data models. But the RAN specific stuff will be problematic.
Action/ user-d3360 send a reminder to the PTLs to update their projects Architecture page within on their wiki pages (near-RT RIC: done, ...)
Reminder sent. Jack will verify progress.
Action/ PTLs get your F2F slide decks ready. Due
Action/ TOC voting members: Provide an alternate contact on the TOC list above.
Action/ user-59b16 talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys
Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.
closed
Action/ user-59b16 update TSC with the short/long term UE simulator support.
Rittwik: initial meeting done, waiting on hearing what Viavi can bring to the community. will follow up with Viavi. Need a Packer Core simulator, UE simulator, RAN simulator, Viavi has all. Really need the full suite of simulator to complete simulating UE actions.
Jack: will pick up in future meetings, May create a track under integration and testing to continue. what to be done here what under TFIG.
Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
Jack: We need to interface with the test group so that we have coordination. Not doing test plans.
David (DT) will reach out to someone he knows and let the TOC know next week.
Jack: it won't be as extravagant as the test group has.
Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
Rittwik: KPI Mon xApp requests certain metrics coming form O-CU.
Yingying: O-CU will focus on U plane. No contribution on RRC part. UE attachment will be a problem in B release. E2 still under discussion with main contributor. E2 will be discussed in following weeks in WG8
Jung/Rittwik: O-CU not advanced enough to provide enough metrics to support traffic steering. Fallback plan needed, enhancing E2 simulator to provide enough support. Can SIM project support this? Otherwise traffic steer is in jeopardy. O-DU has a plan to support. But need O-CU support as well. Need ToC decision on the fallback plan.
CoChairs: Construct document for what's missing. Is this possible in Cherry or even further out?
Rittwik: RSAC to provide document on what's current, what's future, suggesting alternatives.
Jack: It will be a weak message if this cannot be supported.
Second use case (healthcheck) Non-RT RIC making progress
Action: Allocate a time slot next week to discuss.
Yingying: We will have the GUI meeting in an hour
The challenge is this is around the ETE traffic steering use case and how it will work with O-CU and O-DU development.
Action / PTLs Update your section of the Bronze Release (Jun 2020). Convey to people outside what we're going to do in this release.
Lusheng: reminder sent. only three projects which have not completed yet.
Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.