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!

//NRCellDU[ ? ]

Proposed cps query

, 2 step approach (inside CPS Core):

1. Retrieve all unique

1. NRCellDU list entries based on xpath

1. postfix and attribute key and value. Options:

1. 1. /cps-ran-schema/NearRTRIC[?]/GNBDUFunction[?]/NRCellDU[@nRTAC=310]
      

1. 1. i.e. Match full xpath with wildcard for each list-ancestor list key
      Hard to implement, more model knowledge needed
   2. //NRCellDU[@nRTAC=310]
      

1. 1. i.e. xpath ends with NRCellDU[?] and attributes contain nRTAC=310
      

1. 1. 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]

1. 1. 
      Less flexible, less readable
   2. //book[@name="Chapters"]/ancestor::

1. 1. bookstore 
      

1. 1. /

1. 1. /NRCellDU[@nRTAC=310]/ancestor::NearRTRIC
      The preferred option, enough information an unambiguous enough to correctly resolve the query for this API call

<Ahila> Please note the below:

1. Fetch the List of Cells using API #2
2. Fetch the parents and grandparents pertaining to those cells

Fetch the DU functions for sNSSAI

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

Query - get ancestor GNBDUFunctionbased on the sNSSAI. 

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

NOTE - sNssai is the key

For team review

Possible same solution as #1.

Fetch DU Cells for sNSSAI

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.

Fetch NearRTRIC configuration for a sNSSAI

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

NOTE - sNssai is the key

For team review

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

//ranNFNSSIIdList[@RANNFNSSI =1]/ancestor::NearRTRICs

NOTE Model has changed, ranNFNSSIIdList representation now is a leaf-list, thus new type of query is needed 'leaf-list contains a given value'
Here are 2 possible options:

1. //attributes/ranNFNSSIIdList/element[normalize-space(text())= "ac8ca1a9-e1ec-4480-8720-c74e92566885"]/ancestor::NearRTRIC
2. //attributes/ranNFNSSIIdList/element[text()="ac8ca1a9-e1ec-4480-8720-c74e92566885"]/ancestor::

1. NearRTRIC

For team review

Possible same solution as #1.

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.

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

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?

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

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

The questions are as follows

1. When inserting a value that already exists into a list do we reject it or replace it without warning? - <Ahila> It can be rejected.
2. For API number 4, 5 and 6, when this API is called does it create a new entry or does it update an existing entry? <Ahila> - Create a new entry, if it does not exists. Update, if it already exists.
3. Could you confirm the exact list you are referring to for API number 7? <Ahila> - The comment was updated by Toine. He is referring to the list below. The expected behaviour here is that update to the parent and the child list.

+--rw rRMPolicyMemberList* [idx]

        |        |  +--rw idx       uint32

        |        |  +--rw mcc       Mcc

        |        |  +--rw mnc       Mnc

        |        |  +--rw sNSSAI?   SNssai