Figure C.27 - Customer Billing Account Balance, Part 3

CustomerBillingAccountBalance represents and tracks the amount remained or owed in certain CustomerBillingAccount. The attribute remainedAmount is Quantity type. Here Quantity type represents both non-monetary balance and monetary balance. Non-monetary balance is applied to the service usage volume and monetary balance is applied to the monetary amount. <br/>BalanceUsageRule is balance-level rule information constraining the application of CustomerBillingAccountBalance. It could describe the sharing rule, by which CustomerBillingAccountBalance could be shared between different kinds of FinancialCharge which is related to different customer’s product charge. It could emphasize associated CustomerBillingAccountBalance is only applicable for certain usage, for example only applicable for local phone call or domestic flow or intra-PLMN SMS. FinancialChargeSpec could be applied to BalanceUsageRule to help to describe specification of FinancialCharge and relate them to the sharing information and the private usage information. BalanceUsageRule also includes priority and other kinds of rules limits the application of CustomerBillingAccountBalance. For example, the refund SMS account balance should be used before monetary account balance when SMS is used.<br/>The payment model presented here is intended to support a converged payment model for both prepaid and postpaid condition. PaymentPlan could trigger CustomerPayment activities after Bill/AppliedCustomerBillingRate is calculated out. AccountBalancePM defines possible payment method using CustomerBillingAccountBalance as payment source. When CustomerBillingAccountBalance is the payment source, BalanceUsageRule constraints carrying out of payment activities.<br/>Payment activity area is as shown in the Figure C.27 below.  <br/>