2019 05 01

Agenda

Call for Scribe (minutes owner)
Roll Call & Quorum Check
Review and Agree to Minutes of Previous Meetings
Review of Today's Agenda
Status of Open Action Items (Old Business)
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:

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

Company	Contact Name	Attendance	Alternate Contact	Attendance

Company	Contact Name	Attendance
AT&T	Jack Murray Co-Chair	x
China Mobile	Jinri Huang Co-Chair	x
Deutsche Telekom	David Streibl	x
NTT DOCOMO	Toshiro Kawahara
Orange	Vincent Danno	x
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.

Standing Agenda Items (Brief Status of Ongoing Activities)
- Release Manager/Release Planning: Weekly TOC Scheduling
- Report out from PTL: Stand-Up & Report Out on Blockers
- Test & Integration Planning
- Report Out of Sub-Committees
New Agenda Items (New Business): New Items Submitted (+speaker) & Open Call to TOC For Additional Items
- There is an ORAN Alliance meeting in June in Japan. Action Jinri post the ORAN Alliance meeting information to the TOC mail list.
- Release calendar
- M0 starts in a few weeks and we have to recruit working.
  - We need people to pull together the requirements that will lead to epics, and user stories and start sprints.
  - We need to have the main goals and a list of requirements pooled into one place. In a normal cycle in planning M1 a community can work on preparing for the B release. F
  - We have to come up with Naming convention for our releases. Cities, rivers, etc...
Planning for Next Meeting
Open Discussion
Any Other Business (AOB)
Meeting Summary (resolutions, new action items, etc.)
- Resolutions
  - Selected first sub-committee called Requirements and Architecture.
- Action Items
  - Action Phil has the request in to LF does not have a timeline from them and will continue to push.
  - Action Farheen set up the new committee in the wiki and new committee list
  - Action Lusheng will post a list of proposed projects and their structure to the mailing list after the meeting.
  - Action: We will have a discussion around projects in our next meeting.
  - Action: Need a volunteer to work with O-RAN WG. The O-RAN Alliance TSC handles filling in the position O-RAN OFG.
  - Action: Jinri will push on completion of the charter.
  - Action: Jack will push on the completion of the license.
  - Action: ToC membership slot filling.
  - Action Jinri post ORAN event in Japan in June to committee mail list.
  - Action TOC come up with a list of features or epics before the M0 start date.
  - Action TOC come up with a naming convention for our releases.