Jira Ref.
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
To be noted: Dataspace name is fixed to NFP-Operational.
No | API endpoint |
---|
Model | Description | CPS Path Query Description | Comments and Status | Jira |
---|---|---|---|---|
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 Uses cps ran schema model | xpath : /cps-ran-schema/NearRTRIC[@idNearRTRIC="22"]/GNBDUFunction[@idGNBDUFunction="6"]/NRCellDU[@idNRCellDU="15548"]/ attributes : {"nRPCI": 12, "nRTAC": 310, "cellLocalId": 15548} Note. nRTAC is not the key! Proposed cps query, 2 step approach (inside CPS Core):
|
|
|
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.
For team review |
| ||||||||||
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 Uses cps ran schema model | Path - 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
//sNSSAIList[@sNssai=1]/ancestor::GNBDUFunction |
NOTE - sNssai is the key | For team review Possible same solution as #1. | |||
10. | /api/sdnc-config-db/v4/du-cell-list/{sNSSAI} | GET | Fetch DU Cells for sNSSAI Uses cps ran schema model | Path - cps-ran-schema/NearRTRIC/GNBDUFunction/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNssai Query - get ancestor NRCellDU based on the sNSSAI. //sNSSAIList[@sNssai=1]/ancestor::NRCellDU |
NOTE - sNssai is the key | For team review Possible same solution as #1. | ||
11. | /api/sdnc-config-db/v4/profile-config/{sNSSAI} | GET | Fetch slice profile configuration for |
an sNSSAI | Not Needed | Ignore this API | ||
12. | /api/sdnc-config-db/v4/slice-config/{sNSSAI} | GET | Fetch NearRTRIC configuration for a sNSSAI Uses cps ran schema model | Path - cps-ran-schema/NearRTRIC/attributes/pLMNInfoList/sNSSAIList/sNssai Query - |
Get the sibling configData of sNSSAI from the sNSSAIList. //sNSSAIList[@sNssai=1]/ (include children) This will use query 3 CPS-235: Overview of (early) CPS Query and Update Scenarios |
NOTE - sNssai is the key | For team review |
| ||||||||||
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 |
Uses cps ran schema model | Query - We need a query that will get the immediate parent (NearRTRICs) based on attribute values from the list of ranNFNSSIIdList (child). |
We may need to add a new cps query CPS-235: Overview of (early) CPS Query and Update Scenarios to
get a parent value based on the ranNFNSSIId value
//ranNFNSSIIdList[@RANNFNSSI =1]/ancestor::NearRTRICs | For team review Possible same solution as #1. | ||
20. | /api/sdnc-config-db/v4/plmn/{sliceProfileId} | GET | Returns PLMN id for the sliceProfile |
Uses cps ran |
inventory |
model |
Query - We need the following query; based on the sliceProfileId key we will get the sibling that is a pLMIDList |
This will use API 2 CPS-235: Overview of (early) CPS Query and Update Scenarios
Filter list element by other (then key)
e
. |
| 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? | From: ahila.pandaram@wipro.com <ahila.pandaram@wipro.com> As per the current SDN-R implementation, sNSSAI is configured in NRCellDU, NRCellCU & gNBCUUP. NearRTRIC is configured only in closed loop scenarios. So please make use of this for the APIs (9) & (10). cps-ran-schema/GNBDUFunction/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNssai |
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. | From: ahila.pandaram@wipro.com <ahila.pandaram@wipro.com> API (12) can make use of this: cps-ran-schema/NearRTRIC/attributes/pLMNInfoList/sNSSAIList/sNssai |
...