Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

(#2 and #21 have already been analyzed and required queries been identified)

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

A/C

  1. Wiki Page with 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 full team


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


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/[leafName=leafValue]

xpath : /cps-ran-schema/NearRTRIC[@idNearRTRIC="22"]/GNBDUFunction[@idGNBDUFunction="6"]/NRCellDU[@idNRCellDU="15548"]/

attributes : {"nRPCI": 12, "nRTAC": 310, "cellLocalId": 15548}

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 #1
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 #1
10./api/sdnc-config-db/v4/du-cell-list/{sNSSAI}GETFetch DU Cells for sNSSAI
Mentioned in comments of #1
11./api/sdnc-config-db/v4/profile-config/{sNSSAI}GETFetch slice profile configuration for a sNSSAI
Ignored
12./api/sdnc-config-db/v4/slice-config/{sNSSAI}GETFetch NearRTRIC configuration for a sNSSAI
Mentioned in comments of #1
13./api/sdnc-config-db/v4/subscriber-details/{sNSSAI}GETFetch subscriber details
Ignored
19.api/sdnc-config-db/v4/nearrtric/{ranNFNSSIId}GETFetches the NearRTRICs for the RANNFNSSI

20./api/sdnc-config-db/v4/plmn/{sliceProfileId}GETReturns PLMN id for the sliceProfile
Mentioned in comments of #1
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 area
Mentioned in comments of #1
  • No labels