...
Contents
Main Concepts in Modeling
| Anchor |
|---|
| Main Concepts in Modeling |
|---|
| Main Concepts in Modeling |
|---|
|
Information Model
- Defines managed objects at a conceptual level, independent of any specific implementations or protocols used to transport the data
- A semantically meaningful representation of concepts (classes of entities) described in an implementation independent manner
- Contains Class characteristics (attributes), Relationships among classes, Operations (actions) performed on classes by actors
- May be represented in Unified Modeling Language (UML), as agreed in ONAP
- Define and establish the methodology, processes, and supporting tools (Papyrus is the agreed tool in ONAP).
Data Model
- Defines managed objects at a lower level of abstraction than Information Model. Data Model includes implementation and may include protocol specific details.
- Formally describes the structure and the semantics of all the data that are (a) stored in data management systems, and/or (b) accessed and manipulated by data-centric applications across APIs.
...
ONAP Modeling Terminology
| Anchor |
|---|
| ONAP Terminology |
|---|
| ONAP Terminology |
|---|
|
A B B C D E F G H I J K L M N O P Q R S T U V W X Y Z
...
A
...
B
...
P
...
Q
...
R
Resource: It defines a set of capabilities that may be consumed by other Resources and/or Service Components.
...
S
Service: A functionality that can be offered to users, different internal and external users, for different purposes. Services may be used by other Services, but not by Resources or Service Component.
Service Component: A functionality that is not offered to external users. A Service component may be used by Services or other Service Components, but not by Resources. The Service Component is used in the ONAP Information Model but not in the Data Model where it has been collapsed with the Service.
...
T
...
U
...
V
virtualisation container: According to ETSI NFV, partition of a compute node that provides an isolated virtualized computation environment
Virtualisation Deployment Unit (VDU): According to ETSI NFV, a construct that can be used in an information model, supporting the description of the deployment and operational behaviour of a subset of a VNF, or the entire VNF if it was not componentized in subsets.
Virtualised Network Function (VNF): According to ETSI NFV, implementation of an NF that can be deployed on a Network Function Virtualisation Infrastructure (NFVI)
Virtualised Network Function Component (VNFC): According to ETSI NFV, internal component of a VNF providing a defined sub-set of that VNF's functionality, with the main characteristic that a single instance of this component maps 1:1 against a single Virtualisation Container.
...
W
...
X
...
Y
...
Z
...
Standard Terminology
| Anchor |
|---|
| Standard Terminology |
|---|
| Standard Terminology |
|---|
|
ETSI NFV - Terminology for Main Concepts in NFV
| View file |
|---|
| name | gs_NFV003v010301p.pdf |
|---|
| height | 250 |
|---|
|
