Swagger link : SO Swagger

API exposed by NSSMF

Allocate NSSI

MethodURL
POST/onap/so/infra/3gppservices/v1/allocate

Request Example for "networkType"s of "an" or "cn"


Request Example for "networkType"s of "tn"


Response Example

Note :  modelInvariantUuid and modelUuid corresponds to NSST Ids..

Modify NSSI

MethodURL
PUT/onap/so/infra/3gppservices/v1/modify

Request Example for "networkType"s of "an" or "cn"


Request Example for "networkType"s of "tn"


Response Example

Activate NSSI

MethodURL
POST/onap/so/infra/3gppservices/v1/activate

Request Example

Response Example

Deactivate NSSI

MethodURL
POST

/onap/so/infra/3gppservices/v1/deActivate

Request Example

Response Example

Deallocate NSSI

MethodURL
DELETE/onap/so/infra/3gppservices/v1/deAllocate

Request Example

Response Example

Sub-net Capability query

MethodURL
GET/onap/so/infra/3gppservices/v1/subnetCapabilityQuery

Request Example (AN)

Response Example(AN)
Request Example (CN)
Response Example(CN)
Request Example (TN)
Response Example(TN)
Note: Subnet capabilities are stored in a JSON properties file in so-api handler container.

Refer to swagger for allowed enum values.

API consumed by NSSMF

OOF ↔  NSSMF

1.NSSI Selection - OOF

2.NSSI Deallocation - OOF




  • No labels

3 Comments

  1. The Allocate NSSI payload does not seem to have NSST info which is essential.

    The Modify NSSI payload does not seem to have Slice Profile Id.

    Please validate.

  2. Hi Reshmasree c Priyadharshini B ,

    The Activate and De-activate NSSI would also need the S-NSSAI to be activated or de-activated - to be passed as an input in the request body. The NSSMF would need the specific S-NSSAI for which the activate / de-activate operation is being called.

    Also it is assumed that common NSSMF / NSMF workflow shall update the status of S-NSSAI to activated or de-activated as the case may be.

    Could you please confirm / comment on the same.

    Thanks!

  3. Swaminathan Seetharaman Deepika S Zhang Min

    In Allocate NSSI api for Core, we are using
    List of jsonArray for 'endPoints' (as per the request example given in this page)
    "endPoints": [
    {
    "IpAddress": "10.120.1.34",
    "LogicalLinkId": "123456",
    "nextHopInfo": "123456"
    }
    ]
    But it looks like, recently change is done in request payload, for Core and RAN endPoint will be jsonArray instead of list of jsonArray
    "endPoint": {
    "ipAddress": "10.2.3.4",
    "logicInterfaceId": "12",
    "nextHopInfo": "networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.1-ltpId-512"
    }

    Can you please update this wiki page to show changed request(s) payload(s)?