Contribute ecosystem requirements and principles to Requirements and Principles Workstream

Provide requirements to ensure that ODA enables CSPs to become a contributor to an ecosystem platform and/or a curator of such a platform (on-boarding etc.)

Develop an IoT ecosystem scenario & requirements to prove the ecosystem capabilities of ODA (harvest from Catalysts where appropriate)

Contribute diagrams to Functional Architecture Workstream

Evaluate ODA data architecture vs support for data protection / privacy regulation

TMF071

(CORE)

Include references to DPRA / DSRA existing assets in ODA documents.

User Guide for Network Slice Management

GB999

(Plus supporting SID and API documents)

User Guide for Network Slice Management 

Shows how to manage network slices using TM Forum artifacts including Open APIs

• The Connectivity Models needed  between ODA Commerce and production for a Network slices including UML and API data models (expectation is sample JSON schemas for Open API Service Ordering TMF641)
• Mapping the specific platforms and the supporting management systems that take part in 5G slice management.
• Architectural impacts of the data models on the supporting management systems:  intent based management with guaranteed SLAs; configuration of Policy for service assurance and SLA as part of the onboarding metadata; what meta data needs to be discovered; and how policy interacts with SLA and Service Assurance.

Describes how 5G network slices can be managed as abstracted connectivity services between ODA Commerce and Production functions groupings to achieve ODA decoupling.

Demonstrates how connectivity service models can be mapped to the the 5G catalyst functions and systems based on 5G standards in 3GPP used in  the DTW 2018 Nice 5G catalysts.

Lifecycle Management for 5G Network Slice Services

Coordination activity

TOSCA template for 5G services

This work item is about pro-actively coordinating the alignment and consistency  of three deliverablse acorss ODA and and IoE Program.

• Solution Guide for Network Slice Management. charter WI 6.04.1
• TR276 update Monetising 5G
• Lifecycle 5G management template descriptor based on 6.05.3: exemplar based on one of the TR276 service examples Formal deliverable s are an example in 6.05.3 and a github schema
   

Deployment Pattern for SDN/NFV Solutions

Study the deployment patterns  SDN/NFV solutions. using the Green and Brown field examplees

Identifies the risk and challenges from CSPs perspective of differentdeplument paterns

Analyze the various Opensource solutions and SDOs work.

study will recommned wehter a DOman Orchetrator ( DO)  approach can address the CSP diverse deployment needs.

Policy Management for Zero-touch Automation

 Deferred to R19.

Specification of use cases that illustrate the need for policy management, with a focus on zero-touch automation. The use cases will be used to derive requirements, which in turn, will be used to identify information model and API needs. 

The work item will consider traditional Event – Condition – Action (ECA) policy management as well as intent-based policy management.

Note some work in in IG1174 Section 4.1 which can be leveraged in next release.

 ODA Intelligence Management Implementation Guide

(proposal added at AW Dallas may be reallocated to OLM workstram 6.05.x)

IG : Exploratory Report

 This Workstream aims at operationalizing the Design principle and High level Architecture Design of “ODA Intelligence Management “defined IG 1167 by describing the whole process when moving from Design phase to Execution (run-time) phase of Decision making Element and associated Managed Entities.

 In this process Autonomic behaviour of a Decision Making Element auto-discovers the ODA Intelligence Management Policy, Goals and Objectives, other Decision Making Elements it requires to collaborate with, and the capabilities of the Decision Making Element’s assigned Managed Entities (the (information that gets available at run-time). Then the Decision Making Element performs the self-* operations on its assigned ODA Managed Entities by orchestrating (launching and/or configuring) the Managed Entities when required. Orchestration means launching (at run-time) a Managed Entity if no instance exists yet that can provide a desired service and then configuring the instance (the newly launched or an already existing one).

The outcome is to provide guidance to all the actors involved in the process (Architects, Operations Managers, Algorithm Developers, Digital Service Providers, ISVs, and Standard Makers) along with a detailed description of the associated Catalyst that aims at showcasing an implementing the guidance for a real use case in the decision making space. This Catalyst could be conducted jointly with ETSI GANA community.

Guide  defining the  operationalization of the Design principle and High level Architecture Design of “ODA Intelligence Management “defined IG 1167 by describing the whole process when moving from Design phase to Execution (run-time) phase of Decision making Element and associated Managed Entities.Guide

Includes a detailed description of the associated Catalyst that aims at showcasing an implementing the guidance for a real use case in the decision making space. This Catalyst could be conducted jointly with ETSI GANA community.

Scoping and seeking broader vendor support and first draft

ODA Component Definition

Model-Driven Design of Management Interfaces for ODA Components

(prev Composition and Aggregation of ODA Components in a Cloud Native Environment)

IG1174

This document defines common interface elements for the management of ODA components in the context of a platform. The focus is on the management aspects of components and not the core aspect which will vary greatly depending on the type of component. The end goal is to facilitate an ecosystem of components that expose common management interfaces and thus significantly reducing the task of managing components.

Component developers

Input into more detailed API design work for components and/or input to an ODA component lab

The plan is to finish the document early in R18.5 and thus a stable draft is expected in the first 90 days

As noted, the plan is to finish this document well before the deadline for R18.5

The Art of Managing Things

 Prov title: Model driven examples of ODA Component Usage

 Series of examples of use of ODA components derived from TI example of hierarchy of Orchestrators, Activators, Controllers

Validation Activity Approach

Approach is based on each Theme User groups refining and agreeing user stories for sub-themes which the specification teams implement as part of an Application Note for each of those User stories, and any supporting foundational assets.

Validation Activity Description

Validation of the Application Notes is done by the User Groups setting the User Stories / requirements and reviews will be scheduled at TAW and as appropriate. 

Dependencies

Additionally the project is working closely with catalyst projects to capture the key results and this validates through sponsors and participants that the technical work is relevant timely and adoptable.

Comments

Confluence Space

Document creation and publishing

Provided by default

JIRA Space

Contribution and feedback management

Provided by default