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"
------------------------------