Open APIs

Hi everybody

We are starting implementing TMF APIs. Whilst in many cases this is straight forward, we are struggling with TMF634 (Resource Catalog Management API). We are unsure how to deal with dependencies (eg dependency between routers such as 8202-32FH-M, ASR-9902-FC, ASR-9903-FC, N540-ACC-SYS. The documentation is very open with regards to that. Thus our question: is there anybody with experiences with this API and willing to share a concrete implementation example with us? This we could use as an inspiration and would be greatly appreciated.

Kind regards

Daniel

Is there a dependency "between" routers?  I would think you would want a generic Resource Specification for a router which defines characteristics for information you want to capture about all routers and (maybe) also Resource Specifications for specific routers (e.g. 8202-32FH-M). Each specification for a specific router would have a relationship to the generic specification.

{
     "name": "Router 8202-32FH-M",
     "@type": "ResourceSpecification",
     "resourceSpecRelationship": [
          {
               "name: "Generic Router",
               "@type": "ResourceSpecification",
               "relationshipType": "includes",
               ...
          },
     ...
}

There isn't an enumerated list of values for relationshipType, it's left to the implementor, although I highly recommend that an information architect creates a metamodel for your organization which is used consistently.

As far as implementation examples go, I can offer SigScale's open source implementation of resource catalog and inventory (github.com/sigscale/rim) which includes many examples for 5GC, EPC, IMS, ODA Components, etc..

Hi Vance

Thanks, as we have no experiences we are unsure what is correct and what is not correct. The beginners dilemma. Dependencies could be between a router and its subelements, eg

 NE "Router 8202-32FH-M"

·       card "Line-card XR01"

·       PowerSupply "PowerModule"

and line card may have further dependencies: