...
Ctgry | Item | Who | Notes |
Meeting Notes Discussion |
| ||
Use Cases | USE CASE/5G: RAN (ORAN-3GPP) Standards Harmonization with ONAP |
Use Case WIKI: MOBILITY STANDARDS HARMONIZATION WITH ONAP | |
Use Cases | USE CASE/5G: OOF / SON / PCI | PoC for December 2019? SDN-R south-bound NetConf I/F w/ model and also integration with Runtime DB work. | |
Use Cases | USE CASES/5G: PNF S/W Upgrade | R7 Support xNF Software Upgrade in association to schema updates | |
Use Cases | USE CASES/5G: Preonboarding/Onboarding | R7 PNF Pre-onboarding / (onboarding) VNF-SDK Artifact package security | |
Use Cases | USE CASES: Modeling gNB/5G RAN | Align & harmonize information models to ONAP model and ONAP internal information & data model: ETSI SOL001 ... 007 with ONAP internal Model, PNFD modeling (Model S/C), 5G Model (3GPP, RAN), ORAN (WGs, RAN), Open ROADM (reconfig optical add/drop multiplexer, Optical), ONF (Optical), ISOMII (Optical), OTCC (Optical transport config & control) | |
Use Cases | USE CASES: 5G NRM (Network Resource Model) Configuration | wangyaoguang | June 2019 LFN DDF, titled as '5G Provisioning management service to NRM' Presentation: 5G Network Resource Model (NRM) Configuration in R6 Frankfurt |
Use Cases | USE CASES: PNF / Plug and Play | Benjamin Cheung | PNF Plug and Play |
TSC | TSC/USE CASES: Test Automation Progress | Use Case Test Automation Action Items: Use case subcommittee to provide current percentage of testing automation regarding your use case and functional requirements | |
Release Tracking | R7 Frankfurt | All Team Members | Need the U/C teams to fill out the Dev. Impacts. More Generalized Use Case Template (discussed w/ Model team): |
Demos Plug- fest | Demo Plugfest | POC & Plugfest in September 2020 WINLAB? A1/O1 ORAN & ONAP Joint Plugfest Panel Discussion - Setup. Bronze Release. / Slicing, Heart Beat-Health Check | |
Architecture Topics | Architecture Topics | All Team Members | Architecture Component Descriptions and Architecture Flows: https://safratech.net/onapdocs/ |
Use Cases | Read the Docs | All members | DOCUMENTATION - Documentation (Read the Docs) - M1 - M4
"Are you referring to MS1 and the preliminary documentation? https://wiki.onap.org/display/DW/Frankfurt+Documentation Multiple Repo / Use Cases are under Integration Repo VNFREQ has Repo / Verified U/C in Integration Repo Andreas Geissler - Discussed should put docs on the readthedocs (not in wiki) should have own Repo for Use Cases or Req sub-committee own repo |
Use Cases | Req / Use Case Way of Working Process (WoW) | All members | ONAP Use Case / Requirements Teams Process Way of Working (WoW) |
...
USE CASE REQUIREMENTS | DESCRIPTION & DISCUSSION | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OOF SON PCI USE CASE | WIKI PAGE: R7 OOF SON Use Case JIRA: IMPACT: Swaminathan Seetharaman Sandeep Shah
#1 These capabilities exist, migrate to new Yang models. #2 C&PS has configDB deployed. Monitor progress of C&PS and align. #3 VES specs are not finalized. using mechanism for OOF U/C. VES7.2 approved. Link. stndDefined (domain); namespace = 3GPP-configuration. VEs generators, SIM to generate test data in VES format. using Postman to invoke VES message. ACTION: send Sandeep the VES7.2 doc. Extensions to CCSDK/SDN-C C&PS ("ConfigDB") solution to support E2E Network Slicing. | E2E Network Slicing |
| |||||||||||||||||
E2E Network Slicing | WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin JIRA: IMPACT: Key contact: Swaminathan Seetharaman Sandeep Shah guochuyi NSSMF functionality for RAN & Transport CLC functionality Similar to work with OOF/SON - E2ENS RAN slice to be able to create the slice, and config via DMaAP invoke DGs. Netconf comm server in RTRIC. RPC & Yang models fogmount cnfg models. 3GPP-ORAN models - hand-crafting models. flexibility on the yang models, need to be defined. other use case team discussions happening. Java code, CCSDK SLI adaptor might be a good approach to invoke from DG. fx | |||||||||||||||||||
A1 Policy Adaptor ORAN/ONAP/3GPP Harmonization | WIKI PAGE: ONAP/3GPP & ORAN Alignment: A1 Adapter extensions JIRA: IMPACT: Key Contact Michela Bevilacqua John Keeney Deepak Majjiga Question are we leveraging ONAP policy framework for A1 policies? or are there other layers in between? A1 Adaptor from NRt RIC from ONAP DCAE . SMO as ONAP or other. What is the source of A1 policies? ANS: some application sitting above ctrlr ask ctrlr to fwd over A1 I/F in R7 introduce A1 policy mgmt svc to coordinate A1 policies in RAN and keep a synced view of policies handle multiple versions of A1 I/F. Intructions to generate policies need an app - "RApp" executes in ONAP env. generate requests for A1 policies. coming from ctrl loop app (CLAMP, DCAE mS). Controllers NBI to create policies. The policy component in DCAE. OSC A1 policy mgr, ONAP policy framework. ONAP policy framework - no overlap in policies & A1 I/F policies. A1 policies cfgs sent over A1 I/F to RAN. Does the "RApp" exist? ANS: still being defined in WG2. try to define. in ONAP ~ctrl loop (CLAMP). DCAEMod. Q: a challenge - coordinate two open source communities ONAP & ORAN. setup a separate repo for ORAN work to track release w/ ORAN releases. different repo in Gerrit. to make a separate release build. coordinate OSC as a downstream project entire SMO project building on ONAP - A1 control function other coordination for O1 "traditional OAM" / O2 "virtual I/F mgmt I/Fs. data coordination ML model mgmt" wi SDNC CCSDK. eventually C&PS A&AI. RApps. Studying running in ORAN to see results in coming months (R7). basis in Sandeeps work. | MDONS |
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
IMPACT: Xin Miao (Unlicensed)
ONAP/3GPP & O-RAN Alignment:
Standards Defined Notifications over VES
WIKI PAGE: ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES
JIRA:
REQ Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key
347MODELING- 370
IMPACT:
Key Contact Henry Yu / Lin Meng Hesam Rahimi
Presented at SDN-C. Question - creating a new CCSDK SLI adaptor. is this needed?
Do as much as possible w/ DGs. may need Java using CCSDK SLI adaptor/plugin, trouble compiling , need help.
(will resend email)
Question #2. The way I compile for a test/dev env w/ docker compose. building docker images containers in VM
or do we need helm charts? what's the best way to use helm charts? can't bring SDNC w/ A&AI. you can bring up your own env, but it isn't always easy to figure out the dependencies. can run A&AI separately send API responses from A&AI; SDN-C docker. MariaDB galera. Elastic search. but still SDNC doesn't run. Is there a wiki page to help? Dan will post the override file in the wiki.
View file name Transport Slicing Impact on SDNC.PPTX height 250
WIKI PAGE: Guilin release - functional requirements proposed list#SupportforContainerizedNetworkFunctionorchestrationthroughONAPserviceorchestrator- Marge Hillis
The Generic Information Modeling Template:
ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES#INFORMATIONMODELDETAILS
WIKI PAGE: xx
JIRA: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-341
IMPACT: Key Contacts Seshu Kumar Mudiganti Lukasz Rajewski Srinivasa Addepalli
https://wiki.lfnetworking.org/display/LN/2020+June+Virtual+Recordings
Configuration &
Persistency Service
WIKI PAGE: Configuration & Persistency Service R7
JIRA:
REQ Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key
322MODELING- 382
IMPACT: CC-SDK & SDN-C code extended for C&PS.
C&PS PoC based on CC-SDK/SDN-C repo
Key Contacts: Benjamin Cheung Tony Finnerty & Toine Siebelink
Extensions to CCSDK/SDN-C C&PS ("ConfigDB") solution to support E2E Network Slicing.
SDN-C shall get standards-defined StndDefined (CM) VES Event notification from DMaaP when VES collector posts the CM event to DMaaP (Test only)
SDN-C shall get configuration and Yang model from the network device via Netconf and O1 interface. Schema change
SDN-C shall update C&PS DB with configuration data change via an existing REST interface
WIKI PAGE: 5G Network Resource Model (NRM) Configuration in R7 R7 5G Service Modeling
JIRA:
REQ Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key
387MODELING- 369
IMPACT: Key Contact wangyaoguang Benjamin Cheung
The Generic Information Modeling Template: R7 5G Service Modeling#GENERICINFORMATIONMODELFOR5GSERVICE
Q: U/C & Non-functional Req. U/C help out on NFRs. U/C owner should contribute to some NFRs for components they are working on (TSC guidance). Need resources for "must have" DCAE NFRs. should allocate some space/work to help out.
...