...
| USE CASE | IMPACTS | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PNF / Preonboarding Onboarding | No Impact. VNF-SDK. | ||||||||||||||||||||
| PNF / Plug and Play | Wiki Page: PNF PLUG and PLAY in R6 Frankfurt Epic #4: Secure PnP (see next row in this table)
Epic #5: Refactor Tests for DCAE-SDK DMaaP-Client
SUMMARY: DCAE Commits | ||||||||||||||||||||
| CMPv2 Development | CMPv2 being developed in REQ-140 which is the common work in AAF There are then 3 other release requirements covering Use Cases that will use it: (1) Netconf U/C to enhancement w/ Certificate management; (2) enhnace Bulk PM, (3) Enhancing PnP & VES Collector Also DCAE platform CMPv2 cert can be requested correctly and delivered to the micro-services. Was discussed last week with Pawel (Nokia).
SUMMARY: Commit by DCAE | ||||||||||||||||||||
| PNF / Software Upgrade | No Impact | ||||||||||||||||||||
| PNF / Configuration with NetConf | will use CMPv2 (see the CMPv2 Development row) No additional DCAE impact. | ||||||||||||||||||||
| 5G / 5G Service Modeling | No Impact. Modeling impact. SUMMARY: No Impact | ||||||||||||||||||||
| 5G / Bulk PM | Wiki Page: 5G Bulk PM in Frankfurt/R6 Epic #1 PM control -
Epic #2 Secure 5G Bulk PM
OPEN QUESTIONS: Is there further discussion for flow/paths for the Use Case itself? update from AAI triggering updates to SO, SH. change to have new mS and rigger policy update to reconfigure the mS follow policy path flow. Talk, but need follow-ups. AAI I/F vs direct I/F adding new OTI component for R6. Still nee dto close on some open points. (Spreadsheet/Use Case Team): Indicates impact SUMMARY: Will nee some further discussion, need some updated flows and better understanding on the flows. Discussion with Oskar & Michela. | ||||||||||||||||||||
| 5G / PM Dictionary | Wiki Page: FM META DATA & PM DICTIONARY in R6 Frankfurt
DCAEGEN2-1767 Epic
DCAEGEN2-1768 Story Epic: Update PM Dictionary Schema to have one YAML document per measurement. All measurement YAML documents will be in the same PM Dictionary YAML file. Story: VES Event Registration Spec updates to section 3.3 for PM Dictionary schema change. No DCAE Impact. Marge Agrees. New Artifact & definition. SUMMARY: Needs more discussion with Marge. May need to be update, Marge will sync Vijay & Damian. | ||||||||||||||||||||
| 5G / 5G FM Meta Data | No Impact | ||||||||||||||||||||
| 5G / OOF SON (PCI) | Wiki Page: OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt Epic#1 - OOF/SON Enhancements Functionality enhancement to SON Handler MS Will also USE the CM Notify (being introduced in VES update) (Spreadsheet/Use Case Team): Indicates impact SUMMARY: Needs Clarification | ||||||||||||||||||||
| 5G / E2E Network Slicing | Wiki Page: NETWORK SLICING PoC in R6 Frankfurt (Obsolete) No Impact (none listed in Wiki) SUMMARY: (No impact?) | ||||||||||||||||||||
5G / RAN ORAN 3GPP Standards Harmonization | Wiki Page: MOBILITY STANDARDS HARMONIZATION WITH ONAP Might have to delay. Enhancements expected from DCAE (1) CM NOTIFICATION: Listen to CM notification (config change notification). (2) 3GPP FAULT EVENT: how to support 3GPP fault. 3GPP fault as a separate domain; alignment with 3GPP. (3) FILE READY - VES event, add a field for the type of file. Sub: data field collector. Can use existing fields to support this. Applicable to other types of file beyond the PM file (e.g. trace, log files) want it to be generic. (Spreadsheet/Use Case Team): Indicates impact Timeline - meeting held Oct 2 to align 3GPP fault event, converging on an approach; another meeting next week Oct 7+. Maybe difficult to achieve by M2/M3 (Nov 7 2019) SUMMARY: (see CM Notify VES event) | ||||||||||||||||||||
| CM notify new VES event. | CM notications are new impacting VES event registration & listener. VES publications happen before components use it. VES updates need to happen before development. VES event reg & listener, FM dictionary. Modeling updates by M2. A finalized VES document might be difficult by Nov 7 IMPACTS: ORAN/ONAP Harmonization U/C, OOF/SON/PCI Use Case, and RunTime DB Use Case. SUMMARY: DCAE commits, but wants to follow-through on the definition of the VES definitions. WARNING: M2/M3 deadline for M2/M3 Nov 7 2019. Collector change to accommodate VES | ||||||||||||||||||||
| 5G / Runtime DB | Wiki Page: 5G CONFIGURATION (RunTime DB) CONFIGURATION PERSISTENCE SERVICE R6 Epic #1: Base RunTime DB Development E1a. VES/DCAE pathway to provide configuration notification RunTime DB (see also the ORAN/ONAP harmonization U/C ROW ABOVE - CM O1 Notification). DCAE collectors needs a new domain for CM Notify. No additional impact expected to USE the CM Notify. RunTime DB SUBSCRIBES to the CM Notify Event. E1b. VES Event Listener Document to be updated. E1c. New VES Event domain (CM Notify) to be introduced (DCAE VES Listener) (Direct invoke API).
SUMMARY: (impact captured in the CM notify VES impact) | ||||||||||||||||||||
| 5G / NRM CM w/ RESTful HTTPS | No Impact ? | ||||||||||||||||||||
| 5G / Licensing Management | No Impact. Modeling & architecture work for R6. | ||||||||||||||||||||
| SERVICE RESOLVER | No Impact?? (Wiki lists nothing) ?? | ||||||||||||||||||||
| SCALING | Wiki Page: Scaling Use Case (Frankfurt) Goal: Manual and Automatic Scale In Scale In Trigger (Priority: 2) Support creating a Threshold Alert (TA) when capacity needs to be reduced Send the TA to Policy No new functionality for scaling expected. SUMMARY: Needs Investigation. | ||||||||||||||||||||
| Mobile Service Chaining & Service Selection | Wiki Page: MOBILE SERVICE CHAINING We want close loop mechanism for service chaining operation SUMMARY: Need Investigation. | ||||||||||||||||||||
| BBS | Wiki / PPT slide indicates no impact (Spreadsheet/Use Case Team): Indicates impact SUMMARY: No impact | ||||||||||||||||||||
| CCVPN | Wiki Page: CCVPN Use Case in Frankfurt Release (Spreadsheet/Use Case Team): Indicates impact SUMMARY: Needs Investigation | ||||||||||||||||||||
| Control Loop | Self Serve Control Loops - continuation from Dublin PNF support in Control Loops - non-service Control Loops Adding Policy Update and PEP (Policy Enforcement Point) registration with Policy for updates on Decision Policies CLAMP would provide arbitrary blueprints to DCAE instead of SDC. CL Event format standardization to VES (Spreadsheet/Use Case Team): Indicates impact SUMMARY: DCAE some things are committed. Separate requirements created. | ||||||||||||||||||||
| Multi Domain Optical Service L0/L1 Orchestration | Wiki Page: Multi-domain Optical Network Services (Spreadsheet/Use Case Team): Indicates impact SUMMARY: Needs Impact assessment. | ||||||||||||||||||||
| CHANGE MANAGEMENT | Wiki Page: Change Management Frankfurt Extensions (Spreadsheet/Use Case Team): No impact listed SUMMARY: No impact. | ||||||||||||||||||||
| HPA | Wiki Page: Continuation of HPA SUMMARY: Needs investigation | ||||||||||||||||||||
| RUN TIME SECURITY | No Impact?? (Wiki lists nothing) | ||||||||||||||||||||
| K8S Based Cloud Region Support | Wiki Page: K8S based Cloud region support (Continue from R4) (Spreadsheet/Use Case Team): SUMMARY: Needs investigation | ||||||||||||||||||||
| DAaaS | (Spreadsheet/Use Case Team): Indicates impact | ||||||||||||||||||||
| 3rd Party Operational Domain Manager | Wiki Page: Third-party Operational Domain Manager SUMMARY: Needs investigation |
...
| Recording | FILE | ||||||
|---|---|---|---|---|---|---|---|
| Zoom Video & Audio (MP4) |
| ||||||
| Audio Only (M4A) |
| ||||||
| Playback (M3U) |
| ||||||
| Chat (Txt) |