CPS-1992 NCMP to Support new 3GPP sync single FDN request

References

CPS-1992 - Getting issue details... STATUS
https://www.etsi.org/deliver/etsi_ts/128500_128599/128532/16.04.00_60/ts_128532v160400p.pdf
https://www.etsi.org/deliver/etsi_ts/132300_132399/132300/11.02.00_60/ts_132300v110200p.pdf

Assumptions

#	Assumption	Notes
1

Issues & Decisions

#	Issue	Notes	Decision
1	Question: can this interface be delivered as a separate OpenAPI definition?	Kieran Mccarthy A asked if it could be developed separately from NCMP OpenApi definition files

Requirements

Functional

	Requirement	Additional Information
1	By default NCMP shall support DMI API on its southbound interface towards the DMI plugins for CH and 3GPP Northbound APIs	Toine Siebelink I think it is better for backward compatibility that te default behavior is to use the old non-3gpp interface. If think w DO really need this to be the default for ONAP DMI and other non-ericsson DMIs! Actually I now think I misinterpreted your wording. and I think we agree on the required default behavior
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. Toine Siebelink Need some more discussion on Streams, I am not so familiar with this
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	CPS-2249: NCMP To support Conflict Handling using External Service - Developer Wiki - Confluence (onap.org) Kolawole Adebisi-Adeolokun

Error Scenarios

	Error Scenario	Expected behavior	Sign-off
1

Characteristics

	Parameter	Expectation	Notes	Sign-off
1

Out-of-scope

Background

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

Example: register CM Handle with support3GPP28532 is true and appendDataProducer enabled

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

GET https://eric-eo-enm-adapter/ProvMnS/v1/DC=2/SubNetwork=Europe/ManagedElement=LTE01dg2ERBS00001?scopeType=BASE_ONLY

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

Space shortcuts

Page tree