The usage economy is a pay for use based business environment that strives to offer an optimized exchange of value between businesses and their customers.
By utilizing usage based pricing and service delivery, businesses can offer the right price point without leaving money on the table for customers that are seeking to pay for what they use.
Mediate usage feed data from multiple different file formats. LogiSense's powerful data transformation engine allows you to receive usage file export formats in real time from your communications switch and run mediation logic to aggregate and transform the usage data.
One or more filters can be applied for any of the sources of data. Filters that can be used to determine if a line in a source data set (File) should be processed through mediation or ignored. As an example, a given source of data may contain a field called Record Type (First Ordinal position on the line) that indicated a “Record Type”. A filter can be setup such that Only lines with a Record Type value of “6” are to be processed. All other lines are ignored.
Many data Sources have variable mappings of source data elements to a Usage record. The mediation process can be set up to account for this. For example, if the line is identified as an "SMS-MO" record the system may use field 5 for the Usage identifier where as if it is SMS-MT it may use field 6. It is also possible to have different source fields mappings based on Conditional statements. For example, a Carrier might send twenty fields. When field 5 has a value of "SMS" the mediation process would use fields 1-6, 10,14,19 ignore the rest and when it has a value of "DATA" it would use 1-6, 9, 11, 13-16.
Determination of a usage class is usually a function based on conditions specific to data in the source or the source itself. EngageIP provides options for managing this thereby allowing reuse of rules and consistency in setting Usage Class values.
One or more "normalization" functions can be created to format things like phone numbers, IP addresses into common inputs. The following types of normalization can be performed on the feed:
|Normalization Function Type||Definition|
|Phone Number||Normalize the Phone Number|
|Country||Normalize Country and Country Code|
|Network||Normalize the network|
|Date/Time||Normalize the date and or time|
|Usage Identifiers||Normalize usage identifiers|
|Units of Time||Normalize units of measure (time, data etc.)|
Mathematical functions like Sum or Multiplication can also be performed on feeds in order to prepare them for rating. For example, a source that sends data usage in Upload and Download will have to have a sum process applied as well as possible normalization on the whole or parts to a standard unit (i.e. KB).
EngageIP has a powerful rating and mediation engine that can rate any type of usage event in real time or batch. Usage data can take the form of a CDR record or it can take the form of another type of usage feed. The usage data is supplied via API, SFTP or other outbound methods as required.
Because each record will have its own proprietary format, a mediation layer is designed for each solution to format the data into a Usage Data Record (UDR) that can be processed by the rating engine.
Whether you have location specific rates, on-net, off-net or conditional rates based on time of day, custom logic or specific rounding rules; LogiSense's conditional rating engine allows for classification and charging of any kind of usage.
Quickly Launch New Products
LogiSense's 2-tier product catalog allows Product Managers to define, configure and bring new products to market faster than your competitors. Don't let your billing system hold you back from launching a product to meet a market opportunity.
Billing as a Service
Quickly grow your channel partner and reseller organizations by eliminating their overhead of a billing system. Provide billing as a service to unburden your channels to grow quicker!
LogiSense can provide a PCI DSS Level 1 Certified hosting infrastructure to meet your business needs. Our customers have enjoyed the benefits of billing integrations with many different Payment Processors.
A Share Plan is an entity that defines the rules and parameters around how usage is to be shared. These include the following attributes:
|Data Type||The type of data that is being shared. Buckets can be attached to a share plan representing the class of data that is being shared.|
|Activation Rule||The activation rule specifies the mechanism for activation of a share plan. Share plans can be activated through two mechanisms: (1) A selling service which means the selling service has to be sold to the account in order to activate the share plan. (2) A participating service which means that the participating service needs to be sold to an account in order to activate the share plan|
|Contributing and Participating Services||Participating services are services that participate in a share plan – i.e. applicable usage associated with that service are pooled with that share plan. Each participating service specifies a contribution amount. A contribution amount greater than 0 indicates that the service not only participates but also grows the share plan.|
|Growth||Share Plans can have fixed or variable sized buckets. With a fixed bucket all participating share the same pool of usage and the pool size remains the same irrespective of the number of services that participate in the plan. With a variable share plan, the share plan grows by a contribution amount for each contributing service.|
|Share Level||Share level specifies the level at which sharing occurs. A share level of parent indicates that all accounts and services that report to that parent are eligible to participate in the share plan. A share level of account indicates that all services that are assigned to that account are eligible to participate in the share plan.|
|Usage billing frequency||The frequency at which usage gets billed (monthly, weekly, yearly etc.) for the share plan.|
Configuration of a share plan occurs at the catalog level where the administrator defines the various attributes listed above. The administrator also chooses the participating services or service type that can participate in the share plan.
Service types are useful when the intent is to enable sharing for all services of a certain category – for instance any type of SMS service can participate in the share plan. Once the share plan is defined and saved, the service provider can then define the share plan buckets and set contribution rules.
Bill on first use scenarios are gaining more prominence particularly in certain verticals such as IoT . A service is not billed until a certain usage threshold is reached or a configurable period of time has expired. Once either of these conditions are met, subscription and usage billing is triggered and the state of the service is transitioned (e.g. preactive to active).
As part of this workflow, EngageIP also provides a facility to optionally add a time window for when usage needs to come in. If no usage comes in within that timeframe, then the state change is triggered and any applicable one time and recurring charges due to the state change will be charged to the account.