12.9 Semantics query for device discovery across M2M Service Providers
12.9.1 Description
This use case describes discovery of a device based on metadata of the device such as the type of device or its location. It is similar to the use case "Use Case on Devices, Virtual Devices and Things" in clause 8.2 however in the present use case the discovery may be extended to the domains of different M2M service providers.
12.9.2 Source
REQ-2014-0005R01 Semantics query for device discovery across M2M Service Providers
12.9.3 Actors
- M2M Application Provider
The M2M Application Provider provides an application which can employ a device that has already been installed and is operated by a different M2M Application Provider. However, the M2M Application Provider does not have any information (ID, URI, etc.) that can identify the device, the M2M service provider and the M2M Application Provider which the device belongs to. - M2M Service Provider 1
M2M Service Provider 1 is a service provider with whom the M2M Application Provider has a contractual relationship. - M2M Service Provider 2
M2M Service Provider 2 is a service provider with whom the M2M Application Provider does not have a contractual relationship. The M2M Service Infrastructure of M2M Service Provider 1 can communicate with the M2M Service Infrastructure of M2M Service Provider 2 via an inter-provider interface. - The device which M2M Application Provider wants to employ is connected to M2M Service Provider 2.
12.9.4 Pre-conditions
An M2M Device (e.g. a surveillance camera in a public space, a thermometer for agriculture in a field, etc.) has been installed and is operated in the domain of M2M Service Provider 2.
The M2M Application Provider has found the device in the real world (in the public space, the agriculture field, etc.) and wants to make use of the device within his application. The M2M Application Provider, however, does not have any information (ID, URI, etc.) that can identify the device. Further, the M2M Application Provider does not know which M2M Service Provider the device belongs to.
The M2M Application Provider has a contractual relationship with M2M Service Provider 1.
M2M Service Providers 1 and 2 have databases that contain information on their devices. The databases include location information (where each device is currently located) and the device type.
12.9.5 Triggers
Using a suitable interface (e.g. a web-page) of the M2M Application the M2M Application Provider creates a request for using the device. The request contains location information about the device and possibly a device type.
12.9.6 Normal Flow
- The M2M Application launches a query within the domain of M2M Service Provider 1 to find and identify the device. The query is invoked with location information on the device and information on the device type.
- The database of M2M Service Provider 1 is searched whether the requested device is connected to his domain or not.
- If the requested device is connected to M2M Service Provider 1, M2M Service Provider 1 returns to the M2M Application the information to identify the device (ID, URI, etc.) and terms of use for the device.
- If the requested device is not connected to M2M Service Provider 1 then M2M Service Provider 1 forwards the query to other M2M Service Providers to which M2M Service Provider 1 has an inter-provider system interface. Forwarding may depend on whether some criteria of the query are known to be supported / not supported by a certain Service Provider (e.g. if it is known that the devices of a Service Provider only operate in a certain geographical region and the query looks for a device in a different region).
- The query is executed in the domains of the other M2M Service Providers.
- If the requested device is connected to M2M Service Provider 2 then M2M Service Provider 2 returns to M2M Service Provider 1 the information to identify the device (ID, URI, etc.) and terms of use for the device.
- M2M Service Provider 1 returns to M2M Application Provider the information to identify the device (ID, URI, etc.) and terms of use.
12.9.7 Alternative Flow
None
12.9.8 Post-conditions
M2M Application Provider can start to employ the device on the basis of the terms of use sent by M2M Service Provider 1.
12.9.9 High Level Illustration
Figure 12.9.9-1 High Level Illustration of Semantics discovery across M2M Service Providers
12.9.10 Potential Requirements
The following requirements extend the requirement SMR-004 from clause 6.3.2 (Semantic Requirements) of [i.16]:
SMR-004: The M2M System shall provide capabilities to discover M2M Resources based on semantic descriptions.
- The M2M System shall provide a capability to an M2M Application to search (semantic query) within the domain of the application's M2M Service Provider to discover M2M Devices, Virtual Devices and Things on the basis of their semantic descriptions and meta-data such as device location or a device type.
- The M2M System shall provide a capability to a M2M Service Provider to automatically forward such a semantic query via standardized inter-provider interfaces to the domains of other M2M Service providers in order to extend the search to these domains.
Note
Based on Service Provider's policies forwarding can depend on whether some criteria of the query are known to be supported / not supported by a certain Service Provider (e.g. if it is known that the devices of a Service Provider only operate in a certain geographical region and the query looks for a device in a different region).
If M2M Devices, Virtual Devices and Things that match the criteria are found within the domain of a M2M Service Provider to which the semantic query had been forwarded then the search results may be returned via standardized inter-provider interfaces to the domain of the M2M Service Provider that had forwarded the query. The search result shall contain sufficient information to identify the device and the term of use for the device.
- The M2M System shall provide the capability to return to the M2M Application that had issued the semantic query the results of the query from the M2M Service Provider's domain and from M2M Service Provider domains to which the query had been forwarded.
The supported formats for semantic queries shall be described in the oneM2M standard.