Open APIs

Expand all | Collapse all

TMF 633 Service Catalog / Service Specification

  • 1.  TMF 633 Service Catalog / Service Specification

    Posted 18 days ago

    Hi,

     

    We @ Comcast, are trying to align our platform APIs based on TMF and looking at the various specifications (TMF 633 / TMF 640 / TMF 641 etc.) for our business use cases.

    Looking for a sample service specification that is a bundle with multiple service specifications. Specifically, which construct is used to specify that the bundle contains multiple service specifications?

    Primarily, looking at defining catalog of services with service dependency between services and also support the concept of bundle  service specifications that could be used to activate services in the bundle.

     

    Is it it the serviceSpecRelationship or something else? An example would help to understand better.

     

     

    Regards,

    Pattabi Ayyasami

    Comcast



    ------------------------------
    Pattabi Ayyasami
    Comcast Technology Solutions
    ------------------------------


  • 2.  RE: TMF 633 Service Catalog / Service Specification

    TM Forum Member
    Posted 18 days ago
    Hi Pattabi
    To reflect a structured service specification (i.e. a service spec that uses other service specs) you would indeed use serviceSpecRelationship and set relationshipType to bundle or similar.
    The catalog APIs don't have a strongly-typed list of relationship types.
    For the service instance (as embodied in TMF 640, 641, 638), you would use the direct attribute supportingService.
    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: TMF 633 Service Catalog / Service Specification

    Posted 18 days ago
    Thanks, Jonathan for the response.
    In our scenario, we have 2 services Service1 and Service2, and also offer a Bundle (Service1 & Service2). Service2 depends on Service1.
    Our thought process is to have clients activate service instances either using the individual service specifications and/or using the bundle. We don't plan to make use of serviceSpecCharacteristic. Instead, define a JSON schema describing the inputs/characteristics of the service specification.

    Hope I am in the right direction. Please share your thoughts. Following is the snippet.

    Thanks & Regards,
    Pattabi Ayyasami
    Comcast

    ========= Service1 specification ==================
    
    {
      "name": "Service1",
      "displayName": "Service1",
      "category": "Category1",
      "version": "1.0",
      "description": "Service specification for Service 1",
      "isBundle": false,
      "serviceSpecCharacteristic": [ .... ],
      "targetServiceScena": "Reference to a JSON schema"
    }
    
    ========= Service2 specification (Service 2 depends on Service 1) ==================
    
    {
      "name": "Service2",
      "displayName": "Service2",
      "category": "Category2",
      "version": "1.0",
      "description": "Service specification for Service 2",
      "isBundle": false,
      "serviceSpecRelationship": [
        {
          "category": "Category1",
          "name": "Service1",
          "relationshipType": "dependency"      
        }
      ],
      "serviceSpecCharacteristic": [ ... ],
      "targetServiceScena": "Reference to a JSON schema"
    }
    
    ========= Service Bundle =========================
    {
      "name": "ServiceBundle - Service1 and Service2",
      "displayName": "Bundle - Service1 and Service2",
      "category": "Bundle-Category1-Category2",
      "version": "1.0",
      "description": "Service specification bundle for Service1 and Service2 services",
      "isBundle": true,
      "serviceSpecReleationship": [
        {
          "name": "Service1",
          "category": "Category1",
          "relationshipType": "bundle"
        },
        {
          "name": "Service2",
          "category": "Category2",
          "relationshipType": "bundle"
        }
      ]
    }​


    ------------------------------
    Pattabi Ayyasami
    Comcast Technology Solutions
    ------------------------------