Versions Compared

Key

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

Jira Ref. 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-277

...

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}

Note. nRTAC is not the key!

Proposed cps query, 2 step approach (inside CPS Core):

  1. Retrieve all unique RCellDU list entries NRCellDU list entries based on xpath postfix and attribute key and value. Options:
    1. /cps-ran-schema/NearRTRIC[?]/GNBDUFunction[?]/NRCellDU[@nRTAC=310]
      i.e. Match full xpath with wildcard for each list-ancestor list key
      Hard to implement, more model knowledge needed
    2. //NRCellDU[@nRTAC=310]
      i.e. xpath ends with NRCellDU[?] and attributes contain nRTAC=310
      Already have similar? existing code for this in: FragmentRepository.getByAnchorAndXpathAndLeafAttributes()

  2.  Retrieve unique NearRTRIC ancestors (using bookstore generic examples)
    1. //book[@name="Feersum Endjinn"]/ancestor::*[position()=3]
      Less flexible, less readable
    2. //book[@name="Chapters"]/ancestor::bookstore 
      //NRCellDU[@nRTAC=310]/ancestor::NearRTRIC
      Preferred option, enough information an unambiguous enough to correctly resolve query for tis API call

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}GETGet a list of cells that correspond to a specific tracking area
Done
9./api/sdnc-config-db/v4/du-list/{sNSSAI}GETFetch 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

//sNSSAIList[@sNssai=1]/ancestor::GNBDUFunction

Needs clarification from the network slicing team
10./api/sdnc-config-db/v4/du-cell-list/{sNSSAI}GETFetch DU Cells for sNSSAI

cps-ran-schema/NearRTRIC/GNBDUFunction/NRCellDU/attributes/pLMNInfoList/sNSSAIList/sNssai

Query - get ancestor NRCellDU based on the sNSSAI.

//sNSSAIList[@sNssai=1]/ancestor::NRCellDU

Needs clarification from the network slicing team
11./api/sdnc-config-db/v4/profile-config/{sNSSAI}GETFetch slice profile configuration for a sNSSAINot NeededIgnore this API
12./api/sdnc-config-db/v4/slice-config/{sNSSAI}GETFetch 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.


//sNSSAIList[@sNssai=1]


This will use API 2 CPS-235: Overview of (early) CPS Query and Update Scenarios

Needs 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.

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
20./api/sdnc-config-db/v4/plmn/{sliceProfileId}GETReturns PLMN id for the sliceProfile
The ran inventory model was used for this study.
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) leaf value
e.g xpath[sliceProfileId=value]

//SliceProfileList[@sliceProfileId=1]
For 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 area
Done

...