Skip to content

Topics to Be Addressed in User Scenarios

pchainho edited this page Feb 11, 2015 · 1 revision

Aspects to be covered by big scenario to demonstrate reTHINK objectives and vision

  • scenario can be demonstrated in WP6:

Each trial site simulates at least a service provider domain. Ie Four service providers eg 1 or 2 Smart Cities, Communication Service Providers, Network Service Providers, Identity Providers, App Providers, Legal regulators

  • Global Mechanisms for the registration, look-up and discovery of Hyperties as well as communication between them

Show how a Hyperty (Service Enabler) is developed, provisioned and reusable by other App developer stakeholder e.g. real time aggregation of touristic info according to context captured by mobile phone sensors and other public sensors eg iBeacon

  • Application provisioning and enablement in line with the perspective of various users/stakeholders:

Show how easy a new App is developed and delivered to all domains e.g. an individual or SME with few resources has a good business idea (e.g. "Contextual and Remote Adhoc City Guide Expert Service a la Uber" or "Contextual and Remote Enterprise ICT support service for a la Uber") and is able to develop it by reusing existing Hyperties and bring it to the Global Market.

  • Secure and trustworthy service compatible with current and future European/national regulations.

Show how dynamic security legal policies can be enforced for different types of services eg how legal interception for a terrorist suspect having different identities can be performed for Real Time Communication, follow virtual activities in different Social Network (eg UGC), follow real world activities using IoT sensors

  • Service portability compatible with current and future European/national regulations.

Show how subscribers can change from one service provider to another keeping the same public identity for different type of services e.g. Contextual Enterprise RTC or End-user Data Backup service

  • Confidence level measurement of identities provided by a third party service

Different scenarios, including "pure" Real Time Communications and more complex ones mixing eg voting with contextual communication in eGovernment scenario

  • Convergent and multi party services, relying on a trusted identity provider

Extend above with multiparty eg public informative sessions organised by city authorities with remote participation from citizens each using different Identity Providers

  • show business impact of reTHINK concepts on today’s communication and services ecosystems as well as content delivery and how they might be transformed in the future

Show how new SMEs can be part of a collaborative Service Delivery eg City Guide experts service in a collaborative tourist service delivery or new eHealth expert that can be called in emergency situations for tourists

  • show who are the business players now and who will participate in the future

scenario should include all business roles identified in T2.1 including: end-users consumers, business/enterprise consumers, Hyperty SME developers/providers, App SME developers/providers, Identity Providers, Business Brokers, Legal Regulator, Public entities like smart city council, Smart Objects Providers

  • show the impact of reTHINK concepts will have in the economic sphere and in society in general, especially in the European community

A more vibrant and powered startup/ enterpreneurs based economy since we'll lower barrier for new service providers, seamless interoperability and identity agnostic service delivery enabling global market for any service provider, dynamic business ecosystems that can include small SMEs. Improved balance between security and privacy to face eg terrorism.

  • cover real-time audio/video communication use cases
  • cover content delivery use cases via Content Delivery Networks (CDNs),
  • cover M2M communication use cases enabled by the Internet of Things
  • cover classic Telecom services, entertainment, Over-The-Top (OTT) communication services and smart homes/offices
Clone this wiki locally