Technical Charter for O-RAN Software Community

2020 04

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		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda		Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen
   Radisys	Ganesh Shenbagaraman		Sachin Srivastava
   Ericsson	John-Paul Lane

   *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. Vote Release Name for D release is Dawn.

6. Marketing of the current release (WG, LF, PR)

   1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event


7. Status of Open Action Items (Old Business)

8. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.

   2. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 

   3. Action/ William DIEGO update on coordination with the O-RAN test group

   4. Action/ William DIEGO provide more details of how the use cases and Jira items reflect the activities.  simple flow diagram of our activities and their activities and how they are going to work together.
   5. Action/ PTLs provide user-d3360  with your sprint 3 demo dates.
   6. Action/ Martin Skorupski add the link for the yang model to the wiki. https://forge.etsi.org/rep/3GPP/SA5/data-models/tree/master/yang-models

9. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Project Bronze Release

   2. user-59b16 Requirements Software Architecture Committee

   3. user-d3360  Integration and Test

      1. Gerrit review process improvement
      2. Branching and testing strategy

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC) 

      4. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

      7. Martin Skorupski Operations and Maintenance (OAM)

      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)

      11. (TBD) O-RAN Radio Unit (ORU)

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

    1. OAI purposed Meeting
    2. licensing

11. Planning for Next Meeting

12. Any Other Business (AOB) 

13. Meeting Summary (resolutions, new action items, etc.)

14. 1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

       1. Project Bronze Release

    2. user-59b16 Requirements Software Architecture Committee

    3. user-d3360  Integration and Test

       1. Gerrit review process improvement
       2. Branching and testing strategy

    4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

       1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

       2. Matti Hiltunen RIC Applications (RICAPP) 

       3. Thoralf Czichy RIC Platform (RIC) 

       4. user-a934b O-RAN Centralized Unit (OCU) 

       5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

       6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

       7. Martin Skorupski Operations and Maintenance (OAM)

       8. Alex Stancu Simulations (SIM)

       9. Xiaohua Zhang Infrastructure (INF)

       10. weichen ni Documentation (DOC)

       11. (TBD) O-RAN Radio Unit (ORU)

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

    1. OAI purposed Meeting
    2. licensing

16. Planning for Next Meeting

17. Any Other Business (AOB) 

18. Meeting Summary (resolutions, new action items, etc.)

2020 04 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	x	Weichen Ni
   Deutsche Telekom	David Streibl		Ondřej Hudousek
   NTT DOCOMO	Masafumi Masuda	x	Anil Umesh
   Orange	William Diego		Vincent Danno
   Verizon	Viswa Kumar		Kristen Young
   Nokia	Juha Oravainen	x
   Radisys	Ganesh Shenbagaraman	x	Sachin Srivastava
   Ericsson	John-Paul Lane	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 15 Apr 2020 
      2. On motion made by Jinri Huang
      3. Seconded by John-Paul Lane
      4. VOTE: Vote taken, item passed

4. Review of Today's Agenda

   1. Rittwik requesting time extension for RIC App and E2 SIM enhancements.  This will be covered during Rittwik's status.
   2. Jack: O-AI offered to discuss align or collaborate.
   3. Lusheng: Added two items under integration and test section.
   4. John Keeney: Wants to ask a question about Licensing

5. Release Votes and Approval

   1. Vote Release Name for D release is Dawn.

6. Marketing of the current release (WG, LF, PR)

   1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event


   2. Virtual exhibition meeting will be open soon.  Jinri will be meeting with O-RAN Alliance.
   3. Last week people discussed the virtual meeting for June to replace the face to face due to COVID-19.
      1. the virtual meeting will be a little different.
      2. Action/ Jinri Huang  work with Farheen to mark this as an open item.
   4. Jack: There is one marketing item.  Most other open source projects have a logo.  In the early days we talked about creating a logo for O-RAN SC.  It got pushed to the background.  The LF will help with registering a logo.  If a TOC member is interested in taking it on let the TOC know.  It's nice to have and takes time to work through different peoples ideas.  
   5. Jack: I will be replacing the LF Edgeboard AT&T employee.  I will keeping these activities separate.  I wanted to let this team know.

7. Status of Open Action Items (Old Business)

   1. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.

   2. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 

   3. Action/ William DIEGO update on coordination with the O-RAN test group

      1. William presenting slides.
      2. Idea is to have different ETE test spec coordination between O-RAN (Test Integration Focus Group) and OSC.
      3. Jack suggested to add use cases and tools.  We want to make sure we are aligning on the ETE use cases.  The use cases will drive software and drive it back to the TIFG.
      4. Is OSS Open Source Software? 
      5. Yes, up to now we are integrating different software 
      6. William: This scheme tries to illustrate the test and integration framework.
      7. John: Do you mean no Real time RIC?
      8. William: In this first version we will not integrate the RIC.
      9. John: Proprietary OAM interfaces there's no real time RIC there's no A1.
      10. Eng Wei the ETE framework includes all the O-RAN Alliance specifications and all the requirements.  We will be mapping from a subsystem perspective.  Allow blueprint deployment.  What to do via subsystem level.  all the specs will be in place day 1.  Telecom Italia wants to validate the RIC using use cases. Dynamic traffic steering is something they need to use as well.
      11. Jack: I agree with everyone here.  This baseline scenario does not leverage what we have today.
      12. Rittwik: Yes, because ORU is being tested in Bronze.
      13. Jack: But we don't have O-RU?
      14. Yes,
      15. Jack: The way this picture is described is legacy.  As part of the plan for Cherry we have to start understanding how we are going to play into these.  I like your picture on timeline.  We should fold these key dates into our timeline on our release management.
      16. Action/ William DIEGO send John Murray the dates from the TIFG slide deck.
   4. Action/ William DIEGO provide more details of how the use cases and Jira items reflect the activities.  simple flow diagram of our activities and their activities and how they are going to work together.
   5. Action/ PTLs provide user-d3360  with your sprint 3 demo dates.
   6. Action/ Martin Skorupski add the link for the yang model to the wiki. https://forge.etsi.org/rep/3GPP/SA5/data-models/tree/master/yang-models
      1. Martin: We want to have data modeling on the wiki in a broader way.

8. Standing Agenda Items (Brief Status of Ongoing Activities)

   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling

      1. Project Bronze Release

      2. Rittwik: Asking for two weeks to add on to the end of the timeline.

   2. user-59b16 Requirements Software Architecture Committee

      1. Rittwik requesting time extension for RIC App and E2 SIM enhancements.  This will be covered during Rittwik's status.
      2. There are 3 key pieces
         1. Viavi sim files need to come thru.  
         2. Once those files are produced the E2 sim is getting enhanced.  Alex will run with it.
         3. Once E2 format is formed the xApps can start consuming.
      3. We want to make some progress to help gear what we want to do in the next release.  A lot of parties have to get together.  It is better to get this done now.
      4. Alex: What Rittwik said is what I am aware of.  I am talking to Ron and things are going well.
      5. Jack: The code we're talking about is primarily in the simulator project.
      6. Matti: KPI, Traffic steering xApps and ML.  Ron's time is being split between sim and xapp and we lost a developer.  All the interfaces are nailed down so the development can occur in parallel.
      7. Jack: If we stay on the current schedule what kind of functionality will be available.  We have two options we can slide the test date out or stay on schedule and bring some functionality to the maintenance release.
      8. Matti: If you scroll up to the previous screen.  Right now we are at the end of dev sprint 4.  The good thing is the changes between simulator, xapps, and platform will be simpler because we don't need to integrate O-CU, O-DU. 
      9. Rittwik: it's OK to demonstrate in parts.  It's important and will resonate.
      10. Jack: We do ETE sprint testing and then another two weeks of ETE testing.
      11. Lusheng: We are OK.  We will have three separate tracks.  Since this extension impacts Traffic Steering use case.  It is fine to schedule the testing for this track a little later.  We can take a phased approach.  Finish testing of phase one.  We can complete within the release schedule.
      12. Zhimin: O-DU low and O-DU high need an extension to finish development to May 17.  We are following the Intel process.  I need two weeks more.
      13. Jack: It looks like 3 weeks more.
      14. Zhimin: Yes, May 17.  After Intel process we are looking at May 31.  Code freeze is May 17.  
      15. Jack: That's three weeks behind the deadline.  This has to do with developing inside Intel and then dumping them out.  It is best practice to contribute code as you develop for collaboration in open source.
      16. Lusheng: It' not like other components like docker containers.  This is tigher integration.  
      17. Action/ Zhimin Yuan provide a time of when you will be able to deliver?
      18. Sachin: From O-DU High we are going to have the code ready but the integration will take four to five weeks.
      19. Action/ Zhimin Yuan Sachin Srivastava come up with a timeline of your activities with user-d3360 because you are not going to make the timeline for the Bronze release.  Try to come up with a plan that will be able to be delivered in the Bronze Maint release for the FAPI and the O-DU Low and High.  Please try to get it in the B release window.  It's important to have in the Bronze release.  We need to stick with the timeline and deliver the functionality and work into the open source repos and pay attention to the timelines.

   3. user-d3360  Integration and Test

      1. Gerrit review process improvement 
         1. Lusheng: presenting a deck.  During the release I took at the current practice and making some suggestions. gerret requires +2 reviews after jenkins job has passed.  Then the submission becomes mergable.  The problem is if the submitter is a committer as well he can submit the code and give a +2 and merge the code.  We are losing the advantage of using gerret.  There is an improved merging policy call NACR Non-authore code review. 
         2. Ask TOC to move forward with the +2 requirement.  
         3. Jack: Are you asking to use it Bronze or Cherry?
         4. Lusheng: Either way I recommend we start on Cherry due to time delays.
         5. Jack Let's talk about it more next week.  We are not going to change it.
         6. Lusheng: Another practice is to limiting the submission size.  Gerret will block submissions exceeding certain size limits.  Something for us to consider what we want to adopt.  We want to do all the code changes in gerret open source because there is a 5000 lines of code limit. 
      2. Branching and testing strategy
         1. Once testing starts do not adding code to the master branch.  By code freeze we are expecting bug fixes and documentation fixes to the master branch.
         2. For all the repos the code freeze date is this weekend.  Repos involved are the traffic steering use case and the O-DU low and O-DU high.  Branching strategy diagram it is starting the code freeze time and some members of the team create a development branch and put your development code on the development branches.  Once completed make a branch for Bronze.  This time we are going to use all lower case "b". 
         3. After you branch the master branch is open for development again.  If new bugs are being discovered then fix and cherry pick for the head.  It should be the best for the B release.
         4. For healthcheck here are the projects involved from RSAC implementation.
         5. Track 1: We'll finish the RSAC flows.  Track: 2 Approach is the same for call flows. Track 3 O-DU Integration.
         6. Testing Plan 
         7. Testing Set Up we will be using the open public AT&T T-Lab.  For track 2 and 2 we are going to use 2 VMs.  One will run near realtime RIC and the other will run SMO, O-RAN Lite

   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 

      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)

      2. Matti Hiltunen RIC Applications (RICAPP) 

      3. Thoralf Czichy RIC Platform (RIC) 

      4. user-a934b O-RAN Centralized Unit (OCU) 

      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)

      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)

      7. Martin Skorupski Operations and Maintenance (OAM)

      8. Alex Stancu Simulations (SIM)

      9. Xiaohua Zhang Infrastructure (INF)

      10. weichen ni Documentation (DOC)

      11. (TBD) O-RAN Radio Unit (ORU)

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

   1. OAI purposed Meeting
   2. Licensing: John O-RAN Alliance specs.  What is the relationship with O-SC and O-RAN Alliance regarding licensing?
      1. Jinri: Stefan prepared documentation.  EC discussed this and propose it hopes that the board can give the authority to approve a similar request in the future to save time.  
      2. Regarding re-using of the spec there is not specific request for this.
      3. Action/ John Keeney send John Murray your question regarding your licensing question.
         1. O-RAN Alliance can not grant copyright until specification has been approved.
            1. If Ericsson is the source of the message set then Ericsson can choose to add those copyrights to the O-SC.  You need permission from your company.
            2. Content in messages requires a separate copyrite.  They don't want us to release the whole specifications in open source.  It's the content of those messages needs to be copyrights on.
            3. John: it's for the schema definition.
            4. Jack: Send me a note and I want to put it on the list.

2020 04 15

Recording: 2020-04-15_TOC.mp4

Agenda

1. Call for Scribe (minutes owner) Farheen Cefalu

Roll Call & Quorum Check 

Company

Contact Name

Attendance

Alternate Contact

Attendance

AT&T

Jack Murray Co-Chair

x

Lusheng Ji

China Mobile

Jinri Huang Co-Chair

xWeichen Ni

Deutsche Telekom 

David Streibl

xOndřej Hudousek

NTT DOCOMO

Masafumi Masuda

xAnil UmeshOrange

William Diego

xVincent Danno

Verizon

Viswa Kumar

Kristen Young

Nokia

Juha Oravainen

x

Radisys

Ganesh Shenbagaraman

x

Ericsson

John-Paul Lane

x

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

2. Review and Agree to Minutes of Previous Meeting 

3. Review of Today's Agenda
   1. The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
      1. Vote to approve minutes for 08 Apr 2020 
      2. On motion made by user-2057e
      3. Seconded by Juha Oravainen
      4. VOTE: Vote taken, item passed
4. Release Votes and Approval
   1. Vote Release Name: Vote is active to choose name of "D" release.
      1. Running the vote until Saturday.  It looks like Dawn will be the color.
   2. OCU new repo 5G
      1. Jack: As we talked about the last two meetings.  We had some issues with the O-CU project.  Ran into problem where contributors brought in code that they were not allowed to bring to the project.  Since we have cleaned up.  LF decided to drop all code in the O-CU project and focus more on Best Practices and other activities.  It aligns with what's been changed in the O-CU project.  Some new contributors are coming in and we're moving on to the 5G code.
      2. Yingying: For O-CU I have a new repo request 5GNR.
      3. Jinri: Several weeks ago we mobilized a few more contributors on this project.  We will submit a request for a new repo.  We developed a timeline for contributing O-CU code for 5G.  The first patch of code will be uploaded by early next month or the earliest at the end of this month.
      4. Lusheng: The previous code from the Amber release has been purged from the repo.  March 17 there was a new repo request.  Do you want to withdraw the previous request? 
         1. Jinri: The request was raised in March is a part of the restart process.  Thank you for this reminder.
         2. Lusheng: This request is still outstanding.  We will send this out to the main mailing list.  
         3. Jinri: I approved two.
         4. Jack: I want to review for this approval.  Some of the TOC were not included.  This is trying to restart the process with new code and contributors.  We will restart the process focused on 5G.  This code was not in the previous contributions.  We are working closely with contributors to tighten up the best practices and process.  We need to create a repo to restart this process.  Are there any questions?
            1. Ganesh: We are re-writing all the code?
            2. Jack: The code will be 5G O-CU.  Yingying is still the PTL but we are working with a new team of contributors and new code.
            3. Jack: Request a vote to approve a new O-CU 5G repo 
               1.  Vote to approve a new O-CU 5G repo 
               2. On motion made by Jinri Huang
               3. Seconded by user-2057e
               4. VOTE: Vote taken, item passed
5. Marketing of the current release (WG, LF, PR)
   1. ONES = LF Networking Conference tentatively August/ September (Los Angeles).  Open Networking & Edge Summit Event
 
      1. Action/ Jinri Huang communicate the online events on the wiki.
6. Status of Open Action Items (Old Business)
   1. Action/ update on O-CU plans
      1. It is important to have the team do contributions to draw more people to participate in your project.
   2. Action/ update on Intel license agreement on binary usage 
      1. Jack: People may remember as part of O-DU in Bronze doesn't have layer 1 open source contributed at this time.  Intel has offered a binary image of their flex ran software to be used for the O-DU low.  We have been tied to that binary license for testing O-RAN purposes.  We have been trying to have a review with the Intel.  We are hoping for Bronze release to have a test instance of O-DU with Intel binary as a part of that.  There is still progress.  We are looking for contributions and activities for feedback and guidance.  It still has to go for the O-RAN legal team review.  Remember that's not Open Source Code.  The O-DU project is organizing that.
         1. Zhimin (Intel): we will provide a doc file in the O-SC community. 
   3. Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend. 
      1. Send Jack your 
   4. Action / ENGWEI KOO  - will add a deck to RSAC wiki.
      1. Engwei and Rittwik added the deck to the RSAC wiki.
   5. Action / Jinri Huang work with Farheen to add the MWC demos and presentations to the O-RAN SC wiki once posted to the O-RAN Alliance.
      1. O-RAN Alliance created a demo space.  Action/ Jinri Huang work with Farheen to put the virtual demos on our wiki.
   6. Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests. 
      1. The days have been finalized.  It will be the last week of Sept first week of October activities in all three zones.  It will be joint this time it will be joined with Integration and test team in Europe.  A series of events in Asia, Europe, North America.  Not duplicative but complimentary.
      2. Jack: Thank you Tracy.   It is important to learn from our activities.
   7. Action/ user-2057e update Vote Release Name page with the D release name option
      1. you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name
   8. Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
      1. This was done when we discussed the Cherry release.
   9. Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney  opened regarding the Calendar synchronization.
      1. Trishan: Yes, we came back with the recommendation to use the Confluence calendar with the UTC time.
      2. John: It will require people who have Confluence calendars to move over to the groups.io calendar and to change the calendars to UTC.  For a couple weeks the organizers around the world will have to decide what to do for the 
      3. Matin: Is it possible to remove the calendars?
      4. Trishan: We will work on doing that.
      5. Action / Farheen Cefalu update the Calendar Best Practices.  Remind Jack.
   10. Action/ PTLs update your project summaries with your sprint 2 status updates.  Be prepared to review your sprint 2 deliverables with the TOC.
       1. We are in sprint 3.  It is best to incrementally update each projects progress as we move forward.
   11. Action/ Jack will review Thoralf's How to request committer changes
   12. Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
       1. Lusheng: We will make it easier to find the information for SONAR on the Project Developer Wiki.
       2. Jack: Use the project developer wiki for Best Practices.
   13. Action/ William DIEGO update on coordination with the O-RAN test group
       1. William: We have contributions from CMCC AT&T, Orange.  Blueprints will be updated.  Work is ongoing.
       2. Jack: If there is a need to have a meeting let us know.
       3. Rittwik: We need to understand the specifications or testing activities.  We are contributing but I don't see a plan of how TIST and ORAN-Alliance will be coordinate.
       4. Jack: We need a simple flow diagram of our activities and their activities and how they are going to work together.
       5. Action/ William DIEGO provide more details of how the use cases and Jira items reflect the activities.  simple flow diagram of our activities and their activities and how they are going to work together.
   14. Action/ PTLs provide user-d3360  with your sprint 3 demos. 
       1. O-DU HIGH next Wednesday.
7. Standing Agenda Items (Brief Status of Ongoing Activities)
   1. Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
      1. Project Bronze Release
      2. Jack: Looking at our release plan.  Today is the 4-15.  That is dev 4 sprint ist sprint 3.  We are well into the development cycle process.  We have a week and a half to move into ETE testing and interoperability.  Looking at Jira items.  People testing software it is important to work issues between O-CU high and O-CU low.  All the modules need to work with the self test for the capability of the ETE use cases and the progress on the use cases.  Important to have documentation.  Looking at C release with Cherry I have restructured the table to reflect the Maintenance release to give folks a chance to get their backlogs items completed.  This is in Cherry even though it's Bronze release.
   2. user-59b16 Requirements Software Architecture Committee
      1. We are tracking the Traffic Steering use case closely.  Working with Viavi for metrics.  Ron is enhancing the E2 simulator.  That will get worked into this last sprint.  Matti has the TSxApp to make progress. Regards to healthcheck Martin and John.  Speaking to Eliza the healthcheck is getting more ellaborate if youre making changes check back with John Ng and David Kinsey.  If you're making large changes.
      2. John: John Ng is aware and is happy.
      3. Eliza: John will finalize the documentation, right?
      4. John: Yes, OTF documentation is coming together nicely.
      5. Eliza: We worked with Martin for healthcheck2.  Once we have the interface spec for healthcheck 3.  In the mean time the team was working with other information.
      6. John: Let us work together.
      7. Matti: Please keep me in the loop for the A1 healthcheck.  I need to know.
      8. Jack: The question is with all of that work is it staying aligned with the specs coming out of the O-RAN working groups?
      9. Rittwik: Not sure.
      10. Jack: I am making sure we are staying aligned.
      11. Martin: Yes, we try to keep aligned problem WG is 3GPP.  It looks similar but it's not with 3GPP.  I am directly in contact with 3GPP modeler.  There is good progress on the yang model.  This is a major step.
      12. Jack: Did you add that link?
      13. Action/ Martin Skorupski add the link for the yang model to the wiki.
      14. Martin: I wrote a script that will pull the yum models.
      15. Eliza: We need to document what we are doing.  We want to do it incrementally so we are in synch.  Also operators and vendors are supposed to create the tests.  It is important to provide the test team with instructions.
      16. Jack: it is important to carry evolution forward incrementally.
      17. Tracy: We are within working group 1 in the O-RAN Alliance.  We are forming a formal pathway to get the data models from O-RAN to 3GPP so there is version control easy to download data models.  That will be worked out in WG1 and properly documented.
      18. Jack: Do you see there will be yang models beyond 3G-PP.  
      19. Martin: We already have them.  Fronthaul Yang files are in gerrit for modeling.  Also from IXRAN to O-RAN.  They are available for the software community.
      20. Jack: is there an easier way to organize.
      21. Tracy: A reason for O-RAN Alliance we brought in the 5G baseline model from 3GPP and in parallel numerous 3GPP Yang models in need of repair.  They are upstream 3gPP and augmenting 3GPP.  I think we're going to have the repo reside where it is right now and allow access to the O-RAN software community.  We don't want to proliferate.
      22. Lusheng: What license are these under?
      23. Tracy: We are working one on one with the operator liason with 3GPP.
      24. Lusheng: Whether oran alliance 3gpp the question is are we hosting those models?
      25. Tracy: We won't host it on O-SC.
      26. Lusheng: Yes, we don't have to host it if it is in github.  We can just pull github.
      27. Martin: They don't have a license statement on github so we asked them to add their licenses for the yang models.
      28. Jack: the new ones that are generated in O-RAN where are they going?
      29. Martin: It's the decision of O-RAN Alliance.
   3. user-d3360  Integration and Test
   4. Report out from PTL: Stand-Up & Report Out on Blockers - next week we will start to cover this list.  Are there any major items that anyone would like to raise to the TOC this week? 
      1. John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
      2. Matti Hiltunen RIC Applications (RICAPP) 
      3. Thoralf Czichy RIC Platform (RIC) 
      4. user-a934b O-RAN Centralized Unit (OCU) 
      5. Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
      6. Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
      7. Martin Skorupski Operations and Maintenance (OAM)
      8. Alex Stancu Simulations (SIM)
      9. Xiaohua Zhang Infrastructure (INF)
      10. weichen ni Documentation (DOC)
      11. (TBD) O-RAN Radio Unit (ORU)
8. New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items. 

9. Planning for Next Meeting

10. Any Other Business (AOB) 

11. Meeting Summary (resolutions, new action items, etc.)

Return to Todays Agenda ^

Archived Meetings