| Sonstiges: |
- Nachgewiesen in: USPTO Patent Applications
- Sprachen: English
- Document Number: 20150350093
- Publication Date: December 3, 2015
- Appl. No: 14/287631
- Application Filed: May 27, 2014
- Assignees: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL) (Stockholm, SE)
- Claim: 1. A policy server configured to interact with a policy enforcement device 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 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, initiating 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.
- Claim: 2. The policy server of claim 1, further operable to: detect that the service add-on is no longer currently active for the user terminal; and modify the rules to indicate that the service add-on is not to be excluded from the bearer throttling for the user terminal; and, initiate the modified rules for the user terminal in the policy enforcement device.
- Claim: 3. The policy server of claim 1, wherein: the service add-on indicates that bandwidth of service traffic associated with a corresponding service is to be limited to a defined value after the user terminal consumes a defined amount of data associated with the corresponding service during a defined time period; and, the bearer throttling entails limiting the bearer bandwidth to the defined value after the user terminal has consumed the defined amount of data during the defined time period.
- Claim: 4. The policy server of claim 1, wherein: the policy server implements a Policy and Charging Rules Function (PCRF); the policy enforcement device implements at least one of a Policy and Charging Enforcement Function (PCEF) and a Traffic Detection Function (TDF); and, the rules are Policy and Charging (PCC) rules or Application Detection and Control (ADC) rules.
- Claim: 5. The policy server of claim 1, wherein: the rules comprise a parameter which is set to indicate that the service add-on is to be excluded from bearer throttling for the user terminal, the parameter being an Exclude-From-Bearer-Throttling Attribute Value Pair (AVP).
- Claim: 6. A method in a policy server which interacts with a policy enforcement device to dynamically exclude active service add-ons from bearer throttling for a user terminal, the method comprising: receiving, by the policy server, a request for rules, wherein the request comprises an identifier of the user terminal; obtaining, by the policy server, 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, initiating, by the policy server, 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.
- Claim: 7. The method of claim 6, further comprising: detecting, by the policy server, that the service add-on is no longer currently active for the user terminal; modifying, by the policy server, the rules to indicate that the service add-on is not to be excluded from the bearer throttling for the user terminal; and, initiating, by the policy server, the modified rules for the user terminal in the policy enforcement device.
- Claim: 8. The method of claim 6, wherein: the service add-on indicates that bandwidth of the service traffic associated with a corresponding service is to be limited to a defined value after the user terminal consumes a defined amount of data associated with the corresponding service during a defined time period; and, the bearer throttling entails limiting the bearer bandwidth to the defined value after the user terminal has consumed the defined amount of data during the defined time period.
- Claim: 9. The method of claim 6, wherein: the policy server implements a Policy and Charging Rules Function (PCRF); the policy enforcement device implements at least one of a Policy and Charging Enforcement Function (PCEF) and a Traffic Detection Function (TDF); and, the rules are Policy and Charging (PCC) rules or Application Detection and Control (ADC) rules.
- Claim: 10. The method of claim 6, wherein: the rules comprise a parameter which is set to indicate that the service add-on is to be excluded from bearer throttling for the user terminal, the parameter being an Exclude-From-Bearer-Throttling Attribute Value Pair (AVP).
- Claim: 11. A policy enforcement device configured to interact with a policy server to dynamically exclude active service add-ons from bearer throttling for a user terminal, the policy enforcement device 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 enforcement device is operable to: obtain rules for the user terminal from the policy server, wherein the rules indicate that a service add-on is to be excluded from bearer throttling for the user terminal; detect service traffic to or from the user terminal; and, determine if the service traffic matches the service add-on; if the service traffic matches the service add-on, then apply enforcement actions in the rules such that the service traffic of the service add-on is excluded from the bearer throttling for the user terminal; or, if the service traffic does not match the service add-on, then apply enforcement actions in the rules such that the service traffic is not excluded from the bearer throttling for the user terminal.
- Claim: 12. The policy enforcement device of claim 11, further operable to: send a request for rules to the policy server upon a session establishment for the user terminal, wherein the request comprises an identifier of the user terminal.
- Claim: 13. The policy enforcement device of claim 11, further operable to: if the service traffic matches the service add-on, then send a default bearer quality-of-service modification towards an entity handling resources for the default bearer, wherein the default bearer quality-of-service modification indicates a higher load is possible than a currently set load for the default bearer due to the service add-on being excluded from the bearer throttling for the default bearer quality-of-service.
- Claim: 14. The policy enforcement device of claim 11, further operable to: obtain modified rules for the user terminal from the policy server, wherein the modified rules now indicate that the service add-on is not to be excluded from the bearer throttling for the user terminal; and, apply enforcement actions in the modified rules such that the service traffic of the service add-on is not excluded from the bearer throttling for the user terminal.
- Claim: 15. The policy enforcement device of claim 11, wherein: the service add-on indicates that bandwidth of the service traffic associated with a corresponding service is to be limited to a defined value after the user terminal consumes a defined amount of data associated with the corresponding service during a defined time period; and, the bearer throttling entails limiting the bearer bandwidth to the defined value after the user terminal has consumed the defined amount of data during the defined time period.
- Claim: 16. The policy enforcement device of claim 11, wherein: the policy enforcement device implements at least one of a Policy and Charging Enforcement Function (PCEF) and a Traffic Detection Function (TDF); the policy server implements a Policy and Charging Rules Function (PCRF); and, the rules are Policy and Charging (PCC) rules or Application Detection and Control (ADC) rules.
- Claim: 17. The policy enforcement device of claim 11, wherein: the rules comprise a parameter which is set to indicate that the service add-on is to be excluded from bearer throttling for the user terminal, the parameter being an Exclude-From-Bearer-Throttling Attribute Value Pair (AVP).
- Claim: 18. A method in a policy enforcement device that interacts with a policy server to dynamically exclude active service add-ons from bearer throttling for a user terminal, the method comprising: obtaining, by the policy enforcement device, rules for the user terminal from the policy server, wherein the rules indicate that a service add-on is to be excluded from bearer throttling for the user terminal; detecting, by the policy enforcement device, service traffic to or from the user terminal; and, determining, by the policy enforcement device, if the service traffic matches the service add-on; if the service traffic matches the service add-on, then applying by the policy enforcement device enforcement actions in the rules such that the service traffic of the service add-on is excluded from the bearer throttling for the user terminal; or, if the service traffic does not match the service add-on, then applying by the policy enforcement device enforcement actions in the rules such that the service traffic is not excluded from the bearer throttling for the user terminal.
- Claim: 19. The method of claim 18, further comprising: sending a request for rules to the policy server upon a session establishment for the user terminal, wherein the request comprises an identifier of the user terminal.
- Claim: 20. The method of claim 18, further comprising: if the service traffic matches the service add-on, then sending a default bearer quality-of-service modification by the policy enforcement device towards an entity handling resources for the default bearer, wherein the default bearer quality-of-service modification indicates a higher load is possible than a currently set load for the default bearer due to the service add-on being excluded from the bearer throttling for the default bearer quality-of-service.
- Claim: 21. The method claim 18, further comprising: obtaining, by the policy enforcement device, modified rules for the user terminal from the policy server, wherein the modified rules now indicate that the service add-on is not to be excluded from the bearer throttling for the user terminal; and, applying, by the policy enforcement device, enforcement actions in the modified rules such that the service traffic of the service add-on is not excluded from the bearer throttling for the user terminal.
- Claim: 22. The method of claim 18, wherein: the service add-on indicates that bandwidth of the service traffic associated with a corresponding service is to be limited to a defined value after the user terminal consumes a defined amount of data associated with the corresponding service during a defined time period; and, the bearer throttling entails limiting the bearer bandwidth to the defined value after the user terminal has consumed the defined amount of data during the defined time period.
- Claim: 23. The method of claim 18, wherein: the policy enforcement device implements at least one of a Policy and Charging Enforcement Function (PCEF) and a Traffic Detection Function (TDF); the policy server implements a Policy and Charging Rules Function (PCRF); and, the rules are Policy and Charging (PCC) rules or Application Detection and Control (ADC) rules.
- Claim: 24. The method of claim 18, wherein: the rules comprise a parameter which is set to indicate that the service add-on is to be excluded from bearer throttling for the user terminal, the parameter being an Exclude-From-Bearer-Throttling Attribute Value Pair (AVP).
- Current International Class: 04; 04; 04
|
