Skip to main content

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 case, the Machine Service Consumer acts as a proxy between the Human Service Consumer and the Service Provider's machine.

Roles 



Delegation info PIP
No delegationService ProviderEntitled PartyAuthorization Reg
Use case variation11a1b1c

Depiction

 Legal relations

 

 Use case interaction

 

Description

As to use case 1, it is 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 is able to 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 authorizes 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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.