Page 169 - ITU-T Focus Group IMT-2020 Deliverables
P. 169

ITU-T Focus Group IMT-2020 Deliverables                                3


            Figure X illustrates the Capability Exposure Architecture for slice management.


                          Applications & Services with various requirements (M2M/IoT, Content delivery)

                            API for Slice Building / Modification
                                             Network Capability Exposure



                                      Resource Management

                                                 Resource Orchestrator

                                                  Resource Provider









                                       eMBB Slice

                                   IoT Slice
                                M2M Slice


                                     Figure 8.1-1 – Capability Exposure for Slice Building


            Use Case 1: The Creation or instantiation of Slice Triggered by the 3rd Party
                         rd
            1.      The 3  party indicates the functionality and performance requirements to create a slicing via Slice
                    Building API. In terms of implementation, a ServiceTemplate Profile may be sent to by the API. And
                    this temple contains the parameters to describe the functionality and performance requirements.
            2.      The network capability exposure function transfers the above slice building request to the resource
                    management function.

            3.      The Resource Orchestrator function authorizes functionality and performance requirements based
                                                                  rd
                    on the agreement between the operator and the 3  party. If the request is allowed, the Resource
                    Orchestrator function forwards resource requirement to the Resource Provider and accordingly the
                    Resource Provider allocates the required resource (hardware and software) to create or instantiate
                    the dedicated slice.

            Use Case 2: The Dynamic Modification of Functionality and Performance Configuration of Slice
            1.      The 3rd party indicates the modification of functionality or performance for a pre-created slicing via
                    Slice Modification API. The modification may be triggered for the reason of lack of resource or new
                    function needed by the 3rd party in the slice. In terms of implementation, a Service Template Profile
                    may be sent to by the API. And this temple contains the parameters to describe the functionality
                    and performance modification requirement.
            2.      The  network capability exposure  function transfers the  above  slice modification  request  to the
                    resource management function.

            3.      The  Resource  Orchestrator  function  authorizes  functionality  and  performance  modification
                                                                                      rd
                    requirements based on the agreement between the operator and the 3  party. If the request is
                    allowed,  the  Resource  Orchestrator  function  forwards  resource  requirement  to  the  Resource
                    Provider and accordingly the Resource Provider re-allocates the required resource (hardware and
                    software) to modify the dedicated slice.


                                                                                                         163
   164   165   166   167   168   169   170   171   172   173   174