IP Library Granted Patent US 9,848,090
Granted Patent B2
US 9,848,090 · App. 13/357,478 · Granted Dec 19, 2017

Offline charging per service data flow

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 9,848,090
App. No.
13/357,478
Granted
Dec 19, 2017
Kind
B2
Abstract

Systems and methods for selecting offline charging functions per service data flow during a data session over a packet data network. One embodiment comprises a Policy and Charging Rules Function (PCRF) that receives information regarding service data flows initiated during a data session over a packet data network. For each of the service data flows, the PCRF selects an offline charging function for the service data flow based on the information for the service data flow, and provides an identifier for the selected offline charging function to a Policy and Charging Enforcement Function (PCEF). The PCEF may then generate charging requests for the service data flow in response to chargeable events, and route the charging requests to the selected offline charging function based on the identifier.

Claims (60)

1. A system comprising:

a Policy and Charging Rules Function (PCRF) comprising a processor configured to receive information regarding a plurality of service data flows initiated during a data session over a packet data network, and to select offline charging functions for the service data flows where multiple offline charging functions are available for offline charging;

for each individual service data flow of the plurality initiated during the data session, the processor of the PCRF is configured to select one of the multiple offline charging functions based on the information for the individual service data flow to act as a primary offline charging function for the individual service data flow, and to provide an address for the primary offline charging function selected for the individual service data flow to a Policy and Charging Enforcement Function (PCEF) to use for offline charging for the individual service data flow;

the processor of the PCRF is configured to connect to the PCEF over a Diameter Gx interface;

the Gx interface includes a new Attribute Value Pair (AVP) that indicates a mapping between each of the individual service data flows and the primary offline charging function selected for each of the individual service data flows; and

the new AVP includes multiple mappings if multiple service data flows exist for the data session.

2. The system of claim 1 further comprising the PCEF, wherein:

for each individual service data flow of the plurality initiated during the data session, the PCEF includes a processor configured to receive the address for the primary offline charging function selected for the individual service data flow from the PCRF, to generate at least one charging request for the individual service data flow in response to a chargeable event, and to route the at least one charging request to the primary offline charging function based on the address.

3. The system of claim 1 wherein:

the processor of the PCRF is further configured to generate a Diameter Gx message, to insert a mapping between the individual service data flow and the address for the primary offline charging function in the AVP, and to transmit the Diameter Gx message to the PCEF.

4. The system of claim 1 wherein:

the primary offline charging function comprises a Charging Data Function (CDF); and

the address for the primary offline charging function comprises an IP address for the CDF.

5. The system of claim 1 wherein:

the processor of the PCRF is further configured to receive the information regarding the service data flows from the PCEF over the Diameter Gx interface.

6. The system of claim 1 wherein:

the processor of the PCRF is further configured to receive the information regarding the service data flows from an Application Function (AF) over a Diameter Rx interface.

7. The system of claim 1 wherein:

the processor of the PCRF is further configured to select a second one of the multiple offline charging functions based on the information for the individual service data flow to act as a secondary offline charging function for the individual service data flow, and to provide an address for the secondary offline charging function selected for the individual service data flow to the PCEF.

8. A method comprising:

receiving information regarding a plurality of service data flows initiated during a data session over a packet data network; and

selecting offline charging functions for the service data flows where multiple offline charging functions are available for offline charging, wherein selecting offline charging functions comprises:

for each individual service data flow of the plurality initiated during the data session,

selecting one of the multiple offline charging functions based on the information for the individual service data flow to act as a primary offline charging function for the individual service data flow; and

providing an address for the primary offline charging function selected for the individual service data flow to a Policy and Charging Enforcement Function (PCEF) to use for offline charging for the individual service data flow;

wherein selecting the primary offline charging function for the individual service data flow and providing the address for the primary offline charging function to the PCEF is performed in a Policy and Charging Rules Function (PCRF);

the PCRF and the PCEF are connected over a Diameter Gx interface;

the Gx interface includes a new Attribute Value Pair (AVP) that indicates a mapping between each of the individual service data flows and the primary offline charging function selected for each of the individual service data flows; and

the new AVP includes multiple mappings if multiple service data flows exist for the data session.

9. The method of claim 8 further comprising:

for each individual service data flow of the plurality initiated during the data session,

receiving the address for the primary offline charging function selected for the individual service data flow into the PCEF;

generating at least one charging request for the individual service data flow in the PCEF in response to a chargeable event; and

routing the at least one charging request from the PCEF to the primary offline charging function based on the address.

10. The method of claim 8 wherein providing the address for the primary offline charging function to the PCEF comprises:

generating a Diameter Gx message;

inserting a mapping between the individual service data flow and the address for the primary offline charging function in the AVP; and

transmitting the Diameter Gx message to the PCEF.

11. The method of claim 8 wherein:

the offline charging function comprises a Charging Data Function (CDF); and

the address for the primary offline charging function comprises an IP address for the CDF.

12. The method of claim 8 further comprising:

receiving the information regarding the service data flows from the PCEF over the Diameter Gx interface.

13. The method of claim 8 further comprising:

receiving the information regarding the service data flows from an Application Function (AF) over a Diameter Rx interface.

14. The method of claim 8 further comprising:

for each individual service data flow of the plurality initiated during the data session,

selecting a second one of the multiple offline charging functions based on the information for the individual service data flow to act as a secondary offline charging function for the individual service data flow; and

providing an address for the secondary offline charging function selected for the individual service data flow to the PCEF.

15. A system comprising:

a Policy and Charging Enforcement Function (PCEF) having multiple offline charging functions available for offline charging;

the PCEF comprising a processor configured to enforce rules on a plurality of service data flows initiated during a data session over a packet data network;

for each individual service data flow of the plurality initiated during the data session, the processor of the PCEF is configured to receive an address for one of the multiple offline charging functions selected by a Policy and Charging Rules Function (PCRF) as a primary offline charging function for the individual service data flow, to generate at least one charging request for the individual service data flow in response to a chargeable event, and to route the at least one charging request to the primary offline charging function based on the address;

the processor of the PCEF is configured to connect to the PCRF over a Diameter Gx interface; and

the Gx interface includes a new Attribute Value Pair (AVP) that indicates a mapping between each of the individual service data flows and the primary offline charging function selected for each of the individual service data flows;

the new AVP includes multiple mappings if multiple service data flows exist for the data session.

16. The system of claim 15 wherein:

the processor of the PCEF is further configured to transmit an initial request to the PCRF for Policy and Charging Control (PCC) rules when the data session is established, and to receive an answer to the initial request from the PCRF that includes a first address for a first offline charging function that is selected for a first service data flow.

17. The system of claim 16 wherein:

the processor of the PCEF is further configured to transmit an update request to the PCRF for PCC rules when the data session is modified to add a second service data flow, and to receive another answer to the update request from the PCRF that includes a second address for a second offline charging function that is selected for the second service data flow.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 22, 2013
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 029858/0206 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 24, 2012
From: CAI, YIGANG; SHARMA, RANJAN
To: ALCATEL-LUCENT USA INC.
Reel/Frame 027587/0527 →