- Benjamin Cheung
- Borislav Glozman
- Bob Papa
- Sangeeta Nitin Bellara
- S. Ricci
- Joanne Liu Rudel
- Dongho Kim
- Zu Qiang (Ericsson)
TIME FOR THIS MEETING WILL BE 2PM UTC = 10AM EST (USA); 7 AM PST (USA)
Discussion this week
|All in 5G U/C|
Use Case WoW Process: ONAP Use Case / Requirements Teams Process Way of Working (WoW)
|M4 Deadline Deliverables|
All in 5G U/C
M4 for R6 Deliverables DEADLINE:
R6 Frankfurt Release: Frankfurt Milestone Status
Release Planning Page: Release Planning
M1 Deliverables Checklist: Deliverables for Planning Milestone Checklist Template
Deliverables by Milestone: Frankfurt Deliverables by Milestone
(1) FUNCTIONALITY FREEZE -
M2 MILESTONE: Functionality freeze
No new visible functionality is to be added to the current ONAP release.
A stable document describing the API is documented and available in wiki.
Base set of impacts to VNF Requirements identified by use case/ project.
(2) API & DATA MODEL FREEZE -
M3 MILESTONE: API & data model freeze.
Mark the end of API and Data Model change. API and Data Model are now Frozen.
Any changes to the API must be brought to the knowledge of the TSC for review and approval.
50% of Functional Test Case are automated.
(3) FUNCTIONAL TEST CASES -
Functional Test Cases are defined & documented
M2/M3 CHECKLIST: Release Planning (legacy)
(CONTINUOUS) - DOCUMENTATION - Documentation (Read the Docs) - M1 - M4
|CONFERENCES & DEMOS||All in 5G U/C|
ORAN/ONAP Plugfest held Thurs Dec 5, 2019 (AM EDT UTC-4 USA) at Rutgers WIN Lab (Brunswick NJ).
Official WIKI Site: https://wiki.o-ran-sc.org/x/egBv
RECORDING OF DEMOS PLUGFEST
April 22-24 Open Network & Edge Summit (ONES) - Los Angeles - GuiLin R7 (Planning).
Early June DDF - (GuiLin R7)
|Release 7 Guilin Requirements|
Requirement SubCommittee: Requirements subcommittee
R7 requirements page: Guilin release - functional requirements proposed list
RunTime Config DB
Architecture S/C presentation for Run Time DB.
Team is working to define the Proposal (see wiki).
Then it will be presented at the Arch S/C and then TSC.
Sync with Sandeep - will meet with Sandeep Fri 7 2020. Ted Johnson. Existing interface.
CMNotify - The DCAE, CMNotify VES event (proper) are pushed to R7
Feb 3-7 Nokia has confirmed that Step 2/3/4 is in R7 due to VES review.
Meeting setup with Sandeep - R7 planning. Need to make a presentation for Alla's call: ONAP Use Case / Requirements Teams Process Way of Working (WoW)
Automation tool integration. Schema details.
|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.
Presentation/slides at: NETWORK SLICING PoC in R6 Frankfurt (Obsolete)
- Development is proceeding. Start R7 release in next couple of weeks. Next week there will be presentation on requirements for R7.
R4 in 3GPP 28.541 - implemented as part properties of a service. didn't create separate TOSCA type for sliceprofile. Plan to introduce new serivce for serivce & slice profile properties in 3GPP those are recent doc updated in january. introduced many new properties from GSP. You've modeling team presentations were made, platform updated w/ network slicing.
|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.
CM Notify as a new domain has been accepted on the DCAE S/C today Oct 24 2019.
Dongho Kim will be creating the test/integration page.
- A1 & O1 test integration pages have been added & links. DongHo Kim leading the Integration
Sandeep code was merged w/ SDN-C branch. Current container has the latest code. Continuing to test. In AT&T lab now being tested
|OOF SON PCI||N.K. Shankaranarayanan|
From SDN-R when we send config change align to NetConf Yang model avail. whatever yang model used, want config DB schema to be aligned w/ yang model to keep model driven. wanted Yang Models from ORAN if possible. In license catch-22. Some yang models for RAN on ORAN website due to licensing issues from Martin Skorupski took 3GPP model converted to files to compile. Issue w/ ORAN getting ok from 3GPP that it is a valid rep of 3GPP model. Option (1) use previous yang model, or (2) switch to ORAN model if available immediately. yang to SQL schema. Only need some parts of the model for SON project. Currently MariaDB continue to use. Piotr, Marek, et al. If there are useful file wo/ IPR issues, should be a way to use interim files.
|WoW w/ Model & Arch|
Way of Working between Architecture , Modeling Subcommittee & Use Case Teams and what happens and touch-points at M0/M1/M2/M3.
Process for Modeling WoW and development with Architecture & Modeling.
|Use Case Template|
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.
Proposed Functional Template for Use Cases (driven from MEF/TM Forum) - showing interactions & information flows.
Filling out, describing and creating the Wiki for a Use Case
Ben talked w/ Andy Mayer U/CR call Oct 23. He said he is preparing the page, and would present here at the 5G U/C S/C call.
REQUIREMENTS SUBCOMMITTEE - requirements sub-group / not bring use cases any more, refer to them as requirements. / proposed change talk less about architecture in requirements mtgs & reviews. more clear split between req & arch discussion. / Alla Goldberg changed U/C S/C to Requirements S/C. Security and ctl loop req will be discussed in those S/C; other things should go to Req S/C.
Monday - - what input for Req review; should not go into realization aspects should be moved out of req review. What type of info & how much info at M0. when just reviewing proposed req. Andy has said Proposed Functional Template for Use Cases this is ready to go live.
|, PM Dictionary, 5G NRM|
5G U/C teams
Chaker Al-Hakim - History Inventory resources associated w/ xNF. Assumptions: what are the resources that I need to inventory about a xNF so that I have a complete view of the VNF. parms added due to nature of VNF. resource inventory didn't have to do with provisioning data that the xNF can have. Should be evolved to reflect what we know today.
PNF Pre-onboarding/ onboarding
PNF U/C teams
PNF / SW Upgrade
|Zu Qiang (Ericsson)|
Reviewed with SO team.
Preparing for DDF. will discuss with Change Management team, might be presenting. R6 in progress.
5G/ Bulk PM
|PNF / NetConf||Oskar Malm||Basic U/C unchanged, support for NetConf over TLS. What is being worked on in R6 is to have a improved functionality around certificate handling. When you have a TLS 1.x for authentication for ONAP so the NF when it connects to ONAP it is a valid xNF. Authenticate user cert ONAP needs to get the certs from somewhere - a centralized solution w/ AAF. and connect to ext. PKI via CMPv2. ONAP component minimum version TLS 1.2. Dependency to REQ-140|
|PNF / Plug and Play||Benjamin Cheung|
held meeting for discussing Civic Address elements & Geolocation information w/ the modeling S/C
Eventually will the PNFregistration VES event for PnP (R7).
SO presentations related to Building block definitions. Dependency to REQ-140. Option #2 new arch. is agreed. Option #1 continue w/ old.
|R6 Use Case VS Requirements||All in 5G U/C|
TSC Release Page.
WHAT IS A USE CASE VS A REQUIREMENT? 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 Service Modeling U/C||Benjamin Cheung|
CDS Data dictionary - Define attribute, in that entry tells you how to get that value. Yuriy Malakov
If you needed the IP@ you can go that entry → points to the REST call. Used for instantiation and configuration management. Model driven ONAP. Modeling Concepts
3GPP TS28.541/TS28.540 - 5G NRM Network Resource Model analysis (spreadsheet). Looking parameters introduce
Classify parameters - CDS Data Dictionary, A&AI, RunTime Cfg DB.
Presentations - Modeling S/C, U/C S/C, U/C Realization, 5G U/C.
Modeling S/C - Experimental info model introduced (standards driven)
A&AI - classification of A&AI parameters. Commission (might need at installation & commissioning) → A&AI.
Onboarding - Onboarding, PNF PNFregistration, CMNotify (VES events), Pre-defined "load 3GPP model"
Information Flows - Where these might be used.
ORAN Standards - Usage of the 3GPP TS28.541 in ORAN Standards. Might want to consider which 3GPP parameters ORAN cares about & when. They might an opinion of when to incorporate parameters.
Presentation at Use Case Realization call
Use Case Realization Call: January 29, 2020 - next step to present to Modeling S/C.
|CMPv2 Security (AAF enhancements)|
|MP4 (Video + Audio)|