5G RAN Service Modeling & Definition in
...
R5 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 |
...
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | | Epic#1: Defining a 5G Service with associated xNFs | E1a. Potential A&AI schema update? |
| AAF | | No Impact |
|
| APPC | | No Impact |
|
| CLAMP | | No Impact |
|
| CC-SDK | | No Impact |
|
| DCAE | | No Impact |
|
| DMaaP | | No Impact |
|
| External API | | No Impact |
|
| MODELING | | Epic#1: Defining a 5G Service with associated xNFs | E1a. Modeling for 5G Service |
Multi-VIM / Cloud | | No Impact |
|
| OOF | | No Impact |
|
| POLICY | | |
|
| PORTAL | | No Impact |
|
| SDN-C | | No Impact |
|
| SDC | | Epic#1: Defining a 5G Service with associated xNFs | E1a. Modeling & Alignment POB/OB. |
| SO | | No Impact |
|
| VID | ittay | No Impact |
|
| VNFRQTS | | No Impact |
|
| VNF-SDK | | No Impact |
|
| CDS | | No Impact |
|
List of PTLs:All Approved Projects
5G Overview
Image Removed
Image Added
5G RAN Network
Image Removed
Image Added
- Infrastructure orchestration - Core, Transport
- 5G RAN components/resources
5G DEFINING Service
Image Removed
Image Added
gNodeB
Image Removed
Image Added
PRESENTATIONS
| Documents | File |
|---|
| 5G Service Modeling | | View file |
|---|
| name | R6-5GServiceCreation.pdf |
|---|
| height | 250 |
|---|
|
|
|
|
...
| Description | File |
|---|
3GPP TS28.540 / TS28.541 5G NRM (From 3GPP standards) | | View file |
|---|
| name | 3GPPTS28541_01Jn022020.xlsx |
|---|
| height | 250 |
|---|
|
|
3GPP TS28.540 / TS28.541 5G NRM (from 3GPP standards) Version Mar 2, 2020 | | View file |
|---|
| name | 3GPPTS28541_01Jn022020.xlsx |
|---|
| height | 250 |
|---|
|
|
| 3GPP TS28.541 | | View file |
|---|
| name | 28541-f40.doc |
|---|
| height | 250 |
|---|
|
|
|
|
...
| Meeting Date | Recording | Description |
|---|
| 8 Jan 2020 | | Presentation & Discussion with Modeling Sub-committee on 3GPP TS28.541 analysis (see spreadsheet above) | | 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& |
|
|
|