IP Library › Granted Patent US 10,673,817
Granted Patent B2
US 10,673,817 · App. 15/545,080 · Granted Jun 2, 2020

Dynamic policy rule selection

Inventors: Fuencisla Garcia Azorero (Madrid, ES); Victor Ferraro Esparza (Valencia, ES); Ignacio Rivas Molina (Madrid, ES); Filipe Alexandre Rodrigues de Moura Leitao (Heidelberg, DE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04L63/0263H04L41/0893H04L41/5006H04L47/20H04L63/0892H04L63/20H04L41/5022H04L67/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,673,817
App. No.
15/545,080
Filed
Jul 20, 2017
Granted
Jun 2, 2020
Kind
B2
Art Unit
2436
USPC
726/1
Abstract

The invention relates to a method, by a policy controller 100 , for generating policy rules for data packet flows in a communications network. The policy controller 100 has access to a policy database 130 and stores a service level agreement. The service level agreement contains a plurality of different service level identifiers, each service level identifier being associated with a set of conditions that govern the policy rules to be applied to the data packet flows in the communications network. The method comprises the following steps: An authorization request is received for a data packet flow, the authorization request comprising service information for a service and a service level identifier. The policy database 130 is accessed and the set of conditions associated with the received service level identifier is determined. Further, based on the determined set of conditions, a policy rule to be applied to the data packet flow is generated. Policy controller 100 is configured to generate policy rules based on a third party or company profile, with the third party company being able to influence which policy rule should be selected by the policy controller. The authorization request may be received directly from an application function, AF 200 . An input unit 230 is provided via which the third party can define and agree upon the service level agreement with an operator of the communications network. A policy control enforcing function PCEF 51 can interact with the PCRF 100 in order to enforce the policy rules.

Claims (32)

1. A method, by a policy controller, for generating policy rules for data packet flows in a communications network, the policy controller having access to a policy database storing a service level agreement, the service level agreement containing a plurality of different service level identifiers and a plurality of allowable service level data, each service level identifier being associated with a set of conditions that govern the policy rules to be applied to the data packet flows in the communications network, and each allowable service data being associated with a set of further conditions that govern the policy rules to be applied to the data packet flows,

the method comprising the steps of:

receiving an authorization request for a data packet flow, the authorization request comprising service information for a service, a service level identifier, and an allowable service level data,

accessing the policy database and determining a set of conditions associated with the received service level identifier and a set of further conditions associated with the received allowable service level data,

generating, based on the determined set of conditions, a policy rule to be applied to the data packet flow, and

modifying, based on the determined set of further conditions, the generated policy rule.

2. The method according to claim 1 , wherein the determined set of further conditions is used to modify any set of conditions associated with any service level identifier.

3. The method according to claim 2 , wherein the authorization request for the data packet flow comprises a service level data, wherein the method comprises determining that the received service level data corresponds to one amongst the plurality of allowable service level data for the service level agreement stored in the database, and wherein generating the policy rule to be applied to the data packet flow, is based on the set of conditions associated with the received service level identifier and the set of further conditions included in the received service level data.

4. The method according to claim 3 , wherein the received service level data contained in the authorization request is present as an Attribute Value Pair, AVP, in the authorization request.

5. The method according to claim 1 , wherein generating the policy rule includes determining a quality of service parameter to be applied to the data packet flow and a charging information for cost calculation of the data packet flow based on the received service level identifier.

6. The method according to claim 5 , wherein the quality of service parameter and the charging information are determined based on the received service level identifier and the received service level data.

7. The method according to claim 1 , wherein the received authorization request is a request for authenticating a user for which the data packet flow is requested and for authorizing the data packet flow.

8. The method according to claim 1 , comprising the step of transmitting the generated policy rule to a policy enforcing entity of the communications network which enforces the policy rule for the data packet flow.

9. The method according to claim 1 wherein the service level identifier contained in the authorization request is present as an Attribute Value Pair, AVP, in the authorization request.

10. The method according to claim 1 , wherein the received authorization request is generated by an application function entity and received by the policy controller via an Rx interface.

11. The method according to claim 1 , wherein the service level agreement is concluded by an operator of the communications network and a third party, and the received authorization request is received from an application function entity of the third party.

12. A policy controller configured to generate policy rules for data packet flows in a communications network, the policy controller comprising:

a policy database storing a service level agreement, the service level agreement containing a plurality of different service level identifiers and a plurality of allowable service level data, each service level identifier being associated with a set of conditions that govern the policy rules to be applied to the data packet flows in the communications network, and each allowable service data being associated with a set of further conditions that govern the policy rules to be applied to the data packet flows,

a receiver configured to receive an authorization request for a data packet flow, the authorization request containing service information for a service, a service level identifier, and an allowable service level data,

at least one processing unit configured

to access the policy database and to determine a set of conditions associated with the received service level identifier and a set of further conditions associated with the received allowable service level data,

to generate, based on the determined set of conditions, a policy rule to be applied to the data packet flow, and

to modify, based on the determined set of further conditions, the generated policy rule.

13. The policy controller according to claim 12 , wherein the determined set of further conditions is used to modify any set of conditions associated with any service level identifier.

14. The policy controller according to claim 13 , wherein the receiver is configured to receive the authorization request containing a service level data, and wherein the at least one processing unit is configured to determine that the received service level data corresponds to one amongst the plurality of allowable service level data for the service level agreement stored in the database, and to generate the policy rule based on the set of conditions associated with the received service level identifier and the set of further conditions included in the received service level data.

15. The policy controller according to claim 14 , wherein the received service level data contained in the authorization request is present as an Attribute Value Pair, AVP, in the authorization request.

16. The policy controller according to claim 12 , further comprising a transmitter configured to transmit the generated policy rule to a policy enforcing entity configured to enforce the policy rule for the data packet flow in the communications network.

17. The policy controller according to claim 12 , wherein the receiver is configured to receive the authorization request via an Rx interface.

18. The policy controller according to claim 12 , wherein the at least one processing unit is configured to generate, in generating the policy rule, a quality of service parameter to be applied to the data packet flow and a charging information for cost calculation of the data packet flow based on the received service level identifier.

19. The policy controller according to claim 18 , wherein the at least one processing unit is configured to generate the quality of service parameter and the charging information based on the received service level identifier and the received service level data.

20. The policy controller according to claim 12 , further being configured to operate as a policy and charging rules function of the communications network.

21. The policy controller according to claim 12 , wherein the service level identifier contained in the authorization request is present as an Attribute Value Pair, AVP, in the authorization request.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 20, 2017
From: ESPARZA, VICTOR FERRARO; AZORERO, FUENCISLA GARCIA; MOLINA, IGNACIO RIVAS; RODRIGUES DE MOURA LEITAO, FILIPE ALEXANDRE
To: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL)
Reel/Frame 043055/0218 →
Continuity (1)
Related Publication 20180007009A1 · Jan 4, 2018
Cited By (1)
US 12,301,629