Case #1


Telecommunication companies (mobile network operators – MNO’s) operate ecosystems whereby third party service providers provide services to the telcos’ users.  Such strategy allows telcos to focus on the core services (such as voice, messaging, and mobile internet). At the same time service providers cooperating with a telco meet users’ needs in such areas as mobile content, entertainment, gaming, information, etc. The more third party offerings come from a telco the more competitive that telco is compared to other telcos.

Still, interworking with third party service and content providers is hampered by variety and technical complexity of operators’ infrastructure, like billing systems, messaging platforms, service delivery mechanisms. For example, whenever a service is provided by a third party, the telco should make a number of real-time decisions, for instance:

  • Whether this particular subscriber is allowed access to this particular service?
  • How to charge this subscriber for this service taking into account the user profile, personal settings, tariff plan, loyalty program, et cetera?
  • What is the service provider and how to maintain message exchange between the subscriber’s mobile device and the service provider’s system?
  • Can this particular service be provided to this subscriber type? For example, some services may be provided to certain groups of subscribers only (prepaid subscribers only, or postpaid only, or members of a loyalty program only)
  • Can this service be delivered to a subscriber, if the subscriber is currently roaming? Some services can be provided to roaming subscribers, only if they use a real-time billing based on CAMEL protocol.

So, the ability of a telco to interoperate with third party service providers have specific technical restrictions. It means that the telco should thoroughly configure each third party service. For example, if the telco interoperates with dozens of third party service providers each having at least ten services, the result will be hundreds, if not thousands, of third party services. It means that at a certain stage manual technical support becomes almost impossible. This is what the need to have a Service Delivery Platform arises from.

At the core of Eyeline SDP is the semantic rule engine utilizing domain specific language (DSL) to create rules.  Semantic logic-based DSL for telco industry allows to effectively reduce the cost of initial development and deployment by at least 5 times and the total cost of ownership by at least 10 times. For telco this means that the initial investment for SDP would be lowered by 10 times, compared to competitive solutions.

Eyeline SDP is used by Mobile TeleSystems (#1 telco in Russian and Eastern Europe and one of the top telcos in the world, NYSE: MBT) since 2010 to provide services to its 100 mln subscribers, specifically:

  • Third party messaging services
  • Self-care services
  • Mobile advertisement
  • Mobile commerce and payments
Case #2

Moscow Parking System

Moscow with more than 17 mln official population is the largest city on the European continent. As a capital of Russia Moscow is the economic, political, cultural and scientific center of Russia. Before Sergey Sobyanin became a governor of Moscow, car parking in the city was a mess. Residents were parking their cars even on sidewalks, thus blocking them. On the other hand, because Moscow is a very old city dating back to XII century, Moscow’s historical center has the radial-circular layout, making car traffic in the downtown hectic and heavy.

To solve this problem the Moscow Government headed by Mr. Sobyanin decided to introduce the system of paid parking all across the city. The second task was to make this service convenient for the residents while taking into account the social aspect: Russia and, specifically, the Moscow region have very sophisticated social programs providing the citizens with different types of benefits, like the benefits for the elderly people, for the families with 2 and more children, for the disabled people, for the veterans, etc.

Another challenge was that the project that started in February 2012 was to be put into operation by the end of 2012.

To meet all these requirements Eyeline SDP was chosen to implement the following components of the Moscow Parking System:

  • Unified payment gateway designed to connect together the users, the mobile telcos, and the banks and payment systems.
  • Messaging gateway as a communication hub between the users, the telcos and the Moscow Parking System.
  • Statistics and Audit services for the technical and user support, as well as for the financial audit.

Eyeline Service Delivery Platform’s semantic rule engine allows to effectively configure complicated business scenarios for payments and service delivery in the Moscow Parking System.

Particularly, the users are able to pay for parking using their credit cards, mobile payment services provided by their respective telcos, and a special parking mobile wallet. The Moscow Parking System as a state-owned service should stay bank agnostic and as such, operate through several payment gateways on the competitive basis. ESDP semantic rules allow in the real-time to choose the routes to payment processing systems with the lowest transaction costs, taking into account users’ personal preferences and the current agreements between the Moscow Gov, the telcos, and the banks.

Eyeline SDP and its semantic rule engine allowed to put into operation one of the most ambitious services in Moscow in the 10 months’ timeframe and meet all sophisticated operational, financial and social requirements stipulated by the Moscow Government.

Case #3

Mobile Money in Nigeria

In 2012 Nigeria central Government has issued a special regulation for mobile money. To avoid monopolization of a new industry mobile telcos were not allowed to operate mobile money by themselves but rather should open their networks to third party service providers. It should be noted that Nigeria was a country with more than 150 mln population and relatively low average income. That’s why the new industry players focused on USSD and SMS as the primary message transport means for implementing their mobile money services.

It created new challenges for Nigerian telcos (MTN, Glo, Etisalat, Airtel) and mobile money providers:

  • How to connect mobile money providers to all the telcos
  • How to make mobile money services reliable
  • How to organize settlements between the telcos and mobile money service providers

Eyeline has helped its partners in Nigeria (Watago Africa) to implement a unified mobile money service gateway connecting all the 4 telcos and 8 mobile money providers. Eyeline Financial Service Delivery Platform (FSDP) and its semantic rule engine allowed to reduce the cost of initial development and setup by 5 times. At the same time Eyeline technology allowed to reduce the costs of development and operation for the third party mobile money providers by 60%. Eyeline FSDP Semantic rule engine is used to solve the following problems:

  • Routing of USSD/SMS messages and financial transactions between the end users, the telcos, and the mobile money providers
  • Financial settlements between the telcos, and the mobile money providers
  • USSD/SMS services QoS control
  • Statistics, accounting and audit (SAA) for settlements and arbitrage between the telcos and the mobile money providers

Application in Various Spheres

Register to join our presale

Join Whitelist