Company | Name | Alternate |
---|---|---|
Jack Murray Co-Chair | Lusheng Ji | |
Jinri Huang Co-Chair | Weichen Ni | |
David Streibl | Ondřej Hudousek | |
Ericsson | John-Paul Lane | John Keeney |
Masafumi Masuda | Anil Umesh | |
Nokia | Juha Oravainen | Thoralf Czichy |
Orange | William Diego | Vincent Danno |
Radisys | Ganesh Shenbagaraman | Sachin Srivastava |
Viswanath Kumar Skand Priya | Kristen Young | |
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.
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:
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 |
Recording:
Agenda
Call for Scribe (minutes owner):
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 | ||
John-Paul Lane | x | John Keeney | ||
Masafumi Masuda | x | Anil Umesh | ||
Juha Oravainen | x | Thoralf Czichy | ||
William Diego | Vincent Danno | |||
Ganesh Shenbagaraman | x | Sachin Srivastava | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC 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
Release Votes and Approval.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Status of Open Action Items (Old Business).
Ganesh will elaborate the copyright issue regarding O-CU and O-DU, Sachin will check on O-CU and O-DU part with Ganesh
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.
Recording: 2020-09-02_toc.mp4
Agenda
Call for Scribe (minutes owner): David Streibl
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
---|---|---|---|---|
Jack Murray Co-Chair | Lusheng Ji | x | ||
Jinri Huang Co-Chair | x | Weichen Ni | ||
David Streibl | x | Ondřej Hudousek | ||
John-Paul Lane | x | John Keeney | ||
Masafumi Masuda | x | Anil Umesh | ||
Juha Oravainen | x | Thoralf Czichy | ||
William Diego | x | Vincent Danno | ||
Ganesh Shenbagaraman | Sachin Srivastava | x | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. // We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
Release Votes and Approval.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Tracy: Plug-fest preparation is moving forward. There will be virtual/ semi virtual demo in EU, USA, Asia, India
More details for O-RAN members on https://oranalliance.atlassian.net/wiki/spaces/TTIFG/pages/503971932/PF2+General.
If there is interested member of O-RAN willing to present, please contact TIFG
Followed up by US based event after Cherry release last week of November
Status of Open Action Items (Old Business).
Ganesh will also elaborate the copyright issue regarding O-CU and O-DU. Martin will send the written copyright issue description to Jinri and Jack so that Jinri could follow up. DONE.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.
Recording: TOC-weeekly-20200826.mp4
Agenda
Call for Scribe (minutes owner): Jinri Huang, China Mobile
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
---|---|---|---|---|
Jack Murray Co-Chair | Lusheng Ji | X | ||
Jinri Huang Co-Chair | X | Weichen Ni | ||
David Streibl | X | Ondřej Hudousek | ||
John-Paul Lane | X | John Keeney | ||
Masafumi Masuda | X | Anil Umesh | ||
Juha Oravainen | X | Thoralf Czichy | ||
William Diego | X | Vincent Danno | ||
Ganesh Shenbagaraman | X | Sachin Srivastava | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
There is no comment raised on the 0819 meeting minute.
Review of Today's Agenda
Release Votes and Approval.
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Status of Open Action Items (Old Business).
Ganesh: Call has been held to discuss the O-CU dependency with other projects. Key point raised: copyright issue for the 3GPP-defined yang model. Not have permission to use 3GPP yang model in OSC. Any development of the node, esp. CU and DU has to be on hold. The definition is from 3GPP; work can not move forward coz of this.
Rittwik: possible to write the code with STUB. With STUB, people could download the code. We do not inject to the repo. Just like ASN.1 issue. We do not get permission from 3GPP. However it did not stopping us from contribution. When permission coming through, we can open it up. Suggest to continue the work on health check. Not to defer to dawn.
Ganesh: Refer to model, generate the code, not to store the yang files in the repo?
Martin: Exactly how we do so far. We implement the code, save it in privie repo (a bit strange in open source community). Not have this code in any nexus, jenkin, whatever internal tool chain for OAM and SIM project. Can do domenstation to be functional. However, avoid generated code from YANG files at the time of being since somebody may think code generation is viewed as modification.
Ganesh: Any common code generation tool across projects?
Martin: No. Netconf servers or clients have their own code gernation for their purpose. Generate code from YANG for API. Avoid put it in nexus, or else where public.
Ganesh agree.
Rittwik: 2nd comment: Currently getting permission from 3GPP is stalled. Who is the LS/coordinator from O-RAN to 3GPP. Can OSC have direct line of comuincationw tiht 3GPP. Is that possible? Suggest Jinri to surface this up to the EC/TSC.
Jinri: Has the copyright issue been setnt o SDFG before? Old or new issue? Martin answered that it is an old issue. (half an year ago)
Jinri: Later on, we need clear record (of the copyright request/issue in the meeting minute. 2nd, some email from SDFG indictes that ETSI officers are on vacation. Will be back recently and speed up the process. 3rd, Jinri will surface this up to EC/TSC; 4th, we need to push SDFG.
Rittwik: could we have direct line of communication with 3GPP? Jinr: difficult.
For follow-up,
AP: Martin will send the written copyright issue description to Jinri and Jack so that Jinri could follow up. Ganesh will also elaborate the copyright issue regarding O-CU and O-DU.
Ganesh: WG5 also asking t how to handle the YANG model for ODU. Will check with them in the background.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.
Recording: TOC-weekly-20200819-audio-only.mp4
Agenda
Call for Scribe (minutes owner): Jinri Huang, CMCC
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
---|---|---|---|---|
Jack Murray Co-Chair | Lusheng Ji | X | ||
Jinri Huang Co-Chair | X | Weichen Ni | ||
David Streibl | X | Ondřej Hudousek | ||
John-Paul Lane | X | John Keeney | ||
Masafumi Masuda | X | Anil Umesh | ||
Juha Oravainen | X | Thoralf Czichy | ||
William Diego | X | Vincent Danno | ||
Ganesh Shenbagaraman | X | Sachin Srivastava | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
There is no comment raised on the 0812 meeting minute.
Review of Today's Agenda
One new items added:
Release Votes and Approval.
No update on this. EC is too busy to process the request. Jinri and Jack will continue to follow; Meantime, the written request by John has already been forwarded to EC and the legal team, waiting for response;
John: about A1 spec. the code is already ready, whether waiting for 60 days before releaseing the code needs feedback from O-RAN; JInri understood the issue and will continu to follow;
O-RAN-related business (marketing, WG interaction, TSC/EC update etc.)
Jinri mentioned that he noticed there was a TIFG-RSAC call on Monday discussing the MVP and asked for any update.
Rittwik responded that Koo is writing the minutes. This topic is also discussed in RSAC and he has uploaded the material. The goal is to come up with MVP requirement for TIFG.
Jinri asked about the concusion? What MVP should be?
Rittwik responded different people have diffrent Ideas. From OSC perspecitive, it is clear. We focus on 3 use cases. Want to validate them. For example for traffic steering, the minimum requriements include UE attachment, get E2 data, do the hand over. That is min. requiremens.
OSC should provide min. requirement that TIFG can review. And TIFG should come up with test spec.
Jinri invited Rittwik to to attend the call with WG1-UCTG, WG1 co-chairs and TIFG co-chairs to discuss MVP.
JInri asked a question on whether high level requirements are not enough for MVP.
Rittwik: Not high level. We had call flow there.
Question from Jinri: do you expect description of the features on certain interfaces?
Rittwik: call flows dictate what are the components and interface. If a call flow does not show, then not necessary. E.g. in O-CU discussion, the E1 interface is not required, then it is not required for traffic steering use case (as a minimum requirement).
Status of Open Action Items (Old Business).
Ganesh indicated that there was already some discussion on this topic in RSAC. MVP was discussed. A concern is raised in that now we are running out of time for cherry. What content to agree for traffic steering use case in terms of E2 messages, lelvel of CU-DU functionalities etc.. For this Ganesh followed up DU team. They seemed to be ready with message with some already implemented in Bronze release and the others in this release. Question is about CU: By when to finish the work? Need decision from TOC on how to proceed considering that we do not have enough time to push all the content. How to prioritize?
Rittwik: There is no enough visibility of CU in the wiki (need weekly meting update. Need weekly meeting with others). It is difficulty to track the features. No idea on aligning or misaligned with planning. Suggest to prioritize some features to ensure traffic steering to be realized.
JInri indicated that there was a re-org inside CMCC and the O-CU PTL has moved to other position. the O-CU work is not the major obligation. We are discussing with a partner company.
Q: how many features for O-CU in Cherry release?
A: UE Attach; Hand over action, traffic steering app to provide the control action.
Q: Did O-CU project promise to support the features?
A: NO. O-CU is working on other aspects.
AP: The team to arrange an offline meeting to further discuss the challenges. Gu Su from China Mobile can help.
Matti: What is the summary table means? For Bronze release , we hve a wike page. Not one for cherry. Where to update? Or is it excel spreadsheet?
Lusheng: a wiki page with template, will it help? Farheen do that last time. Lusheng will help this time.
AP: Lusheng to create a wiki page with a template for PTL to fill in the Cherry deliverable summary
Jack to talk with Trisan offline to make sure the voting process is right.
Q: in addition to ONAP, what other open source communities are you heavily involved and contributed?
A: Mainly ONAP. Yet also moved around LINUX, internally (inside Ericsson) wrote linux kernel (not contributing);
Q: Your role in ONAP?
A: Design the architcure policy framework; involved in control loop committee, lead the development part in Ericsson; is one of the biggest contributors for Ericsson in ONAP;
Q: What is your view on the relationship b/w SMO and ONAP; i.e. what components should be developed in ONAP and OSC respectively?
A: Not doing SW in OSC which has been developed in ONAP; The OSC coding would be more about use cse side of thing as user advise. Bringing back to ONAP would be powerful;
Presentation by Mahesh Jethanandani
Q: If becoming the PTL, how many resources to bring in?
A: Have contact with OSN, OPENDALYLIGH etc. Could generate enough interest in the group. They would be interest.
For the next step, Trisan will contact JInri and start the voting process. There is a tool for the voting;
Reminder again from Jinri on this topic. There will be a TSC call in two weeks. need to report the progress there.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.
Recording: TOC-weekly-20200812.mp4
Agenda
Call for Scribe (minutes owner): Jinri Huang from China Mobile
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 | ||
John-Paul Lane | X | John Keeney | ||
Masafumi Masuda | X | Anil Umesh | ||
Juha Oravainen | X | Thoralf Czichy | ||
William Diego | X | Vincent Danno | ||
Ganesh Shenbagaraman | X | Sachin Srivastava | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC voting members unless excluded due to attendance. We have a quorum and can vote on activities.
Review and Agree to Minutes of Previous Meeting
There is no comment raised on the 0805 meeting minute.
Decision: Moved by Jinri and seconded by David, without objection and abstention, the 20200805 meeting minute is approved.
Jack also mentioned that the history TOC meetings are also archived. The link is at the bottom of the page.
Review of Today's Agenda
No new agenda items raised. Some topics, such as some remaining question regarding the Bronze Maintenance Release, the nomination status etc. will be discussed in old business section (e.g. release note etc.)
Release Votes and Approval.
Jack mentioned that there were a couple of APs last week regarding the Maintainence Rel.
Lusheng responded: one request is from Jinri which is about a summary of changes. That was done. See https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=14221635. Regarding the licensing, 2 ways. One is to manually went through all the updated files to make sure the licensing is ok. Another check is done by Steve from LF. No problem found. Also clarified that O-CU is not in the scope.
Jack: did that address people’s questions to cover the maintenance Release? Any more question? No response.
Motion moved by Lusheng to accept and release the Bronze maintenance release;
Jinri seconded;
There was a comment from John-Paul, indicating that he was not on the call last week. Will vote in the dark. Jack indicated that last week John Keeney was the deputy and he did not raised an critical issues. Indeed, he also indicated some updated on NRT RIC in the maintenance release. John is fine with the response.
ALL the TOC members voted yes. There is no objection/abstaintion.
Decision: The maintenance release is approved.
Marketing of the current release (WG, LF, PR)
Jinri indicated that this item is not just about marketing. It should be related to many other O-RAN issues. Suggest to change the name to O-RAN-related business (EC/TSC/WG/, marketing etc.);
Jinri indicated recently O-RAN has initated the work on TSC-level minimum viable product (MVP) which is important to OSC’s future planning. Will come back with more information when there is more consolidated result.
Jack also indicated that more representation should be in the RSAC from different companies. All the major companies involved should be part of the RSAC committee. PTL have already been there. Operators should also be there too. So people could understand better. Sometime, two lines of items means 2-year coding. Understanding where the SW is from our standpoint to where we can achieve, the goal is important to their process. RSAC should be involved in the discussion. At least some people. It is daunting to steer through the list of spec. and capabilities for any particular release. Always a lot of opportunity there. Yet what to focus with the limited resource? How to do that? Getting more people involved. RSAC is important.
Lusheng will be leaving on from the assignment from a couple of weeks later, expecting people to step in and help; will be some big gap (lusheng has been doing a lot); need more participation in that space; ATT will participate yet need someone to take leadership there;
Status of Open Action Items (Old Business).
O-CU update. See the presentation. https://wiki.o-ran-sc.org/download/attachments/10715432/OSC%20O-CU%20RelC%20-ICT-8.12.pptx?api=v2
Questions are raised on e.g. whether the handover procedure could be supported, how/when the O-CU could be integrated with O-DU-HIGH. Some discussion on this. No conclusion. A suggestion from Jack is to request O-CU PTL to organize a meeting and invite all the relevant projects (O-DU-HIGH, OAM, RIC etc.) and discuss the cooperation. Another suggestion from Rittwik is to prioritize the items shown on the slide to make sure some key features such as handoff could be supported for traffic steering use case. It is indicated that if we wait for the 3GPP O-CU features to be finished and then add on the E2 support, it will be two release late.
A reminder to make sure work is ongoing. Will go throught the table in the upcoming week;
Currently there are two nomination from Ericsson and VMWare. The nomination will be open until next week TOC call. After that, the voting will be kicked off.
AP: Jack will talk with Trisan offline to make sure the voting process is right.
Next TOC call, the candidates will be invited to give a short introduction talk.
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
Matin not here. Alex made the presentation which is on https://wiki.o-ran-sc.org/display/OAM/2020-08-12+OAM+report
There was a question out there relevant to OTF team and Alex is suggested to reach David Kinsey for help.
Question from David: If go with DECA microseverice, how much of the DCAE needed up and running in the environment for the OSC to be functional? No conclusion/answer to it. Will be discussed in RSAC. In particular, it is also related to the job division b/w SMO, OAM, ONAP.
David: RSAC this week not holding meeting, rittwik not available. Suggest to hold this question off and line it up after we have the SMO vote to make sure have right people on; Later there will be two RSAC meetings per week. We are already a little behind for the cherry;
Jack: Regarding how to work with other projects, EC is pushing us to enhance the cooperation; would like to make sure RSAC involved in any requirements we asked for. There is a Jira request on our side document that request and how we can use it. Be careful about how much we build requirement for ONAP. Not all the communities are committed to ONAP. Have to make sure the committeement we made. That is why we need more participation in RSAC going forward. Need better job of coordination;
Tracy: for some of the requirements that are understood, are you meaning creating corresponding jira ticket in the OSC or coross-referencing? Jack: yes. Not want to duplicate things. There is need to record the process so O-RAN can find out what we are relying on them.
Alex Stancu Simulations (SIM)
Xiaohua Zhang Infrastructure (INF)
weichen ni Documentation (DOC)
(TBD) O-RAN Radio Unit (ORU)
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.
Recording: TOC-weekly-20200805.mp4
Agenda
Call for Scribe (minutes owner): Lusheng Ji (AT&T)
Roll Call & Quorum Check
Company | Contact Name | Attendance | Alternate Contact | Attendance |
---|---|---|---|---|
Jack Murray Co-Chair | Y | Lusheng Ji | ||
Jinri Huang Co-Chair | Y | Weichen Ni | ||
David Streibl | Y | Ondřej Hudousek | ||
John-Paul Lane | John Keeney | Y | ||
Masafumi Masuda | Y | Anil Umesh | ||
Juha Oravainen | Y | Thoralf Czichy | ||
William Diego | Y | Vincent Danno | ||
Ganesh Shenbagaraman | Y | Sachin Srivastava | ||
Viswa Kumar | Kristen Young |
*Quorum: 50% or more of total TOC 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
Release Votes and Approval
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.
Recording: GMT20200729-120223_Zoom2-O-RA_1920x1020.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 | Ondřej Hudousek | |||
John-Paul Lane | x | John Keeney | ||
Masafumi Masuda | x | Anil Umesh | ||
Juha Oravainen | x | Thoralf Czichy | ||
William Diego | x | Vincent Danno | ||
Ganesh Shenbagaraman | Sachin Srivastava | |||
Viswa Kumar | Kristen Young |
*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
Vote to approve minutes for
Review of Today's Agenda
Release Votes and Approval
Marketing of the current release (WG, LF, PR)
Status of Open Action Items (Old Business)
Standing Agenda Items (Brief Status of Ongoing Activities)
Release Manager Trishan de Lanerolle /Release Planning: Weekly TOC Scheduling
user-59b16 Requirements Software Architecture Committee
user-d3360 Integration and Test
Report out from PTL: Stand-Up & Report Out on Blockers
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)
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.)
Review and Agree to Minutes of Previous Meeting
Vote to approve minutes for