You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 266 Next »

TOC Voting Members 

Company

NameAlternate

AT&T

Jack Murray Co-Chair

Lusheng Ji

China Mobile

Jinri Huang Co-Chair

Weichen Ni

Deutsche Telekom 

David Streibl

Ondřej Hudousek

NTT DOCOMO

Masafumi Masuda

Anil Umesh
OrangeWilliam DiegoVincent Danno

Verizon

Viswanath Kumar Skand Priya


Available (7)Available (7)
Available (8)Available (8)
Available (9)Available (9)
Available (10)Available (10)
Available (11)Available (11)
Available (12)Available (12)

*Quorum: 50% or more of total TOC voting members unless excluded due to attendance.


Heads Up! Different International Timings for Daylight Savings (Fall back one hour)

O-RAN-SC TOC

Local times

Japan

China

India

Israel

Central Europe

Ireland

US-East

US-West

2019-10-23, Mi

21:00

20:00

17:30

15:00

14:00

13:00

08:00

05:00

2019-10-30, Mi

21:00

20:00

17:30

14:00

13:00

12:00

08:00

05:00

2019-11-06, Mi

22:00

21:00

18:30

15:00

14:00

13:00

08:00

05:00

daylight savings impact

TOC Meeting Info

Technical Oversight Committee meetings are open to the public and held on Wednesdays at 8 AM Eastern Time USA.  World Time Zone Map

Zoom 2 Info:

  • Join from PC, Mac, Linux, iOS, or Android: https://zoom.us/j/6540568082
  • Or Telephone: Dial (for higher quality, dial a number based on your current location)
CityTimeZoom/Audio Bridge
UTC-timeWednesday 12:00

https://zoom.us/j/6540568082

New York (EDT / UTC-4)Wednesday 08:00+1 669 900 6833
+1 646 558 8656
855 880 1246 (Toll Free)
877 369 0926 (Toll Free)
Meeting ID: 654 056 8082
Paris (CEST / UTC+2)Wednesday 14:00+33 7 5678 4048
+33 1 8288 0188
805 082 588 (Toll Free)
Meeting ID: 654 056 8082
Beijing (CST / UTC+8)Wednesday 20:00+86 10 87833177
+86 10 53876330
400 616 8835 (Toll Free)
400 669 9381 (Toll Free)
Meeting ID: 654 056 8082
Tokyo (JST / UTC+9) Wednesday 21:00+81 524 564 439
+81 3 4578 1488
0 800 100 5040 (Toll Free)
Meeting ID:
654 056 8082
Helsinki  (EEST / UTC+3)Wednesday 15:00

+358 341092129

Meeting ID: 654 056 8082


2020 01 29


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 Ji

    China Mobile

    Jinri Huang Co-Chair


    Weichen Ni

    Deutsche Telekom 

    David Streibl




    NTT DOCOMO

    Masafumi Masuda


    Anil Umesh
    Orange

    William Diego


    Vincent 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

  4. Review of Today's Agenda
  5. Release Votes and Approval
    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
  6. Marketing of the Amber release (WG, LF, PR)
    1. MWC (Barcelona)
    2. O-RAN Alliance F2F Feb 17-21 (Paris)
    3. ONES = LF Networking Conference in April (Los Angeles).  
  7. Status of Open Action Items (Old Business)
    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. Actionuser-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. Actionuser-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
    6. Actionuser-d3360 set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
    7. Actionuser-d3360 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.  
  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. 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
  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 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 user-2057e
      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. Action/ Jinri Huang add a few lines to MWC.
    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. Actionuser-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. Actionuser-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. Actionuser-d3360 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. Actionuser-d3360 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. 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
  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 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. Actionuser-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. Actionuser-a934b provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.
      6. Actionuser-d3360 set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
      7. Actionuser-d3360 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.  

Return to Todays Agenda ^

Archived Meetings

  • No labels