Versions Compared

Old Version 14

changes.mady.by.user sendil kumar Jaya kumar

Saved on

compared with

New Version 15

changes.mady.by.user Ahila P

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Refer Intelligent Slicing flow for complete closed loop sequence. Existing ML MS (not officially exposed to ONAP) requires certain enhancements to satisfy the intent guarantee. PM data generated for the closed loop realization is based on the RAN network elements - GNBCUCPFunction .

Overview


Prerequisites:

  1. Configuration of E2E network slices  (~ 5 slices)
  2. RAN Simulator, VES Collector, PM Mapper, Data File Collector, Slice Analysis MS, ML Prediction MS, SO, Policy, SDNR, Config DB components should be up and running
  3. SFTP setup to store the PM messages from RAN Simulator
  4. Manual configurations are detailed at Closed Loop for Network Slicing


Functionality of ML block is divided into three two parts. 

  1. Model Training (Offline) and validation
  2. Prediction

...

  • The training modules trigger PM data generation for slices using the below RAN Simulator API topics
  • The process typically waits for more data to be generated. Currently it waits for 2 hours.

...

  • After the time elapse, the training modules perform stop PM data generated for slices using following topicAPI.
Code Block
curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i
  • The Training module start to get the acquired data for all the slices and cells using PM Mapper topic
Code Block
curl -X POST -H "Content-Type:  text/plain" https://localhost:8081/events/org.onap.dmaap.mr.PERFORMANCE_MEASUREMENTS/mlms-cg/mlms-cid
  • While acquiring each slice and cell data, the training module also acquire the intent configuration for each cell and slices. using following topic. using following Config DB API. Config DB will be replaced by CPS in the next release.
Code Block
curl -X POST -H "Content-Type:  text/plain" https://localhost:8081/api/sdnc-config-db/v4/nrcellcu-configdata/1/snssai/01-B989BD

...

is performed by first by acquiring the current time instance data from slices and cells. The data are acquired from following topicsAPIs.

  • The Prediction modules trigger PM data generation for slices using the below RAN Simulator API topics
  • The process typically waits for more data to be generated. Currently it waits for 2 hours.

...

  • After the time elapse, the Prediction modules perform stop PM data generated for slices using following topicAPI.
Code Block
curl -X POST -H "Content-Type:  text/plain" http://localhost:8081/ransim/api/stopIntelligentSlicingPmData -i
  • The Prediction module start to get the acquired data for all the slices and cells using the PM Mapper topic
Code Block
curl -X POST -H "Content-Type:  text/plain" https://localhost:8081/events/org.onap.dmaap.mr.PERFORMANCE_MEASUREMENTS/mlms-cg/mlms-cid
  • While acquiring each slice and cell data, the Prediction module also acquire the intent configuration for each cell and slices. using following topicConfig DB API. Config DB will be replaced by CPS in the next release.
Code Block
curl -X POST -H "Content-Type:  text/plain" https://localhost:8081/api/sdnc-config-db/v4/nrcellcu-configdata/1/snssai/01-B989BD

...

Expand
titleRecommendation format

{
    "snssai": "0001-0111",
    "data": [{
        "gNBCUName": "cucpName",
        "nearRTRICId": "NearRTRIC1",
        "cellCUList": [{
            "cellLocalId": 111,
            "configData": {
                "maxNumberofConns": "20",
                "predictedMaxNumberofConns": "25",
                "lastUpdatedTS": "yyyy/MM/dd HH:mm:ss"
            }
        }, {
            "cellLocalId": 112,
            "configData": {
                "maxNumberofConns": "20",
                "predictedMaxNumberofConns": "25",
                "lastUpdatedTS": "yyyy/MM/dd HH:mm:ss"
            }
        }]
    }, {
        "gNBCUName": "cucpName2",
        "nearRTRICId": "NearRTRIC2",
        "cellCUList": [{
            "cellLocalId": 113,
            "configData": {
                "maxNumberofConns": "20",
                "predictedMaxNumberofConns": "25",
                "lastUpdatedTS": "yyyy/MM/dd HH:mm:ss"
            }
        }, {
            "cellLocalId": 114,
            "configData": {
                "maxNumberofConns": "20",
                "predictedMaxNumberofConns": "25",
                "lastUpdatedTS": "yyyy/MM/dd HH:mm:ss"
            }
        }]
    }]
}


CPS API:

The Once the CPS integration for RAN slice allocation is completeddone in J-release, Config DB API needs to will be replaced with the CPS API .

CPS API:

To be updatedin the next release.