> For the complete documentation index, see [llms.txt](https://framework.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/1.-m2m-service-provision/m2m-service-provision-including-an-app.md).
# 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
### Depiction
#### Legal relations
#### Use case interaction
### Description
**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 %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/1.-m2m-service-provision/m2m-service-provision-including-an-app.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.