Topic2 - Automation in Multi-Stakeholder Ecosystems

From ZSM Wiki
Revision as of 10:31, 19 November 2021 by Vreck (talk | contribs) (Description)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Telecom operators wanting to offer end-to-end services with potential global reach will typically require dynamic and automated interaction with other providers for enabling an Open Coopetitive  5G Service Ecosystem but

•    How can they find out about the capabilities of other providers?

•    How can they handle the lifecycle of such services?

•    How can they ensure SLAs among providers?

Presently, interconnection and wholesale environments are static requiring considerable interactions for any inter-provider connection, largely dependent on manual operation.

We should be able to leverage on virtualization & programmability for creating service offerings with

•    Proper mechanisms for trading these capabilities (at resource and XaaS/VNFaaS/ level)

•    Interfaces / APIs that could allow this to happen in an automated way

•    Configure and manage capabilities on the instantiated resources & functions


ACTIVE (Approved at ZSM#04, Oct 2018)

Points to prove/refute

What aspects of automation were used to support the PoC, which means were used, and how did it enrich the PoC?

Criteria of success

Document how the scenarios, management solutions or management interfaces have been implemented.

Technical information to be provided by the PoC Team

•    Scenario, management solution or management interface description

•    High-level PoC architecture

•    Specifics on the issues faced

•    Specifics on the solutions provided

•    Specifics on the lessons learnt

Template for the PoC Feedback Contribution

No specific template. POC Teams are expected to submit a Technical Report covering the points mentioned above.

Concerned WIs

ZSM-001 “Requirements based on documented scenarios”

ZSM-003 “End to end management and orchestration of network slicing”