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.
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.