TOC Voting Members
Company | Name | Alternate |
---|---|---|
Jack Murray Co-Chair | Lusheng Ji | |
Jinri Huang Co-Chair | Weichen Ni | |
David Streibl | Ondřej Hudousek | |
Masafumi Masuda | Anil Umesh | |
Orange | William Diego | Vincent Danno |
Viswanath Kumar Skand Priya | Kristen Young | |
Juha Oravainen | ||
Ganesh Shenbagaraman | ||
John-Paul Lane | ||
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.
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
City | Time | Zoom/Audio Bridge |
---|---|---|
UTC-time | Wednesday 12:00 | |
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) | Mar-11/Mar-18/Mar-25: Wednesday 13:00 Apr-1-2020 onwards: 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) | Mar-11/Mar-18/Mar-25: Wednesday 14:00 Apr-1-2020 onwards: Wednesday 15:00 | +358 341092129 Meeting ID: 654 056 8082 |
2020 04 15
Recording: 2020-04-15_TOC.mp4
Agenda
- Call for Scribe (minutes owner) Farheen Cefalu
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji Jinri Huang Co-Chair
x Weichen Ni David Streibl
x Ondřej Hudousek Masafumi Masuda
x Anil Umesh Orange William Diego
x Vincent Danno Viswa Kumar
Kristen Young Juha Oravainen
x Ganesh Shenbagaraman
x 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.
Review and Agree to Minutes of Previous Meeting
- Review of Today's Agenda
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Vote to approve minutes for
- On motion made by user-2057e
- Seconded by Juha Oravainen
- VOTE: Vote taken, item passed
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Release Votes and Approval
- Vote Release Name: Vote is active to choose name of "D" release.
- Running the vote until Saturday. It looks like Dawn will be the color.
- OCU new repo 5G
- 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.
- Yingying: For O-CU I have a new repo request 5GNR.
- 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.
- 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?
- Jinri: The request was raised in March is a part of the restart process. Thank you for this reminder.
- Lusheng: This request is still outstanding. We will send this out to the main mailing list.
- Jinri: I approved two.
- 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?
- Ganesh: We are re-writing all the code?
- 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.
- Jack: Request a vote to approve a new O-CU 5G repo
- Vote to approve a new O-CU 5G repo
- On motion made by Jinri Huang
- Seconded by user-2057e
- VOTE: Vote taken, item passed
- Vote Release Name: Vote is active to choose name of "D" release.
- Marketing of the current release (WG, LF, PR)
- ONES = LF Networking Conference tentatively August/ September (Los Angeles). Open Networking & Edge Summit Event
- Action/ Jinri Huang communicate the online events on the wiki.
- ONES = LF Networking Conference tentatively August/ September (Los Angeles). Open Networking & Edge Summit Event
- Status of Open Action Items (Old Business)
Action/ update on O-CU plans- It is important to have the team do contributions to draw more people to participate in your project.
Action/ update on Intel license agreement on binary usage- 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.
- Zhimin (Intel): we will provide a doc file in the O-SC community.
- 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.
Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend.- Send Jack your
Action/ ENGWEI KOO - will add a deck to RSAC wiki.- Engwei and Rittwik added the deck to the RSAC wiki.
- 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.
- O-RAN Alliance created a demo space. Action/ Jinri Huang work with Farheen to put the virtual demos on our wiki.
- Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.
- 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.
- Jack: Thank you Tracy. It is important to learn from our activities.
Action/ user-2057e update Vote Release Name page with the D release name option- you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name
Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.- This was done when we discussed the Cherry release.
- Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney opened regarding the Calendar synchronization.
- Trishan: Yes, we came back with the recommendation to use the Confluence calendar with the UTC time.
- 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
- Matin: Is it possible to remove the calendars?
- Trishan: We will work on doing that.
- Action / Farheen Cefalu update the Calendar Best Practices. Remind Jack.
Action/ PTLs update your project summaries with your sprint 2 status updates. Be prepared to review your sprint 2 deliverables with the TOC.- We are in sprint 3. It is best to incrementally update each projects progress as we move forward.
Action/ Jack will review Thoralf's How to request committer changesAction/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.- Lusheng: We will make it easier to find the information for SONAR on the Project Developer Wiki.
- Jack: Use the project developer wiki for Best Practices.
- Action/ William DIEGO update on coordination with the O-RAN test group
- William: We have contributions from CMCC AT&T, Orange. Blueprints will be updated. Work is ongoing.
- Jack: If there is a need to have a meeting let us know.
- 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.
- Jack: We need a simple flow diagram of our activities and their activities and how they are going to work together.
- 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.
- Action/ PTLs provide user-d3360 with your sprint 3 demos.
- O-DU HIGH next Wednesday.
- Standing Agenda Items (Brief Status of Ongoing Activities)
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- Project Bronze Release
- 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.
- user-59b16 Requirements Software Architecture Committee
- 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.
- John: John Ng is aware and is happy.
- Eliza: John will finalize the documentation, right?
- John: Yes, OTF documentation is coming together nicely.
- 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.
- John: Let us work together.
- Matti: Please keep me in the loop for the A1 healthcheck. I need to know.
- Jack: The question is with all of that work is it staying aligned with the specs coming out of the O-RAN working groups?
- Rittwik: Not sure.
- Jack: I am making sure we are staying aligned.
- 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.
- Jack: Did you add that link?
- Action/ Martin Skorupski add the link for the yang model to the wiki.
- Martin: I wrote a script that will pull the yum models.
- 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.
- Jack: it is important to carry evolution forward incrementally.
- 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.
- Jack: Do you see there will be yang models beyond 3G-PP.
- 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.
- Jack: is there an easier way to organize.
- 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.
- Lusheng: What license are these under?
- Tracy: We are working one on one with the operator liason with 3GPP.
- Lusheng: Whether oran alliance 3gpp the question is are we hosting those models?
- Tracy: We won't host it on O-SC.
- Lusheng: Yes, we don't have to host it if it is in github. We can just pull github.
- Martin: They don't have a license statement on github so we asked them to add their licenses for the yang models.
- Jack: the new ones that are generated in O-RAN where are they going?
- Martin: It's the decision of O-RAN Alliance.
- user-d3360 Integration and Test
- 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?
- John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
- Matti Hiltunen RIC Applications (RICAPP)
- Thoralf Czichy RIC Platform (RIC)
- user-a934b O-RAN Centralized Unit (OCU)
- Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
- Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
- Martin Skorupski Operations and Maintenance (OAM)
- Alex Stancu Simulations (SIM)
- Xiaohua Zhang Infrastructure (INF)
- weichen ni Documentation (DOC)
- (TBD) O-RAN Radio Unit (ORU)
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
- Planning for Next Meeting
- Any Other Business (AOB)
- Meeting Summary (resolutions, new action items, etc.)
2020 04 08
Recording: 2020-04-08_toc.mp4
Agenda
- Call for Scribe (minutes owner) Chris Lott
Roll Call & Quorum Check
Company
Contact Name
Attendance
Alternate Contact
Attendance
Jack Murray Co-Chair
x
Lusheng Ji Jinri Huang Co-Chair
x Weichen Ni David Streibl
x Ondřej Hudousek Masafumi Masuda
x Anil Umesh Orange William Diego
x Vincent Danno Viswa Kumar
Kristen Young Juha Oravainen
x Ganesh Shenbagaraman
x 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.
Review and Agree to Minutes of Previous Meeting
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Vote to approve minutes for
- On motion made by user-2057e
- Seconded by Juha Oravainen
- VOTE: Vote taken, item passed
- The minutes of the prior meetings were reviewed, and there were no comments, questions or corrections.
- Review of Today's Agenda
Issue of licensing and code contributions in O-CU gerrit repos
LF investigated also
taking an unusual activity for our community, code needs to be removed
will restart the O-CU project with new, empty repos
rebuilding is the easiest way to clean up and address all concerns
re-examining some best practices
concerns?Rittwik asked, integrated eNodeB OCU or distributed eNodeB OCU?
Jack answered, Affects all OCU repos.
Jack asked, how much OCU is used in this release?
Rittwik answered, not very much.
William asked, new contributors in OCU?
Jack answered, contributors to area of concern have changed; 4G area
has been reexamined; 5G area has different contributors; focusing on
5G portion which didn't have code/licensing issues
William asked, only 4G code is impacted? 5G also?
Jack answered, going thru process for both as everything is
re-submitted, adhering to guidelines; LF giving guidance how best to
proceed.
John Paul asked, how to capture lessons learned from OCU project,
publicize to other projects?
Jack answered, this gives us an opportunity to review best practices
and make sure people are aware & complying, following well-established
open source guidelines for all projects, so other projects can avoid
complications. Rely on contributors to follow guidelines, sometimes
have to clean things up, taking a strong step to address the
concerns.
John Paul asked, these principles and guidelines, where are they
published?
Jack answered, the O-RAN-SC wiki has the page, not easy to find,
https://wiki.o-ran-sc.org/display/ORAN/Best+Practices
- Release Votes and Approval
- Vote is active to choose name of "D" release.
Leading candidate today is "Dawn"
What color is Dawn? Nobody was quite certain.
- Vote is active to choose name of "D" release.
- Marketing of the current release (WG, LF, PR)
- ONES = LF Networking Conference tentatively August/ September (Los Angeles). Open Networking & Edge Summit Event
- Status of Open Action Items (Old Business)
- Action/ new TOC members provide an alternate contact for TOC calls when they are unable to attend.
- Action / ENGWEI KOO - will add a deck to RSAC wiki.
- 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.
- Action / Tracy Van Brakle clarify Open Testing and Integration (OTIC) North America
- Action/ Farheen Cefalu work with Tracy Van Brakle to update the events page with plugfests.
- Action/ user-59b16 upload the UE emulator short/long term slide deck to the RSAC page.
- Action/ TOC provide feedback to Jack regarding the Cherry and D Release calendars on the Releases page
- Action/ Jinri Huang will point Thoralf Czichy to the appropriate WG specification times. There are 3 trains for the specifications.
Action/ user-2057e update Vote Release Name page with the D release name options.you can now vote on name for release D here: https://wiki.o-ran-sc.org/display/REL/Vote+Release+Name
- Action/ Jinri Huang provide the TOC with the new O-RAN Alliance timeline.
- Action/ Trishan de Lanerolle let us know the outcome of the ticket that John Keeney opened regarding the Calendar synchronization.
- Action/ PTLs update your project summaries with your sprint 2 status updates. Be prepared to review your sprint 2 deliverables with the TOC.
- Action/ Jack will review Thoralf's How to request committer changes
- Action/ user-d3360 add the wiki link for SONAR to the Integration and Test wiki where people can easily find.
- Action/ user-59b16 set up a meeting with Viavi, O-RAN Alliance test committee (whoever is leading the test committee (David Orloff)), and the TOC.
- Action/ William DIEGO we need a test coordinator with the O-RAN test group so we can come up with a common plan between the test groups
- Action/ user-d3360 add the link in the Integration and Test wiki to the SONAR instructions that you discussed on TOC meeting.
- Action/ PTLs provide user-d3360 with your sprint 2 demos.
- Standing Agenda Items (Brief Status of Ongoing Activities)
- Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
- 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?
- Matti Hiltunen RIC Applications (RICAPP)
Ongoing activity RIC applications -
Matti H. gave update that a person is assigned for simulator
- Thoralf Czichy RIC Platform (RIC)
- note I updated the committer change process as per discussion last week: How to request committer changes.
Thoralf C. gave update
. many epics in Bronze release
. 8 done, 6 in progress, 38 not started
. 2 new epics related to ASN.1 problemThoralf C. asked, is there progress on ASN.1 legal issues with 3GPP and
ORAN Alliance?
Jack M. answered, writeup is being reviewed, process is onerous, have to
go to board for permission
Jinri H. answered, EC has reviewed, (?) has approved, then will forward
request to board
Jack M. answered, once approved it can be used by all ORAN projects, not
just one
Jinri H. clarified, this is for ASN.1; Hank wants to broaden request.
Current request is from Thoralf targeting specific ASN.1 content in
one ORAN specification. Want to broaden this to apply to all the
ASN.1 content from ORAN alliance. Hank wants to improve/refine the
proposal so it's a bit on hold. Expect to hear tomorrow. Once the
specific request is approved, it will apply to all projects.Held demo of development sprint 3, recording is available for people to
view
- user-a934b O-RAN Centralized Unit (OCU)
- Ongoing activity - OCU
skipped, have discussed the exception being handled there
- Ongoing activity - OCU
- Sachin Srivastava O-RAN Distributed Unit High (ODUHIGH)
- Ongoing activity - ODUHIGH
Sachin of Radisys gave update
Demonstrated F1-U and F1-C
working on traffic steering implementation, that will be in next
demonstration, with limitations based on specification
working with Intel team on IPC mechanisms and L1
might have to push some content to Cherry release due to recent late
changes
expect to be formally available in ORAN wiki
Jack asked, please update wiki page to capture progress
Sachin added, seeing lots of effort required here
Jack asked, are working group specifications coming out, how is the
interface to the WGs functioning?
Sachin answered, they are aligning to specifications; also dependent on
E2 SM specifications, may have to adapt
- Ongoing activity - ODUHIGH
- Zhimin Yuan O-RAN Distributed Unit Low (ODULOW)
- Ongoing activity - ODULOW
Zhimin Yuan of Intel gave update
working on shared memory feature between ODULOW and ODUHIGH
Jack asked, have you updated wiki pages with status?
Zhimin answered, have updated for front haul library; other pieces in
development
Rittwik asked, for the WLS binary files, this is not exactly open
source, cannot see the IPC mechanisms used, is this done or in
progress?
Zhimin answered, in progress, shared with Radisys
Rittwik asked, how will it work eventually?
Zhimin answered, get approval from Intel, pass legal check
Rittwik asked, will be approved for Bronze release?
Zhimin answered, it is possible but not definite
Rittwik noted, this is a bilateral arrangement today; unclear how it
will work in the future
Zhimin answered, working for approval by end of May
- Ongoing activity - ODULOW
- Martin Skorupski Operations and Maintenance (OAM)
- Ongoing activity - OAM
Martin S. of Highstreet gave update
Working to finalize the deployment
Contribution depends on YANG models
Got in contact with 3GPP YANG developers directly for assistance
Hoping to use YANG models as basis in Cherry release
Identified use case to be proposed for Cherry, a software update from
XRAN device, becomes ORAN front-haul device, maybe O1 device
Jack suggested, get this in early to requirements group
Martin noted, Jira pages are very slow to load
Jack asked, how are demonstrations of health check going?
Martin answered, demonstration tomorrow of using a health check, but
not sure if it can be recorded; demo can be repeated anytime
- Ongoing activity - OAM
- Alex Stancu Simulations (SIM)
- Ongoing activity - simulators
Alex S. of Highstreet gave update
finally have a resource to work on simulator
hope to finish what they need for traffic steering use case
working on build job for Jenkins at LF
health check use case is implemented in the project
John is working on moving A1 stub simulator into repos
Jack asked, stub simulator in this release?
Alex answered, yes only have to move Jenkins jobs
- Ongoing activity - simulators
- Xiaohua Zhang Infrastructure (INF)
- Ongoing activity - infrastructure
Xiaohua Z. of Wind River gave update
By end of March had ARM-based K8S cluster available
Want to use third-party layer1/layer2 to demonstrate
Invites people to look at code in integration repo
working with ODULOW project so their deliverable meets requirements
hope to finish this week, plan to work with integration team in
integration lab
rest of Jira is related to platform services enabling, ongoing
schedule is challenging, have good chance to finish in Bronze
holding biweekly meetings, minutes are in the wiki
Jack asked, will ARM-based system be available to wider community, to
see the demo?
Xiaohua answered, code has been upstreamed into repo, instructions are
uploaded how to build and run demo, but Layer 1/layer 2 applications
are from third-party company, only agreed to use as demo not open
source, shows capability of ARM-based platform
Jack noted, important to have diversity in the project; please follow
best practices around open-source contributions vs test fixtures, make
clear what's open source and what is only a demo test fixture
- Ongoing activity - infrastructure
- weichen ni Documentation (DOC)
- Ongoing activity - documentation
Weichen N. of China Mobile gave update
not many new features
created a label on documentation page to switch between branches
already have amber from last year
when we release bronze release, can have selection button for bronze
next is API documentation
if any project is willing to add API doc, please let Weichen know and
he will collect the doc from different projects to form OSC API
document
Jack asked, need to pull together doc on end-to-end use cases part of
Bronze release; work with RSAC committee to understand where will we
send someone as part of Bronze release to see use cases, also a
description of how to recreate/download/build use cases as end user;
people need to learn from use cases, as projects deliver their pieces
and users come in to see what we have done
- Ongoing activity - documentation
- John Keeney Non-RealTime RIC (RAN Intelligent Controller) (NONRTRIC)
- Reached 9am, unable to hear John's update on NON realtime RIC,
John will go first at next meeting
- Reached 9am, unable to hear John's update on NON realtime RIC,
- (TBD) O-RAN Radio Unit (ORU)
- Matti Hiltunen RIC Applications (RICAPP)
- user-59b16 Requirements Software Architecture Committee
- user-d3360 Integration and Test
- New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items.
- Planning for Next Meeting
- Any Other Business (AOB)
- Meeting Summary (resolutions, new action items, etc.)