This page and its sub-pages captures all requirement and implementation details for the E2E Network Slicing use case for Guilin release.
The E2E Network Slicing use case started in Frankfurt. Details of the Frankfurt implementation can be found at E2E Network Slicing Use Case in R6 Frankfurt.
Participants: China Mobile, Wipro, Huawei, AT&T, Amdocs, Verizon, Reliance Jio, Tencent, China Telecom
Use Case Owners and Contacts
LIN MENG menglinyjy@chinamobile.com
Swaminathan Seetharaman swaminathan.seetharaman@wipro.com
Chuanyu Chen chenchuanyu@huawei.com
Shankaranarayanan Puzhavakath Narayanan snarayanan@research.att.com
Borislav Glozman Borislav.Glozman@amdocs.com
Sub-pages
Table of Contents
USE CASE KEY INFORMATION
| USE CASE | LEAD CONTACTS / DESCRIPTION | WIKI |
| PNF Plug and Play | 5G - PNF Plug and Play | |
| Integration Leads | ||
| Requirement ID | Jira for the requirement | REQ-318 - Getting issue details... STATUS |
| SO Story Jira for PnP | SO-2981 - Getting issue details... STATUS | |
| Modeling jira for PnP | MODELING-368 - Getting issue details... STATUS | |
| Architecture Sub-committee Jira tracker | Architecture sub-committee presentation | ONAPARC-575 - Getting issue details... STATUS |
Model Place / Geolocation / AAI Schema Meetings Register | PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion | |
| Generic Information Element Definition for Geolocation Model | Generic Information Element Definition for Geolocation Model |
BUSINESS DRIVER
This section describes Business Drivers needs.
EXECUTIVE SUMMARY - This requirement will augment the work-flow to building block management within SO for Plug and Play operation. The continues the work started in R6. In R6, some of the SO work-flow to building block work was finished, and in R7 this is enhanced. The description of the "base" work which will be enhanced is shown in the wiki: PNF PLUG and PLAY in R6 Frankfurt
BUSINESS IMPACT - The enhancement to Plug and Play operation in ONAP is a critical business function because they enhance installation and commissioning activities.
BUSINESS MARKETS - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage.
FUNDING/FINANCIAL IMPACTS - The plug and play project has Operating Expense (OPEX) savings for operators because of the ability to saving time and expenses during installation and commissioning and contributes towards ZTM (Zero touch management).
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
Requirement | |||
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | No impact foreseen | ||
| APPC | |||
| CLAMP | No impact foreseen | ||
| CC-SDK | |||
| DCAE | |||
| DMaaP | No impact foreseen | ||
| External API | |||
| Integration | |||
| MODELING | |||
Multi-VIM / Cloud | No impact foreseen | ||
| OOF | |||
| POLICY | |||
| PORTAL | No impact foreseen | ||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | No impact foreseen | ||
| VF-C | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS | |||
| UUI | |||
| Runtime Config DB | |||
List of PTLs:Approved Projects
INFORMATION ELEMENT DATA DETAILS
This table is taken from the generic information template: Generic Information Element Template
Information Element Template (one table for each Information Element)
Information Element Name | Name of the Information Element |
| Points of Contact | Authors and maintainers of the Information Element Information Element Main Contact (typically Use Case SME) Information Modeling Contact Schema Definition Contact |
| Related Use Cases | Use Cases that have interactions using this Information Element. Please provide a point of contact for each related Use Case. |
Participating ONAP Components | The list of ONAP Components that are stakeholders for the Information Element |
| Related JIRA | Please provide link to related JIRA item |
Description | Overview and description of the Information Element. |
Related Standards & Industry Activities | Please refer to any standards or industry activities that should be taken into account when defining the Information Model related to this Information Element. Please provide links to relevant material. |
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 |
Use Case Functional Definitions
Section | Description |
|---|---|
Use Case Title | 5G SON |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
Description | Short overview of the Use Case |
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. |
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
Test Cases and Status
| # | Test Case | Status |
|---|---|---|
| 1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
| 2 | create additional requirements as needed for each discreet step | COMPLETE |
| 3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
| 4 | Test Cases should include enough detail for testing team to implement the test | FAILED |
Supporting Files
| Description | File |
|---|---|
| Presentation on Use Case Realization Call on 1 Apr, 2020 | https://wiki.onap.org/download/attachments/81403386/ONAP_E2E_Network_Slicing_Usecase_realization_call_20200401.pptx?version=1&modificationDate=1585804290000&api=v2 |
| Presentation to Requirements Sub-Committee on 2 Mar, 2020 | |
| Presentation from F2F | |
| Joint S/C presentation | RAN and Transport Slicing: Joint Meeting Apr 30, 2020 |
| Presentation to ArchCom on 26 May, 2020 |