5G RAN Service Modeling & Definition in R6 Frankfurt

R5 CANDIDATE ENHANCEMENTS	IMPACT
Modelling	Evolution of Platform Info & Data model in support of 5G Service
SDC	Support for creation of a 5G Service (E2E integration only), Design Time.
Architecture	New Flows for 5G Services

BUSINESS DRIVERS

This section describes Business Drivers for this Use Case.

Executive Summary - This use case is will define a creating a 5G Service to represent a 5G gNB which will be important to attach 5G resources (PNFs/DU, VNFs/CU) such that the infrastructure to deliver a 5G service has been properly instantiated for the Day0/Day1 deployment.

Business Impact - This use case, defining a 5G service (representing a 5G gNB) is vital to underpin defining and modeling a Network Slice. This use case will identify some of the key gaps in defining a 5G service both in design time and run time. The 5G orchestration process needs to be defined. Examples of "what is a 5G Service" (i.e. does it include a RAN, Core, Transport?). Identifying Gaps in SDC and Controllers to orchestrate a 5G service. Bringing the open-source ONAP community and various involved platform components to come together to come to some common understanding and agreements as to what a 5G service should be, and how a 5G service would be orchestrated. ANR, Nested services.

Business Markets - Applies to Wireless domain market. In so much the transport is involved with getting a 5G service orchestrated, transport and optical domains are also important.

Funding/Financial Impacts - TBD.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider..

DEVELOPMENT IMPACTS

PROJECT	PTL	User Story / Epic	Requirement
A&AI	James Forsyth	Epic#1: Defining a 5G Service with associated xNFs	E1a. Potential A&AI schema update?
AAF	Jonathan Gathman	No Impact
APPC	Takamune Cho	No Impact
CLAMP	Gervais-Martial Ngueko	No Impact
CC-SDK	Dan Timoney	No Impact
DCAE	Vijay Kumar	No Impact
DMaaP	Mandar Sawant	No Impact
External API	Matthieu Geerebaert	No Impact
MODELING	Hui Deng	Epic#1: Defining a 5G Service with associated xNFs	E1a. Modeling for 5G Service
Multi-VIM / Cloud	Bin Yang	No Impact
OOF	Shankaranarayanan Puzhavakath Narayanan	No Impact
POLICY	Pamela Dragosh	No Impact
PORTAL	Manoop Talasila	No Impact
SDN-C	Dan Timoney	No Impact
SDC	Ofir Sonsino	Epic#1: Defining a 5G Service with associated xNFs	E1a. Modeling & Alignment POB/OB.
SO	Seshu Kumar Mudiganti	No Impact
VID	ittay	No Impact
VNFRQTS	Steven wright	No Impact
VNF-SDK	victor gao	No Impact
CDS	Yuriy Malakov	No Impact

List of PTLs:Approved Projects

5G Overview

5G RAN Network

Infrastructure orchestration - Core, Transport
5G RAN components/resources

5G DEFINING Service

gNodeB

PRESENTATIONS

Documents	File
5G Service Modeling

Modeling Standards Bodies

The Platform Data & Information model needs to harmonize with models from the following standards bodies or modeling groups.

ETSI SOL001 ... 007

PNFD modeling (Model S/C)

5G Model (3GPP, SA5, 5GNRM)

ORAN (WGs) - NetConf/Yang WG4

Open ROADM (reconfig optical add/drop multiplexer)

ONF (equipment specific conditional package for wireless transport/air interface)

ISOMII

OTCC (Optical transport config & control)

GROUP	DOMAIN	MODELING EFFORTS
ETSI	Wireless	SOL001 PNFD, VNFD Model SOL004 PNF/VNF Package
ORAN	Wireless	WG6 E2E orchestration. CU (CU-CPM CU-UP)/DU/RIC NE. Flat model managed by ONAP. Service model to deploy a RAN at this location.
3GPP	Wireless	CRAN model CU/DU Split
Open ROADM	Optical
ONF	Optical
ISOMII	Optical
OTCC	Optical

SUPPORTING DOCUMENTATION

Description

File

3GPP TS28.540 / TS28.541

5G NRM (From 3GPP standards)

3GPP TS28.541

RECORDINGS & MEETINGS

Meeting Date

Recording

Description

8 Jan 2020

zoom_0.mp4

Presentation & Discussion with Modeling Sub-committee on 3GPP TS28.541 analysis (see spreadsheet above)

29 Jan 2020

Use Case Realization Call: January 29, 2020

Use Case Realization Call

MODELING - Maybe first focus on models classes that A&AI might need. How do those elements get populated & modified. RTCfg will also need details & the architectural approach how they would approach extensibility; representing in swagger API or flexible schema approach.
A&AI - The A&AI will be stopping at level of PNF (CU/DU), the cells underneath associated w/ a DU you can't find in A&AI. That would be stored in RTCfg DB the index would match with the PNF.
NETWORK SLICING - (Swami) building up, intro some classes. in R7 should we introduce all the classes? Q? (Michela) Where were the classes introduced? For R6 modeling the slice as a service using the only the existing constructors & current platform info-model.
ORAN MODELING - The ORAN alignment, w/ their yang info-models. ORAN-ONAP alignment. Contact ORAN SMEs.
RunTime Config DB - Q? (Joanne) The config DB would be focused on SON U/C importing ORAN yang model to be used in the SON/PCI & associated attributes in R6. (Swami) No. The yang models are not officially available from ORAN. In OOF/SON will still use the old yang models. There is work in converting yang to the schema. ORAN yang model itseill be in R7. Alignment taking ORAN alignment; earlier CMNotify notification over Netconf I/F because ORAN decided it will be a VES event, that VES have a draft specification basedon that will generate a VES notification.
RunTime config DB Schema & Extensibility - Q (Andy)? How does RunTime Config DB deal w/ Extensiblity - the YANG model. Schema in R6 is hard-coded; iin the long term the info from vendor provided PNF package could guide the RTCffDB schema (R7). Q (Joanne)? Relation between 5G info model . Attach the 5G Specific aspects for 5G elements (xNFs). Runtime pc the yang model info that would be represented in A&AI. other info only be in RTCfgDB. MODEL the DOMAIN. Config stuff as a "blob" need to parse. A view of what the info model is. Anything dynamic, changeable, or discovering (would not be in A&AI).
OOF/SON PCI - The Parameters already used for the OOF/SON PCI U/C e.g. NetworkID, CellID, PCIValue, nbrList, ... are these in 3GPP TS28.541 (mapping?). Key ideas - OOF/SON/PCI cares about Cells. Model Cells ... how should they be modeled? is that something that should be evolved in the platform model. how Will that evolve. Maybe start w/ SON as a reference or starting point. The requirements are lmited what info we are looking for in Cell.
DOMAIN - RAN (Wireless). the modeling stuff that is introduced will not preclude the ability to support other domains, such routers. EXTENSIBILITY.
MODELING S/C - NEXT STEPS: ... present an abbreviated presentation to Modeling S/C, what would be reused or re-imported from the 3GPP model and how to attach/hang them to base classes. 3GPP has functions functions separated out and attached to the element. ASK who would like to help create the papyrus model as input.
A&AI - NEXT STEPS I've made presentation at the A&AI Team (Weds 9AM EDT USA), they will also be hosting future discussions on parameters flagged as "A&AI" in the spreadsheet.
NOTES - Q (Zu Q.) Add a column for "Notes" justifying if something will be in A&

5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt