Open APIs

Expand all | Collapse all

TMF639 Resource Inventory specification in IG1217 Resource Inventory of 3GPP NRM for Service Assurance

  • 1.  TMF639 Resource Inventory specification in IG1217 Resource Inventory of 3GPP NRM for Service Assurance

    Posted 24 days ago
    Edited by Marlon Almazan 24 days ago
    Im trying to find some examples of proper devices connection description using TMF639 specification and came across some incomprehensible place in IG1217 document. There in Resource json used fields "connectionPoint" and "connectivity"  that not discribed in TMF639 specification (thouse json in the end of post).
    Can someone explain, why this fields came from TMF664 and may be direct to examples of some device connectity using TMF spec. combination

    {
    "id": "f9f6e895-cae2-49bf-8883-844d1173aaee",
    "href": "/resourceInventoryManagement/v4/resource/f9f6e895-cae2-49bf-8883-844d1173aaee",
    "@type": "ResourceFunction",
    "name": "DC=example.net,SubNetwork=4,ManagedElement=1",
    ...
    "resourceCharacteristic": [...],
    "resourceRelationship": [...],
    "connectionPoint": [
    {
    "id": "a0fb2b1c-9a26-4337-aaea-c2e09e4d1a51",
    "href": "/resourceInventory/resource/a0fb2b1c-9a26-4337-aaeac2e09e4d1a51",
    "@type": "ConnectionPointRef",
    "@referredType": "ResourceFunction",
    "name": "DC=example.net,SubNetwork=4,ManagedElement=1,MMEFunction=1,EP_RP_EPS=1"
    }
    ...
    ],
    "connectivity": [
    {
    "id": "5921a308-322c-40fe-80e8-c2a7bc0ba546",
    "name": "Internal Adjacency Graph",
    "@type": "ResourceGraph",
    "connection": [
    {
    "associationType": "pointtoPoint",
    "@type": "Connection",
    "endpoint": [
    ...
    {
    "id": "a19a85e5-b128-49d5-8c39-ac314d53386a",
    "href": "/resourceInventory/resource/a19a85e5-b128-49d5-8c39-ac314d53386a",
    "@type": "EndpointRef",
    "@referredType": "ResourceFunction",
    "name": "DC=example.net,SubNetwork=4,ManagedElement=1,MMEFunction=1",
    "isRoot": true,
    "connectionPoint": {
    "id": "a0fb2b1c-9a26-4337-aaea-c2e09e4d1a51",
    "href": "/resourceInventory/v4/resource/a0fb2b1c-9a26-4337-aaea-c2e09e4d1a51",
    "@type": "ConnectionPointRef",
    "@referredType": "ResourceFunction",
    "name": "DC=example.net,SubNetwork=4,ManagedElement=1,MMEFunction=1,EP_RP_EPS=1"
    }
    },
    {
    "id": "a9a14a94-7606-4ce3-b045-a2642972e107",
    "href": "/resourceInventory/resource/a9a14a94-7606-4ce3-b045-a2642972e107",
    "@referredType": "ResourceFunction",
    "@type": "EndpointRef",
    "name": "DC=example.net,SubNetwork=4,Link_HSS_MME=1",
    "isRoot": true
    }
    ]
    }
    ]
    }
    ]
    }
     


    ------------------------------
    alexander adamov
    OJSC "Megafon"
    ------------------------------


  • 2.  RE: TMF639 Resource Inventory specification in IG1217 Resource Inventory of 3GPP NRM for Service Assurance

    TM Forum Member
    Posted 23 days ago
    Alexander,

    TMF664 Resource Function Activation and Configuration API introduces a subclass of LogicalResource for representing "functions": ResourceFunctionTR255 describes resource functions as a generalization of (network) elements which takes input(s) and/or produce output(s) which may be used to model VNF, PNF, flows, service chains, etc.. The schema for ResourceFunction adds attributes to describe the external connections points and internal connectivity topology .

    The TMF664 API provides the Activation pattern. Most APIs fall into one of the patterns of Catalog, Inventory, Activation and Order.  All of the APIs within a domain use the same data model for their resources and should work together.  We manage ResourceFunctionSpecifications using TMF634 Catalog Management API and once instantiated with TMF664 a ResourceFunction  instance may be available in an inventory managed with TMF639.


    ------------------------------
    Vance Shipley
    SigScale
    ------------------------------