...
Interface | Requirement | Additional Information | Signoff | ||
---|---|---|---|---|---|
1 | New southbound 3GPP interface on DMI | By default NCMP shall support DMI API on its southbound interface towards the DMI plugins for CH and 3GPP Northbound APIs | Toine Siebelink | ||
2 | DMI plugins shall be able to indicate that they support 3GPP API. | implementation suggestion: no need to parse request/response bodies, they can be handled simply as InputStreams. | |||
3 | DMI plugins shall be able to indicate if they want the dataProducerId to be inserted by NCMP into the FDN as the first DC component when a request comes on the 3GPP Northbound API. | ||||
4 | If a DMI plugin indicated that the dataProducerId needs to be inserted into the FDN then the dataProducerId must be supplied when creating a CMHandle. | ||||
5 | Shall support New conflict management interface - PolicyExecution | CPS-2249: NCMP To support Conflict Handling using External Service - Developer Wiki - Confluence (onap.org) Kolawole Adebisi-Adeolokun Registration need to indicate whether DMI supports 3GPP southbound interface! |
Error Scenarios
Error Scenario | Expected behavior | Sign-off | |
---|---|---|---|
1 |
...
There is a requirement that NCMP should support 3GPP 28.532 API. The current plan is that NCMP accepts requests on this API and forward it to DMI plugins using the DMI API. However this is a wasteful approach if the Southbound system supports 3GPP 28.532. It would be more efficient if NCMP could simply forward the requests as-is for such DMI plugins.
Proposal
Add two new fields for creating new cmhandles and updating existing ones:
Name | Description | Type | Mandatory | |
---|---|---|---|---|
1 | support3GPP28532 | DMI plugin indicates that it supports 3GPP 28.532 | boolean | No |
2 | appendDataProducer | DMI plugin indicates that it needs the dataProducerId added to the FDN as DC. Only applicable for the 3GPP API. | boolean | No |
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
POST [https://%3ceic-domain%3e/ncmpInventory/v1/ch]https://<eic-domain>/ncmpInventory/v1/ch
{
"dmiDataPlugin": https://eric-eo-enm-adapter,
"dmiModelPlugin": https://eric-oss-enm-model-adapter,
"createdCmHandles": [{
"cmHandle": "123456789",
"cmHandleProperties": {
"subSystem":"2",
"targetDnPrefix":"SubNetwork=Europe",
"targetNode":"ManagedElement=LTE01dg2ERBS00001",
"nodeModelIdentity":"22.Q1-R48A08",
"ossModelIdentity":"22.Q1-R48A08",
"softwareSyncStatus":"AS_IS",
"neType": "RadioNode",
},
"publicCmHandleProperties" : {
"emsId" : "2"
},
"dataProducerId" : "2",
"alternateId" : "/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001",
"support3GPP28532" : true,
"appendDataProducer" : true
}]
} |
Read request coming on the NCMP 3GPP 28.532 API:
GET [https://%3ceic-domain%3e/ProvMnS/v1/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001?scopeType=BASE_ONLY]
https://<eic-domain>/ProvMnS/v1/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001?scopeType=BASE_ONLY
Forwarded request to DMI plugin (ENM Adaper):
Forwarded request to ENM:
GET [https://%3ccustomer-domain%3e/enm-nbi/cm/v1/data/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001?scopeType=BASE_ONLY]https://<customer-domain>/enm-nbi/cm/v1/data/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001?scopeType=BASE_ONLY