Method, system, and entity for exercising policy control
First Claim
1. A method for exercising policy control over data flow of an application service, comprising:
- subscribing, by a Policy and Charging Rule Function PCRF, to an application event, where the subscribing to the application event comprising;
generating a Re-Authorization Request (RAR) message or a first Credit Control Answer (CCA) message that includes an identifier of the application service and an event of the application service and sending the RAR message or the first CCA message to a Policy and Charging Enforcement Function (PCEF);
detecting, by the PCEF, the application event based on the identifier of the application service and the event of the application service received in the RAR message or the first CCA message;
generating, by the PCEF, a Diameter Credit Control Request (CCR) message wherein the Diameter CCR message includes information on the detected application event comprising the identifier of the application service and the event of the application service;
sending, by the PCEF, the Diameter CCR message to the PCRF;
generating, by the PCRF, a control policy of the data flow of the application service according to the information on the detected application event in response to receiving the Diameter CCR message; and
delivering, by the PCRF, the control policy to the PCEF through a second CCA message, wherein the application service does not include involvement of an Application Function.
2 Assignments
0 Petitions
Accused Products
Abstract
A method and a system for exercising policy control, a policy and charging enforcement function (PCEF), and a policy control and charging rules function (PCRF) are provided, which can solve the problem that no policy control can be exercised over application service flows without an application function (AF). The method includes of the following steps: a PCRF receiving information about an application event sent by a PCEF; and the PCRF generating a control policy for a service flow of the application according to the information about the application event, and delivering the control policy to the PCEF. In the present invention, the PCEF sends the obtained information about the application event to the PCRF, so that even when no AF is involved, the PCRF can still generate a control policy according to policy contexts including the information about the application event and the like, so as to exercise an effective policy control over the QoS guarantee, charging and gating of the service flow, thus meeting the requirements of exercising the policy control over data applications with no AF being involved.
20 Citations
7 Claims
-
1. A method for exercising policy control over data flow of an application service, comprising:
-
subscribing, by a Policy and Charging Rule Function PCRF, to an application event, where the subscribing to the application event comprising;
generating a Re-Authorization Request (RAR) message or a first Credit Control Answer (CCA) message that includes an identifier of the application service and an event of the application service and sending the RAR message or the first CCA message to a Policy and Charging Enforcement Function (PCEF);detecting, by the PCEF, the application event based on the identifier of the application service and the event of the application service received in the RAR message or the first CCA message; generating, by the PCEF, a Diameter Credit Control Request (CCR) message wherein the Diameter CCR message includes information on the detected application event comprising the identifier of the application service and the event of the application service; sending, by the PCEF, the Diameter CCR message to the PCRF; generating, by the PCRF, a control policy of the data flow of the application service according to the information on the detected application event in response to receiving the Diameter CCR message; and delivering, by the PCRF, the control policy to the PCEF through a second CCA message, wherein the application service does not include involvement of an Application Function. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
Specification