Skip to end of metadata
Go to start of metadata

2020 03 25

Audio Recording020-03-25-toc-audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    xOndřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting 

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by David Streibl
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
    1. Jack - Next week will be our first meeting of April. We will cross over completion of our first year as our open source community.  Thank you to everyone who supported the projects and contributed.  We will be transitioning to add 3 additional members to the TOC.  We will move to a 9 members of the TOC.  They will be introduced next week.
  5. Release Votes and Approval
  6. Marketing of the current release (WG, LF, PR)
    1. Jinri - Nothing to report for marketing.
      1. Jack - We have to talk about  how to broaden our communication to the broader community.  We have to educate and communicate progress and activities.  We will have to get back to this at some point.
    2. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
  7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
    1. ActionENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi.
      1. Rittwik - 7a and 7e relate to work with Viavi.  
      2. Jack - 7a was to discuss O-1 functionality and how there work will impact.
      3. Engwei - John, Martin, and High Street met on how O-1 testing is required here.  We concluded that there will be further dicussions for use cases. requirements for simulators.  What measurements and pm counters over to RIC for dynamic traffic steering.  We discussed E-1.  From Viavi we will make sure we are tracking the team.  John mentioned the need is for the Cherry release and anything for the Bronze.  Thanked the team for bringing Viavi up to speed.
      4. Action ENGWEI KOO  - will add a deck.  Looking at the swim lane tables to track how Viavi will 
    2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
    3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
    4. ActionFarheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
    5. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
      1. Rittwik - sharing slide of what is needed for the short term.
      2. ActionRittwik Jana upload the slide to the RSAC page.
    6. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.
      1. Jack - Reviewed Releases page.  Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      2. Rittwik - WG input requirements from 14 - 20th of June.  Not sure that WG3 requirements will be done by then.
        1. Then we won't use them.  We can't be constantly changing so developers don't know what to build.  If we don't have then we will rework the use cases.  We can shift things a little.  The timelines are aggressive enough without changes.
        2. Rittwik - Please bring this chart up on this point to the TSC.  
        3. Jack - If it's not in the Cherry Release then it will get into the plan for D but won't happen until a year later.
        4. David - What do you mean by working group input freeze?
          1. Jack - We've been asked to coordinate with the O-RAN WGs.  We have Bronze release touchpoints.  The goal was to look for WG input.  When we complete our planning we will do a review with them.  We have a touch base twice.  Dev Sprint 4 ends 4-26.  We will give a demo of the functionality we plan to release.  In this case it's Bronze.  For Cherry I added the comment that we'd be freezing what specifications we'll be working with. 
          2. Thoralf - There is a difference between specifications.  
          3. Jinri - The freeze is not the freeze of specs.  We recognize at this time the latest spec we have from WG.
          4. In week 21 we will use version spec 2.1 that O-RAN Alliance is expecting to release in week 23.
          5. Jack - we agree on which specs we are working.  I'll be happy to use a different word than "freeze".
          6. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
          7. Jack - We need to figure out how to align.  I expect they will be in the same release window.
            1. Rittwik - We will face challenges with the current situation.
            2. Jack - Each release has it's own set of decisions.  We can stretch out a little bit.  If we stretch out in ETE testing then we have stretch.  The community can review if we provide it to the TOC.
    7. ActionDavid Streibl update Vote Release Name page with the D release name options.
      1. David - There are very few colors with the word D in it.  It will be a fairly short list to avoid the "dark"  and "deep" colors.
    8. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
    9. ActionJinri Huang provide the TOC with the new O-RAN Alliance timeline.
    10. ActionThoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
    11. ActionTracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
      1. Jack - will continue the discussion to see how we can improve.  We're a young community.  Some of our needs are different than other communities.  As a community if people find better ideas, or ways to do things bring them to the PTL or the TOC.  There may be things we can learn and get better at.
    12. ActionJohn Keeney open a trouble ticket with LF for the Confluence calendar issue.
      1. ActionTrishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
      2. We are in the sprint 3.  
      3. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
      4. Next week we will spend more time with each PTL.  Be prepared to inform us on what the projects have completed in sprint 2.
    2. 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. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. note I updated the committer change process as per discussion last week: How to request committer changes.
        2. Action/ Jack Review Thoralf's How to request committer changes
        3. Committers don't require a TOC votel.  
      3. Yingying Wang O-RAN Centralized Unit (OCU) 
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
      1. We will be starting Cherry.
      2. We need the Viavi simulator.
      3. Jack - Pulling together the overall stack it is important to show pieces evolving and their progress.
      4. Lusheng - we have one and a half development sprints left before the testing cycle starts and the simulator plays a very important role.  We would like to have the simulator sooner than later is preferred.
        1. Jack- As people know we have a plan and we have decisions with the broader TOC.
      5. Jack - David - Was there any update with the test focus group?
        1. David - William was working on that task.
        2. William - We are working on test and integration specification.  Work is ongoing. Orange will provide input next week.  We have made good progress.  The aspects from Open source simulations could be interesting.
          1. Jack - Has that group provided a plan for simulation?
            1. William - Yes, Viavi is leading the test and integration focus group.  They have great suggestions.  We are trying to work with them to organize interfaces it will be a key aspect.  We are trying to get more input from other WGs to understand their specifications and we are taking their needs into account.
            2. Jack - Action/ William Diego Maza work with Rittwik Jana and set up a meeting with whoever the leadership is in the test committee so we are synchronized with the other TOC members.  The key is to get some of the decision makers from the test group so we can have their input.
            3. Action/ Rittwik Jana set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
    4. Lusheng Ji  Integration and Test
      1. In terms of code quality.  LF is using SONAR Cloud to report unit test coverage.  The integration team is providing  the sample repo set up to set up your code and publish to SONAR cloud.  Captured in the wiki page.  If you are a PTL you can work with your committers to add SONAR to the projects.
        1. Where can people find examples?
        2. ActionLusheng Ji add the wiki link in the Integration and Test.
        3. Post it on the integration and test wiki.
      2. Sprint demos: We have simulation and OAM have completed their demos.  The non Real Time did not have significant things to demonstrate.  Near real time will demo next Thursdays. 
        1. Action/ PTLs provide Lusheng Ji  with your sprint 2 demos. 
        2. Demo activities are important and required to keep the overall project and stakeholders in synch. 
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 
    1. Jinri Huang  - I saw an O-CU approval with two votes has that been closed?
      1. The PTL will raise it if it is an issue.  
    2. weichen ni  - There is a new request by documentation to create an API document.  Suggest each PTL to use an API document.  Be sure it generates a weblink to create a page in the docs.
      1. Where will the html be hosted?
        1. https://docs.o-ran-sc.org/en/latest/
        2. Weichen - you can put your api documentation in your repos docs directory and I will generate the html.
        3. Standardize the tools we use so we have a common set of tools.
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes: 
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Jinri found typos and will discuss with Farheen offline. 
        2. Vote to approve minutes for  
        3. On motion made by Jinri Huang
        4. Seconded by David Streibl
        5. VOTE: Vote taken, item passed
    2. Actions:
      1. Action ENGWEI KOO  - will add a deck to RSAC wiki.
      2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
      4. ActionFarheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
      5. ActionRittwik Jana upload the UE emulator short/long term slide deck to the RSAC page.
      6. Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      7. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
      8. ActionDavid Streibl update Vote Release Name page with the D release name options.
      9. ActionJinri Huang provide the TOC with the new O-RAN Alliance timeline.
      10. ActionTrishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
      11. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
      12. Action/ Jack Review Thoralf's How to request committer changes
      13. ActionLusheng Ji add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
      14. Action/ Rittwik Jana set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
      15. Action/ William Diego Maza  we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      16. ActionLusheng Ji add the link in the Integration and Test wiki to the SONAR instructions that you discussed on  TOC meeting.
      17. Action/ PTLs provide Lusheng Ji  with your sprint 2 demos. 


2020 03 25

Audio Recording020-03-25-toc-audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    xOndřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting 

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by David Streibl
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
    1. Jack - Next week will be our first meeting of April. We will cross over completion of our first year as our open source community.  Thank you to everyone who supported the projects and contributed.  We will be transitioning to add 3 additional members to the TOC.  We will move to a 9 members of the TOC.  They will be introduced next week.
  5. Release Votes and Approval
  6. Marketing of the current release (WG, LF, PR)
    1. Jinri - Nothing to report for marketing.
      1. Jack - We have to talk about  how to broaden our communication to the broader community.  We have to educate and communicate progress and activities.  We will have to get back to this at some point.
    2. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
  7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
    1. ActionENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi.
      1. Rittwik - 7a and 7e relate to work with Viavi.  
      2. Jack - 7a was to discuss O-1 functionality and how there work will impact.
      3. Engwei - John, Martin, and High Street met on how O-1 testing is required here.  We concluded that there will be further dicussions for use cases. requirements for simulators.  What measurements and pm counters over to RIC for dynamic traffic steering.  We discussed E-1.  From Viavi we will make sure we are tracking the team.  John mentioned the need is for the Cherry release and anything for the Bronze.  Thanked the team for bringing Viavi up to speed.
      4. Action ENGWEI KOO  - will add a deck.  Looking at the swim lane tables to track how Viavi will 
    2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
    3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
    4. ActionFarheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
    5. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
      1. Rittwik - sharing slide of what is needed for the short term.
      2. ActionRittwik Jana upload the slide to the RSAC page.
    6. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.
      1. Jack - Reviewed Releases page.  Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      2. Rittwik - WG input requirements from 14 - 20th of June.  Not sure that WG3 requirements will be done by then.
        1. Then we won't use them.  We can't be constantly changing so developers don't know what to build.  If we don't have then we will rework the use cases.  We can shift things a little.  The timelines are aggressive enough without changes.
        2. Rittwik - Please bring this chart up on this point to the TSC.  
        3. Jack - If it's not in the Cherry Release then it will get into the plan for D but won't happen until a year later.
        4. David - What do you mean by working group input freeze?
          1. Jack - We've been asked to coordinate with the O-RAN WGs.  We have Bronze release touchpoints.  The goal was to look for WG input.  When we complete our planning we will do a review with them.  We have a touch base twice.  Dev Sprint 4 ends 4-26.  We will give a demo of the functionality we plan to release.  In this case it's Bronze.  For Cherry I added the comment that we'd be freezing what specifications we'll be working with. 
          2. Thoralf - There is a difference between specifications.  
          3. Jinri - The freeze is not the freeze of specs.  We recognize at this time the latest spec we have from WG.
          4. In week 21 we will use version spec 2.1 that O-RAN Alliance is expecting to release in week 23.
          5. Jack - we agree on which specs we are working.  I'll be happy to use a different word than "freeze".
          6. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
          7. Jack - We need to figure out how to align.  I expect they will be in the same release window.
            1. Rittwik - We will face challenges with the current situation.
            2. Jack - Each release has it's own set of decisions.  We can stretch out a little bit.  If we stretch out in ETE testing then we have stretch.  The community can review if we provide it to the TOC.
    7. ActionDavid Streibl update Vote Release Name page with the D release name options.
      1. David - There are very few colors with the word D in it.  It will be a fairly short list to avoid the "dark"  and "deep" colors.
    8. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
    9. ActionJinri Huang provide the TOC with the new O-RAN Alliance timeline.
    10. ActionThoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
    11. ActionTracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
      1. Jack - will continue the discussion to see how we can improve.  We're a young community.  Some of our needs are different than other communities.  As a community if people find better ideas, or ways to do things bring them to the PTL or the TOC.  There may be things we can learn and get better at.
    12. ActionJohn Keeney open a trouble ticket with LF for the Confluence calendar issue.
      1. ActionTrishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
      2. We are in the sprint 3.  
      3. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
      4. Next week we will spend more time with each PTL.  Be prepared to inform us on what the projects have completed in sprint 2.
    2. 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. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. note I updated the committer change process as per discussion last week: How to request committer changes.
        2. Action/ Jack Review Thoralf's How to request committer changes
        3. Committers don't require a TOC votel.  
      3. Yingying Wang O-RAN Centralized Unit (OCU) 
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
      1. We will be starting Cherry.
      2. We need the Viavi simulator.
      3. Jack - Pulling together the overall stack it is important to show pieces evolving and their progress.
      4. Lusheng - we have one and a half development sprints left before the testing cycle starts and the simulator plays a very important role.  We would like to have the simulator sooner than later is preferred.
        1. Jack- As people know we have a plan and we have decisions with the broader TOC.
      5. Jack - David - Was there any update with the test focus group?
        1. David - William was working on that task.
        2. William - We are working on test and integration specification.  Work is ongoing. Orange will provide input next week.  We have made good progress.  The aspects from Open source simulations could be interesting.
          1. Jack - Has that group provided a plan for simulation?
            1. William - Yes, Viavi is leading the test and integration focus group.  They have great suggestions.  We are trying to work with them to organize interfaces it will be a key aspect.  We are trying to get more input from other WGs to understand their specifications and we are taking their needs into account.
            2. Jack - Action/ William Diego Maza work with Rittwik Jana and set up a meeting with whoever the leadership is in the test committee so we are synchronized with the other TOC members.  The key is to get some of the decision makers from the test group so we can have their input.
            3. Action/ Rittwik Jana set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
    4. Lusheng Ji  Integration and Test
      1. In terms of code quality.  LF is using SONAR Cloud to report unit test coverage.  The integration team is providing  the sample repo set up to set up your code and publish to SONAR cloud.  Captured in the wiki page.  If you are a PTL you can work with your committers to add SONAR to the projects.
        1. Where can people find examples?
        2. ActionLusheng Ji add the wiki link in the Integration and Test.
        3. Post it on the integration and test wiki.
      2. Sprint demos: We have simulation and OAM have completed their demos.  The non Real Time did not have significant things to demonstrate.  Near real time will demo next Thursdays. 
        1. Action/ PTLs provide Lusheng Ji  with your sprint 2 demos. 
        2. Demo activities are important and required to keep the overall project and stakeholders in synch. 
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 
    1. Jinri Huang  - I saw an O-CU approval with two votes has that been closed?
      1. The PTL will raise it if it is an issue.  
    2. weichen ni  - There is a new request by documentation to create an API document.  Suggest each PTL to use an API document.  Be sure it generates a weblink to create a page in the docs.
      1. Where will the html be hosted?
        1. https://docs.o-ran-sc.org/en/latest/
        2. Weichen - you can put your api documentation in your repos docs directory and I will generate the html.
        3. Standardize the tools we use so we have a common set of tools.
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes: 
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Jinri found typos and will discuss with Farheen offline. 
        2. Vote to approve minutes for  
        3. On motion made by Jinri Huang
        4. Seconded by David Streibl
        5. VOTE: Vote taken, item passed
    2. Actions:
      1. Action ENGWEI KOO  - will add a deck to RSAC wiki.
      2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      3. Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America 
      4. ActionFarheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
      5. ActionRittwik Jana upload the UE emulator short/long term slide deck to the RSAC page.
      6. Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
      7. Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times.  There are 3 trains for the specifications.  
      8. ActionDavid Streibl update Vote Release Name page with the D release name options.
      9. ActionJinri Huang provide the TOC with the new O-RAN Alliance timeline.
      10. ActionTrishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
      11. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
      12. Action/ Jack Review Thoralf's How to request committer changes
      13. ActionLusheng Ji add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
      14. Action/ Rittwik Jana set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
      15. Action/ Rittwik Jana set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.  
      16. ActionLusheng Ji add the link in the Integration and Test wiki to the SONAR instructions that you discussed on  TOC meeting.
      17. Action/ PTLs provide Lusheng Ji  with your sprint 2 demos. 

2020 03 18

Recorded Video2020-03-18-toc.mp4

Audio2020-03-18-toc-audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    xOndřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting 

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by David Streibl
      5. VOTE: Vote taken, item passed
    2. The minutes of the prior meetings were reviewed, and there was a comment on updating 7, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by David Streibl
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    1. Jinri - OC-U needs a new repo.
  6. Marketing of the Amber release (WG, LF, PR)
    1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
  7. Status of Open Action Items (Old Business)Jack - How does the OSC evolve from where we're at.  Every piece is under construction.  O-DU Emulation will help with that.
    1. Action Ken Trudgeon from Viavi will report back on O-1 capabilities for an end to end full stack capability for the OAM team John Keeney.
    2. ActionENGWEI KOO will set up a meeting with  Tracy Van Brakle , Martin Skorupski John Keeney , and Alex Stanc to discuss O-1 interface options with Viavi
    3. ActionJinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
      1. Shared slides with the team and the slides are being updated.  We have a policy update and it is under the clearance process.  Jinri will update the community once it's finalized.
    4. ActionJinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      1. Demos were moved to virtual.  O-RAN Alliance is working on this.  Jinri will work with Farheen to add the link.
      2. ActionFarheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.  OTIC will be voting on the moving the Plugfest to September.
    5. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
      1. We have to make decisions about what simulator and emulator support we need and can attain.
      2. Rittwik - We've built a technical plan to build out the O-RAN Lab in T-lab.  Viavi has proposed emulator and simulator.  You will also get a business proposal from Viavi today.  You will have all the plans.  The technical plan is in the RSAC space.  
      3. Action / Tracy Van Brakle clarify OTIC North America
    6. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. Spoke to colleague but didn't reach a conclusion.
    7. Action/William Diego Maza  will talk to the focus group regarding test coordinator for the O-RAN SC.
      1. William spoke to companies needs to have ETE framework.  Viavi is providing contributions to this focus group.
        1. Jack is looking for OSC interacting with the focus group and how we are doing that.
      2. William - it is important to wait until we have the ETE framework is established.  Once it's documented I can present that and position us with this group.
    8. Action/ Lusheng follow up with Zhimin offline to set up target architecture for O-DU Low.
      1. Lusheng - we understand what O-DU Low means for setting up an environment for unit testing and building.  We have a path forward.  It was presented last night to the RSAC and will be on the Integration Test plan.  Side note for technical proposal of the integration lab is subject to EC approval.
        1. Jack - It will continue to evolve.  I have been contacted by other peoples interest in O-DU as well.
    9. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release. 
      1. We are getting close to D release naming poll.  We can move forward with the D release naming poll.
    10. Action/ Jinri Huang will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
      1. Getting the WGs to understand what are their cut-off dates for their specifications.  Want to put the specifications for Cherry from WG2 and WG3 in our timeline.
      2. Rittwik - We need to align what use cases can be done.  Specs won't be out in time.  We need to tell them these. are our times but the WG2 and WG3 can't meet the dates.  Either wait for specs come out in Q3 because Cherry dev will be ending.  Or pre-spec but then you have to wait to D release to test it.  Any use case will require an E2 service model.  If the E2 service model is the key.  Timing alignment and communicating priorities so they can work it to meet our timeline.  Can we bring this issue to EC for discussion?  It is informally discussed. 
      3. Jack - There's a use case that is part of WG1.  Have they accepted this as one of their use cases?
        1. Yes. Traffic steering use case.
      4. Jinri - During virtual F2F with WG3 they have adjusted their timeline to meet our Bronze release.  For Cherry release they have not provided a design date.  They agreed to the timing adjustment method.
        1. Rittwik - At the F2F they will be publishing 3 versions of E2 v.1 will com out in August v. 3 will come out in December.  Thoralf provided guidance when it should start and finish.  
          1. Jinri - Meeting Cherry release is in synch.  
          2. ActionThoralf Czichy share the OSC Alignment Aspects slides with Jack.  We have means to align with WG3.  
          3. Rittwik - We need a timeline chart for C and D.  We need to know our timelines of what is at stake.  We need this for all WGs.
    11. ActionYingying Wang work with Lusheng to create the test cases for O-CU.
      1. Lusheng - Yingying brought a contact for integration and test.  We will work together.
    12. ActionYingying Wang update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
    13. ActionTracy Van Brakle  Trishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.
      1. Tracy will take the action item.
    14. ActionSachin Srivastava update ODU-High Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues. 
    15. Action/ PTLs assign someone to lead the integration and test.
      1. If you go to Integration and Test there the table is in the Bronze release 
    16. Action/ Farheen Cefalu request to escalate the calendar issue with LF or add it to agenda for TOC call.
      1. Home time zone for the calendar.  
      2. Difficult to coordinate the calendars with Outlook.  There are errors with the format of the calendars.  Does OSC have a home time zone?  What is it and what time zone should be used.
      3. Thoralf - For Confluence raise a ticket with help at LF. For local time zones use UTC.  
      4. Lusheng - We have two calendar applications one is a part of Confluence and the other is from Groups.io.  The mailing list is triggered by Groups.ioGroups.io takes care of the time change but the Confluence does not seem to work.
      5. Jack will work with Trishan de Lanerolle to address the items above.
      6. ActionJohn Keeney open a trouble ticket with LF for the Confluence calendar issue.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
    2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. note I updated the committer change process as per discussion last week: How to request committer changes
      3. Yingying Wang O-RAN Centralized Unit (OCU) 
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
    4. Lusheng Ji  Integration and Test
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)

2020 03 04

Recording: 2020-03-04_toc.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    xOndřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by David Streibl
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    1. Repo request for RICAPP - 4th reminder - Matti Hiltunen

      1. Dear O-RAN SC TOC members,

        I would like to request the following new repos to accommodate the new xApps required for the O-RAN SC Bronze release use cases (traffic steering and health check). 

        Jinri and Jack have already approved this - waiting for one more.

        TS xAPP:

        • Proposed repository name: ric-app/ts
        • License: Apache 2 
        • A brief description: This repo will host the source code for the TS (Traffic Steering) xApp. Written in C++. 
        • A list of committers:
          1. Ron Shacham, rshacham@...
          2. Shraboni Jana, sj492a@...
          3. Scott Daniels, daniels@...

        QP xApp:

        • Proposed repository name: ric-app/qp
        • License: Apache 2 
        • A brief description: This repo will host the source code for the QP (QuE Predictor) xApp that uses a machine learning model to predict the QoE of a UE if it is handed over to a new cell. Written in Python.
        • A list of committers:
          1. Manoop Talasila, talasila@...
          2. Guy Jacobson, guy@...
          3. Gueyoung Jung, gjung@....com
        • QP Driver xApp:
        • Proposed repository name: ric-app/qp-driver
        • License: Apache 2 
        • A brief description: This repo will host the source code for the QP Driver xApp that pulls the features used in the QP ML model out of the SDL layer for the UEs whose QoE we want to improve. Written in go.
        • A list of committers:
          1. Tommy Carpenter, tommy@...
          2. Scott Daniels, daniels@...
          3. Jack Lucas, jflucas@...

        HW xApp:

        • Proposed repository name: ric-app/hw
        • License: Apache 2 
        • A brief description: This repo will host the source code for the HW (HellowWorld) demo xApp that demonstrates how to utilize the different RIC capabilities from a C++-based xApp (HelloWorld A1 policy, HelloWorld E2 SM, RMR, SDL, O-1 config). This demo xApp will also implement the A1 health check.
        • A list of committers:
      2. Ron Shacham, rshacham@...
      3. Shraboni Jana, sj492a@...
      4. Scott Daniels, daniels@... 
      5. VOTE: On motion made by Matti Hiltunen
        1. Seconded by David Streibl
        2. VOTE: Vote taken, item passed
    2. Repo Request - portal/nonrtric-controlpanel - 2nd reminder John Keeney

      1. Hi TOC members,

        Please prioritise the request below. Thanks Jack for your previous reply.

        Thanks,

        John

        Sent: Wednesday 26 February 2020 13:25
        Subject: Repo Request - portal/nonrtric-controlpanel

        Hi TOC members

        We agreed at last week’s TOC meeting to permit creation of a GUI for the NONRTRIC function. Thank you.

        But we also decided that it  would be ok to change the name, however LF will very likely require the name to be included in the official approval.

        So I am re-submitting the request with a new name “portal/nonrtric-controlpanel

        I would like to request the following new repo:

        1. Proposed repository name: portal/nonrtric-controlpanel
        2. License: Apache 2 
        3. A brief description: This repo will be used for the NONRTRIC GUI – for visualising and manipulating NONRTRIC concepts such as A1 Policies/PolicyTypes supported in RAN, R-APPs, etc.
        4. A list of initial committers:
          a)  John Keeney, John.Keeney@... , lfid: JohnKeeney
          b) Patrik Buhr, patrik.buhr@... , lfid: PatrikBuhr

        Note: NONRTRIC GUI  functionality already exists in nonrtric repo. This new repo will be the new home for this.

        Thank you in advance

        John Keeney

      2. VOTE: On motion made by John Keeney
        1. Seconded by David Streibl
        2. VOTE: Vote taken, item passed
    3. New committers in SIM project - E2 and A1 repos request from Alex Stancu

      1. Dear ToC members,

        I would like to request approval for some committer changes under the SIM project:

        1. sim/e2-interface repository
          • Add new committer, because we want to move the E2 Simulator from INT project to SIM project. Harry is the main E2 Simulator developer, so we need to add him as a committer to the SIM project.
            1. First new committer
              • name: Harry Tran
              • email: tuyen@...
              • company: AT&T
              • Linux Foundation id: harrytran
              • timezone: America/New York (GMT -5)
        2. sim/a1-interface repository
          • Add new committers, because we want to move the A1 stub simulator from NONRTRIC project to SIM project.
            1. First new committer
              • name: 'John Keeney’
              • email: 'John.Keeney@...
              • id: ‘johnkeeney'
              • company: 'Ericsson Software Technology’
              • timezone: 'Europe/Dublin’
            2. Second new committer
              • name: 'Maxime Bonneau’
              • email: ' maxime.bonneau@...
              • company: 'Ericsson Software Technology’
              • id: ‘maximesson'
              • timezone: 'Sweden/Stockholm’

        Many thanks in advance!

        Kind Regards,
        Alex
        O-RAN-SC SIM project PTL

        --
        Alexandru Stancu, PhD
        Senior Software and Telecommunications Engineer

        Skype: stancu.liviualex
        E-Mail: alexandru.stancu@...
        Web: https://www.highstreet-technologies.com

        highstreet technologies GmbH
        Hähnelstraße 6
        12159 Berlin

      2. VOTE: On motion made by Alex Stancu
        1. Seconded by Jinri Huang
        2. VOTE: Vote taken, item passed
  6. Marketing of the Amber release (WG, LF, PR)
    1. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
    2. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
    3. Jinri is plannng the virtual O-RAN demo at the end of this month.
  7. Status of Open Action Items (Old Business)
    1. Action/ Rittwik Jana Start an email chain with Viavi regarding how much will it cost and value are we getting?
      1. Viavi is putting together a proposal.  
      2. Jack - I'd like to see it hosted in the cloud so different teams can use it.  It will easier and open access.  Were they OK with that plan? 
        1. Yes, but there may be a cost associated with it.  Viavi will reach out to Jack and discuss offline.
    2. ActionJinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
    3. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
    4. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
    5. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
    6. Action/William Diego Maza  will talk to the focus group regarding test coordinator for the O-RAN SC.
      1. William - Participated last Monday and will provide more information in the coming meetings.
      2. Jack - David and William touch base with Rittwik regarding the Viavi emulator.
    7. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
    8. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.  Jinri will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
    9. ActionYingying Wang work with Lusheng to create the test cases for O-CU.
    10. ActionTrishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.  
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
    2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
        1. There are about 17 epics where one is listed as done.  
          1. Jinri - there is an issue for the RICApp project.  Jinri will communicate with Matti offline.  Thoralf will respond to Jinri's request regarding the issue.  Matti Hiltunen document the copyrite issues as a part of your ongoing summary of the project.  There is a recording of the RSAC presentation.  
      2. Thoralf Czichy RIC Platform (RIC) 
      3. Yingying Wang O-RAN Centralized Unit (OCU)
        1. ActionYingying Wang update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues.  
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
        1. Have a discussion with Jack regarding the 
      6. Martin Skorupski Operations and Maintenance (OAM)
        1. Will update the pie for non real time RIC.
        2. For OAM we are focusing on Bronze release.  
        3. For NetConf is challenging and we spoke at the F2F client.
        4. Development and deployment for SMO Bronze.  We need better documentation.  In addition we are having public URLs and public service available.
        5. Jinri - Defining SMO functions.  
          1. Martin I am not defining them I am looking at deploying them.
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
        1. 148 issues and tasks. Large number of subtasks have been closed for test coverage and sonar scores.  Jira workflows are different across different projects such as O-RAN.  Our epics span releases. Upcoming sprint we are focusing on use case and design and architecture around rApp.  We will be defining what the rApp is.
          1. Jack - Across the board we need a metric on how many issues tasks are targeted in Bronze.  Suggestions?
          2. John - Trust the feedback from the PTLs that user stories and tasks are being delivered on time.
          3. Tracy is late with setting up the meeting with David Mc Bride.  
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Actions
      1. ActionJinri Huang will share slides to set up projects using the O-RAN SC regarding the Open Data Set project from O-RAN TSC.
      2. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      3. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
      4. Action/ David (DT) we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      5. Action/William Diego Maza  will talk to the focus group regarding test coordinator for the O-RAN SC.
      6. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
      7. Action/ Jack will update the O-RAN SC release timeline with Cherry and D release.  Jinri will provide Jack with the WG2 and WG3 adjusted timeline for Cherry and D release.
      8. ActionYingying Wang work with Lusheng to create the test cases for O-CU.
      9. ActionTrishan de Lanerolle set up a call with Jack and David because the Community asked for a release manager.  
      10. ActionYingying Wang update the Bronze Release (Jun 2020) page with Bronze release epics, user stories, and issues.

2020 02 26

Recording: 2020-02-26_audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl


    Ondřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by William Diego Maza
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
    1. Rittwik add Viavi
  5. Release Votes and Approval
    1. John Keeney  wants to rename his repo.
    2. RIC App approval need to be made.
    3. Portal Non Real time RIC Control panel rename from John Keeney.
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona)
    2. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
    3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. We put in a request for a talk.
      2. Tracy: unofficial: Ericsson, Nokia, Samsung and Comscope submitted a request with AT&T person as a moderator.  We submitted a request for a panel discussion.  Will discuss lessons learned and cross activities.  Proposal references O-RAN SC.
      3. John K has also submitted a talk. 
        1. Jinri - Companies who are had demonstrations MWC can submit their demos to the website.  Action / Jinri Huang work with Farheen to add to events.
        2. Jinri - We had planned lots of items for discussion.  We only scheduled two days plus one joint session with WG1.  We have a lot of items to discuss.  the original plan is to do this week.  We want to hold it off until next week.  
          1. project report from each PTL lasting 10 - 20 minutes.
          2. Collaboration discussion with OAI.
        3. Can we take next Tuesday, Thursday, and Friday the same time as TOC?  We don't expect too much participation with O-RAN WGs.  Suggest we use the 8AM - 9:30 EST, T, W, R,F.
        4. If we have our regular meeting on a Wednesday we will have to use 4 days in a row.  Instead let's dedicate this time slot.
          1. Lusheng - Demonstrations have to be scheduled.  Planning to start next week.
          2. Jack - Let's use this time slot next week to address the critical items.  We will skip the TOC for one meeting.  Let's get the most productive items in the time frame rather than have too many meetings in one week.  Let us figure out the most effective way.
          3. Rittwik - You can use the RSAC timeslot.
      4. John Keeney  is considering an Ericsson for a brief non real time RIC demo.  Tracy will share the details.
  7. Status of Open Action Items (Old Business)
    1. Action/ Rittwik wants to discuss Viavi Emulators.
      1. Viavi is discussing contributions for the test and emulator lab.  After checking internally with the team they will report back next week.  Send Rittwik questions around Viavi contributions.  Licensing and cost.  Jack or Jinri viewpoints?
      2. Jack - Funding is an option but we'll have to ask for additional funding.  The question is how much and whats the value to us.  Whatever we invest in is effectively used by the community.  They want it set up in a community friendly cloud.  Could it be a yearly agreement hosted in the cloud and managed by the integration and test team.  Let's see what the best terms and conditions we can get for the software community to accomplish our goals.  We should ask everyone to comment.  Action/ Rittwik Jana start an email chain .
      3. Rittwik - slides are on the RSAC meetings page.
      4. Tracy - Not sure if O-RAN SC and O-RAN testing labs will share lab facilities.
    2. Jinri wants to discuss F2F. 
    3. ActionFarheen Cefalu update the Events page with the updated virtual meetings.
    4. ActionJinri Huang wants to discuss the Open Data Set .
      1. Big data will be useful for Ai/ML and test.  O-RAN TSC set up a project to open data set.  LF open data set has 3 projects set up regarding opening of data.  What is the mechanism to open data?  LF has already developed an agreement specifying the regulations that we need to comply.  Community data license agreement has been created.
      2. This CDLA has been written into our SC charter.  We can open projects using the CDLA in the O-RAN SC.
      3. China Mobile wants to propose opening the CDLA.  This is a brief introduction.  Action/ Jinri Huang will shared slides to set up projects using the SC.
        1. Jack - we need to form a working activity to spend time talking and thinking it through.  The data is always a rich place for discussions.  The TOC doesn't have enough time to work it out.  We need to report back to TSC what our plans and goals are starting this new effort.  We should go through a process and talk to people and we're doing it right. 
        2. Jinri will provide materials and seek comments.
        3. We should form a spot here of where to put the materials and have the discussion.  Create the TOC on the left side of the tree to give the community a time to participate.
        4. Jinri will use RSAC time to review.
    5. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
    6. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. David (DT) will reach out to someone he knows and let the TOC know next week. 
      2. William Diego Maza  will talk to the focus group.
        1. 4 timeslots for this focus group and they are working on different documentations.  I didn't have time last week to introduce myself.  This afternoon I will introduce myself and be part of a link.
        2. Lusheng - we have software called OTF open test framework.  We are using it for the ETE flows for the health-check.
        3. Jack - Let us figure out how to collaborate.  We'll leave it to you and David.
        4. Zhimin Yuan raised a concern about the ODU Low and test.  Jack instructed Zhimin to work with Lusheng to address their hardware requirements needs.
        5. Lusheng - Zhimin's ask is beyond test but also the building on the platform.
          1. Actually it is software.
          2. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
    7. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      1. Raised issue with aligning.
      2. Jinri - we conveyed this information twice during WG and TSC sessions.  The WG co-chairs have taken this message.  One is WG2 and WG3 we adjusted the timeline with Cherry and D release.
      3. Action/ Jack update the timeline and capturing the information.  Jack will start generating Cherry for his release.
      4. Action/ Yingying Wang work with Lusheng to create the test cases.
    8. Community asked for a release manager.  
      1. We have a request out to the LF for some support on this.  Trishan - will have a discussion with David Mc Bride.  ActionTrishan de Lanerolle set up a call with Jack and David.
    9. Action/ PTLs be prepared to discuss Bronze development sprint 1 demos.
      1. Lusheng will organize the end of sprint demos.
      2. Jack after ever sprint we have demos to reflect the items completed.
      3. Lusheng - We have a review process and only the committers can merge to master.  In open source community we are having contributors who are committers and merging.  Contributors should not merge.
      4. Trishan - There is a +2 process.  
      5. Lusheng we want to have the +2 process an not allow the contributor to merge.
      6. Action/ Trishan de Lanerolle provide status of the 
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
    2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC)
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. (proposed by Thoralf): Any update (compared to last week) on ASN.1 availability from O-RAN (for E2AP) and from 3GPP?
    2. Jack most projects are under Apache but the documentation is under Creative Common 4.  As part of the charter we are an LLC under a series of LLC.  Jack will respond to them.
    3. Thoralf E2AP is the most needed. 
    4. Jinri - tomorrow there will be an E2 call. We can bring this there.
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)

2020 02 26

Recording: 2020-02-26_audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl


    Ondřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Jinri found typos and will discuss with Farheen offline. 
      2. Vote to approve minutes for  
      3. On motion made by Jinri Huang
      4. Seconded by Vincent Danno
      5. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
    1. Rittwik add Beave
  5. Release Votes and Approval
    1. John Keeney  wants to rename his repo.
    2. RIC App approval need to be made.
    3. Portal Non Real time RIC Control panel rename from John Keeney.
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona)
    2. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
    3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. We put in a request for a talk.
      2. Tracy: Ericsson, Nokia, Samsung and Comscope with AT&T person as a moderator.  We submitted a request for a panel discussion.  Will discuss lessons learned and cross activities.  Proposal references O-RAN SC.
        1. Jinri - Companies who are had demonstrations MWC can submit their demos to the website.  Action / Jinri Huang work with Farheen to add to events.
        2. Jinri - We had planned lots of items for discussion.  We only scheduled two days plus one joint session with WG1.  We have a lot of items to discuss.  the original plan is to do this week.  We want to hold it off until next week.  
          1. project report from each PTL lasting 10 - 20 minutes.
          2. Collaboration discussion from OAI.
        3. Can we take next Tuesday, Thursday, and Friday the same time as TOC?  We don't expect too much participation with O-RAN WGs.  8:30 - 9 EST.
        4. If we have our regular meeting on a Wednesday we will have to use 4 days in a row.  Instead let's dedicate this time slot.
          1. Lusheng - Demonstrations have to be scheduled.
          2. Jack - Let's use next week to address the critical items.  We will skip the TOC for one meeting.  Let's get the most productive items in the time frame rather than have too many meetings in one week.  Let us figure out the most effective way.
          3. Rittwik - You can use the RSAC timeslot.
      3. John Keeney  is considering an Ericsson for a brief non real time RIC demo.  Tracy will share the details.
  7. Status of Open Action Items (Old Business)
    1. Action/ Rittwik and Viavi.
      1. contributions for the test and emulator lab.  After checking internally with the team they will report back next week.  Licensing and cost.  Jack or Jinri viewpoints?
      2. Jack - Funding is an option but we'll have to ask for additional funding.  The question is how much and whats the value to us.  Whatever we invest in is effectively used by the community.  They want it set up in a community friendly cloud.  Could it be a yearly agreement hosted in the cloud and managed by the integration and test team.  Let's see what the best terms and conditions we can get for the software community to accomplish our goals.  We should ask everyone to comment.  Action/ Rittwik Jana start an email chain .
      3. Rittwik - slides are on the RSAC meetings page.
      4. Tracy - Not sure if O-RAN SC and O-RAN testing labs will share lab facilities.
    2. Jinri wants to discuss F2F. 
    3. ActionFarheen Cefalu update the Events page with the updated virtual meetings.
    4. ActionJinri Huang wants to discuss the Open Data Set .
      1. Big data will be useful for Ai/ML and test.  O-RAN TSC set up a project to open data set.  LF open data set has 3 projects set up regarding opening of data.  What is the mechanism to open data?  LF has already developed an agreement specifying the regulations that we need to comply.  Community data license agreement has been created.
      2. This CDLA has been written into our SC charter.  We can open projects using the CDLA in the O-RAN SC.
      3. China Mobile wants to propose opening the CDLA.  This is a brief introduction.  Action/ Jinri Huang will shared slides to set up projects using the SC.
        1. Jack - we need to form a working activity to spend time talking and thinking it through.  The data is always a rich place for discussions.  The TOC doesn't have enough time to work it out.  We need to report back to TSC what our plans and goals are starting this new effort.  We should go through a process and talk to people and we're doing it right. 
        2. Jinri will provide materials and seek comments.
        3. We should form a spot here of where to put the materials and have the discussion.  Create the TOC on the left side of the tree to give the community a time to participate.
        4. Jinri will use RSAC time to review.
    5. ActionRittwik Jana update TSC with the short/long term UE emulator support.  
    6. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. David (DT) will reach out to someone he knows and let the TOC know next week. 
      2. William Diego Maza  will talk to the focus group.
        1. 4 timeslots for this focus group and they are working on different documentations.  I didn't have time last week to introduce myself.  This afternoon I will introduce myself and be part of a link.
        2. Lusheng - we have software called OTF open test framework.  We are using it for the ETE flows for the health-check.
        3. Jack - Let us figure out how to collaborate.  We'll leave it to you and David.
        4. Zhimin Yuan raised a concern about the ODU Low and test.  Jack instructed Zhimin to work with Lusheng to address their hardware requirements needs.
        5. Lusheng - Zhimin's ask is beyond test but also the building on the platform.
          1. Actually it is software.
          2. Action/ Lusheng follow up with Zhimin offline to set up target architecture for ODU Low.
    7. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      1. Raised issue with aligning.
      2. Jinri - we conveyed this information twice during WG and TSC sessions.  The WG co-chairs have taken this message.  One is WG2 and WG3 we adjusted the timeline with Cherry and D release.
      3. Action/ Jack update the timeline and capturing the information.  Jack will start generating Cherry for his release.
      4. Action/ Yingying Wang work with Lusheng to create the test cases.
    8. Community asked for a release manager.  
      1. We have a request out to the LF for some support on this.  Trishan - will have a discussion with David Mc Bride.  ActionTrishan de Lanerolle set up a call with Jack and David.
    9. Action/ PTLs be prepared to discuss Bronze development sprint 1 demos.
      1. Lusheng will organize the end of sprint demos.
      2. Jack after ever sprint we have demos to reflect the items completed.
      3. Lusheng - We have a review process and only the committers can merge to master.  In open source community we are having contributors who are committers and merging.  Contributors should not merge.
      4. Trishan - There is a +2 process.  
      5. Lusheng we want to have the +2 process an not allow the contributor to merge.
      6. Action/ Trishan de Lanerolle provide status of the 
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
    2. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC)
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    3. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. (proposed by Thoralf): Any update (compared to last week) on ASN.1 availability from O-RAN (for E2AP) and from 3GPP?
    2. Jack most projects are under Apache but the documentation is under Creative Common 4.  As part of the charter we are an LLC under a series of LLC.  Jack will respond to them.
    3. Thoralf E2AP is the most needed. 
    4. Jinri - tomorrow there will be an E2 call. We can bring this there.
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)

2020 02 19

Recording: 2020-02-19-toc-audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    xOndřej Hudousek

    NTT DOCOMO

    Masafumi Masuda


    Anil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar


    Skand Priya

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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by Jinri Huang
      3. Seconded by David Streibl
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
    1. Open Data Set
  5. Release Votes and Approval
    1. Outstanding request from Thoralf, Matti, and John Keeney for a new repos
    2. John Keeney  wants to rename his repo.
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona)
    2. O-RAN Alliance  Feb 17-21 (Paris) F2F canceled and now virtual meeting schedule published
    3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. ActionFarheen Cefalu update the Events page with the updated virtual meetings.
  7. Status of Open Action Items (Old Business)
    1. ActionJinri Huang Open Data Set
    2. O-RAN Alliance spec license restriction for ASN.1 spec (raised by Thoralf)
      1. Jack has been talking to Stephan (O-RAN Alliance lawyer) to address the O-RAN Specification copyright in the O-RAN SC.  There are discussions going on an alliance with TIP and with TMC. 
        1. From 3GPP we have submitted several requests about copyright usage.  We've submitted requests twice and they've come back for more clarification.  We are working through the standards groups to get done.
    3. O-RAN Alliance spec license restriction for Yang model (raised by Martin)
      1. Jack: Is it a copyright issue?
        1. Martin: Yes, not clear how to use 3GPP data models 
          1. 3GPP models are broken from syntax and how can we fix them?  By working group 1 license statement. Latest ask by 3GPP is still not addressing our needs.  Next version coming out in March is not useful and I can'tuse them in the Bronze.
            1. Are you using them as a baseline?
              1. We have modified once and found we are not allowed to modify.
              2. We demonstrated at one event but I can not share the modeified ones with the public.
              3. Likelihood high that all has to be modified and tested.
              4. Clear statement that O-RAN Alliance should use and influence 3GPP but 3GPP is not used in the software community.
              5. Any comments or thoughts?
                1. Tracy: Thinks this topic will be discussed during WG1 modeling discussion at 5PM EST today.  The goal is to getting this resolved but it's organizationally complicated across 3GPP and the O-RAN Alliance.  
                2. Martin: I am careful in selecting to avoid future issues.
              6. Jack: There needs to be an abstraction layer.  Once solved every time there is a change to the system doesn't it have to cascade through these layers. 
                1. Martin: The model was supposed to be the abstraction layer you will have a model on a model with a 1:1 relationship.
                  1. Jack: We're running into problems because we're tying to specifications that were never validated.
                    1. Martin: That is why I am selecting young data models.  But the RAN specific stuff will be problematic.
    4. Action/ Lusheng Ji  send a reminder to the PTLs to update their projects Architecture page within on their wiki pages (near-RT RIC: done, ...)
      1. Reminder sent.  Jack will verify progress.
    5. Action/ PTLs get your F2F slide decks ready.  Due  
    6. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      1. Viswa provided 
    7. ActionJinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
      1. We will be notified on  
    8. ActionRittwik Jana talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys

    9. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.

      1. closed
    10. ActionRittwik Jana update TSC with the short/long term UE simulator support.  

      1. Rittwik: initial meeting done, waiting on hearing what Viavi can bring to the community.  will follow up with Viavi.   Need a Packer Core simulator, UE simulator, RAN simulator, Viavi has all.  Really need the full suite of simulator to complete simulating UE actions.
      2. Jack: will pick up in future meetings, May create a track under integration and testing to continue.  what to be done here what under TFIG.
    11. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. Jack: We need to interface with the test group so that we have coordination.  Not doing test plans.  
        1. David (DT) will reach out to someone he knows and let the TOC know next week. 
        2. William Diego Maza  will talk to the focus group.
          1. Jack: it won't be as extravagant as the test group has. 
    12. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      1. Rittwik: KPI Mon xApp requests certain metrics coming form O-CU. 
      2. Yingying: O-CU will focus on U plane.  No contribution on RRC part.  UE attachment will be a problem in B release.  E2 still under discussion with main contributor.  E2 will be discussed in following weeks in WG8
      3. Jung/Rittwik: O-CU not advanced enough to provide enough metrics to support traffic steering.  Fallback plan needed, enhancing E2 simulator to provide enough support.  Can SIM project support this?  Otherwise traffic steer is in jeopardy. O-DU has a plan to support.  But need O-CU support as well.  Need ToC decision on the fallback plan.
      4. CoChairs: Construct document for what's missing.  Is this possible in Cherry or even further out?
      5. Rittwik:  RSAC to provide document on what's current, what's future, suggesting alternatives.
      6. Jack: It will be  a weak message if this cannot be supported.
      7. Second use case (healthcheck) Non-RT RIC making progress 
      8. Action: Allocate a time slot next week to discuss.
        1. Yingying:  We will have the GUI meeting in an hour
          1. The challenge is this is around the ETE traffic steering use case and how it will work with O-CU and O-DU development. 
    13. Action / PTLs Update your section of the Bronze Release (Jun 2020).  Convey to people outside what we're going to do in this release.
      1. Lusheng: reminder sent.  only three projects which have not completed yet.
      2. Jack: Need to be done by Friday.
    14. ActionTracy Van Brakle send the URL of where on the wiki you posted the POC plugfest through lists.o-ransc.org.  
      1. Tracy will double check the O-RAN-SC wiki.  
    15. Community asked for a release manager.
      1. Jack: will keep looking for an option.
        1. Tracy - we'll have a call with David McBride who has served as release manager for many LF projects.  He is a part of LF.  He works on ONAP and ODL.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
        1. Action/ PTLs be prepared to discuss Development sprint 1 demos.
        2. Lusheng: For dev sprint 2 we will have a demo.  Asking PTLs to prepare for post sprint demos.  Lusheng will send out Jira tickets and coordinate.
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
        2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. Someone mentioned a TOC meeting.  When was that scheduled?  
      1. Jack: We had Tuesday, Thursday, Thursday.  I don't have the time for the Monday meeting.
      2. John Keeney Can someone add some slides to do offline reading?  It will be helpful.
      3. Jack will talk to Jinri
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.
    1. Votes:
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Vote to approve minutes for  
        2. On motion made by Jinri Huang
        3. Seconded by David Streibl
        4. VOTE: Vote taken, item passed
    2. Actions:
      1. ActionFarheen Cefalu update the Events page with the updated virtual meetings.
      2. ActionJinri Huang wants to discuss the Open Data Set .
      3. ActionRittwik Jana update TSC with the short/long term UE simulator support.  
      4. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
        1. David (DT) will reach out to someone he knows and let the TOC know next week. 
        2. William Diego Maza  will talk to the focus group.
      5. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      6. Community asked for a release manager.
      7. Action/ PTLs be prepared to discuss Bronze development sprint 1 demos.

2020 02 12

Recording: toc-20200212-audio_only.m4a

Agenda

  1. Call for Scribe (minutes owner) Lusheng Ji
  2. Roll Call & Quorum Check 

    Company

    Contact Name

    Attendance

    Alternate Contact

    Attendance

    AT&T

    Jack Murray Co-Chair

    Y

    Lusheng Ji

    China Mobile

    Jinri Huang Co-Chair

    YWeichen Ni

    Deutsche Telekom 

    David Streibl


    Ondřej Hudousek

    NTT DOCOMO

    Masafumi Masuda

    YAnil Umesh
    Orange

    William Diego

    YVincent Danno

    Viswa Kumar




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

  3. Review and Agree to Minutes of Previous Meeting

    1. Moved by Jinri, Seconded by William, passed.
  4. Review of Today's Agenda
    1. Jung requested item on discrepancy between WG3 and Near RT RIC PLT: added item 9.a
    2. Jinri requested  item on Open Dataset project: added item 9.b
  5. Release Votes and Approval
    1. None
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona): AT&T will not attend; China Mobile will not attend; NTT will not attend. 
    2. O-RAN Alliance F2F Feb 17-21 (Paris): F2F may be cancelled or changed to virtual.
    3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
  7. Status of Open Action Items (Old Business)
    1. Action/ Lusheng Ji Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
      1. Closed
    2. Action/ Lusheng Ji  send a reminder to the PTLs to update their projects Architecture page within on their wiki pages (near-RT RIC: done, ...)
      1. Reminder sent.  Jack will verify progress.
    3. Action/ PTLs get your F2F slide decks ready.  Due  
      1. Jinri: alternative plan is work in progress, no decision yet.  If virtual, will mimic the schedule of f2f meeting. 
    4. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      1. Waiting for action by Viswa
    5. ActionJinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
      1. Tracy: Ericsson et. al. submitted panel discussion proposal for sharing 2019Dec PoC results and plan for 2020Jun PoC.
      2. Closed (will update community after LF result)
    6. ActionRittwik Jana talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys

    7. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.

      1. closed
    8. ActionRittwik Jana update TSC with the short/long term UE simulator support.  

      1. Rittwik: initial meeting done, waiting on hearing what Viavi can bring to the community.  will follow up with Viavi.   Need a Packer Core simulator, UE simulator, RAN simulator, Viavi has all.  Really need the full suite of simulator to complete simulating UE actions. 
      2. Jack: will pick up in future meetings, May create a track under integration and testing to continue.  what to be done here what under TFIG.
    9. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      1. CoChairs: Invitation also extended to the 3 upcoming new ToC members as well.
      2. Jack: The only way to ensure software aligned as intended is through testing.  This is important.
    10. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      1. Rittwik: KPI Mon xApp requests certain metrics coming form O-CU. 
      2. Yingying: O-CU will focus on U plane.  No contribution on RRC part.  UE attachment will be a problem in B release.  E2 still under discussion with main contributor.  E2 will be discussed in following weeks in WG8
      3. Jung/Rittwik: O-CU not advanced enough to provide enough metrics to support traffic steering.  Fallback plan needed, enhancing E2 simulator to provide enough support.  Can SIM project support this?  Otherwise traffic steer is in jeopardy. O-DU has a plan to support.  But need O-CU support as well.  Need ToC decision on the fallback plan.
      4. CoChairs: Construct document for what's missing.  Is this possible in Cherry or even further out?
      5. Rittwik:  RSAC to provide document on what's current, what's future, suggesting alternatives.
      6. Jack: It will be  a weak message if this cannot be supported.
      7. Second use case (healthcheck) Non-RT RIC making progress
      8. Action: Allocate a time slot next week to discuss.
    11. Action / PTLs Update your section of the Bronze Release (Jun 2020).  Convey to people outside what we're going to do in this release.
      1. Lusheng: reminder sent.  only three projects which have not completed yet.
      2. Jack: Need to be done by Friday.
    12. ActionTracy Van Brakle send the URL of where on the wiki you posted the POC plugfest through lists.o-ransc.org.  
    13. Community asked for a release manager.
      1. Jack: will keep looking for an option.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
        1. Repo requests on mailing list from RICAPP and Non RT RIC
      2. Thoralf Czichy RIC Platform (RIC) 
        1. How to use ASN1 spec from O-RAN Alliance, due to its restrictive licensing requirements. 
          1. Martin: same problem for OAM, yang model from O-RAN Alliance is not open.
          2. Jack: on-going with O-RAN Alliance legal on permissions.  To add agenda item next week (added as 10.a and 10.b)
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. Jung: WG3 co-chairs, discrepancy between Near RT RIC PLT and WG3.  WG3 completed E2 spec R1, approval coming this week.  R2 work starts immediately after, to be complete by 3Q20.  Bronze (end of 2Q20) will be E2 R1 or E2 R2 pre-release?  How to support traffic steering because needed features not in R1.
      1. Jack: if R2 completes by 3Q, it will not be in Cherry because it misses planning window.  Need more structured naming since as minor versioning.  Features may be available at minor revisions. 
      2. Jung: there should be a regular channel to exchange requirements. 
      3. CoChairs: OSC have people attending WG3 regularly.  Rarely get feedback from WG3.  We need more feedback from WG3
      4. Jung: Need written feature request.
      5. Jack: Need a table for communicating the structure, which version of spec / feature to implement.  Also need firm dates on when the spec is needed by to be included in an OSC release.
    2. Jinri: Open dataset
  10. Planning for Next Meeting
    1. O-RAN Alliance spec license restriction for ASN.1 spec (raised by Thoralf)
    2. O-RAN Alliance spec license restriction for Yang model (raised by Martin)
  11. Any Other Business (AOB)
  12. Meeting Summary (resolutions, new action items, etc.)

2020 02 05

Recording: 2020-02-05-toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. Roll Call & Quorum Check 

    Company

    Contact Name

    Attendance

    Alternate Contact

    Attendance

    AT&T

    Jack Murray Co-Chair


    Lusheng Jix

    China Mobile

    Jinri Huang Co-Chair

    xWeichen Ni

    Deutsche Telekom 

    David Streibl




    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar




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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by Masafumi Masuda
      3. Seconded by William Diego Maza
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    • Maintenance window closed last Saturday.  Lusheng asked PTLs to update their information.  
    • Action/ Lusheng Ji Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
    • Is there a doc meeting required for the maintenance release?
      • The docs project will automatically update the documentation.
    • Except for the Amber Maintenance (Feb, 2020) updates the maintenance release is complete?
      • Bug fixes.
      • Unfinished features had an opportunity to be completed.
    • Motion made by Lusheng Ji to approve the Amber maintenance release on  
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona)
      1. Jinri - More about O-RAN Alliance demo.
        1. for this year O-RAN Alliance will have 23 demos which will be scattered from different sponsors.  This is a large number considering O-RAN Alliance opened it's membership 1.5 years ago.  It already had 150 members.  There are 26 operator members.
        2. O-RAN does not have it's own dedicated booth.
    2. O-RAN Alliance F2F Feb 17-21 (Paris)
      1. Jinri - will have to leave in 10 minutes for an adhoc TSC meeting regarding the current tense situation caused by the Corona virus in China. The F2F may be changed to an online virtual meeting or have the attendees meet remotely.
      2. For the TOC meeting Agenda 
        1. Take an opportunity to introduce our Bronze release.
        2. Require the PTLs to bring their project status report for the discussion.  PTLs can introduce additional functionality in order to support the Bronze release.  What is the current status, challenges, and architecture.
        3. Bring your alignment with the working groups in particular WG3.
        4. Jinri will bring brief TSC reports from TOC.
        5. When and where will we know about the decision about the F2F.
        6. Do we simply point to the Jira tickets or should we have a slide deck?

          1. Slide decks are preferred because they will distributed to other O-RAN Alliance WGs.  This is a good opportunity to share your accomplishments with the WG.  Looking for design, timeframe, challenges, and most importantly WG alignment.

          2. Two weeks to go for F2F so we need to prepare.

        7. Action/ PTLs get your F2F slide decks ready.  That is in 3 days.

    3. ONES = LF Networking Conference in April (Los Angeles).  Open Networking & Edge Summit Event
 
      1. Ericsson submitted a proposal for a panel discussion that will discuss the results in Amber plugfest.  Confident that the proposal will be accepted.  We are trying to get visibility for OSC-Amber and get everybody excited about OSC Bronze.
      2.  Jinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
  7. Status of Open Action Items (Old Business)
    1. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.

    2. Action / TOC voting members: Provide an alternate contact on the TOC list above.

    3. ActionThoralf Czichy update the TOC with the new Nokia TOC members.

    4. ActionRittwik Jana talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys.

    5. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.

    6. ActionRittwik Jana update TSC with the short/long term UE simulator support.  

      1. He has been talking to members regarding feasibility but not sure if he has gotten commitment for it.
      2. ENGWEI KOO - Rittwik Jana asked Engwei to join.  We created a slide to better understand the UE simulator.
      3. Shared a high-level slides.
        1. We are looking for the O-DU, O-CU generating messages to the real time RIC.
        2. Engwei - Are you looking for OCU simulator that's connected to 
        3. We need emulator UE KPIs that represent the RF signal strengths of neighbors so we can predict based on signal strength whether the UE quality of experience from a neighbor or serving cells.  We need those measurements and KPIs.  Cell utilization metrics are also needed.  
        4. Engwei set up a call with Rittwik Jana
    7. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.

    8. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.

    9. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.Take a look at the template and fill out what you can.  If you don't have information then let Martin know.

      1. PTLs provide general or any kind of alarms 
    10. Action / On the Bronze release page update their table.  A few have but I would like everyone to begin filling out their tables.  Convey to people outside what we're going to do in this release.

    11. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.

      1. Readout June 25 and as we get closer we'll have a project plan.  We are focusing on two first responder scenarios.  Tracy posted the slides on the wiki.
      2. ActionTracy Van Brakle send the URL for the POC plutfest through lists.o-ransc.org.  
    12. Action/ PTLs update Architecture pages.

      1. Lusheng Ji  send out a reminder to PTLs.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release - is closed
      2. Project Bronze Release
        1. Working with LF on the CI/CD pipeline.  Contact Lusheng Ji if you have trouble with the CI/CD pipeline.  Jenkins server has been acting up.
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
        2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. Intel contributions - Jack is working with legal issues with binary contributions. C++ compiler to build G++ for Amber.  The G++ performance is not as high as Intel.
    2. Formalizing structure for release management.
    3. We need a release manager.
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes 
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Vote to approve minutes for  
        2. On motion made by Masafumi Masuda
        3. Seconded by William Diego Maza
        4. VOTE: Vote taken, item passed
      2. Motion made by Lusheng Ji to approve the Amber maintenance release on  
    2. Actions
      1. Action/ Lusheng Ji Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
      2. Action/ PTLs get your F2F slide decks ready.  Due  
      3. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      4. ActionJinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
      5. ActionRittwik Jana talk to Jack to send out an email to the new TOC members; Nokia, Ericsson, and Radisys.

      6. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.

      7. ActionRittwik Jana update TSC with the short/long term UE simulator support.  

      8. Action/ TOC we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups.
      9. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      10. Action / PTLs Update your section of the Bronze Release (Jun 2020).  Convey to people outside what we're going to do in this release.
      11. ActionTracy Van Brakle send the URL of where on the wiki you posted the POC plugfest through lists.o-ransc.org.  
      12. Action/ Lusheng Ji  send a reminder to the PTLs to update their projects Architecture page within their spaces on the wiki.
      13. Community asked for a release manager.

2020 01 22

Recording: 2020-01-22_toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar




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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by David Streibl
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    1. No approvals this week
  6. Marketing of the Amber release (WG, LF, PR)
    1. Upon Maintenance release  we will do a small notification of Bronze features.
      1. Jinri - PM is preparing PR before MWC.  We can enter a few sentences there.
        1. Jack - Agrees
        2. ActionJinri Huang add a few lines to MWC.
          1. I need assistance.
          2. Paul Smith - we are going to be making additions to the PR.  We need changes as soon as possible.
          3. Jack - the maintenance release doesn't have any features.
            1. Lusheng from integration there is a bug fix.
              1. Jack - Bugs are not something we want to report.
              2. Is there anything in doing the plugfest?
                1. Martin - Not for the Amber release 
                2. Jack - we are not going add a few lines.
    2. MWC (Barcelona)
      1. Gate 2 MWC demos.  16 demos.  There are 3 demos that can feature the bronze release elements.  I requested sponsors to include the software community demo whenever appropriate.
        1. Jun Hyuk Song  wants to see the which demos have the Bronze elements. 
          1. Jinri - 2 or 3 demos out of 16 are demonstrating SC.  It will be on the o-ran alliance wiki.  Paul may be putting this demo on their wiki.  If it urgent for you then please reach out to Paul.
          2. David Kinsey - A1 is mis-leading
            1. We refer to it as O1-A1 functionality. David and Tracy will talk offline.
    3. O-RAN Alliance F2F Feb 17-21 (Paris)
      1. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
      2. Jinri requested PTLs to report their progress during the F2F meeting.  
        1. There is status of what's been established and the plan of what is in Bronze.  
          1. Focus on the plans for Bronze.  We will arrange 1/2 hour for each project.  
            1. Jack encouraging everyone to be engaged in communicating the message of Bronze.
            2. That every element in the stack and be built and deployed by the LF toolbase and the second ETE use case can be exercised the way it is supposed to function.  Rittwik has defined what use case will be exercised in the Bronze.
            3. John Keeney  and Tracy Van Brakle  and Martin Skorupski we want to articulate what we are targeting to release in Bronze.  We need to reduce that to a written objective now that we are closing our use cases. 
              1. Rittwik as a part of closing this use case we need a clear two paragraph message that articulates what the community can expect out of the use case.  This is an executive summary more than technical details.  2 paragraph executive summary.  Whatever we've agreed to has to be documented.  We have concerns that we won't progress far enough on the use cases but we should agree on what we are going to do in Bronze.  Less about negotiation and more about what we have agreed to what the target is.
            4. John Keeney , Martin Skorupski , Xiaohua Zhang , David Kinsey (covering for Rittwik), KJ - Kaustubh Joshi
    4. ONES = LF Networking Conference in April (Los Angeles).  
      • Open Networking & Edge Summit Event
 
        • CFP is closing Feb 3, Monday.  This is the primary networking event for the Edge group Akraino, 
        • Can we recycle the demos in MWC.
          • Is anyone planning to have a booth there?
            • Trishan - Is there interest in doing a stand alone O-RAN booth?
              • Jinri - We can use our partners booth such as O1-A1 demo by AT&T and Ericsson.  Will Hank be there?
              • We have to decide if we want him to propose a talk.  If yes, then Jack will ask Hank.  It seems at this time 
  7. Status of Open Action Items (Old Business)
    1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      1. Jack will share an update next week for the ECs recommendation on the path forward.
    2. ActionRittwik Jana send Alex Stancu contact for UE simulator support.
      1. Rittwik - Asked Alex to reach out.  Martin Skorupski we are in contact VeeAvi (sp?).  For UE's we will need hardware which is difficult to acquire.
      2. We need to find out what is the UE agenda.  The O-DU project should see how they are testing the O-DU.  We have to see if the actual UE simulators can be used to test O-CUs.  
        1. Jack - You will need a UE and a radio emulator.
          1. Yes, I need a server that emulates a UE.  You don't need RF equipment for this.
          2. This is an important topic and key issue.  Which raises, we need better coordination with the test focus group in O-RAN.  I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.  It will take a commitment from TOC to spend time on the subject.  Jinri is doing the PR work.  If one of the other TOC can take on the role of coordinating with the test group.  It is an important activity that will require coordination between the development and test teams.  If we are going to coordinate on a UE simulator then the test group should also come up with someone. 
          3. Action / Farheen add to next weeks agenda
    3. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
      1. Jack - Look at negotiating with the working groups about our needs.  I let the EC know that it is harder to maintain momentum in the second release due to exhaustion from the first release.  We need to keep advancing.  The first 3 or 4 releases are critical to the success.
      2. Jinri - we can remind the working groups at the F2F meeting.
      3. Rittwik - Reached out to WG8 RCU about supporting hand over for OSC.  Their answer is negative.  O-Cu feature won't be ready until Cherry release.  
        1. Be cautious that for Cherry release it has to be executable.  It is too late to plan at the Cherry release.
    4. ActionLusheng Ji set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
      1. Sorting out Intel's contribution for license.  Lusheng will look into that.  Intel API interfaces and loader are a part of the SC.  They allow someone to take their software.  Not compatible with SC licenses.  Jack will be meeting with Stephan (Intel) that O-RAN can use their software for testing but is not an approved open source software.  It is a testing apparatus that we can load.  We still have a gap on what constitutes a layer 1 open source contribution.
    5. ActionLusheng Ji send Trishan de Lanerolle and email with the question regarding the license discrepancy.
    6. ActionMartin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
      1. Martin Skorupski : posted: Bronze use case: Health-Checkhttps://lists.o-ran-sc.org/g/main/topic/bronze_usecase_heathcheck/69880291?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,69880291
      2. Any question talk to Martin
    7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
      1. If there are one or two alarms already known then inform Martin Skorupski
      2. Martin will be flexible about the alarm formats, etc.
    8. Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
    9. Rittwik - OAI fell off the list.  We had a meeting with OAI.  
      1. Christian (Orange) - Drafted the open interface license with Nokia to understand the differences between OAI and 
      2. Christian - OAI across systems to provide something related to E2 service model.  Not directly open interface focused but Eurocom (sp?) funded Mosaic 5G within this is a flexran project.  Flexran is related to near real time RIC in O-RAN world.
      3. Mohamed (Orange) - As a part of my work on 5G RAN i investigated FLex-RAN.  Flexor and controller is an implementation of near real time RIC.  If you want to manage the schedule then control or manage the CU or DU.  For southbound there is a embedded agent within the source code for enode gnode B.  To perform near real time operations on open interface.  Available under Apache 2.0 license. 
      4. It is a brief description of what we can do with Flex-RAN.  If you need it we could organize a presentation for the F2F
      5. Action / Farheen put this back on the agenda.  In terms of licensing we can set up parallel meeting times.
      6. http://mosaic-5g.io/flexran/
    10. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
    11. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
    12. Action/ PTLs update Architecture pages.  
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
      2. Project Bronze Release
        1. Thoralf Czichy proposes that near-RT RIC platform functionality (content) freeze is Feb-7. This is as there's a near-RT RIC platform contributor planning f-2-f workshop planned Feb-3 to Feb-5. Bronze Timeline doesn't have an exact date (drawing suggest in week of Feb-3 to Feb-8). Preliminary content is here: filter10401.
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
        2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes:
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Vote to approve minutes for  
        2. On motion made by David Streibl
        3. Seconded by MASAFUMI MASUDA
        4. VOTE: Vote taken, item passed
    2. Actions
      1. Action/ Jinri Huang add a few lines to MWC.
      2. Action/ Farheen - Get the information from Jack and put it on the events page of the wiki.
      3. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      4. ActionRittwik Jana send Alex Stancu contact for UE simulator support.  
        1. we need better coordination with the test focus group in O-RAN.  I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.
      5. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      6. ActionLusheng Ji set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
      7. ActionLusheng Ji send Trishan de Lanerolle and email with the question regarding the license discrepancy.
      8. ActionMartin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
      9. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
      10. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
      11. Action/ PTLs update Architecture pages.  

2020 01 15

Recording: 2020-01-15-toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar

    x

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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by Jinri Huang
      3. Seconded by David Streibl
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    1. No approvals this week
  6. Marketing of the Amber release (WG, LF, PR)
    • MWC (Barcelona)
      • WG1 are correcting a list of demos for MWC compared to last year there were 6 demos.  This year we have collected 16 demos.
      • 2 demos are related to SC. 
        • A1 PoC
        • Edge Cloud Platform (AT&T and Nokia).  Release A is demonstrated in this PoC.
        • Jun Song (Samsung) has a demo to offer for the RIC platform.
          • Submitted to WG3 video for Network slicing.
        • For MWC PoC.  Next Monday there will be a gate to review the PoC.
      • Feb 25 9:30 - 10:45 event Dutch Telecom will have a briefing.  In an auditorium with 200 seats.  Agenda will have the key chair of O-RAN Alliance, Dutch Telecom Executive, China Mobile Co-Chair (Jinri).
    • O-RAN Alliance F2F Feb 17-21 (Paris)
      • Do we have the schedule on the web site so people know when our meetings are.
      • For the TOC will be Tuesday and Thursday evening in Paris.  Those are two sessions.  
    • ONES = LF Networking Conference in April (Los Angeles).  
      • Open Networking & Edge Summit Event
 
      • 2020-02-03 deadline for proposals.  Planning on having a small kiosk or booth for demos.
      • Next weeks meeting is the deadline for raising interest.  Talk to you companies and teams and reach out to Jinri and Jack and let them know what your interests are.  We have to decide how much we want to participate.
      • It will have ONES participation.  Including Akraino and ONAP.  We need EC to be aware of this event to enhance this collaboration.  It is a smaller event to have more interaction.
        • Look for feedback between now and next week.
        • Action/ Farheen add this to next weeks agenda.
        • Action/ Farheen ONES. Correct the entry for LF Networking event to LF. Networking: Open Networking & Edge Summit (formerly Open Networking Summit)
.
  7. Status of Open Action Items (Old Business)
    • Action / TOC voting members: Provide an alternate contact on the TOC list above.
      • Action/ Farheen get Masafumi's backup from Jack.
    • ActionRittwik Jana Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      • First meeting with Christian and his counterparts was held last week.
      • E2 traffic steering model needs to be approved by WG3. O-CU and O-DU handoffs won't happen until the Cherry release.  Another is healthcheck.
        • Is this advancing the software and moving the community forward?
        • Concern that we may have to add another use case to develop another aspect of the software.  How much do we advance in each release.  One thing that blocks should not prevent us from moving forward.
          • Hampered by the O-CU O-DU profile timeline alignment with OSC is tricky.  They have their timeline already that doesn't align.
            • Can we enrich the use case around some other functionality that is advancing.
          • O-CU and O-DU have to step up and what value they can add.
            • Can we develop a better set of detailed and expanded data so we can have a complete set?
            • How complete of data collection can we do in this release.
          • Steering use case.  Cu and DU should implement the E2 interface.  There were attributes and KPIs identified for modules.  That document needs to be reviewed so that it is clear to CU and DU.
            • We need to see how we can get the data into CU and DU but we don't have SMO support for that.
              • Challenge is getting the data out of those devices at performance levels.  First step is to acquire it and manage it.  The next step is to deliver it to the upstream layers.
                • We don't have any in 01 or ONAP or SMO to do real time PM.  We need to get leverage against ONAP and O-1 team to define those interfaces in support of non-RT RIC.  Or we do that work ahead of specs which leads to problems. 
                  • Get that proposal.
            • Rittwik - O-DU and O-CU teams have to get together for the traffic steering use case.  
            • Sachin - Call flow is not listed for a simple traffic steering use case.  As a first step we should look at a simulator based approach.  Simply simulate the use case and then the CU and DU can adopt that simulators results.
            • The use case lists KPIs but doesn't list which one is for CU and what is DU.  The document we have today is an extensive list of KPIs to use and how training will take place.  We don't know how to get it to the SMO.  We don't need to use ONAP for now.
              • Jack asking the team to figure out how best to advance these features in the B release.  Expecting O-CU and O-DU to support the other healcheck use case.  Expecting a minimum software element with O1 communication.  The team can decide how extensive it is.  Second use case know that we've deployed every element in the stack and validate that it is running.  This is a necessary first step to deploy all the pieces.
    • ActionJinri Huang provide an answer to Rittwik Jana regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
      • We had a meeting with CM, Radisys, Intel
      • Rittwik has not heard back about simulator.
        • Call to community:  What are we doing about a UE simulator.
        • Rittwik - we can have one or two cell phones.  But not sure that is possible in bronze release. You have to have many UEs in multiple cells.  It's OK to do unit tests but to test in full force we have to do it with a simulator.
          • Martin Skorupski  will use cell phones instead of a simulator for Bronze release.
    • ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
    • Action/ O-CU and O-DU PTLs and RSAC to get together regarding the end to end steering use case jeopardy. 
    • Action/ Community to address the UE simulator jeopardy on this TOC call.
    • Action/ PTLs enter epics from Contributions into jira.
      • Thoralf - see section 8c below.  This will happen next week to discuss.  Having trouble with the traffic steering use case.  Don't see how the traffic steering use case fits with near RT RIC.  Healthcheck of the different interfaces will be entered this week into jira.  We will have a list on the meeting after next week.e
      • Matti - Use case details are evolving.  
      • Sachin - Expecting Jira stories to be in Jira by next week.
      • Zhimin - Yes we put the O-DU tasks in Jira.  
        • Lusheng - discussed at the end of last release.  Issue is to compilation in LF.  The licensing is different.  We will need some legal council on this matter.
        • Jack - Have a meeting.  ActionLusheng Ji set up a call with John MurrayTrishan de LanerolleJinri Huang.  We want to make sure we can do the logging.  Take it to another meeting.  ActionLusheng Ji send Trishan de Lanerolle and email with the question.
      • Martin - Common data models from WG4 and how to make it available for the software community.  We want to continue what John Keeney did called an SMO that can be deployed.  What the SMO should look like.
        • Focus on what the distribution of an SMO will use for our work in Bronze and then we will update it for Cherry.  Lusheng and team for integration and the O-RAN test community.  When you listed the alarms, is that the same as all the error messages?  Software will generate error messages but we don't gather that info. 
          • If they report according to the ONAP standards then VES collector will display the alarm list.
            • Each piece of software needs to gather their alarms and be documented.
              • Yes.  that is in my proposal.
              • Every PTL come up with a list of alarm names, and document it.  That can be translated to VES message formats.
              • Jack asking people to use spreadsheet.
          • ActionMartin Skorupski will provide the PTLs a template spreadsheet for alarms.
          • Speaking to Chris Lott about portal and dashboard discussion.
      • Alex - Simulator project will have epics.  
        • Jack - We need to know what Simulator is focusing on.
      • Xiaohua - Epics are in jira.  Trying to finish by the end of next week.  Community members can read up.
      • Wei Chen - no epics
      • John K. - Traffic steering functionality at the SMO level is happening.  Getting closer to entering but needs more time.
    • Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
    • Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
    • ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
    • Action/ PTLs update Architecture pages with the Bronze release features they plan to deliver.  
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
      2. Project Bronze Release
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
          1. note that from traffic steering epic/use case I did not see any use cases that fit to the near-RT RIC platform
          2. multiple meetings related to health check epic subitems still be created in JIRA related to E2,A1,O1 health check and related to self-monitoring and alarm management.
          3. what is this item about (from Bronze spreadsheet): "RAN NE to support Dynamic Data Collection (DDC) Measurement Intervals"
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Vote to approve minutes for  
        2. On motion made by Jinri Huang
        3. Seconded by David Streibl
        4. VOTE: Vote taken, item passed
    2. Actions
      1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
      2. ActionRittwik Jana send Alex Stancu contact for UE simulator support.
      3. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
      4. ActionLusheng Ji set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
      5. ActionLusheng Ji send Trishan de Lanerolle and email with the question regarding the license discrepancy.
      6. ActionMartin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
      7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
      8. Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
      9. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
      10. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
      11. Action/ PTLs update Architecture pages.  

2020 01 08

Recording: 2020-01-08_toc.mp4

Agenda

  1. Call for Scribe (minutes owner) Farheen Cefalu
  2. 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 Nix

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda

    x

    Orange

    William Diego

    xVincent Danno

    Viswa Kumar




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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by weichen ni
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval:
  6. Marketing of the Amber release (WG, LF, PR)
    1. There is work going on for demos.  Jinri is collecting material.  This is an O-RAN activity.
    2. LF Networking Conference in April.  If people are planning on attending please reach out to Jack or Jinri.  This will be in LA.  Feb 3rd deadline for proposal.  Planning on having a small kiosk or booth for demos.
      1. Tracy - The work we did for the plugfest is on the LFN program this month.  That is not a big event. This is for developers.
        1. Action/ Tracy Van Brakle will send info on LF Networking to Jack and add the event to our wiki.
  7. Status of Open Action Items (Old Business)
    • Action / TOC voting members: Provide an alternate contact on the TOC list above.
      • Jinri to send out email.
    • Action / Tracy Van Brakle and Martin Skorupski to align and document the plugfest plan for a demo video.
      • There is a press release on O-RAN wiki for this event that went out.  They are waiting for the press release.  The executive committee will let us know in the next two days.  The press release was impressive.
        • We learned a lot captured in Jira tickets.
    • ActionRittwik Jana Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      • Rittwik will meet this week and report out next week.
    • ActionJinri Huang provide an answer to Rittwik Jana regarding support for O-CU, O-DU.  Without commitments from O-CU and O-DU the end to end use cases are in jeopardy.
      • One based on O-RAN services and OAM functions that will form tracks that each release will be improving OAM.  The end to end use case relies heavily on O-CU and O-DU functionality that we can progress in this release.
      • We need to synch up with the PTLs of O-CU and O-DU and the architecture committee to support these use cases.
      • Rittwik - update yesterdays RSAC meeting Ganesh from Radisys this Friday.  He is encouraging O-CU and O-DU come together and identify feasible use cases.
      • This is a high priority and PTLs must work together.  Be modestly aggressive to target this release.  Looking forward to an update next week on these discussions.
      • Rittwik - Setting expectations: when KPIs come to RIC (measurement page) then you do the analytics and then turn it into a traffic steering action as a simple hand off from one cell to another not a real UE.  We need a realy UE simulator component needs to be contributed to understand the hand off.  
      • Action/ Farheen Cefalu  add to agenda.  Call to Community to address the UE simulator as well as the fact that the test community in O-RAN will have a need for this.  We have our Simulator team that can identify a UE simulator.
    • Action/ PTLs enter epics from Contributions into jira.
      • Jack will start pulling reports from Jira to see the scope of this release.
    • Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
      • Action/ PTLs pull together a summary of each of the projects on what they plan to deliver in Bronze release.
      • ETE use case is focused on the lower stack but we don't want to ignore the higher level functions.  What use case can drive the work in the non-Realtime RIC.
        • Tracy - O-RAN testing group has a POC plugfest keyed up for the Bronze release.  Plugfest will be end of June 2020.  It's a dynamic 5G multi-operator with first responders.  
        • ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
        1. Clean up documentation 
        2. Close Jira issues
        3. After every release we will have a window where a developer can work on the maintenance items.  We're trying to improve what we have done for the Amber release.
        4. Make changes to the Amber branch.  If you need help to trigger the jobs for the Amber maintenance release contact Lusheng Ji
      2. Project Bronze Release
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. No epics yet.  I am having a problem with the healthcheck use case.  There is a meeting with John Ng to meet tomorrow.  
      3. Yingying Wang O-RAN Centralized Unit (OCU)
        1. We have some new committers in the B release.  
          1. Is there a roadmap of the O-CU functionality of how you will add functionality?
          2. ActionYingying Wang provide a list of functionality that you plan on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
        1. We are updating the scope for the Bronze release.
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
        1. We will be working closely with the ODUHIGH project.
        2. Our plan is to release the binary.  We are reviewing the license.  We need to have a license agreement first. 
        3. Jack will work with the legal team to address the license.
      6. Martin Skorupski Operations and Maintenance (OAM)
        1. We are working on the healthcheck use case.  We are forming our epics.
      7. Alex Stancu Simulations (SIM)
        1. Planning to work with OTF team for the Bronze release. 
      8. Xiaohua Zhang Infrastructure (INF)
        1. Working on epics.  Planning to deliver epics next week for Bronze release.  We need to work with O-DU to provide infrastructure.  Please include Xiaohua Zhang for infrastructure.
      9. weichen ni Documentation (DOC)
        1. Think about best practices area.  Read that and give guidance to the team of what your expectations are around the documentation.  To make things usable outside of developers to make it work.  Both the software detailed documentation and how to use the overall system. 
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
        1. Working on epics.  We plan to tidy up our repo.  There is functionality that should be in other projects such as simulations, and dashboard (OAM).  We will set up sub repos in those repos.
        2. The need for coordination of the SC and O-RAN projects.  IBM is duplicating work.  We plan to look through our roadmap to see where to push those changes.  Whether to O-RAN or O-RAN SC.
          1. Part of the challenge of being new and starting new.  People are confused on coordination.  This raises another discussion about what an SMO is and should we have a project and space to pull together the SMO owrk.  Original agreement was ONAP would be upstream and RAN specific should be here with O-RAN Alliance.  As a community how do we sort out this overlap and now that this community has been established how do we structure the needs.
            1. This is a good conversation to start at the plugfes in Prague.  If we have a slide that explains the division of labor that would be very useful.  I know Vimal worked on something like that.  Jack will talk to Vimal to sort it out
            2. All parties are well aware with Vimal's slides but we want more.
            3. One suggestion ONAP may need to be happening this conversation rather than here.  Trishan de Lanerolle can help get the right people.  
              1. We have the right people.  We need to coordinate it better.
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
      1. O-CU and O-DU teams look at the steering and healthcheck and simulator use cases.
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
    1. By Jinri: possible contribution to MWC Barcelona
      1. Can we see what demos are planned?
        1. Paul - This is out on the wiki.
    2. O-ARN Alliance Face to face meeting: 
      1. Jinri: on Monday TSC call, we discussed meeting arrangement but no conclusion yet.  F2F to be held Feb 17-21, Paris. 
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)
    1. Votes
      1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
        1. Vote to approve minutes for  
        2. On motion made by weichen ni
        3. Seconded by MASAFUMI MASUDA
        4. VOTE: Vote taken, item passed
    2. Actions
      1. Action/ Tracy Van Brakle will send info to Jack and add the event to our wiki.
      2. Action / TOC voting members: Provide an alternate contact on the TOC list
      3. ActionRittwik Jana Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
      4. Action/ Farheen Cefalu  add to agenda.  Call to Community to address the UE simulator as well as the fact that the test community in O-RAN will have a need for this.  We have our Simulator team that can identify a UE simulator.
      5. Action/ PTLs enter epics from Contributions into jira
      6. Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
      7. Action/ PTLs pull together a summary of each of the projects on what they plan to deliver in Bronze release.
      8. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
  • No labels