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.
:
"Are you referring to MS1 and the preliminary documentation?
This is mainly relevant to new projects. The link that you provided below covers that, since the 5G use case team is not a new project, your documentation is already published on RTD."
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.
:
(1) ROADMAP - Proceeding with detail, developments for roadmap beyond R6.
(2) API - defining API in progress.
(3) PoC - Prototype of PoC from Orange focusing on VNF-portion.
(4) SO - Implementation in SO W/F and hierarchy using Svc ref concept to be discussed beyond R6.
(5) ORCHESTRATION - documentation what will ONAP do wr.t. slice orchestration
(6) MODELING - Discussing Modeling aspects, how to represent CSI, NSSI, NSSMF etc how to implement in SO how to communicate w/ external domain NSSMF.
- 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.
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
marge.hillis will setup a call to discuss possibly some gaps maybe move things to R7. Meetings w/ Dave Smith et al. trying to push through harmonization. Standards meeting in Nov. 2019. There was push back & negotiation between 3GPP & ONAP as to how to proceed. This is because it was first exercise, once we have a process in place it should go more smoothly. 3GPP specified some stuff and tried to over-specify into ONAP. Shortcoming in 3GPP current CMnotification only handles one MO if this was adopted. Working with 3GPP to correct. Waiting to see if 3GPP will accept the proposal. Working w/ standards for 3GPP FEB SA5 standards meeting.
Harmonization U/C- Some things pushed out (Partial Green) at M2/M3 - O1 enhancements moved to G release hoping to harmonize (1) Fault & (2) Config change Notification (CMNotify) Thus CMNotify will be pushed to R7. Meetings to harmonize 3GPP standards. Waiting for Standards to be Harmonized. Intentionally descope something so that we don't cause churn. Don't want to implement something that would have to be re-implemented. Don't want to implement something that would have to be re-implemented. Trying to get VES SMEs engaged. But won't make R6 because of the timeframe. The VES Specs does need to be updated (see next point). Trying to align ORAN, ONAP & 3GPP aligned.
ONAP 3GPP CONVERGENCE MEETING- - Dave Kinsey didn't agree option that was optimal wanted to discuss option he proposed. Wanted to bring in VES ppl to look at options. David Smith created & leading the meeting. Should invite Oskar Malm, Cormac Mullally, Mark Scott. Looking at options to populate the common header such that events w/ opaque payload can be fwded to correct DMAAP topic. to harmonize ONAP different standard standards defined things.
CMNotify for PoC/Demo - R6, OOF-SON-PCI & the RunTime Config DB U/C needed the CMNotify, Sandeep Shah said they had a simulation of CMNotify for demo purposes.
INTEGRATION- Update from Dongho Kim for A1 interface: (Feb 13 2020) Dongho talked to Sandeep this week (Feb 13), he found a bug, and he is testing it. Was dev. done for A1 I/F? Phase 1 = A1 adapter (testing, bug found). For RTCDB has A1 policy schema. O1 I/F partial (to be completed in R7). May need more full-fledge use case. defining E2E use case.
VES Spec updates- DCAE project next week to discuss how to proceed. Need to make sure it is one w/ the correct content. DRAFT 4. Alok G. is on medical leave, and Albino Pinho / Trevor Lovett is the current delegate. PM schema update needed. Security change. Trevor has sent out a review. CRs are posted. Does not include the Fault & CMNotify (will be in VES 7.2 which is in R7). Gerard Hynes pulling in VES experts. David Kinsey looking at Harmonization options. David Smith (ATT) Jean-Michel Corneley (Orange) to discuss options for Harmonization. Should happen before DCAE call. From Ericsson Oskar Malm has forwarded. Gerrit Review open for VES event listening & VES registration. Pulling these documents into READTHEDOCs: https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter7/index.html . Re-reviewing the deltas from last Red the docs updates. Trevor going over comments. deltas from Dec 10, 2018. CMNotify NOT in version associated with R6. Gerrit Review: https://gerrit.onap.org/r/dashboard/self
Harmonization U/C- Some things pushed out (Partial Green) at M2/M3 - O1 enhancements moved to G release hoping to harmonize (1) Fault & (2) Config change Notification (CMNotify) Thus CMNotify will be pushed to R7. Meetings to harmonize 3GPP standards. Waiting for Standards to be Harmonized. Intentionally descope something so that we don't cause churn. Don't want to implement something that would have to be re-implemented. Don't want to implement something that would have to be re-implemented. Trying to get VES SMEs engaged. But won't make R6 because of the timeframe. The VES Specs does need to be updated (see next point). Trying to align ORAN, ONAP & 3GPP aligned.
ONAP 3GPP CONVERGENCE MEETINGDave Kinsey didn't agree option that was optimal wanted to discuss option he proposed. Wanted to bring in VES ppl to look at options. David Smith created & leading the meeting. Should invite Oskar Malm, Cormac Mullally, Mark Scott. Looking at options to populate the common header such that events w/ opaque payload can be fwded to correct DMAAP topic. to harmonize ONAP different standard standards defined things. Meeting to be held to make more progress.
CMNotify for PoC/Demo - R6, OOF-SON-PCI & the RunTime Config DB U/C needed the CMNotify, Sandeep Shah said they had a simulation of CMNotify for demo purposes.
INTEGRATION- Update from Dongho Kim for A1 interface: (Feb 13 2020) Dongho talked to Sandeep A1 adaptor unit-test bug fixed & tested. No automation yet. Check with Dan Timoney. Testing was done with A1 mediator from A1C repo south-bound, no device compliant to A1 spec, Sandeep used S/W using A1 mediator.
VES Spec updates- DCAE project next week to discuss how to proceed. Need to make sure it is one w/ the correct content. DRAFT 4. Alok G. is on medical leave, and Albino Pinho / Trevor Lovett is the current delegate. PM schema update needed. Security change. Trevor has sent out a review. CRs are posted. Does not include the Fault & CMNotify (will be in VES 7.2 which is in R7). Gerard Hynes pulling in VES experts. David Kinsey looking at Harmonization options. David Smith (ATT) Jean-Michel Corneley (Orange) to discuss options for Harmonization. Should happen before DCAE call. From Ericsson Oskar Malm has forwarded. Gerrit Review open for VES event listening & VES registration. Pulling these documents into READTHEDOCs: https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter7/index.html . Re-reviewing the deltas from last Red the docs updates. Trevor going over comments. deltas from Dec 10, 2018. CMNotify NOT in version associated with R6. Gerrit Review: https://gerrit.onap.org/r/dashboard/self VES spec in the ReadtheDocs, meeting held to discuss issues Monday Feb24 & Wed Feb26. VNF or PNF requirements Documentation > Appendix > Service: VES Event Registration 3.2 ...
ACTION: Marge Hillis - VNF-Requirements. Zu: this is not in the normative text format ("should"=recommended "may"=optional & "shall"=must opening statement of everything in this doc is "mandatory" or not??) some things should move to the VNF-requirements project (many people made comments to that end). Requirements there are there need to follow conventional req language. Reach to Trevor
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.
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.
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.
New Use Case Template: Andy Mayer presented on new additions to Use Case Template: Use Case Tracking Template proposed for R7. If a U/C is extending from a Prior Release should we convert to new Template, or can we maintain. Use cases should to link to new req in the proposals.
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.
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
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. Option #2 new arch. is agreed. Option #1 continue w/ old. Use Case Realization Call: February 19, 2020
Benjamin Cheung Find out if - will we support >1 PNF instance / template per service 5G Service (Run-Time). Plan to test/Integration how to do the instantiation. Use CLI to do instantition, limitation in SO workflow limitation in controller, PRH.
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.
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
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.
REPO Avail - Nokia has created a repo, discussing architecture now.
Access - Confirmed, we can access the Repo.
Deliveries- Nokia planning to deliver the CertService (accept request from client), CertService Client (init container w/ ONAP apps), and integration with external CMP v2 service.
Integration to Border Components - Integration with ONAP modules, DCAE/VES, SDNC, DCAE/DFC very likely to bepost-posted to R7. High Risk The ONAP "bordering" components. Consequences- in scenario where you int ONAP w/ external function won't be able to dist cert generated in external Cert. Authority (CA) within ONAP; thus would still be able to integrate a NF to ONAP but would need to distribute manually bring the certs to ONAP. The Automation of distribution would be missing. The NFs contact the CAs to get certs. Integrate ONAP w/ CMPv2 w/ CertSvc to same Ext. CA. Integrate the xNF gets the cert to Ext. CA. ONAP gets matching trust anchors from same Ext. CA, loaded to an ONAP component. CertSvc bought back dist. within ONAP volume where cert is stored & consumed by ONAP component. 3GPP requires/originated. Consumes maximum of what 3GPP has.
Slides-
Jira Legacy
server
System Jira
serverId
4733707d-2057-3a0f-ae5e-4fd8aff50176
key
ONAPARC-553
Integration- Separate integration efforts. 140 is the common part in AAF, including client component that can be reused, there is integration work which have separate requirements. This creates a dependency on those other requirements, being delivered with enough time to do integration.
Plug and Play, Bulk PM, NetConf - CMPv2 PnP got descoped, secure Bulk PM is descoped, NetConf is proceeding see: Frankfurt Release Requirements
REQ-76 - If we manage to complete the integration into SDN-C (REQ-76) additional integration related to that.
