we need better coordination with the test focus group in O-RAN. I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.
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.
Thoralf Czichy proposes that near-RT RIC platform functionality (content) freeze is Feb-7. This is as there's a near-RT RIC platform contributor planning f-2-f workshop planned Feb-3 to Feb-5. Bronze Timeline doesn't have an exact date (drawing suggest in week of Feb-3 to Feb-8). Preliminary content is here: filter10401.
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.
Gate 2 MWC demos. 16 demos. There are 3 demos that can feature the bronze release elements. I requested sponsors to include the software community demo whenever appropriate.
Jun Hyuk Song wants to see the which demos have the Bronze elements.
Jinri - 2 or 3 demos out of 16 are demonstrating SC. It will be on the o-ran alliance wiki. Paul may be putting this demo on their wiki. If it urgent for you then please reach out to Paul.
David Kinsey - A1 is mis-leading
We refer to it as O1-A1 functionality. David and Tracy will talk offline.
O-RAN Alliance F2F Feb 17-21 (Paris)
Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
Jinri requested PTLs to report their progress during the F2F meeting.
There is status of what's been established and the plan of what is in Bronze.
Focus on the plans for Bronze. We will arrange 1/2 hour for each project.
Jack encouraging everyone to be engaged in communicating the message of Bronze.
That every element in the stack and be built and deployed by the LF toolbase and the second ETE use case can be exercised the way it is supposed to function. Rittwik has defined what use case will be exercised in the Bronze.
John Keeney and Tracy Van Brakle and Martin Skorupski we want to articulate what we are targeting to release in Bronze. We need to reduce that to a written objective now that we are closing our use cases.
Rittwik as a part of closing this use case we need a clear two paragraph message that articulates what the community can expect out of the use case. This is an executive summary more than technical details. 2 paragraph executive summary. Whatever we've agreed to has to be documented. We have concerns that we won't progress far enough on the use cases but we should agree on what we are going to do in Bronze. Less about negotiation and more about what we have agreed to what the target is.
Rittwik - Asked Alex to reach out. Martin Skorupski we are in contact VeeAvi (sp?). For UE's we will need hardware which is difficult to acquire.
We need to find out what is the UE agenda. The O-DU project should see how they are testing the O-DU. We have to see if the actual UE simulators can be used to test O-CUs.
Jack - You will need a UE and a radio emulator.
Yes, I need a server that emulates a UE. You don't need RF equipment for this.
This is an important topic and key issue. Which raises, we need better coordination with the test focus group in O-RAN. I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group. It will take a commitment from TOC to spend time on the subject. Jinri is doing the PR work. If one of the other TOC can take on the role of coordinating with the test group. It is an important activity that will require coordination between the development and test teams. If we are going to coordinate on a UE simulator then the test group should also come up with someone.
Action / Farheen add to next weeks agenda
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. It is a critical piece and will need a roadmap view.
Jack - Look at negotiating with the working groups about our needs. I let the EC know that it is harder to maintain momentum in the second release due to exhaustion from the first release. We need to keep advancing. The first 3 or 4 releases are critical to the success.
Jinri - we can remind the working groups at the F2F meeting.
Rittwik - Reached out to WG8 RCU about supporting hand over for OSC. Their answer is negative. O-Cu feature won't be ready until Cherry release.
Be cautious that for Cherry release it has to be executable. It is too late to plan at the Cherry release.
Sorting out Intel's contribution for license. Lusheng will look into that. Intel API interfaces and loader are a part of the SC. They allow someone to take their software. Not compatible with SC licenses. Jack will be meeting with Stephan (Intel) that O-RAN can use their software for testing but is not an approved open source software. It is a testing apparatus that we can load. We still have a gap on what constitutes a layer 1 open source contribution.
Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
If there are one or two alarms already known then inform Martin Skorupski
Martin will be flexible about the alarm formats, etc.
Action/ PTLs participate in the Bronze planning meetings held twice a week by theRSACcommittee. PTLs who are planning to contribute to Bronze must attend.
Rittwik - OAI fell off the list. We had a meeting with OAI.
Christian (Orange) - Drafted the open interface license with Nokia to understand the differences between OAI and
Christian - OAI across systems to provide something related to E2 service model. Not directly open interface focused but Eurocom (sp?) funded Mosaic 5G within this is a flexran project. Flexran is related to near real time RIC in O-RAN world.
Mohamed (Orange) - As a part of my work on 5G RAN i investigated FLex-RAN. Flexor and controller is an implementation of near real time RIC. If you want to manage the schedule then control or manage the CU or DU. For southbound there is a embedded agent within the source code for enode gnode B. To perform near real time operations on open interface. Available under Apache 2.0 license.
It is a brief description of what we can do with Flex-RAN. If you need it we could organize a presentation for the F2F
Action / Farheen put this back on the agenda. In terms of licensing we can set up parallel meeting times.
Thoralf Czichy proposes that near-RT RIC platform functionality (content) freeze is Feb-7. This is as there's a near-RT RIC platform contributor planning f-2-f workshop planned Feb-3 to Feb-5. Bronze Timeline doesn't have an exact date (drawing suggest in week of Feb-3 to Feb-8). Preliminary content is here: filter10401.
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.
we need better coordination with the test focus group in O-RAN. I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.
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.