Page tree
Skip to end of metadata
Go to start of metadata

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

TODO-approval request 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

2020 01 22

Agenda

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

    Company

    Contact Name

    Attendance

    Alternate Contact

    Attendance

    AT&T

    Jack Murray Co-Chair

    x

    Lusheng Ji

    China Mobile

    Jinri Huang Co-Chair

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar




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

  3. Review and Agree to Minutes of Previous Meeting

    1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for  
      2. On motion made by David Streibl
      3. Seconded by MASAFUMI MASUDA
      4. VOTE: Vote taken, item passed
  4. Review of Today's Agenda
  5. Release Votes and Approval
    1. No approvals this week
  6. Marketing of the Amber release (WG, LF, PR)
    1. Upon Maintenance release  we will do a small notification of Bronze features.
      1. Jinri - PM is preparing PR before MWC.  We can enter a few sentences there.
        1. Jack - Agrees
        2. 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. ActionRittwik Jana send Alex Stancu contact for UE simulator support.
      1. Rittwik - Asked Alex to reach out.  Martin Skorupski we are in contact VeeAvi (sp?).  For UE's we will need hardware which is difficult to acquire.
      2. We need to find out what is the UE agenda.  The O-DU project should see how they are testing the O-DU.  We have to see if the actual UE simulators can be used to test O-CUs.  
        1. Jack - You will need a UE and a radio emulator.
          1. Yes, I need a server that emulates a UE.  You don't need RF equipment for this.
          2. This is an important topic and key issue.  Which raises, we need better coordination with the test focus group in O-RAN.  I'd like to ask if one of the other TOC members will take on the role of coordination with the test group so we can come up with a common plan in the test group.  It will take a commitment from TOC to spend time on the subject.  Jinri is doing the PR work.  If one of the other TOC can take on the role of coordinating with the test group.  It is an important activity that will require coordination between the development and test teams.  If we are going to coordinate on a UE simulator then the test group should also come up with someone. 
          3. Action / Farheen add to next weeks agenda
    3. ActionYingying Wang provide a list of functionality that O-CU plans on targeting of where the O-CU is going in the coming releases.  It is a critical piece and will need a roadmap view.  
      1. Jack - Look at negotiating with the working groups about our needs.  I let the EC know that it is harder to maintain momentum in the second release due to exhaustion from the first release.  We need to keep advancing.  The first 3 or 4 releases are critical to the success.
      2. Jinri - we can remind the working groups at the F2F meeting.
      3. Rittwik - Reached out to WG8 RCU about supporting hand over for OSC.  Their answer is negative.  O-Cu feature won't be ready until Cherry release.  
        1. Be cautious that for Cherry release it has to be executable.  It is too late to plan at the Cherry release.
    4. ActionLusheng Ji set up a call with John MurrayTrishan de LanerolleJinri Huang regarding license differences from the LF license scans for logging.
      1. Sorting out Intel's contribution for license.  Lusheng will look into that.  Intel API interfaces and loader are a part of the SC.  They allow someone to take their software.  Not compatible with SC licenses.  Jack will be meeting with Stephan (Intel) that O-RAN can use their software for testing but is not an approved open source software.  It is a testing apparatus that we can load.  We still have a gap on what constitutes a layer 1 open source contribution.
    5. ActionLusheng Ji send Trishan de Lanerolle and email with the question regarding the license discrepancy.
    6. ActionMartin Skorupski will provide the PTLs a template spreadsheet for alarms.  VES collector will display the alarm list.
      1. Martin Skorupski : posted: Bronze use case: Health-Checkhttps://lists.o-ran-sc.org/g/main/topic/bronze_usecase_heathcheck/69880291?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,69880291
      2. Any question talk to Martin
    7. Action/ All PTLs take Martin's alarm template and fill out your own components alarms.
      1. If there are one or two alarms already known then inform Martin Skorupski
      2. Martin will be flexible about the alarm formats, etc.
    8. Action/ PTLs participate in the Bronze planning meetings held twice a week by the RSAC committee.  PTLs who are planning to contribute to Bronze must attend.
    9. Rittwik - OAI fell off the list.  We had a meeting with OAI.  
      1. Christian (Orange) - Drafted the open interface license with Nokia to understand the differences between OAI and 
      2. Christian - OAI across systems to provide something related to E2 service model.  Not directly open interface focused but Eurocom (sp?) funded Mosaic 5G within this is a flexran project.  Flexran is related to near real time RIC in O-RAN world.
      3. Mohamed (Orange) - As a part of my work on 5G RAN i investigated FLex-RAN.  Flexor and controller is an implementation of near real time RIC.  If you want to manage the schedule then control or manage the CU or DU.  For southbound there is a embedded agent within the source code for enode gnode B.  To perform near real time operations on open interface.  Available under Apache 2.0 license. 
      4. It is a brief description of what we can do with Flex-RAN.  If you need it we could organize a presentation for the F2F
      5. Action / Farheen put this back on the agenda.  In terms of licensing we can set up parallel meeting times.
      6. http://mosaic-5g.io/flexran/
    10. Action/ PTLs pull together a summary of each of the projects and what they plan to deliver in Bronze release.
    11. ActionTracy Van Brakle post POC plugfest in June to the wiki events page.
    12. Action/ PTLs update Architecture pages.  
  8. Standing Agenda Items (Brief Status of Ongoing Activities)
    1. Release Manager/Release Planning: Weekly TOC Scheduling
      1. Amber Maintenance Release
      2. Project Bronze Release
        1. Thoralf Czichy proposes that near-RT RIC platform functionality (content) freeze is Feb-7. This is as there's a near-RT RIC platform contributor planning f-2-f workshop planned Feb-3 to Feb-5. Bronze Timeline doesn't have an exact date (drawing suggest in week of Feb-3 to Feb-8). Preliminary content is here: filter10401.
    2. Lusheng Ji Test & Integration Planning (INT)
    3. Report out from PTL: Stand-Up & Report Out on Blockers
      1. Matti Hiltunen RIC Applications (RICAPP) 
      2. Thoralf Czichy RIC Platform (RIC) 
        1. list of draft epics: use this JIRA filter as per Jira usage conventions. Seven subteams now analyze this draft.
        2. Traffic steering derived JIRA epics: filter (2 of 4 are currently in Bronze) // Health-check derived JIRA epics: filter . Already sure that not all will fit in Bronze.
      3. Yingying Wang O-RAN Centralized Unit (OCU)
      4. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      5. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      6. Martin Skorupski Operations and Maintenance (OAM)
      7. Alex Stancu Simulations (SIM)
      8. Xiaohua Zhang Infrastructure (INF)
      9. weichen ni Documentation (DOC)
      10. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      11. (TBD) O-RAN Radio Unit (ORU)
    4. Rittwik Jana Requirements Software Architecture Committee
  9. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
  10. Planning for Next Meeting
  11. Any Other Business (AOB) 
  12. Meeting Summary (resolutions, new action items, etc.)



2020 01 15

Recording: 2020-01-15-toc.mp4

Agenda

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

    Company

    Contact Name

    Attendance

    Alternate Contact

    Attendance

    AT&T

    Jack Murray Co-Chair

    x

    Lusheng Ji

    China Mobile

    Jinri Huang Co-Chair

    xWeichen Ni

    Deutsche Telekom 

    David Streibl

    x

    NTT DOCOMO

    Masafumi Masuda

    xAnil Umesh
    Orange

    William Diego

    xVincent Danno

    Viswa Kumar

    x

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

  3. Review and Agree to Minutes of Previous Meeting

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

Return to Todays Agenda ^

Archived Meetings

  • No labels

11 Comments

  1. The "Zoom Meeting Recording" link under the "2019 05 01" Meeting minutes points to an O-RAN-SC charter PDF instead of the expected .MP4 file

    1. Ranny Haiby  I have updated the link to the correct link.  Thanks for catching!

  2. The "Zoom Meeting Recording" link under the "2019 0515" Meeting minutes points to 2019 0508 meeting recording.MP4 file.


  3. Jun Hyuk Song , I was unable to upload the May 15 recorded zoom meeting.  I opened a trouble ticket.  I'll keep you posted.

  4. I suggest creating one sub page per week to record meeting minutes to prevent scroll overflow of this page.

    1. Viswanath Kumar Skand Priya Yes, All archived minutes are on the side navigation.  This page is reserved for future meetings.

  5. July 3rd 7.2 recording is the same as June 26th.  Actually, Jinri explained meeting results with David & Inspur, and Xiaohua Zhang from Wind River confirmed the cooperation with Inspur on StarlingX. Jack concerned about the relationship between upstream and OSC, suggested Inspur to do work different from upstream in OSC. So it is better to revise it.

  6. gao xian , thank you for bringing the issue to my attention.  I have updated the video file.  The meeting has been archived.  2019 07 03.  Good luck!

  7. Farheen Cefalu

    A few comments on Aug. 7 meeting minute.


    1, throughout the whole minute, it should be "O-RAN" instead of "ORAN";

    2, In New business → POC and Spec investigation from EC discussion: it should be "MWC" instead of "NWC". There are 3 such occurrence. 

    3, In 5.d.3 regarding Ganesh and Alex's AP: it should be ODU instead of ODL;


  8. Farheen Cefalu


    One more comment regarding the Aug. 7 minute.


    On the last AP, the POC could be video, ppt, or live/static demo

  9. Farheen Cefalu


    The numbering of 0828's agenda looks not correct...