Floating License Diagram

This diagram illustrates the complete floating license process including request, usage, heartbeat verification, and release:

1. The user launches the application.

2. The application reads the user key from its configuration.

3. The application sends a request to the Babel Licensing Service for a floating license, including the user key and a unique client ID.

4. The service verifies the license exists in the database.

5. The service validates the license, checking expiration and revocation status.

6. The service checks if there are licenses available in the floating pool.

7. If licenses are available:

   • The service allocates a floating token and associates it with the client ID

   • The application receives the license token and enables full functionality

   • The application sends periodic heartbeats to maintain the license

   • When the user exits or manually releases the license, the token is returned to the pool

8. If no licenses are available:

   • The service returns an error

   • The application displays a message to the user

This sequence diagram highlights the dynamic nature of floating licenses, where licenses are temporarily allocated during use and then returned to the pool when released, making them available for other users.