...
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 | Epic Jira for the requirement |
| ||||||||||
SO Story Jira for PnP |
| |||||||||||
Modeling Story jira for PnP |
| |||||||||||
Architecture Sub-committee Jira tracker | Architecture sub-committee presentation |
| ||||||||||
Model Place / Geolocation / AAI Schema Meetings Register | PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion Papyrus model: | |||||||||||
Generic Information Element Definition for Geolocation Model | Generic Information Element Definition for Geolocation Model |
NON FUNCTIONAL REQUIREMENT CONTRIBUTION
COMPONENT | U/C STORY JIRA | NFR JIRA | COMPANY | DESCRIPTION | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SO |
|
| Nokia | Non Functional requirement associated contribution. No technical dependency/ organizational dependency. SO NFR Support: Component of SO/LIBs update to Java v11 | ||||||||||||||||
SO Dashboard | Service Orchestrator Guilin Release M1 |
BUSINESS DRIVER
This section describes Business Drivers needs.
...
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | NO IMPACT | ||
AAF | Jonathan Gathman → x | EPIC #1 (TEST ONLY / Integration) CMPv2 - Enhanced Secure X.509 Certificate support (email from Damian Nowak suggests to remove this dependency - testing will occur with REQ-321) REQ-318 PNF Plug & Play in R7 I think, we need to remove the dependency to AAF for REQ-318. REQ-318 covers mainly work in the SO component. Looking at PNF PNP feature E2E we might have some relation to REQ-321, but no strict dependency. Perhaps some AAF dependency was mentioned in REQ-318, before REQ-321 was created. I`d remove the AAF dependency from REQ-318 actually. | |
APPC | NO IMPACT | ||
CLAMP | NO IMPACT | ||
CC-SDK | NO IMPACT | ||
DCAE | NO IMPACT | ||
DMaaP | NO IMPACT | ||
External API | NO IMPACT | ||
MODELING | NO IMPACT | ||
Multi-VIM / Cloud | NO IMPACT | ||
MUSIC | Bharath Balasubramanian → (Empty) | NO IMPACT | |
OOF | NO IMPACT | ||
POLICY | NO IMPACT | ||
PORTAL | NO IMPACT | ||
SDN-C | EPIC #3 Licensing Management flow w.r.t. PnP (q.v. Licensing Management Use Case) (Dependency) Enhancements for requesting License Key File (LKF) & Licenses from License Service (message exchange) | ||
SDC | NO IMPACT | ||
SO | EPIC #2 Workflow to Building Block Development and integration BB execution Framework, extended to understand PNFs. Preparing input object used for different BBs. Framework needs to take into PNFs. (Possible debug/work) (Testing & Integration Work). Environment where this is run Model parameters added, address the right CDS Blueprint. | ||
VID | NO IMPACT | ||
VF-C | → Yuanhong Deng | NO IMPACT | |
VNFRQTS | NO IMPACT | ||
VNF-SDK | NO IMPACT | ||
CDS | NO IMPACT |
...
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
USE CASE FUNCTIONAL DEFINITIONS
Use Case Title | PNF Plug and Play - SO Building Block (Work flow) | ||
Actors (and System Components) | PNF (5G DU) ONAP DCAE-VES Event Listener / PRH: PNF Registration Handler | ||
Description | PNF Plug and Play is used for installation and commissioning when a PNF registers with ONAP | ||
Points of Contact | |||
Preconditions | Design time activities have occurred, and Stage 1 of the Plug and Play Base Use Cases documented here: 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 CaseThis is used during Installation & Commissioning for Plug and Play when SO needs to initiate the Building Block flow for PnP | ||
Steps / Flows (success) | The flows are documented here: 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 CaseIncludes description of Information Producedpost-conditions are after the flows are after the ConfigDeployPNF. The workflow has been completed and executed in SO | ||
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 | ||
Errors can occur while executing the AssignPNF BB, Waiting for PNF ready BB, Config Assign PNF BB or Config Deploy PNF BB. If the Waitfor PNF ready BB waiting for the PNF ready event never arrives because the PNF does not send the PNFRegistration event. (the full details of the flows are in this wiki: 5G - PNF Plug and Play | |||
Related Use Cases | None | ||
Assumptions | None | Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | References are listed in the base wiki: 5G - PNF Plug and Play |
INFORMATION MODEL TEMPLATE
The modeling information for Geolocation can be found here:
Generic Information Element Definition for Geolocation Model
SUPPORTING FILES
Topic | File | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Place / Geolocation Parameters & Analysis View file | | height | 250 | | |||||||||
ETSI SOL001 proposal - Geolocation Update |
| ||||||||||||
PLACE Proposal (Updated Aug 6 2020) |
| ||||||||||||
TESTING
Current Status
...