Open APIs

Hello,

we plan to use the API for commercial and technical feasibility of product offerings. According to TMF 679, the qualification response contains items referring to product offerings from the catalog. Lets assume we have the following catalog model:

ProductOffering "DSL"
L ProductOffering "Internet"
  L ProductSpecification "Internet"
    L Characteristic "Bandwidth" with possible values {50 MBit, 100 MBit}
L ...​

Lets assume we want to check the eligibility for the ProductOffering "DSL" at address "Example Street 123", we make the following request:

ProductOfferingQualification
L Place "Example Street 123"
L ProductOfferingQualificationItem (action = add)
  L ProductOfferingRef -> ProductOffering "DSL"

In the case that only 50 MBit at the address would be feasible, how can we restrict the ProductOffering "DSL" in the response, that only the value 50 MBit is choosable for Characteristic "Bandwidth"?

Best regards

Hello Sebastian,

You could leverage the capability to perform a request at productSpecification level (using ProductRefOrValue class). In this case in the request or/and in the response you could describe characteristic value.

Hope it helps,

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Hello Ludovic,

thanks for your reply. I can imagine to use the ProductRefOrValue association for qualification requests for new offerings (action = add), because than there is no existing one.
But how should this look like for change offerings? In such cases, I would assume that the ProductRefOrValue association refers to the product instance to modify.


Best regards
Original Message:
Sent: Feb 17, 2020 03:22
From: Ludovic Robert
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Sebastian,

You could leverage the capability to perform a request at productSpecification level (using ProductRefOrValue class). In this case in the request or/and in the response you could describe characteristic value.

Hope it helps,

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Hello Sebastian

From my perspective you could also leverage the ProductRefOrValue to described the 'targeted' value to be qualified for an existing product.

for example:

{
    "description": "string",
    "instantSyncQualification": true,
    "provideAlternative": false,
    "provideOnlyAvailable": false,
    "provideUnavailabilityReason": false,
    "requestedPOQCompletionDate": "2020-02-18T08:08:54.544Z",
    "productOfferingQualificationItem": [
      {
        "id": "1",
        "expectedActivationDate": "2020-02-18T08:08:54.544Z",
        "action": "change",
        "product": {
          "id": "456-yt6-ii8-oi5",
          "productCharacteristic": [
            {
              "name": "Data volume",
              "valueType": "string",
              "value": "50"
            }
          ],​

in this case, for existing product456-yt6-ii8-oi5 you ask for a qualification to change Data volume characteristic to 50 (assuming that in the inventory you have another value). The product construction here allow you to describe target and not existing.

Hope it helps

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------

Original Message:
Sent: Feb 17, 2020 06:32
From: Sebastian Gebhardt
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Ludovic,

thanks for your reply. I can imagine to use the ProductRefOrValue association for qualification requests for new offerings (action = add), because than there is no existing one.
But how should this look like for change offerings? In such cases, I would assume that the ProductRefOrValue association refers to the product instance to modify.


Best regards

Original Message:
Sent: Feb 17, 2020 03:22
From: Ludovic Robert
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Sebastian,

You could leverage the capability to perform a request at productSpecification level (using ProductRefOrValue class). In this case in the request or/and in the response you could describe characteristic value.

Hope it helps,

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF

Hello Ludovic,

your answers help me a lot. Thanks


Regards
Sebastian
Original Message:
Sent: Feb 18, 2020 03:23
From: Ludovic Robert
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Sebastian

From my perspective you could also leverage the ProductRefOrValue to described the 'targeted' value to be qualified for an existing product.

for example:

{    "description": "string",    "instantSyncQualification": true,    "provideAlternative": false,    "provideOnlyAvailable": false,    "provideUnavailabilityReason": false,    "requestedPOQCompletionDate": "2020-02-18T08:08:54.544Z",    "productOfferingQualificationItem": [      {        "id": "1",        "expectedActivationDate": "2020-02-18T08:08:54.544Z",        "action": "change",        "product": {          "id": "456-yt6-ii8-oi5",          "productCharacteristic": [            {              "name": "Data volume",              "valueType": "string",              "value": "50"            }          ],​

in this case, for existing product456-yt6-ii8-oi5 you ask for a qualification to change Data volume characteristic to 50 (assuming that in the inventory you have another value). The product construction here allow you to describe target and not existing.

Hope it helps

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------


Original Message:
Sent: Feb 17, 2020 06:32
From: Sebastian Gebhardt
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Ludovic,

thanks for your reply. I can imagine to use the ProductRefOrValue association for qualification requests for new offerings (action = add), because than there is no existing one.
But how should this look like for change offerings? In such cases, I would assume that the ProductRefOrValue association refers to the product instance to modify.


Best regards

Original Message:
Sent: Feb 17, 2020 03:22
From: Ludovic Robert
Subject: TMF 679 - Product Offering Qualification - Restricting parts of a product offerings

Hello Sebastian,

You could leverage the capability to perform a request at productSpecification level (using ProductRefOrValue class). In this case in the request or/and in the response you could describe characteristic value.

Hope it helps,

Ludovic

------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF