The DiscoveryProfiles element is the key in the "Unknown" communication patterns where the participants do not know who are the others. Thus the information is requested or routed based on the service profile. Instead of describe a specific participant we found a description of the required service.
The DiscoveryProfiles element describes the characteristics associated in both the service and the provider. The underlying entity in the CISE service model is the ServiceProfile entity. It is used to request to the CISE Node to look for services of a specific type and/or from a specific type of provider (using information such as community, country, sea basin...).
See the attributes described in The DiscoveryProfiles page.
Communication patterns that use the DiscoveryProfiles
The DiscoveryProfiles is used in the Push and PullRequest messages.
Example of the DiscoveryProfiles
In this example, we are defining a service addressed to the BorderControl in Italy, and in the Mediterranean sea basin.
<DiscoveryProfiles> <Community>BorderControl</Community> <Country>IT</Country> <DataFreshness>RealTime</DataFreshness> <Function>Security</Function> <SeaBasin>Mediterranean</SeaBasin> <ServiceID>rc.lsA.service1A1.vessel.pull.provider</ServiceID> <ServiceOperation>Pull</ServiceOperation> <ServiceRole>Consumer</ServiceRole> <ServiceType>RiskService</ServiceType> <ServiceStatus>Online</ServiceStatus> <ServiceCapability> <ExpectedResponseTime>15</ExpectedResponseTime> <MaxEntitiesPerMsg>10</MaxEntitiesPerMsg> </ServiceCapability> </DiscoveryProfiles>
Example of the DiscoveryProfiles producing no results
In this example, we are defining a service; this service was not active at the time of the request. Below you can find the acknowledgement response of no services found.
<DiscoveryProfiles> <Country>IT</Country> <SeaBasin>Mediterranean</SeaBasin> <ServiceType>VesselService</ServiceType> </DiscoveryProfiles>