...
TOPIC | DESCRIPTION | WIKI PAGE | ||||||||||
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | E2E_Network_Slicing_R9_Requirements_20200329_v1.0.pptx | ||||||||||
Architecture S/C info | Information on the Architecture sub-committee presentation |
Presentation: E2E_Network_Slicing_ArchCom_Review_v1.0.pptx | ||||||||||
Prior Project "Base" Wiki | Link to the Honolulu release page for this use case | |||||||||||
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case |
| ||||||||||
Key Use Case Leads & Contacts | USE CASE LEADS: LIN MENG , Ahila P Saravanan Ayyadurai Ratna Shanker Mishra USE CASE KEY CONTACTS: LIN MENG , Ahila P Saravanan Ayyadurai , Ratna Shanker Mishra , Henry Yu, Milind Jalwadi (Unlicensed) Borislav Glozman | |||||||||||
Meetings Register & Recordings | Link to Use Case Team meetings |
...
PROJECT | PTL | User Story / Epic | Requirement | ||||||||||
A&AI | No impact | ||||||||||||
AAF | No impact | ||||||||||||
APPC | No impact | ||||||||||||
CLAMP | No impact | ||||||||||||
CC-SDK |
| Interface to CPS, RAN configuration & A1 interface | |||||||||||
DCAE |
| Enhancements in Slice Analysis MS, and KPI Computation MS (Stretch goal) | |||||||||||
DMaaP | No impact | ||||||||||||
External API | No impact | ||||||||||||
HOLMES | No impact | ||||||||||||
MODELING | No impact, CPS related modeling aspects will be covered by CPS project | ||||||||||||
Multi-VIM / Cloud | No impact | ||||||||||||
OOF |
| ||||||||||||
OOM | No impact | ||||||||||||
POLICY | No impact | ||||||||||||
PORTAL | No impact | ||||||||||||
SDN-C | No impact | ||||||||||||
SDC | No impact | ||||||||||||
SO |
| Minor enhancements, some major enhancements are stretch goals | |||||||||||
VID | No impact | ||||||||||||
VF-C | No impact | ||||||||||||
VNFRQTS | No impact | ||||||||||||
VNF-SDK | No impact | ||||||||||||
CDS | No impact | ||||||||||||
CPS | Models, and interface to store/retrieve use case related data |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...