Newer
Older
Examples
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_8_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_4_8">
<span class="md-nav__icon md-icon"></span>
Examples
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="service_design/examples/intro/" class="md-nav__link">
<span class="md-ellipsis">
Introduction
</span>
</a>
</li>
<li class="md-nav__item">
<a href="service_design/examples/calculator_crd_aas/calculator_crd_aas/" class="md-nav__link">
<span class="md-ellipsis">
Calculator CRD aaS
</span>
</a>
</li>
<li class="md-nav__item">
<a href="service_design/examples/jenkins_helm_install_aas/jenkins_helm_install_aas/" class="md-nav__link">
<span class="md-ellipsis">
Jenkins Helm Installation aaS
</span>
</a>
</li>
<li class="md-nav__item">
<a href="service_design/examples/monitoring_aas/monitoring_aas/" class="md-nav__link">
<span class="md-ellipsis">
Monitoring aaS
</span>
</a>
</li>
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
</ul>
</nav>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_5" >
<label class="md-nav__link" for="__nav_5" id="__nav_5_label" tabindex="0">
<span class="md-ellipsis">
Service Ordering
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_5_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_5">
<span class="md-nav__icon md-icon"></span>
Service Ordering
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="service_ordering/ordering_services/" class="md-nav__link">
<span class="md-ellipsis">
Ordering Services from catalogs
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_6" >
<label class="md-nav__link" for="__nav_6" id="__nav_6_label" tabindex="0">
<span class="md-ellipsis">
Addons
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_6_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_6">
<span class="md-nav__icon md-icon"></span>
Addons
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="addons/intro/" class="md-nav__link">
<span class="md-ellipsis">
Introduction
</span>
</a>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_6_2" >
<label class="md-nav__link" for="__nav_6_2" id="__nav_6_2_label" tabindex="0">
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
<span class="md-ellipsis">
CAMARA
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_6_2_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_6_2">
<span class="md-nav__icon md-icon"></span>
CAMARA
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="addons/camara/intro/" class="md-nav__link">
<span class="md-ellipsis">
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
Offering CAMARAaaS
</span>
</a>
</li>
<li class="md-nav__item">
<a href="addons/camara/qod/" class="md-nav__link">
<span class="md-ellipsis">
Quality on Demand
</span>
</a>
</li>
</ul>
</nav>
</li>
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
<li class="md-nav__item">
<a href="addons/sylva/" class="md-nav__link">
<span class="md-ellipsis">
LF Sylva
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_7" >
<label class="md-nav__link" for="__nav_7" id="__nav_7_label" tabindex="0">
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
<span class="md-ellipsis">
Design & Architecture
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_7_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_7">
<span class="md-nav__icon md-icon"></span>
Design & Architecture
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="architecture/architecture/" class="md-nav__link">
<span class="md-ellipsis">
Architecture
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/messagebus/" class="md-nav__link">
<span class="md-ellipsis">
Message bus
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/osom/" class="md-nav__link">
<span class="md-ellipsis">
OSOM
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/cridge/" class="md-nav__link">
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
<span class="md-ellipsis">
CRIDGE
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/metrico/" class="md-nav__link">
<span class="md-ellipsis">
METRICO
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/oauth/" class="md-nav__link">
<span class="md-ellipsis">
Authentication
</span>
</a>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_7_7" >
<label class="md-nav__link" for="__nav_7_7" id="__nav_7_7_label" tabindex="0">
<span class="md-ellipsis">
APIs
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="2" aria-labelledby="__nav_7_7_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_7_7">
<span class="md-nav__icon md-icon"></span>
APIs
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="architecture/tmfapi/" class="md-nav__link">
<span class="md-ellipsis">
TMF API
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/nfvapi/" class="md-nav__link">
<span class="md-ellipsis">
NFV API
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="architecture/issuemgt/" class="md-nav__link">
<span class="md-ellipsis">
Issue management
</span>
</a>
</li>
<li class="md-nav__item">
<a href="architecture/centrallog/" class="md-nav__link">
<span class="md-ellipsis">
Central logging
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item md-nav__item--nested">
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_8" >
<label class="md-nav__link" for="__nav_8" id="__nav_8_label" tabindex="0">
<span class="md-ellipsis">
Contribute
</span>
<span class="md-nav__icon md-icon"></span>
</label>
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_8_label" aria-expanded="false">
<label class="md-nav__title" for="__nav_8">
<span class="md-nav__icon md-icon"></span>
Contribute
</label>
<ul class="md-nav__list" data-md-scrollfix>
<li class="md-nav__item">
<a href="contribute/developing/" class="md-nav__link">
<span class="md-ellipsis">
Developing
</span>
</a>
</li>
<li class="md-nav__item">
<a href="contribute/documenting/" class="md-nav__link">
<span class="md-ellipsis">
Documenting
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="terminology/" class="md-nav__link">
<span class="md-ellipsis">
Terminology
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
</span>
</a>
</li>
</ul>
</nav>
</div>
</div>
</div>
<div class="md-sidebar md-sidebar--secondary" data-md-component="sidebar" data-md-type="toc" >
<div class="md-sidebar__scrollwrap">
<div class="md-sidebar__inner">
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
<label class="md-nav__title" for="__toc">
<span class="md-nav__icon md-icon"></span>
Table of contents
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#usage" class="md-nav__link">
<span class="md-ellipsis">
Usage
</span>
</a>
<nav class="md-nav" aria-label="Usage">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#an-end-to-end-e2e-service-orchestration-framework" class="md-nav__link">
<span class="md-ellipsis">
An end-to-end (E2E) service orchestration framework
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#an-e2e-service-orchestration-workflow" class="md-nav__link">
<span class="md-ellipsis">
An E2E service orchestration workflow
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#openslice-for-service-providers" class="md-nav__link">
<span class="md-ellipsis">
OpenSlice for Service Providers
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#openslice-for-service-consumers" class="md-nav__link">
<span class="md-ellipsis">
OpenSlice for Service Consumers
</span>
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#live-demo" class="md-nav__link">
<span class="md-ellipsis">
Live Demo
</span>
</a>
</li>
<li class="md-nav__item">
<a href="#probe-further" class="md-nav__link">
<span class="md-ellipsis">
Probe further
</span>
</a>
</li>
</ul>
</nav>
</div>
</div>
</div>
<div class="md-content" data-md-component="content">
<article class="md-content__inner md-typeset">
<h1 id="introduction">Introduction</h1>
<p><a class="glightbox" href="images/openslice_logo.png" data-type="image" data-width="100%" data-height="auto" data-desc-position="bottom"><img src="images/openslice_logo.png" alt="logo" width="200"/></a></p>
<p><strong>Version</strong>: 2024Q4 (<a href="https://labs.etsi.org/rep/osl/code/org.etsi.osl.main/-/releases">Release Notes</a>)</p>
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
<p>The ETSI Software Development Group for OpenSlice (SDG OSL) is developing an open-source service-based Operations Support System (OSS) to deliver Network as a Service (NaaS) following specifications from major SDOs including ETSI, TM Forum and GSMA.</p>
<h2 id="usage">Usage</h2>
<p>OpenSlice can be used in managing 5G network services from the user device to the core network and cloud as well as for Orchestrating cloud resources across private and public clouds for enterprise applications. OpenSlice is capable of supporting most of the features of an end-to-end (E2E) service orchestration framework while many of them will be more mature in future releases. The following figure displays the general usage of OpenSlice. </p>
<p><a class="glightbox" href="images/global_approach.png" data-type="image" data-width="100%" data-height="auto" data-desc-position="bottom"><img alt="OpenSlice usage" src="images/global_approach.png" /></a></p>
<p>The image illustrates how OpenSlice supports the idea of an E2E network service orchestration framework by integrating multiple network components and layers, from user devices at the edge to radio, transport networks, core and public cloud services, ensuring seamless, secure, and efficient delivery of network services. Assuming that there are domain controllers for all the above domains OpenSlice can create the end-to-end service via the domain controllers by following the process of creating and deploying the end-to-end service by implementing transformations, and consuming APIs from various network entities.
OpenSlice, in a nutchell, offers user interfaces where users can interact with the framework to order, expose, and manage service catalogs, services and resources that can be ordered, following business logic and policies and exposed through the APIs. </p>
<h3 id="an-end-to-end-e2e-service-orchestration-framework">An end-to-end (E2E) service orchestration framework</h3>
<p>An end-to-end (E2E) service orchestration framework is designed to manage and automate the entire lifecycle of services across multiple domains and technologies. For delivering, especially, Network as a Service (NaaS) a comprehensive system is needed that automates and manages the entire lifecycle of network services, from provisioning to monitoring and decommissioning, while ensuring seamless integration, operation, and delivery of services from the initial request to the final delivery, spanning all involved components and layers. Such E2E frameworks enable users to consume network services on-demand, similar to how cloud computing services are consumed. Some key components and features of such frameworks are:</p>
<ul>
<li>Service Catalogs including predefined Network Services based on service templates for common network services like 5G core functions, 5G slices, VPNs, SD-WAN, firewalls, load balancers, etc. as well as custom Network services with Options for users to define their own network configurations.</li>
<li>User Interface (UI) and APIs exposure, offering both a Self-Service Portal that allows users to request, configure, and manage network services as well as APIs for enabling programmatic access to network services for integration with other systems and automation scripts.</li>
<li>Service Design and Creation through service templates based on predefined models for creating services.</li>
<li>Automation and Workflow Management via Orchestration Engines, supporting Process Automation for automating repetitive tasks and processes, workflow management and orchestration for automating the provisioning, configuration, and management of network services while coordinating multiple workflows to ensure services are delivered efficiently, ensuring that services comply with predefined policies and standards.</li>
<li>Standardized API exposure for seamless integration with different systems and services and APIs transformation support for converting data formats and protocols to ensure compatibility and information exchange between systems during workflows orchestration</li>
<li>Service and Resource management and Orchestration while including the capability of multi-domain coordination in managing services/resources across different domains like cloud, 5G core, radios, transport network, and edge including dynamic allocation with adjusting resources based on demand and service requirements. To accomplish the above advanced technologies need to be exploited like, Containerized workloads, Network Function Virtualization (NFV) which uses virtualized network functions to provide services like routing, switching, and security and Software-Defined Networking (SDN) which Controls the network programmatically to dynamically manage traffic and resources.</li>
<li>Monitoring and Analytics including Service Monitoring while continuously tracking the performance and health of services with capabilities to analyse data to optimize service delivery and predict issues. Real-Time Monitoring is also needed for tracking the performance and health of network services enabling analytics that provide insights for optimization and troubleshooting.</li>
<li>Security and Access Control for ensuring only authorized users and systems can access network services. while implementing rules and policies to comply with regulatory requirements.</li>
</ul>
<h3 id="an-e2e-service-orchestration-workflow">An E2E service orchestration workflow</h3>
<p>In general an E2E service orchestration workflow includes the following phases:</p>
<ul>
<li>Service Request: Users or systems request a network service through the self-service portal or API. The request can specify details such as bandwidth, security features, geographic coverage, and duration.</li>
<li>Service Orchestration: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with the underlying components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers ) to provision and configure the required network functions and connectivity.</li>
<li>Provisioning and Configuration: Services, network resources and network functions (VNFs) are instantiated and configured according to the service request during Service Orchestration through the orchestration engine. Other controllers manage their own domains, for example SDN controllers, manage the flow of data through the network to ensure optimal performance and adherence to policies, RAN controllers manage the RAN resources, Containerized controllers manage their workload, etc</li>
<li>Service Delivery: The E2E network service is activated and made available to the user. Continuous monitoring ensures the service operates as expected, with automatic adjustments made as necessary.</li>
<li>Lifecycle Management: The orchestration framework handles updates, scaling, and any necessary modifications throughout the service lifecycle.</li>
<li>At the end of the service period, resources are decommissioned and reclaimed.</li>
</ul>
<h3 id="openslice-for-service-providers">OpenSlice for Service Providers</h3>
<p>OpenSlice is used by Service Providers to design Network Services, expose them in Service Catalogues and make them available for Service Orders. OpenSlice then can perform the E2E service orchestration workflow.</p>
<p>There are various portals offering UI friendly access to users acting as Service Providers:</p>
<ul>
<li>The Services portal allows Service Providers to design and expose services.</li>
<li>The Resource portal allows users to access resource specifications and running resources in resource inventory.</li>
<li>The NFV portal allows users to manage NFV artifacts and onboard them to a target MANO/NFV Orchestrator.</li>
<li>The Testing portal allows Service Providers to manage test artifacts</li>
<li>The Products portal allows Service Providers to expose services as products</li>
</ul>
<h3 id="openslice-for-service-consumers">OpenSlice for Service Consumers</h3>
<p>OpenSlice allows Service Consumers to browse the available offered service specifications in a self-service manner. It also supports TMFORUM Northbound APIs regarding Service Catalog Management, Ordering, Resource, etc.
There are various portals offering UI friendly access to users acting as Service Consumers:</p>
<ul>
<li>The Services portal allows Service Consumers to select and order predefined services.</li>
<li>The Resource portal allows users to access running resources in resource inventory.</li>
<li>The NFV portal allows users to self-manage NFV artifacts and onboard them to a target MANO/NFV Orchestrator.</li>
<li>The Testing portal allows Service Consumers to manage test artifacts</li>
<li>The Products portal allows Service Consumers to expose services as products</li>
</ul>
<p>3rd party applications can use OpenSlice through TMForum Open APIs.</p>
<h2 id="live-demo">Live Demo</h2>
<p>Check a live demo of OpenSlice in the following pages:</p>
<ul>
<li>OpenSlice demo: <a href="http://portal.openslice.eu/">http://portal.openslice.eu/</a></li>
<li>OpenSlice Service Catalogs and ordering: <a href="http://portal.openslice.eu/services/">http://portal.openslice.eu/services/</a></li>
<li>OpenSlice NFV Services onboarding: <a href="http://portal.openslice.eu/nfvportal">http://portal.openslice.eu/nfvportal</a></li>
</ul>
<p>Login credentials:</p>
<ul>
<li>username=admin, password=openslice </li>
<li>username=admin, password=changeme</li>
</ul>
<h2 id="probe-further">Probe further</h2>
<ul>
<li>How OpenSlice works? See the <a href="architecture/architecture/">Architecture</a> section</li>
<li>Installing OpenSlice? See the <a href="getting_started/deployment/introduction/">Deployment</a> section</li>
<li>Learn more on <a href="naas/introduction/">how OpenSlice supports Network as a Service(NaaS)</a></li>
<li>Who is maintaining OpenSlice? See <a href="https://osl.etsi.org/">OSL ETSI SDG</a></li>
</ul>