Revenue Settlement and Sharing System - RSS RI

Applications/Services and Data Delivery
Contact Person:
Francisco de la Vega
This GE is in support mode, which means that this GE won't have further evolution, being offered and supported in its current version (Release 4 of FIWARE). The functionality provided by the FIWARE Business Framework will be offered by the new Business API Ecosystem GE, which will be released in the release 5 of FIWARE

What you get

The Revenue Settlement and Sharing System (RSS) GE is in charge of distributing the revenues originated by the usage of a given service among the involved stakeholders. In particular, it focuses on distributing part of the revenue generated by a service between the Store Provider and the Service Provider(s) responsible for the service. With the term "service" we refer to both final applications and backend application services (typically exposed through an API). Note that, in the case of composite services, more than one service provider may have to receive a share of the revenues.

Revenue sharing is based on a set of business models (revenue sharing models) which dictate how to distribute revenues. The RSS GE is fed, via available APIs, with these models and additional information regarding service providers. In addition, Charging Data Records (CDRs), based on service usage information, are periodically fed to the RSS GE to enable the revenue sharing process. CDRs must be created by another GE (e.g., the Store GE) and/or external system based on per service specified price models and accounting information.

Different revenue sharing models can be assigned to Service Providers, each of them based on a combination of parameters such as product class or the Store that offers the service. For instance, the revenue sharing model used to calculate payments to a given Service Provider for music may be different from the one used for applications.

The RSS GE exposes an API for other components to send charging information and to manage revenue sharing models. It also features a GUI which can be used by RSS and Store administrators to manage revenue sharing models, access reporting information and perform additional administration tasks.

Additionally to this functionality the RSS GE offers the possibility to consult reports, regarding the CDR received, to both RSS and Store administrators. Example of these reports can be the quantity of amounts received in a period, number of transactions per application provider, or information regarding the most purchased applications.

Finally as a supplementary functionality, expenditure limits functionality is offered in this GE. The expenditure limit API provides a mechanism through which an application provider can limit the amount of money spent by a customer using the services, along a specific time interval. Once this limit is exceeded, it will not be possible to purchase anything until next period of time.

This API exposes the functionality that a provider will use to check the balance and accumulated expenses of a given customer, previously to accept a purchase.

The RSS GE is part of FIWARE's Business Framework and thus can work in close cooperation with other GEs like the Store GE. However, it can also work in a standalone way.

Main capabilities offered include:
  • Storage of trading transactions
  • Definition of revenue sharing models
  • Revenue settlement
  • Revenue reporting capabilities
  • Expenditure control management
For more details, see: RSS GE description

Why to get it

The RSS GE offers advanced revenue management capabilities which enable the proper monetization of your applications and services. Together with the rest of the FIWARE's business framework GEs, it creates a powerful trading environment which will help you reach and interact with a large amount of customers while requiring very little effort from your side. In addition, sophisticated analytics and reporting tools will help you better understand customers behaviour and business trends.

RSS is an implementation of the FIWARE RSS Generic Enabler. More specifically, RSS implements the following APIs and Open Specifications: