#145 Allow for type ref in Get services

[Whitney Cox]

Currently, all Get services that can be filtered are filtered by passing a handle. Adding the ability to search by type (Context Free 10 codes) would allow for a client to discover metrics/services without having to have specific insight to a device's custom handles.

This would be specifically useful for the GetContainmentTree and GetMDescription requests.

[Stefan Schlichting]

Hi Whitney,
thank you for your ticket!

We will discuss the topic in our regular SDC contributor meeting next week and will provide you feedback.

I have one question beforehand:
What would be the desired result? The one Descriptor excluding child descriptors or the whole containment tree below the descriptor? One would probably also need something like the handle of the parent so that you know where the descriptor is embedded ?

It is really a good point and I think we consider it for something like an "AdvancedContainmentTreeService".

If you have any further ideas, sequence diagrams or message signatures we would highly appreciate this.

Best regards
Stefan

P.s.: You maybe want to have also a look at the section "Complex device component based discovery" from 11073-20701. It recommands to make the device and module types usable for discovery purposes. This maybe already a good starting point to filter if the device is relevant.

[Whitney Cox]

Hi Stefan,

I think that returning one descriptor(for each instance of the type) and the parent handle after using the getContainmentTree service with a type would be interesting. This would allow for "bottom-up" searching instead of "top-down".

Either then the getDescriptor service can be used with the resolved handle to obtain full information about the descriptor. Or if getDescriptor could take in a type it would be able to return all descriptors with the type without having to go through handle resolution.

Thanks for pointing us to the complex device based discovery we will look into this for advertisment of types.

Thanks,
Whitney

[Stefan Schlichting]

Hi Whitney,

we discussed your proposal and would be happy if you could draft a first sketch for the new operations of a new service.
We intend to use this as a starting point for more sophisticated filtering mechanisms.

So if you have some kind of sequence diagram and a message signature with some documentation we could start creating the xsd schema and port type.

All the best,
Stefan

[Whitney Cox]

Hi Stefan,

Sorry for the delay. I have attached a quick draft for a more advanced searching service. The service addresses some of the inefficiencies that occur when using the GetContainmentTree service and allows a service consumer to resolve handles offered by a provider using a type code.

This proposed service can also be used by a consumer to quickly discover types offered by a provider without passing over the entire MDIB.

Let me know if you have any questions.

Thanks,
Whitney

[Stefan Schlichting]

Hi Whitney,
thanks for the perfect description of your proposal!
We will discuss your proposed "SearchDescriptors" service and I will propose to accept it.

Best regards,
Stefan

[Stefan Schlichting]

PROPOSED ACCEPT

Add an optional "SearchDescriptors" service as described in Whitney's draft to ease searching for specific capabilities.

[Whitney Cox]

Hi @schlich09,

Hope you are doing well. I was wondering if you ever got any feedback on this capability?

Thanks,
Whitney Cox

[Stefan Schlichting]

Hi,

the ticket has been accepted for the amendment.

All the best
Stefan