Analyze all API GET calls listed on this page: https://wiki.onap.org/display/DW/CPS+APIs
...
No | API endpoint | HTTP Method | Description | CPS Path Query | Comments |
|---|---|---|---|---|---|
| 1. | /api/sdnc-config-db/v4/nearrtric-list/{trackingArea} | GET | Get complete details associated with a list of NearRT RIC's and corresponding managed elements | xpath : /cps-ran-schema/NearRTRIC[@idNearRTRIC="22"]/GNBDUFunction[@idGNBDUFunction="6"]/NRCellDU[@idNRCellDU="15548"]/ attributes : {"nRPCI": 12, "nRTAC": 310, "cellLocalId": 15548} Proposed cps query; Retrieve all unique list based on xpath prefix and attribute key and value /cps-ran-schema//{"nRTAC":310} | e.g. /dataspace/"NFP-Operational"/anchor/"ran-slicing" From our discussion with Ruslan Kashapov and Niamh Core, we came to an understanding that we would require a special query mechanism that can retrieve the parent from its attribute values. |
| 2. | /api/sdnc-config-db/v4/cell-list/{trackingArea} | GET | Get a list of cells that correspond to a specific tracking area | Done | |
| 9. | /api/sdnc-config-db/v4/du-list/{sNSSAI} | GET | Fetch the DU functions for sNSSAI | cps-ran-schema/NearRTRIC/GNBDUFunction/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNssai Query - get ancestor GNBDUFunctionbased on the sNSSAI. 9,10 and 12 belong to the cps ran schema model All have the same input but expect a different output. | Needs clarification from the network slicing team |
| 10. | /api/sdnc-config-db/v4/du-cell-list/{sNSSAI} | GET | Fetch DU Cells for sNSSAI | cps-ran-schema/NearRTRIC/GNBDUFunction/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNssai Query - get ancestor NRCellDU based on the sNSSAI. | Needs clarification from the network slicing team |
| 11. | /api/sdnc-config-db/v4/profile-config/{sNSSAI} | GET | Fetch slice profile configuration for a sNSSAI | Ignore this API | |
| 12. | /api/sdnc-config-db/v4/slice-config/{sNSSAI} | GET | Fetch NearRTRIC configuration for a sNSSAI | cps-ran-schema/NearRTRIC/attributes/pLMNInfoList/sNSSAIList/sNssai Query - get a sibling value based on the given sNSSAI. Get the sibling configData of sNSSAI from the sNSSAIList. | Needs clarification from the network slicing team |
| 13. | /api/sdnc-config-db/v4/subscriber-details/{sNSSAI} | GET | Fetch subscriber details | Ignore this API | |
| 19. | api/sdnc-config-db/v4/nearrtric/{ranNFNSSIId} | GET | Fetches the NearRTRICs for the RANNFNSSI | The RANNFNSSI is stored within the ranNFNSSIIdList. Query - We need a query that will get the immediate parent (NearRTRICs) based on attribute values from the list of ranNFNSSIIdList (child). | For team review |
| 20. | /api/sdnc-config-db/v4/plmn/{sliceProfileId} | GET | Returns PLMN id for the sliceProfile | The ran inventory model was used for this study. | For team review |
| 21. | /api/sdnc-config-db/v4/ta-list/{mcc}/{mnc}/{coverageArea} /api/sdnc-config-db/v4/ta-list/{PLMNId}/{coverageArea} | GET | Returns List of a tracking area (coverageAreaTAList) of the specified coverage area | Done |
| Question | Comment | |
|---|---|---|
| 1 | API 9 & 10: There are multiple placeholders for it in the same ancestor of DU, RTRIC, CUUP and CUCP NFs. For DU-list we have identified: cps-ran-schema/GNBDUFunction/attributes/RRMPolicyRatio/attributes/sNSSAI For the DU list, we can also use the sNSSAI from cell-list which comes under DU. For cell-list we have identified: cps-ran-schema/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNSSAI Would you please guide us as to what would be the right attributes to be considered in the search for these GET APIs? | |
| 2 | API 12: We did not identify the slice config attribute for API#12 to be mapped in the Network Slicing. Kindly provide us with the right model and data. |