How can an application get multiple contexts from an infrastructure so it can aggregate them and consume them to enable secure, dynamic policy-driven context-aware experiences?
The holy-grail of any Context-aware application is user identity, device (mobile device, IOT device) identity, location and dynamic security policies enforcement based on the context.
A context-aware application needs a north-bound API access to aggregated infrastructure contexts so it can enable context-aware experiences to its clients.
- Gather and aggregate infrastructure contexts
- Provide APIs for context-aware infrastructure requests by domain use cases
- Extend user, device, location, domain, application profile with tagging to enable context-aware experiences
An application consuming Context-aware Infrastructure Services can deliver contextual experiences to its users – based on user, device, location or environment context. For example, a hotel chain can serve its guests the tourist spots, shopping centers, local news, and local advertisements of the city on the mobile wherever the guest stays. Similarly, the hotel can provide different experience zones to its guests when they access with the same ID from different locations, based on guest’s preferences and tastes. Thus, a context-aware infrastructure can enable delightful experiences to it users.
1.1.4 Examples / Use-cases
Any application needing to enable context-aware experiences normally fall in this category.
- Drive increased sales by observing how a shopper behaves when in store and enabling interactive shopper experiences to shoppers
- Improve patient’s experience by guiding him/her from the time patient arrives in the vicinity of hospital