...
R7 May 2020 through December 2020
Parent Page: R7 PNF Plug and Play PnP and R7 5G Service Modeling
Previous Meetings: PNF PLUG and PLAY in R6 Frankfurt
Goals
- Discuss PNFD/SDC AID/A&AI Schema Mapping - Action Items and Geolocation
- 5G Service Modeling
...
| TOPIC | DISCUSSION |
|---|---|
| PNFD MAPPING | PNFD and ending up in an instance data (A&AI Model mapping) From PNFD (onboarded) loaded into SDC AID to A&AI Improvement of ingestion onto SDC AID PNF ETSI NFV SOL001 - descriptor_id, function_description, provider, version, descriptor_invariant_id, name, geographical_location_info, virtual_link SDC - invariantUUID, uui, customizationUUID, version, type, name, description, resourceVendor, resourceVendorRelease, resourceVendorModelNumber, category, subcategory, nf_function, nf_role, nf_type, software_versions ACTION: Go to SDC and/or CDS. Identify Use Case. Will specification for geolocation in SOL001. Geolocation in PNFD not per site. Inventory information. For vendor may not be so useful as sites instances are tied to locations not so much descriptors; for service provider probably country or region may be useful. Onboarding in ETSI. SDC → Vendor PNFD → SDC Model |
TOPIC #4
| TOPIC | DISCUSSION |
|---|---|
| 5G Service Model Use Case | The 5G service model use case in R6 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt is analyzing the incorporation of 3GPP TS28.540, 3GPP TS28.541 (the 5G NRM) ~100 parameters driven from the standards that might be incorporated into the ONAP databases incl. A&AI and Runtime Config DB. Parameters related to inventory & commissioning would go to A&AI and schema updates. Others (run-time) would go into the runTime DB. in R6 we expect only modeling analysis, in R7 look and see which parameters might actually be used. Onboarding - and schema definition for RunTime Cfg DB could be either (a) artifact loaded from vendors and (b) pre-defined driven from standards. Arch. Flows that are used: SDC artifact distribution, RunTime Cfg DB flows. Presentations: Modeling S/C calls, U/C realization call, 5G U/C call. ETSI Thinh / Model coordinated / Information Modeling need & use case |
LOGISTICS
5G resources for 5G BTS (DU, PNF) to introduce an object in Resource Model Right now stored in controller's database. R6 CCSDK / R7 C&PS - pulled out as separate repository. would model. model concepts of NE, EP, to scaffolding. Modeling team with ideas. Propose as R7 future requirement. Providing logical model. Network slicing. NEXT STEP: Modeling discuss with Modeling S/C. What do we need to store; information model for C&PS. path to follow to get to info needed which guides API development & schema formation. Storing information relates to Netconf yang model ; common constructs topo endpoint that you would hang w/ more detailed implementation specific resource information; extend it for any resource; common constructs. ONF. R7 mature a model to evolve. Introduce modeling requirement |
LOGISTICS
| TOPIC | DISCUSSION |
|---|---|
| TIMETABLE (WHAT RELEASE TO INTRODUCE) | Investigate when these would be really necessary. Are they needed in R6? Our discussion today (educated guess) is that they will be needed probably a release or two AFTER an actual, real physical DU is integrated with ONAP. No code changes being requested in R6; but will likely need S/W changes in R7. ACTION: R6: OUTPUT in R6 - Need to document what S/W and U/C (PnP) impacts that there will be. Schema impacts, API changes, and consumers of the API impacts. |
| NEXT MEETING | Meeting on the FIRST Thursday of Each Month ONAP Meeting 4 is inviting you to a scheduled Zoom meeting. Meeting ID: 112 318 171 |
| R7 Model Release Planning | ONAP R7 Modeling High Level Requirements Modeling Activity & Use Case Relevance |
...
| DATE | Attendees |
|---|---|
| |
RECORDING
| Date | Zoom Recording | Audio File |
|---|---|---|
| ||
x | ||
x |
...