Page 242 - 5G Basics - Core Network Aspects
P. 242

1                                                Core network aspects


            Preconditions

            A virtualized network entity is composed of six running VMs.
            Operational flows

            This operational flow shows scaling out/in.


















                                                      Figure I.3 – Scaling out/in


            1)      The resource management system detects that the traffic volume is decreasing, and it asks  the
                    virtualized network entity to shut down the components of the entity running on two VMs.
            2)      Two VMs in network entity is shut down, and if there is no VM running on a physical server, the
                    physical server can be shut down.
            3)      The resource management system detects that the traffic volume is reaching the upper threshold,
                    it asks the virtualized network entity to boot two VMs.
            4)      Two VMs in network entity boot, and if there is no available resource on running physical servers, a
                    new physical server should be booted firstly.

            I.3     SAME network slice for MVNO scenario
            Descriptions

            An MVNO utilizes part of the operator's current network, such as RAN and IP network, but wants to deploy
            some  other  functions  independently,  such  as  the  gateway  (GW),  user  profile  function,  IP  multimedia
            subsystem (IMS) and application servers. The MNO provides SAME network slices to the MVNO to deploy the
            specific function elements in virtual manner.

            Preconditions
            A  MVNO  wants  to  deploy  some  network  functions  by  itself  except  the  shared  infrastructure  with  the
            operator. The operator provides a SAME network slice that contains SAME functions, and related resources
            like computing, storage, networking, to the MVNO. The MVNO deploys its network functions on the hardware
            resource pool of the operator. The MNO is responsible for the management of the MVNO's network.

            Operational flows
            1)      The MVNO asks the operator to provide the network resource with required network performance,
                    such as bandwidth, session number, quality of service (QoS) level.
            2)      The operator allocates a SAME network slice to the MVNO that contains SAME functions and related
                    resources. The MVNO can also install individual network functions in a virtualized manner. The
                    MVNO sets up the network and launches the services.
            3)      The operator adjusts the SAME network slice dynamically following the requirements and the load
                    of the network functions of the MVNO.
            4)      The operator maintains the MVNO's network built on the hardware resource pool.



            232
   237   238   239   240   241   242   243   244   245   246   247