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
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 |
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 |