# 1. M2M service provision

In use case 1, a service is provided by the Service Provider to the Machine Service Consumer.

### Roles <a href="#id-1.m2mserviceprovision-roles" id="id-1.m2mserviceprovision-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>VC Variant</td></tr><tr><td>Use case variation</td><td>1. M2M service provision</td><td>1a</td><td><a href="1.-m2m-service-provision/1b.-m2m-service-provision-with-the-ep-as-the-delegation-info-pip">1b</a></td><td><a href="1.-m2m-service-provision/1c.-m2m-service-provision-with-the-ar-as-the-delegation-info-pip">1c</a></td><td><a href="1.-m2m-service-provision/1d.-m2m-service-provision-with-verifiable-credentials">1d</a></td></tr></tbody></table>

As no delegation takes place, the legal entity fulfilling the Entitled Party role also fulfils the Service Consumer role.

### Depiction <a href="#id-1.m2mserviceprovision-depiction" id="id-1.m2mserviceprovision-depiction"></a>

#### **Legal relations** <a href="#id-1.m2mserviceprovision-legalrelations" id="id-1.m2mserviceprovision-legalrelations"></a>

<figure><img src="broken-reference" alt=""><figcaption></figcaption></figure>

#### **Use case interaction** <a href="#id-1.m2mserviceprovision-usecaseinteraction" id="id-1.m2mserviceprovision-usecaseinteraction"></a>

<figure><img src="broken-reference" alt=""><figcaption></figcaption></figure>

### Description <a href="#id-1.m2mserviceprovision-description" id="id-1.m2mserviceprovision-description"></a>

**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:**

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.

### Sequence diagram <a href="#id-1.m2mserviceprovision-sequencediagram" id="id-1.m2mserviceprovision-sequencediagram"></a>

<figure><img src="https://399850463-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVbeX1IpIWRqMpyA3SdQH%2Fuploads%2Fgit-blob-54393295dc985e11d23d45e9b2e00f327e967501%2F170219%20UC1A-%20M2M%20basic%20service%20consumption.png?alt=media" alt=""><figcaption></figcaption></figure>
