Page History

...

1. Slice analysis ms consumes PM messages from PERFORMANCE_MEASUREMENTS topic
2. For analysis Slice analysis MS consumes various data from Config DB
   1. List of Network Functions which serves the snssai
   2. List of RICs and its corresponding cell mappings of the snssai
   3. Current Configuration of the RICs
   4. Slice Profile of the snssai
   5. Subscriber details of the snssai (for sending the onset message to policy)
3. With the help of pm data, Slice analysis MS computes the DLThptPerSlice and ULThptPerSlice for the RICs of the snssai, and the computed value is compared with the current configuration of the RICs.
4. If the change in configuration exceeds the minimum percentage value which is kept as a configuration parameter, then the closed-loop will be triggered by posting the onset message to DMAAP

Architecture

DMAAP Client - creates a thread pool for every DMAAP topic consumer. The thread polls the DMAAP topic for every configured time interval and whenever a message is received it stores that message in the Postgres DB.

PM Thread - reads the PM event from the database and puts the PM sample in the internal queue in the format which is needed for further processing.

Consumer Thread - Consumes pm samples from the internal queue and make all the required Config DB calls, perform the analysis, and puts the onset message to the DMAAP topic

Deployment Prerequisite/dependencies

...