License Tokens

In the context of the Babel Licensing Service, license tokens are used to manage licenses and track their usage. There are two main types of license tokens: floating license tokens and license activation tokens.

Floating License Tokens

In the case of floating licenses, a token represents a client that is connected to the server and using a specific license. When a client requests a license, a token is allocated to that client, indicating that the license is in use. The token remains associated with the client until the client releases the floating license, either explicitly or when the client disconnects from the server. Once the license is released, the token becomes available again for other clients to request.

The use of floating license tokens offers flexibility, as multiple clients can connect to the server and request tokens for the available licenses. This allows for efficient license utilization and enables concurrent usage of licenses among multiple clients. If a license is not actively used or activated, the token associated with that license can be reused, making the allocation of licenses more dynamic.

License Activation Tokens

In the case of license activation, a token represents a client that has successfully activated a license. When a client activates a license, a token is assigned to that client, indicating that the license is activated and tied to that specific client. Activation tokens are typically used when the license is intended for a specific client or device, and it remains associated with that client until the license is deactivated.

Compared to floating licenses, license activation tokens provide a more static allocation of licenses, as the token remains tied to a specific client for the duration of the license activation. This approach is useful when licenses must be specifically assigned or restricted to certain clients or devices.

It’s important to note that in the Server edition of the Babel Licensing Service, there is a limit on the number of active tokens that can be allocated at a given time. This limit determines the maximum number of clients that can be connected and actively using licenses simultaneously. However, if a license is not being used or activated, the associated token can be freed up and made available for other clients to request, maximizing the efficient utilization of licenses.

If the number of license tokens provided by the Server edition is not sufficient for your needs, you have the option to upgrade to the Data Center edition of the Babel Licensing Service. The Data Center edition offers the ability to unlock an unlimited number of tokens, allowing for a higher number of concurrent client connections and license usage.

In summary, license tokens in the Babel Licensing Service play a crucial role in managing licenses and tracking their usage. Floating license tokens enable flexible allocation and dynamic reusability of licenses among multiple clients, while license activation tokens provide a more static assignment of licenses to specific clients. By understanding the different token usage scenarios and considering the available token limits, you can effectively manage and optimize the licensing capabilities of the Babel Licensing Service for your application.

Consumption Tokens

Understanding Consumption Tokens

Consumption Tokens represent a different licensing concept that operates alongside the License Token system. They are used to track and manage the volume of service usage rather than just concurrent connections.

Key characteristics of Consumption Tokens:

• Permanent Consumption: Unlike License Tokens that are allocated and released, Consumption Tokens are permanently consumed when services are used.
• Usage Metering: They measure the actual volume of service usage rather than just connection time.
• Billing Support: They enable usage-based billing models that more accurately reflect the value delivered to customers.
• Detailed Analytics: They provide granular information about how, when, and where services are being used.

Prepaid and Postpaid Models

Consumption Tokens support two primary payment models:

Prepaid Token Model

The prepaid model supports two subscription variants:

Token-Based Prepaid

• Customers buy a specific quantity of tokens upfront
• Tokens are deducted from the balance as they use the service
• When the balance reaches zero, they need to purchase additional tokens
• Tokens may have an expiration date

Money-Based Prepaid

• Customers prepay a monetary amount (e.g., $1000)
• System tracks both monetary balance and equivalent token value using price-per-token
• As services are used, the monetary balance decreases
• More intuitive for customers who think in terms of budget rather than tokens

Postpaid Token Model

In the postpaid model, consumption is tracked during a billing period and charged afterward:

• Consumption is tracked throughout a defined billing period (e.g., monthly)
• At the end of the period, customers are billed based on their actual usage
• Useful for enterprise customers who prefer predictable billing cycles
• Can include minimum usage commitments or volume-based discounts

Integration with License Tokens

Consumption Tokens work alongside the existing License Token system:

1. A client connects to the system and obtains a License Token (for concurrent usage tracking)
2. As the client performs operations, Consumption Tokens are deducted from their balance (for usage volume tracking)
3. When the client disconnects, the License Token is released, but the consumed Consumption Tokens remain used

This dual-token approach provides a comprehensive view of both concurrent usage and total consumption, enabling more flexible licensing models.

Usage Scenarios

Common scenarios for Consumption Token usage:

• API Calls: Track and bill for the number of API requests made
• Processing Time: Charge based on CPU/GPU processing time consumed
• Data Volume: Bill based on the amount of data processed or stored
• Feature Usage: Charge differently for standard vs. premium features
• Hybrid Models: Combine subscription fees with consumption-based charges

Consumption Token Management

The TokenBalanceManager service handles Consumption Token balances, including:

• Creating token balances for customers
• Checking token availability before operations
• Tracking token consumption for each operation
• Generating usage reports for billing and analysis
• Supporting both prepaid and postpaid payment models

For detailed implementation information, refer to the Token-Based Licensing Extension documentation.