Open APIs

 View Only
  • 1.  How is ServiceAccessPoint (SAP) represented in the openAPI structure?

    TM Forum Member
    Posted Dec 16, 2022 10:46
    Hi,

    We are in the middle of a CRM transformation program at Magyar Telekom based significantly on the SID and openAPI model defined by TMForum.
    In our business processes, we use a ServiceAccessPoint that defines all services that the customer can accessed on a particular phisical or virtual place. The service point as an object has importancy also from the point of view of fault handling to identify all servivices that are provided on the same service point.
    While the SID discusses the relation between Service, ServiceAccessPoint and Resource, I can see any reference to SAP neither in ServiceInventoryManagement (TMF638) nor ResourceInventoryManagement (TMF639) API user guides.
    Could you give us a guideline how shold be depicted the SAP in the Service and/or Resource related openAPIs?

    Regard
    @Tibor Ujszászi

    ------------------------------
    Tibor Ujszászi
    Magyar Telekom Plc.
    ------------------------------


  • 2.  RE: How is ServiceAccessPoint (SAP) represented in the openAPI structure?

    TM Forum Member
    Posted Dec 18, 2022 07:19
    Hi Tibor
    Service Access Point is referenced indirectly in Resource Function API (TMF664), as ConnectionPoint, but the ConnectionPoint entity itself does not have an API that manages it.
    One could also argue that, at least for physical access, a geographicaddress serves the purpose.

    @Vance Shipley might want to relate to this in more detail.

    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: How is ServiceAccessPoint (SAP) represented in the openAPI structure?

    TM Forum Member
    Posted Dec 18, 2022 08:34
    Edited by Vance Shipley Dec 18, 2022 08:34
    Jonathan,

    While the type of the connectionPoint attribute value, of ResourceFunction, is a ConnectionPointRef, which is simply an EntityRef, the expectation is that it is actually another ResourceFunction, and so manageable with TMF664, TMF639, etc..

    One could argue that this is just a resourceRelationship however connectionPoint is a critical part of the concept of ResourceFunction which warrants first class treatment.

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



  • 4.  RE: How is ServiceAccessPoint (SAP) represented in the openAPI structure?

    TM Forum Member
    Posted Dec 18, 2022 08:20
    GB922 does describe class ServiceAccessPoint (and SapSpecification) within the TIP Service Management ABE of the Service Domain.
    Represents a set of parameters associated (directly or indirectly) with a unique (logical and/or physical) resource where the Service can be accessed.
    Note that this allows you to describe within the Service Domain the SAP which exists as an entity of the Resource Domain.  You may not need this level of sophistication.

    Using the Service Inventory API (TMF638) when you describe an Resource Facing Service (RFS) you should populate the supportingResource attribute with a reference to one or more entities in the Resource Domain which provides the bridge between domains and would be your SAP.

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