1. FI-WARE GEs Backend 1 FI-Star SEFI-Ware GE specificationFI-Ware GEi used Back-End Connectivity Service Name: S3C Extended: Yes Rationale of extension:  Supporting HTTP and CoAP with security option  Update the specification to meet RESTfull principle  Adding new REST interfaces Adopted GEi Name: I2ND-S3C-EPC-OTT Extended: Yes Rationale: Extracted the Rx interface implementation from the I2ND-S3C-EPC-OTT- API Event Service Name: Context Broker Extended: Yes Rationale of extension:  Adding new interface for OAuth authentication  Adding new interface for SE administration Adopted GEi Name: Orion Context Broker Extended: Yes Rationale of extension Used the Orion Context broker and implemented both OAuth authentication and administration interfaces Targeting and Profiling Service Name: Gateway Data Handling GE Name: BigData GE Extended: Yes Rational of extension: To support two interfaces: authentication and administration Adopted GEi Name: None Extended: No Rationale : No FI-Ware GE implementation was used Used, instead, the EspR4FastData library, which is exploited, in turn, by the Gateway Data Handling GE - EspR4FastData. Monitoring Service Name: FI-WARE Cloud Monitoring GE Extended: Yes Rationale of extension: the new version is under development as joint activity with XIFI project. FI-Star team will contribute to the new version Adopted GEi Name: None Extended: No Rationale: Not using FI-Ware implementation offered by Telfonica I+D, as it is not positively evaluated by us and XIFI. FI-STAR Implementation is based on Zabbix

2. FI-WARE GEs Backend 2 FI-Star SEFI-Ware GE specificationFI-Ware GEi used Device Management Service Name: IoT Backend Device Management GE Extended: Yes Rationale of extension: To support lightweight OMA M2M specification for device management. Adopted GEi name: None Extended: No Rationale : To support constrained device requirements such as Android-compatible devices, we implemented new reference implementation following FI-Star spec. Further details in the next column. Security and Privacy Service Name: IdM GE Name: Access Control GE Extended: Yes Rationale of extension: Adopting FI-WARE access control model to secure API access, specifying and implementing some new APIs (e.g. provisioning, access log) Adopted GEi Name: None Extended: No Rationale : As available only as service the GCP, One-IDM and DigitalSelf IdMs cannot be used in Fi-Star at this point in time due to our “Reverse Cloud” requirement. Actually only the KeyRock IdM is offered as open source but it does not provide several required features such as OpenID Connect and SAML. The Access Control GE implementation by Thales has only tested with GCP IdM so far. As a result, FI-STAR implementation is based on an open source solution WSO2 IS (version 4.6.0) Time Service New SEAdopted GEi Name: None Extended: No Rationale: N.A.

3. FI-WARE GEs Front-end 3 FI-Star SEFI-Ware GE specificationFI-Ware reference implementation Front-end Connectivity Service The Connected Device Interface (CDI) Enabler from the Service Capability, Connectivity and Control (S3C) Generic Enabler Extended: Yes Rationale of extension:  Supporting HTTP and CoAP with security option  Supporting NAT  QoS support  Store data temporary in case no connectivity available  Ensure End-to-End security Extended: Yes Rationale: develop the SE completely new in order to support the new specification December 16th 2014

4. 4 FI-Star SEFI-Ware GE specification FI-Ware reference implementation Sensor Data Collection Service GW Device Adapter and Protocol Adapter from the IoT GE Extended: No Extended: NA New implementation for both GE is implemented to meet for Android-compliant devices with support of set of different protocol adapters from the health domain December 16th 2014 FI-WARE GEs Front-end

5. 5 FI-Star SEFI-Ware GE specification FI-Ware reference implementation Local Data Storage Service Extended: no Rational: new specification to support the trial use-case requirements Extended: no Rational: new implementation for Android (alpha) and multiple platforms (beta) December 16th 2014 FI-WARE GEs Front-end

6. 6 FI-Star SEFI-Ware GE specification FI-Ware reference implementation Notification ServiceIoT Broker and Context Broker specifications used. Extended: no Extended: no Rational: new implementation for Android (alpha and beta) December 16th 2014 FI-WARE GEs Front-end

7. 7 FI-Star SEFI-Ware GE specification FI-Ware reference implementation Local Data Processing Service IoT Gateway Data Handling and CEP specifications used. Extended: no Adapted: yes Rational: The specifications have been adapted for better integration. Extended: no Rational: new implementation for Android (alpha and beta) December 16th 2014 FI-WARE GEs Front-end