TC9.10 - Managing multiple protocols City, human, machine and their several combinations

Test Case Title	TC9.10 - Managing multiple protocols City, human, machine and their several combinations
Goal	Facilitate communications and notification involving human, machine and their combinations. Log the activities for managing events and critical situations. Log any kind of access to Smart city API and Km4City queries.
Prerequisites	Using a PC or Mobile with a web browser. Access to the back office since this process for. The following functionalities are available only for specific Snap4city users with specific privileges.
Expected successful result	See the results on multiple test cases, this is only a recap.
Steps

 

The following flows are only samples, and they are not exhaustive of all the possible evolutions for this protocol.

These complex scenarios/flows are composed by steps that have been already shown, if not clearly specified.

1. City to human (for directives)
   
   1. Snap4City IOT Applications, direct push towards users with specific IOT Applications;
   2. web and mobile App via Advanced Smart City API, civil protection alerts,
   3. Dashboards and MicroApplications of the municipality,
   4. calls via Notificator (Emails),
   5. social media messages via IOT applications: Telegram, Facebook, Twitter,
   6. sending SMS via IOT applications of the municipality,
   7. changing variable message panel text via IOT applications of the municipality,
   8. producing RSS Feed via IOT application of the municipality

Major examples of this kind of communication can be via:

• Data Sources --> Data Analytics --> Dashboards --> Notificator --> humans
  • ETL/IOT --> R studio --> Dashboard --> Notificator --> humans
• Data Sources --> Data Analytics --> Snap4City Applications --> humans
  • ETL/IOT --> IOT Application (also calling R studio) --> Dashboard
• Data Sources --> Data Analytics --> Advanced Smart City API (Suggester, Personal Assistant) --> web and mobile Apps
  • ETL/IOT --> R studio --> Hbase/Phoenix --> Advanced Smart City API --> web and mobile APP or IOT Applications --> Humans
• Data Sources (as events) --> Dashboards Engine --> Notificator --> humans
  • ETL/IOT --> Dashboard --> Notificator --> humans

2. Human to city
   
   1. anonymous annotations via Smart City API, posed via MicroApplications on Dashboards,
   2. personal annotations posed public by the users to communicate to the city eventual problems,
   3. comments and data from the IOT Applications of the city users,
   4. comments from the Snap4City portal blogs, etc.
   5. post passing on social media: Twitter with citation, Twitter with hashtags for example by using Twitter Vigilance. 

Major examples of this kind of communication can be via:

• Human --> web --> Dashboard Actuator --> IOT Broker --> data, Actions
  • Human --> Dashboard --> IOT Broker --> IOT application --> action
• Human --> mobile app or IOT app --> Advanced Smart City API --> UserProfile --> Collective User profile --> data, Actions
  • Human --> IOT application --> Advanced Smart City API --> UserProfile --> Collective User profile --> data, Actions
  • Etc.
• Human --> IOT actuator --> Snap4City Applications --> data, Actions (messages, SMS, calls, dashboard, variable messages panels, etc.)
• Human --> ETL  / Data Analytics development --> new processes, data results
• Human --> Data on DataGate --> Data Storage/knowledge base --> Actions/processes

3. Machine to machines by automating a large number of processes
   
   1. Snap4City IOT Applications propagating event driven alerts, and/or managing back office activities,
   2. ETL processes for periodic data transformation,
   3. Data Analytics periodic task for anomaly, and/or to identify conditions that are not operating in the correct manner, thus activating recovery tasks,
   4. Firing condition and activation of the Notificator and usage of connected IOT applications to automated processes of recovering from failure, sending rescue teams, informing, 
   5. ESB notifying the  activation of critical events, or just reconfiguration, thus starting corresponding actions on other services;

Major examples of this kind of communication can be via:

• data --> Snap4City Applications --> data --> new knowledge
• data --> ETL processes --> data --> new knowledge
• ETL  / Data Analytics processes  --> Notificator --> any third party servers, actions

4. Human to human
   
   1. IOT applications sharing information via MyPersonalData service, for example the position
   2. Posting MyAnnotation and delegating access to them to specific users
   3. Creating Dashboard and delegating access to them  to specific users
   4. Creating IOT Application with Dashboard and delegating access to them  to specific users
   5. Direct connecting IOT applications via WebSocket for direct messages,
   6. Direct connecting IOT application and devices with Dashboard services and IOT Applications of other users.

Major examples of this kind of communication can be via:

• human --> Snap4City Applications --> human (see the above example with the Dimer and Switch, a number of people could receive this information)
• human --> ChatRoom of the Dashboard System --> human (not yet available)
• human --> Snap4City Web Portal and information --> human
• exploiting messages and WebSocket at level of Dashboard services,