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

Signalling aspects                                             3


                                                        Annex C


                       Scenarios and requirements of BNG event and status notification
                                               to the service platform

                                  (This annex forms an integral part of this Recommendation.)

            C.1     Scenarios and requirements of BNG event and status notification to the service platform
            Network services and the service platform have the requirement of knowing what is happening in the BNG.
            Based on the running status of the BNG, network services do their specific service handing.
            The event and status notifications to the service platform may be reported in a reactive or proactive way. In
            the  reactive  way,  only  when  the  request  from  the  service  platform  is  received,  will  the  BNG  send  the
            notifications. On the other hand, in the proactive way, the BNG keeps on sending the notification to the
            service platform whether it is requested or not.

            The event and status notification are categorized into three types: resource notifications, failures/faults
            notifications, and statistics notifications. The following clauses elaborate each of these in detail.
            C.1.1   Resource notifications

            Resources within the BNG are composed of general resources of IT, such as CPU, RAM, storage, etc. As a
            network entity, BNG resources include ports, bandwidth between the BNG and service platform, capacity of
            forwarding rules, line-card forwarding speed, capacity of access users, etc.
            Most of the time, these resources remain the same. Resource notification only needs to be reported to the
            service platform once.
            These notifications properly fall into the reactive way.

            C.1.2   Failure/faults notifications

            The failure/faults are of all levels of BNG malfunctions, such as port down or up, link down or up, unsupported
            rules, exceeding the capacity, line-card dump, etc. All these events are essential to specific network services.

            For example, the link down or up notifications are crucial to the network topology discovery service. Based
            on the notification, the topology can be closely in accordance with the real network topology.

            The failure and faults should to be handled promptly, and then these notifications should be in the proactive
            way.
            C.1.3   Statistics notifications

            The BNG acts according to the actions from the service platform and network services. The BGN can be
            configured to do some statistics. The statistics may include port rate, bandwidths consumed, link utilization,
            current CPU usage, percentage of forwarding rules consumed, etc.
            When  the  BNG  receives  the  statistics  requests,  and  in  case  this  kind  of  statistics  are  enabled  by  the
            configuration, the statistics will be reported to the service platform or the network service.
            The statistics notifications are sent to the service platform only when they are requested. This is the reactive
            way.















                                                                                                        1385
   1390   1391   1392   1393   1394   1395   1396   1397   1398   1399   1400