Human Context Presence Management

Actors

Alice and Bob are Identified Consumers that are subscribers of different Context Service Providers.

Alice asks authorisation to Bob to subscribe to his Context / Presence
Bob receives Alice’s request and accepts (usually this procedure also gives permission to Bob to subscribe to Alice Context )
Alice is informed Bob has accepted her subscription and receives current Bob context
Every time Bob’s Context change is published, Alice is notified
Depending on the Context Service provided, Bob’s Context data is the agregation of data from different sources, including:
- availability status explicitly set by Bob
- connectivity status derived from events received from the network
- activity status derived from data collected from sensors
- connectivity description eg IP Address and ports
- device profile eg available resources including media (mic, cam), data sources (sensors) and associated codecs.
- localisation collected from sensors
- environmental data (eg temperature, light, noise) derived from data collected from sensors
- etc
every time Alice registers with her service provider, she receives the most updated context data of Bob as a response to a request that is automatically authorized by Bob’s Context Provider (or a separated Authorisation / Identity Provider in case Bob has subscribed the Context Provider with an external Identity) as set with the Context subscription

Currently it is not possible, seamless interoperability between Context providers and consumers.

#64 Human Context