Skip to content

8.6 Holistic Service Provider

8.6.1 Description

In this use case a "Holistic Service Provider" provides M2M Application services for a large building, an industry facility, a sports complex, a public infrastructure, etc. In contrast to 'normal' M2M Application service providers a Holistic Service Provider mainly aggregates and combines data from other M2M Application service providers of the facility, e.g. to provide analytics ore forecast services.

In this use case a Holistic Service Provider for a football stadium provides the optimal fill status of the water reservoir of the stadium, taking into account:

  • Event calendar and occupancy patterns for the planned events
  • Current weather conditions and forecast,
  • Ticket sales,
  • lawn irrigation with the target to enable a high level of rain water

The requirement for such a scenario is that M2M Application service providers can provide limited access to a subset of their M2M data to the Holistic Service Provider. In addition this needs to be done in a semi-automated way that requires minimal human involvement

8.6.2 Source

REQ-2015-0527R01

Note

This use case has been gathered from material of the EU FP7 Project CAMPUS 21 (http://www.campus21-project.eu), in particular from Deliverable 1.1 "Analysis of Existing Business Models and Procurement Schemes" (http://www.campus21-project.eu/media/publicdeliverables/D1-1.pdf)

8.6.3 Actors

  • Holistic Management Service Provider (HM) : A company that provides holistic management services for energy, material and resource flows for any kinds of facilities. The actor provides the synergetic analytics over all data sources within different dimensions like time, space and context, and provides decision support for advanced facility control operations. This actor cooperates with the facility operator in order to provide holistic data management and control.
    According to oneM2M terminology the HM is a M2M Application Service Provider
  • Facility Operator (FO) : A company that is in charge of the operation of facility. The main focus is the main facility's metering and control system (e.g. building automation systems) and therefore the operation of the facility in a cost- and energy-efficient manner. This actor will cooperate with third party facility services in order to enable holistic data integration. It is in charge of the business relations for all actors active within and for the facility.
    According to oneM2M terminology the FO is a M2M Application Service Provider
  • Third Party Facility ICT provider (TP): A company which provides an additional sensor/ control/ metering system into the facility operated independently (installed permanently or temporarily, e.g. event ticketing system) from the main facility monitoring system. This actor might have a business relation with the facility operator, and enables access to its data.
    According to oneM2M terminology the TP is a M2M Application Service Provider

All the above mentioned actors provide oneM2M System compliant M2M Application services.

8.6.4 Pre-conditions

  • In order to provide services the Holistic Management Service Provider (HM) needs to get access to M2M data of multiple, independent Third Party Facility ICT providers (TP) in near real time. He needs to prove legitimacy of his request to access these data by some authorization of the Facility Operator (FO)
  • The Facility Operator has established a business relationship with the Holistic Management Service Provider
    (FO <-> HM)

  • The Facility Operator has established business relationships with Third Party Facility ICT providers that provide:

    • The event calendar and ticket sales (TP for event management)
    • ticket sales solutions at the stadium
    • maintenance (temperature- and humidity control, irrigation) of the lawn of the stadium
    • maintenance (filling level, quality control, outflow- and inflow control) of the water reservoir of the stadium

    (FO <-> TP) - Facility Operator, Holistic Management Service Provider and Third Party Facility ICT providers has established business relationships with the M2M Service Provider.
    (FO, HM, TP <-> M2M-SP)

Note, there is no business relationship between the Holistic Management Service Provider and Third Party Facility ICT providers.

8.6.5 Triggers

None

8.6.6 Normal Flow

  1. Offline Step:
    (a) The Holistic Management Service Provider (HM) requests the Facility Operator (FO) to provide him with data read-access to event calendar, ticketing information, lawn conditions and water reservoir conditions. These data are required with a certain quality/granularity (e.g. twice a day). Moreover actuation-access to the inflow of the water reservoir is requested
    (b) The Facility Operator (FO) returns a list of IDs of Third Party Facility ICT providers (TP) whose Applications provide these data

  2. The Facility Operator (FO) provides the HM with an electronic token that certifies the FO's consent to allowing the HM's applications to access Third Party Facility ICT provider (TP) data.
    This consent - and the token - is restricted to only

    • The TPs and the data of these TPs that are required for the holistic service
    • The necessary quality/granularity of the data.

    The Facility Operator (FO) can at any time revoke his consent by invalidating the electronic token 3. Based on list of IDs of TPs the M2M Application of the HM discovers relevant applications of the TPs 4. The M2M Application of the HM requests read / write access to the relevant data of the TPs applications. The electronic token provided by the FO is attached to this request to prove its legitimacy. 5. Since the legitimacy of the data access request is proven through the electronic token the TP enables the data access to the HM with the necessary quality/granularity of the data.

8.6.7 Alternative flow

None

8.6.8 Post-conditions

None

8.6.9 High Level Illustration

Figure 8.6.9-1 Holistic Service Provider High Level Illustration

Figure 8.6.9-1 Holistic Service Provider High Level Illustration

8.6.10 Potential requirements

  1. When an M2M Application (A) has access (read and/or write) to application data of another M2M Application (B) then (A) shall be able to create an electronic means - e.g. a token - that certifies the consent of (A) that a third M2M Application (C) is authorized to access these data too.
  2. The M2M Application (A) shall be able to provide a third M2M Application (C) with this authorization token.
  3. The M2M Application (A) shall be able to restrict the consent expressed in the authorization token to specify:
    • the authorized M2M Application (C)
    • the data accessed from a specified M2M Application (B)
    • the type of data access (read and/or write) and time when (how often) data can be accessed.
    • in case of subscription to the data the time granularity of providing data updates
  4. An M2M Application (B) shall be able to receive a request to access its data from an M2M Application (C) together with an authorization token that certifies the consent of M2M Application (A) that (C) has been authorized by (A) to access these data.
  5. The M2M Application (A) that had issued the authorization token shall be able to revoke the authorization token.
  6. When an authorization token has been revoked, then any M2M Application (B) that had granted access to its data based on the presence of this authorization token shall receive notification by the M2M System that the authorization token has been revoked.