bpp_id and bpp_uri in /on_discover

[aadishjain-pulse]

I was going through the discover response and couldn't find the bpp_id or bpp_uri for the item in the response. We need it in the context for other requests (/select, /init, etc), going to bpp, right?

[TANMOYDADA]

@anandp504

[ameetdesh]

Hi @anandp504 this is the coderef for on_discover. IIUC @aadishjain-pulse is asking where in flow will a BAP receive BPP id, if BAP is supposed to send it for say select call here.

[anandp504]

@aadishjain-pulse The CDS is performing a search across multiple BPP catalogs and returning the response which match the filtering criteria. Since the discover results can be across multiple BPPs, we can't possibly send one BPP_ID and BPP_URI as part of the discover response. We will need a larger discussion on this aspect.

[aadishjain-pulse]

So in the earlier draft that was created, where /search and /on_search were used, for each catalog, there was a context that was present to identify the bpp_id and bpp_uri of the context. Can we do the same here?

[nirmalnr]

@anandp504 @ameetdesh One suggestion is to add it to a catalog in the catalogs array, the bpp_id and bpp_uri to denote theses details for all the items and offers in this catalog object belongs to the said BPP. I believe CDS would have this data from the catalog upload stage.

{
  "context": {
    "version": "2.0.0",
    "action": "on_discover",
    "domain": "beckn.one:deg:ev-charging:*",
    "timestamp": "2024-01-15T10:30:05Z",
    "transaction_id": "2b4d69aa-22e4-4c78-9f56-5a7b9e2b2002",
    "message_id": "a1eabf26-29f5-4a01-9d4e-4c5c9d1a3d02",
    "bap_id": "app.example.com",
    "bap_uri": "https://app.example.com/bap",
    "ttl": "PT30S"
  },
  "message": {
    "catalogs": [
      {
        "@context": "https://raw.githubusercontent.com/beckn/protocol-specifications-new/refs/heads/draft/schema/core/v2/context.jsonld",
        "@type": "beckn:Catalog",
        "beckn:bpp_id": "ev-charging-bpp.example.com",
        "beckn:bpp_uri": "https://ev-charging-bpp.example.com/bpp",
        "beckn:descriptor": {
          "@type": "beckn:Descriptor",
          "schema:name": "EV Charging Services Network",
          "beckn:shortDesc": "Comprehensive network of fast charging stations across Bengaluru"
        },
        "beckn:validity": {
          "@type": "beckn:TimePeriod",
          "schema:startDate": "2024-10-01T00:00:00Z",
          "schema:endDate": "2025-01-15T23:59:59Z"
        },
        "beckn:items": [...],
        "beckn:offers": [...]
      }
    ]
  }
}

[ameetdesh]

This was added by @anandp504 here: beckn/protocol-specifications-v2#33

@aadishjain-pulse please check, and let me know if this needs to be reopened.

[anandp504]

@aadishjain-pulse We have added the bppId and bppUri as part of the discover response at the Catalog level. The items array under a Catalog object will contain items associated with the specific BPP. We will update the examples accordingly.