Domain Expertise > Interactive TV Print this page
Network Servers and Subscriber Management

Broadband Network Controller

Description of a few Network based System Components Developed:

  • Session controller, for managing multiple connections on a single end-to-end session over an integrated Broadband and Local Access network.

      -  Session protocol was based on DAVIC and DSSM-CC standards
      -  Interface with the Service Provider’s Network Resource Manager and 3rd party vendor
         EMSs to setup end-to-end sessions.
      -  Generate Transaction information and forward to the backend OSS for processing
     
  • Initialization and Configuration System, for setting up CPEs (i.e. STB and Residential Gateway) based on the device capability, Service Providers network parameters and Subscriber/Service information.

      -  Interface with the backend Provisioning Module to extract subscriber and service
         related information
      -  Time Synchronization between CPE and Application Servers
      -  Remote Software Upgrade and release management
      -  Remote Monitoring and System Administration

Back

Service Selection Gateway

Rebaca was responsible for developing a Service Portal that would enable subscribers to get a listing of different Service Offerings and subscribe on demand based on STB capability and available bandwidth.

Capabilities

  • Service Listing of available Services
  • Authentication of Service and User
  • Provisioning of Service based on subscriber Profiles
  • Allocation of Service to different Users
  • Administration of Services/Servers
  • System Management and Maintenance
  • EPG server
  • Support for User-User and Administrator-User messages

Back


Subscriber Management

Rebaca is working to develop a server-side Conditional Access (CA) system that would create and manage user profiles and send the appropriate authorization information to the STBs. This system primarily comprises of the Subscriber Management System (SMS); the Subscriber Authorization System (SAS) and the Entitlement Management Message (EMM) injector. User profiles are created at the SMS – and a message is sent out to the SAS on a standard interface. The SAS creates appropriate EMMs based on the service codes the subscriber is authorized for. These EMMs are passed on to the EMM injector; which encapsulates them into MPEG private data and pushes them to the appropriate client device. The injector implements a cyclical queueing mechanism to ensure retransmission of the EMMs in case of error situations.

Key features of the solution

  • Seamless Interoperability – The different components (SMS, SAS and Injector) have well defined standard interfaces to each other. This enables them to potentially interoperate with other vendor’s products.
     
  • Service Code Handling - Assigning of specific subscription packages to subscribers is handled by associating service codes to each subscription package. The system allows operators to create subscription packages and associate them with subscribers; who are also notified of the same.
     
  • Parental Control – The system allows Parental Controls to be either set to a subscriber-specified value or to factory default. Parental Controls provide a filtering mechanism to prevent certain members of the household from viewing unsafe content
     
  • Pay-per-view (PPV) Handling – Once the user buys a PPV event; it is registered at the SMS; and is notified to the STB through the SAS. Each PPV event is internally associated with a Service Code at the SMS. The following PPV scenarios are handled:

      -  Add/Delete PPV Order for a subscriber.
      -  Associate PPV credit value for a subscriber. The credit value determines how many
         PPVs a subscriber can purchase.
      -  Trigger uploading of PPV history from STB (client device) to the server. The history
         data is used for analysis, troubleshooting and customer support. The SAS passes  
         on the PPV data to the SMS upon receiving it from the STBs.
     
  • Message Scheduling – The system enables operators to trigger specific messages in the client device at any point of time. The STB has several messages stored internally. Any specific message can be triggered by the SMS – and would get displayed at the specified STB. Emergency broadcast messages may also be sent through this component.

Technologies

  • MS VC++ ( without using MFC)
  • Windows 2003 Server
  • MS SQLServer 2000
  • Standard Template Library (STL components)
  • ODBC for database connectivity.
  • IIS as a Web Service Container

Back

www.rebaca.com  | Close