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

Signalling aspects                                             3


                                                        Annex B


                    Scenarios and requirements of network service configuration on BNG
                                  (This annex forms an integral part of this Recommendation.)


            This annex describes some scenarios related to flexible network service combination on BNG.


            B.1     Scenarios and requirements of the network service configuration on BNG
            Network services all have different ways of packet handling. Different kinds of BNG functionalities are needed
            by different kinds of network services.
            Through the service platform, the network services enforce the functionalities required on BNG. At the same
            time, the network services may also enforce their configuration on the service platform.
            Most of the configurations fall into either the static configuration or the runtime configuration. The following
            two clauses elaborate these in detail.

            B.1.1   Static network service configuration on BNG
            Mostly,  the  static  configurations  needed  by  a  network  service  are  pre-installed  on  the  BNG  before  the
            network service totally runs up. The static configurations mainly include the following:
            1)      Resource management:
                    The resource includes physical resources as well as logical resources, which may be ports, queues,
                    bandwidth, link-utilization, etc.
            2)      Network service handling configuration:
                    The service platform may include some basic network service handling entities, which are called
                    service atoms. For the network service composed of the service atoms, some rules/policies may be
                    needed by the service atoms. Then the network service handling configuration is just for these. One
                    possible example would be the URL filtering service atom, which is aimed to filter out and stop the
                    forbidden URL visiting based on black/white URL lists. The default black/white URL lists are setup by
                    the configuration. Some runtime configurations are also needed.
            3)      BNG behaviours management:
                    The BNG may behave either in the legacy network forwarding manner or in the software defined-
                    networking (SDN)/OpenFlow forwarding manner. Or the BNG may behave with both of the two, in
                    the hybrid manner. This main behaviour should be configurable in all levels of granularities, such as
                    per port, per line card, per chassis, entire network device, etc. Additional behaviours may include
                    topology discovery enabling or disabling, link monitoring enabling or disabling, statistics enabling or
                    disabling,  etc.  The  BNG  behaviour  configuration  should  be  able  to  enable  or  disable  these
                    functionalities.
            The static configurations may be done in the following ways:
            1)      by the operators/managers of the networks services;

            2)      by the networks service itself at initialization stage;
            3)      by the combination of the operators/managers and network service itself.

            B.1.2   Runtime network service configuration on BNG
            The runtime configurations are highly network service type and runtime packet relative. Some of the runtime
            network service configurations are in the same range with the static configurations, the only difference is
            whether the configuration is pre-determined or not.







                                                                                                        1383
   1388   1389   1390   1391   1392   1393   1394   1395   1396   1397   1398