# 1b. M2M service provision with the EP storing delegation info
In use case 1b, a service is provided by the Service Provider to the Machine Service Consumer. The Service Consumer has been delegated by the Entitled Party.
### Roles
### Roles
{% hint style="info" %}
An Authorisation Registry can be played by an EP itself or another organisation. In this case, the Entitled Party acts as the Authorisation Registry by holding its delegation evidence.
{% endhint %}
Note that interaction sequences are not described in the table above. In derived use case 1b, three interaction sequences are possible depending on who requests delegation info from the Authorisation Registry:
1. The Service Provider can request delegation info after a service request from the Service Consumer.
2. The Machine Service Consumer can request delegation info and include it in its service request to the Service Provider.
3. The Entitled Party can push delegation info to the Machine Service Consumer, so it can include it in its service request to the Service Provider.
Interaction sequence 3 is detailed below.
### Depiction
#### Legal relations
Note that no prior legal relation exists between the Service Consumer and the Service Provider. Which services can be consumed by the Service Consumer, as delegated by the Entitled Party, is set out in the mandatory relation between this Entitled Party and the Service Provider.
#### Prerequisite registration
**Use case interaction**
### Description
**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 can authenticate the Service Consumer.
* The delegation/authorisation responsible at the Entitled Party delegates (part of) the Entitled Party's rights (as registered at the Service Provider) to the Service Consumer. He provides the Machine Service Consumer of the Service Consumer with evidence of this delegation.
\*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. These requests include the evidence obtained from the Entitled Party.
2. The Service Provider authenticates the Machine Service Consumer and validates the iSHARE adherence of the Service Consumer;
3. The Service Provider validates the received delegation evidence through the following steps:
1. The Service Provider authenticates the Entitled Party and validates its iSHARE adherence based on the delegation evidence.
2. The Service Provider authorises the Entitled Party based on the entitlement information registered with the Service Provider.
4. The Service Provider authorises the Machine Service Consumer of the Service Consumer based on the validity of the delegation evidence.
5. The Service Provider executes the requested service.
6. The Service Provider provides the service result to the Machine Service Consumer.
### Sequence diagram
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/1.-m2m-service-provision/1b.-m2m-service-provision-with-the-ep-as-the-delegation-info-pip.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.