Technical Charter for O-RAN Software Community

TOC Mail Lists

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)
  • 855 880 1246 (Toll Free), 877 369 0926 (Toll Free)
  • Meeting ID: 654 056 8082
  • International numbers available: https://zoom.us/u/acyy3hylQi

2019 05

15

Zoom Meeting Recording

Agenda 

1. Call for Scribe (minutes owner) 

2. Roll Call & Quorum Check  

   Company	Contact Name	Attendance	Alternate Contact	Attendance
   AT&T	Jack Murray Co-Chair
   China Mobile	Jinri Huang Co-Chair
   Deutsche Telekom	David Streibl
   NTT DOCOMO	Toshiro Kawahara
   Orange	Vincent Danno
   Verizon	Viswa Kumar

   
   

3. Review and Agree to Minutes of Previous Meeting
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
6. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Action Phil has the request in to LF does not have a timeline from them and will continue to push.
   2. Action Farheen set up the new committee in the wiki and new committee list
   3. Action Lusheng will post a list of proposed projects and their structure to the mailing list after the meeting.  

      1. The purpose of this email is to kick off the planning discussion for what projects* we should include for the A-release Nov 2019.  This is an action item from the ToC call on 04/30. 

         (* The term “project” is very overloaded.  Just to clarify, here we are talking about the code development projects within the O-RAN SC and O-RAN SCP “Linux Foundation projects”.  Some people call these development projects “JIRA projects”.  It is expected that each of such development project will have a PTL, runs its own meetings, manages its own Confluence pages and a set of repos, etc.)

         Below is a first draft list:

         • Near real-time RIC
           • AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         • Near real-time RIC xApps
           • AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         • Non real-time RIC
           • ONAP can function as the non real-time RIC.  But still there are artifacts to be developed by the O-RAN SC, such as documentations, integration codes, life cycle management code, etc.
         • Portal/dashboard
           • UI for operating O-RAN components and demonstration
         • OAM
         • CU/DU
         • Simulator
           • Simulators serve two purposes: if we do not have real implementation for a component, a simulator may serve as a means to completing end-to-end use cases; simulators are also extremely useful in development and testing.
           • We can start with small set of simulator in A-release, graduate adding more.
   4. Action: We will have a discussion around projects in our next meeting.
   5. Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG. 
   6. Action: Jinri will push on completion of the charter.
   7. Action: Jack will push on the completion of the license.
   8. Action: ToC membership slot filling.
   9. Action Jinri post ORAN event in Japan in June to committee mail list.
   10. Action  TOC come up with a list of features or epics before the M0 start date.
   11. Action TOC come up with a naming convention for our releases.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)

Minutes:

1. Call for Scribe (minutes owner): Farheen Cefalu
2. Roll Call & Quorum Check
3. Review and Agree to Minutes of Previous Meetings 
4. Review of Today's Agenda 
5. Status of Open Action Items (Old Business)
6. Status of Open Action Items (Old Business)
   1. Action Phil has the request in to LF does not have a timeline from them and will continue to push.
   2. Action Farheen set up the new committee in the wiki and new committee list
   3. Action Lusheng will post a list of proposed projects and their structure to the mailing list after the meeting.  

      1. The purpose of this email is to kick off the planning discussion for what projects* we should include for the A-release Nov 2019.  This is an action item from the ToC call on 04/30. 

         (* The term “project” is very overloaded.  Just to clarify, here we are talking about the code development projects within the O-RAN SC and O-RAN SCP “Linux Foundation projects”.  Some people call these development projects “JIRA projects”.  It is expected that each of such development project will have a PTL, runs its own meetings, manages its own Confluence pages and a set of repos, etc.)

         Below is a first draft list:

         1. Near real-time RIC
            1. AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         2. Near real-time RIC xApps
            1. AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         3. Non real-time RIC
            1. ONAP can function as the non real-time RIC.  But still there are artifacts to be developed by the O-RAN SC, such as documentations, integration codes, life cycle management code, etc.
         4. Portal/dashboard
            1. UI for operating O-RAN components and demonstration
         5. OAM
         6. CU/DU
         7. Simulator
            1. Simulators serve two purposes: if we do not have real implementation for a component, a simulator may serve as a means to completing end-to-end use cases; simulators are also extremely useful in development and testing.
            2. We can start with small set of simulator in A-release, graduate adding more.
   4. Action: We will have a discussion around projects in our next meeting.
   5. Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG. 
   6. Action: Jinri will push on completion of the charter.
   7. Action: Jack will push on the completion of the license.
   8. Action: ToC membership slot filling.
   9. Action Jinri post ORAN event in Japan in June to committee mail list.
   10. Action  TOC come up with a list of features or epics before the M0 start date.
   11. Action TOC come up with a naming convention for our releases.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

9. Planning for Next Meeting
10. Open Discussion
11. Any Other Business (AOB)
12. Meeting Summary (resolutions, new action items, etc.)

2019 05 01

Zoom Meeting Recording

Agenda

1. Call for Scribe (minutes owner) 
2. Roll Call & Quorum Check 
3. Review and Agree to Minutes of Previous Meetings
4. Review of Today's Agenda
5. Status of Open Action Items (Old Business)
6. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

8. Planning for Next Meeting
9. Open Discussion
10. Any Other Business (AOB)
11. Meeting Summary (resolutions, new action items, etc.)

Minutes:

• Call for Scribe (minutes owner)
• Roll Call & Quorum Check

Company

AT&T

Jack Murray Co-Chair

China Mobile

Jinri Huang Co-Chair

Deutsche Telekom 

David Streibl

NTT DOCOMO

Toshiro Kawahara

Vincent Danno

Verizon

Viswa Kumar

• Review and Agree to Minutes of Previous Meetings 

  • The minutes of the prior meeting were reviewed, and there were no comments, questions or corrections. On motion made by Vincent and seconded by Jinri, the minutes of the May 5, 2019 meeting were the approved by the TOC members. 

    • VOTE: Vote taken, item passed.
• Review of Today's Agenda
• Status of Open Action Items (Old Business)
  • Phil will go ahead and make the change to o-ran-sc.org and move away from oran-osc.org and provide feedback from IT team in two days.
    • Action Phil has the request in to LF does not have a timeline from them and will continue to push.
  • Vincent will lead TOC based effort to identify and recommend what sub committees we want for the A release cycle.
    • Vincent shared O-RAN SC TOC Subcommittees presentation.
    • The action I took is we got in subcommittees we may want to launch.  This is a proposal and open to discussion.
    • Preliminary: We are kicking off work and starting out.  We want to delegate some tasks to subcommittees.
    • Help us focus on topics through subcommittees. 
      • Cautioning not to launch too many sub-committees. 
      • Launching will not insure right level of competencies.
    • TOC must approve subcommittees as consultants.
    • We are linked to ORAN Alliance.  All new sub-committees must be reviewed by the ORAN Alliance.
    • Proposal
      • Launch one sub-committee to make proposal to TOC for use cases & requirements of the O-RAN Software Community releases.  This sub-committee will embark any software architecture & security considerations
      • Launch new sub-committees as needed.  Start simple but stay flexible.
      • Feedback / Comments
        • Jinri under working group 1 there is a use case task group.  From TOC what Vince just presented use cases again.  What will be the difference between the use cases task team and subcommittee.
          • In our software community we are working with releases such as "A".  We have our own schedule and ORAN Alliance has their own.  There must be strong links between ORAN Alliance and ORNA SC TOC.  The Software community must inherit from ORAN Alliance.  However we have release A but may not embark on all ORAN Alliance use cases.  This subcommittee needs to define which use cases we will embark in release A.
          • Jinri - ORAN SC sub-committee is a subset of ORAN Alliance task force?
          • Jack - I agree to make the software work there are use cases that are more functionally addressed here.  Whereas ORAN Alliance is looking at overall functionality. As we break the task down.  The use case will be more specific around software.  There may be implementational use cases and not functional use cases.
          • Rittwik - There are use cases that WG1 has that straddles across the whole stack.  There are also use cases that each individual  work group has sanctioned.   example use cases in WG2 that are being used by WG3. 2 use cases are sanctioned by WG2 and being used by WG3.  My confusion is when you say use cases for the software community for each part of the stack you will need to exercise the use cases the use cases that are sanctioned by each group.  Because there is not one use case that will straddle across the whole board.  The interoperability across WG1 - 8 is not there. for first release Instead work through individual use cases.  
          • Jack - we may have to have end to end use cases that will connect the stack together.  but thats the challenge for this team we have to agree on some subset of requirements that drive the software, architecture and implementation of this release.  We at least have to have clear goals for each release.  
          • Jinri- Rittwik suggests use case per developing group.  Even in this case the use case in our subcommittee in software community is not a subset of the use cases by working groups.  For our community we are describing use cases from software development perspective but use cases of working groups are in line with functional perspective.  are we in line?
          • Rittwik - Each working group has interfaces.  Your use cases revolve around API and interfaces.  But the end to end use cases I don't think this team constructs. Or is that a part of the scope?
          • Only if software plays a part of the role.  If that gets targeted as a software capability that their use case drives.
          • Rittwik - as a product does this team drive the end to end?
          • Jack - Yes if the community feels it's a driver for evaluating the software.  We are a long way away from a full stack use case.  For people outside to see value will have to have end to end use cases.  Deploy the software, deploy the RIC.  (MACD).  This will bring people together to show broader interested parties.  We'll talk more as this committee brings together.
          • Jack - Rittwik is a part of the committee.  He is involved in working groups and RIC.  Lusheng has proposals of project structure.  Action Lusheng will post that up to the email list after the meeting.  Dave from AT&T as somebody who can participate and start working on this first sub committee that is being proposed.  He is a software and RAN architect that will help to work in that space.  This meeting will continue to grow in participants.  As we form subcommittees they will break off from this committee.  We have two zoom bridges to coordinate meetings between subcommittees. At this point we are being pressed. Please start the subcommittee but 
          • Jack - Proposal to name subcommittee to requirements and software architecture and remove the word use cases.
            • David agrees to remove use cases from the name of the subcommittee.  We already have a lot in ORAN.  The work of the subcommittee into ORAN as a whole into functional and non-functional requirements for software development.
            • Part of it we use jira.  This committee worries about the epic level and the project or working groups will do the user stories to break down the epics into details.  There is a natural tracking process in jira.
            • Is there a reason why security is a part of software architecture?
              • All topics are grouped into one sub-committee for now.  The committee will decide to recommend to subdivide in the future.
              • Phil- You will want to have a process for external groups to report and react to vulnerabilities.
          • Jinri - I am not receiving mail.
            • Jack- other people in China mobile that are getting emails to other projects.
            • Action Jinri - Reach out to Phil directly.  
            • Jack - Everything can be posted to the mail list.
          • Do we have the a place to put the proposal on the website?
            • Action Farheen Create a directory on the wiki for the proposal deck.

1. 1. Release Manager/Release Planning: Weekly TOC Scheduling
   2. Report out from PTL: Stand-Up & Report Out on Blockers

   3. Test & Integration Planning

   4. Report Out of Sub-Committees

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

3. Planning for Next Meeting
4. Open Discussion
5. Any Other Business (AOB)
6. Meeting Summary (resolutions, new action items, etc.)

2019 05 08

Zoom Meeting Recording

Agenda 

• Call for Scribe (minutes owner) 
• Roll Call & Quorum Check  

• Review and Agree to Minutes of Previous Meeting

  • The minutes of the prior meeting were reviewed, and there were no comments, questions or corrections. On motion made by Jinri and seconded by David, the minutes of the May 1, 2019 meeting were the approved by the TOC members. 

    • VOTE: Vote taken, item passed.
• Review of Today's Agenda
  • Reviewed by TOC - Only TOC are allowed to vote and second items.  Others can make proposals.
• Status of Open Action Items (Old Business)
  • Domain name change - rough timeline of 2 weeks. 
    • The operations team will reach out to Lusheng. 
    • When we launched we were oran-osc.  We have been guided to change the dns to o-ran-sc.org.
    • No disruption to anyone using the old domain name.
    • Mailing lists are on the Groups.io will move to the new domain name.
    • Action Phil will contact Jordan from LF Ops.
  • Decide on requirements for first A release.
    • We can started a new sub-committee.  I have posted a document of what functionality we want to target for this first release.
    • WG3 started putting out some use cases.
    • We have to decide what we are targeting to buld epics and use cases around that requirement.
    • This committees job is to work on requirements for the software release.  We need to form that committee and start having meetings around that activity.
    • Action Lusheng post a message in the email list to organize that meeting.  We will elect the PTL for that activity.  We have until the end of the month to get into the release A process and plan.  The key here is deciding what we will do in this first release.  AT&T has pushed seed code for the near real time RIC and xApps (orchestration and A1) and are looking for contributions as well as building blocks and logging.  Then there is the dicussion about how much further down the stack we will work for this release for CU, DU, RU, areas.  Do we consider a simulator?  All that starts around the subcommittee and documents around A release.
      • Jinri - Lusheng I suggest you reach out to WG co-chairs in the ORAN Alliance.  Their early involvement is very important.
    • We will start with one committee for now to get started.  There is a large amount of work to be done.
    • Lusheng sent out an email to the mailing list to start the conversation.
      • These are the items we think we should get started with.  If we want to set up an end to end system running by the end of this year.
      • Action Team  Looking for contributors for near real time RIC.  
        • Plantform stable and open plugable architecture.
        • xApps are targeting specific functions for the NRTRIC.  
          • Expecting vendors to contribute their xApps to the project.
        • There is also real time RIC and looking for contributions to ONAP.  This the function that oversees the operation of the RIC.  We are looking to adopt.
        • The next item is portal or dashboard.  You need a UI to operate the deployments and operations.
        • CU/DU we are looking for contributions to run.  Intel and Radisys intends to contribute.  
        • Simulator project this is the initial release and we won't have the luxury of all the pieces.

1. Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG. 
2. Action: Jinri will push on completion of the charter.
3. Action: Jack will push on the completion of the license.
4. Action: ToC membership slot filling.
5. Action Jinri post ORAN event in Japan in June to committee mail list.
6. Action  TOC come up with a list of features or epics before the M0 start date.
7. Action TOC come up with a naming convention for our releases.

• Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

• Planning for Next Meeting
• Open Discussion
• Any Other Business (AOB)
• Meeting Summary (resolutions, new action items, etc.)

Minutes:

1. Call for Scribe (minutes owner): Farheen Cefalu
2. Roll Call & Quorum Check
3. Review and Agree to Minutes of Previous Meetings 
4. Review of Today's Agenda 
5. Status of Open Action Items (Old Business)
   1. Action Phil has the request in to LF does not have a timeline from them and will continue to push.
      1. Rough timeline of two weeks.  To do it as quickly as possible.  We launched under ORAN-OSC and we changed the domain to O-RAN-SC.org.  LF will swap to the new domain name going forward.
   2. Action Farheen

1. 1. set up the new committee in the wiki and new committee list

1. 1. 1. Jack- Lusheng post a message in the email list and pick a time to start to organize that meeting and process plan around workign group 8.  The key here is deciding what we're going to do in the first release.  AT&T is pushing seed code for the near real time RIC and xapps.  We are interested in contributions in the xapps, orchestration, and building blocks like portal.  What progress do we make on the CU, DU, RU.  This all starts around the sub-committee and the requirements.  
         1. Jinri - Suggestion to reach out to WG6 and WG8. 
   2. Action Lusheng will post a list of proposed projects and their structure to the mailing list after the meeting.  
      1. Lenovo and China mobile also has code to conribute. Action Lusheng will set up a call to get them started.
      2. The motivation for this list was to have an end to end  system running by the end of the year it will be good for our initial release.  It's divided into Platform and xApp component.  xApps are targeting specific functions for the near real time RIC.  We also have a framework to contribute their own xApps.  The framework should allow xApps to be used in their deployment environments.  

      3. The purpose of this email is to kick off the planning discussion for what projects* we should include for the A-release Nov 2019.  This is an action item from the ToC call on 04/30. 

         (* The term “project” is very overloaded.  Just to clarify, here we are talking about the code development projects within the O-RAN SC and O-RAN SCP “Linux Foundation projects”.  Some people call these development projects “JIRA projects”.  It is expected that each of such development project will have a PTL, runs its own meetings, manages its own Confluence pages and a set of repos, etc.)

         Below is a first draft list:

         1. Near real-time RIC
            1. AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         2. Near real-time RIC xApps
            1. AT&T and Nokia has contributed seed code into repos falling into the scope of this project.
         3. Non real-time RIC
            1. ONAP can function as the non real-time RIC.  But still there are artifacts to be developed by the O-RAN SC, such as documentations, integration codes, life cycle management code, etc.
               1. At this point we are looking at ONAP.   
         4. Portal/dashboard
            1. UI for operating O-RAN components and demonstration
               1. By the end of the A release they will have a UI to see how to do certain operations.
         5. OAM
         6. CU/DU
            1. We have contributions from ORAN alliance placement.  Intel and Radisys expressed intent to contribute.  It would be great to get an update from them.
         7. Simulator
            1. Simulators serve two purposes: if we do not have real implementation for a component, a simulator may serve as a means to completing end-to-end use cases; simulators are also extremely useful in development and testing.
            2. We can start with small set of simulator in A-release, graduate adding more.
               1. If any pieces that is needed but we do not have a fully functional contribution then simulations will fulfill that role during that time.  If we want to test part of the system they can use simulation process.
               2. Please let us discuss more if you want to contribute.
               3. Jack- The next stage is projects.  They are important to set up the repos, jira, build process.  Also, how the overall project is organized .  Each area will operate as a sub-team.  We will get people to contribute to it.  Typically there are Product Technical Lead (PTL) who leads each group.  We are looking for community participation.  
                  1. Jinri - Accelerator Project is missed here. 
                     1. This is a first draft and a work in progress.
                  2. We have to determine how we want to organize the projects.
   3. Action: We will have a discussion around projects in our next meeting.
      1. We already had this.
   4. Action: Need a volunteer to work with O-RAN WG.  The O-RAN Alliance TSC handles filling in the position O-RAN OFG. 
      1. We need to close on filling the rest of the TSC slots for us here in the open source project.  It's an ORAN-TSC function.  They select the TSC members.  We are going to work with whatever TSC members that we have assigned.  We have six and we need the TSC to fill out the remaining 6 seats.  As they are approved by ORAN Alliance TSC they will become active in this community.  
      2. Jinri - There is a change of attitude with EC.  This meeting is not the right forum.  I will update Jack later.  
      3. Jack - 
   5. Action: Jinri will push on completion of the charter.
      1. Hank has not approved the final draft but is OK with us sharing it.
      2. Action Jinri double check with Hank.
   6. Action: Jack will push on the completion of the license.
   7. Action: ToC membership slot filling.
      1. Vincent has the date for the document been decided yet?
      2. This TOC decided to have drafts completed by last Friday and get the final comments by May 17th.
      3. In our last meeting we agreed to get their feedback by May 17.  We may miss that target by a few days.  Maybe May 23, or 24 or end of May.
      4. With this new version it is accepting of key players.  It takes the feedback from the first round and incorporates it.
      5. Would people want that document 
   8. Action Jinri post ORAN event in Japan in June to committee mail list.
   9. Action  TOC come up with a list of features or epics before the M0 start date.
   10. Action TOC come up with a naming convention for our releases.
       1. Look into something generic that can't be trademarked.
       2. Perhaps constellations?
2. Standing Agenda Items (Brief Status of Ongoing Activities)
1. Release Manager/Release Planning: Weekly TOC Scheduling
   1. We need a release manager that will keep everyone on plan.
   2. We have a proposed A Release calendar.  We have a May 20th but we may have to move this to begin the first week of June.
2. Report out from PTL: Stand-Up & Report Out on Blockers

3. Test & Integration Planning

4. Report Out of Sub-Committees

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

   1. Does anyone have any new agenda items they want to add?
      1. No volunteers
   2. Action All participants Send comments to main@lists.oran-osc.org.  We have a month to put together a plan to launch this project.  Each component needs a developer.
   3. The big push is to work on developers 
4. Planning for Next Meeting
5. Open Discussion
6. Any Other Business (AOB)
7. Meeting Summary (resolutions, new action items, etc.)

Return to todays agenda