Twenty Key Use Cases For the Telecom Multiscreen Converged Experience
Telecom Multiscreen App Use Cases
These use cases highlight the technologies required to deliver personalized, multiscreen services.
  • Project Year
  • Creator Name
    Kevin Grant
  • Organization
    Amdocs Canada
  • City
  • Country
  • Creation Date
    02 May 2012
  • Modification Date
    13 March 2021
  • Version

UXP Systems presents 20 Key Use Cases showcasing the extension of video, voice and messaging services to new screens, in order to:

  • Adapt from a device-centric user paradigm to a user-centric multiscreen paradigm Retain subscribers and increase the penetration of the service bundle
  • Differentiate services against over-the-top and traditional operators
  • Optimize the user experience across all screens

These use cases are designed to highlight technical enablers required across all services for personalized, multiscreen services, and how a common platform can optimize the operator’s network architecture to realize the vision.

UXP Systems’ Multiscreen Interaction Platform is an industry leading platform that has enabled these use cases leveraging existing IP services and back-office operator systems.

UXP Systems’ MINT Platform Enablers for Multiscreen

1. Profile & Subscription Management

  • Personalized profile & subscription management, that integrates to billing, entitlement and SSO.

2. Service Orchestration & Modeling

  • Pre-built workflows and APIs that integrate to, abstract and expose operator and 3rd party services for users.

3. Interaction Console & Platform

  • An interaction container (front end) and (back end) platform, with common and key utilities/features to enable converged multiscreen services.

4. Operator Interface

  • Protocol agnostic interface and API to integrate to back end operator network & third party service systems.

5. Administration Console

  • Module for Multiscreen User Reporting and Administration

Personalization & Profile Management

  • Bringing together multiple services requires personalization whereby the operator can federate services to an individual. In addition, to seamlessly enable a single log-in, entitlements and credentials must be associated to the individual.

Service Orchestration & Modeling

  • While traditional single screen services are typically orchestrated on a device, an interact

Offline/App Optimization (Interaction Console Layer)

  • To optimize the experience for tablets and smartphones, a device side console should provide utilities to store offline data, and hold personalization and orchestration rules so the user may enjoy an offline experience, as well as an online one.

Other Enablers & Utilities

  • Many enablers/utilities are used to optimize each multiscreen, multiservice experience, and are detailed in this document
Twenty Key Use Cases For the Telecom Multiscreen Converged Experience


Contact Details and Map