...
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CPS-200 |
---|
|
Models and data
There was an issue with the original json data provided. We corrected this issue by modifying the root element.
cps-ran-inventory.yang-data-incorrect.json (original)
cps-ran-inventory-data.json (corrected)
cps-ran-inventory.yang
Queries used for the RAN inventory model
API Path | Description of Operation |
---|
GET /ran-inventory/sliceProfilesList/{sNSSAI} | Find a slice profile list that has the given sNSSAI value |
For the model provided above it will return:
groupingSliceProfileleaf sliceProfileId{
type string mandatory true;
description "slice profile id";
}leaf sNSSAI{
type string;
mandatory false;
description "The S-NSSAI may include both the SST and SD fields (in which case the S-NSSAI length is 32 bits in total), or the S-NSSAI may just include the SST field (in which case the S-NSSAI length is 8 bits only)";
}
leaf maxNumberofUEs{
type int64 { range "0..68719476735"; }
mandatory false;
description "maximum number of UEs";
}
leaf latency{
type int64 { range "0..68719476735"; }
mandatory false;
description "latency of the slice requested by the operator";
}
leaf uLThptPerSlice{
type int64 { range "0..68719476735"; }
mandatory false;
description "uplink throughput of the slice requested by the operator";
}
leaf dLThptPerSlice{
type int64 { range "0..68719476735"; }
mandatory false;
description "downlink throughput of the slice requested by the operatordescription "List of slice profiles supported by the ran slice";
|
|
leaf maxNumberofConns{
type int64 { range "0..68719476735"; }
mandatory false;
description "maximum number of connections to be served by the slice";
}
leaf uEMobilityLevel{
type string;
mandatory false;
description "Mobility level of the UE";
}
leaf resourceSharingLevel{
type string;
description "Resource sharing level";
}
- use query of cpsPath starting with given path (maybe even add '[') - '/ran-inventory/sliceProfilesList[@sliceProfileId=\'f33a9dd8-ae51-4acf-8073-c9390c25f6f1\']
- use json-query tools to only get the 'fragment' that contain required name-value pair
(probably need native-query annotation)
|
PUT /ran-inventory/{rannfnssiid}/sliceProfilesList/ | Add/update the given slice profile for the given rannfnssi |
Groovy Test - E2E Coverage Area-Tracking Area & TA-Cell mapping data can be parsed for RAN inventory
...