Page Comparison

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

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

Possible same solution as #1.

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

Possible same solution as #1.

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]/ (include children)

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

Needs clarification from the network slicing team

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

Possible same solution as #1.

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]

//SliceProfileListsliceProfilesList[@sliceProfileId=1] include descendants (pLMIDList is descendant)