...
| Table of Contents |
|---|
USE CASE KEY INFORMATION
| USE CASE | LEAD CONTACTS / DESCRIPTION | WIKI | ||||||||||
| E2E Network Slicing | 8139896516414821 | |||||||||||
| Integration Leads | ||||||||||||
| Requirement ID | Jira for the requirement |
| ||||||||||
| Architecture Sub-committee Jira tracker | Architecture sub-committee presentation |
| ||||||||||
| Prior projects wiki link | Frankfurt Release | E2E Network Slicing Use Case in R6 Frankfurt |
...
Requirement | |||||||||||||||||||||||
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||||||||||||||
| A&AI |
| ||||||||||||||||||||||
| AAF | No impact foreseen | ||||||||||||||||||||||
| APPC | No impact foreseen | ||||||||||||||||||||||
| CLAMP | No impact foreseen | ||||||||||||||||||||||
| CC-SDK |
| CDS impacts related to initial configuration of Core NSSI NFs, reconfiguration during Core NSSI reuse as well as due to Closed Loop actions. Potential impacts for RAN Slicing. | |||||||||||||||||||||
| DCAE |
| Impacts for (a) KPI Monitoring (b) Closed Loop Control (c) Intelligent Slicing | |||||||||||||||||||||
| DMaaP | No impact foreseen | ||||||||||||||||||||||
| External API |
| Impacts for Service Activation/Deactivation and Termination based on TMF 641 | |||||||||||||||||||||
| Integration | |||||||||||||||||||||||
| MODELING |
| ||||||||||||||||||||||
Multi-VIM / Cloud | No impact foreseen | ||||||||||||||||||||||
| OOF |
| Impacts for (a) Improvements in Frankfurt functionality - e.g., callback for NST/NSI selection (b) Slice profile generation (c) RAN/Core/Transport Slice NSSI selection | |||||||||||||||||||||
| POLICY |
| Control Loop enhancements | |||||||||||||||||||||
| PORTAL | No impact foreseen | ||||||||||||||||||||||
| SDN-C |
| Initial configuration of RAN NSSI, reconfiguration during NSSI reuse, RAN NSSI termination, Closed Loop actions. | |||||||||||||||||||||
| SDC |
| NSST design (RAN, Core, Transport) | |||||||||||||||||||||
| SO |
| Impacts for (a) CSMF/NSMF improvements (b) NSMF interactions with all 3 NSSMFs - internal and external (c) Core NSSMF (d) RAN NSSMF (e) Transport NSSMF (f) Closed Loop (g) Intelligent Slicing | |||||||||||||||||||||
| VID | No impact foreseen | ||||||||||||||||||||||
| VF-C | No impact foreseen | ||||||||||||||||||||||
| VNFRQTS | No impact foreseen | ||||||||||||||||||||||
| VNF-SDK | No impact foreseen | ||||||||||||||||||||||
| CDS | See CCSDK | See CCSDK impacts | |||||||||||||||||||||
| UUI |
| ||||||||||||||||||||||
| Runtime Config DB | No impact foreseen, as Config DB shall be used in Guilin release. | ||||||||||||||||||||||
List of PTLs:Approved Projects
Use Case Functional Definitions
...
This information is taken from this template: Generic Information Element Template
should be copied in the Parent Page (CNF Modeling Workspace) for each Information Element to be defined.
...
Information Element Name | RAN NSST, TN NSST and Slice Profile T (Service template), Endpoint, ConnectionLink and Transport-sla(Data type) |
| Points of Contact | Information Element Main Contact : guochuyi Borislav Glozman Swaminathan Seetharaman Information Modeling and Data Modeling Contact: guochuyi Zhang Min Schema Definition Contact : guochuyi @Henry Yu |
| Related Use Cases | The E2E Network Slicing Use Case: WIKI: E2E Network Slicing Use Case in R7 Guilin and CCVPN Use Case are related to TN Network Slicing: WIKI: CCVPN-TransportSlicing |
Participating ONAP Components | SDC, OOF, SO, AAI, SDN-C, UUI |
| Related JIRA | The related Modeling JIRA is here: |
Description | The modeling design is to enable RAN NSSMF and TN NSSMF internal or external ONAP, and 3 sub-domains combination. |
Related Standards & Industry Activities | Related Standards : 3GPP TS 28.530, TS 28.531, TS 28.541 IETF Related Industry : ORAN |
Attributes | Attributes: Name and describe each attribute of this Information Element. Please include the datatype of the attribute if possible. Is this attribute read-only, read-write? Are there any default values? |
Relationships | Relationships: Describe how this Information Element is related to other Information Elements. Also describe nature of the relationship: association, inheritance, dependency, etc. and multiplicity. |
Originator | Where does this information come from? (What component initially creates it) |
| Consumers | Who uses this information inside & outside of ONAP? How do they use it? Includes description of information consumed (whole class, specific attributes, etc.) |
Producers | Who updates this information inside & outside of ONAP? Under what conditions do they update it? Includes description of information produced (whole class, specific attributes, etc.) |
Steward | Where will this information stored and maintained in ONAP? |
| Impacted APIs & Schemas | Identify impacted ONAP schemas & APIs Are there existing schemas be used or extended? |
Information Modeling Status | What is the status of ONAP Information Modeling activities associated with this Information Element. Please provide links to relevant wiki pages & JIRA. |
Schema Definition Status | What is the status of ONAP Schema Definition activities associated with this Information Element. Please provide links to relevant wiki pages & JIRA. |
ONAP Release Priority | Prioritization for ONAP Releases |
...
| # | Test Case | Status | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Successful design of CST, Service Profile and Slice Profile Templates |
| ||||||||||
| 2 | Successful design of NST, NSSTs (RAN, Core and Transport) |
| ||||||||||
| 3 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets. (Option 1) |
| ||||||||||
| 4 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in a new NSI and new NSSIs to be created for all sub-nets. (Option 2) |
| ||||||||||
| 5 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in existing NSSI to be reused at least for 1 subnet. (Option 1) |
| ||||||||||
| 6 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in existing NSSI to be reused for RAN sub-net and transport subnet (e.g., FH).(Option 2) |
| ||||||||||
| 7 | Service activation from CSMF portal – resulting in slice service activation |
| 8 instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF within ONAP). It should result in existing NSI to be reused (Option 1) |
| ||||||||
| 8 | Service instantiation via CSMF portal which involves RAN, Core and Transport sub-nets (RAN NSSMF outside ONAP). It should result in existing NSI to be reused. (Option 2) |
| ||||||||||
| 9 | Service activation from CSMF portal – resulting in slice service activation |
| ||||||||||
| 10 | Service de-activation from CSMF portal – resulting in slice service deactivation |
| ||||||||||
| 911 | Service termination from CSMF portal (remove service profile/slice profile from NSI/NSSI only) |
| ||||||||||
| 1012 | Service termination (terminate NSI/NSSI also) |
| ||||||||||
| 1113 | Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated (similar to test case 3) |
| ||||||||||
| 1214 | Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI (similar to test case 5) |
| ||||||||||
| 1315 | Service activation request via ExtAPI (using postman) - resulting in slice service activation |
| ||||||||||
| 1416 | Service de-activation via ExtAPI (using postman) - resulting in slice service deactivation |
| ||||||||||
| 1517 | Service termination via ExtAPI (using postman) - (remove service profile/slice profile from NSI/NSSI only) |
| ||||||||||
| 1618 | KPI Monitoring request to be sent from UUI |
| ||||||||||
| 1719 | KPI Monitoring response to be displayed on UUI |
| ||||||||||
| 1820 | Simple closed loop for NSI/NSSI resource optimization (RRM Policy update) (stretch goal) |
| ||||||||||
| 1921 | Intelligent Slicing - take actions based on ML recommendations to ensure KPI adherence (Admission Control in RAN) (stretch goal) |
|
...
| Description | File |
|---|---|
Presentations from LFN Virtual DTF on Jun 24, 2020
| All presentations and recordings are available at: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606742 (or) https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297 |
| Presentation to ArchCom on 26 May, 2020 | |
| Joint S/C presentation | RAN and Transport Slicing: Joint Meeting Apr 30, 2020 |
| Presentation on Use Case Realization Call on 1 Apr, 2020 | https://wikilf-onap.onapatlassian.orgnet/wiki/download/attachments/8140338616417805/ONAP_E2E_Network_Slicing_Usecase_realization_call_20200401.pptx?version=1&modificationDate=1585804290000&api=v2 |
| Presentation to Requirements Sub-Committee on 2 Mar, 2020 |
...