Source: http://www.google.ca/patents/US8615237
Timestamp: 2017-11-22 03:53:59
Document Index: 597622251

Matched Legal Cases: ['art 1', 'art 2', 'Application No. 10841605', 'Application No. 05', 'Application No. 05854512', 'application No. 05854512', 'Application No. 05854512', 'Application No. 05854512', 'art 2', 'art 1']

Patent US8615237 - Methods, systems, and computer readable media for policy and charging rules ... - Google Patents
The subject matter described herein includes methods, systems, and computer readable media for PCRF node selection. According to one aspect, a system for PCRF node selection is provided. The system includes a first PCRF selection node for receiving a first request message for which PCRF node selection...http://www.google.ca/patents/US8615237?utm_source=gb-gplus-sharePatent US8615237 - Methods, systems, and computer readable media for policy and charging rules function (PCRF) node selection
Publication number US8615237 B2
Application number US 12/974,869
Also published as CN102948115A, CN102948115B, EP2522102A2, EP2522102A4, EP2522102B1, US20110165901, WO2011082090A2, WO2011082090A3
Publication number 12974869, 974869, US 8615237 B2, US 8615237B2, US-B2-8615237, US8615237 B2, US8615237B2
Inventors Uri Baniel, Kenneth Charles Jackson, Tarek Abou-Assali, Michael Mercurio, David Michael Sprague
Patent Citations (91), Non-Patent Citations (90), Referenced by (11), Classifications (7), Legal Events (6)
Methods, systems, and computer readable media for policy and charging rules function (PCRF) node selection
US 8615237 B2
1. A system for a policy and charging rules function (PCRF) node selection, the system comprising:
a first PCRF selection node for receiving a first request message for which PCRF node selection is required; for determining whether to select a PCRF node or to delegate selection of the PCRF node; and, in response to determining to delegate selection of the PCRF node, for generating and sending a second request message based on the first request message; and
a second PCRF selection node for, in response to receiving the second request message from the first PCRF selection node, determining whether to select the PCRF node; and, in response to determining to select the PCRF node, for selecting the PCRF node, wherein the second PCRF selection node, in response to selecting the PCRF node, writes information indicating at least one of: an identity of the selected PCRF and an identity of the second PCRF selection node to a database node, wherein the database node comprises a subscription binding repository (SBR), and wherein the SBR is configured as part of an SBR hierarchy for providing PCRF selection information in response to queries for PCRFs within a domain of responsibility of the SBR.
7. The system of claim 1 wherein the database node comprises a home subscriber server (HSS).
8. The system of claim 1 wherein the SBR is configured for forwarding SBR queries to other SBRs in the SBR hierarchy when the queries request information outside of the domain of responsibility of the SBR.
9. The system of claim 1 wherein the second PCRF selection node determines to select the PCRF node based on a token present in the second request message.
10. The system of claim 1 wherein the first and second PCRF selection nodes are dedicated to performing PCRF node selection.
11. The system of claim 1 wherein the first and second PCRF selection nodes each include diameter relay agent (DRA) functionality.
12. A method for policy and charging rules function (PCRF) node selection, the method comprising:
in response to determining to select the PCRF node, for selecting the PCRF node, wherein the second PCRF selection node, in response to selecting the PCRF node, writes information indicating at least one of: an identity of the selected PCRF and an identity of the second PCRF selection node to a database node, wherein the database node comprises a subscription binding repository (SBR), and wherein the SBR is configured as part of an SBR hierarchy for providing PCRF selection information in response to queries for PCRFs within a domain of responsibility of the SBR.
13. The method of claim 12 wherein the first PCRF selection node determines whether to select the PCRF node based on a subscriber identifier in the first request message.
14. The method of claim 13 wherein the first PCRF selection node performs a hash function of the subscriber identifier to determine whether to select the PCRF node.
15. The method of claim 12 wherein the first PCRF selection node determines whether to select the PCRF node based on dynamic criteria.
16. The method of claim 15 wherein the dynamic criteria include at least one of load balancing criteria and node availability criteria.
17. The method of claim 12 wherein the second PCRF selection node selects the PCRF node using at least one of: load balancing criteria and node availability criteria.
18. The method of claim 12 wherein the database node comprises a home subscriber server (HSS).
19. The method of claim 12 wherein the SBR is configured for forwarding SBR queries to other SBRs in the SBR hierarchy when the queries request information outside of the domain of responsibility of the SBR.
20. The method of claim 12 wherein the second PCRF selection node determines to select the PCRF node based on a token present in the second request message.
21. The method of claim 12 wherein the first and second PCRF selection nodes are dedicated to performing PCRF node selection.
22. The method of claim 12 wherein the first and second PCRF selection nodes each include diameter relay agent (DRA) functionality.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/292,062, filed Jan. 4, 2010 and U.S. Provisional Patent Application Ser. No. 61/405,629, filed Oct. 21, 2010; the disclosure of each of which is incorporated herein by reference in its entirety.
The subject matter described herein relates to identifying PCRF nodes in communications networks. More particularly, the subject matter described herein relates to PCRF node selection in a network with plural PCRFs and/or plural diameter relay agents (DRAs) or other nodes that perform PCRF node selection.
Accordingly, there exists a need for methods, systems, and computer readable media for PCRF node selection.
As used herein, the term “node” refers to a physical entity, such as a computing platform having one or more processors, memory, and one or more network interfaces.
FIG. 1 is a network diagram illustrating an exemplary system for PCRF node selection according to an embodiment of the subject matter described herein;
FIG. 2 is a message flow diagram illustrating exemplary messages that are exchanged for static PCRF node selection where a PCRF selection node locally performs PCRF node selection according to an embodiment of the subject matter described herein;
FIG. 3 is a message flow diagram illustrating exemplary messages exchanged for static PCRF node selection where selection of the PCRF is delegated from a first PCRF selection node to a second PCRF selection node according to an embodiment of the subject matter described herein;
FIG. 4 is a message flow diagram illustrating static PCRF node selection where a PCRF selection node uses a previously selected PCRF node according to an embodiment of the subject matter described herein;
FIG. 5 is a message flow diagram illustrating static PCRF selection for an application function (AF) session where a PCRF selection node delegates PCRF selection according to an embodiment of the subject matter described herein;
FIG. 6 is a message flow diagram illustrating dynamic PCRF node selection where a PCRF is selected locally by a PCRF selection node according to an embodiment of the subject matter described herein;
FIGS. 7A and 7B are a message flow diagram illustrating dynamic PCRF selection where PCRF selection is delegated according to an embodiment of the subject matter described herein;
FIG. 8 is a message flow diagram illustrating exemplary messages exchanged for dynamic PCRF selection for an AF session where a PCRF selection node selects a previously selected PCRF according to an embodiment of the subject matter described herein;
FIG. 9 is a message flow diagram illustrating dynamic PCRF selection for an AF session where a PCRF selection node delegates PCRF selection according to an embodiment of the subject matter described herein;
FIG. 10 is a flow chart illustrating exemplary steps for PCRF node selection according to an embodiment of the subject matter described herein;
FIG. 11 is a block diagram of an exemplary PCRF selection node according to an embodiment of the subject matter described herein; and
FIG. 12 is a network diagram where PCRF selection state is maintained by a subscription binding repository (SBR) according to an embodiment of the subject matter described herein.
Methods, systems, and computer readable media for PCRF node selection are provided. FIG. 1 is a block diagram illustrating an exemplary network including a system for PCRF node selection according to an embodiment of the subject matter described herein. Referring to FIG. 1, the network includes PCRF selection nodes 100, 102, and 103 that perform PCRF selection among PCRF nodes 104 1-104 3, 106 1-106 4, and 108 1-108 2, respectively. Each PCRF is capable of executing policies for subscribers in a communications network, including wireless and/or wireline networks. An exemplary network for implementing the subject matter described herein is an LTE network. Each PCRF selection node 100, 102, and 103 include the ability to select and route signaling to the proper PCRF for a subscriber. In addition, each PCRF selection node 100, 102, and 103 may include DRA functionality.
The network illustrated in FIG. 1 further includes packet gateway/home service gateways (PGW/HSGWs) 110 and 112 and proxy call session control functions (P-CSCFs) 114 and 116. PGW/HSGWs 110 and 112 provide access network services to subscriber terminals. Without the subject matter described herein, PGW/HSGWs 110 and 112 would be required to be programmed with PCRF node selection functionality for all the PCRFs in the network. Thus, each time a new PCRF was added anywhere in the network, each PGW or HSGW would have to be updated. Such a solution is not scalable, as the number of PGWs and HSGWs in a network may be large. Accordingly, PCRF selection nodes 100, 102, and 103 shield PGW/HSGWs 110 and 112 and P-CSCFs 114 and 116 from having to communicate directly with PCRFs.
P-CSCFs 114 and 116 perform proxy call session control functions for subscriber terminals and communicate with PCRF selection nodes 100, 102, and 103 via Rx interfaces. The P-CSCF is the key element in an IMS network in that the P-CSCF handles signaling for voice over IP (VoIP) calls. One function that must be performed by each P-CSCF in establishing a VoIP call is to obtain authorization from a PCRF to connect the call. Rather than having every P-CSCF programmed to select a PCRF for a given call, the subject matter described herein allows the P-CSCF to offload the functionality of selecting a PCRF for a particular call to PCRF selection nodes 100, 102, and 103.
FIG. 2 is a message flow diagram illustrating static PCRF node selection where PCRF node selection is performed locally by a PCRF selection node in response to UE attachment to a network according to an embodiment of the subject matter described herein. Referring to FIG. 2, in line 1, a home service gateway (HSGW) 110A that serves a user terminal sends a Gxx credit control request (CCR) message to PCRF selection node 100. The CCR message may be generated by the HSGW in response to a user activating the user's mobile phone for the first time within an area served by a radio tower. In response to the user activating the user's mobile phone, the phone signals the radio tower. The radio tower signals HSGW 110A of the attachment. In the illustrated example, the core network to which the UE is attaching is assumed to be an LTE network. However, the access network components may not be LTE components. As such, the attachment procedure illustrated in FIG. 2 is an evolved high rate packet data (eHRPD) attachment. Using an eHRPD attachment allows operators to incrementally upgrade to LTE components. However, the subject matter described herein is not limited to performing PCRF node selection in response to a UE attachment procedure. The PCRF selection methods and systems described herein may also be used to perform PCRF node selection when the UE attaches to the network via an LTE node, such as an eNodeB.
Once attachment occurs, HSGW 110A needs to establish a Gxx session with a local PCRF. However, rather than contacting a PCRF directly, HSGW 110A signals PCRF selection node 100, which may be implemented by a DRA local to HSGW 110A. In line 2, PCRF selection node 100 performs a hash algorithm on the IMSI in the CCR message, determines that PCRF selection node 100 should be the node that selects the PCRF, and selects PCRF 104 1, based on any suitable criteria, such as load balancing, node availability, and/or the IMSI. Accordingly, in line 3, PCRF selection node 100 sends a Gxx CCR message to PCRF 104 1. In line 4, PCRF 104 1 queries home subscriber server (HSS) 200 to obtain the subscriber's policy. In line 5, PCRF 104 1 sends a credit control answer (CCA) message to PCRF selection node 100. In line 6, PCRF selection node 100 sends a Gx CCA message to HSGW 110A.
In line 7, packet gateway (PGW) 110B sends a CCR message over the Gx interface to PCRF selection node 100. PGW 110B may generate the CCR message to establish a Gx session for the subscriber with the assigned PCRF. However, rather than communicating directly with the assigned PCRF, PGW 110B, which does not know which PCRF has been assigned, contacts its local DRA/PCRF selection node 100. In line 8, PCRF selection node 100 determines that PCRF 104 1 has already been selected for the IMSI in the CCR message and, in line 9, sends a CCR message to the selected PCRF 104 1. In line 10, PCRF 104 1 sends a Gx CCA message to PCRF selection node 100. In line 11, PCRF selection node 100 sends a Gx CCA message to packet gateway 110B.
FIG. 3 is a message flow diagram illustrating static PCRF selection where the PCRF selection is delegated according to an embodiment of the subject matter described herein. Referring to FIG. 3, when a UE attaches to the network, in line 1, HS gateway 110A sends a CCR message over the Gx interface to PCRF selection node 100. In line 2, PCRF selection node 100 performs a hash function on the IMSI in the CCR message and determines that PCRF selection node 100 is not the node that is assigned to select the PCRF. As set forth above, PCRF selection node 100 may determine that the subscriber's IMSI is local to another PCRF selection node. In this example, the PCRF selection node local to the IMSI (i.e., the subscriber's home PCRF selection node) is assumed to be PCRF selection node 102. Accordingly, PCRF selection node 100 sends a CCR message to PCRF selection node 102, delegating the PCRF node selection. In line 4, PCRF selection node 102 determines, based on the IMSI, that PCRF selection node 102 is the PCRF selection node assigned to select the PCRF and selects PCRF 106 1, based on any suitable criteria, such as load balancing, node availability, and/or a subscriber identifier in the message. In line 5, PCRF selection node 102 sends a CCR message to the selected PCRF 106 1. In line 6, PCRF 106 1 obtains the subscriber's policy from HSS 200. In line 7, PCRF 106 1 sends a CCA message to PCRF selection node 102. In line 8, PCRF selection node 102 sends a CCA message to PCRF selection node 100. In line 9, PCRF selection node 100 sends a CCA message to HS gateway 110A. The response CCA messages may follow the same paths as the corresponding requests using standard Diameter routing.
In line 10 of the message flow diagram, packet gateway 110B sends a CCR message to PCRF selection node 100 to initiate a Gx session for the subscriber. In line 11, PCRF selection node 100 performs the hash function based on the IMSI in the CCR message and determines that the CCR message should be routed to PCRF selection node 102. In line 12, PCRF selection node 100 sends a CCR message to PCRF selection node 102. In line 13, PCRF selection node 102 determines that PCRF 106 1 has already been selected for the IMSI. Accordingly, in line 14, PORE selection node 102 sends a CCR message to the selected PCRF 106 1. In line 15, PCRF 106 1 sends a CCA message to PCRF selection node 102. In line 16, PCRF selection node 102 sends a CCA message to PCRF selection node 100. In line 17, PCRF selection node 100 sends a CCA message to packet gateway 110B.
FIG. 4 is a message flow diagram illustrating exemplary messages exchanged for establishment of an application function (AF) session where a PORE was selected using the method illustrated in FIG. 2 according to an embodiment of the subject matter described herein. Referring to FIG. 4, it is assumed that a UE is attached to the network and that PCRF selection node 100 selected PCRF 104 1 to serve the UE, as illustrated in FIG. 2. In line 1 of the message flow diagram illustrated in FIG. 4, an AF 400 sends an AA request (AAR) message to PCRF selection node 100 to establish an AF session with the PCRF assigned to the subscriber. AF 400 may be a web server, a video server, or a P-CSCE that seeks to establish a session with a user. Rather than communicating directly with a PCRF, application function 400 may communicate with its local DRA/PCRF selection node 100. In line 2, PCRF selection node 100 determines, using its stored PCRF selection state, that PCRF 104 1 has already been selected for the IMSI received in the AAR message. Accordingly, in line 3, PCRF selection node 100 sends an AAR message over the Rx interface to PCRF 104 1. In line 4, PCRF 104 1 sends an AA answer (AAA) message to PCRF selection node 100 over the Rx interface. In line 5, PCRF selection node 100 sends an AAA message to AF 400 over the Rx interface.
FIG. 5 is a message flow diagram illustrating exemplary messaging for establishment of an AF session where PCRF selection was delegated during UE attachment. Referring to FIG. 5, it is assumed that PCRF selection node 102 select PCRF 106 1 for the subscriber using the method illustrated in FIG. 3. In line 1 of the message flow diagram in FIG. 5, AF 400 sends an AAR message over the Rx interface to PCRF selection node 100 to initiate the AF session. PCRF selection node 100 does not store PCRF selection state because PCRF selection node 100 did not select the PCRF for this particular subscriber. Accordingly, in line 2, PCRF selection node 100 determines that the AAR message should be routed to PCRF selection node 102 based on the IMSI in the AAR message. In line 3, PCRF selection node 100 sends an AAR message over the Rx interface to PCRF selection node 102. PCRF selection node 102 is the node that performs the PCRF selection and stores PCRF selection state for the IMSI. Accordingly, in line 4 of the message flow diagram, PCRF selection node 102 determines that PCRF 106 1 has already been selected for the IMSI. In line 5, PCRF selection node 102 sends an AAR message to the selected PCRF 106 1. In line 6, PCRF 106 1 sends an AAA message to PCRF selection node 102. In line 7, PCRF selection node 102 sends an AAA message to PCRF selection node 100. In line 8, PCRF selection node 100 sends an AAA message to AF 400.
If a PCRF selection node that receives a session establishment request has already selected a PCRF for the user, it will route the request to the selected PCRF. Otherwise, it will query the HSS or other database to determine if a PCRF has already been selected. If the result of the query indicates that a PCRF has already been selected, the PCRF selection node will route the request to the PCRF via the PCRF's DRA/PCRF selection node. If a PCRF was not previously selected, the PCRF selection node will dynamically determine (e.g., using load balancing and/or node availability information) a PCRF selection node that will be responsible for PCRF selection and will route the request to that node. The request to the receiving PCRF selection node may include a token or parameter that indicates to the receiving PCRF selection node that it is the last node in a hierarchy of PCRF selection nodes and that the PCRF selection node should perform, rather than delegate, the PCRF selection. The PCRF selection node that receives the request will select the PCRF and write the HSS or other database its identity and optionally the identity of the selected PCRF. The PCRF selection node that performed the selection may store the identity of the selected PCRF locally to shield the HSS or other database from subsequent queries to determine the assigned PCRF.
FIG. 6 is a message flow diagram illustrating dynamic PCRF selection where a PCRF is selected locally by a DRA/PCRF selection node that receives a Diameter session establishment request in response to user attachment to a network according to an embodiment of the subject matter described herein. Referring to FIG. 6, it is assumed that user equipment attaches to the network and, in line 1, HS gateway 110A sends a CCR message over the Gxx interface to PCRF selection node 100 to initiate establishment of a Gxx session for the user. PCRF selection node 100 determines in line 2 that it does not store information indicating that a PCRF has been selected for the UE. Accordingly, in line 3, PCRF selection node 100 queries HSS 200 to determine whether a PCRF has been selected. As set forth above, the subject matter described herein is not limited to storing PCRF selection state in an HSS. Any suitable centralized database accessible by DRA/PCRF selection nodes to store and access PCRF selection information is intended to be within the scope of the subject matter described herein. In an alternate implementation, which will be described in detail below, PCRF selection state may be maintained by a node that is dedicated to storing PCRF selection state, referred to as a subscription binding repository (SBR). In the embodiment illustrated in FIG. 6, it is assumed that once PCRF selection has occurred, the selection state is stored in HSS 200.
In line 4, PCRF selection node 100 determines that no PCRF has been selected, so PCRF selection node 100 dynamically determines that PCRF selection node 100 is the PCRF selection node responsible for selecting the PCRF and selects PCRF selection node 104 1. As set forth above, the determination as to whether to perform PCRF selection locally may be based on dynamic criteria, such as load balancing and/or node availability. Other dynamic criteria that may be used may include PCRF selection delegation token in a message received from another DRA/PCRF selection node.
In line 5, PCRF selection node 100 sends a CCR message to the selected PCRF 104 1 over the Gxx interface. In line 6, the selected PCRF 104 1 queries HSS 200 to obtain a policy for the subscriber. In line 7, PCRF node 104 1 sends a CCA message to PCRF selection node 100 over the Gxx interface. In line 8, PCRF selection node 100 writes the identifier of the selected PCRF for the user equipment to HSS 200. As set forth above, it may not be necessary for the identifier of selected PCRF to be written to the HSS. In an alternate implementation, only the identifier of the PCRF selection node/DRA that performs the selection may be written to the HSS. Since the PCRF selection node/DRA that performs the selection stores the PCRF selection state, subsequent queries to the HSS will yield the PCRF selection node/DRA, and the PCRF selection node/DRA will route the signaling to the proper PCRF. In line 9, PCRF selection node 100 sends a CCA message to HS gateway 110A. In line 10, packet gateway 110B sends a CCR message to PCRF selection node 100 to establish a Gx session for the UE. In line 11, PCRF selection node 100 determines whether a PCRF has already been selected by PCRF selection node 100 for the UE. Because PCRF 104 1 has already been selected by PCRF selection node 100, in line 12, PCRF selection node 100 sends a CCR message to PCRF 104 1 over the Gx interface. In line 13, PCRF 104 1 sends a CCA message to PCRF selection node 100 over the Gx interface. In line 14, PCRF selection node 100 sends a Gx CCA message to packet gateway 110B.
FIGS. 7A and 7B are a message flow diagram illustrating exemplary messages exchanged for dynamic PCRF selection where PCRF selection is delegated from one PCRF selection node/DRA to another PCRF selection node/DRA according to an embodiment of the subject matter described herein. Referring to FIG. 7A, it is assumed that a UE attaches to the network via an access network within the domain of responsibility of HSGW 110A. According, in line 1, HS gateway 110A sends a CCR message to PCRF selection node 100 via the Gxx interface to establish a Gx session for the UE. In line 2, PCRF selection node 100 determines whether PCRF selection node 100 has information that indicates that a PCRF has been selected for a session. No information is determined to be present in this example, so in line 3, PCRF selection node 100 queries HSS 200 to determine whether a PCRF has been assigned. In line 4, PCRF selection node 100 determines, based on the response from HSS 200, that no PCRF has been selected. Accordingly, PCRF selection node 100 performs a load balancing or other suitable algorithm and selects PCRF selection node 102 to perform the PCRF selection. Accordingly, in line 5, PCRF selection node 100 sends a CCR message to PCRF selection node 102. As set forth above, the CCR message may include a PCRF selection delegation token that indicates to PCRF selection node 102 that PCRF selection node 102 is to perform the PCRF selection, rather than delegate the PCRF selection to another node. In line 6, PCRF selection node 102 performs PCRF selection using a load balancing or other suitable algorithm to select PCRF node 106 1. In line 7, PCRF selection node 102 sends a CCR message to the selected PCRF 106 1. In line 8, PCRF 106 1 queries HSS 200 to obtain a policy for the subscriber.
Referring to FIG. 7B, in line 10, PCRF selection node 102 writes the identity of the selected PCRF and/or the identity of PCRF selection node 102 to HSS 200. In line 11, PCRF selection node 102 sends a CCA message to PCRF selection node 100 over the Gxx interface. In line 12, PCRF selection node sends a CCA message to HS gateway 110A over the Gxx interface.
In line 13, PGW 110B sends a CCR message to PCRF selection node 100 to establish a Gx session for the UE. In line 14, PCRF selection node 100 determines whether a PCRF has already been selected for this session. In this example, PCRF selection node 100 does not know whether a PCRF has been selected, because PCRF selection node 100 did not perform the selection and store the selection state locally. Accordingly, PCRF selection node 100 sends a PCRF selection query to HSS 200. In line 16, PCRF selection node 100 determines, from the response from the HSS 200, that PCRF 106 1 is selected and determines that the CCR message should be routed to PCRF 106 1 via PCRF selection node 102. In line 17, PCRF selection node 100 sends a CCR message to PCRF selection node 102 via the Gx interface. In line 18, PCRF selection node 102 determines, using locally stored PCRF selection state, that PCRF 106 1 has already been selected for the UE. Accordingly, in line 19, PCRF selection node 102 sends a CCR message to the selected PCRF 106 1. In line 20, PCRF 106 1 sends a CCA message to PCRF selection node 102 over the Gx interface. In line 21, PCRF selection node 102 sends a CCA message to PCRF selection node 100 over the Gx interface. In line 22, PCRF selection node 100 sends a CCA message to PGW 110B over the Gx interface.
FIG. 8 is a message flow diagram illustrating assignment of PCRF to an AF session where the PCRF was previously dynamically selected using the method illustrated in FIG. 6 according to an embodiment of the subject matter described herein. Referring to FIG. 8, it is assumed that a UE has attached to the network and PCRF 104 1 has been selected by PCRF selection node 100, as illustrated in FIG. 6. In line 1 of FIG. 8, AF 400 sends an AAR message to PCRF selection node 100. In line 2, PCRF selection node 100 determines, using locally stored PCRF selection state, that PCRF 104 1 has already been selected for this session. Accordingly, in line 3, PCRF selection node 100 sends an AAR message over the Rx interface to the selected PCRF 104 1. In line 4, PCRF 104 1 sends an AAA message over the Rx interface to PCRF selection node 100. In line 5, PCRF selection node 100 sends an AAA message to application function 400.
FIG. 9 is a message flow diagram illustrating assignment of PCRF to an AF session where the PCRF was previously dynamically selected using the method illustrated in FIG. 6. However, unlike the example illustrated in FIG. 8, the PCRF selection node that receives the initial AAR message in FIG. 9 is not the PCRF selection node that performed the PCRF selection. In FIG. 9, it is assumed that a PCRF 104 1 and PCRF selection node 100 have been selected using the method set forth in FIG. 6. Accordingly, in line 1, AF 400 sends an AAR message to PCRF selection node 102. In line 2, PCRF selection node 102 determines that PCRF selection node 102 does not have any local state information indicating that a PCRF selection has occurred. Accordingly, in line 3, PCRF selection node 102 queries HSS 200 for the selected PCRF information. In line 4, PCRF selection node 102 determines that PCRF 104 1 has been selected and that the request should be routed to PCRF 104 1 via PCRF selection node 100. In line 5, PCRF selection node 102 sends an AAR message to PCRF selection node 100. In line 6, PCRF selection node 100 determines, using locally stored PCRF selection state, that PCRF 104 1 is already selected for the UE. In line 7, PCRF selection node 100 sends an AAR message to PCRF 104 1. In line 8, PCRF 104 1 sends an AAA message to PCRF selection node 100. In line 9, PCRF selection node 100 sends an AAR message to PCRF selection node 102. In line 10, PCRF selection node 102 sends an AAA message to AF 400.
FIG. 10 is a flow chart illustrating exemplary overall steps for PCRF node selection according to an embodiment of the subject matter described herein. Referring to FIG. 10, in step 1000, a request for which PCRF node selection is required is received at a first PCRF selection node. In step 1002, the first PCRF selection node determines whether to select the PCRF locally or to delegate the selection. If the first PCRF selection node determines to select the PCRF locally, control proceeds to step 1004 where the first PCRF selection node selects the PCRF locally. The determination as to whether to select the PCRF locally or to delegate the PCRF selection may be determined statically, using the IMSI, as described above, or dynamically, based on dynamic criteria, as described above.
Returning to step 1002, if the first PCRF selection node determines to delegate the PCRF selection, control proceeds to step 1006 where the first PCRF selection node sends a second request message related to the first request message to a second PCRF selection node. The second PCRF node may execute the same algorithm illustrated in FIG. 10 to determine whether it should select the PCRF or delegate the selection.
FIG. 11 is block diagram illustrating an exemplary PCRF selection node according to an embodiment of the subject matter described herein. Referring to FIG. 11, PCRF selection node 100, 102, or 103 includes a communications interface 1100 for receiving request messages for which PCRF selection is indicated. The request messages may be CCR message and they may arrive over any suitable interface, such as the Gx or the Gxx interfaces. For application originated sessions, the messages may be AAR messages that arrive over the Rx interface. PCRF selection node 100, 102, or 103 may include a PCRF selection module 1102 that performs local or delegates PCRF selection as described above. PCRF selection nodes 100, 102, or 103 may also store PCRF selection state information 1104 to avoid unnecessary contact with HSS nodes to obtain PCRF selection information. As set forth above, PCRF selection node 100, 102, or 103 may be dedicated to performing PCRF node selection or may include diameter routing agent (DRA) functionality. As such, PCRF selection node 100, 102, or 103 may include a Diameter routing table 1106 that contains information for routing diameter signaling messages sent by Diameter parameters, such as destination-realm and destination-host.
FIG. 12 illustrates an embodiment of the subject matter described herein where PCRF selection state information is stored in a database separate from the HSS and from the DRA. Referring to FIG. 12, a node that is dedicated to storing PCRF selection state, referred to as a subscription binding repository (SBR) 1200, stores PCRF selection state information. SBR 1200 can be updated with PCRF selection state using any of the methods used herein. For example, PCRF selection nodes 100 or 102 can select the PCRF statically based on the IMSI, as described above or dynamically, using load balancing, as described above. The PCRF selection state may be written to SBR 1200. In an alternate implementation, PCRF selection nodes 100 and 102 may select one of front end nodes 1204 and 1206, and front end nodes 1204 and 1206 may perform the PCRF selection based on load balancing or other suitable criteria. Front end nodes 1204 and 1206 may be dedicated to performing PCRF node selection. Alternatively, front end nodes 1204 and 1206 may also include DRA functionality, similar to PCRF selection nodes 100 and 102. Once a PCRF is selected, that information will be stored in SBR 1200. Storing PCRF selection information in SBR 1200 allows SBR 1200 to be queried to obtain PCRF selection state and further offloads traffic and processing from the HSS and the DRA. In addition, SBRs may be arranged in a hierarchy such that each SBR stores PCRF selection state for its domain of responsibility and forwards PCRF-related queries requests to peers when an SBR does not have the selection state to provide in response to a query but knows of a peer SBR that might have the PCRF selection state.
2 "3rd Generation Partnership Project; Technical Specification Group Core Network; Cx and Dx Interfaces Based on the Diameter Protocol; Protocol Details (Release 5)," 3GPP TS 29.229, V5.6.0, pp. 1-23 (Dec. 2003).
3 "3rd Generation Partnership Project; technical Specification Group Core Network; IP Multimedia (IM) Session Handling; IM Call Model; Stage 2 (Release 6)," 3GPP TS 23.218, V6.1.0, pp. 1-56 (Mar. 2004).
4 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging architecture and principles (Release 9)," 3GPP TS 32.240, V9.1.0 (Jun. 2010).
5 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Diameter charging applications (Release 9)," 3GPP TS 32.299, V9.4.0 (Jun. 2010).
6 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Packet Switched (PS) domain charging (Release 9)," 3GPP TS 32.251, V9.4.0 (Oct. 2010).
7 "All-IP Core Network Multimedia Domain," 3rd Generation Partnerships Project 2 (3GPP2), 3GPP2 X.S0013-000-0, Version 1.0, pp. i-ii and 1-14 (Dec. 2003).
8 "Digital Cellular Telecommunications System (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (Release 5)," 3GPP TS 23.228, V5.7.0, pp. 1-130 (Dec. 2002).
9 "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; End-to-end Quality of Service (QoS) concept and architecture (3GPP TS 23.207 version 9.0.0 Release 9)," ETSI TS 123 207 V9.0.0 (Oct. 2010).
10 "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 9.4.0 Release 9)," ETSI TS 123 228, V9.4.0 (Oct. 2010).
11 "IMS Security Framework," 3GPP2 S.R0086-0, Version 1.0, pp. 1-39 (Dec. 11, 2003).
12 "IP Multimedia Subsystem IMS Over and Applications," 3G Americas, pp. 1-17 (Jul. 2004).
13 "IP Multimedia Subsystem-Accounting Information Flows and Protocol," 3GPP2 X.S0013-008-0, Version 1.0, pp. 1-42 (Dec. 2003).
14 "IP Multimedia Subsystem-Charging Architecture," 3GPP2 X.S0013-007-0, Version 1.0, pp. 1-16 (Dec. 2003).
15 "Operator Guidebook to IMS and New Generation Networks and Services," www.morianagroup.com, First Edition, pp. 1-450 (Aug. 2005) (Part 1 of 2).
16 "Operator Guidebook to IMS and New Generation Networks and Services," www.morianagroup.com, First Edition, pp. 451-934 (Aug. 2005) (Part 2 of 2).
17 "Operator Guidebook to IMS and New Generation Networks and Services," www.morianagroup.com, Second Edition (Feb. 2006).
18 "Tekelec Announces TekCore IMS Core Platform," (Jun. 5, 2006).
21 3GPP, "3rd Generation Parnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control Over Gx Reference Point (Release 9)," 3GPP TS 29.212 V9.2.0, pp. 1-111 (Mar. 2010).
23 3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Networks and Terminals; Sh Interface based on the Diameter protocol; Protocol details (Release 8)," 3GPP TS 29.329, V8.8.0 (Dec. 2010).
27 Calhoun et al., "Diameter Base Protocol," Network Working Group, RFC 3588, pp. 1-138 (Sep. 2003).
32 Commonly-assigned, co-pending International Application No. PCT/US12/23971 for "Methods, Systems, and Computer Readable Media for Provisioning a Diameter Binding Repository," (Unpublished, filed Feb. 6, 2012).
33 Commonly-assigned, co-pending International Application No. PCT/US12/27263 for "Methods, Systems, and Computer Readable Media for Sharing Diameter Binding Data," (Unpublished, filed Mar. 1, 2012).
34 Commonly-assigned, co-pending International Application No. PCT/US12/27269 for "Methods, Systems, and Computer Readable Media for Dynamically Learning Diameter Binding Information," (Unpublished, filed Mar. 1, 2012).
35 Commonly-assigned, co-pending International Application No. PCT/US12/27281 for "Methods, Systems, and Computer Readable Media for Hybrid Session Based Diameter Routing," (Unpublished, filed Mar. 1, 2012).
36 Commonly-assigned, co-pending International Application No. PCT/US12/27736 for "Methods, Systems, and Computer Readable Media for Enriching a Diameter Signaling Message," (Unpublished, filed Mar. 5, 2012).
37 Commonly-assigned, co-pending U.S. Appl. No. 13/366,928 titled "Methods, Systems, and Computer Readable Media for Provisioning a Diameter Binding Repository," (Unpublished, filed Feb. 6, 2012).
38 Commonly-assigned, co-pending U.S. Appl. No. 13/409,893 for "Methods, Systems, and Computer Readable Media for Sharing Diameter Binding Data," (Unpublished, filed Mar. 1, 2012).
39 Commonly-assigned, co-pending U.S. Appl. No. 13/409,914 titled "Methods, Systems, and Computer Readable Media for Dynamically Learning Diameter Binding Information," (Unpublished, filed Mar. 1, 2012).
40 Commonly-assigned, co-pending U.S. Appl. No. 13/409,949 titled "Methods, Systems, and Computer Readable Media for Hybrid Session Based Diameter Routing," (Unpublished, filed Mar. 1, 2012).
41 Commonly-assigned, co-pending U.S. Appl. No. 13/412,352 titled "Methods, Systems, and Computer Readable Media for Enriching a Diameter Signaling Message," (Unpublished, filed Mar. 5, 2012).
42 Commonly-assigned, co-pending U.S. Appl. No. 13/465,552 for "Methods, Systems, and Computer Readable Media for Caching Call Session Control Function (CSCF) Data at the Diameter Signaling Router (DSR)," (Unpublished, filed May 7, 2012).
43 Commonly-assigned, co-pending U.S. Appl. No. 13/712,481 for "Methods, Systems, and Computer Readable Media for Encrypting Diameter Identification Information in a Communication Network," (Unpublished,filed Dec. 12, 2012).
44 Communication of European publication number and information on the application of Article 67(3) EPC for European Patent Application No. 10841605.8 (Oct. 17, 2012).
45 Communication pursuant to Article 94(3) EPC for European Application No. 05 854 512.0 (Oct. 12, 2010).
46 Communication pursuant to Article 94(3) EPC for European Application No. 05854512.0 (Feb. 8, 2010)
47 Communication under Rule 71(3) EPC for European application No. 05854512.0 (Nov. 11, 2011).
48 Decision to grant a European patent pursuant to Article 97(1) EPC for European Application No. 05854512.0 (Mar. 15, 2012).
49 Faltstrom, "E.164 Number and DNS," RFC 2916, pp. 1-10 (Sep. 2000).
50 Final Office Action for U.S. Appl. No. 13/409,893 (Jul. 1, 2013).
51 Final Official Action for U.S. Appl. No. 11/303,757 (Dec. 9, 2009).
52 Final Official Action for U.S. Appl. No. 11/303,757 (Oct. 6, 2008).
53 Gonzalo et al., "The 3G IP Multimedia Subsystem," Chapter 3: General Principles of the IMS Architecture (Aug. 20, 2004).
54 Hakala et al., "Diameter Credit-Control Application," RFC 4006, pp. 1-114 (Aug. 2005).
55 Howard, "Sipping IETF51 3GPP Security and Authentication," http://www3.ietf.org/proceedings/01aug/slides/sipping-7/index.htm (Dowloaded from Internet on Dec. 16, 2005) (Sep. 13, 2001).
56 Jalava, "Service Routing in 3GPP IP Multimedia Subsystem," Nokia, pp. 1-16 (Publication Date Unknown).
57 Narten et al., "Privacy Extensions for Stateless Address Autoconfiguration in IPv6," RFC 3041, pp. 1-16 (Jan. 2001).
58 Non-Final Office Action for U.S. Appl. No. 12/409,914 (Jun. 7, 2013).
59 Non-Final Office Action for U.S. Appl. No. 13/192,410 (Dec. 20, 2012).
60 Non-Final Office Action for U.S. Appl. No. 13/366,928 (Mar. 26, 2013).
61 Non-Final Office Action for U.S. Appl. No. 13/409,893 (Dec. 13, 2012).
62 Non-Final Office Action for U.S. Appl. No. 13/409,949 (Feb. 15, 2013).
63 Non-Final Official Action for U.S. Appl. No. 12/409,914 (Nov. 6, 2012).
64 Non-Final Official Action for U.S. Appl. No. 13/412,352 (Oct. 26, 2012).
65 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/303,757 (May 11, 2011).
66 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/366,923 (Jan. 7, 2013).
67 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/412,352 (May 28, 2013).
68 Notification of the Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2010/061934 (Oct. 25, 2011).
69 Notification of Transmital of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2012/027281 (Jun. 15, 2012).
70 Notification of Transmittal of the International Search Report and the Written Opinion corresponding to International Application No. PCT/US05/45813 (Mar. 24, 2008).
71 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/039285 (Feb. 9, 2012).
72 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2012/027263 (Jun. 14, 2012).
73 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2012/023971 (Jun. 11, 2012).
74 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2012/027269 (Jun. 11, 2012).
75 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2012/027736 (Jun. 12, 2012).
76 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2012/036784 (Nov. 1, 2012).
77 Official Action for U.S. Appl No. 11/303,757 (Dec. 22, 2010)
78 Official Action for U.S. Appl. No. 11/303,757 (Feb. 21, 2008).
79 Official Action for U.S. Appl. No. 11/303,757 (May 28, 2009).
80 Official Action for U.S. Appl. No. 11/303,757 (May 7, 2008).
81 Olson et al., "Support for IPv6 in Session Description Protocol (SDP)," RFC 3266, pp. 1-5 (Jun. 2002).
82 PCT International Patent Application No. PCT/US2012/036784, Titled, "Methods, Systems, and Computer Readable Media for Steering a Subscriber Between Access Networks," (Unpublished, Filed May 7, 2012).
83 Restriction Requirment for U.S. Appl. No. 11/303,757 (Oct. 4, 2007).
84 Rosenberg et al., "SIP: Session Initiation Protocol," RFC 3261, pp. 1-252 (Jun. 2002).
85 Rouse, "Platform," http://searchservervirtualization.techtarget.com/definition/platform, pp. 1-2 (2006-2009).
86 Supplementary European Search Report for European Application No. 05854512.0 (Nov. 17, 2009).
87 Tekelec, "Eagle® Feature Guide," P/N 910-1225-01 (Jan. 1998).
88 Vaha-Sipila, "URLs for Telephone Calls," RFC 2806, pp. 1-20 (Apr. 2000).
89 Znaty, "Diameter, GPRS, (LTE + ePC = EPS), IMS, PCC and SDM," EFORT pp. 230-461 (Part 2 of 2) (May 2010).
90 Znaty, "Diameter, GPRS, (LTE + ePC = EPS), IMS, PCC and SDM," EFORT, pp. 1-229 (Part 1 of 2) (May 2010).
US9661151 * 24 Jun 2014 23 May 2017 Huawei Technologies Co., Ltd. Method, apparatus and system for determining policy and charging rule function entity
Cooperative Classification H04L67/1036, H04L67/1004, H04M15/66, H04W8/04, H04L67/28
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BANIEL, URI;JACKSON, KENNETH CHARLES;ABOU-ASSALI, TAREK;AND OTHERS;SIGNING DATES FROM 20110219 TO 20110311;REEL/FRAME:025955/0191
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BANIEL, URI;JACKSON, KENNETH CHARLES;ABOU-ASSALI, TAREK;AND OTHERS;SIGNING DATES FROM 20110627 TO 20110707;REEL/FRAME:026767/0114