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

Core network aspects                                            1


            •       traffic scheduling based on information provided by network resource management, application
                    requirements  provided  by  the  S-NICE  orchestration  capabilities,  and  analysis  results  from  the
                    content and context analysis capability;
            •       receiving results of content and context analysis of infrastructure and applications, and performing
                    policy control and traffic scheduling based on these results. The S-NICE controller capabilities are
                    required to be aware of physical and virtual network topology, traffic flows and information of the
                    infrastructure;
            •       cooperation  with  the  network  management  system  to  provide  operation,  administration  and
                    maintenance (OAM) and alarm information;
            NOTE 3 – The S-NICE controller capabilities can provide additional support for the provisioning of OAM and alarm
            information, however  functional overlapping between  S-NICE controller capabilities and the network management
            system needs to be avoided.
            •       cooperation between physical network and virtualized network;
            •       connection with other S-NICE controller capabilities;
            •       monitoring of physical network and virtualized network.

            7.4     The S-NICE infrastructure capabilities at the transport layer

            The S-NICE infrastructure capabilities implement the actions decided by the S-NICE controller capabilities.
            The  S-NICE  infrastructure  capabilities  include  the  policy  enforcement  capability,  the  traffic  scheduling
            enforcement capability, the content and context detection capability, and the access and core transport
            capability of S-NICE.
            The S-NICE infrastructure capabilities are required to support, but are not limited to, the following features:

            •       communication with the S-NICE controller capabilities;
            •       provision of the infrastructure information (e.g., network topology information, flow information,
                    service routing information) to the relevant S-NICE controller capabilities based on requests;

            NOTE 1 – Different S-NICE controller capabilities may request different infrastructure information.
            •       forwarding of traffic on a per flow basis;
            •       forwarding of traffic while maintaining policy consistency among the S-NICE controller capabilities,
                    the S-NICE infrastructure capabilities and the applications;
            •       isolation and virtualization of different parts of the network;
            NOTE 2 – For example, many access transport networks can be isolated from each other and virtualized as one network.
            •       reception of policy decisions from the S-NICE controller capabilities and enforcement of these policy
                    decisions (e.g., by packet forwarding and processing);
            •       reception of traffic scheduling rules from the S-NICE controller capabilities and enforcement of these
                    traffic scheduling rules (e.g., by transport node selection and path selection).


            8       Security considerations

            The security requirements of S-NICE are aligned with the security requirements of NICE [ITU-T Y.2301] with
            the following additional requirements:

            •       enhanced security of the SDN controller(s) which incorporates the transport control capabilities,
                    because the logically centralized controller could be a single point of failure, or a target of malicious
                    attacks;
            •       secure  mechanisms  to  authorize  network  configurations  and  operations  such  as  routing  path
                    establishment  or  virtualized  network  function  deployment,  upon  demand  by  services  or
                    applications;






                                                                                                         195
   200   201   202   203   204   205   206   207   208   209   210