Open APIs

Expand all | Collapse all

TMF 639 Resource Management API

  • 1.  TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 02, 2019 05:03
    In TMF 639 Resource Management API  document , examples for Request and Responses include  'Resource Specification' which maps to  Resource Catalog Management API.

    Snippet from Specification document
    "resourceSpecification": {
    "id": "4",
    "href": " http://server:port/resourceCatalogManagement/resourceSpecification/4"
    }

    Where as in JSON file Definition of resource doesn't have Resource Specification Details.  Please let us know which is appropriate- JSON file or specification document?



    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------


  • 2.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 03, 2019 09:59
    You want the TMF634 Resource Catalog Management API specification.

    ------------------------------
    Vance Shipley
    SigScale Global Inc.
    ------------------------------



  • 3.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 03, 2019 10:00
    Hi,

    I have few more queries for the same specification TMF 639 - Resource Management API

    a. Would like to know which systems implement below dependent specifications of TMF 639
          Party Management (TMF 632)   is it BRM (Billing and Revenue Management) or any other system ?
          Party Role Management (TMF 669)
          Resource Catalog Management ( TMF 634)
          Geographic Address, Geographic Location, Geographic Site APIs(TMF 673, TMF 674, TMF 675)
    b. There are discrepancies in JSON schema file and Specification document . Which one is latest?

    Thanks in Advance

    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------



  • 4.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 05, 2019 04:30
    Hi Rajeswari,
    For your question, which system owns the entities and subsequently implements the APIs, the answer would lie in your Application Architecture.
    Ideally (this may or may not apply to your Architecture), the answers are
    1. Party Management (TMF 632)   - CRM. Billing will have a different flavour but it needs to be mapped to the Party entity in CRMs
    2. Party Role Management (TMF 669) - CRM
    3. Resource Catalog Management ( TMF 634) - Definition of the Resource specs and relationship to the Product Specs in the Enterprise Catalog. The actual resource management happens in other systems based on the Resource type.
    4. Geographic Address, Geographic Location, Geographic Site APIs(TMF 673, TMF 674, TMF 675) - CRM. Against the Customer Account or as separate module like Field Service with a relation to the party role = Customer
    API exposure is easy once you decide this.


    ------------------------------
    Sri Jagadish Baddukonda
    Principal Consultant
    Sigma Systems
    ------------------------------



  • 5.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 09, 2019 07:37
    Thanks Jagadish

    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------



  • 6.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 03, 2019 10:00
    Hi,

    I have few more queries for the same specification TMF 639 - Resource Management API

    a. Would like to know which systems implement below dependent specifications of TMF 639
    Party Management (TMF 632) is it BRM (Billing and Revenue Management) or any other system ?
    Party Role Management (TMF 669)
    Resource Catalog Management ( TMF 634)
    Geographic Address, Geographic Location, Geographic Site APIs(TMF 673, TMF 674, TMF 675)
    b. There are discrepancies in JSON schema file and Specification document . Which one is latest?

    Thanks in Advance

    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------



  • 7.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 03, 2019 10:00
    Hi Rajeswari
    In TMF639, the REST entity that you referred to is ResourceSpecificationRef - this is a reference entity that generally has only a small subset  (id, href, name) of the attributes of the full entity.
    The full entity is described elsewhere, specifically for the Resource domain in the Resource Catalog API TMF634.
    All the published APIs are available at https://projects.tmforum.org/wiki/display/API/Open+API+Table
    Hope it helps


    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------



  • 8.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 04, 2019 06:43
    Thanks Jonathan.

    a. I see there are discrepancies in Swagger file and specification document , which one is latest and what to be considered.
    b. Would like to know which systems implement below dependent specifications of TMF 639
    Party Management (TMF 632) is it BRM (Billing and Revenue Management) or any other system ?
    Party Role Management (TMF 669)
    Resource Catalog Management ( TMF 634)

    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------



  • 9.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 08, 2019 08:42
    Hi
    The Open API team is working to eliminate discrepancies between the specs and the swagger files. This started in the Service-related APIs that were published in R18.5, is going on in a wide range of APIs that will be published in R19, and will continue for R19.5. The Resource APIs are currently planned for refresh in R19.5, although it would be inappropriate to make firm promises.
    Basically consistence is guaranteed going forward by generating the swagger file and the specification document from the same basic assets (json schemas for the entities). The spec documents will have additional hand-crafted narrative sections, but the basic contents of entity description and operations are single-sourced.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------



  • 10.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 08, 2019 08:42
    Hi

    Regarding point a. - please see another recent post I made (at time of writing this my other post is pending approval - this is a monitored forum), where I explained what steps the Open API team is taking to eliminate discrepancies between swagger and spec document going forward.

    Regarding point b. - purely from an Open API perspective there is no prescription of system architecture. The ~60 published APIs could all be implemented by a single monolithic system. Practically, however, we could expect individual APIs to be implemented by more modular fine-grained subsystems, and in modern implementations by individual microservices. I refer you to the TM Forum Open Digital Architecture initiative, which is starting to lay down a functional architecture division for telco applications. @Dave Milham, a lead ODA architect, might be able to provide additional perspective.

    Hope it helps
    ​​

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    ------------------------------



  • 11.  RE: TMF 639 Resource Management API

    TM Forum Member
    Posted Jul 09, 2019 07:37
    Thanks Jonathan.

    ------------------------------
    Rajeswari Kolluri
    Oracle Corporation
    ------------------------------