Versions Compared

Old Version 12

changes.mady.by.user Niamh Core

Saved on

compared with

New Version 13

changes.mady.by.user Niamh Core

Saved on

Key

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

Analyse Analyze all API GET calls listed on this page: https://wiki.onap.org/display/DW/CPS+APIs

...

  • Ensure use case is clear using given model and data example
  • Find out required (new) query functionality in CPS (several API call calls might need the same CPS functionality)to 'find' the required data given the provided parameters (request payload) and model.
  • One (Slicing) API call might require more then than one CPS-Core call, indicate in the report if this is the case
    • One API call might need to access more then than one model (report!)
  • Distinguish between NCMP (ran network data) and CPS-Core access for NW Slicing specific data.

A/C

  1. Wiki Page with the conclusion for each API call
  2. Add new query functionality if needed to  https://wiki.onap.org/display/DW/CPS-235%3A+Overview+of+%28early%29+CPS+Query+and+Update+Scenarios
  3. Review with the full team


To be noted: Dataspace name is fixed to NFP-Operational.

...

xpath/[leafName=leafValue]

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.This is applicable to other APIs on 2, 9, 10, 12, 20, and 21.

2./api/sdnc-config-db/v4/cell-list/{trackingArea}GETGet a list of cells that correspond to a specific tracking area
Mentioned in comments of #1Done
9./api/sdnc-config-db/v4/du-list/{sNSSAI}GETFetch the DU functions for sNSSAI

9,10 and 12 belong to the cps ran schema model

  • All have the same input but expect a different output. 
  • Will we know the sNSSAI value? Is the data incomplete?
  • Use the xpath ends with cps query
Mentioned in comments of #1Needs clarification from the network slicing team
10./api/sdnc-config-db/v4/du-cell-list/{sNSSAI}GETFetch DU Cells for sNSSAIMentioned in comments of #1
Needs clarification from the network slicing team
11./api/sdnc-config-db/v4/profile-config/{sNSSAI}GETFetch slice profile configuration for a sNSSAI
Ignore this API
12./api/sdnc-config-db/v4/slice-config/{sNSSAI}GETFetch NearRTRIC configuration for a sNSSAIMentioned
in comments of #1Needs clarification from the network slicing team
13./api/sdnc-config-db/v4/subscriber-details/{sNSSAI}GETFetch subscriber details
Ignore this API
19.api/sdnc-config-db/v4/nearrtric/{ranNFNSSIId}GETFetches the NearRTRICs for the RANNFNSSI

The RANNFNSSI is stored within the ranNFNSSIIdList.

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}GETReturns PLMN id for the sliceProfile
The ran inventory model was used for this study.
We need the following query; based on the sliceProfileId key we will get the sibling that is a pLMIDList.
Mentioned in comments of #1For team review
21.

/api/sdnc-config-db/v4/ta-list/{mcc}/{mnc}/{coverageArea}

/api/sdnc-config-db/v4/ta-list/{PLMNId}/{coverageArea}

GETReturns List of a tracking area (coverageAreaTAList) of the specified coverage areaMentioned in comments of #1
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
cps-ran-schema/NRCellDU/attributes/RRMPolicyRatio/attributes/rRMPolicyMemberList/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.