FROG BACKEND

The Frog Backend addresses the operators’ needs for convergence and monetisation in a multiscreen ecosystem. Frog Backend is a service platform that provides the missing business logic to power innovative TV experiences, based on intimate knowledge of the end-user’s viewing habits and devices in use.

It is a modular and scalable suite of independent and optional add-ons to the TV Operator’s existing systems to be deployed within broadband or broadcast backends.

With Frog Backend operators can step-by-step bridge the infrastructure gap between their legacy systems and a “next-gen” cloud and multi-tenant service delivery platform, without being locked into a single-vendor proprietary solution.

Example uses cases include personalised TV user interface delivery to client devices, targeted advertisements insertion, contents search and recommendation based on the viewer’s profile, and more

ARCHITECTURE

The Frog Backend is based on a very modular architecture, so that any feature can be deployed independently from the others. The common set of core components implements an asynchronous service bus in node.js that orchestrates between the existing operator infrastructure and Frog Backend’s service features modules. A NoSQL database (MongoDB) hosts all subscriber and usage tracking information. 

Each convergent TV service feature is implemented as an independent plugin that integrates with the core and external systems (e.g. operator OSS/BSS, third-party applications such as recommendation engines, VoD CMS, and more).

Frog Backend easily integrates as an add-on to the existing operator infrastructure thanks to its design that follows Service-Oriented Architecture (SOA) and Entreprise Application Integration (EAI) principles. It provides RESTful APIs with JSON data formats that can be leveraged with minimal effort to integrate Frog backend with other systems (client devices, existing backend …).

 

>> ARCHITECTURE DIAGRAM

 

 

 

 

 

CORE ENGINE FEATURES

  • User Management: profiles, rights, households, accounts, single sign-on
  • Broadcast & Broadband Devices Management: monitoring, software upgrade, device class management
  • Usage Tracking: audience measurement, user behaviour
  • Security Management: secured connections, file encryption, certificates, tokens
  • Multi-Network File Delivery: firmware images, applications, EPG, catalog and metadata
  • Multi-screen API: RESTful interface designed for any application / middleware
  • Smart Client Synchronization : Push notifications and “Rendez-vous” mechanism to optimise bandwidth use over broadcast, unicast or multicast networks

CONVERGENT TV SERVICES FEATURES

  • Personalized TV Experience: Sharing user’s data (settings, notifications, records list…) irrespective of applications & devices
  • Multiscreen TV EPG: Building blended services TV line-up or multi-source EPG
  • Multiscreen centralized PVR: Defining a centralized PVR strategy for any device and recorder
  • Integrated social TV: Plugging the social network use cases in the TV experience
  • Proxy for Search & Recommendation: Exchanging data between Content Management Systems (CMS), end-users database, 3rd-party engines
  • Application Store: Receive, validate, organize and publish HMTL5 and Android applications

DEPLOYMENT OPTIONS

Frog Backend allows a variety of deployment scenarios depending on each operator’s requirements in terms of features, existing systems to integrate with, required capacity and more.

Frog Backend’s core and service-features plugins are typically deployed as highly available load-balanced clusters of instances, either on-premise in physical servers or in the cloud (public or private).

For example, an operator can integrate and deploy the core and only one of the possible services on a small number of instances, and later grow its deployment by adding more instances running the same services and/or adding new services, going up to a deployment that may span operations with millions of subscribers in multiple countries with several business entities managed in a multi-tenant way. With this approach, new services can be developed while keeping the legacy systems.