London, United Kingdom
+44 20 3432 8178

Telesens Ring Back Tone (T-RBT) — solution for operators, subscribers, and content providers. A unique platform for high quality personalized audio content instead of “long beeps”.

Mobile communications are a part of our life. People desire to get what they want as soon as possible, and an individual approach at the same time. It caused a revision of such “little things” as the process of establishing a connection. Waiting a long time for an answer becomes a waste of time, and the standard dial tone is sometimes annoying.

Connection time is a cost for a telecom operator that is desirable to reduce.

The answer to these challenges is the Ring Back Tone (RBT) service — a piece of music or a personal greeting instead of the standard signal.

The RBT service is not a new one, but the evolution of mobile networks to support 4G technologies has led to a serious modernization of operators’ core networks. New protocols for interaction between the operator’s network elements were created as well as new services and methods of their promotion. The modernization of the platforms has led to their complication, an increase in maintenance costs, and the time required to launch new services.

New requirements from subscribers have appeared: simplicity and flexibility in service management, expansion of its capabilities.

Besides, operators would like to get more from new and existing services: to increase the average monthly income per client, to minimize operating costs, and to have the ability to deploy new types of voice services, communication channels with subscribers.

Telesens is offering a new RBT service solution to handle these requests.

The T-RBT platform is a software package that ensures the interaction of three stakeholders:

  • subscribers
  • telecom operator
  • content providers

For subscribers (both individual and corporate), the T-RBT platform provides service and management tools.

For the operator, the platform provides opportunities to increase monthly income, control the provision of service.

For content providers — opportunities to promote their services (audio content).

RBT service for the subscriber

The essence of the service: instead of “long beeps” while waiting for a connection, for the caller the called subscriber’s RBT content is playing. It can be a popular melody or song, a personalized voice message, greeting, a joke, or a sound effect. Moreover, you can set one ringtone for all or choose different ringtones for different people, depending on the date, day of the week, and even time of day.

RBT demonstrates the individual attitude of the subscriber to relatives, friends, and even business partners. It also makes it more pleasant to wait for your reply.

It is easy to order and manage the service.

Interaction options:

  • SMS channel: by sending special short messages-commands to the short number of the RBT service
  • Web Channel: Interaction via a Web browser with a RBT service portal
  • RBT service mobile application
  • Interactive Voice Response (IVR) service
  • USSD channel: by sending special USSD commands

Personal and public content

As part of the RBT service, the subscriber can use the content that is uploaded to the T-RBT platform. Depending on who uploaded the content, there are two types of content:

  • Public content – content uploaded by a content provider or content aggregator *.
  • Personal content – content uploaded by the subscriber himself.

*A content provider or content aggregator is engaged in the sale of content belonging to him or the rights to use it to subscribers. If the content is sold through an operator, the operator pays the content provider a part of the income received from subscribers, and the content provider shares this income between the copyright holders, leaving a part of the income for himself.

As a rule, a content provider is a separate organization, but if desired, the operator himself can act as a content provider. The T-RBT platform supports an unlimited number of content providers.

Public content is purchased for a certain period at a certain cost. Whenever purchasing public content T-RBT platform notifies the subscriber about the terms of purchase (term, cost). The conditions for the purchase of content are public information and are available to the subscriber on the official portal of the RBT service.

At the time of purchasing content, the following is made:

  • placing content in the subscriber’s personal library.
  • debiting funds from the subscriber’s account in accordance with the terms of purchase

One of the tasks of the T-RBT platform is to track the period of content purchase and its automatic renewal. The subscriber can at any time refuse to automatically renew or, on the contrary, set such an option.

Personal content is some sound file prepared by the subscriber himself and uploaded to the T-RBT platform. After downloading, personal content undergoes a special authorization procedure in order to check its compliance with certain rules. After successful authorization, personal content can be used as RBT content on a par with purchased public content. 

Personal content does not require automatic renewal. The subscriber can at any time remove content (public or personal) from the library.

Content playback rules

Content that has been placed in the personal library is used as RBT content during an incoming call.

The subscriber can control the playback of content by setting up the playback rules based on two criteria: the caller; day and time of day.

Caller criteria can be as follows:

  • “Play by default” — play RBT content to all callers;
  • “Play to the individual number” — to play RBT content for a specified caller;
  • “Play for a group of numbers” — the set RBT content is played for subscribers included in the group of numbers.

Criteria for day and time of day can be as follows:

  • Play daily“ —  installed RBT content will be played daily all 24 hours or only at certain times (for example, from 9:00 to 18:00);
  • “Play on certain days of the week” — the installed  RBT content will be played on certain days of the week for a full day (for example, Sat-Sun) or at certain times of the day (for example, Mon-Fri from 18:30 to 24:00).
  • “Play monthly” —  the installed RBT content will be played on certain days of the month around the clock or at certain hours (for example, monthly from the 1st to the 12th day from 8:00 to 23:00).
  • “Play annually” —  the installed RBT content will be played annually at a certain date interval around the clock or at certain hours (for example, annually from December 14 to December 31 from 0:00 to 23:00).
  • “Play once” —  the installed RBT content will be played only at a certain date interval around the clock (for example, annually from December 14 to 31) or at certain hours (for example, annually from December 14 to 31 from 6:00 to 15:00).

T-RBT capabilities

T-RBT has an open and extensible architecture, is based on IP technologies, provides scalability and load balancing both at the level of processes and at the level of subsystem instances. To organize reliable service provision, fault tolerance is implemented based on redundancy and clustering technologies.

T-RBT provides a set of open programming interfaces (API) that provides integration with various information systems of both the Operator (for example, billing system, CRM) and Content Providers.

T-RBT allows providing services for subscribers with 2 options: prepaid and postpaid. For the tariffication T-RBT supports the internal product model of services, tariff models, and directories describing charged events and the method of their tariffication. The system allows collecting billed events and organizing online and offline interaction with the Operator’s billing systems.

The tariffication model allows you to set a one-time or periodic payment for services/content available to the subscriber.

Service management is based on supporting the life cycles of a subscriber, services, content, and a set of business processes that describe the states of life cycles and the procedures for the transition between them. The main business processes of subscribers include activation/deactivation of services and content, purchase, donation, copying, content capture, setting the rules for playing content. Additional management capabilities include access to various types of content catalogs, usage history, payment, and notification of services and content. The content provided to end-users is loaded into the system by the Operator itself or partners.

The main business processes for content management include:

  • single and mass loading of content with verification,
  • setting up and promoting content through marketing lists,
  • content price management.

To interact with subscribers, T-RBT allows using the main channels adopted in this kind of system — SMS, IVR, Web, MobileApp. The functionality available to subscribers through a specific channel is based on a basic set of service management functions, taking into account the characteristics of the channel itself. The main channel for notification is SMS, and the main channels for setting up the use of services are Web and MobileApp.

The users of the system are end-users, employees of the Telecom Operator, and employees of partners (for example, content providers). To differentiate access rights to functionality and data, a role model is used to simplify and facilitate the process of managing user connection to the system.

T-RBT service

To service T-RBT, an OAM subsystem with a Web interface is provided. The functionality of the subsystem contains the main sections — user administration, directory management, reporting, setting and launching periodic tasks, system monitoring. The solution also allows you to manage event logging, including setting the depth and scope of business and service protocols.

The system has a two-level structure:

  • Upper level: the BackEnd (BE) subsystem that implements the business functionality for managing content and services. BE modules provide an open API for the information systems of the Operator and Content Providers and contain connectors to various information systems of the Operator, for example, a billing system, an SMS exchange center, etc.
  • Lower level: FrontEnd (FE) subsystem designed to interact with the Operator’s core network and play content for subscribers. A wide variety of codecs can be used while content is playing. Both subsystems are connected with the database of subscribers and services, and the content storage.

T-RBT is deployed on physical or virtual servers running Linux and operates in a J2EE environment.

System-wide scalability is achieved at the level of BE and FE components within a single site, as well as by hosting multiple FE sites in remote data centers for geographically dispersed networks.

Fault tolerance is provided at the FE and BE level of sites by combining physical site servers into a cluster or virtual machines using standard means of a virtual environment, respectively.

The performance of each FE site is determined by the physical and virtual resources provided. The vertical and horizontal scalability of all system components allows achieving of operator-specific performance metrics.

To differentiate user access rights to the functionality and data of the Solution, a role model is used to simplify and facilitate the process of managing user connection to the system.

We will be happy to give you more detail about the T-RBT platform