...
Section | Description |
|---|---|
Use Case Title | E2E Network Slicing |
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 |
GENERIC INFORMATION MODEL FOR 5G SERVICE
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 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 |
Test Cases and Status
| # | 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. |
| ||||
| 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. |
| ||||
| 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. |
| ||||
| 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). |
| ||||
| 7 | Service activation from CSMF portal – resulting in slice service activation |
| ||||
| 8 | Service de-activation from CSMF portal – resulting in slice service deactivation |
| ||||
| 9 | Service termination from CSMF portal (remove service profile/slice profile from NSI/NSSI only) |
| ||||
| 10 | Service termination (terminate NSI/NSSI also) |
| ||||
| 11 | Service instantiation request via ExtAPI (using postman) - resulting in new NSI to be instantiated (similar to test case 3) |
| ||||
| 12 | Service instantiation request via ExtAPI (using postman) - resulting in reuse of existing NSI (similar to test case 5) |
| ||||
| 13 | Service activation request via ExtAPI (using postman) - resulting in slice service activation |
| ||||
| 14 | Service de-activation via ExtAPI (using postman) - resulting in slice service deactivation |
| ||||
| 15 | Service termination via ExtAPI (using postman) - (remove service profile/slice profile from NSI/NSSI only) |
| ||||
| 16 | KPI Monitoring request to be sent from UUI |
| ||||
| 17 | KPI Monitoring response to be displayed on UUI |
| ||||
| 18 | Simple closed loop for NSI/NSSI resource optimization (RRM Policy update) (stretch goal) |
| ||||
| 19 | Intelligent Slicing - take actions based on ML recommendations to ensure KPI adherence (Admission Control in RAN) (stretch goal) |
|
...