There is work going on for demos. Jinri is collecting material. This is an O-RAN activity.
LF Networking Conference in April. If people are planning on attending please reach out to Jack or Jinri. This will be in LA. Feb 3rd deadline for proposal. Planning on having a small kiosk or booth for demos.
Tracy - The work we did for the plugfest is on the LFN program this month. That is not a big event. This is for developers.
Action/ Tracy Van Brakle will send info on LF Networking to Jack and add the event to our wiki.
Status of Open Action Items (Old Business)
Action/ TOC voting members: Provide an alternate contact on theTOClist above.
There is a press release on O-RAN wiki for this event that went out. They are waiting for the press release. The executive committee will let us know in the next two days. The press release was impressive.
We learned a lot captured in Jira tickets.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Rittwik will meet this week and report out next week.
Action/ Jinri Huangprovide an answer to user-59b16regarding support for O-CU, O-DU. Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
One based on O-RAN services and OAM functions that will form tracks that each release will be improving OAM. The end to end use case relies heavily on O-CU and O-DU functionality that we can progress in this release.
We need to synch up with the PTLs of O-CU and O-DU and the architecture committee to support these use cases.
Rittwik - update yesterdays RSAC meeting Ganesh from Radisys this Friday. He is encouraging O-CU and O-DU come together and identify feasible use cases.
This is a high priority and PTLs must work together. Be modestly aggressive to target this release. Looking forward to an update next week on these discussions.
Rittwik - Setting expectations: when KPIs come to RIC (measurement page) then you do the analytics and then turn it into a traffic steering action as a simple hand off from one cell to another not a real UE. We need a realy UE simulator component needs to be contributed to understand the hand off.
Action/ Farheen Cefalu add to agenda. Call to Community to address the UE simulator as well as the fact that the test community in O-RAN will have a need for this. We have our Simulator team that can identify a UE simulator.
Action/ PTLs enter epics from Contributions into jira.
Jack will start pulling reports from Jira to see the scope of this release.
Action/ PTLs participate in the Bronze planning meetings held twice a week by theRSACcommittee. PTLs who are planning to contribute to Bronze must attend.
Action/ PTLs pull together a summary of each of the projects on what they plan to deliver in Bronze release.
ETE use case is focused on the lower stack but we don't want to ignore the higher level functions. What use case can drive the work in the non-Realtime RIC.
Tracy - O-RAN testing group has a POC plugfest keyed up for the Bronze release. Plugfest will be end of June 2020. It's a dynamic 5G multi-operator with first responders.
Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
Standing Agenda Items (Brief Status of Ongoing Activities)
After every release we will have a window where a developer can work on the maintenance items. We're trying to improve what we have done for the Amber release.
Make changes to the Amber branch. If you need help to trigger the jobs for the Amber maintenance release contact user-d3360
Is there a roadmap of the O-CU functionality of how you will add functionality?
Action/ user-a934b provide a list of functionality that you plan on targeting of where the O-CU is going in the coming releases. It is a critical piece and will need a roadmap view.
Working on epics. Planning to deliver epics next week for Bronze release. We need to work with O-DU to provide infrastructure. Please include Xiaohua Zhang for infrastructure.
Think about best practices area. Read that and give guidance to the team of what your expectations are around the documentation. To make things usable outside of developers to make it work. Both the software detailed documentation and how to use the overall system.
John KeeneyNon-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
Working on epics. We plan to tidy up our repo. There is functionality that should be in other projects such as simulations, and dashboard (OAM). We will set up sub repos in those repos.
The need for coordination of the SC and O-RAN projects. IBM is duplicating work. We plan to look through our roadmap to see where to push those changes. Whether to O-RAN or O-RAN SC.
Part of the challenge of being new and starting new. People are confused on coordination. This raises another discussion about what an SMO is and should we have a project and space to pull together the SMO owrk. Original agreement was ONAP would be upstream and RAN specific should be here with O-RAN Alliance. As a community how do we sort out this overlap and now that this community has been established how do we structure the needs.
This is a good conversation to start at the plugfes in Prague. If we have a slide that explains the division of labor that would be very useful. I know Vimal worked on something like that. Jack will talk to Vimal to sort it out
All parties are well aware with Vimal's slides but we want more.
One suggestion ONAP may need to be happening this conversation rather than here. Trishan de Lanerolle can help get the right people.
We have the right people. We need to coordinate it better.
Jinri requested new agenda item for discussing community contributions too PoC at MWC Barcelona.
Jun Song: procedure for individual company to contribute at MWC?
Jack: open use of O-RAN SC software because it is open source, but nice to know who/how using; but if making claims regarding O-RAN such as compliance, then need permission from O-RAN Alliance.
Jinri: concur with Jack. also can be done by individual company, but we are collecting and coordinating for representing the community under WG1
Jun: customer related, so need to discuss with them.
Jinri: can proceed in parallel, discussing with customer and providing info to the collection table.
Jinri: regarding the MWC demos: Paul Smith and Jinri are collecting info on MWC demos; two gate points: 12/19 for entering info and preliminary approval, 01/20 for completing preparation and final approval for any PR.
Jack: LF Networking conference April 2020. we will coordinate presentations there.
Jinri: Global plugfest events at NA, EU, Beijing. PR under preparation, will be on wire today, covering O1/A1 PoC, as well as Beijing plugfest. Active attendance: over 70 companies; 200+ attendees; 4 integration groups testing open front haul; WG6 in HW SW decoupling;
Status of Open Action Items (Old Business)
Action / TOC voting members: Provide an alternate contact on the TOC list above.
Tracy: completed uploading video recording to O-RAN.Need approval to upload to LF wiki.
Jinri will make request to EC tomorrow.
Martin: remove this action item.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Jack: Rittwik on vacation, action item deferred.
Action/ Jinri Huang provide an answer to user-59b16 regarding support for O-CU, O-DU. Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
Jack: will be high priority when we come back in Jan.End-to-end use cases require support from O-CU and O-DU.Need PTL commitments.
O-CU PTL: support UE attachment first, challenge for e2e data collection, design in release B.
Work with RSAC to pull this together, to identify which items to complete in B, which to defer.
Same for O-DU's.
Every module to perform some basic self-test, reporting, and communication functions so dashboard reports them as part of the inventory.
From RSAC main ask for O-CU is E2 interface reporting which depends on progress by WG3.
Many software functions can move ahead of spec.
Action/ PTLs enter epics from Contributions into jira.
Will use JIRA more in Release B for reporting and tracking.
Need more participation on cross-project/company activities/contributions. Will ask one ToC member to coordinate inter-project activities.
Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee. PTLs who are planning to contribute to Bronze must attend.
Standing Agenda Items (Brief Status of Ongoing Activities)
Jinri - Making a video that will cover the software community.
Zbynek (PM O-RAN Alliance marketing and communications) wrote a newsletter for the EC meeting. Jinri will attend and will include the Amber release in this newsletter.
Jinri - 2 plugfest sessions last week organized by Tracy has been recorded. Tracy reported this to EC this morning. Tracy raised whether she can share the video with the SC. Suggested to put it on the o-ran wiki first then decide whether to make it public on the software wiki.
North American and Asian session happening this week.
Preparation work has been done
Tomorrow there will an operator lab tour
Orange, Telecom Italia, Geo, and Sprint will be visiting the lab for the plugfest.
Tomorrow afternoon we arranged a slot to shoot a video for the MWC video.
In the Asian session we prepared 5 integration line. You can understand it as 5 different sets of test and integration.
5 sets of demos integration and test.
We will demonstrate an online show that will be available to public to watch the demo live.
To accomodate time zones morning timeslot will be made convenient to US and afternoon for Europe.
Around 200 attendees.
Keynotes, test and integration results by the group data gates, and round tables.
We also prepared the live broadcast can join via Zoom bridge.
Although in Chinese we provide translation
Next week will be a deep dive sessions.
Anyone who is interested can join us.
A lot of attention is being given to the software community. We need to work with the plugfest attendees how to utilize their feedback and use it.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Started communicating.
Standing Agenda Items (Brief Status of Ongoing Activities)
Action/ Jinri Huang provide an answer to user-59b16 regarding support for O-CU, O-DU. Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
Use Samsung as an E2 starter example.
Between now and end of year all PTLs must put the epics into Jira.
In January the TOC calls should refer Jira tickets.
We are ready to release the bronze release document.(Contributions)
Action/ PTLs enter epics from Contributions into jira.
Martin - suggestion to create one common link.
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
Jinri - 5 minutes to introduce the Asian Plugfest and 3 minutes for the O-RAN F2F
Next F2F is in Feb 17 - 22 in Paris. One week after Barcelona meeting.
Daily working sessions with only 3 hours for TOC. Would like to see more time for TOC added to the agenda.
All these sessions happen in parallel. They are across different working groups. Before we used to invite our delegates from other WGs to join. We also want to reach out to have different WGs meet. Example would be Rittwik attending another working group meeting.
Rittwik only drawback is when TOC is going on you miss the parallel sessions.
Rittwik - Raise a concern about the low attendance of PTLs for the Bronze release planning.
It is the end of year holiday season so low attendance is expected this time of year.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
Votes
The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
Action/ Jinri Huang provide an answer to user-59b16 regarding support for O-CU, O-DU. Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
Action/ PTLs enter epics from Contributions into jira.