Versions Compared

Key

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

...

Addresses: 

Jira Legacy
serverONAP JIRASystem Jira
serverId425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176
keyCPS-222

Investigation into (long and short term) feasibility options for CPS Dta updates.

Some possibilities like:

  1. Setting a single attribute (value) using a xPath
  2. Update a DataNode (yang fragment) by supplying a new DataNode object with  update data
    1. With children
    2. Ignoring children i.e leaving existing child relations intact
  3. Using the Yang Patch (also used in NetConf?)
  4. Replacing complete instance tree

Options 4 and 1 seem the easiest to implement?!

Option 3 was mentioned by the E2E slicing team but I suspect it to be harder and require a further break down of the Yang-Path ‘language’ features

Out of scope: Validation. The intention is that validation will be handled later using separate study/epic/user stories as required

...

Code Block
titlePATCH
// xPath: /ran-network/NearRTRIC[@idNearRTRIC='11']/GNBDUFunction[@idGNBDUFunction='1']/NRCellDU[@idNRCellDU='103594001']/attributes
{
   "pLMNInfoList": [{
	   "mcc": "310",
       "mnc": "410",
       "sNSSAIList": [{
            "sNssai": "10000100",
            "status": "INACTIVE",
            "configData": [{
                "configParameter": "maxNumberOfConns",
                "configValue": 5000
            }]
        }]
    }]
}

...

Drawio
diagramDisplayName
borderfalse
diagramNameCPS partial data persistence
simpleViewerfalse
width
linksauto
tbstyleinline
lboxfalse
diagramDisplayName
diagramWidth871
revision2

From one hand it seems extra to persist upper level nodes if these nodes are never requested. From other hand it could lead to data inconsistency
if the parent node being added after child nodes (C). The case  however can be resolved by existing data check before inserting new entries.

...