IP Library Granted Patent US 9,350,876
Granted Patent B2
US 9,350,876 · App. 12/974,892 · Granted May 24, 2016

Methods, systems, and computer readable media for detecting initiation of a service data flow using a Gx rule

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,350,876
App. No.
12/974,892
Granted
May 24, 2016
Kind
B2
Abstract

Methods, systems, and computer readable media for detecting a service data flow using a Gx rule are disclosed. According to one method, a policy and charging rules function (PCRF) node sends to a policy and charging enforcement function (PCEF) node, a Gx rule for triggering the PCEF node to generate a notification message upon initiation of a service data flow. The PCEF node receives and installs the Gx rule and uses the Gx rule to detect and report initiation of a service data flow.

Claims (29)

1. A method for detecting initiation of a service data flow using a Gx rule, the method comprising:

sending, by a policy and charging rules function (PCRF) node to a policy and charging enforcement function (PCEF) node, a first Gx rule for triggering the PCEF node to generate a notification message upon initiation of a service data flow associated with an application that is unknown to the PCRF node when the first Gx rule is sent, wherein the first Gx rule lacks a service identifier parameter, wherein each of the PCEF node and the PCRF node includes a processor and a memory;

receiving and installing, by the PCEF node, the first Gx rule;

using, by the PCEF node, the first Gx rule to detect and report initiation of the service data flow associated with the application, wherein using the first Gx rule to detect and report initiation of the service data flow comprises detecting, by the PCEF node, traffic matching a traffic classifier specified by the first Gx rule and both generating and sending, by the PCEF node, the notification message reporting the initiation of the service data flow;

receiving, by the PCRF node from the PCEF node, a notification message for reporting the initiation of the service data flow associated with the application, wherein the notification message includes information about the service data flow; and

after receiving the notification message, sending, by the PCRF node to the PCEF node, a second Gx rule for enforcement by the PCEF, wherein the second Gx rule includes a service identifier parameter associated with the service data flow.

2. The method of claim 1 wherein using the first Gx rule to report initiation of the service data flow includes reporting the initiation of the service data flow to the PCRF node.

3. The method of claim 2 further comprising relaying, by the PCRF node, notification of the initiation of the service data flow to an application function (AF) node.

4. The method of claim 1 wherein using the first Gx rule to report initiation of the service data flow includes reporting the initiation of the service data flow to an application function (AF) node.

5. The method of claim 1 wherein the notification message comprises a Diameter message, an extensible markup language (XML) message, or a simple object access protocol (SOAP) message.

6. The method of claim 1 wherein the first Gx rule is associated with a subscriber.

7. The method of claim 1 wherein the first Gx rule is sent via a Diameter message, an extensible markup language (XML) message, or a simple object access protocol (SOAP) message.

8. The method of claim 7 wherein the first Gx rule is sent via a Diameter message and wherein the Diameter message comprises a credit control answer (CCA) message.

9. A system for detecting a service data flow using a Gx rule, the system comprising:

a policy and charging enforcement function (PCEF) node configured to enforce policies; and

a policy and charging rules function (PCRF) node configured to communicate with the PCEF node and to send, from the PCRF node to the PCEF node, a first Gx rule for triggering the PCEF node to generate a notification message upon initiation of a service data flow associated with an application that is unknown to the PCRF node when the Gx rule is sent, wherein the first Gx rule lacks a service identifier parameter, wherein the PCEF node receives and installs the first Gx rule and uses the first Gx rule to detect and report initiation of the service data flow associated with the application, wherein using the first Gx rule to detect and report initiation of the service data flow comprises detecting, by the PCEF node, traffic matching a traffic classifier specified by the first Gx rule and both generating and sending, by the PCEF node, the notification message reporting the initiation of the service data flow, wherein the PCRF node is configured to receive, from the PCEF node, a notification message for reporting the initiation of the service data flow associated with the application, wherein the notification message includes information about the service data flow, and after receiving the notification message, to send, to the PCEF node, a second Gx rule for enforcement by the PCEF node, wherein the second Gx rule includes a service identifier parameter associated with the service data flow, wherein each of the PCEF node and the PCRF node includes a processor and a memory.

10. The system of claim 9 wherein the PCEF node sends the notification message to the PCRF node.

11. The system of claim 10 wherein the PCRF node relays the notification message to an application function (AF) node.

12. The system of claim 9 wherein the PCEF node sends the notification message to an application function (AF) node.

13. The system of claim 9 wherein the notification message comprises a Diameter message, an extensible markup language (XML) message, or a simple object access protocol (SOAP) message.

14. The system of claim 9 wherein the first Gx rule is associated with a subscriber.

15. The system of claim 9 wherein the PCRF node is configured to send the rule via a Diameter message, an extensible markup language (XML) message, or a simple object access protocol (SOAP) message.

16. The system of claim 15 wherein the first Gx rule is sent via a Diameter message and wherein the Diameter message comprises a credit control answer (CCA) message.

17. A non-transitory computer readable medium comprising computer executable instructions that when executed by a processor of a computer perform steps comprising:

sending, by a policy and charging rules function (PCRF) node to a policy and charging enforcement function (PCEF) node, a first Gx rule for triggering the PCEF node to generate a notification message upon initiation of a service data flow associated with an application that is unknown to the PCRF node when the Gx rule is sent, wherein the first Gx rule lacks a service identifier parameter, wherein each of the PCEF node and the PCRF node includes a processor and a memory;

receiving and installing, by the PCEF node, the first Gx rule;

using, by the PCEF node, the first Gx rule to detect and report initiation of the service data flow associated with the application, wherein using the first Gx rule to detect and report initiation of the service data flow comprises detecting, by the PCEF node, traffic matching a traffic classifier specified by the first Gx rule and both generating and sending, by the PCEF node, the notification message reporting the initiation of the service data flow;

receiving, by the PCRF node from the PCEF node, a notification message for reporting the initiation of the service data flow associated with the application, wherein the notification message includes information about the service data flow; and

after receiving the notification message, sending, by the PCRF node to the PCEF node, a second Gx rule for enforcement by the PCEF, wherein the second Gx rule includes a service identifier parameter associated with the service data flow.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 9, 2012
From: TEKELEC GLOBAL, INC.
To: TEKELEC, INC.
Reel/Frame 028184/0119 →
CHANGE OF NAME Recorded Apr 20, 2012
From: TEKELEC
To: TEKELEC GLOBAL, INC.
Reel/Frame 028078/0287 →
SECURITY INTEREST Recorded Feb 24, 2012
From: TEKELEC; CAMIANT, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 028035/0659 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 17, 2011
From: RILEY, YUSUN KIM; BANIEL, URI
To: TEKELEC
Reel/Frame 026767/0052 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2011
From: RILEY, YUSUN KIM; BANIEL, URI
To: TEKELEC
Reel/Frame 025994/0451 →