# M2M service provision including an app

Use case 1 and its variations can be initiated by a Human Service Consumer through an app. In such a case, the Machine Service Consumer acts as a proxy between the Human Service Consumer and the Service Provider's machine.

### Roles <a href="#m2mserviceprovisionincludinganapp-roles" id="m2mserviceprovisionincludinganapp-roles"></a>

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><br><br></td><td><strong>Delegation info PIP</strong></td><td></td><td></td><td></td><td></td></tr><tr><td></td><td><em>No delegation</em></td><td>Service Provider</td><td>Entitled Party</td><td>Authorisation Reg</td><td>Verifiable Credentials Variant</td></tr><tr><td>Use case variation</td><td><a href="">1</a></td><td>1a</td><td><a href="1b.-m2m-service-provision-with-the-ep-as-the-delegation-info-pip">1b</a></td><td><a href="1c.-m2m-service-provision-with-the-ar-as-the-delegation-info-pip">1c</a></td><td><a href="1d.-m2m-service-provision-with-verifiable-credentials">1d</a></td></tr></tbody></table>

### Depiction <a href="#m2mserviceprovisionincludinganapp-depiction" id="m2mserviceprovisionincludinganapp-depiction"></a>

#### Legal relations <a href="#m2mserviceprovisionincludinganapp-legalrelations" id="m2mserviceprovisionincludinganapp-legalrelations"></a>

<figure><img src="https://399850463-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVbeX1IpIWRqMpyA3SdQH%2Fuploads%2Fgit-blob-16b601e7faf7e3660e3403cee5f7b279a7dc3842%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Use case interaction <a href="#m2mserviceprovisionincludinganapp-usecaseinteraction" id="m2mserviceprovisionincludinganapp-usecaseinteraction"></a>

<figure><img src="https://399850463-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVbeX1IpIWRqMpyA3SdQH%2Fuploads%2Fgit-blob-8601e9dd39f6adf5b073c2f99f9cb57831bb6a08%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Description <a href="#m2mserviceprovisionincludinganapp-description" id="m2mserviceprovisionincludinganapp-description"></a>

**As to use case 1, it is a prerequisite of this use case that:**

* The Service Provider has and manages its own entitlement information indicating what Entitled Parties are entitled to what (parts of) services\*;
* The Service Consumer can authenticate the Service Provider.
* The Service Provider is able to authenticate the Service Consumer.
* In this use case, the Entitled Party is also the Service Consumer.

\*The Service Provider can outsource this function to a third party

**The use case consists of the following steps:**

* The Human Service Consumer uses an app to request a service at the Machine Service Consumer - the Human Service Consumer's identity is included in the request.
* The request is mapped to a service request.

1. The Machine Service Consumer requests a service from the Service Provider.
2. The Service Provider authenticates the Machine Service Consumer and validates the iSHARE adherence of the Service Consumer;
3. The Service Provider authorises the Machine Service Consumer of the Service Consumer based on the entitlement information registered with the Service Provider;
4. The Service Provider executes the requested service;
5. The Service Provider provides the service result to the Machine Service Consumer;

* The Human Service Consumer accesses the result through app.

{% hint style="info" %}
**\[VC Variant]:** The HSC stores the Verifiable Credentials in a digital wallet and provides necessary credentials (Participant and DataRights Credential) upon App's request.
{% endhint %}