Redesigning Radius + Mysql authentication to use bandwidth capping, traffic, time and huntgroups within the same radius DB.

I require some help in changing the authentication design for the radius AAA server / client components and /or via SQL scripting I currently have. The components involved are radius clients, radius server, mysql with a default radius db installed on mysql. The radius uses huntgroups to check that a user is allowed to come through a given server IP. I would like to move away from the solely time based subscription and introduce a traffic and bandwidth utilisation over a monthly, quarterly, bi-annually or yearly period instead. It should be possible for the user of a particular subscription period to have unlimited traffic and bandwidth based if they choose for such a particular type of subscription package. It should also be possible for a user to purchase a permanent quota of data transfer for a period of time that does not expire as well as purchasing a quota for a period of time that does expire after x days. So in summary there are a couple of types of packages available. First the subscription based on time and data amount. The second is based on pure data and the third is a period of time but without limitations on the amount of data. The addition of bandwidth speed should be able to be applied to certain packages where possible. When two plans co-exist the plan based on time and data should be used first, this is, subscription quotas will always be consumed before permanent quotas. All packages should also factor in hunt groups. This is already setup so the assumption is that no extra changes need to be made here to the existing setup. The above should be easily done by someone familiar with the workings of radius, it's associated attributes and the various configuration files available in radius.