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.
Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms. VES collector will display the alarm list.
Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
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 and what they plan to deliver in Bronze release.
Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
Action/ PTLs update Architecture pages.
Standing Agenda Items (Brief Status of Ongoing Activities)
note that from traffic steering epic/use case I did not see any use cases that fit to the near-RT RIC platform
multiple meetings related to health check epic subitems still be created in JIRA related to E2,A1,O1 health check and related to self-monitoring and alarm management.
what is this item about (from Bronze spreadsheet): "RAN NE to support Dynamic Data Collection (DDC) Measurement Intervals"
WG1 are correcting a list of demos for MWC compared to last year there were 6 demos. This year we have collected 16 demos.
2 demos are related to SC.
A1 PoC
Edge Cloud Platform (AT&T and Nokia). Release A is demonstrated in this PoC.
Jun Song (Samsung) has a demo to offer for the RIC platform.
Submitted to WG3 video for Network slicing.
For MWC PoC. Next Monday there will be a gate to review the PoC.
Feb 25 9:30 - 10:45 event Dutch Telecom will have a briefing. In an auditorium with 200 seats. Agenda will have the key chair of O-RAN Alliance, Dutch Telecom Executive, China Mobile Co-Chair (Jinri).
O-RAN Alliance F2F Feb 17-21 (Paris)
Do we have the schedule on the web site so people know when our meetings are.
For the TOC will be Tuesday and Thursday evening in Paris. Those are two sessions.
ONES = LF Networking Conference in April (Los Angeles).
2020-02-03 deadline for proposals. Planning on having a small kiosk or booth for demos.
Next weeks meeting is the deadline for raising interest. Talk to you companies and teams and reach out to Jinri and Jack and let them know what your interests are. We have to decide how much we want to participate.
It will have ONES participation. Including Akraino and ONAP. We need EC to be aware of this event to enhance this collaboration. It is a smaller event to have more interaction.
Look for feedback between now and next week.
Action/ Farheen add this to next weeks agenda.
Action/ Farheen ONES. Correct the entry for LF Networking event to LF. Networking: Open Networking & Edge Summit (formerly Open Networking Summit) .
Status of Open Action Items (Old Business)
Action/ TOC voting members: Provide an alternate contact on theTOClist above.
Action/ Farheen get Masafumi's backup from Jack.
Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance. This is an architectural review of fitting the code.
First meeting with Christian and his counterparts was held last week.
E2 traffic steering model needs to be approved by WG3. O-CU and O-DU handoffs won't happen until the Cherry release. Another is healthcheck.
Is this advancing the software and moving the community forward?
Concern that we may have to add another use case to develop another aspect of the software. How much do we advance in each release. One thing that blocks should not prevent us from moving forward.
Hampered by the O-CU O-DU profile timeline alignment with OSC is tricky. They have their timeline already that doesn't align.
Can we enrich the use case around some other functionality that is advancing.
O-CU and O-DU have to step up and what value they can add.
Can we develop a better set of detailed and expanded data so we can have a complete set?
How complete of data collection can we do in this release.
Steering use case. Cu and DU should implement the E2 interface. There were attributes and KPIs identified for modules. That document needs to be reviewed so that it is clear to CU and DU.
We need to see how we can get the data into CU and DU but we don't have SMO support for that.
Challenge is getting the data out of those devices at performance levels. First step is to acquire it and manage it. The next step is to deliver it to the upstream layers.
We don't have any in 01 or ONAP or SMO to do real time PM. We need to get leverage against ONAP and O-1 team to define those interfaces in support of non-RT RIC. Or we do that work ahead of specs which leads to problems.
Get that proposal.
Rittwik - O-DU and O-CU teams have to get together for the traffic steering use case.
Sachin - Call flow is not listed for a simple traffic steering use case. As a first step we should look at a simulator based approach. Simply simulate the use case and then the CU and DU can adopt that simulators results.
The use case lists KPIs but doesn't list which one is for CU and what is DU. The document we have today is an extensive list of KPIs to use and how training will take place. We don't know how to get it to the SMO. We don't need to use ONAP for now.
Jack asking the team to figure out how best to advance these features in the B release. Expecting O-CU and O-DU to support the other healcheck use case. Expecting a minimum software element with O1 communication. The team can decide how extensive it is. Second use case know that we've deployed every element in the stack and validate that it is running. This is a necessary first step to deploy all the pieces.
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.
We had a meeting with CM, Radisys, Intel
Rittwik has not heard back about simulator.
Call to community: What are we doing about a UE simulator.
Rittwik - we can have one or two cell phones. But not sure that is possible in bronze release. You have to have many UEs in multiple cells. It's OK to do unit tests but to test in full force we have to do it with a simulator.
Martin Skorupski will use cell phones instead of a simulator for Bronze release.
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.
Action/ O-CU and O-DU PTLs and RSAC to get together regarding the end to end steering use case jeopardy.
Action/ Community to address the UE simulator jeopardy on this TOC call.
Action/ PTLs enter epics from Contributions into jira.
Thoralf - see section 8c below. This will happen next week to discuss. Having trouble with the traffic steering use case. Don't see how the traffic steering use case fits with near RT RIC. Healthcheck of the different interfaces will be entered this week into jira. We will have a list on the meeting after next week.e
Matti - Use case details are evolving.
Sachin - Expecting Jira stories to be in Jira by next week.
Zhimin - Yes we put the O-DU tasks in Jira.
Lusheng - discussed at the end of last release. Issue is to compilation in LF. The licensing is different. We will need some legal council on this matter.
Martin - Common data models from WG4 and how to make it available for the software community. We want to continue what John Keeney did called an SMO that can be deployed. What the SMO should look like.
Focus on what the distribution of an SMO will use for our work in Bronze and then we will update it for Cherry. Lusheng and team for integration and the O-RAN test community. When you listed the alarms, is that the same as all the error messages? Software will generate error messages but we don't gather that info.
If they report according to the ONAP standards then VES collector will display the alarm list.
Each piece of software needs to gather their alarms and be documented.
Yes. that is in my proposal.
Every PTL come up with a list of alarm names, and document it. That can be translated to VES message formats.
Jack asking people to use spreadsheet.
Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.
Speaking to Chris Lott about portal and dashboard discussion.
Alex - Simulator project will have epics.
Jack - We need to know what Simulator is focusing on.
Xiaohua - Epics are in jira. Trying to finish by the end of next week. Community members can read up.
Wei Chen - no epics
John K. - Traffic steering functionality at the SMO level is happening. Getting closer to entering but needs more time.
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 and what they plan to deliver in Bronze release.
Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
Action/ PTLs update Architecture pages with the Bronze release features they plan to deliver.
Standing Agenda Items (Brief Status of Ongoing Activities)
note that from traffic steering epic/use case I did not see any use cases that fit to the near-RT RIC platform
multiple meetings related to health check epic subitems still be created in JIRA related to E2,A1,O1 health check and related to self-monitoring and alarm management.
what is this item about (from Bronze spreadsheet): "RAN NE to support Dynamic Data Collection (DDC) Measurement Intervals"
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.
Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms. VES collector will display the alarm list.
Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
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 and what they plan to deliver in Bronze release.
Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.