...
Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-1992 - 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
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 | ||
| 2 | Registration need to indicate whether DMI supports 3GPP southbound interface! |
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.