openbrm€¦ · microservices and api driven architecture make this platform technology and ......

15
OpenBRM WHITEPAPER V1.1 OpenBRM Billing & Revenue Management System on Blockchain (BRM) OpenBRM WHITEPAPER

Upload: others

Post on 30-May-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

OpenBRM WHITEPAPER V1.1 

  

 

 

 

 

OpenBRM 

 

 

Billing & Revenue Management System on Blockchain (BRM)     

OpenBRM WHITEPAPER 

Page 2: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

1  OpenBRM WHITEPAPER V1.1 

Overview OpenBRM is a carrier-grade billing platform aimed at telecommunications, Subscription, Utilities and logistics organizations. Built using state of the art but future proof technology. 

Customer Billing and Revenue management is an essential part of any business. A sophisticated and flexible billing system is key to service delivery and efficient billing thus better revenue management. 

In modern competitive landscape it is important for any business to be able to rapidly design service offerings and delivery will give an edge for a business to win the customers. 

The proposed ‘OpenBRM on Blockchain’ will leverage the inherent technological benefits of blockchain to replace the traditional COTS applications by a flexible, scalable, secure and transparent platform benefitting both service providers (Billers) and consumers.  

We are a team of techno-functional experts having varied experience ranging from 6 - 15 years in BRM domain. We have delivered dozens of deployments based on traditional COTS and current OpenBRM (non-blockchain) to various businesses across the world. 

Problem with traditional BRM solutions There are numerous operational and technical limitations to current COTS systems given they are closed source, most of them lack versatility, sometimes flexibility within the scope of system it is made for. 

Challenges for businesses (Billers) 

● Closed source making backoffice IT teams heavily rely on documentation and product support delaying solution testing and delivery thus affecting business goals 

● Lack of versatility meaning a COTS product from a vendor caters mostly to a specific domain or business type (ex : ISP Billing system works only for ISP not for Utilities) 

● Designs are mostly rigid limiting the extensions possible ● These products mostly built on old technology stacks ● It is really tough or sometime impossible to adapt latest technologies ● Integrations need third party interfaces or middleware making it more complex ● Deployed on tradition IT infrastructure leaving it unscalable or limited scalable ● Uses typical RDBMS with hard coded data models and isolated from other 

applications. It is not possible to share data across different applications without effort 

● Payment gateway commissions and banking delays ● Bottlenecks in cross borders transactions 

OpenBRM WHITEPAPER 

Page 3: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

2  OpenBRM WHITEPAPER V1.1 

 

Challenges for end-users or customers 

● Discovery of service providers requires good time and research ● Every service provider has their own apps, websites making it time consuming and 

confusing to compare and choose services ● Lack of common payment channel across the globe ● Switching and portability from one provider to other requires repeated KYC ● Transparency in usage billing and payments 

Solution using Blockchain for BRM Building Billing and Revenue Management system on Blockchain is going to be a game changer with EOS.IO blockchain inherent technological benefits and BRM core library on top. EOS.IO plugin architecture eases the BRM platform development and gives greater flexibility to functional modules to cater to dynamic DAPP requirements. 

The following will address the problems for business (Biller)  

● BRM is going to be an open source platform like EOS on top of EOS.IO ● DAPPS on top of BRM core really makes it versatile meaning providing functionality 

required by different business types in the same platform ● Design is based on OS - App philosophy. BRM core and flexible DAPP development 

will solve the ‘Limited by Design problem’ ● Microservices and API driven architecture make this platform technology and 

programming interface agnostic for DAPPS ● Distributed processing giving more power to functional modules ● Replacing RDBMS with EOS IPFS will help developers extend the data model with 

ease. It also help sharing data across multiple applications ● Provides potential customer history and KYC ● Unified payment method using tokens reduces delays and commissions free 

transactions 

What is for end users (consumers) 

● A single place to discover, compare and choose services (providers) ● A place to manage all subscriptions and payments from one place and one account ● Works similar to single sign-on ● Transparency in usage billing and payments ● Easy payment through tokens ● Fringe benefits from platform revenues 

 

OpenBRM WHITEPAPER 

Page 4: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

3  OpenBRM WHITEPAPER V1.1 

Multi-Layer & Multi-Dapp Architecture:  

 

 

 

 

 

BRM Tokens are used as utility token for all the dapps build on BRM Platform. 

 

 

 

OpenBRM WHITEPAPER 

Page 5: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

4  OpenBRM WHITEPAPER V1.1 

Architecture The following high level architecture diagram describes the proposed BRM platform on EOSIO blockchain. 

 

 

 

EOSIO EOS.IO is a blockchain protocol powered by the native cryptocurrency EOS. The protocol emulates most of the attributes of a real computer including hardware (CPU(s) & GPU(s) for processing, local/RAM memory, hard-disk storage) with the computing resources distributed equally among EOS cryptocurrency holders. EOSIO operates as a smart contract platform and decentralized operating system intended for the deployment of industrial-scale decentralized applications through a decentralized autonomous corporation model. The smart contract platform claims to eliminate transaction fees and also conduct thousands of transactions per second. 

 

 

 

OpenBRM WHITEPAPER 

Page 6: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

5  OpenBRM WHITEPAPER V1.1 

BRM Core Billing and Revenue Management (BRM) core is a software library built on top of EOS platform, leveraging EOS services like computational power, storage and security.  

BRM consists of functional modules which helps to build business DAPPs on top. 

Hence BRM Core should be seen more as platform or a framework rather than a mere software package. BRM Core offers necessary API and Utilities that are common in a BRM system. 

Some core functions include the following 

● Customer management ● Product catalogue ● Charging and Billing ● Revenue recognition and GL ● Payments & Collections ● Partner management and Resellers ● Data encryption, security and storage  ● Integration hooks to enable third party system integration ● Call back hooks 

 

Privacy Layer It is necessary for Billers to keep the customer data safe and secure and follow the state laws to protect sensitive information hence BRM core provides necessary functions to achieve this requirement. 

Privacy Layer is part of BRM Core library where customer data is encrypted and stored with privacy options. BRM core will explore readily available third party privacy solutions like Priveos or build custom layer based on the compatibility and feasibility. 

DAPP Layer DAPP layer is where the business applications are built on top of BRM Core for each specific industry. DAPPs for Utility, Subscription, Telecom and Finance industries will be built as part of original scope of development of OpenBRM project. DAPPs development is not limited to the above but we continue to support advanced use cases like IoT, M2M apps and more. 

 

 

OpenBRM WHITEPAPER 

Page 7: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

6  OpenBRM WHITEPAPER V1.1 

  

 

Market Place Market place is the visible component of the OpenBRM platform where both Service Provides aka Billers can onboard with relevant DAPPS and start advertising their services and accept customer signups. Billers can also push bills to the customers without established relations in advance. 

On the other hand, consumers can discover service providers, find services/products, compare, choose and signup or pay utility bills through OpenBRM platform. 

BRM Token BRM is the utility token used for making payments for DAPPs running on BRM platform. 

Using native BRM token will eliminate middleman commissions and banking delays. 

Since BRM platform is going to be a global platform with users (Billers and Customers) from different parts of the world, a common BRM token will eliminate the need of currency conversion and help to standardise the payment processing. 

Payments made using BRM tokens might fetch discounts on DAPP subscription fee to Billers (Service Provider). More details to come along with platform launch. 

OpenBRM WHITEPAPER 

Page 8: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

7  OpenBRM WHITEPAPER V1.1 

How it works For Business users / Service Providers aka Billers 

 Service Providers aka Billers subscribe to DAPPS like Utility/Telecom/Logistic Billing for a subscription fee which generates revenue for BRM platform. Billers then start creating offers for the potential customer as smart contract and advertise on the market place. 

For end users / customers  

 

A person looking for any service like internet or mobile connection can find suitable offers on BRM marketplace, place an order and signup. BRM will seamlessly associate the customer with chosen provider. Billers DAPP will take care of service delivery, billing and payments. 

 

 

OpenBRM WHITEPAPER 

Page 9: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

8  OpenBRM WHITEPAPER V1.1 

Marketplace BRM Marketplace is a transparent ecommerce platform where customers and service providers are connected. The uniqueness about this marketplace is that all the interactions are governed by blockchain protocol establishing trust. Mockups@ https://app.moqups.com/[email protected]/z012TJJfT1/view/page/ad64222d5?ui=0 

 

OpenBRM WHITEPAPER 

Page 10: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

9  OpenBRM WHITEPAPER V1.1 

Roadmap 

 

OpenBRM WHITEPAPER 

Page 11: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

10  OpenBRM WHITEPAPER V1.1 

Token Distribution Tokens are issued based on EOS account snapshot taken on 24th Dec 2018. 

Initial airdrop of BRM tokens issued to users holding EOS greater than 500 at 1:1 ratio followed by an airgrab to all other users, amounting to 5% of total tokens. 

Airdrop completed for the EOS holders on Chaince exchange. 

Monthly reward drops starts March 1st 2019. Each month tokens will be rewarded to existing token holders in the ratio of 4:1 for contribution on OpenBRM platform in form of simple tasks like registration, surveys, voting, review, rating etc. 

30% of tokens is locked for reserve funding. 5% of reserve funding tokens will be released every year for platform development and operational enhancement purposes. 

7% of the tokens will be converted EOS tokens required for running BRM on the EOS network. 

 

 

 

OpenBRM WHITEPAPER 

Page 12: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

11  OpenBRM WHITEPAPER V1.1 

 

 

Revenue generated by BRM DAPPs will be converted to BRM tokens and the same will be distributed as outlined in the above flow chart. 

 

OpenBRM WHITEPAPER 

Page 13: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

12  OpenBRM WHITEPAPER V1.1 

Reward Drop 

35% of the BRM tokens from the revenue will be distributed to token holders for completing simple tasks like registration, survey, voting, rating and reviews. 

Reward DAPP 

10% of the BRM tokens from the revenue will be used to develop new DAPPs. New DAPPs will use BRM token. If any new token is created, we will try to distribute them to BRM token holders. However, our goal is to use BRM token for all new DAPPs to avoid extra costs (RAM etc) involved in creating new tokens. 

Reward non BRM token holders 

5% of the BRM tokens from the revenue will be distributed to non BRM token holders for contributing to BRM platform (registration, referrals) which might help add more users to the platform. 

Funding for BRM platform development 

5% of the reserved funding will be released every year to support development and operational costs of BRM platform. 

Advertising revenues 

Revenue generated by advertisements will be converted to BRM tokens and will go through the same flow as shown in the flow chart. 

 

 

 

Declaimer When using BRM tokens, users must take their local laws and regulations into consideration and avoid violation. We do not make any form of commitment, nor guarantee of the intrinsic value and appreciation of our token BRM.  

We didn't conduct any private or presale for BRM tokens. Token distribution was purely done through airdrops and air grabs.   

 

OpenBRM WHITEPAPER 

Page 14: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

13  OpenBRM WHITEPAPER V1.1 

Reward Drop 

After Initial Airdrop/Airgrab is completed Reward drop Tokens will be distributed to BRM token holders over a period of 6 months starting March 1st 2019. 

Reward drop tokens are allocated to reward users who believe in BRM project and support project development by completing simple tasks on BRM platform. 

Following Steps needs to be completed to be eligible for Monthly Reward drops:: 1. Stake BRM tokens. Unstaking will take 10 days to unlock tokens 2. Register and complete simple Monthly tasks on BRM platform 

Multiple snapshots are taken each month to calculate average staked BRM token holdings of month. Each month 4 snapshots are taken once every 7 days on dates (7,14,21,28). 

Reward Drop Registration start Date : Feb 1st 2019. 

BRM Token staking start Date : Feb 10 2019 

First Reward Drop Date : Mar 1st 2019. 

 

Monthly Distribution Details:   

BRM Tokens will be distributed in the ratio of 4:1 to the BRM token holders. If you are holding 1000 tokens you get 250 tokens each month. 

Top 20% gets additional 5% and Top 5% gets additional 10% tokens.  

 

  Ratio  Reward Drop %  Total % Reward Drop received 

All Token Holders  4:1  25% of BRM holdings  25% of BRM holdings 

Top 20% Holders    Additional 5%  30% of BRM holdings 

Top 5% Holders    Additional 10%  35% of BRM holdings 

 

Examples of Monthly Reward Drop Distribution: 

  BRM holdings Rank  BRM holdings  Reward %  Reward count 

User1  300 (Below 20%)  100  25%   25 

User2  99 (Top 20%)  1000  30%   300 

User3  5 ( Top 5%)  10,000  35%   3500 

OpenBRM WHITEPAPER 

Page 15: OpenBRM€¦ · Microservices and API driven architecture make this platform technology and ... Hence BRM Core should be seen more as platform or a framework rather than a mere

14  OpenBRM WHITEPAPER V1.1 

 

Team 

We are a team of 12 people with experience in customizing and building Billing Solutions for various business types including Utility, Telecom, Logistic and Finance but not limited. 

We are planning augment more members (20 EOY 2019) to the team to speedup the development. 

We have been in this business for over a decade and have had numerous implementation based on OpenBRM and other COTS Billing solutions world wide. 

Since the blockchain has been emerging as the promising technology for future, we have been envisaging the idea of moving traditional Billing and Revenue Management system functionality to the blockchain.  

 

Hanumantha Marikanti Chief architect with over 15y. of expertise in building Enterprise applications. Hands on C/C++/Java and scripting languages like Javascript, python, php and perl 

Ayyapa Raju BRM SME with over 15y. of  expertise in BRM applications. Hands on C/C++ programmer. 

Swagath Pondugula Tech Operation with 12y of experience in handling large scale projects from inception to go-live. Skilled in C++/Java and web technologies 

Sampath Konka Senior Developer with over 10y. of expertise in Java programming   

Anvesh Koya Senior Developer with over 10y. of expertise in Java programming 

Venkatesh Koleti UI Lead with 10+y of experience. Expert in making cool web apps 

Ravinder Annaram UI Dev with over 8y of experience in developing responsive web pages 

Mamatha Rapolu Junior Dev with over 5y of experience in Java programming  

Sindhu Bodige Junior Dev with over 5y of experience in Java programming 

Sandeep Pudi Junior Dev with experience in Java programming 

Sridhar Dividi UI Dev. Experience in developing web pages 

Gayatri Marikanti Program Director 

Sasidhar Reddy Pakala Tech Lead with 12y. of expertise in C/C++/Java and BRM application. Has been working with BRM product development since its inception 

   

   

OpenBRM WHITEPAPER