| ID | 3.1.1 |
| Title | Communication Model building and notification of its updates |
| Expert | Claudia Villalonga (NEC) |
| Priority | mandatory |
| Description | The SPICE platform MUST keep a user's Communication Model in sync with the state of the user's Distributed Communication Sphere (DCS) in terms of devices, networks, services hosted by DCS devices and users/groups. The SPICE platform MAY keep this Communication Model by regularly probing the user's environment. The SPICE platform MUST be able to discover the capabilities of the devices and the networks in the DCS of the user (e.g., their screen sizes and available codecs) and their available resources (e.g., remaining battery power and available network bandwidth). The SPICE platform MUST be able to dynamically discover the services that are running on the devices in a user s DCS (e.g., services that can render multimedia streams), their interfaces, and the resources they require. The SPICE platform MUST provide the possibility to publish this Communication Model to authorized/trusted parties and services. SPICE services and applications MUST be able to register for changes in the Distributed Communication Sphere, and therefore changes in the Communication model, so that they CAN adapt when they receive the notification of a change (e.g., the appearance of new accessible devices and networks). The communication model MUST be a part of a user's context and MUST be accessible as any other piece of knowledge information through a request-response and a publish-subscribe interface. |
| Rationale | The Communication model is the set of symbolic data that describes the composition of the the Distributed Communication Sphere of a user. The Communication model is used to allow communication with the user in order to ensure the best possible user's experience as far as using services is concerned. |
| Type | functional |
| Depends on | 1.5.3 - Legal requirements Privacy - Key Principles of Data Processing 1.5.4 - Legal requirements Privacy - Rights of the Data Subject and Obligantions to the Data Controller 1.5.5 - Legal requirements Privacy - Transferring data to third countries 3.2.1 - Group management |
| Child dependencies | 3.0.1 - SPICE Terminal and Device requirements 3.3.1 - Multimodal and multi-device delivery of services 7.3.4 - Changing the Presentation Modality and Interactive Modality |
| Environment | |
| Other_info | |
| Category | technical;device;open market |
| Subcategory | |
| Subcategory2 | |
| Scenario_scene | unified.scene13 unified.scene14 |
| SPICE_value | (seamless) service adaptation;service roaming |
| Demo | implemented |
| Keywords | Communication Model;Distributed Communication Sphere;DCS;device;network;service;user group;change in DCS;change in Communication Model;notification |
| Home |