...
- Swaminathan Seetharaman
- Borislav Glozman
- Dongho Kim
- Sandeep Shah
- Zu Qiang
- Oskar Malm
- Prabhu
- Bob Papa
- 46107114668
- Mduduzi Mudumbe
...
Discussion items
Time | Item | Who | Notes | |||
---|---|---|---|---|---|---|
M1 Deadline Deliverables | All in 5G U/C | All in 5G M1 Deliverables, DEADLINE: Oct 31, 2019 TSC Evaluation & Integration leads - Deadline Oct 15, 2019 Release Planning Page: Release Planning M1 Deliverables Checklist: Deliverables for Planning Milestone Checklist Template (1) TESTING - Integration Testing End-to-end use cases listed (2) PTLs - commitments from the Platform component PTLs (3) RELEASE PAGE - Frankfurt Release Requirements page needs to be updated. (4) MODEL - Modeling Requirements Page for R6 (Planning) ONAP R6 Modeling High Level Requirements (5) CHECKLIST - Deliverables for planning milestone checklist template: Deliverables for Planning Milestone Checklist Template Checking & cross-checking that Epic REQ-# Jira tickets are made (Sept 19)
INTEGRATION DISCUSSION Oct 17 2019 - | Antwerp F2F | Reviewed Release Requirements ACTIONS:
|
Dongho Kim - discussing with Ericsson and AT&T who can commit. A1 adaptor unit testing. For O1 part Nokia. CMnotif. fault, CallTrace(no), ...
2. RunTime Config DB Integration Lead
3. OOF/SON/PCI U/C Integration Lead
4. Pre-onboarding/Onboarding U/C We do not need full E2E Integration Zu Qiang , only need to integrate the new development in VNF-SDK ACTIONS:
| |
ORAN ONAP Plugfest Demos | All in 5G U/C | Realization Call Oct 16 Use Case Realization Call: October 16, 2019 Discussion with Tracy Van Brakle Demos will be on Dec 5, 2019 (AM EDT UTC-4 USA) | ||||
R6 Use Case Proposals / Requirements | All in 5G U/C | TSC Release Page. Frankfurt Release Requirements In the REQUIREMENTS Table of the R6 Release Requirements Wiki (above) the Use Case requirements as discussed on the TSC call for Sept 12, and David McBride has asked that we have requirements (jiras) on separate rows. Further follow-up discussions will be had for "what is a use case" and if some of the 5G use cases should be moved up to the first table. | 5G U/C Team | Updating Component impacts Table | ||
RunTime DB | Use Case presentation. | Architecture S/C presentation for Run Time DB. Documenting (1) Arch component wiki ARC RunTime DB Component Description - R6 Frankfurt (2) Flow using Run Time DB. Presented Oct 15, 2019. (3) Making RunTime DB as a separate common service component - Discussed at the Architecture S/C oct 2, need a follow-up agenda item on the Arch S/C meeting, will request for Oct 9.Oct 23. (4) Need to present TSC AFTER approval from Architect S/C. (5) Meeting with David McBride | ||||
Network Slicing R6 Proposal | Update on slicing proposal. SO/Seshu presented. Multiple functional requirements/Use Cases. Recursive orchestration of nested services. Didn't want independent W/F for flows but try to leverage/reuse work. Presented the End to End U/C with macro-view for E2E slice. and components impacted. Right now impact will be on SO, OOF, Policy, SDC and AAI. What controller will be used for managing slices? Focusing on design aspects and instantiation and activation. Put up logical E2E slice. Target simple VNFs. Focus to create VNF vs reconfiguring a VNF? Slice segments are going to be both dedicated/shared. Started with discovering existing resources; assume segments created with VNF/PNFs in inventory & discoverable. Spinup new slice instances. Setting up regular meetings? Ad-hoc meetings. Presentation/slides at: NETWORK SLICING PoC in R6 Frankfurt F2F - 2 presentations on Network Slicing China Model - create slice across multiple service providers - dynamic slice creation use Ext.API Prov#1/#2. Slice aware KPI - analytics. Swami had an action item to make 1 use case. Presentation. to present to architecture S/C. Proceed towards M1, additional requirements can be integrated and the merging to the two Network Slicing U/C proposals can proceed in parallel. Let's keep the use cases working in parallel and then merge them later. Convergence plan merging the two proposals by Oct 17, 2019. Convergence Plan Presented Oct 17, 2019 Setting up Regular meetings Discussion: Milind Jalwadi (Unlicensed) JSON based screens for VID would want to upstream that NSST NSSD Part of the Network Slicing Use Case. | |||||
ORAN/3GPP ONAP Harmonization U/C | Trying to settle on scope of the Use Case. List of many possible contributions that will take more than one release to complete. Impacts for items to be added to wiki (analysis). Prioritize the work items what we could propose to accomplish. | |||||
WoW w/ Model & Arch | Way of Working between Architecture , Modeling Subcommittee & Use Case Teams and what happens and touchpoints at M0/M1/M2/M3. | |||||
Use Case Template | 5G U/C Team | Use Case Template - discuss updating the Use Case template & pages with some of these fields. Modeling team has said it would be useful for them to have the pre-condition & post-conditions, and information being passed (info-flows) documented. Filling out, describing and creating the Wiki for a Use Case | ||||
SUPPORTING SLIDES
Document | File |
---|---|
Network Slicing Convergence Plan
| |
RECORDING
Recording | File |
---|---|
MP4 (Video + Audio) | |
Audio Only | |
M3U, Chat |
...