Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Jinri found typos and will discuss with Farheen offline. 
   2. Vote to approve minutes for 19 Feb 2020 
   3. On motion made by Jinri Huang
   4. Seconded by Vincent Danno
   5. VOTE: Vote taken, item passed

1. Rittwik add Beave

1. John Keeney  wants to rename his repo.
   
   • https://wiki.o-ran-sc.org/display/TOC/Outstanding+Resource+Requests+for+Linux+Foundation

   • Repo requests:
     https://lists.o-ran-sc.org/g/toc/message/184
     https://lists.o-ran-sc.org/g/toc/message/194
     https://lists.o-ran-sc.org/g/toc/message/191
2. RIC App approval need to be made.
   • 4 repos of office steering xApps, qp driver, and a hello world xapp.  Posting in the chat.
   • https://lists.o-ran-sc.org/g/toc/topic/repo_requests_for_ricapp/71539539?p=,,,100,0,0,0::recentpostdate%2Fsticky,,,100,2,0,71539539
3. Portal Non Real time RIC Control panel rename from John Keeney.

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.

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/ user-59b16 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. Action / Farheen Cefalu update the Events page with the updated virtual meetings.
4. Action / Jinri 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. Action/ user-59b16 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  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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   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/ user-a934b 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.  Action/ Trishan 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 

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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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.

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 12 Feb 2020 
   2. On motion made by Jinri Huang
   3. Seconded by user-2057e
   4. VOTE: Vote taken, item passed

1. Open Data Set

1. Outstanding request from Thoralf, Matti, and John Keeney for a new repos
2. John Keeney  wants to rename his repo.
   
   • https://wiki.o-ran-sc.org/display/TOC/Outstanding+Resource+Requests+for+Linux+Foundation

   • Repo requests:
     https://lists.o-ran-sc.org/g/toc/message/184
     https://lists.o-ran-sc.org/g/toc/message/194
     https://lists.o-ran-sc.org/g/toc/message/191

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. Action / Farheen Cefalu update the Events page with the updated virtual meetings.

1. Action / Jinri 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/ user-d3360  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 07 Feb 2020 
6. Action / TOC voting members: Provide an alternate contact on the TOC list above.
   1. Viswa provided 
7. Action/ Jinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.
   1. We will be notified on 03 Mar 2020 

8. Action/ user-59b16 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. Action/ user-59b16 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  will talk to the focus group.
          1. Jack: it won't be as extravagant as the test group has. 
12. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
    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. Action/ Tracy 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.

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. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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

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 12 Feb 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
2. Actions:
   1. Action / Farheen Cefalu update the Events page with the updated virtual meetings.
   2. Action / Jinri Huang wants to discuss the Open Data Set .
   3. Action/ user-59b16 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  will talk to the focus group.
   5. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   6. Community asked for a release manager.
   7. Action/ PTLs be prepared to discuss Bronze development sprint 1 demos.

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. Moved by Jinri, Seconded by William, passed.

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

1. None

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
 

1. Action/ user-d3360 Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
   1. Closed
2. Action/ user-d3360  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 07 Feb 2020 
   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. Action/ Jinri 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. Action/ user-59b16 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. Action/ user-59b16 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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
    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. Action/ Tracy 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.

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Project Bronze Release
2. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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
   

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)
   

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 29 Jan 2020 
   2. On motion made by Masafumi Masuda
   3. Seconded by William DIEGO
   4. VOTE: Vote taken, item passed

• Maintenance window closed last Saturday.  Lusheng asked PTLs to update their information.  
• Action/ user-d3360 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 user-d3360 to approve the Amber maintenance release on 05 Feb 2020 
  • Seconded by MASAFUMI MASUDA
  • VOTE: Vote taken, item passed

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.

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. Action/ Thoralf Czichy update the TOC with the new Nokia TOC members.

4. Action/ user-59b16 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. Action/ user-59b16 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 - user-59b16 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 user-59b16

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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.

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. Action/ Tracy 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. Action/ Tracy Van Brakle send the URL for the POC plutfest through lists.o-ransc.org.  

12. Action/ PTLs update Architecture pages.

    1. user-d3360  send out a reminder to PTLs.

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 user-d3360 if you have trouble with the CI/CD pipeline.  Jenkins server has been acting up.
2. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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.

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 29 Jan 2020 
      2. On motion made by Masafumi Masuda
      3. Seconded by William DIEGO
      4. VOTE: Vote taken, item passed
   2. Motion made by user-d3360 to approve the Amber maintenance release on 05 Feb 2020 
      • Seconded by MASAFUMI MASUDA
      • VOTE: Vote taken, item passed
2. Actions
   1. Action/ user-d3360 Ask PTLs to update the Status column on Amber Maintenance (Feb, 2020) page.
   2. Action/ PTLs get your F2F slide decks ready.  Due 07 Feb 2020 
   3. Action / TOC voting members: Provide an alternate contact on the TOC list above.
   4. Action/ Jinri Huang  Tracy Van Brakle  suggested speak with Paul about the demos at ONES.

   5. Action/ user-59b16 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. Action/ user-59b16 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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   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. Action/ Tracy Van Brakle send the URL of where on the wiki you posted the POC plugfest through lists.o-ransc.org.  
   12. Action/ user-d3360  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.

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 29 Jan 2020 
   2. On motion made by Jinri Huang
   3. Seconded by user-2057e
   4. VOTE: Vote taken, item passed

1. Into near-RT RIC section: Already handled by e-mail: Approval obtained from TOC for new repo o1 in near-RT-RIC: https://lists.o-ran-sc.org/g/toc/topic/new_repo_ricp_near_rt_ric/70071381?p=,,,100,0,0,0::recentpostdate%2Fsticky,,,100,2,0,70071381
   1. We are in the last week of the maintenance release approval.

1. MWC (Barcelona)
2. O-RAN Alliance F2F Feb 17-21 (Paris)
3. ONES = LF Networking Conference in April (Los Angeles).  
   • Open Networking & Edge Summit Event
 
   • There doesn't seem to be interest in activities at ONES.
     • Tracy - There will be a discussion today whether or not we should have the POC Plugfest at ONES.
       • That would be a paper which will be acceptable option that we can discuss.
       • Rittwik - Thoralf, Matti, and I are going to put an abstract together.
         • Jack - If people want to submit talks then include everyone in your community.

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.
   1. We have approval for new seats for new TOC members. 
   2. The TSC will vote to approve the new TOC members of the O-RAN SC who will serve as voting members from 01 Apr 2020  - 01 Apr 2021 
   3. Nokia, Radisys, and Ericsson will be TOC members for next year.
      1. No one from Radisys is on the call.
      2. No one from Ericsson is on the call.
      3. Action/ Thoralf Czichy update Nokia.
   4. Action/ user-59b16 send out an email to all three new companies above.
4. Action/ user-59b16 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.
   2. Rittwik - Martin and Alex have a TM500 for the POC. This is where the UE simulator talks to the BU.  Martin - The labs are in Europe and can not be used for a long run.
      1. Jack - We appreciate the stop gap but need to work on coming up with a long term solution.
5. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
6. Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang regarding license differences from the LF license scans for logging.
   1. The issue was from O-DU low Intel using binary as upstream and use ICC compiler.  We discussed this and you started the discussion on the legal side.
      1. Jack can speak to the licensing but editing the compiler.
      2. Action / Lusheng update and make it clear.
      3. Intel has a provision that allows them to use their license code.  But because it's the O-DU project it is not OSI approved.  We are working with them to allow O-RAN project to use their Intel code.  They plan to use it as a test or demo apparatus.  If a company decides to build their own O-DU they would deal with Intel to address their licenses to use that code.  This will allow us to use the Layer 1 binary that will make it easier to work.  The Intel binary is officially part of the O-SC project.  It is used for test purposes only.
7. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
8. Action/ Martin 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.Take a look at the template and fill out what you can.  If you don't have information then let Martin know.
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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
12. Action/ PTLs update Architecture pages.  

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Amber Maintenance Release
      1. Lusheng - is not aware of any feature updates beyond bug fixes.
      2. Action/ Rittwik - Talk to Jack about Radisys involvement.  
         1. They understand the flows.  We discussed except there is no O-CU to provide the metrics.  I asked Radisys they're thinking about using their closed O-CU API on a black box. 
         2. Action/ Rittwik set up a time with Jack and Radisys to discuss Jira and their needs.
   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. Matti asked for an extension for the RIC app.
         1. Both RIC and RIC apps will finalize their commitment in Jira next week.
2. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

1. Ask LF for more support for CI.  Code changes and submits don't mandate a connection to the Jira id.  If the submissions have a link we can view.
   1. What if we don't turn on the linkage?
      • From contribution perspective not much impact.  This is our current practice we do not add this line.  By adding this line this will force people to use Jira to track the issues.  This adds one more reference for people to investigate.  This is good software practice.  
      • Chris L. Can we start with a phased approach?  
        • yes, does LF support this?
          • you can turn on warning on the gerrit commit content.
            • Lusheng - If the TOC is OK we will do this on a warning basis first.  After M4 we will enforce.  
            • Jira usage will begin with a warning phase and then will be enforced after M4.
              1. Vote to approve to turn on the warning feature on the gerrit commit content for 29 Jan 2020 
              2. On motion made by Jinri Huang
              3. Seconded by user-2057e
              4. VOTE: Vote taken, item passed
2. Add a Jira plugin called Test management used for entering test cases into jira.  Request to ask LF to add this test management plugin to be added for 10 users or less.
   1. How many users will be using this?
      1. 3 - 4 tops.  If the Jira platform supports a group of users.
         1. Up to 10 users the cost is $100.  We can revisit if there are more.
      2. Request to ask LF to add this test management plugin to be added for 10 users or less.
         1. Vote to approve addition of test use case plugin 29 Jan 2020 
         2. On motion made by Jinri Huang
         3. Seconded by user-2057e
         4. VOTE: Vote taken, item passed

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 29 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
   2. ira usage will begin with a warning phase and then will enforce.
      1. Vote to approve to turn on the warning feature on the gerrit commit content for 29 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
   3. Request to ask LF to add this test management plugin to be added for 10 users or less.
      1. Vote to approve addition of test use case plugin 29 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
2. Actions
   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. Action/ Thoralf Czichy update the TOC with the new Nokia TOC members.
   4. Action/ user-59b16 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. Action/ user-59b16 update TSC with the short/long term UE simulator support.  
   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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   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.
   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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   12. Action/ PTLs update Architecture pages.

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 15 Jan 2020 
   2. On motion made by user-2057e
   3. Seconded by MASAFUMI MASUDA
   4. VOTE: Vote taken, item passed

1. No approvals this week

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. Action/ Jinri 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 

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. Action/ user-59b16 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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
   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. Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri 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. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
6. Action/ Martin 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-Check, https://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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
12. Action/ PTLs update Architecture pages.  

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. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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 15 Jan 2020 
      2. On motion made by user-2057e
      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. Action/ user-59b16 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. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
   6. Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang regarding license differences from the LF license scans for logging.
   7. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
   8. Action/ Martin 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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   11. Action/ PTLs update Architecture pages.  

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 08 Jan 2020 
   2. On motion made by Jinri Huang
   3. Seconded by user-2057e
   4. VOTE: Vote taken, item passed

1. No approvals this week

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

• Action / TOC voting members: Provide an alternate contact on the TOC list above.
  • Action/ Farheen get Masafumi's backup from Jack.
• Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
  • First meeting with Christian and his counterparts was held last week.
  • E2 traffic steering model needs to be approved by WG3. O-CU and O-DU handoffs won't happen until the Cherry release.  Another is healthcheck.
    • Is this advancing the software and moving the community forward?
    • Concern that we may have to add another use case to develop another aspect of the software.  How much do we advance in each release.  One thing that blocks should not prevent us from moving forward.
      • Hampered by the O-CU O-DU profile timeline alignment with OSC is tricky.  They have their timeline already that doesn't align.
        • Can we enrich the use case around some other functionality that is advancing.
      • O-CU and O-DU have to step up and what value they can add.
        • Can we develop a better set of detailed and expanded data so we can have a complete set?
        • How complete of data collection can we do in this release.
      • Steering use case.  Cu and DU should implement the E2 interface.  There were attributes and KPIs identified for modules.  That document needs to be reviewed so that it is clear to CU and DU.
        • We need to see how we can get the data into CU and DU but we don't have SMO support for that.
          • Challenge is getting the data out of those devices at performance levels.  First step is to acquire it and manage it.  The next step is to deliver it to the upstream layers.
            • We don't have any in 01 or ONAP or SMO to do real time PM.  We need to get leverage against ONAP and O-1 team to define those interfaces in support of non-RT RIC.  Or we do that work ahead of specs which leads to problems. 
              • Get that proposal.
        • Rittwik - O-DU and O-CU teams have to get together for the traffic steering use case.  
        • Sachin - Call flow is not listed for a simple traffic steering use case.  As a first step we should look at a simulator based approach.  Simply simulate the use case and then the CU and DU can adopt that simulators results.
        • The use case lists KPIs but doesn't list which one is for CU and what is DU.  The document we have today is an extensive list of KPIs to use and how training will take place.  We don't know how to get it to the SMO.  We don't need to use ONAP for now.
          • Jack asking the team to figure out how best to advance these features in the B release.  Expecting O-CU and O-DU to support the other healcheck use case.  Expecting a minimum software element with O1 communication.  The team can decide how extensive it is.  Second use case know that we've deployed every element in the stack and validate that it is running.  This is a necessary first step to deploy all the pieces.
• Action/ Jinri Huang provide an answer to user-59b16 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.
      • Action/ user-59b16 send Alex Stancu contact for simulator support.
    • Rittwik - we can have one or two cell phones.  But not sure that is possible in bronze release. You have to have many UEs in multiple cells.  It's OK to do unit tests but to test in full force we have to do it with a simulator.
      • Martin Skorupski  will use cell phones instead of a simulator for Bronze release.
• Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
• Action/ O-CU and O-DU PTLs and RSAC to get together regarding the end to end steering use case jeopardy. 
• Action/ Community to address the UE simulator jeopardy on this TOC call.
• Action/ PTLs enter epics from Contributions into jira.
  • Thoralf - see section 8c below.  This will happen next week to discuss.  Having trouble with the traffic steering use case.  Don't see how the traffic steering use case fits with near RT RIC.  Healthcheck of the different interfaces will be entered this week into jira.  We will have a list on the meeting after next week.e
  • Matti - Use case details are evolving.  
  • Sachin - Expecting Jira stories to be in Jira by next week.
  • Zhimin - Yes we put the O-DU tasks in Jira.  
    • Lusheng - discussed at the end of last release.  Issue is to compilation in LF.  The licensing is different.  We will need some legal council on this matter.
    • Jack - Have a meeting.  Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang.  We want to make sure we can do the logging.  Take it to another meeting.  Action/ user-d3360 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.
      • Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.
      • Speaking to Chris Lott about portal and dashboard discussion.
  • Alex - Simulator project will have epics.  
    • Jack - We need to know what Simulator is focusing on.
  • Xiaohua - Epics are in jira.  Trying to finish by the end of next week.  Community members can read up.
  • Wei Chen - no epics
  • John K. - Traffic steering functionality at the SMO level is happening.  Getting closer to entering but needs more time.
• Action/ PTLs participate in the Bronze planning meetings held twice a week by 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.
• Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
• Action/ PTLs update Architecture pages with the Bronze release features they plan to deliver.  

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Amber Maintenance Release
   2. Project Bronze Release
2. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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 08 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
2. Actions
   1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
   2. Action/ user-59b16 send Alex Stancu contact for UE simulator support.
   3. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
   4. Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang regarding license differences from the LF license scans for logging.
   5. Action/ user-d3360 send Trishan de Lanerolle and email with the question regarding the license discrepancy.
   6. Action/ Martin 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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
   11. Action/ PTLs update Architecture pages.  

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 08 Jan 2020 
   2. On motion made by Jinri Huang
   3. Seconded by user-2057e
   4. VOTE: Vote taken, item passed

1. No approvals this week

• 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.  
• LF Networking Conference in April (Los Angeles).
  • Feb 3rd 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)
https://events.linuxfoundation.org/open-networking-edge-summit-north-america/


• Action / TOC voting members: Provide an alternate contact on the TOC list above.
  • Action/ Farheen get Masafumi's backup from Jack.
• Action/ user-59b16 Alignment and adjust OAI code to be compliant with O-RAN Alliance.  This is an architectural review of fitting the code.
  • First meeting with Christian and his counterparts was held last week.
  • E2 traffic steering model needs to be approved by WG3. O-CU and O-DU handoffs won't happen until the Cherry release.  Another is healthcheck.
    • Is this advancing the software and moving the community forward?
    • Concern that we may have to add another use case to develop another aspect of the software.  How much do we advance in each release.  One thing that blocks should not prevent us from moving forward.
      • Hampered by the O-CU O-DU profile timeline alignment with OSC is tricky.  They have their timeline already that doesn't align.
        • Can we enrich the use case around some other functionality that is advancing.
      • O-CU and O-DU have to step up and what value they can add.
        • Can we develop a better set of detailed and expanded data so we can have a complete set?
        • How complete of data collection can we do in this release.
      • Steering use case.  Cu and DU should implement the E2 interface.  There were attributes and KPIs identified for modules.  That document needs to be reviewed so that it is clear to CU and DU.
        • We need to see how we can get the data into CU and DU but we don't have SMO support for that.
          • Challenge is getting the data out of those devices at performance levels.  First step is to acquire it and manage it.  The next step is to deliver it to the upstream layers.
            • We don't have any in 01 or ONAP or SMO to do real time PM.  We need to get leverage against ONAP and O-1 team to define those interfaces in support of non-RT RIC.  Or we do that work ahead of specs which leads to problems. 
              • Get that proposal.
        • Rittwik - O-DU and O-CU teams have to get together for the traffic steering use case.  
        • Sachin - Call flow is not listed for a simple traffic steering use case.  As a first step we should look at a simulator based approach.  Simply simulate the use case and then the CU and DU can adopt that simulators results.
        • The use case lists KPIs but doesn't list which one is for CU and what is DU.  The document we have today is an extensive list of KPIs to use and how training will take place.  We don't know how to get it to the SMO.  We don't need to use ONAP for now.
          • Jack asking the team to figure out how best to advance these features in the B release.  Expecting O-CU and O-DU to support the other healthcheck use case.  Expecting a minimum software element with O1 communication.  The team can decide how extensive it is.  Second use case know that we've deployed every element in the stack and validate that it is running.  This is a necessary first step to deploy all the pieces.
• Action/ Jinri Huang provide an answer to user-59b16 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 China Mobile, Radisys, Intel
  • Rittwik has not heard back about simulator.
    • Call to community:  What are we doing about a UE simulator.
      • Action/ user-59b16 send Alex Stancu send contact for simulator support.
    • Rittwik - we can have one or two cell phones.  But not sure that is possible in bronze release. You have to have many UEs in multiple cells.  It's OK to do unit tests but to test in full force we have to do it with a simulator.
      • Martin Skorupski  will use cell phones instead of a simulator for Bronze release.
• Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
• Action/ O-CU and O-DU PTLs and RSAC to get together regarding the end to end steering use case jeopardy. 
• Action/ Community to address the UE simulator jeopardy on this TOC call.
• Action/ PTLs enter epics from Contributions into jira.
  • Thoralf - see section 8c below.  This will happen next week to discuss.  Having trouble with the traffic steering use case.  Don't see how the traffic steering use case fits with near RT RIC.  Healthcheck of the different interfaces will be entered this week into jira.  We will have a list on the meeting after next week.e
  • Matti - Use case details are evolving.  
  • Sachin - Expecting Jira stories to be in Jira by next week.
  • Zhimin - Yes we put the O-DU tasks in Jira.  
    • Lusheng - discussed at the end of last release.  Issue is to compilation in LF.  The licensing is different.  We will need some legal council on this matter.
    • Jack - Have a meeting.  Action/ user-d3360 set up a call with John Murray, Trishan de Lanerolle, Jinri Huang.  We want to make sure we can do the logging.  Take it to another meeting.  Action/ user-d3360 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.
      • Action/ Martin Skorupski will provide the PTLs a template spreadsheet for alarms.
      • Speaking to Chris Lott about portal and dashboard discussion.
  • Alex - Simulator project will have epics.  
    • Jack - We need to know what Simulator is focusing on.
  • Xiaohua - Epics are in jira.  Trying to finish by the end of next week.  Community members can read up.
  • Wei Chen - no epics
  • John K. - Traffic steering functionality at the SMO level is happening.  Getting closer to entering but needs more time.
• Action/ PTLs participate in the Bronze planning meetings held twice a week by 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.
• Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.
• Action/ PTLs update Architecture pages.  

1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. Amber Maintenance Release
   2. Project Bronze Release
2. user-d3360 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. user-a934b 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. user-59b16 Requirements Software Architecture Committee

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 08 Jan 2020 
      2. On motion made by Jinri Huang
      3. Seconded by user-2057e
      4. VOTE: Vote taken, item passed
2. Actions
   1. Action / TOC voting members: Provide an alternate contact on the TOC list above.
   2. Action/ user-59b16 send Alex Stancu send contact for simulator support.
   3. Action/ user-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  

Roll Call & Quorum Check 

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

Review and Agree to Minutes of Previous Meeting

1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
   1. Vote to approve minutes for 18 Dec 2019 
   2. On motion made by weichen ni
   3. Seconded by MASAFUMI MASUDA
   4. VOTE: Vote taken, item passed

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.

• 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.
• Action/ user-59b16 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.
• Action/ Jinri Huang provide an answer to user-59b16 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.  
    • Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.

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 user-d3360
   2. Project Bronze Release
2. user-d3360 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. user-a934b 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. Action/ user-a934b 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. user-59b16 Requirements Software Architecture Committee
   1. O-CU and O-DU teams look at the steering and healthcheck and simulator use cases.

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. 

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 18 Dec 2019 
      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. Action/ user-59b16 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. Action/ Tracy Van Brakle post POC plugfest in June to the wiki events page.