미터링 서버와의 사용량 집계 연동 분석서

참조문서

http://killbill.io/blog/usage-billing/

• Is the usage section specifying to be billed in advance or in arrear?
• Is the usage metric something that is consumed (units) or is it a rate (can go up and down during the period)?

Usage type 분류

• billingMode
  • IN ARREA : 후지급(연체) 방식
  • IN ADVANCE : 선지급 방식
• usageType
  • CAPACITY : 용적(수용량)
  • CONSUMABLE : 소모적

ex)
<usages>
    <usage name="bullets-usage-in-arrear-usage" billingMode="IN_ARREAR" usageType="CONSUMABLE">
or
<usages>
    <usage name="bullets-usage-in-arrear-usage" billingMode="IN_ADVANCE" usageType="CONSUMABLE">
or
<usages>
    <usage name="bullets-usage-in-arrear-usage" billingMode="IN_ARREAR" usageType="CAPACITY">
or
<usages>
    <usage name="bullets-usage-in-arrear-usage" billingMode="IN_ADVANCE" usageType="CAPACITY">

• Capacity in advance (사전 용량 결제):
  • Specify auto-upgrade to higher plan if such plan exists
  • Specify remedial action when user goes beyond limit
• Consumable in advance (사전 소모품 결제):
  • Specify if credit should be automatically be purchased when they drop below a certain level
  • Specify what happens to credits non used in a given period (rollover,…)
  • Specify remedial action if credits expired
• Capacity in arrear (후불 용량 결제):
  • Specify high watermark
  • Specify possible tiers with policy
• Consumable in arrear(후불 소모품 결제):
  • Specify possible tiers with policy

usage 프로퍼티

• Tiers: The in-arrear billing quadrants can be configured using tiers. Those tiers define the price that should be billed depending on the usage. Tiers cannot be used for in-advance billing because billing platform could not know in advance which one to pick.

• Limits: The capacity quadrants need to define limits which are checked against to provide some sort of enforcement. Those limits define the unit and conditions such as max allowed,…

• Blocks: The consumable quadrants need to define blocks, which define a unit of some sort, the size/price of the block.

초기 버젼 목표는 Consumable in arrear 을 지원하도록 코딩한다.