A policy server configured to interact with a policy enforcement device (305, 306) to dynamically exclude active service add-ons from bearer throttling for a user terminal, the policy server comprising: at least one processor; and, at least one memory that stores processor-executable instructions, wherein the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby said policy server is operable to: receive, from the policy enforcement device (305, 306), a request for rules, wherein the request comprises an identifier of the user terminal; obtain subscriber information corresponding to the user terminal, wherein the subscriber information is obtained by using the identifier of the user terminal and indicates there is a service add-on which is currently active for the user terminal; and, initiate rules for the user terminal in the policy enforcement device, wherein the rules, which are based at least in part on the subscriber information, indicate that the service add-on is to be excluded from bearer throttling for the user terminal, and wherein the service add-on indicates a defined amount of data that a service corresponding to the service add-on can consume whilst being excluded from bearer throttling, even if a total amount of data subscribed for the user terminal has been consumed. at least one processor; and, at least one memory that stores processor-executable instructions, wherein the at least one processor interfaces with the at least one memory to execute the processor-executable instructions, whereby said policy server is operable to: receive, from the policy enforcement device (305, 306), a request for rules, wherein the request comprises an identifier of the user terminal; obtain subscriber information corresponding to the user terminal, wherein the subscriber information is obtained by using the identifier of the user terminal and indicates there is a service add-on which is currently active for the user terminal; and, initiate rules for the user terminal in the policy enforcement device, wherein the rules, which are based at least in part on the subscriber information, indicate that the service add-on is to be excluded from bearer throttling for the user terminal, and wherein the service add-on indicates a defined amount of data that a service corresponding to the service add-on can consume whilst being excluded from bearer throttling, even if a total amount of data subscribed for the user terminal has been consumed. receive, from the policy enforcement device (305, 306), a request for rules, wherein the request comprises an identifier of the user terminal; obtain subscriber information corresponding to the user terminal, wherein the subscriber information is obtained by using the identifier of the user terminal and indicates there is a service add-on which is currently active for the user terminal; and, initiate rules for the user terminal in the policy enforcement device, wherein the rules, which are based at least in part on the subscriber information, indicate that the service add-on is to be excluded from bearer throttling for the user terminal, and wherein the service add-on indicates a defined amount of data that a service corresponding to the service add-on can consume whilst being excluded from bearer throttling, even if a total amount of data subscribed for the user terminal has been consumed.