Table of Contents

2020 08 12

Agenda

Call for Scribe (minutes owner)

Roll Call & Quorum Check

Company	Contact Name	Alternate Contact
AT&T	Jack Murray Co-Chair	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Weichen Ni
Deutsche Telekom	David Streibl	Ondřej Hudousek
Ericsson	John-Paul Lane	John Keeney
NTT DOCOMO	Masafumi Masuda	Anil Umesh
Nokia	Juha Oravainen	Thoralf Czichy
Orange	William Diego	Vincent Danno
Radisys	Ganesh Shenbagaraman	Sachin Srivastava
Verizon	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
Review of Today's Agenda
Release Votes and Approval
Copyright updates
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.

2020 08 05

Agenda

Call for Scribe (minutes owner)

Roll Call & Quorum Check

Company	Contact Name	Alternate Contact
AT&T	Jack Murray Co-Chair	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Weichen Ni
Deutsche Telekom	David Streibl	Ondřej Hudousek
Ericsson	John-Paul Lane	John Keeney
NTT DOCOMO	Masafumi Masuda	Anil Umesh
Nokia	Juha Oravainen	Thoralf Czichy
Orange	William Diego	Vincent Danno
Radisys	Ganesh Shenbagaraman	Sachin Srivastava
Verizon	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
Review of Today's Agenda
Release Votes and Approval
Copyright updates
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.

2020 07 29

Agenda

Call for Scribe (minutes owner)

Roll Call & Quorum Check

Company	Contact Name	Alternate Contact
AT&T	Jack Murray Co-Chair	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	Weichen Ni
Deutsche Telekom	David Streibl	Ondřej Hudousek
Ericsson	John-Paul Lane	John Keeney
NTT DOCOMO	Masafumi Masuda	Anil Umesh
Nokia	Juha Oravainen	Thoralf Czichy
Orange	William Diego	Vincent Danno
Radisys	Ganesh Shenbagaraman	Sachin Srivastava
Verizon	Viswa Kumar	Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
Review of Today's Agenda
Release Votes and Approval
Copyright updates
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.

2020 07 22

Recording: GMT20200722-120257_Zoom2-O-RA_1920x1080.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair	x	Weichen Ni
Deutsche Telekom	David Streibl		Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Juha Oravainen	x	Thoralf Czichy
Orange	William Diego	x	Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 15 Jul 2020
  2. On motion made by Jinri Huang
  3. Seconded by John Paul Lane
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. ~~Action~~ / Farheen Cefalu add it to the top of the agenda next week. Do we create a new project called the SMO as described by the needs of the requirements committee?
2. ~~Action~~/ user-59b16 bring slides for the SMO project proposal.
Release Votes and Approval
Copyright updates
Marketing of the current release (WG, LF, PR)
1. Bronze Release PR
2. Virtual Exhibition
3. OSC Logo status
Status of Open Action Items (Old Business)
1. Action / Jack get the O-RAN teams perspective on Juha's concern whether Lusheng's 3rd party proposal is in line with the technical charters.
2. Action/ Requesting TOC to vote on allowing 3rd party code use policy
3. Action/ Jinri Huang ask Zbynek. didn't get a formal notification from Zbynek regarding copyright policy approval by the board.
4. Action/ Jinri Huang send Jack and Farheen Zbynek's official O-RAN approval.
5. Action/ Farheen Cefalu post on wiki and oran site.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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)
1. John Paul Will we take a vote on the 3rd party technical charter today?
2. No
3. There was an ACOP meeting IPOR how soon after a spec can the spec be used? How many days were required from when approved to when it can be used. 60 or 90 days? There is an action has the OSC been engaged.
4. Not engaged.
5. There is a question from when the working group approves there is a 3 month delay before it can be exercised.
6. The company that owns or contributes it is their responsibility. Once it becomes a part of the O-RAN specification it begins after board approval. Is it 60 - 90 days after the board?
7. Yes, after the board approves there is an 30 day delay. This may impact on the OSC so the OSC should be involved with the conversation.
8. Jinri: I am aware. Which meeting are you speaking about?
  1. John Paul It was an ACOP meeting.
  2. Jinri: During the board meeting last month after the TSC submits. Before board approves they will request the O-RAN legal review to allow companies to review their IPR status. They will decide on options for royalties. The 60 days allows the companies to review their IPR. After 60 days an additional 30 days to allow O-RAN to publish. For OSC this will not impact us. Even with the specification we can get some approval from EC for copyright.
  3. Jon Paul In he ACOP said that there may be impacts to OSC.
  4. Jinri: There is possibly some risk here. During the 60 days some company claims an IPR. But what if during that period the OSC has implemented the spec with the IPR.
  5. Jack: We will continue that clarification moving forward.
Copyright updates
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
1. Action / Jack get the O-RAN teams perspective on Juha's concern whether Lusheng's 3rd party proposal is in line with the technical charters.
  1. Lusheng sent out an email with multiple requests. He removed the license vote from the most recent
2. ~~Action~~/ Jinri Huang ask Zbynek. didn't get a formal notification from Zbynek regarding copyright policy approval by the board.
3. Action/ Jinri Huang send Jack and Farheen Zbynek's official O-RAN approval.
4. Action/ Farheen Cefalu post on wiki and oran site.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
  1. SMO for Cherry Release: Cherry SMO (with future items in rel D "Dawn" or beyond)
    1. Jack - this is a project. Continue the OSC journey to bring enough code to bring a minimum viable product and position so that companies can take it and commercialize it. The intent is not to make a commercial SMO for people to pull and use instead to make it functional so people can demontrate. We should not want to fork code or duplicate code. We want to recognize during development in case of ONAP it is hard to synchronize with upstream projects. There will be a pull/push of code in order for people to see progress. We are not going to name a PTL today. We will establish a project first with a range of companies to demonstrate of pulling together an O-RAN system that shows functionality and progress.
    2. Jack: Should SMO be ONAP based or other project? The community should decide by where and how it contributes. We are asking for an SMO based project. If we want to create a project that is MANO focused then let the community drive what are the options. We are doing that in the DU LOW. The community should decide and evolve. For today we are talking about an SMO that is ONAP focused. I recommend to create them as two separate projects with two PTLs.
    3. Jinri: Currently OAM project is focused on O1 interface. SMO is focused on O2.
    4. Jack: The Non Real time RIC is 15% of what SMO should be. OAM is larger but combined they are far less than 50% of what the SMO is going to be. There are catalogs and ML that can not be addressed by either OAM or NonReal time RIC. There is a whole series of items that will be pushed into revision control that goes into Life Cycle Management (LCM). If something else becomes a subcomponent we will consider splitting it out to allow ease of development.
    5. Rittwik: Outside of the bounds of the NONRT RIC have to be in scope of another project such as SMO.
    6. John Keeney: We need to be very clear about the scope of the overlapping projects. We can't come to agreement of in the Alliance either. If you look at the scope suggestions for NONRTRIC we will need to change. We need to define what is and what is not in scope of NONRTRIC. I would like to ask for ideas of how we clearly define the scope?
    7. Jack: The process defines that there is another side and define what that boundary. Doing it one sided complicates. That is why we need the SMO project to work through that discussion. SMO will not work overnight. We need to work the project and work down those discussions. The truth is we need to move forward on making and demonstrating a larger working environment and figure out way to do that. We have been discussing for three weeks. Rittwik has brought a proposal. We need to go through steps to get this resolved through Dawn release. If the SMO becomes a big or small project that is yet to be determined. The intent is not to re-create the code. This is beyond the requirements of the integration and test team. Without the effort of the SMO we won't get a more functional.
    8. John Keeney: If we are agreeing that there needs to have a defined scope.
    9. Jack: Having an upper level in a stack requires a defined scope.
    10. John Keeney: As long as we understand there needs to be time dedicated to scope definition negotiation.
    11. Jack: This is a journey we've been on. I've noticed that multiple people creating different dashboards that will require technical debt to coordinate. That needs to be discussed.
    12. John Paul: I agree with Jack this is a journey.
    13. Gill: Should we agree where the functionality goes?
    14. John Keeney: That should be RSAC.
    15. Jack: There may be a technical change downstream that allows you to make a decision.
    16. John Keeny: You mentioned avoiding code duplication. How do we coordinate that?
    17. David Kinsey: you should have Jira tickets to track what is being planned. Documenting the capabilities and features is needed in order to coordinate through jira.
    18. Jack: We don't steer what ONAP does so we may not agree with their implementation. It has to work through the RSAC to accomplish our goals. It needs to be better coordinated.
  2. Rittwik is proposing an SMO project for Cherry. On motion made by Rittwik to create and SMO project with an ONAP focus at this time. We are open to other projects in the future.
    1. Seconded by John Paul Lane
    2. Jinri Huang abstains
    3. No negative votes
    4. John Murray votes in favor
    5. Masafumi Masuda votes in favor
    6. Juha Oravainen votes in favor
    7. We will work offline for clarification because Ganesh Shenbagaraman dropped early and Jinri Huang wants time to think about it.
3. user-d3360 Integration and Test
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (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.
1. Actions
  1. Action / Jack get the O-RAN teams perspective on Juha's concern whether Lusheng's 3rd party proposal is in line with the technical charters.
  2. Action/ Jinri Huang send Jack and Farheen Zbynek's official O-RAN approval.
  3. Action/ Farheen Cefalu post on wiki and oran site.
2. Votes
  1. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 15 Jul 2020
    2. On motion made by Jinri Huang
    3. Seconded by John Paul Lane
    4. VOTE: Vote taken, item passed
  2. Rittwik is proposing an SMO project for Cherry. On motion made by Rittwik to create and SMO project with an ONAP focus at this time. We are open to other projects in the future.
    1. Seconded by John Paul Lane
    2. Jinri Huang abstains
    3. No negative votes
    4. John Murray votes in favor
    5. Masafumi Masuda votes in favor
    6. Juha Oravainen votes in favor
    7. We will work offline for clarification because Ganesh Shenbagaraman dropped early and Jinri Huang wants time to think about it
Meeting Summary (resolutions, new action items, etc
1. 1. 1. .

2020 07 15

Recording: GMT20200715-120233_Zoom2-O-RA_2108x1120.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair		Weichen Ni	x
Deutsche Telekom	David Streibl	x	Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
Nokia	Juha Oravainen	x	Thoralf Czichy
Orange	William Diego		Vincent Danno
Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 08 Jul 2020
  2. On motion made by user-2057e
  3. Seconded by Juha Oravainen
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
1. Farheen put SMO as an open item
2. Rittwik requesting extending the timeline for the maintenance release.
3. Lusheng disucss licensing attribution
Release Votes and Approval
1. Currently items out in email for voting.
  1. Gerrit submissions to have Jira id reference
  2. All repos to define the Nexus IQ scan for licensing.
  3. Symantec versioning.
    1. Email vote was sent on July 9 and so far we have 3 votes.
    2. Ganesh will respond with 3 votes.
Copyright updates
1. Jack: We got confirmation that the copyright approval is in place. The board gave the EC permission to approve copyright requests from OSC. But the EC wanted clarification on how we want to structure that. If anyone has input send it this week about items they are concerned about so I have everyones input so I can continue to work it with EC. We cover error messages and apis and if someone has particular concerns send me a message so I can get this wrapped up.
Marketing of the current release (WG, LF, PR)
1. OSC Logo status
Status of Open Action Items (Old Business)
1. Action/ Jinri Huang ask Zybnek. didn't get a formal notification from Zbynek regarding copyright policy approval by the board.
2. Action/ Jinri Huang send Jack and Farheen Zbynek's official O-RAN approval.
3. Action/ Farheen Cefalu post on wiki and oran site.
4. ~~Action~~/ Farheen Cefalu update www.o-ran-sc.org site with Bronze Press Release .
5. ~~Action~~/ Farheen Cefalu We will post a link to the LF Insights in the Software page.
6. ~~Action~~/ Farheen Cefalu get link to virtual exhibition from Jinri and post it on the home page of the wiki.
7. ~~Action~~/ Farheen Cefalu put SMO discussion on the agenda.
8. Action/ user-59b16 bring slides for the SMO project proposal.
Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
  1. Bronze Maintenance Release
    1. Rittwik - 2 items being tested
      1. Pipeline - simulator trace file and KPI MON are both back logged. KPIMON is in the repo but subscription is not working correctly. Samsung is investigation. Viavi gave us a schema however trace file needs to be obtained. One week extension at least or two weeks are better.
      2. Setting up lab with O-DU testing.
      3. One week is not enough for both items. If possible two week extension.
      4. Matti - we can not guarantee we can get it working. Subscription manager folks are on vacation this month and we will attempt but no guarantees can be made.
      5. Lusheng - Yes accurate what Rittwik described. Everything is installed and now we can access the servers and ready to open up to Intel and Wind River for install. It's taking longer than expected so an extension will be nice.
      6. John-Paul - It will be good to know a definite date. Ongoing extensions we have to make a call.
      7. Jack - The original Cherry date is July 18. The maintenance release was July 18. The Bronze delayed by one week. This is a concern that we are creeping into the Cherry release development. The Bronze maintenance release will be dead ended on August 1. The maintenance release is scheduled for July 25th. There is a no activity block between June 27 - 31. We will fill up this no activity week and add an additional week to August 1. Maintenance release from July 25 - August 1.
      8. John-Paul - Acceptable as long as we don't push into the Cherry development.
      9. Zhimin - Server can be brought up. We need to program the server that will take time to prepare for the setup. It is not possible to finish the O-DU Low and O-DU High by August 1.
      10. Jack - That will move out of Bronze timeline to Cherry. How will that effect your Cherry development.
      11. Zhimin - From integration perspective we need to finish the O-DU Low and O-DU High integration. For O-DU Low there is uncertainty. I am not sure what is the overall impact to get into Cherry.
      12. Rittwik - My understanding was Low, High pairwise testing in Cherry. If we could test the RU test simulator with DU low that will suffice for the bronze maintenance release.
      13. Zhimin - We are remote programming which is causing delays. Programming the accelerate.
      14. On motion by Rittwik to extend the maintenance release deadline to August 1 with guidance not to extend that time.
        seconded by John- Paul
        Vote taken, item passed
      15. Jack - Let's pull together these key items so we can move on to focus on Cherry. Ganesh any concerns from your side? The low to high integration is primarily in Cherry.
      16. Ganesh - We will work this out with Intel.
  2. CherryTimeline
2. user-59b16 Requirements Software Architecture Committee
3. user-d3360 Integration and Test
  1. Lusheng - Originally it was brought up as an email vote that is going on. There is discussion about this particular item. Also from Sorav there were concerns about original licensing proposal. Sharing slides
    1. OSC License policy. some of the code is not licensed as Apache 2. We used previously an attribution list. We are asking TOC explicit case by case. We are including for example MIT license as source code. Going forward we should adopt a policy that is limiting popular and friendly licenses instead of going on a code case by case basis. There was a misunderstanding mostly on my part of what are the popular open source license. Creativecommons.org. has a large variety of licenses. I am now revising this request to a shorter list. The charters are using Apache2 for code. Ask user-d3360 for details.
    2. Requesting TOC to vote on allowing 3rd party code use policy.
    3. Jack this is too complicated to rush to vote. Action participating companies review your corporate legal licensing issues with your company and come back with comments. We have time to get this resolved. We want to clarify the use of software licenses for the development team. Each company needs to go and do their research and come back if things on this list make sense then we need to follow a process. Trishan and Lusheng have run it past the LF team and you are comfortable with this?
    4. Trishan, Yes.
    5. Juha - Nokia had this original proposal requires approval. This new proposal has to be reviewed. Is this new proposal in line with the technical charters or should the charters be updated first?
    6. Action / Jack get the O-RAN teams perspective on Juha's concern whether Lusheng's 3rd party proposal is in line with the technical charters.
4. Report out from PTL: Stand-Up & Report Out on Blockers
  1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
  2. Matti Hiltunen RIC Applications (RICAPP)
  3. Thoralf Czichy RIC Platform (RIC)
    1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
  4. user-a934b O-RAN Centralized Unit (OCU)
  5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
  6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
  7. Martin Skorupski Operations and Maintenance (OAM)
  8. Alex Stancu Simulations (SIM)
  9. Xiaohua Zhang Infrastructure (INF)
  10. weichen ni Documentation (DOC)
  11. (TBD) O-RAN Radio Unit (ORU)
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
1. Do we create a new project called the SMO as described by the needs of the requirements committee? Action / Farheen Cefalu add it to the top of the agenda next week.
2. Rittwik - If the need for the SMO is realized next week then can we get the group together quickly in the interest of time for the Cherry impacts.
3. Jack - Starting a new project takes time to get over the original startup threshold. Gathering the team getting all the repos in place. The expectation whenever we add it will be limited. The second release is when you start to see the team work .
Planning for Next Meeting
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.
1. Actions
  1. Action / Farheen Cefalu add it to the top of the agenda next week. Do we create a new project called the SMO as described by the needs of the requirements committee?
  2. Action/ user-59b16 bring slides for the SMO project proposal.
  3. Action / Jack get the O-RAN teams perspective on Juha's concern whether Lusheng's 3rd party proposal is in line with the technical charters.
  4. Action/ Requesting TOC to vote on allowing 3rd party code use policy
  5. Action/ Jinri Huang ask Zybnek. didn't get a formal notification from Zbynek regarding copyright policy approval by the board.
  6. Action/ Jinri Huang send Jack and Farheen Zbynek's official O-RAN approval.
  7. Action/ Farheen Cefalu post on wiki and oran site.
2. Votes:
  1. On motion by Rittwik to extend the maintenance release deadline to August 1 with guidance not to extend that time.
    1. seconded by John- Paul
    2. Vote taken, item passed
  2. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 08 Jul 2020
    2. On motion made by user-2057e
    3. Seconded by Juha Oravainen
    4. VOTE: Vote taken, item passed

2020 07 08

Recording: 2020_07_01_toc.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair		Weichen Ni	x
Deutsche Telekom	David Streibl		Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda		Anil Umesh
Nokia	Juha Oravainen	x	Thoralf Czichy
Orange	William Diego	x	Vincent Danno
Radisys	Ganesh Shenbagaraman		Sachin Srivastava	x
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 24 Jun 2020
  2. On motion made by Juha Oravainen
  3. Seconded by John Paul
  4. VOTE: Vote taken, item passed
Review of Today's Agenda
Release Votes and Approval
Copyright updates
1. Jack will get the new software specifications posted on the site. The board had a meeting and approved. The leadership was supportive and excited about the progress. Virtual exhibition has some nice demos.
1. 1. 1. John-Paul are there plans to make the Virtual Exhibition publicly accessible.
    2. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
  2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.
2. Marketing of the current release (WG, LF, PR)
  1. Bronze Release PR
  2. Virtual Exhibition.
  3. OSC Logo status.
3. Status of Open Action Items (Old Business)
  1. ~~Action~~ / user-d3360 add the topic of license attributions to the agenda. We want to start the pairwise testing.
  2. Action/ John Murray get clarification regarding transfer of AT&T Apache code into the new dual license repo
    1. Apache can be copy forward but we do not remove the Apache license. We will move that to an inactive status and the Samsung contributions will be in the new license repo.
4. Standing Agenda Items (Brief Status of Ongoing Activities)
  1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
    1. REL Cherry Release Planning
      1. We should be in the epic and what are the main end to end use cases.
  2. user-59b16 Requirements Software Architecture Committee
    1. Sharing spreadsheet.
      1. OCU Epics. These are the things we will do with O-CU. WG8 epics for Cherry. No Bronze pairwise testing with O-CU. Still pairwise testing with O-CU High.
      2. OTF Epics. Planning resources for OTF.
        Eliza some epics are lower priority for Cherry. Also the deployment of xApps and rApps. That is not here. Eliza Celenti is coming up with a plan.
        Rittwik will catch up David about call flow.
        David Kinsey yes, we have to establish a timeline and xApp deployment. We came up with a simple approach of a flow. We want O-SC to have a Cherry requirement. This will validate O2. The app should be able to join with the RIC.
        user-59b16 will that touch non RTU RIC?
        David Kinsey not really. You will have a piece of the SMO and xApp. The non RT RIC is aware ahead of time and doesn't use A1 to discover. We should have a discussion but may not be able to form epics.
        Non RT RIC is a requirement study.
        You have to have some software. Parts are at risk and others are not. SDK will not be at risk. The thing in the SMO that would manage the LCM would be at risk. We are proposing it can be applied to MANO or ONAP but it would have to be downstream to provide real value.
        ACiton/ David Kinsey set up a meeting with Martin Skorupski to continue discussion.
      3. INF Epics
        StarlingX is the commercial apps. Which part is commercialized? I think StarlingX is what is being commercialized. What we have with OSC is a derivative of that.
      4. NRT RIC has a lot of epics. The epics come down to many things. Some of it may happen in Cherry and some may not. There is a priority list of High, medium, low.
        The PTL and the people need to manage their epics. The key is to have the E2E use cases working.
        The ETE flows have not chained. There were four health check flows.
        We need to have a checklist of where we are with the end to end flows. They are complex. It is important that you give organization for each use case of where we are in the progress of that use check.
      5. We had a discussion on O-DU High on flows but because of resources and time we have to have a prioritized, stretched, and agressive plan to demonstrate significant progress to the overall flow.
      6. ODU-Low epics
      7. Simulator E2 simulator enhancements.
      8. Traffic Steering xApp Bronze - Viavi decided to contribute access to some of their tools. Add it to the agenda. Be sure everyone understands what's available from the simulator.
      9. What are the major advances that are significant to the E2E use cases.
        Get the pipeline working. For Cherry it is ambitious to get the KPI-MON thru the xApp.
        Mentality how do you get the data just in time and target a UE. That's the E2E healthcheck validation. See RSAC Cherry Release presentation.
        E2 service model may not be fully complete before sprint development starts. This is pre-spec. so it will be a challenge.
      10. Healthcheck - The healthcheck flows will not change. Components will have to adhere. near RT RIC has not completed their flows. It is up to the PTLs to take a look. We need a score card or else we wont know where people are at.
      11. LCM - David is coming up with call flows.
      12. Jack - Does anyone want to add items to our E2E use case. How do we show A1 functionality? How do we demonstrate more of the A1 controller as part of the E2E use cases?
        John-Paul Is there something required for OR-Apps?
        Jack How do we pull cases together like rApps and getting the SDK in place and get rApps. We have the pieces but to pull it all together we need to create 2 projects. 1 for SMO and who wants to contribute a model. I want to open up a discussion to create an SMO project and elect a PTL to make an overall system gradually. I do want people to think about it and who would want to participate in organizing it. We need to start and manage contributions to it to get to the point of getting rApps in place.
        John-Paul If we had an ORApp.
        There is a Hello World that can be either rApp or OApp.
        We can list some of the code for the R1 interface.
        These need to go into more depth in the RSAC. We can summarize here but the details.
        I am getting interest in O-DU Low project. The question is how best to manage that. I thought the most effective way is to treat them in parallel. We can see how much code can be used across them. There is interest and people will be joining in the next few weeks to discuss.
        Rittwik - I will update the spreadsheet. When the planning is done it is up to the PTLs to run with it.
        Jack - The challenge in Cherry is to develop technology adding the O-1 interface and become more of a functional subsystem. We will get O-CU code that will start to fill out those blocks. Just because people are active in xApps we don't want to lose the focus of developing all the parts of the stack. Each component should advance a certain amount in that release in coming up with an O-RAN system.
        PTLs think about advancing their modules and making it interoerable with the E2E flows. We must make it a useful system where people can grab parts of the code and move the whole O-RAN community forward. Try to make as much re-usable for the community as they leverage those products. We've gotten through 2 releases and declared the paths we're on. We have to listen to the larger community and grow participation of people using and contributing the code. This will only happen if people and companys participate.
        Think of how we can improve Cherry. Look for ideas of how to improve how we work. We need to grow and round out. This is a group of small teams. O-RAN Alliance is over 200 members we have to get more people to participate. It is a project for wider participation including service providers not just generating specs but dealing with ramifications of using those specs.
  3. user-d3360 Integration and Test
    1. user-d3360 discuss general practice.
    2. user-d3360 Getting Started
  4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
    1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
    2. Matti Hiltunen RIC Applications (RICAPP)
    3. Thoralf Czichy RIC Platform (RIC)
      1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
    4. user-a934b O-RAN Centralized Unit (OCU)
    5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
    6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
    7. Martin Skorupski Operations and Maintenance (OAM)
    8. Alex Stancu Simulations (SIM)
    9. Xiaohua Zhang Infrastructure (INF)
    10. weichen ni Documentation (DOC)
    11. (TBD) O-RAN Radio Unit (ORU)

New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.

Discuss SMO

1. is Planning for Next Meeting
2. Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
1. Votes
  1. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 24 Jun 2020
    2. On motion made by Juha Oravainen
    3. Seconded by John Paul
    4. VOTE: Vote taken, item passed
2. Actions
  1. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
  2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.

2020 07 01

Recording: 2020_07_01_toc.mp4

Agenda

Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check

Company	Contact Name	Attendance	Alternate Contact	Attendance
AT&T	Jack Murray Co-Chair	x	Lusheng Ji
China Mobile	Jinri Huang Co-Chair		Weichen Ni	x
Deutsche Telekom	David Streibl		Ondřej Hudousek
Ericsson	John-Paul Lane	x	John Keeney
NTT DOCOMO	Masafumi Masuda		Anil Umesh
Nokia	Juha Oravainen	x	Thoralf Czichy
Orange	William Diego	x	Vincent Danno
Radisys	Ganesh Shenbagaraman		Sachin Srivastava	x
Verizon	Viswa Kumar		Kristen Young

*Quorum: 50% or more of total TSC voting members unless excluded due to attendance. We have a quorum and can vote on activities.

Review and Agree to Minutes of Previous Meeting
1. The minutes of the prior meetings were reviewed, and no corrections.
  1. Vote to approve minutes for 24 Jun 2020
  2. On motion made by Juha Oravainen
  3. Seconded by John Paul
  4. VOTE: Vote taken, item passed
1. Review of Today's Agenda
2. Release Votes and Approval
3. Copyright updates
  1. Jack will get the new software specifications posted on the site. The board had a meeting and approved. The leadership was supportive and excited about the progress. Virtual exhibition has some nice demos.
    1. John-Paul are there plans to make the Virtual Exhibition publicly accessible.
    2. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
  2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.
4. Marketing of the current release (WG, LF, PR)
  1. Bronze Release PR
  2. Virtual Exhibition.
  3. OSC Logo status.
5. Status of Open Action Items (Old Business)
  1. ~~Action~~ / user-d3360 add the topic of license attributions to the agenda. We want to start the pairwise testing.
  2. Action/ John Murray get clarification regarding transfer of AT&T Apache code into the new dual license repo
    1. Apache can be copy forward but we do not remove the Apache license. We will move that to an inactive status and the Samsung contributions will be in the new license repo.
6. Standing Agenda Items (Brief Status of Ongoing Activities)
  1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
    1. REL Cherry Release Planning
      1. We should be in the epic and what are the main end to end use cases.
  2. user-59b16 Requirements Software Architecture Committee
    1. Sharing spreadsheet.
      1. OCU Epics. These are the things we will do with O-CU. WG8 epics for Cherry. No Bronze pairwise testing with O-CU. Still pairwise testing with O-CU High.
      2. OTF Epics. Planning resources for OTF.
        Eliza some epics are lower priority for Cherry. Also the deployment of xApps and rApps. That is not here. Eliza Celenti is coming up with a plan.
        Rittwik will catch up David about call flow.
        David Kinsey yes, we have to establish a timeline and xApp deployment. We came up with a simple approach of a flow. We want O-SC to have a Cherry requirement. This will validate O2. The app should be able to join with the RIC.
        user-59b16 will that touch non RTU RIC?
        David Kinsey not really. You will have a piece of the SMO and xApp. The non RT RIC is aware ahead of time and doesn't use A1 to discover. We should have a discussion but may not be able to form epics.
        Non RT RIC is a requirement study.
        You have to have some software. Parts are at risk and others are not. SDK will not be at risk. The thing in the SMO that would manage the LCM would be at risk. We are proposing it can be applied to MANO or ONAP but it would have to be downstream to provide real value.
        ACiton/ David Kinsey set up a meeting with Martin Skorupski to continue discussion.
      3. INF Epics
        StarlingX is the commercial apps. Which part is commercialized? I think StarlingX is what is being commercialized. What we have with OSC is a derivative of that.
      4. NRT RIC has a lot of epics. The epics come down to many things. Some of it may happen in Cherry and some may not. There is a priority list of High, medium, low.
        The PTL and the people need to manage their epics. The key is to have the E2E use cases working.
        The ETE flows have not chained. There were four health check flows.
        We need to have a checklist of where we are with the end to end flows. They are complex. It is important that you give organization for each use case of where we are in the progress of that use check.
      5. We had a discussion on O-DU High on flows but because of resources and time we have to have a prioritized, stretched, and agressive plan to demonstrate significant progress to the overall flow.
      6. ODU-Low epics
      7. Simulator E2 simulator enhancements.
      8. Traffic Steering xApp Bronze - Viavi decided to contribute access to some of their tools. Add it to the agenda. Be sure everyone understands what's available from the simulator.
      9. What are the major advances that are significant to the E2E use cases.
        Get the pipeline working. For Cherry it is ambitious to get the KPI-MON thru the xApp.
        Mentality how do you get the data just in time and target a UE. That's the E2E healthcheck validation. See RSAC Cherry Release presentation.
        E2 service model may not be fully complete before sprint development starts. This is pre-spec. so it will be a challenge.
      10. Healthcheck - The healthcheck flows will not change. Components will have to adhere. near RT RIC has not completed their flows. It is up to the PTLs to take a look. We need a score card or else we wont know where people are at.
      11. LCM - David is coming up with call flows.
      12. Jack - Does anyone want to add items to our E2E use case. How do we show A1 functionality? How do we demonstrate more of the A1 controller as part of the E2E use cases?
        John-Paul Is there something required for OR-Apps?
        Jack How do we pull cases together like rApps and getting the SDK in place and get rApps. We have the pieces but to pull it all together we need to create 2 projects. 1 for SMO and who wants to contribute a model. I want to open up a discussion to create an SMO project and elect a PTL to make an overall system gradually. I do want people to think about it and who would want to participate in organizing it. We need to start and manage contributions to it to get to the point of getting rApps in place.
        John-Paul If we had an ORApp.
        There is a Hello World that can be either rApp or OApp.
        We can list some of the code for the R1 interface.
        These need to go into more depth in the RSAC. We can summarize here but the details.
        I am getting interest in O-DU Low project. The question is how best to manage that. I thought the most effective way is to treat them in parallel. We can see how much code can be used across them. There is interest and people will be joining in the next few weeks to discuss.
        Rittwik - I will update the spreadsheet. When the planning is done it is up to the PTLs to run with it.
        Jack - The challenge in Cherry is to develop technology adding the O-1 interface and become more of a functional subsystem. We will get O-CU code that will start to fill out those blocks. Just because people are active in xApps we don't want to lose the focus of developing all the parts of the stack. Each component should advance a certain amount in that release in coming up with an O-RAN system.
        PTLs think about advancing their modules and making it interoerable with the E2E flows. We must make it a useful system where people can grab parts of the code and move the whole O-RAN community forward. Try to make as much re-usable for the community as they leverage those products. We've gotten through 2 releases and declared the paths we're on. We have to listen to the larger community and grow participation of people using and contributing the code. This will only happen if people and companys participate.
        Think of how we can improve Cherry. Look for ideas of how to improve how we work. We need to grow and round out. This is a group of small teams. O-RAN Alliance is over 200 members we have to get more people to participate. It is a project for wider participation including service providers not just generating specs but dealing with ramifications of using those specs.
  3. user-d3360 Integration and Test
    1. user-d3360 discuss general practice.
    2. user-d3360 Getting Started
  4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list. Are there any major items that anyone would like to raise to the TOC this week?
    1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
    2. Matti Hiltunen RIC Applications (RICAPP)
    3. Thoralf Czichy RIC Platform (RIC)
      1. See status notes under "Status 2020-04-29 and 2020-04-30 and 2020-05-06 and 2020-05-12" in Bronze Release (Jun 2020)
    4. user-a934b O-RAN Centralized Unit (OCU)
    5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
    6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
    7. Martin Skorupski Operations and Maintenance (OAM)
    8. Alex Stancu Simulations (SIM)
    9. Xiaohua Zhang Infrastructure (INF)
    10. weichen ni Documentation (DOC)
    11. (TBD) O-RAN Radio Unit (ORU)
7. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
  1. Discuss SMO
8. is Planning for Next Meeting
9. Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
1. Votes
  1. The minutes of the prior meetings were reviewed, and no corrections.
    1. Vote to approve minutes for 24 Jun 2020
    2. On motion made by Juha Oravainen
    3. Seconded by John Paul
    4. VOTE: Vote taken, item passed
2. Actions
  1. Action/ John Murray will check the progress of making the Virtual Exhibition being made public.
  2. Action/ Farheen Cefalu add a link to the LF analytics Insight on this page.

Show all results

Space shortcuts

Page tree

Versions Compared

Old Version 12

New Version 13

Key

2020 08 12

2020 08 05

2020 07 29

2020 07 22

2020 07 15

2020 07 08

2020 07 01

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 12

New Version 13

Key

2020 08 12

2020 08 05

2020 07 29

2020 07 22

2020 07 15

2020 07 08

2020 07 01