IP Library Granted Patent US 8,837,500
Granted Patent B2
US 8,837,500 · App. 13/167,522 · Granted Sep 16, 2014

Service data flow direction/redirection

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 8,837,500
App. No.
13/167,522
Granted
Sep 16, 2014
Kind
B2
Abstract

Systems and methods are disclosed for directing/redirecting service data flows to Packet Data Networks (PDN). A subscriber database (e.g., HSS) stores direction/redirection criteria along with mapping data that includes information for directing/redirecting service data flows to PDNs. An element of a network may then query the subscriber database to direct or redirect service data flows to PDNs. The subscriber database receives a query from a network element, and identifies the direction/redirection criteria and mapping data for the data service. The subscriber database then transmits the direction/redirection criteria and mapping data to the network element in response to the query to allow the network element to direct/redirect a service data flow to a PDN for the data service.

Claims (46)

1. A system comprising:

a subscriber database comprising a processor operable to store subscriber profiles for end users of a communication network;

the subscriber database further operable to store direction criteria defining conditions for directing service data flows to Packet Data Networks (PDN), to store mapping data associated with the direction criteria that includes information for directing the service data flows to the PDNs when a condition from the direction criteria is satisfied, and to store flow condition data indicating a status of the service data flows over the PDNs;

the subscriber database further operable to transmit the direction criteria and mapping data to a network element in response to a query to allow the network element to direct a service data flow to a first PDN for a data service;

the subscriber database is further operable to store redirection criteria defining conditions for redirecting service data flows among PDNs, and to store mapping data associated with the redirection criteria that includes information for redirecting service data flows from one PDN to another PDN;

the subscriber database is further operable to transmit the redirection criteria and mapping data to the network element in response to another query to allow the network element to redirect the service data flow from the first PDN to a second PDN.

2. The system of claim 1 wherein:

the subscriber database is further operable to process the flow condition data to identify a problem in the first PDN, and to transmit the redirection criteria and mapping data to the network element when the problem is identified in the first PDN.

3. The system of claim 1 wherein:

the network element comprises a Policy and Charging Rules Function (PCRF); and

the subscriber database connects to the PCRF over an Sp interface.

4. The system of claim 1 wherein:

the subscriber database is further operable to store the direction criteria and mapping data with a Public Service Identifier (PSI); and

the subscriber database is further operable to store the redirection criteria and mapping data with the PSI.

5. The system of claim 1 wherein:

the subscriber database is further operable to store the direction criteria and mapping data with a Public User Identifier (PUID) for an end user; and

the subscriber database is further operable to store the redirection criteria and mapping data with the PUID for the end user.

6. The system of claim 1 wherein:

the subscriber database is further operable to store the flow condition data with a Public Service Identifier (PSI).

7. A method comprising:

storing subscriber profiles for end users of a communication network in a subscriber database;

storing, in the subscriber database, direction criteria defining conditions for directing service data flows to Packet Data Networks (PDN), mapping data associated with the direction criteria that includes information for directing the service data flows to the PDNs when a condition from the direction criteria is satisfied, and flow condition data indicating a status of the service data flows over the PDNs;

transmitting the direction criteria and mapping data from the subscriber database to a network element in response to a query to allow the network element to direct a service data flow to a first PDN for a data service;

storing, in the subscriber database, redirection criteria defining conditions for redirecting service data flows among PDNs, and mapping data associated with the redirection criteria that includes information for redirecting service data flows from one PDN to another PDN; and

transmitting the redirection criteria and mapping data from the subscriber database to the network element in response to another query to allow the network element to redirect the service data flow from the first PDN to a second PDN.

8. The method of claim 7 further comprising:

processing the flow condition data to identify a problem in the first PDN; and

transmitting the redirection criteria and mapping data to the network element when the problem is identified in the first PDN.

9. The method of claim 7 wherein:

the network element comprises a Policy and Charging Rules Function (PCRF); and

the subscriber database connects to the PCRF over an Sp interface.

10. The method of claim 7 wherein:

storing the direction criteria and mapping data comprises storing the direction criteria and mapping data with a Public Service Identifier (PSI); and

storing the redirection criteria and mapping data comprises storing the redirection criteria and mapping data with the PSI.

11. The method of claim 7 wherein:

storing the direction criteria and mapping data comprises storing the direction criteria and mapping data with a Public User Identifier (PUID) for an end user; and

storing the redirection criteria and mapping data comprises storing the redirection criteria and mapping data with the PUID for the end user.

12. The method of claim 7 wherein:

storing the flow condition data comprises storing the flow condition data with a Public Service Identifier (PSI).

13. A system comprising:

a Home Subscriber Server (HSS) coupled to a Policy and Charging Rules Function (PCRF) over an Sp interface;

the HSS comprising a processor operable to store subscriber profiles for end users of a communication network;

the HSS further operable to store redirection criteria defining conditions for redirecting service data flows among Packet Data Networks (PDNs), to store mapping data associated with the redirection criteria that includes information for redirecting service data flows from one PDN to another PDN, and to store flow condition data indicating a status of service data flows over the PDNs;

the HSS further operable to receive a query from the PCRF over an Sp interface involving a service data flow for an end user over a first PDN, to process the flow condition data to identify a problem with the first PDN, to identify the redirection criteria and mapping data for the service data flow, and to transmit the redirection criteria and mapping data to the PCRF over the Sp interface to allow the PCRF to redirect the service data flow from the first PDN to a second PDN.

14. The system of claim 13 wherein:

the flow condition data is stored with a Public Service Identifier (PSI).

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0555 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 24, 2012
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 028620/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 23, 2011
From: CAI, YIGANG; HUA, SUZANN
To: ALCATEL-LUCENT USA INC.
Reel/Frame 026491/0627 →