Page Comparison

...

Slice analysis MS consumes PM message from PM-Mapper and analyze the slice PM data and triggers the closed-loop if needed. For analyzing the PM data, it consumes data from Config DB.

The PM data which the slice analysis MS consumes currently are:

SM.PrbUsedDl.snssai

SM.PrbUsedUl.snssai

Bulk PM Flow:

1. NF notifies VES Collector that a PM file is available for upload.
2. Data File Collector downloads PM Files from the NF and publishes them to Data Router.
3. PM-Mapper creates custom Performance events (VES) from the PM File data according to PM Mapping File.
4. Analytics Applications (Slice Analysis MS) use these performance events for targeted analysis of network operations.

Slice Analysis MS Flow:

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

Deployment Prerequisite/dependencies

...