...
Information Element Name | VES Information Model | ||||||||
Points of Contact | Information Element Main Contact - Marge Hillis Oskar Malm Information Modeling Contact - Marge Hillis Schema Definition Contact - Damian Nowak | ||||||||
Related Use Cases | C&PS Configuration & Persistency Service (for the CM notifications) | ||||||||
Participating ONAP ComponentsThe list of ONAP Components that are stakeholders for the Information Element | DCAE (DCAE VES Event Listener) | ||||||||
Related JIRA |
| ||||||||
Description | VES Information Model Adding a new valid enum for the domain and new field for the namespace only populated if the domain is stndDefinedOverview 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.) | ||||||||
3GPP Standards TS28.532 | |||||||||
Attributes | Domain (Existing Attribute), adding a new enum value "stndDefined" stndDefinedNamespace (NEW Attribute); type: (string) / enum ?? stndDefined field added to VES common schema. | ||||||||
Relationships | VES Information Model Does not change the VES Object class or Object class relationships in the Information Model. | ||||||||
Originator | The xNF sends the stndDefined Event, and is the "owner" (source of truth) of the data. The payload (e.g. CM information) is owned by the xNF and originates sending the VES event to ONAP. | ||||||||
Consumers | DCAE receives this information through VES event listener How DCAE uses it: it routes it to the proper DMaAP topic based on the stndDefined domain and namespace. Micro-services (future) could subscribe to these events listening for these topics. How would micro-services use it (future): Depends on the event (type of namespace events), depends what purpose of the micro-services. Nothing outside of ONAP will access this information. | ||||||||
Producers | The namespace may be updated if additional standards bodies join in on the definition for the emission of events supported by ONAP. For example IETF, broadband forum etc. It allows ONAP to process general events from various standards bodies. Condition when they update - New category of action, (CM, PM, FM) needs to be added. | 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? Valid model - in the VES event listener specification. | ||||||||
Impacted APIs & Schemas | VES Schema (loaded and defined in design time) in the xNF onboarded artifacts. API/Swaggers - DCAE API for DMaaP. DCAE to VES header (modified) DCAE to SDK API (modified) DCAE to CBD API (modified) Identify impacted ONAP schemas & APIs Are there existing schemas be used or extended? | ||||||||
Information Modeling StatusWhat | This is scheduled in the R7 Modeling planning page. The Wiki page: ONAP R7 Modeling High Level Requirements It is being tracked by the Modeling-370 Jira which can be found here:
Status: It is active for the current release, this use case has been accepted. The model is being developed. | ||||||||
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. | A schema was provided in the architecture presentation | |||||||
ONAP Release Priority | R7 Guilin - Model work has been approved to proceed. In the R7 planning page: Guilin Release Requirements , the Modeling-370 is under REQ-327 and TSC Priority 0 "Go" | ONAP Release Priority | Prioritization for ONAP Releases |
Supporting Files:
Topic | File | ||||||
---|---|---|---|---|---|---|---|
Architecture Subcommittee Presentation May 19, 2020 |
| ||||||
...