Table of Contents
2020 12 16
Recording: 2020-12-16_toc.mp4
...
Call for Scribe (minutes owner): Thoralf Czichy
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
X
Lusheng Ji
Jinri Huang Co-Chair
X
Weichen Ni
David Streibl
Ondřej Hudousek
John-Paul Lane
X
John Keeney Masafumi Masuda
X
Anil Umesh
Juha Oravainen
Thoralf Czichy X William Diego
X
Vincent Danno
Ganesh Shenbagaraman
Sachin Srivastava Sphoorthi Dayanand (Radisys) standing in even if not listed here. Jack asked her to coordinate with Ganesh if there's an updated name here. Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // Yes, we have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Motion by Thoralf, second by Jinri. No objections. 2020-12-09 minutes approved
- Review of Today's Agenda.
- Release Votes and Approval.
- Cherry release status
- All code has been branched. Tar ball already created and included in release page. All docker containers have been released. Ready. Most projects have updated their documentation. Felix working on "getting started" page. tar ball and getting started page link is available on Cherry page: Cherry Release (Dec 2020)
- Discussion on documentation
- Jack: Is it clear where to ask questions? Felix proposed that the integration team acts as contact as well as the PTLs of the individual subprojects.
- Jinri is working on blog/press release, but seems not yet approved by EC, but plan is to get it released today in the blog. Still discussion related to quotes from Radisys and WR (Gil H. asked about this in the meeting). EC makes final decision and we might not include quotes from everyone in every release to balance this out. Jack trying to see what EC policy on this is. Jinri also provided number of source code commits to EC.
- Thoralf commented that the Dawn timeline needs an update for the week numbers and, e.g., Feb-3 should be Feb-1 (as that's a Monday). Jack will fix.
- Q: there seems to be still changes? Felix confirmed that documentation and binary artifacts (tar balls, and release images) are fixed and available.
- Jinri: What is the official release data for Cherry? Jack: depends on what you want to call it. Press release date vs last artifacts uploaded (Tue, Dec-15 confirmed by Felix): We decided on release date as Dec-15-2020. Jinri will update PR accordingly.
- Cherry release status
- Copyright update.
- Copyright permission proposal to be approved by O-RAN EC.
- Jack: shared the proposal to TOC members. Action point: TOC members Please review copyright permission proposal and provide feedback and setup a meeting with Jack to discuss if needed
- 2020-12-16:
- Jack shared with TOC members the draft (last week). There's an update to the draft, which Jack will send out (post-meeting update: this was sent about 10min after the meeting). Refinements happened based of comments by some member (separating code and documentation). Word "copyright" added to the title.
- John-Paul asked for purpose of separating code and documentation. Jack: seemingly because they (the licenses) are structured differently. John-Paul might still send comments to Jack.
- Jack says he hopes this to be acceptable to 3GPP as well. But Jack not involved in 3GPP discussions.
- Jack hopes for end of January this being finalized and posted by O-RAN alliance, e.g., visible under the same page as the other "o-ran.org/software" page talking about licenses.
- Copyright case to be resolved with 3GPP.
- Copyright permission proposal to be approved by O-RAN EC.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- WG1 MVP proposal by early December.
- OSC Cherry blog post and PR
- Gu Su has draft PR
- PoC on Dec 3.
- 2020-12-16: Re-election in O-RAN EC. The one going out is also sitting in O-RAN-SC TOC as well. We might have to talk about O-RAN-SC TOC composition.
- need to go back to our charter.
- we might want to do elections and work on this in the beginning of next year.
- 2020-12-16: MVP (minimum viable product) was discussed as well in EC. We need to pay attention to that plan. 2021 will be a critical year. For example, OCU being important. More participation is needed. More companies. We do have a challenge around the integration team, also on SMO side. We do need a PTL for the integration and test project ideally with five participants and better alignment with test focus group on O-RAN alliance side. Dawn will need an improvement in this area, also because use cases become more complex.
- 2020-12-16: once we come back next year we need to produce a session (middle/end of Jan) for O-RAN alliance to show what we achieved in Cherry and look for their feedback.
- Rittwik: traffic steering and network slicing was discussed in earlier O-RAN - O-RAN-SC virtual face-to-face, but unsure what actually makes up the MVP
- Jack promised to set up a call, probably part of Rittwik's architecture sessions.
- Jinri: end of Jan or beginning of Feb is next virtual f-2-f on O-RAN alliance side.
- key is to make sure what we aim for in Dawn and "E" release.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- New O-CU PTL onboarding.
- Binary version of Radisys O-CU.
- Radisys legal document to be sent to Jack and Jinri in week of Nov 30.
- 2020-12-16: Ganesh sent the agreement to Jack and Jinri. Jinri to forward this to Stefan and follow up with Stefan to get this finalized. Use of a binary as a test fixture for OCU. Still a challenge to get an OCU implementing the O-RAN alliance interfaces.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- PTLs to keep summary page for Cherry release current and up-to-date.
- 2020-12-16: Close this
- Dawn Release requirement
- 2020-12-16: still open
- "E" Release naming.
- "E" Release voting ongoing.
- 2020-12-16: Jack proposed to continue with only letters. To remove any possibility of potential negative associations with colors in the diverse cultural backgrounds we operate in.
- CII Badging
- Action Point PTLs to go through the questionnaires to know gaps by Jan 2.
- Liaison with Security TG to be set up.
- Cooperation with ONF, OAI and ONAP.
- ONAP alignment to be discussed.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Zhe Huang (Felix) Integration and Test
- Decision: Move by Jack , second by Jinri. No objections. Felix approved as a committer to it/int, it/otf and it/test repositories
- O-DU low contributions. Action point Felix please resolve with Trishan
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
- This week will be the last TOC meeting of the year and we will continue on January 6th and begin the process for Dawn release. Juha will be scribe of Jan 6th meeting
- Next meeting: January-6-2021
- Tracy: not sure if press release will include reference to proof-of-concept. But note that PoC included WG1 November train output. Jinri to close out the press release.
- This week will be the last TOC meeting of the year and we will continue on January 6th and begin the process for Dawn release. Juha will be scribe of Jan 6th meeting
Meeting Summary (resolutions, new action items, etc.)
...
Call for Scribe (minutes owner): Juha Oravainen
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
x
Weichen Ni
David Streibl
x
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
x
Thoralf Czichy William Diego
Vincent Danno
Ganesh Shenbagaraman
x
Sachin Srivastava Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by Juha, second by John-Paul. No objections. 2020-12-02 minutes approved.
- Review of Today's Agenda.
- Release Votes and Approval.
- Cherry approval vote on Dec 9.
- Cherry release status
- Felix presented O-RAN Cherry Release Integration and Testing readout: Cherry-release-readout.pptx
- Felix presented highlighted use cases
- Rittwik: Use cases are ok from RSAC point of view
- Felix: Delivery Status Overview
- Release recommendation is green for all the other projects except for Integration/OTF, OAM and O-CU
- Jack:How many use cases did not get validated at this point?
- Felix: Use cases highlighted by RSAC are all validated
- Rittwik: Within the realms we have in open source we have got it to make it work. If the component doesn't exist, we can't make the full stack work.
- Jack: And it is documented what works and what doesn't?
- Rittwik: Yes
- Jack: Is there anything that has the light green tick, which won't be completed by Saturday
- Felix: No
- Jack: Let's see red boxes, O-CU clearly is not being released as part of Cherry release. Does anybody has any concerns to exclude O-CU from the release?
- Decision: O-CU is not supported in C-release, no objections
- Integration/OTF
- Felix: My proposal is to defer OTF Framework to Dawn release because OTF Helm charts needs further integration
- Jack: Do we defer this to Dawn or can we complete this in maintenance release? Does this require new code?
- Felix: New code is needed but is doable by the end of January 2021
- Jack: Proposal is to acknowledge that OTF Framework has some defects and will be postponed to maintenance release. Does anybody has any concerns with this?
- Decision: OTF has been postponed to maintenance release, no objections
- OAM
- Jack: EC raised some concerns how dependant OAM is from ONAP
- Tracy: This will be discussed on Friday TSC meeting.
- Jack: We are trying to find the right path through this and make sure both communities get what they need and move forward
- Felix: OAM contains EPL-1.0 license. LF can't exactly identify which pieces of the code is under this license and they raised a question how code is downloaded from the upstream project? Could we use Apache-2 license instead?
- Jack: Who will resolve this question because we can't release that particular repository until we get this resolved?
- Martin: My proposal is not to release this part of the code
- Tracy: I'm optimistic that this issue will be solved but not in this release
- Jack: Proposal is not to release this part of the code
- Jack: Two actions. 1. To remove TR69 part from the release and 2. to address the licensing issue
- Felix: Most of the OAM code is in ONAP repositories. All container images and Helm charts are contributed to ONAP. My biggest concerns are that there is no source code in OSC, binaries are pointing to ONAP projects, platform integration and deployment are done through ONAP OOM, there are challenges in releasing E2E flows due to data model licensing issues (3GPP) and it is hard to recreate E2E flows in OSC labs. I need guidance from TOC on release strategy
- Jack: There is minimum ONAP build you use. How many components you are using?
- Martin listed the components
- Rittwik: Why don't you fork the code?
- Martin: I don't need to fork it because all the functionality is already existing and the problem is that we are now in the level and working more closely with ODL teams and we are now moving more from ONAP towards ODL. I'd not like to fork ODL.
- Mahesh: SMO has also lot of dependencies and I'm not sure why we have SMO project?
- Jack: OAM and non RT-RIC are very big components of SMO. If there is no code in OSC repos then there is nothing to release. We need to continue this discussion and figure out what is the best way to continue the structure of this work going forward
- Jack: In Cherry there is no code or processes in OSC Cherry that need to be released for OAM?
- Martin: There is something for YANG validation. One repository and one folder
- Jack: There will be a minimum OAM released and documentation needs to be setup that way. The bigger issue is how this should work over time.
- Tracy showed a slide, which was prepared for O-RAN TSC: Attachments - Use case demonstration - OAM - Confluence (o-ran-sc.org)
- Jack: We are going to release Cherry. I make the motion to approve C-release, exclude O-CU, footnote OTF that it will be corrected in maintenance release and OAM will be minimised to repositories to support SMO. Does any TOC members have any concerns with this path?
- Rittwik: Which Yang model we are using in open FH?
- Martin: We can release like in B-release
- Decision: Move by Jack, second by Jinri. No objections. C-release approved with exceptions
- Cherry release status
- Cherry approval vote on Dec 9.
- Copyright update.
- Copyright permission proposal to be approved by O-RAN EC.
- Jack: shared the proposal to TOC members. Action point: TOC members Please review copyright permission proposal and provide feedback and setup a meeting with Jack to discuss if needed
- Copyright case to be resolved with 3GPP.
- Copyright permission proposal to be approved by O-RAN EC.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- WG1 MVP proposal by early December.
- OSC Cherry blog post and PR
- Gu Su has draft PR
- PoC on Dec 3.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- New O-CU PTL onboarding.
- Binary version of Radisys O-CU.
- Radisys legal document to be sent to Jack and Jinri in week of Nov 30.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- PTLs to keep summary page for Cherry release current and up-to-date.
- Dawn Release requirement
- "E" Release naming.
- "E" Release voting ongoing.
- CII Badging
- Action Point PTLs to go through the questionnaires to know gaps by Jan 2.
- Liaison with Security TG to be set up.
- Cooperation with ONF, OAI and ONAP.
- ONAP alignment to be discussed.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Zhe Huang (Felix) Integration and Test
- Decision: Move by Jack , second by Jinri. No objections. Felix approved as a committer to it/int, it/otf and it/test repositories
- O-DU low contributions. Action point Felix please resolve with Trishan
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
- Next week will be the last TOC meeting of the year and we will continue on January 6th and begin the process for Dawn release. Juha will be scribe of Jan 6th meeting
Meeting Summary (resolutions, new action items, etc.)
- Decision: O-CU is not supported in C-release
- Decision: OTF has been postponed to maintenance release
- Decision: Approve C-release, exclude O-CU, footnote OTF that it will be corrected in maintenance release and OAM will be minimised to repositories to support SMO
- Action point: TOC members Please review copyright permission proposal and provide feedback and setup a meeting with Jack to discuss if needed
- Decision: Felix approved as a committer to it/int, it/otf and it/test repositories
- Action point Felix please resolve O-DU low contribution issue with Trishan
...
Call for Scribe (minutes owner): Juha Oravainen
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
x
Weichen Ni
David Streibl
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
x
Thoralf Czichy William Diego
x
Vincent Danno
Ganesh Shenbagaraman
Sachin Srivastava x Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by Masafumi, second by Jinri. No objections. 2020-11-25 minutes approved.
Review of Today's Agenda.
- Release Votes and Approval.
- Cherry approval vote on Dec 2.
- Jack: Rittwik, how is the documentation and preparation work for the C-release proceeding?
- Rittwik: Documentation is coming through and we are identifying some Dawn use cases
- Jack: Where in the Wiki is the documentation?
- Rittwik: We can put the pointers from the regular SW dev page to integration page
- Jack: This should be put to Cherry release page. Introduction, how to get started, where to get SW and other relevant documentation/links should be found from Cherry release page
- John: Every project has their own documentation. Please add these links to documentation page
- Jinri: Do you need help in documentation?
- Rittwik: Yes, I'll contact to Weichen
- Jinri: Please copy also me when you contact Weichen
- Jack: We have only 10 days left before release date, which is Dec 12th. We are not ready to vote yet but everything needs to be done by next week's TOC meeting
- Integration and Test status, please see chapter 9c below
- Cherry approval vote on Dec 2.
- Copyright update.
- Copyright permission proposal to be approved by O-RAN EC.
- Jack: Proposal got from the legal team and this will be discussed on Friday how to proceed and after that we start sharing it. Expect me to start to reach out at the beginning of next week with a copy what we are proposing and setting up meetings.
- Jack: Anyone who is interested in reviewing the copyright statement, please let me know.
- Jack: This should cover all of the O-RAN original copyrighted material but it does not address 3GPP copyright items
- Copyright case to be resolved with 3GPP.
- Jack: This work is done by standards group. We have some inputs to the process and tracking it but they are the one who are leading the work with 3GPP
- Copyright permission proposal to be approved by O-RAN EC.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- WG1 MVP psoposal by early December.
- OSC Cherry blogpost draft submission by Dec 2.
- Jinri: We are working with the blog post. We already got input from Rittwik but we need still input/highlights/summary from projects.
- Jinri: We need also short descriptions to highlight key features from each project. This is mainly for PR
- We need also quotes from the contributing companies to PR. So far we have input from WR, Nokia and Ericsson
- Jack: Cherry release date is 2020-12-12
- Jinri: Deadline for inputs is this Friday as there will be EC meeting next week
- PoC on Dec 3.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- New O-CU PTL onboarding.
- Binary version of Radisys O-CU.
- Radisys legal document to be sent to Jack and Jinri in week of Nov 30.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- PTLs to keep summary page for Cherry release current and up-to-date.
- Dawn Release requirement
- "E" Release naming.
- "E" Release voting ongoing.
- CII Badging
- Action Point PTLs to go through the questionnaires to know gaps by Jan 2.
- Liaison with Security TG to be set up.
- Cooperation with ONF, OAI and ONAP.
- ONAP alignment to be discussed.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Zhe Huang (Felix) Integration and Test
- Jack: we need more people in Integration and Test project in D release. One person really can't do all this stuff.
- Felix: Cherry Release Testing Plans: Cherry Release Testing Plans - Integration and Testing - Confluence (o-ran-sc.org) Here you can find all the flows what we want to test
- Felix: near RT-RIC has some new flows
- Thoralf: In the worst case scenario we can't test all of these
- Jack: Please make sure and say what flow is approved and part of the release and what isn't
- Jack: It is important to map use cases and e-2-e flows we are testing
- Rittwik: There is not one to one mapping
- Jack: It doesn't have to be but there should be a place where we can see which work flows support which use cases
- Felix: Some part of the non RT-RIC code is contributed to ONAP, which means we need to use artifacts from ONAP
- John: I see no problems here as code is copied from ONAP and re-released via OSC + both releases use Apache-2 licence. So, licenses are compatible
- Jack: This is ok from open source point of view. The only question is, if they make changes to that code we are referencing in OSC and it breaks our downstream usage. PTL and the team is responsible to make sure it builds and works properly and delivers it to Integration and Test project
- David Kinsey: Why can't we use the boundary or container of that it is part of ONAP?
- John: There are several possibilities but we see this the most feasible and flexible option at the moment
- John: We can use the code in two different projects
- Felix: There is "Copyright 2020 Nordix Foundation" license headers in some non RT-RIC code
- Jack: They are granting this code contribution under the Apache-2 license. That's the key, not who does it but what license they are doing it
- Jack: has the license scan been run yet by the Linux Foundation
- Felix: not yet
- Trishan: I will follow this with Steve
- Jack: we need to run this before we release the code
- Felix: I'm pretty happy with the code but have some concerns with OAM. I will contact Martin off-line
- Jack: what about SMO?
- Felix: My opinion is that tests have passed
- Rittwik: What about SIM and O-CU projects?
- Felix: SIM project is contributing code directly to non RT-RIC code
- Felix: I have also concerns with O-CU but currently I don't have any flows that needs to be tested with O-CU
- Rittwik: How do we address O-CU, definitely for Dawn. And what do we do in Cherry
- Jack: currently we are using Radisys O-CU binary code as a test fixture
- Jack: As far as I know, the code is contributed but there are no test use cases currently that leverage O-CU. Code sits in the repos but we are not using it in integration or e-2-e flows with that code and we should in the documentation call that in that way
- Jack: the key issue is that we have still quite a lot of work to do in the coming week. Rittwik: you are working with Weichen on the documentation project and Felix is working with different teams to validate the remaining flows. And there is the scanning for the SW
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
...
Call for Scribe (minutes owner): Masafumi Masada
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
x
Weichen Ni
David Streibl
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
Thoralf Czichy x William Diego
x
Vincent Danno
Ganesh Shenbagaraman
x
Sachin Srivastava Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by Masafumi, second by John-Paul. No objections. 2020-11-18 minutes approved.
Review of Today's Agenda.
- Release Votes and Approval.
- Cherry approval vote on Dec 2.
- Copyright update.
- Copyright permission proposal to be approved by O-RAN EC.
- Jack: O-RAN Legal Stefan is evaluating the proposals.
- John: Didn't we hope to have a written proposal you can share this week?
- Jack: We had a proposal we referred to last week and got an additional option last Friday. We hope to have a feedback we can share from Stefan early next week.
- Copyright case to be resolved with 3GPP.
- Jack: No update.
- Copyright permission proposal to be approved by O-RAN EC.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Jinri: There is no specific item to mention. MVP discussion is ongoing. There were several discussions with WG2 and WG3 last week.
- Jack: We are approaching US/Europe holiday season. We need to finalize focus points in "D" Release.
- Jinri: WG1 is expected to come out with a MVP proposal by the end of this month. We will get that early December at the latest.
- Jack: We want to have a plan by Jan 2.
- Jack: Last week, Tracy talked about PoC on Dec 3. No update on MWC LA.
- John-Paul: I have a question about OSC Cherry blogpost. Who is coordinating?
- Jack: It should be Jinri.
- Jinri: I can help with this.
- John-Paul: Is there a deadline for submission?
- Jack: We need it by next Wednesday.
- Jinri: Do we also need to prepare a PR?
- Jack: We are doing just blogpost. We need to discuss in EC.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- New O-CU PTL onboarding.
- Binary version of Radisys O-CU.
- Rittwil: We haven't received yet.
- Ganesh: Our legal team is working on a legal document. Who will be the person to send it to?
- Jack: Me and Jinri. We will forward it to Stefan to review.
- Jinri: When can we expect to receive the document?
- Ganesh: Next week.
- Rittwik: We have configured fronthaul. Viavi RU emulator TM500 is being shipped and to arrive at the lab by Dec 4. We will do the radio mode testing for Dawn Release.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- PTLs to keep summary page for Cherry release current and up-to-date.
- Dawn Release requirement
- Jack: Any progress on documentation?
- Rittwik: We got some documents from ODU. We started a discussion on 2 new use cases. We are moving and good to go for January.
- Jack: I don't see Mahesh to provide SMO status.
- Rittwik: He has tested Yang models. He is working to finalize.
- Jack: Do you need any specific inputs?
- Rittwik: One thing from Viavi.
- Jack: We need to get our plan in place for "D" Release at the begining of next year.
- Rittwik: I will reach out to PTLs.
- John: We still need to work on A1-based use cases.
- "E" Release naming.
- "E" Release voting ongoing.
- CII Badging
- Action Point: PTLs to look at CII Badging requirements and pick up 1 or 2.
- Trishan: Next step is to create a child page.
- Rittwik: Each sub-projects will get a badge, right?
- Trishan: Yes.
- Rittwik: What's your guideline, Jack?
- Jack: We need initial assessment from each PTL going through the questionnaires to know gaps by Jan 2.
- Trisian: One item accross the projects is around security.
- Jack: O-RAN has a TG for security. We don't have a specific security comittee in the software comunity.
- Trishan: I would recomend to have a liaison.
- Jack: You can go ahead and set up.
- ONF update.
- John: I saw press releases saying ONF is contributing to OSC. What's the current status?
- Jack: There were meetings with EC and ONF in terms of alignment. Discussion has been around RIC, little on rApp and mostly on xApp.
- Rittwik: Discussion is moving forward. They are contributing to WG3.
- Jack: Challenge is to bring the 2 projects together and keep them aligned. It's an open discussion driven by EC.
- Gil: Is there a discussion to formalize an API into a spec?
- Matti: That's happening in WG3. ONF memebers have been there for a while.
- John: Are there any discussions touching O1 and rApp in WG2?
- Rittwik: Maybe it's beginning.
- Jack: There is a part that we can build in common to drive the concept, but we are not able to do that for everything.
- John: There seems to be a lot of Incentive to get alignment between OSC and ONF. No desire to have a similar alignment with ONAP?
- Jack: Let's have the discussion next week.
- OAI discussion.
- Jack: We continue dialogue about copyright and other points.
- William: They are trying to work on license agreement.
- Jack: Discussions are going on. Nothing acionable.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Zhe Huang (Felix) Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
...
Call for Scribe (minutes owner): Masafumi Masada
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
Weichen Ni
David Streibl
x
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
x
Thoralf Czichy William Diego
x
Vincent Danno
Ganesh Shenbagaraman
Sachin Srivastava Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by Masafumi, second by David. No objections. 2020-11-11 minutes approved.
Review of Today's Agenda.
- Release Votes and Approval.
- Jack: We are approaching the time when we will take a vote on approving Cherry. We are going to do some work to be ready by the final approval date of Dec 2. After releasing, we will move on to a blogpost and press release process.
- Tracy: Jus a reminder, we are doing a Proof of Concept on Dec 3.
- Copyright update.
- Action Point Jack/Jinri: Check approval to use O-RAN ASN.1 by OSC with O-RAN legal to clarify what spec. version it relates to. Also, a similar case to be resolved with 3GPP.
- Jack: We met last week and have a written up proposal for approval by EC. It doesn't address 3GPP, but at least O-RAN SC .
- John: What is the proposal?
- Jack: The proposal is to grant a copyright permission to the Software Community for the O-RAN specifications. It has nothing to do with patent or IPR.
- John: I'm not sure it's applicable for code, models, specs and documents.
- Jack: My understanding is that all those items are protected under copyright. That's what legal discussions are about.
- Juha: Is there a draft version our legal can read through?
- Jack: We will get a feedback this Friday. Let's have our legal team review first.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Jack: Tracy has already mentioned Dec-3 PoC.
- Rittwik: There is MWC LA. I can send it to the email.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- Jack: The new PTL Su Gu is not on due to the time difference. We might have to set anotehr time.
- Rittwik: Ganesh is figuring out the binary version of Radisys O-CU.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- PTLs to keep summary page for Cherry release current and up-to-date.
- Cherry Release cut-ff.
- Jack: Cut-off date is November 14th.
- Mahesh: SMO missed the deadline, but the demo is ready.
- Jack: Please work with Rittwik and Felix to set up a demo time and process the other steps.
- Vidhu: ODUHIGH missed the deadline, but the code is ready.
- Felix: No problem.
- "E" Release naming.
- David: I sent a link of voting page via email.
- Jack: There is an unintentional correlation between colors and derogatory meanings. We need to remove Ebony and vote again.
- Action Point "E" Release voting.
- ONF update.
- OAI discussion.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- CherryTimeline
- Jack: We need to finalize documentation.
- Rittwik: OK.
- Jack: Felix, what do you need?
- Felix: I need details from each team how to verify the use cases and test flows.
- Jack: The goal is by Dec 3 meeting to have everything approved.
- Felix: It's durable.
- Jack: Please prioritize and support Felix. Trisian, I will get you involved in blog write-up.
- Trisian: Sounds good.
- Jack: How are we getting ready for "D" Release requirement?
- Rittwik: Making progress. We need to get more integrated. That's our challenge for Dawn.
- Jack: The key part is how lifecycle management can deploy the functions.
- Rittwik: The step 2 and 3 of the 4 steps are being done in Cherry.
- Jack: We need process in place.
- Mahesh: I understand.
- Jack: Even if it's not full production ready, at least the initial deployment.
- John: A lot of functions needed just to get the first use case working.
- Jack: We need to make some progress. Rittwik, do we have a roadmap?
- Rittwik: We still need particular use cases.
- Jack: Write up the whole scenario. We need to make sure these plans are laid out.
- Rittwik: We've been working mainly on the user plane.
- Jack: Make sure that the goal and how we make progress to that is clear.
- Rittwik: Use case is very high level. There is a gap OSC is trying to fill.
- Jack: The real item is what needs to be specified and what needs to be implementation. Let's continue the discussion.
- Jack: We need to think about hand-off for "C" Release. We want to invite WG groups and do a demo in January. Based on the "D" Release schedule, the 16th is the last meeting in 2020 and we are going to resume on Jan 6.
user-59b16 Requirements Software Architecture Committee
Action Point PTLs to look at CII Badging requirements and pick up 1 or 2.
- Rittwik: Trisian has created a link.
- Trisian: It's in Best Practice. There are 64 questions.
- Jack: The key thing is to get people go thorough.
- Trisian: It's a good practice.
Zhe Huang (Felix) Integration and Test
- Action Point Felix and Zhimin to work together to resolve issue of ICC Compiler access. (Not a barrier to complete Cherry.)
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
...
Call for Scribe (minutes owner): Masafumi Masada
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
x
Weichen Ni
David Streibl
x
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
x
Thoralf Czichy William Diego
Vincent Danno
Ganesh Shenbagaraman
x
Sachin Srivastava Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by Masafumi, second by John-Paul. No objections. 2020-11-04 minutes approved.
Review of Today's Agenda.
- Release Votes and Approval.
- Jinri: There was a request on new repo.
- Thoralf: On libe2ap repo.
- Jack: Who made the request?
- Thoralf: My request, I would suggest to vote now,
- Jack: Do you keep creating several repos for segments?
- Thoralf: This is a special case.
- Jack: As a general guidance, try not to create a repo each time. We'll go ahead with this case.
- Decision: Move by Jack, second by Jinri. No objections. New repo "o-ran-sc/libe2ap" approved.
- Copyright update.
- Action Point Jack/Jinri: Check approval to use O-RAN ASN.1 by OSC with O-RAN legal to clarify what spec. version it relates to.
- Jack: We had a meeting last Friday including O-RAN Legal Stefan and Scott Nicholas from LF. He has generated his blog being reviewed. Another topic we discussed is 3GPP copyright. I'm looking for an example of 3GPP specification we need copyright permission. We've made some progress on copyright for O-RAN Alliance. It will include copyright forward permission, meaning goal here is OSC permission. We are getting closer.
- Thoralf: That was a discussion with O-RAN SC and O-RAN Alliance. Do we still have a similar discussion with 3GPP?
- Jack; Correct. I'm less involved.
- Rittwik: Why is it such a difficult thing? We end up releasing anyway.
- Jack: The challenge is copyright is a thing that has to be enforced. We are trying to close the legal gap. We are trying to get a clarity around the right permission.
- John: I think it's time to push down.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Jinri: EC touched the copyright issue. Second thing is regarding MVP. MVP group is discussing with each WG co-chairs. That's the current status.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- Action Point planning for 2021 elections.
- Jack: We approved the new PTL for O-CU.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- Jack: PTLs, please keep summary page for Cherry release current and up-to-date.
- Cherry Release cut-ff.
- Jack: Let's see we can pull in the code by November 14th.
- "E" Release naming.
- Action Point David to start a poll for the naming of "E" Release.
- David: I will send an email.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Action Point Trishan/Rittwik to sync up on CII Badge passing.
- Rittwik: We had a meeting with Near-RT RIC. My request for PTLs is to look at requirements and pick up 1 or 2 items.
- Action Point PTLs to look at CII Badging requirements and pick up 1 or 2.
Zhe Huang (Felix) Integration and Test
- Action Point Felix and Zhimin to work together to resolve issue of ICC Compiler access.
- Felix: We had several meetings. The idea is that at the end of Cheery Release we should be able to deploy all the projects. We also talked about testing environment. There are multiple projects ongoing.
- Jack: How is the documentation going?
- Felix: I just get started. I need help from PTLs. That's about testng. Who is working on documentation?
- Jack: There is a documentaiton lead. You can reach out.
- Jinri: Weichen is working on this. I was suggesting him to give feedback or update in the next call. I can connect Felix to Weichen.
- Jack: The other item is license scan.
- Felix: Yes.
- Jack: How is the testing going with DU and use cases?
- Rittwik: DU-RU testing is moving ahead. Fronhaul server has already been installed. RU emulator TM500 is still getting installed. Checking with Viavi. DU-low - DU-high testing has happened to some extent. We are still waiting for Radisys to provide a binary version of CU. Once that comes in, we can hook up.
- Jack: Ganesh, are you aware?
- Ganesh: Yes. I should have update in the next meeting.
- Jack: How do we get it and pull into the documentation package so that other people can see?
- Rittwik: I can take the action.
- Jack: We usually create a link. We shoul also talk about what has been done and what is know to work.
- Rittwik: We have some slides.
- Felix: I will check with Integration team.
- Jack: Are you going to have a follow-up meeting?
- Felix: No. I'm going to reach out to indivisual teams.
- Jack: Has ICC Compiler access been resolved?
- Felix: No.
- Jack: Is that a barrier to complete Cherry?
- Felix: No.
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-Real Time RIC (RAN Intelligent Controller) (NONRTRIC)
- Rittwil: What A1 EI code is there? How will we test it using A1 simulator?
- John: That funcion has been delivered and being tested to be deployed in Cherry.
- Jack: You are expanding use cases.
- John: We had brain storming.
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
- Jack: How is SMO going?
- Mahesh: Copyright is one issue we've already discussed. LCM package work is going on. The team is working on pre-standard implementation. Work is going on.
- Jack: Do you think you'll be wrapping up something for "C" Release in the next few weeks?
- Mahesh: Yes. We should be able to demonstrate LCM and Yang model testing.
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
- ONF updae
- Jack: They came out with a blog about there are interested in aligning with O-RAN Alliance and with OSC. There is overall planning discussion going on. They are particularly interested in xApp APIs and software development kit. They built their own Near RT RIC. One of the objectives is to try to understand how we can build xApp. They will start joining the call. The goal is in time for Dawn Release.
- Rittwik: Are we creating a new project?
- Jack: We are trying to figure out. The goal would be common pieces. Deciding about what's upstream and what's downstream is part of the discussions. Principle right now is OSC would be upsteream activities. Our concern is how do they interoperate, test and do demonstrations utilizing things from O-RAN Alliance if you don't have any activities demonstrating alignment or compliance. ONF is interested in O-RAN compliance, but what does that mean.
- OAI discussion
- Jack: Christian is organizing OAI discussions. Challenge is that licensing is not compatible. We are trying to see if we can do something slimilar to what we are doing with Intel O-DU. There are a couple of additional meetings coming up.
- Rittwil: Say, we want to use O-DU from OAI, but OSC will build E2 adapter to talk to O-DU. Where would the E2 part be maitained?
- Jack: E2 should be built in OSC.
- RIttwik: We will just download from OAI?
- Jack: Just like we download Intel FlexRAN code.
- ONF updae
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
...
Call for Scribe (minutes owner): Masafumi Masada
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji
Jinri Huang Co-Chair
Weichen Ni
David Streibl
x
Ondřej Hudousek
John-Paul Lane
x
John Keeney Masafumi Masuda
x
Anil Umesh
Juha Oravainen
x
Thoralf Czichy William Diego
Vincent Danno
Ganesh Shenbagaraman
x
Sachin Srivastava Viswa Kumar
Kristen Young
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Decision: Move by John-Paul, second by David. No objections. 2020-10-28 minutes approved.
Review of Today's Agenda
Jack: Let's discuss release plan. The release date of "C" Release is Dec-12. We need to do test and license scan, to have documentation review in week of 23rd and to write a summary and pull together the package at the beginning of December. Any questions?
- Mahesh: Code freeze is supposed to be week 40. We need some extension for some projects. We don't have the final code in the repo yet.
- Jack: Is your case that large amounts of code that haven't been tested or looked at yet or is there some specific pieces of a bigger release? Your are talking about the except, right?
- Mahesh: Yes. We are hoping to get the Machine Learning version of the QP except in this release. The ML code is not in the repo yet. I will find out.
- Jack: We would like to see the code there as soon as possible. The question is how close it is. We need to bring the code into the repos so that we can start running scans and packing things up. Let's get an update this week.
- Mahesh: I will find it out in today's meeting.
- Jack: Who is the lead?
- Mahesh: An AT&T guy.
- Jack: Does any other PTLs have any outstanding items or concerns?
- Thralf: RIC Platform has a few items.
- Jack: How open are they?
- Thralf: We have 3 items on which review ongoing last week and 2 items to finish over the next few weeks.
- Jack: Let's see we can pull in in the next week and half before the 14th.
- Thralf: When do we expect is the date after which everything that goes in has to be especially managed?
- Jack: After the 14th, we need to cut it off.
- Thralf: I agree.
- Matti: Sounds good.
- Zhimin: O-DU - RU testing is still ongoing. I don't think we can make the 14th.
- Jack: The question is whether all the code is in the repo.
- Zhimin: That's fine.
- Jack: We need to make sure that we are bringing this to a point where people can start to donwload and use it. That's a big part of the goal.
- Jack: The schedule shows us starting up the 1st week of January for the "D" Release. We need to start talking about what's going to be in. Also, there is a maintenance window for the Cherry Release. David, maybe you should start a poll for the naming of "E" Release.
- David: OK.
- Action Point David to start a poll for the naming of "E" Release.
- Release Votes and Approval.
- None.
- Copyright update.
- Action Point Jack/Jinri: Check approval to use O-RAN ASN.1 by OSC with O-RAN legal to clarify what spec. version it relates to.
- Jack: I'm waiting for an email from Scott Nicholas at LF on the copyright blog. The goal is to articulate what 3GPP, ETSI and others might need to consider when supporting open source communities in what they need in terms of copyright permissions from their specifications. I was trying to use that as a way to give an assist these organizations with information on how the open source community looks at their needs for this issue to be addressed.
- John: It doesn't directly address the issue. It's getting close to the stage where we are going to have to consider stopping code contributions until we get this clarity.
- Jack: Understood. I'll highlight it again in the EC meeting.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
- Jack: LF re-published O-RAN blog post about Plugfest 2.
Status of Open Action Items (Old Business).
- O-CU development and O-CU for Cherry traffic steering use-cases.
- Decision: Move by Ganesh, second by Juha. No objections. Su Gu for O-CU PTL position approved.
- Beginning of April, we should be running an election cycle for renewing the elections for the key positions in the TSC as well as the PTLs. We want to have overlap, hand-off and preparation time for "D" Release. We have some issues in O-CU area to address. Going forward, hopefully Su Gu can help the dialogue move forward and we will make that decision at that time.
- Action Point planning for 2021 elections.
- Cherry deliverable summary page (see Cherry Release (Dec 2020)) . Update once a month and review on first TOC call of a month.
- Jack: PTLs, please keep summary page for Cherry release current and up-to-date.
- O-CU development and O-CU for Cherry traffic steering use-cases.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
Rittwik: We met with the Security Committee. They are requesting us to control CII Badge passing requirement. Each PTL needs to pick 1 or 2 items in the list for Dawn Release to fill out forms. Trishan can help coordinate the form filling and be responsible for what level of badging each project obtains. Pick up maybe 1 item for Dawn Release to avoid too much burden and more for "E" and "F" Releases. The only concern Security Committee has is continuity.
- Jack: We need a checklist saying which project has completed which tasks.
- Trishan: One way to maintain is to create a table with a check list on the O-RAN SC Wiki. I can take care. We usually do it at a main project (O-RAN SC in this case) not each sub project. Let me check.
- Jack: As a group, we need to focus on the threshold.
- Trishan: Rittwik, let's sync up off-line.
- Action Point Trishan/Rittwik to sync up on CII Badge passing.
- Jack: How are we on track for getting early work done on the "D" Release requirements?
- Rittwik: We are aligned except traffic steering. They expect to have a service model by the March Train.
- Jack: What is the major control action on the each interface?
- Rittwik: Control action on E2.
- Jack: Is there a full loop on O1 and A1?
- Rittwik: There are some aspects of O1 that we are able to control. There are some models that are getting tight in the small project. The only control except is traffic steering. The others are directives.
- Martin: That's correct. Currently we get the alarm list and those kind of things. Most of the problem is that we cannot contribute based on the Yang models from 3GPP. That's what currently happens in O1. We depends on 3GPP that is one of the main issues.
- Jack: We need to take a look broader than just E2. We need to get a demonstrable system that exercises that full range of control for "D" and "E" Releases.
- Martin: That's already there since Amber and Bronze. What's missing is taking an action doing closed-loop or performance based.
- Jack: We completed them for at least O1. We need to look at the whole area so that everybody can see all the functionality of O1, A1 and E2.
- Rittwik: I understand your request. That also depends on the specs. What's your viewpoint on MVP?
- Jack: I agree with MVP bringing focus, but my concern is that we are focusing on such a narrow piece for each release. I want to make sure we are covering that around the 3 interfaces.
- Martin: What is necessary is that we exchange topology information of O1, A1 and E2.
- John: I agree. What's missing is a node in RAN producing some monitoring data we can use to drive use cases. I can't see that coming from simulation functions. Just alarm type of data coming up from PM would be useful.
- Rittwik: That's what we are trying to set the system up so that at least functional system is working. Without all the pieaces working, it's difficult to get any PM data. You don't have a full functional E2E stuck. I get John and Jack's point.
Zhe Huang (Felix) Integration and Test
- Action Point Felix and Zhimin to work together to resolve issue of ICC Compiler access.
Report out from PTL: Stand-Up & Report Out on Blockers
John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
Matti Hiltunen RIC Applications (RICAPP)
Thoralf Czichy RIC Platform (RIC)
user-a934b O-RAN Centralized Unit (OCU)
Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
Martin Skorupski Operations and Maintenance (OAM)
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
- Mahesh Jethanandani Service Management and Orchestration (SMO)
(TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
...