WO2012041150A1 - 用量监测方法及策略控制与计费规则功能实体 - Google Patents

用量监测方法及策略控制与计费规则功能实体 Download PDF

Info

Publication number
WO2012041150A1
WO2012041150A1 PCT/CN2011/079294 CN2011079294W WO2012041150A1 WO 2012041150 A1 WO2012041150 A1 WO 2012041150A1 CN 2011079294 W CN2011079294 W CN 2011079294W WO 2012041150 A1 WO2012041150 A1 WO 2012041150A1
Authority
WO
WIPO (PCT)
Prior art keywords
usage
session
value
session level
level
Prior art date
Application number
PCT/CN2011/079294
Other languages
English (en)
French (fr)
Inventor
周晓云
宗在峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012041150A1 publication Critical patent/WO2012041150A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1432—Metric aspects
    • H04L12/1435—Metric aspects volume-based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the technical field of the Policy and Charging Rules Function (PCRF), and in particular, to a usage monitoring method and a PCRF.
  • PCRF Policy and Charging Rules Function
  • the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project)'s Policy and Charging Control (PCC) architecture is a functional framework that can be applied to multiple access technologies. It can be applied to the Universal Mobile Telecommunications System (UMTS, UMTS Terrestrial Radio Access Network), Global System for Mobile Communication (GSM), GSM data enhancement. EDGE (Enhanced Data Rates for Global Evolution) radio access network, interworking wireless local area network (I-WLAN), and evolved packet system (EPS, Evolved Packet System).
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data Rates for Global Evolution radio access network
  • I-WLAN interworking wireless local area network
  • EPS evolved packet system
  • the application function entity is used to provide access points for service applications.
  • the network resources used by these service applications require dynamic policy control.
  • the AF transmits the related service information to the PCRF that is connected to the Rx interface.
  • the PCRF accepts the negotiation if it determines that the received service information is consistent with the locally configured policy; otherwise, the negotiation is rejected.
  • the business parameters acceptable to the PCRF are also given in the feedback. Subsequently, the AF can return these parameters to the user equipment (UE, User Equipment);
  • the PCRF is the core of the PCC and is responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules.
  • the PCRF sends its formulated policies and charging rules to the Policy and Charging Enforcement Function (PCEF), and the PCRF There is also a need to ensure that these rules are consistent with the user's contract information.
  • the basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information related to the user policy charging control from the SPR (Spent Profile Repository); and obtaining the bearer related information from the PCEF Internet Information.
  • the PCEF is usually located in the gateway (GW, Gate-Way), such as general packet radio service technology.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • the charging rule sent by the PCRF the PCEF performs the charging operation of the corresponding service data flow, and the charging mode can be either online charging or offline charging.
  • PCEF needs to manage credit with the Online Charging System (OCS).
  • OCS Online Charging System
  • the PCEF needs to exchange relevant charging information with the offline charging system (OFCS).
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the PC and the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • PCEF can also have Application Detection and Control (ADC).
  • ADC Application Detection and Control
  • PCEF can control detection (ADC, redirection, bandwidth limitation, and usage monitoring) based on local configuration or PCRF including application detection control policy; ; ⁇
  • TDF Traffic Detection Function
  • PCRF Traffic Detection Function
  • Bearer Binding and Event Reporting Entity BBERF , Bearer Binding and Event Reporting Entity
  • E-UTRAN Evolved Universal Terrestrial Radio Access
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • ePDG Evolved Packet Data Gateway
  • the SPR and the PCRF are connected by using a Sp interface, and the user policy charging control subscription information related to policy control and charging is stored;
  • OFCS and PCEF together perform the charging operation in the offline charging mode.
  • the PCC architecture implements policy charging control for the IP-Connected Network (IP-Access, Network Access Access Network) session established by the UE to access a Packet Data Network (PDN).
  • IP-Access IP-Access, Network Access Access Network
  • PDN Packet Data Network
  • the PCC supports dynamic usage monitoring control to implement dynamic policy decisions based on the total amount of real-time network resource usage.
  • Usage monitoring can be applied to a single service data stream, a group of service data streams, or all traffic data streams for an IP-CAN session (referred to as IP-CAN session level). If the UE establishes multiple IP-CAN sessions to a certain PDN, the usage monitoring can also be applied to the multiple IP-CAN sessions. At this point, the usage monitoring of the IP-CAN session level is to monitor all traffic data flows of the multiple IP-CAN sessions. Currently, usage refers to user plane data traffic.
  • a monitoring key is used to identify an instance that needs to be monitored, for example:
  • the PCRF assigns a Monitoring Key and a corresponding threshold to all traffic flows of an IP-CAN session
  • the PCEF will All traffic flows of the IP-CAN session are monitored according to the threshold, and the Monitoring Key is used to identify the usage of the uplink.
  • the PCRF assigns a monitoring key and a corresponding threshold to a service data stream or a group of service data streams
  • the PCRF carries the monitoring key in the PCC rule corresponding to the service data stream or a group of service data streams.
  • the PCEF will monitor the service data flow corresponding to the PCC rule with the same Monitoring Key according to the threshold, and use the Monitoring Key to identify the reported usage.
  • the current PCC architecture supports simultaneous monitoring of multiple Monitoring Key instances, including monitoring the usage of the entire IP-CAN session and the usage of a specific service data stream.
  • the usage of the IP-CAN session corresponds to the Monitoring Key and the service data flow.
  • the Monitoring Key is not the same.
  • the PCEF can also perform usage monitoring control on an application or a group of applications.
  • usage monitoring can be applied to a single application, a group of applications, or all applications of a TDF session (TDF session level) (TDF sessions are typically associated with IP-CAN sessions).
  • the PCRF assigns a monitoring key and a corresponding threshold to an application or a group of applications
  • the PCRF carries the Monitoring Key in the ADC rule corresponding to the application or a group of applications
  • the PCEF or TDF will be based on the The value monitors the traffic of the application corresponding to the ADC rule of the same Monitoring Key, and uses the Monitoring Key to identify the reported amount.
  • the total allowed amount of a user's PDN can be saved in the SPR, that is, the total allowed amount of all traffic flows for an IP-CAN session, which can also be called the total per-PDN per user (Per PDN and UE). Dosage.
  • the SPR can also store the total allowed usage of certain specific services in a user's PDN, that is, the total allowed usage for a service data stream or a group of service data streams. It can also be identified by the Monitoring Key.
  • SPR When the user establishes an IP-CAN session to a PDN, SPR will send the total allowed amount to the PCRF.
  • PCRF When the PCRF performs the usage monitoring control, it will subscribe to the PCEF subscription usage report ( Usage_Report) event trigger.
  • Usage_Report usage report
  • the PCC rules with the same Monitoring Key share the threshold corresponding to the Monitoring Key.
  • all service data streams of the IP-CAN session share the threshold corresponding to the Monitoring Key.
  • PCEF will report to PCRF when it detects that the usage has reached a threshold, the IP-CAN session is terminated, all PCC rules containing a Monitoring Key are deleted/deactivated, or the PCRF explicitly requests usage. The consumption of the related Monitoring Key since the last time.
  • the PCRF When the PCRF receives the dose from the PCEF, the PCRF will deduct the reported usage value from the total allowable amount. If the PCEF needs to continue monitoring after reporting the usage of a certain Monitoring Key, the PCRF will provide a new threshold to the PCEF; if it is not necessary to continue monitoring, the PCRF will not provide a new threshold to the PCEF.
  • the PCRF When the last IP-CAN session of a user's Access Point Name (APN, Access Point Name) is terminated, the PCRF will save the remaining total allowed amount in the SPR, including the total allowed amount of the PDN or some of the PDN. The total allowable amount of specific business.
  • APN Access Point Name
  • TDF when a user establishes an IP-CAN session to a PDN, SPR will send the total allowed amount to the PCRF.
  • the PCRF performs the dose monitoring control, the PCRF subscribes to the PCEF subscription usage event trigger.
  • the Monitoring Key is included in the ADC rules, it has a phase
  • the threshold corresponding to the Monitoring Key is shared with the ADC rule of the Monitoring Key.
  • the Monitoring Key is not included in any ADC rule, all applications of the TDF session share the threshold corresponding to the Monitoring Key.
  • TDF detects that the usage has reached a threshold, the TDF session is terminated, all ADC rules containing a Monitoring Key are deleted/deactivated, or the PCRF explicit request is used, the TDF will report to the PCRF since the last time.
  • the PCRF When the PCRF receives the dose from the TDF, the PCRF will deduct the amount of the dose from the total allowable amount. If the amount of a Monitoring Key is used on the TDF and monitoring is required, the PCRF will provide a new threshold to the TDF; if no further monitoring is required, the PCRF will not provide a new threshold to the TDF.
  • the PCC architecture supports usage monitoring called Sponsored Data Connectivity.
  • the so-called sponsored data connection service can also be called sponsored data connection, which refers to the consumption consumption generated by the user for accessing the service, which is not borne by the user but by the service provider.
  • the AF provides the PCRF with the usage threshold of the service provider to access the service (that is, the user can access the service for free).
  • the PCRF sets the amount of the PCEF monitoring according to the amount of the amount of the AF issued.
  • the PCEF notifies the PCRF.
  • the existing IP-CAN session level usage monitoring strategy and the method for issuing the usage monitoring policy of the sponsored data connection service include the following steps:
  • the gateway where the PCEF is located receives the IP-CAN session establishment request, where the user identifier and the PDN identifier of the PDN network requesting access are carried;
  • the PCEF sends an IP-CAN session establishment indication to the PCRF, and carries the user identifier, the PDN identifier, and an IP address (IP Address) allocated to the UE in the IP-CAN session establishment indication message;
  • the PCRF sends a subscription document request to the SPR according to the received user identifier when determining that the user does not save the subscription information of the user, and carries the user identifier and the PDN identifier in the subscription document request.
  • the SPR returns a subscription document response to the PCRF, where the user subscription information corresponding to the received user identifier and the PDN identifier is included, and the user subscription information includes at least the user.
  • PDN Per PDN and User
  • Total Allowed Usage TAU, Total Allowed Usage 1 (ie IP-CAN session level total allowable usage);
  • the PCRF formulates a policy according to the user subscription information returned by the SPR, the network policy, and the access information of the UE.
  • the usage monitoring policy includes: setting a Monitoring Keyl; setting an event trigger whose value is Usage_Report; setting the usage threshold (UT, Usage Threshold) 1.
  • the PCRF sets the threshold UT1 for the user according to the TAU1 obtained from the SPR, and UT1 ⁇ TAU1; after completing the policy formulation, returns an IP-CAN session establishment confirmation to the PCEF, which carries the above-mentioned setting of the Monitoring Keyl, UT1 and triggers the usage. Report the incident.
  • the usage monitoring is for all service data flows of the IP-CAN session, and the Monitoring Keyl is not included in any PCC rules (the PCRF indicates that the PCEF monitoring of the Monitoring Keyl is IP-CAN session level);
  • PCEF installation strategy including installing the above usage detection strategy.
  • the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, and the IP-CAN session establishment response carries the IP Address allocated to the UE in S202.
  • the UE may also establish another IP-CAN session with the PDN.
  • the Monitoring Keyl is for all traffic data flows of all IP-CAN sessions established by the UE and the PDN. That is, Monitoring Keyl is for PDN and UE combination (Per PDN and UE).
  • the PCEF performs a usage monitoring policy to perform usage monitoring on all service data flows accessed by the user (through one or more IP-CAN sessions) (ie, performing IP-CAN session-level usage monitoring). During this process, the PCEF may interact with the PCRF to report the consumed usage value and request a new usage threshold.
  • the UE connects to the server of the third-party application service provider (ASP) through the IP-CAN session established by S201 ⁇ S207 (including one or more IP-CAN sessions) and requests the service.
  • ASP server decides to provide the sponsored data connection service for the user, it provides the AF with the sponsored data connection service information, which includes the sponsor identification, the ASP identifier, the sponsored user identification information (such as IP Address), and the IP flow information and Allowed Usage Threshold (AUT) for sponsored services.
  • the sponsored data connection service information which includes the sponsor identification, the ASP identifier, the sponsored user identification information (such as IP Address), and the IP flow information and Allowed Usage Threshold (AUT) for sponsored services.
  • the AF is located in the PDN in the above step; 5209, the AF provides the sponsored data connection service information to the PCRF, where the information includes the sponsor identifier, the ASP identifier, the sponsored user identifier information (such as IP Address), the IP stream information of the sponsored service, and the allowable usage threshold;
  • the PCRF After storing the sponsored data connection service information, the PCRF returns an acknowledgement message to the AF. S211.
  • the PCRF makes a policy decision based on the sponsored data connection service information, the network policy, and the user subscription information obtained from the AF, and formulates a PCC rule.
  • the PCRF decides to monitor the usage of the sponsored data connection services and develops a usage monitoring strategy, including: setting the Monitoring Key2 and the usage threshold UT2, where UT2 ⁇ AUT.
  • the PCRF includes the Monitoring Key2 in the PCC rule corresponding to the service;
  • the PCRF sends a policy and charging rule providing message to the PCEF, where the PCC rule including the Monitoring Key2 and the corresponding usage threshold UT2 prepared by S211 is carried;
  • the UEF After the PCEF installs the policy, the UEF returns a policy and a charging rule to provide confirmation.
  • PCEF performs both IP-CAN session level usage monitoring and service data flow level usage monitoring. At this time, the consumption of Monitoring Key2 will also be accumulated in the consumption of the IP-CAN session level.
  • the PCRF needs to instruct the PCEF to monitor the IP-CAN session level according to the subscription data in the SPR (that is, all IPs of the UE to the PDN).
  • the AF will provide the sponsored usage amount to the PCRF, and the PCRF instructs the PCEF to monitor the sponsored service.
  • the amount of data connection In this case, PCEF will also calculate the usage of the user's access to the sponsored data connection service in the IP-CAN session level, which will eventually lead to usage monitoring errors.
  • the technical problem to be solved by the present invention is to provide a usage monitoring method and a PCRF to solve the user's IP-CAN session level usage monitoring while accessing the sponsored data connection service through the monitored IP-CAN session.
  • the resulting dose monitors for erroneous defects.
  • a usage monitoring method applied to a policy and charging control architecture including:
  • the policy execution function entity reports the first usage report of the session level to the policy and the charging rule function entity (PCRF) when the user's session level usage reporting condition is met;
  • the PCRF After receiving the PCRF, requesting, by the policy execution function entity, the second usage report corresponding to the service or application that is not required to be accumulated into the session level by the user through the IP-CAN session; After the second usage report of the functional entity replies, the PCRF uses the difference between the value reported by the first usage amount and the value reported by the second usage amount as the cumulative usage value of the session level.
  • the session level usage reporting condition includes: the value of the first usage report of the session level has reached a first threshold.
  • the usage monitoring method further includes: after obtaining the cumulative usage value, the PCRF updates the locally allowed total usage amount of the session level to a difference between the original total allowable usage value and the accumulated usage value.
  • the usage monitoring method further includes: after the total allowed usage value of the session level is updated, if the PCRF decides to continue monitoring the usage of the session level, the PCRF will be based on the updated total allowed usage value.
  • the first threshold value corresponding to the re-set the session is sent to the policy execution function entity, and the value of the locally saved first threshold is updated by the policy execution function entity.
  • the usage monitoring method further includes: after the PCRF receives the second usage amount replied by the policy execution function entity, the locally saved service or application of the user that does not need to be accumulated into the session level usage
  • the corresponding allowable amount threshold is updated to the difference between the original allowable amount threshold and the value reported by the second amount.
  • the usage monitoring method further includes: a service in the user that does not need to accumulate usage at the session level After the update of the corresponding allowable usage threshold is completed, if the PCRF decides to continue monitoring the usage of the service or application that does not need to be accumulated into the session level, the PCRF will re-establish the threshold according to the updated allowable usage threshold. And the second threshold value corresponding to the service or the application that is not required to be accumulated into the session level is sent to the policy execution function entity, where the policy execution function entity performs corresponding value of the locally saved second threshold value. Update.
  • the usage monitoring method further includes: when the usage condition of the user or the application that does not need to accumulate the usage of the session level is satisfied, the policy execution function entity reports to the PCRF that the user does not need to accumulate the session.
  • the third amount of service corresponding to the level of usage of the business or application;
  • the locally saved user accesses the total allowable usage value of the session level used by the service or application that does not need to accumulate the session level usage to the original total allowable usage value and the third
  • the sum of the values of the usage report, and the locally allowed amount of the allowable usage threshold corresponding to the service or application that does not need to be accumulated into the session level usage of the user is updated to be the difference between the original allowable usage threshold and the value of the third usage report. value.
  • the condition that the user does not need to accumulate the usage of the session-level usage or the application includes: the value of the third usage of the service or the application that does not need to be accumulated into the session-level usage of the user has been reached. All the policy rules corresponding to the second threshold of the service or application that does not need to accumulate the usage of the session level, or the monitoring key that contains the service or application that does not need to accumulate the usage of the session level are deleted or deactivated, or The PCRF explicitly requests the policy execution function entity to report the usage amount of the service or application that does not need to accumulate the session level usage of the user.
  • the session level usage is an IP connection access network (IP-CAN) session level usage
  • the session level usage is a TDF session level usage.
  • the policy enforcement function entity is a policy and charging execution function PCEF
  • the session level usage is an IP-CAN session level usage
  • the policy rule is a policy and charging control rule
  • the session level usage is TDF session level usage
  • the policy rule is application detection and control.
  • the service or application that does not need to accumulate the usage of the session level is:
  • a sponsored data connection or a business or application that does not need to accumulate session-level usage based on user subscription or network policies.
  • a usage monitoring system is applied to the policy and charging control architecture, and includes: a usage report receiving device, a second usage report device, and a cumulative usage calculation device;
  • the usage report receiving device is configured to: receive a first usage report of the user session level reported by the policy execution function entity; and receive the user not required to accumulate the session through the IP-CAN session reported by the policy execution function entity The second usage report corresponding to the level usage business or application;
  • the second usage report requesting device is configured to: after the usage report receiving device receives the first usage report, request the second usage report from the policy execution function entity;
  • the cumulative usage value calculation device is configured to: after the usage report receiving device receives the second usage report, the difference between the value of the first usage report and the value of the second usage report is used as a session The cumulative usage value of the level.
  • the usage monitoring system further includes a total allowable amount value updating device
  • the total allowable usage value update device is configured to: after the cumulative usage value calculation device calculates the cumulative usage amount value, update the locally saved session level total allowable usage value to the original total allowable usage value and The difference between the cumulative usage values.
  • the usage monitoring system further includes a first wide value delivery device
  • the first threshold issuing device is configured to: when the PCRF decides to continue monitoring the usage of the session level, the first session corresponding to the session that is reset according to the updated session level total allowed usage value The threshold value is sent to the policy execution function entity.
  • the usage monitoring system further includes an allowable usage threshold update device
  • the allowable amount threshold updating device is configured to: after the usage report receiving device receives the second usage report, the locally reserved content of the user or the application corresponding to the service or application that does not need to be accumulated into the session level usage
  • the threshold value is updated as the difference between the original allowable amount threshold and the value of the second amount.
  • the usage monitoring system further includes a second wide value delivery device;
  • the second wide value issuing device is configured to: when the usage monitoring system decides to continue monitoring the usage of the service or application level that does not need to be accumulated into the session level, according to the updated allowed usage threshold
  • the second threshold value corresponding to the service or application that is not required to be accumulated in the session-level usage is sent to the policy execution function entity.
  • the usage report receiving device is further configured to: receive, when the usage condition of the service or the application that does not need to be accumulated into the session level is satisfied, the policy execution function entity reports the non-accumulation The third usage report corresponding to the service or application of the usage level; the total allowable usage value update device is further configured to: after the usage report receiving device receives the third usage > 3 ⁇ 4, the locally saved The session-level total allowable usage value used by the user to access the service or application that does not need to accumulate the session-level usage is updated to the sum of the original total allowable usage value and the value of the third usage report;
  • the allowable amount threshold updating device is further configured to: after the usage report receiving device receives the third usage amount>3 ⁇ 4, the locally saved service or application corresponding to the user that does not need to be accumulated into the session level usage The allowable usage threshold is updated to the difference between the original allowable usage threshold and the third usage amount.
  • the session level usage is an IP-CAN session level usage
  • the session level usage is a TDF session level usage.
  • the usage monitoring system is included in a Policy Control and Charging Rules Function Entity (PCRF).
  • PCRF Policy Control and Charging Rules Function Entity
  • a sponsored data connection or a business or application that does not need to accumulate session-level usage based on user subscription or network policies.
  • the PCRF is more accurate based on the policy control decision of the quantity monitoring.
  • BRIEF abstract 1 is a schematic diagram of a Rel-8 PCC non-roaming architecture in the prior art
  • FIG. 2 is a flow chart of the IP-CAN session level usage monitoring strategy and the usage monitoring strategy of the sponsored data connection service in the prior art
  • FIG. 3 is a flow chart of reporting IP-CAN session level usage according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of reporting a service data flow level usage according to an embodiment of the present invention. Preferred embodiment of the invention
  • the PCEF reports the first usage report of the current IP-CAN session level of the user to the PCRF;
  • the user's IP-CAN session level usage reporting condition may be: the value of the user's current IP-CAN session level usage has reached a preset first threshold;
  • the PCRF may first determine whether the user accesses the sponsored data connection through the monitored IP-CAN session, and if so, may initiate a request to the PCEF to request the second usage report. ;
  • the PCRF After receiving the second usage report of the PCEF reply, the PCRF uses the difference between the value of the first usage report and the value reported by the second usage as the cumulative usage value of the current IP-CAN session level.
  • the PCRF may also update the locally saved IP-CAN session level total allowable usage value of the user to the difference between the original total allowable usage value and the accumulated usage value. If the PCRF decides to continue to monitor the usage of the IP-CAN session level, the first wide value corresponding to the IP-CAN session reset according to the updated total allowed usage value may be sent to the PCEF, and the PCEF is localized. The value of the saved first threshold is updated accordingly. Wherein, the value of the reset first threshold value may be less than or equal to the updated total allowable usage value.
  • the PCRF may further update the difference between the allowable usage threshold value of the sponsored data connection of the user and the value of the second usage report that is locally updated.
  • the allowable usage threshold for the sponsored data connection If the PCRF decides to continue The second wide value corresponding to the sponsored data connection that is reset according to the updated allowable usage threshold is sent to the PCEF, and the PCEF performs corresponding update locally.
  • the value of the reset second threshold may be less than or equal to the updated allowed amount threshold.
  • the PCEF reports the third usage report corresponding to the sponsored data connection to the PCRF; wherein the usage reporting condition of the sponsored data connection may be: the third corresponding to the currently sponsored data connection
  • the usage reporting condition of the sponsored data connection may be: the third corresponding to the currently sponsored data connection
  • the amount of the usage report has reached the second threshold, or all PCC rules containing the monitoring key of the sponsored data connection are deleted or deactivated, or the PCRF explicitly requests the PCEF to report the amount corresponding to the sponsored data connection.
  • the -CAN session level total allowable usage value is updated to the sum of the original total allowable usage value and the value of the third usage amount, and the difference between the allowable usage threshold of the user's sponsored data connection and the third usage amount As an updated allowable usage threshold for the sponsored data connection.
  • the IP-CAN session level usage reporting process includes the following steps:
  • the PCEF performs the next step; wherein, the IP-CAN session level usage reporting condition includes, but is not limited to, including: a current IP-CAN session level (identified by Monitoring Keyl) The dosage has reached the corresponding threshold (ie UT1). It should be noted that the amount of the amount described herein reaches a threshold value means that the amount is equal to the threshold;
  • the PCEF reports to the PCRF through the policy and charging rule to report the usage report of the IP-CAN session level, where the current usage report of the IP-CAN session level is carried.
  • Usage Reprotl
  • the PCRF makes a decision based on the usage report reported by the PCEF.
  • PCRF determines the user
  • the IP-CAN session (including one or more IP-CAN sessions) monitored by the IP-CAN session level usage accesses the sponsored data connection service, so the IP-CAN session level usage reported by the PCEF (the usage corresponding to the Monitoring Keyl) is reported.
  • the value contains the amount of the sponsored data connection (that is, the amount corresponding to Monitoring key2), but these consumptions must be deducted from the value reported by the IP-CAN session level. Therefore, the PCRF sends a usage report request to the PCEF, where the Monitoring key2 is carried to request the current consumption consumption corresponding to the Monitoring key2;
  • the PCEF returns a dose response to the PCRF
  • the PCEF reports the usage report to the PCRF, where the usage of the sponsored data connection UR2 is carried;
  • the PCRF updates the allowable usage threshold AUT value corresponding to the local Monitoring Key2 to
  • the PCRF decides to continue monitoring the amount of the sponsored data connection, the PCRF carries the Monitoring Key2 and the corresponding updated usage threshold UT2' in the usage report confirmation returned to the RCEF; otherwise, the process ends.
  • the value of UT2' is less than or equal to the value of the updated AUT (obviously the updated AUT is greater than 0);
  • PCRF makes policy decisions.
  • the UR2 obtained by S305 is deducted from UR1 obtained through S302, and the total allowable amount TAU1 corresponding to Monitoring Keyl is updated to TAU1-UR1 + UR2;
  • the PCRF decides to continue monitoring the usage of the Monitoring Key1, the PCRF carries the Monitoring Key1 and the corresponding updated usage threshold UT1' in the policy and charging rule request confirmation; otherwise, the process ends.
  • the value of UT1' is less than or equal to the value of the updated TAU1 (obviously the updated TAU1 is greater than 0);
  • the execution and interaction process of the PCRF and the PCEF It is similar.
  • the PCEF sends a PCR report to the PCRF to report the usage of the user IP-CAN session level (the usage report corresponding to the Monitoring Keyl).
  • PCEF requests user access
  • the IP-CAN session access does not need to accumulate the usage report corresponding to the IP-CAN session level usage (the usage report corresponding to Monitoring Key2); the IPEF CAN session level is not required to be accumulated after receiving the PCEF reply.
  • the PCRF takes the difference between the value reported by the IP-CAN session level and the value of the usage report corresponding to the service that does not need to be accumulated into the IP-CAN session level as the cumulative IP-CAN session level. Usage value.
  • the UE accesses the sponsored data connection through the IP-CAN session, or an application that does not need to accumulate TDF session level usage according to the user's subscription or network policy, and the execution and interaction process of the PCRF and the TDF It is similar.
  • the TDF session level usage reporting condition is met, the TDF reports the usage report of the user TDF session level (the usage report corresponding to the Monitoring Key 1) to the PCRF.
  • the TDF requests the TDF to access the user through the IP-CAN session.
  • the usage report corresponding to the application of the TDF session level is not required to be accumulated (the usage report corresponding to the Monitoring Key2); after receiving the usage report corresponding to the application of the TDF reply that does not need to be accumulated into the TDF session level, the PCRF will The difference between the value of the usage report of the TDF session level and the value of the usage amount corresponding to the service that does not need to be accumulated into the TDF session level is used as the cumulative usage value of the TDF session level.
  • the usage report reporting process at the service data flow level includes the following steps:
  • the usage of the service data level includes, but is not limited to, the current service data level (identified by Monitoring Key2) has reached the corresponding usage.
  • the threshold ie UT2
  • all PCC rules containing the Monitoring Key2 are deleted/deactivated, or the PCRF explicitly requests the PCEF to report the usage of the Monitoring Key2;
  • the PCEF reports the policy and charging rule request to the PCRF, where the current usage report of the service data level corresponding to Monitoring 6 2 is 1 ⁇ 86 ⁇ 0112 (1; 1 2 ), where the current usage has reached the corresponding threshold.
  • the value of UR2 is equal to the value of UT2;
  • the PCRF makes a decision according to the usage report reported by the PCRF.
  • the PCRF determines that the IP-CAN session through which the user accesses the sponsored data connection service also performs IP-CAN session level usage monitoring. Since the service data corresponding to the Monitoring Key 2 is a sponsored data connection, it should not be accumulated in the usage of the IP-CAN session level (ie, the usage amount corresponding to the Monitoring Keyl). Cause Therefore, the total allowable amount TAU1 of the user's IP-CAN session level is updated to TAU1+UR2, and the allowable usage threshold AUT of the sponsored data connection is updated to AUT-UR2;
  • the PCRF determines to continue to monitor the usage of the Monitoring Key2, the PCRF returns the policy and the charging rule request confirmation to the PCEF to carry the Monitoring Key2 and the corresponding usage threshold UT2.
  • the value d of UT2 ' is equal to the value of the updated AUT;
  • the execution and interaction process of the PCRF and the PCEF It is similar.
  • the PCEF reports to the PCRF the usage report corresponding to the service that does not need to accumulate the IP-CAN session level usage (the usage report corresponding to the Monitoring Key2)
  • the locally saved IP-CAN session level used by the user that does not need to accumulate IP-CAN session level usage is updated to the original total allowable usage value and does not need to be accumulated.
  • the sum of the values of the usage report corresponding to the service of the IP-CAN session level usage, and the locally allowed allowable usage threshold value of the user that does not need to be accumulated into the IP-CAN session level usage is updated to the original allowable usage threshold and There is no need to accumulate the difference in the value of the usage report corresponding to the service entering the IP-CAN session level.
  • the UE accesses the sponsored data connection through the IP-CAN session, or an application that does not need to accumulate TDF session level usage according to the user's subscription or network policy, and the execution and interaction process of the PCRF and the TDF It is similar.
  • the PCRF according to the embodiment of the present invention is applied to a policy and charging control architecture, and includes: a usage report receiving device, a second usage report request device, and a cumulative usage computing device, wherein:
  • the usage report receiving device is configured to: receive a first usage report of the user IP-CAN session level reported by the PCEF; and receive a second usage report corresponding to the sponsored data connection accessed by the PCEF through the IP-CAN session. ;
  • the second usage report requesting device is configured to: after the usage report receiving device receives the first usage report, request the second usage report from the PCEF;
  • the cumulative usage value calculation device is configured to: after the usage report receiving device receives the second usage report, the difference between the value of the first usage report and the value of the second usage report is used as an IP - The cumulative usage value of the CAN session level.
  • the PCRF may further include a total allowable usage value updating device, where the total allowable usage value updating device is configured to: after the cumulative usage value computing device calculates the cumulative usage value, the IP of the user saved locally The -CAN session level total allowable usage value is updated to the difference between the original total allowable usage value and the stated cumulative usage value.
  • the PCRF may further include a first threshold issuing device, where the first threshold issuing device is configured to: according to the updated IP-CAN session when the PCRF decides to continue monitoring the usage of the IP-CAN session level.
  • the first threshold value corresponding to the IP-CAN session whose level is allowed to be reset is sent to the PCEF.
  • the above-mentioned PCRF may further include an allowable usage threshold update device, and the allowable usage threshold update device is configured to: after the usage report receiving device receives the second usage report, the locally saved user-sponsored data connection corresponding to the user The allowable usage threshold is updated to the difference between the original allowable usage threshold and the second usage amount.
  • the PCRF may further include a second threshold issuing device, where the second threshold issuing device is configured to: when the PCRF decides to continue monitoring the usage of the sponsored data connection level, it will be wider according to the updated permitted amount.
  • the second threshold corresponding to the sponsored data connection that is reset by the value is sent to the PCEF.
  • the usage report receiving device is further configured to: receive a praise that satisfies the user
  • the total allowable usage value updating device is further configured to: after the usage report receiving device receives the third usage report, the locally saved IP used by the user to access the sponsored data connection- The total allowable usage value of the CAN session level is updated to the sum of the original total allowable usage value and the value reported by the third usage amount;
  • the allowable amount threshold updating device is further configured to: after the usage report receiving device receives the third usage report, update the locally allowed permitted value of the user's sponsored data connection to the original allowable value The difference between the amount of use and the value of the third amount.
  • the usage monitoring system of the embodiment of the present invention is applied to a policy and charging control architecture, and includes: a usage report receiving device, a second usage report request device, and a cumulative usage computing device;
  • the usage report receiving device is configured to: receive a first usage report of a user session level reported by the policy execution function entity; and further receive the user that is reported by the policy execution function entity
  • the second usage report corresponding to the service or application of the IP-CAN session access does not need to be accumulated into the session level usage
  • the second usage report requesting device is configured to: after the usage report receiving device receives the first usage report, request the second usage report from the policy execution function entity;
  • the cumulative usage value calculation device is configured to: after the usage report receiving device receives the second usage report, the difference between the value of the first usage report and the value of the second usage report is used as a session The cumulative usage value of the level.
  • the usage monitoring system further includes a total allowable amount value updating device
  • the total allowable usage value update device is configured to: after the cumulative usage value calculation device calculates the cumulative usage amount value, update the locally saved session level total allowable usage value to the original total allowable usage value and The difference between the cumulative usage values.
  • the usage monitoring system further includes a first wide value delivery device
  • the first threshold issuing device is configured to: when the PCRF decides to continue monitoring the usage of the session level, the first session corresponding to the session that is reset according to the updated session level total allowed usage value The threshold value is sent to the policy execution function entity.
  • the usage monitoring system further includes an allowable usage threshold update device;
  • the allowable amount threshold updating device is configured to: after the usage report receiving device receives the second usage amount, the locally saved service or application of the user that does not need to be accumulated into the session level usage corresponding to the user
  • the allowable amount threshold is updated to the difference between the original allowable amount threshold and the second amount.
  • the usage monitoring system further includes a second wide value delivery device
  • the second wide value issuing device is configured to: when the usage monitoring system decides to continue monitoring the usage of the service or application level that does not need to be accumulated into the session level, according to the updated allowed usage threshold The second threshold value corresponding to the service or application that is not required to be accumulated in the session-level usage is sent to the policy execution function entity.
  • the usage report receiving device is further configured to: receive, when the usage condition of the service or the application that does not need to be accumulated into the session level is satisfied, the policy execution function entity reports the non-accumulation The third usage report corresponding to the service or application of the usage level; the total allowable usage value update device is further configured to: after the usage report receiving device receives the third usage report, the locally saved user access The session-level total allowable usage value used by the service or application that does not need to accumulate the session-level usage is updated to the sum of the original total allowable usage value and the value of the third usage report;
  • the allowable amount threshold updating device is further configured to: after the usage report receiving device receives the third usage amount>3 ⁇ 4, the locally saved service or application corresponding to the user that does not need to be accumulated into the session level usage The allowable usage threshold is updated to the difference between the original allowable usage threshold and the third usage amount.
  • the session level usage is an IP-CAN session level usage
  • the session level usage is a TDF session level usage.
  • the usage monitoring system is included in a Policy Control and Charging Rules Function Entity (PCRF).
  • PCRF Policy Control and Charging Rules Function Entity
  • the technical solution of the invention makes the PCRF control decision based on the quantity monitoring strategy more precise, and therefore has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种用量监测方法和系统，应用于策略和计费控制架构中，该方法包括：当满足用户的会话级别用量上报条件时，策略执行功能实体向策略与计费规则功能实体（PCRF）上报所述会话级别的第一用量报告；所述PCRF收到后，向所述策略执行功能实体请求所述用户通过所述会话访问的不需累计入会话级别用量的业务或应用对应的第二用量报告；在收到所述策略执行功能实体回复的所述第二用量报告后，所述PCRF将所述第一用量报告的值与所述第二用量报告的值的差值作为所述会话级别的累计用量值。采用上述技术方案后，使得PCRF基于用量监测的策略控制决策更加精确。

Description

用量监测方法及策略控制与计费规则功能实体
技术领域
本发明涉及策略与计费规则功能实体（PCRF, Policy and Charging Rules Function )技术领域， 尤其涉及一种用量监测方法及 PCRF。
背景技术
第三代合作伙伴计划（3GPP , 3rd Generation Partnership Project )的策略 和计费控制 （PCC, Policy and Charging Control )架构是一个能够应用于多种 接入技术的功能框架。 其可应用于通用移动通信系统 （UMTS , Universal Mobile Telecommunications System ) 的陆上无线接入网 （UTRAN, UMTS Terrestrial Radio Access Network )、 全球移动通信系统 ( GSM, Global system for Mobile Communication ) /GSM数据增强演进 ( EDGE , Enhanced Data rates for Global Evolution )无线接入网、 互通无线局域网 （I-WLAN ) 以及演进的 分组系统（ EPS , Evolved Packet System )等。
如图 1所示， 在 Rel-8 PCC非漫游架构中各个逻辑功能实体及接口功能 下：
应用功能实体 ( AF, Application Function )用于提供业务应用的接入点， 这些业务应用所使用的网络资源需要进行动态的策略控制。 在业务面进行参 数协商时， AF将相关业务信息传递给与其通过 Rx接口相连的 PCRF; PCRF 如果判断出接收到的业务信息与本地配置的策略一致， 则接受该协商； 否则 拒绝该协商， 并在反馈中同时给出 PCRF可接受的业务参数。 随后， AF可将 这些参数返回给用户设备 ( UE, User Equipment ) ；
PCRF是 PCC的核心， 负责策略决策和计费规则的制定。 PCRF提供了 基于业务数据流的网络控制规则， 这些网络控制包括业务数据流的检测、 门 控（ Gating Control ) 、 服务质量（QoS, Quality of Service )控制以及基于数 据流的计费规则等。 PCRF将其制定的策略和计费规则发送给策略和计费执行 功能实体（ PCEF , Policy and Charging Enforcement Function )执行，同时， PCRF 还需要保证这些规则和用户的签约信息一致。 PCRF制定策略和计费规则的依 据包括：从 AF获取与业务相关的信息；从用户签约数据库（SPR, Subscription Profile Repository )获取与用户策略计费控制相关的签约信息； 从 PCEF获取 与承载相关的网络信息。
PCEF 通常位于网关 （GW, Gate-Way ) 内， 如通用分组无线服务技术
( GPRS, General Packet Radio Service ) 中的 GPRS网关支持节点 （ GGSN, Gateway GPRS Support Node )以及 I-WLAN中的分组数据网关（ PDG, Packet Data Gateway ) , 在承载面执行 PCRF所制定的策略和计费规则。 PCEF按照 PCRF所发送的规则中的业务数据流过滤器对业务数据流进行检测，进而对这 些业务数据流执行 PCRF所制定的策略和计费规则。在承载建立时， PCEF按 照 PCRF发送的规则进行 QoS授权， 并根据 AF的执行进行门控控制。 根据 PCRF发送的计费规则， PCEF执行相应的业务数据流的计费操作， 计费方式 既可以是在线计费， 也可以是离线计费。 如果釆用在线计费方式， PCEF则需 要和在线计费系统（OCS, Online Charging System )—起进行信用管理。 釆用 离线计费方式时， PCEF需要和离线计费系统（ OFCS , Offline Charging System ) 之间交换相关计费信息。 PCEF与 PCRF之间的接口是 Gx接口，与 OCS之间 的接口是 Gy接口， 与 OFCS之间的接口是 Gz接口。 PCEF也可以具有应用 检测和控制 （ ADC, Application Detection and Control )功能。 PCEF可以根 据本地配置或是 PCRF下发的包含应用检测控制策略的应用检测控制（ADC, 重定向、 带宽限制和用量监控） ； ； ' ^
此外，网络中还可能存在业务检测功能（ TDF , Traffic Detection Function ) , 此时 TDF与 PCRF通过 Sd接口， TDF可以根据预配置或 PCRF下发的 ADC 规则进行应用检测和策略执行。
承载绑定和事件报告功能实体 ( BBERF , Bearer Binding and Event
Reporting Function ) , 其功能包括承载绑定、 上行承载绑定的验证以及事件报 告。 当 UE通过演进通用地面无线接入网 （E-UTRAN, Evoluted Universal Terrestrial Radio Access )接入， 并且服务网关（S-GW, Serving Gateway )与 分组数据网网关（ P-GW, PDN Gateway )之间釆用代理移动 Ιρν6 ( ΡΜΙΡνό ) 协议时， BBERF就位于 S-GW; 当 UE通过可信任非 3GPP接入系统接入时， BBERF位于可信任非 3GPP接入网关； 当 UE通过不可信任非 3GPP接入系 统接入时、 BBERF位于演进的分组数据网关 （ePDG, Evolved Packet Data Gateway ) 。 此时， PCEF不再执行承载绑定功能；
SPR与 PCRF之间通过 Sp接口相连，其中存储了和策略控制与计费相关 的用户策略计费控制签约信息；
OCS和 PCEF—起进行在线计费方式下用户信用的控制和管理；
OFCS与 PCEF—起完成离线计费方式下的计费操作。
PCC 架构通过以上各功能实体实现了对 UE 为访问一个分组数据网络 ( PDN , Packet Data Network ) 所建立的 IP 连接接入网 （IP-CAN , IP Connectivity Access Network )会话的策略计费控制。
现有技术中， PCC支持动态的用量监测控制， 以实现基于实时的网络资 源使用总量执行动态的策略决策。 用量监测可应用于单个业务数据流、 一组 业务数据流或者一个 IP-CAN会话的所有业务数据流（简称为 IP-CAN会话级 别） 。 若 UE到某个 PDN建立了多个 IP-CAN会话， 则用量监测也可应用于 这多个 IP-CAN会话。此时 IP-CAN会话级别的用量监测是监测这多个 IP-CAN 会话的所有业务数据流。 目前， 用量（usage )指用户面数据流量。 现有技术 中， 釆用监测键（ Monitoring Key )来标识一个需要进行用量监测的实例， 比 如： 当 PCRF为一个 IP-CAN会话的所有业务流分配了 Monitoring Key以及相 应的阔值后， PCEF将根据该阔值监测该 IP-CAN会话的所有业务流流量， 并 用该 Monitoring Key来标识上 ^艮的用量。 当 PCRF为一个业务数据流或一组 业务数据流分配了 Monitoring Key 以及相应的阔值后， PCRF 会将该 Monitoring Key携带在这个业务数据流或一组业务数据流对应的 PCC规则中， 此后， PCEF将根据该阔值监测具有相同 Monitoring Key的 PCC规则所对应 的业务数据流流量， 并用该 Monitoring Key标识上报的用量。 目前的 PCC架 构支持同时监测多个 Monitoring Key实例，包括同时监测整个 IP-CAN会话的 用量和某个具体业务数据流的用量， 此时 IP-CAN 会话的用量对应的 Monitoring Key和业务数据流的 Monitoring Key是不相同的。 当 PCEF支持 ADC时， PCEF也可以对一个应用或一组应用进行用量监测控制。 类似地，对于 TDF,用量监测可应用于单个应用、一组应用或者一个 TDF 会话的所有应用 （ TDF会话级别） （ TDF会话通常和 IP-CAN会话是——对 应的） 。 此时， 当 PCRF为一个应用或一组应用分配了 Monitoring Key以及 相应的阔值时， PCRF将 Monitoring Key携带在这个应用或一组应用对应的 ADC规则中，那么， PCEF或 TDF将根据该阔值监测具有相同 Monitoring Key 的 ADC规则所对应的应用的流量， 并用该 Monitoring Key标识上报的用量。
同时， 在 SPR中还可以保存用户某个 PDN的总允许用量， 即针对一个 IP-CAN会话的所有业务流的总允许用量， 也可以称为每 PDN每用户 （Per PDN and UE ) 的总允许用量。 SPR中还可以保存用户某个 PDN中的某些具 体业务的总允许用量， 即针对一个业务数据流或一组业务数据流的总允许用 量 , 通常也可以用 Monitoring Key进行标识。
当用户建立到某个 PDN的 IP-CAN会话后， SPR将总允许用量下发给 PCRF。 PCRF 在进行用量监测控制时， 会向 PCEF 订阅用量上报 ( Usage— Report )事件触发器。 当 Monitoring Key包含在 PCC规则中下发后， 具有相同 Monitoring Key的 PCC规则共享该 Monitoring Key对应的阔值。 当 Monitoring Key不包含在任何 PCC规则中时， IP-CAN会话的所有业务数据流 共享该 Monitoring Key对应的阔值。 PCEF在监测到用量已达到阔值、 IP-CAN 会话终结、 包含某个 Monitoring Key的所有 PCC规则均被删除 /去激活、 或者 PCRF 显式请求用量上^艮时， 将向 PCRF ^艮告自从上一次上 ^艮以来相关 Monitoring Key的用量消耗情况。当 PCRF收到来自 PCEF的用量上报后， PCRF 将从总允许用量中扣除上报的用量值。如果 PCEF上报完某个 Monitoring Key 的用量后需要继续进行监测， 则 PCRF将提供新的阔值给 PCEF; 若无需继续 进行监测， PCRF不提供新的阔值给 PCEF。 当用户的一个接入点名称（ APN, Access Point Name )的最后一个 IP-CAN会话终结时， PCRF将在 SPR中保存 剩余的总允许用量， 包括该 PDN的总允许用量或该 PDN的某些具体业务的 总允许用量。
类似地， 对于 TDF, 当用户建立到某个 PDN的 IP-CAN会话后， SPR将 总允许用量下发给 PCRF。 PCRF进行用量监测控制时， PCRF向 PCEF订阅 用量上报事件触发器。 当 Monitoring Key包含在 ADC规则中下发后， 具有相 同 Monitoring Key 的 ADC 规则共享该 Monitoring Key对应的阔值。 当 Monitoring Key不包含在任何 ADC规则中时， TDF会话的所有应用共享该 Monitoring Key对应的阔值。 TDF监测到用量已达到阔值、 TDF会话终结、 包含某个 Monitoring Key的所有 ADC规则均被删除 /去激活或者 PCRF显式请 求用量上 ^艮时， TDF将向 PCRF报告自从上一次上 ^艮以来相关 Monitoring Key 的用量消耗情况。 当 PCRF收到来自 TDF的用量上报后， PCRF将从总允许 用量中扣除上 ^艮的用量值。 如果 TDF上^艮某个 Monitoring Key的用量并且需 要继续进行监测， 那么， PCRF将提供新的阔值给 TDF; 若无需继续进行监 测， PCRF不提供新的阔值给 TDF。
目前， PCC 架构支持称为被赞助数据连接业务 （ Sponsored data connectivity ) 的用量监测。 所谓被赞助数据连接业务亦可称为被赞助数据连 接， 是指用户为访问业务所产生的用量消耗， 并不是由用户自己承担， 而是 由业务提供方承担。 此时， 当用户发起该类业务访问时， AF在向 PCRF提供 业务信息时，还会向 PCRF提供业务提供方赞助访问该类业务的用量阔值（即 用户可以免费访问该类业务的用量）。 此时， PCRF根据 AF下发的用量阔值 设置 PCEF监测的用量阔值， 当到达该阔值时， PCEF通知 PCRF。
如图 2所示， 现有 IP-CAN会话级别用量监测策略和被赞助数据连接业 务的用量监测策略的下发方法， 包括以下步骤：
5201 , 在 UE请求建立到 PDN的 IP-CAN会话的过程中， PCEF所在的 网关接收到 IP-CAN会话建立请求， 其中携带有用户标识和请求接入的 PDN 网络的 PDN标识；
5202, PCEF向 PCRF发送 IP-CAN会话建立指示， 并在该 IP-CAN会话 建立指示消息中携带用户标识、 PDN标识以及为上述 UE分配的 IP地址（IP Address ) ；
S203 , PCRF根据接收到的用户标识在判断出本地没有保存该用户的签 约信息时， 向 SPR发送签约文档请求， 并在该签约文档请求中携带上述用户 标识和 PDN标识；
S204, SPR向 PCRF返回签约文档应答， 其中携带有与接收到的用户标 识和 PDN标识对应的用户签约信息， 该用户签约信息中至少包含该用户该 PDN ( Per PDN and User ) 的总允许用量 （ TAU, Totally Allowed Usage ) 1 (即 IP-CAN会话级别总允许用量） ；
5205 , PCRF根据 SPR返回的用户签约信息、 网络策略、 UE的接入信息 等制定策略， 其中制定用量监测策略包括： 设置 Monitoring Keyl ; 设置取值 为 Usage— Report的事件触发器； 设置用量阔值（UT, Usage Threshold ) 1。 其中， PCRF根据从 SPR中获得的 TAU1 为用户设置阔值 UT1 , 且 UT1 < TAU1 ; 在完成策略制定后， 向 PCEF返回 IP-CAN会话建立确认， 其中携带 上述设置的 Monitoring Keyl、 UT1并触发用量上报事件。
这里，用量监测是针对 IP-CAN会话所有业务数据流的， Monitoring Keyl 不包含在任何 PCC规则中 （ PCRF指示 PCEF该 Monitoring Keyl的用量监测 为 IP-CAN会话级别） ；
5206, PCEF安装策略， 包括安装上述用量检测策略。 PCEF所在的网关 向上述 UE返回 IP-CAN会话建立应答，在 IP-CAN会话建立应答中携带有在 S202中为该 UE分配的 IP Address;
在 S206后， UE可能还会与该 PDN建立另外的 IP-CAN会话， 此时
Monitoring Keyl针对 UE与 PDN建立的所有 IP-CAN会话的所有业务数据流。 即 Monitoring Keyl是针对 PDN和 UE组合的 （ Per PDN and UE ) 。
5207, PCEF执行用量监测策略， 对用户访问该 PDN (通过一个或多个 IP-CAN会话）的所有业务数据流进行用量监测（即执行 IP-CAN会话级的用 量监测）。 在这个过程中， PCEF可能会与 PCRF进行交互， 上报消耗的用量 值以及请求新的用量阔值。
5208 , UE通过 S201~ S207建立的 IP-CAN会话（包含一个或多个 IP-CAN 会话）与第三方应用业务提供者（ASP, Application Service Provider ) 的服务 器连接并请求业务。 ASP服务器决定为该用户提供被赞助数据连接业务后， 向 AF提供动态的被赞助数据连接业务信息， 该信息中包括赞助方标识、 ASP 标识、 被赞助的用户标识信息 （如 IP Address ) 、 被赞助业务的 IP流信息和 允许用量阔值（AUT, Allowed Usage Threshold ) 。 即可以理解为 AF位于上 述步骤中的 PDN中； 5209, AF向 PCRF提供被赞助数据连接业务信息， 该信息中包括赞助方 标识、 ASP标识、 被赞助的用户标识信息 （如 IP Address ) , 被赞助业务的 IP流信息和允许用量阔值；
5210, PCRF保存上述被赞助数据连接业务信息后，向 AF返回确认消息； S211 , PCRF根据从 AF获得的被赞助数据连接业务信息、 网络策略以及 用户签约信息等进行策略决策， 制定 PCC规则。 PCRF决定对被赞助数据连 接业务进行用量监测， 制定用量监测策略， 包括： 设置 Monitoring Key2及用 量阔值 UT2 , 其中 UT2 < AUT。 PCRF将 Monitoring Key2包含在该业务对应 的 PCC规则中；
S212, PCRF向 PCEF下发策略和计费规则提供消息， 其中携带 S211制 定的包含 Monitoring Key2及对应的用量阔值 UT2的 PCC规则；
5213 , PCEF安装策略后， 向 PCRF返回策略和计费规则提供确认；
5214, PCEF同时执行 IP-CAN会话级别的用量监测和业务数据流级别的 用量监测。 此时， 对于 Monitoring Key2的用量消耗， 也会累计在 IP-CAN会 话级别的用量消耗中。
根据上述流程可知， 若 SPR中保存有某用户基于 IP-CAN会话级别的用 量签约数据， 即 PCRF需要根据 SPR中的签约数据指示 PCEF监测 IP-CAN 会话级别 （即该 UE到该 PDN的所有 IP-CAN会话的所有业务数据流） 的累 计用量。 而此时， 若该用户又通过其所建立到该 PDN的一个或多个 IP-CAN 会话访问了某种被赞助数据连接业务， AF将向 PCRF提供赞助的用量， PCRF 指示 PCEF监测该被赞助数据连接的用量。 在这种情况下， 就会导致 PCEF 也会把用户访问被赞助数据连接业务所产生的用量计算在 IP-CAN会话级别 的用量里面， 最终导致用量监测错误。
此外， 若根据用户签约或网络策略， 用户访问的某种或某些业务不应该 累计入 IP-CAN会话级别的用量时， 现有技术也会出现同样的问题。
类似地， 当 PCC架构引入了 TDF并且 TDF也执行用量时， 若用户访问 了被赞助数据连接或根据用户签约或网络策略， 用户访问的某种或某些应用 不应该累计入 TDF会话级别的用量时， 现有技术也会出现同样的问题。 发明内容
本发明要解决的技术问题是提供一种用量监测方法及 PCRF,以解决用户 在进行 IP-CAN会话级别的用量监测的同时又通过该被监测的 IP-CAN会话访 问了被赞助数据连接业务所引起的用量监测错误的缺陷。
一种用量监测方法， 应用于策略和计费控制架构中， 包括：
当满足用户的会话级别用量上报条件时， 策略执行功能实体向策略与计 费规则功能实体（PCRF )上报所述会话级别的第一用量报告；
所述 PCRF收到后，向所述策略执行功能实体请求所述用户通过 IP-CAN 会话访问的不需累计入会话级别用量的业务或应用对应的第二用量报告； 在收到所述策略执行功能实体回复的所述第二用量报告后， 所述 PCRF 将所述第一用量报告的值与所述第二用量报告的值的差值作为所述会话级别 的累计用量值。
其中， 所述会话级别用量上报条件包括： 所述会话级别的第一用量报告 的值已达到第一阔值。
该用量监测方法还包括： 在得到所述累计用量值后， 所述 PCRF将本地 保存的所述会话级别的总允许用量值更新为原总允许用量值与所述累计用量 值的差值。
该用量监测方法还包括： 在所述会话级别的总允许用量值完成更新后， 若所述 PCRF决定继续对所述会话级别的用量进行监测， 则所述 PCRF将根 据更新后的总允许用量值重新设置的所述会话对应的第一阔值下发给所述策 略执行功能实体， 由所述策略执行功能实体对本地保存的第一阈值的值进行 相应更新。
该用量监测方法还包括： 所述 PCRF在收到所述策略执行功能实体回复 的所述第二用量>¾告后， 将本地保存的所述用户的不需累计入会话级别用量 的业务或应用对应的允许用量阔值更新为原允许用量阔值与所述第二用量报 告的值的差值。
该用量监测方法还包括： 在所述用户的不需累计入会话级别用量的业务 或应用对应的允许用量阔值完成更新后， 若所述 PCRF决定继续对所述不需 累计入会话级别用量的业务或应用的用量进行监测， 所述 PCRF将根据更新 后的允许用量阔值重新设置的所述不需累计入会话级别用量的业务或应用对 应的第二阔值下发给所述策略执行功能实体， 由所述策略执行功能实体对本 地保存的第二阔值的值进行相应更新。
该用量监测方法还包括： 当满足所述用户的不需累计入会话级别用量的 业务或应用的用量上报条件时， 所述策略执行功能实体向所述 PCRF上报所 述用户的不需累计入会话级别用量的业务或应用对应的第三用量 ^艮告；
所述 PCRF收到后， 将本地保存的所述用户访问不需累计入会话级别用 量的业务或应用所使用的所述会话级别的总允许用量值更新为原总允许用量 值与所述第三用量报告的值的和， 将本地保存的所述用户的不需累计入会话 级别用量的业务或应用对应的允许用量阔值更新为原允许用量阔值与所述第 三用量报告的值的差值。
其中， 所述用户的不需累计入会话级别用量的业务或应用的用量上 4艮条 件包括： 所述用户的当前不需累计入会话级别用量的业务或应用对应的第三 用量的值已达到所述不需累计入会话级别用量的业务或应用对应的第二阔 值、 或包含所述不需累计入会话级别用量的业务或应用的监测键的所有策略 规则被删除或被去激活、 或所述 PCRF显式请求所述策略执行功能实体上报 所述用户的不需累计入会话级别用量的业务或应用对应的用量。
其中： 当所述策略执行功能实体为策略和计费执行功能（PCEF )时， 所 述会话级别用量为 IP连接接入网 （IP-CAN )会话级别用量；
当所述策略执行功能实体为应用监测功能 （TDF ) 时， 所述会话级别用 量为 TDF会话级别用量。
其中： 当所述策略执行功能实体为策略和计费执行功能 PCEF时， 所述 会话级别用量为 IP-CAN会话级别用量， 所述策略规则为策略和计费控制规 则；
当所述策略执行功能实体为应用监测功能 TDF时， 所述会话级别用量为 TDF会话级别用量， 所述策略规则为应用检测和控制。 其中： 所述不需累计入会话级别用量的业务或应用为：
被赞助数据连接或者根据用户签约或网络策略不需累计入会话级别用量 的业务或应用。
一种用量监测系统， 应用于策略和计费控制架构中， 包括： 用量报告接 收装置、 第二用量^艮告请求装置及累计用量计算装置；
所述用量报告接收装置设置成： 接收策略执行功能实体上报的用户会话 级别的第一用量报告； 还接收所述策略执行功能实体上报的所述用户通过 IP-CAN会话访问的不需累计入会话级别用量的业务或应用对应的第二用量 报告；
所述第二用量报告请求装置设置成： 在所述用量报告接收装置收到所述 第一用量报告后， 向所述策略执行功能实体请求所述第二用量报告；
所述累计用量值计算装置设置成： 在所述用量报告接收装置收到所述第 二用量报告后 , 将所述第一用量报告的值与所述第二用量报告的值的差值作 为会话级别的累计用量值。
该用量监测系统还包括总允许用量值更新装置；
所述总允许用量值更新装置设置成： 在所述累计用量值计算装置计算出 所述累计用量值后， 将本地保存的所述用户的会话级别总允许用量值更新为 原总允许用量值与所述累计用量值的差值。
该用量监测系统还包括第一阔值下发装置；
所述第一阔值下发装置设置成： 在所述 PCRF决定继续对所述会话级别 的用量进行监测时， 将根据更新后的会话级别总允许用量值重新设置的所述 会话对应的第一阔值下发给所述策略执行功能实体。
该用量监测系统还包括允许用量阈值更新装置；
所述允许用量阔值更新装置设置成： 在所述用量报告接收装置接收到所 述第二用量 告后， 将本地保存的该用户的不需累计入会话级别用量的业务 或应用对应的允许用量阔值更新为原允许用量阔值与所述第二用量 ^艮告的值 的差值。
该用量监测系统还包括第二阔值下发装置； 所述第二阔值下发装置设置成： 在所述用量监测系统决定继续对所述不 需累计入会话级别用量的业务或应用级别的用量进行监测时， 将根据更新后 的允许用量阔值重新设置的不需累计入会话级别用量的业务或应用对应的第 二阔值下发给所述策略执行功能实体。
其中： 所述用量报告接收装置还设置成： 接收在满足所述用户的不需累 计入会话级别用量的业务或应用的用量上报条件时， 所述策略执行功能实体 上报的所述不需累计入会话级别用量的业务或应用对应的第三用量报告； 所述总允许用量值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量>¾告后， 将本地保存的该用户访问所述不需累计入会话级别用 量的业务或应用所使用的会话级别总允许用量值更新为原总允许用量值与所 述第三用量 告的值的和；
所述允许用量阔值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量>¾告后， 将本地保存的该用户的不需累计入会话级别用量的业 务或应用对应的允许用量阔值更新为原允许用量阔值与所述第三用量 ^艮告的 值的差值。
其中： 当所述策略执行功能实体为策略和计费执行功能（PCEF )时， 所 述会话级别用量为 IP-CAN会话级别用量；
当所述策略执行功能实体为业务检测功能 （TDF ) 时， 所述会话级别用 量为 TDF会话级别用量。
所述用量监测系统包含于策略控制与计费规则功能实体（PCRF ) 中。 其中： 所述不需累计入会话级别用量的业务或应用为：
被赞助数据连接或者根据用户签约或网络策略不需累计入会话级别用量 的业务或应用。
釆用本发明的上述技术方案后， 使得 PCRF基于用量监测的策略控制决 策更加精确。
附图概述 图 1为现有技术中 Rel-8 PCC非漫游架构的示意图；
图 2为现有技术中 IP-CAN会话级别用量监测策略和被赞助数据连接业 务的用量监测策略的下发流程图；
图 3为本发明实施例中 IP-CAN会话级别用量的上报流程图；
图 4为本发明实施例中业务数据流级别用量的上报流程图。 本发明的较佳实施方式
本发明实施例的方法包括：
A、 当满足用户的 IP-CAN会话级别用量上报条件时， PCEF向 PCRF上 报该用户当前 IP-CAN会话级别的第一用量报告；
其中，用户的 IP-CAN会话级别用量上报条件可以为：该用户当前 IP-CAN 会话级别的用量的值已达到预设的第一阔值；
B、 PCRF收到后， 向 PCEF请求该用户通过上述 IP-CAN会话访问的被 赞助数据连接对应的第二用量报告；
其中， 在向 PCEF发起请求之前， PCRF可以先判断该用户是否通过该被 监测的 IP-CAN会话访问了被赞助数据连接， 若是， 则可向 PCEF发起请求， 以请求上述第二用量 4艮告；
C、 在收到 PCEF回复的第二用量报告后， PCRF将上述第一用量报告的 值与第二用量报告的值的差值作为当前 IP-CAN会话级别的累计用量值。
在得到上述累计用量值后， PCRF还可以将本地保存的该用户的 IP-CAN 会话级别总允许用量值更新为原总允许用量值与上述累计用量值的差值。 若 PCRF决定继续对上述 IP-CAN会话级别的用量进行监测，则可以将根据该更 新后的总允许用量值重新设置的 IP-CAN会话对应的第一阔值下发给 PCEF , 由 PCEF对本地保存的第一阔值的值进行相应更新。 其中， 重新设置的第一 阔值的值可以小于等于上述更新后的总允许用量值。
此外， PCRF在收到 PCEF回复的第二用量报告后，还可以将本地保存的 该用户的该被赞助数据连接对应的允许用量阔值与该第二用量报告的值的差 值作为更新后的该被赞助数据连接对应的允许用量阔值。 若 PCRF决定继续 对被赞助数据连接级别的用量进行监测， 则将根据该更新后的允许用量阔值 重新设置的该被赞助数据连接对应的第二阔值下发给 PCEF, 由 PCEF在本地 进行相应更新。 其中， 重新设置的第二阔值的值可以小于等于上述更新后的 允许用量阔值。
当满足被赞助数据连接的用量上报条件时， PCEF向 PCRF上报该被赞助 数据连接对应的第三用量报告； 其中， 被赞助数据连接的用量上报条件可以 为： 当前被赞助数据连接对应的第三用量报告的值已达到第二阔值、 或包含 该被赞助数据连接的监测键的所有 PCC规则被删除或被去激活、 或 PCRF显 式请求 PCEF上报该被赞助数据连接对应的用量。 PCRF收到后， 若判断出该 用户访问被赞助数据连接所通过的 IP-CAN会话还执行了 IP-CAN会话级别用 量监测， 则将本地保存的该用户访问该被赞助数据连接所使用的 IP-CAN会 话级别总允许用量值更新为原总允许用量值与上述第三用量^艮告的值的和， 将该用户的被赞助数据连接对应的允许用量阔值与上述第三用量的差值作为 更新后的该被赞助数据连接对应的允许用量阔值。
下文中将参考附图并结合实施例来详细说明本发明的实施例。 需要说明 的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组 合。
如图 3所示， IP-CAN会话级别的用量上报流程， 包括以下步骤：
S301 , 当满足 IP-CAN会话级别用量上报条件时， PCEF执行下一步骤； 其中， IP-CAN会话级别用量上报条件包括但不限于包括： 当前 IP-CAN会话 级别 （用 Monitoring Keyl来标识）的用量已达到相应阔值（即 UT1 ) 。 需要 说明的是， 本文所述用量达到阔值意指用量等于阔值；
5302, PCEF通过策略和计费规则请求向 PCRF上报 IP-CAN会话级别的 用量报告， 其中携带该 IP-CAN会话级别的当前用量报告 Usage Reprotl
( UR1 ) , 在当前用量报告的值已达到相应阔值的情况下， UR1的值和 UT1 的值相等；
5303 , PCRF根据 PCEF上报的用量报告进行决策。 PCRF判断出该用户 通过 IP-CAN会话级别用量监测的 IP-CAN会话 (包含一个或多个 IP-CAN会 话）访问被赞助数据连接业务， 因此 PCEF 上报的 IP-CAN会话级别用量 ( Monitoring Keyl对应的用量）报告的值中包含了被赞助数据连接的用量（即 Monitoring key2对应的用量）消耗，但这些用量消耗必须从 IP-CAN会话级别 的用量报告的值中扣除。 因此， PCRF向 PCEF发送用量上报请求， 其中携带 Monitoring key2 , 以请求 Monitoring key2对应的当前用量消耗；
5304, PCEF向 PCRF返回用量上 应答；
5305, PCEF向 PCRF上报用量报告， 其中携带上述被赞助数据连接的用 量 UR2;
S306, PCRF将本地 Monitoring Key2对应的允许用量阔值 AUT值更新为
AUT-UR2。 若 PCRF决定继续监测该被赞助数据连接的用量， 则 PCRF在向 RCEF返回的用量上报确认中携带 Monitoring Key2以及对应的更新后的用量 阔值 UT2'; 否则， 结束该流程。 其中， UT2'的值小于等于更新后的 AUT的 值（显然更新后的 AUT大于 0 ) ；
S307, PCRF进行策略决策。 从通过 S302获得的 UR1中扣除通过 S305 获得的 UR2 , 并将 Monitoring Keyl 对应的总允许用量 TAU1 更新为 TAU1-UR1 + UR2;
5308 , 若 PCRF决定继续监测 Monitoring Keyl对应的用量， 则 PCRF在 策略和计费规则请求确认中携带 Monitoring Keyl以及对应的更新后的用量阔 值 UT1'; 否则， 结束该流程。 其中， UT1'的值小于等于更新后的 TAU1的值 (显然更新后的 TAU1大于 0 ) ；
5309, PCEF安装策略后， 继续进行 IP-CAN会话级别和业务数据流级别 的用量监测。
类似地，若 UE通过 IP-CAN会话访问的不是被赞助数据连接， 而是一种 根据用户的签约或网络策略不需累计入 IP-CAN会话级别用量的业务， PCRF 和 PCEF的执行和交互流程是类似的。当满足用户的 IP-CAN会话级别用量上 才艮条件时， PCEF 向 PCRF 上 ^艮所述用户 IP-CAN会话级别的用量 4艮告 ( Monitoring Keyl对应的用量报告） ， PCRF收到后， 向 PCEF请求用户通 过 IP-CAN会话访问的不需累计入 IP-CAN会话级别用量的业务对应的用量报 告（ Monitoring Key2对应的用量报告 ) ； 在收到所述 PCEF回复的不需累计 入 IP-CAN会话级别用量的业务对应的用量报告后， PCRF将 IP-CAN会话级 别的用量报告的值与不需累计入 IP-CAN会话级别用量的业务对应的用量报 告的值的差值作为 IP-CAN会话级别的累计用量值。
对于 PCC架构引入 TDF功能后， UE通过 IP-CAN会话访问被赞助数据 连接， 或是一种根据用户的签约或网络策略不需累计入 TDF会话级别用量的 应用， PCRF和 TDF的执行和交互流程是类似的。 当满足用户的 TDF会话级 别用量上报条件时， TDF向 PCRF上报所述用户 TDF会话级别的用量报告 ( Monitoring Key 1对应的用量报告 ) , PCRF收到后， 向 TDF请求用户通过 IP-CAN会话访问的不需累计入 TDF会话级别用量的应用对应的用量报告 ( Monitoring Key2对应的用量报告 ) ； 在收到所述 TDF回复的不需累计入 TDF会话级别用量的应用对应的用量报告后， PCRF将 TDF会话级别的用量 报告的值与不需累计入 TDF会话级别用量的业务对应的用量 告的值的差值 作为 TDF会话级别的累计用量值。
如图 4所示， 业务数据流级别的用量报告上报过程， 包括以下步骤：
5401 , 当满足业务数据级别的用量上报条件时， PCEF执行下一步骤； 其 中，业务数据级别的用量上报条件包括但不限于包括： 当前业务数据级别（用 Monitoring Key2来标识）的用量已达到相应阔值（即 UT2 )、或包含 Monitoring Key2的所有 PCC规则被删除 /去激活、或 PCRF显式请求 PCEF上报 Monitoring Key2的用量；
5402, PCEF 向 PCRF上报策略和计费规则请求， 其中携带 Monitoring 6 2对应的业务数据级别的当前用量报告1^ 86 ^^0112 ( 1；1 2 ) , 其中， 在 当前用量已达到相应阔值的情况下， UR2的值和 UT2的值相等；
5403 , PCRF根据 PCRF上报的用量报告进行决策。 PCRF判断出该用户 访问被赞助数据连接业务所通过的 IP-CAN会话还执行了 IP-CAN会话级别用 量监测。 由于 Monitoring Key2对应的业务数据是被赞助数据连接， 不应该累 计在 IP-CAN会话级别的用量（即 Monitoring Keyl对应的用量） 消耗中。 因 此， 将该用户的 IP-CAN会话级别的总允许用量 TAU1更新为 TAU1+UR2, 将被赞助数据连接的允许用量阔值 AUT更新为 AUT-UR2;
5404, 在更新后的 AUT值大于 0 的前提下， 若 PCRF 决定继续监测 Monitoring Key2对应的用量， 则 PCRF向 PCEF返回的策略和计费规则请求 确认中携带 Monitoring Key2以及对应的用量阔值 UT2，。 其中， UT2 '的值 d、 于等于更新后的 AUT的值；
5405, PCEF安装策略后， 继续进行用量监测。
类似地，若 UE通过 IP-CAN会话访问的不是被赞助数据连接， 而是一种 根据用户的签约或网络策略不需累计入 IP-CAN会话级别用量的业务， PCRF 和 PCEF的执行和交互流程是类似的。当满足用户的不需累计入 IP-CAN会话 级别用量的业务的用量上报条件时， PCEF向 PCRF上报不需累计入 IP-CAN 会话级别用量的业务对应的用量报告（Monitoring Key2对应的用量报告） ； PCRF收到后，将本地保存的该用户访问不需累计入 IP-CAN会话级别用量的 业务所使用的 IP-CAN会话级别的总允许用量值更新为原总允许用量值与不 需累计入 IP-CAN会话级别用量的业务对应的用量报告的值的和， 将本地保 存的该用户的不需累计入 IP-CAN会话级别用量的业务对应的允许用量阔值 更新为原允许用量阔值与不需累计入 IP-CAN会话级别用量的业务对应的用 量报告的值的差值。
对于 PCC架构引入 TDF功能后， UE通过 IP-CAN会话访问被赞助数据 连接， 或是一种根据用户的签约或网络策略不需累计入 TDF会话级别用量的 应用， PCRF和 TDF的执行和交互流程是类似的。 当满足用户的不需累计入 TDF会话级别用量的应用的用量上报条件时， TDF向 PCRF上报不需累计入 TDF会话级别用量的应用对应的用量报告 ( Monitoring Key2对应的用量报 告） ； PCRF收到后， 将本地保存的该用户访问不需累计入 TDF会话级别用 量的应用所使用的 TDF会话级别的总允许用量值更新为原总允许用量值与不 需累计入 TDF会话级别用量的应用对应的用量 告的值的和， 将本地保存的 该用户的不需累计入 TDF会话级别用量的应用对应的允许用量阔值更新为原 允许用量阔值与不需累计入 TDF会话级别用量的应用对应的用量 ^艮告的值的 差值。 本发明实施例所述 PCRF,应用于策略和计费控制架构中， 包括： 用量报 告接收装置、 第二用量报告请求装置及累计用量计算装置， 其中：
所述用量报告接收装置设置成：接收 PCEF上报的用户 IP-CAN会话级别 的第一用量报告；还接收 PCEF上报的该用户通过上述 IP-CAN会话访问的被 赞助数据连接对应的第二用量报告；
所述第二用量报告请求装置设置成： 在所述用量报告接收装置收到所述 第一用量报告后， 向 PCEF请求所述第二用量报告；
所述累计用量值计算装置设置成： 在所述用量报告接收装置收到所述第 二用量报告后， 将所述第一用量报告的值与所述第二用量报告的值的差值作 为 IP-CAN会话级别的累计用量值。
此外， 上述 PCRF还可包括总允许用量值更新装置， 所述总允许用量值 更新装置设置成： 在所述累计用量值计算装置计算出所述累计用量值后， 将 本地保存的该用户的 IP-CAN会话级别总允许用量值更新为原总允许用量值 与所述述累计用量值的差值。
上述 PCRF还可包括第一阔值下发装置，所述第一阔值下发装置设置成： 在 PCRF决定继续对上述 IP-CAN会话级别的用量进行监测时， 根据更新后 的 IP-CAN会话级别总允许用量值重新设置的该 IP-CAN会话对应的第一阔值 下发给 PCEF。
上述 PCRF还可包括允许用量阈值更新装置， 所述允许用量阈值更新装 置设置成： 在所述用量报告接收装置接收到上述第二用量报告后， 将本地保 存的该用户的该被赞助数据连接对应的允许用量阔值更新为原允许用量阔值 与所述第二用量 ^艮告的值的差值。
上述 PCRF还可包括第二阔值下发装置，所述第二阔值下发装置设置成： 在 PCRF决定继续对上述被赞助数据连接级别的用量进行监测时， 将根据更 新后的允许用量阔值重新设置的该被赞助数据连接对应的第二阔值下发给 PCEF。
优选地， 所述用量报告接收装置还设置成： 接收在满足上述用户的被赞 助数据连接的用量上报条件时， PCEF上报的被赞助数据连接对应的第三用量 报告；
相应地， 所述总允许用量值更新装置还设置成： 在所述用量报告接收装 置接收到所述第三用量报告后， 将本地保存的该用户访问所述被赞助数据连 接所使用的 IP-CAN会话级别总允许用量值更新为原总允许用量值与该第三 用量报告的值的和；
所述允许用量阔值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量报告后， 将本地保存的该用户的被赞助数据连接对应的允许用 量阔值更新为原允许用量阔值与上述第三用量 ^艮告的值的差值。
本发明实施例的用量监测系统， 应用于策略和计费控制架构中， 包括： 用量报告接收装置、 第二用量报告请求装置及累计用量计算装置；
所述用量报告接收装置设置成： 接收策略执行功能实体上报的用户会话 级别的第一用量报告； 还接收所述策略执行功能实体上报的所述用户通过
IP-CAN会话访问的不需累计入会话级别用量的业务或应用对应的第二用量 报告；
所述第二用量报告请求装置设置成： 在所述用量报告接收装置收到所述 第一用量报告后， 向所述策略执行功能实体请求所述第二用量报告；
所述累计用量值计算装置设置成： 在所述用量报告接收装置收到所述第 二用量报告后 , 将所述第一用量报告的值与所述第二用量报告的值的差值作 为会话级别的累计用量值。
该用量监测系统还包括总允许用量值更新装置；
所述总允许用量值更新装置设置成： 在所述累计用量值计算装置计算出 所述累计用量值后， 将本地保存的所述用户的会话级别总允许用量值更新为 原总允许用量值与所述累计用量值的差值。
该用量监测系统还包括第一阔值下发装置；
所述第一阔值下发装置设置成： 在所述 PCRF决定继续对所述会话级别 的用量进行监测时， 将根据更新后的会话级别总允许用量值重新设置的所述 会话对应的第一阔值下发给所述策略执行功能实体。 该用量监测系统还包括允许用量阈值更新装置；
所述允许用量阔值更新装置设置成： 在所述用量报告接收装置接收到所 述第二用量"¾告后， 将本地保存的该用户的不需累计入会话级别用量的业务 或应用对应的允许用量阔值更新为原允许用量阔值与所述第二用量 ^艮告的值 的差值。
该用量监测系统还包括第二阔值下发装置；
所述第二阔值下发装置设置成： 在所述用量监测系统决定继续对所述不 需累计入会话级别用量的业务或应用级别的用量进行监测时， 将根据更新后 的允许用量阔值重新设置的不需累计入会话级别用量的业务或应用对应的第 二阔值下发给所述策略执行功能实体。
其中： 所述用量报告接收装置还设置成： 接收在满足所述用户的不需累 计入会话级别用量的业务或应用的用量上报条件时， 所述策略执行功能实体 上报的所述不需累计入会话级别用量的业务或应用对应的第三用量报告； 所述总允许用量值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量报告后， 将本地保存的该用户访问所述不需累计入会话级别用 量的业务或应用所使用的会话级别总允许用量值更新为原总允许用量值与所 述第三用量 告的值的和；
所述允许用量阔值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量>¾告后， 将本地保存的该用户的不需累计入会话级别用量的业 务或应用对应的允许用量阔值更新为原允许用量阔值与所述第三用量 ^艮告的 值的差值。
其中： 当所述策略执行功能实体为策略和计费执行功能（PCEF )时， 所 述会话级别用量为 IP-CAN会话级别用量；
当所述策略执行功能实体为业务检测功能 （TDF ) 时， 所述会话级别用 量为 TDF会话级别用量。
所述用量监测系统包含于策略控制与计费规则功能实体（PCRF ) 中。 其中： 所述不需累计入会话级别用量的业务或应用为：
被赞助数据连接或者根据用户签约或网络策略不需累计入会话级别用量 的业务或应用。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
工业实用性
本发明的技术方案使得 PCRF基于用量监测的策略控制决策更加精确， 因此具有很强的工业实用性。

Claims

权 利 要 求 书
1、 一种用量监测方法， 应用于策略和计费控制架构中， 包括： 当满足用户的会话级别用量上报条件时， 策略执行功能实体向策略与计 费规则功能实体（PCRF )上报所述会话级别的第一用量报告；
所述 PCRF收到后，向所述策略执行功能实体请求所述用户通过 IP-CAN 会话访问的不需累计入会话级别用量的业务或应用对应的第二用量报告； 在收到所述策略执行功能实体回复的所述第二用量报告后， 所述 PCRF 将所述第一用量报告的值与所述第二用量报告的值的差值作为所述会话级别 的累计用量值。
2、 如权利要求 1所述的用量监测方法， 其中， 所述会话级别用量上报条 件包括： 所述会话级别的第一用量 ^艮告的值已达到第一阔值。
3、 如权利要求 1所述的用量监测方法， 该用量监测方法还包括： 在得到所述累计用量值后， 所述 PCRF将本地保存的所述会话级别的总 允许用量值更新为原总允许用量值与所述累计用量值的差值。
4、 如权利要求 3所述的用量监测方法， 该用量监测方法还包括： 在所述会话级别的总允许用量值完成更新后， 若所述 PCRF决定继续对 所述会话级别的用量进行监测， 则所述 PCRF将根据更新后的总允许用量值 重新设置的所述会话对应的第一阔值下发给所述策略执行功能实体， 由所述 策略执行功能实体对本地保存的第一阔值的值进行相应更新。
5、 如权利要求 1所述的用量监测方法， 该用量监测方法还包括： 所述 PCRF在收到所述策略执行功能实体回复的所述第二用量报告后， 将本地保存的所述用户的不需累计入会话级别用量的业务或应用对应的允许 用量阔值更新为原允许用量阔值与所述第二用量 ^艮告的值的差值。
6、 如权利要求 5所述的用量监测方法， 该用量监测方法还包括： 在所述用户的不需累计入会话级别用量的业务或应用对应的允许用量阔 值完成更新后， 若所述 PCRF决定继续对所述不需累计入会话级别用量的业 务或应用的用量进行监测， 所述 PCRF将根据更新后的允许用量阔值重新设 置的所述不需累计入会话级别用量的业务或应用对应的第二阔值下发给所述 策略执行功能实体， 由所述策略执行功能实体对本地保存的第二阈值的值进 行相应更新。
7、 如权利要求 1所述的用量监测方法， 该用量监测方法还包括： 当满足所述用户的不需累计入会话级别用量的业务或应用的用量上报条 件时， 所述策略执行功能实体向所述 PCRF上报所述用户的不需累计入会话 级别用量的业务或应用对应的第三用量 ^艮告；
所述 PCRF收到后， 将本地保存的所述用户访问不需累计入会话级别用 量的业务或应用所使用的所述会话级别的总允许用量值更新为原总允许用量 值与所述第三用量报告的值的和， 将本地保存的所述用户的不需累计入会话 级别用量的业务或应用对应的允许用量阔值更新为原允许用量阔值与所述第 三用量报告的值的差值。
8、 如权利要求 7所述的用量监测方法， 其中， 所述用户的不需累计入会 话级别用量的业务或应用的用量上才艮条件包括： 所述用户的当前不需累计入 会话级别用量的业务或应用对应的第三用量的值已达到所述不需累计入会话 级别用量的业务或应用对应的第二阔值、 或包含所述不需累计入会话级别用 量的业务或应用的监测键的所有策略规则被删除或被去激活、 或所述 PCRF 显式请求所述策略执行功能实体上报所述用户的不需累计入会话级别用量的 业务或应用对应的用量。
9、 如权利要求 1-7中任意一项所述的用量监测方法， 其中：
当所述策略执行功能实体为策略和计费执行功能（PCEF )时， 所述会话 级别用量为 IP连接接入网 （IP-CAN )会话级别用量；
当所述策略执行功能实体为业务检测功能 （TDF ) 时， 所述会话级别用 量为 TDF会话级别用量。
10、 如权利要求 8所述的用量监测方法， 其中：
当所述策略执行功能实体为策略和计费执行功能 PCEF时， 所述会话级 别用量为 IP-CAN会话级别用量， 所述策略规则为策略和计费控制规则； 当所述策略执行功能实体为业务检测功能 TDF时， 所述会话级别用量为 TDF会话级别用量， 所述策略规则为应用检测和控制。
11、 如权利要求 1-8 中任一项所述的用量监测方法， 其中： 所述不需累 计入会话级别用量的业务或应用为：
被赞助数据连接或者根据用户签约或网络策略不需累计入会话级别用量 的业务或应用。
12、 一种用量监测系统， 应用于策略和计费控制架构中， 包括： 用量报 告接收装置、 第二用量报告请求装置及累计用量计算装置；
所述用量报告接收装置设置成： 接收策略执行功能实体上报的用户会话 级别的第一用量报告； 还接收所述策略执行功能实体上报的所述用户通过 IP-CAN会话访问的不需累计入会话级别用量的业务或应用对应的第二用量 报告；
所述第二用量报告请求装置设置成： 在所述用量报告接收装置收到所述 第一用量报告后， 向所述策略执行功能实体请求所述第二用量报告；
所述累计用量值计算装置设置成： 在所述用量报告接收装置收到所述第 二用量报告后， 将所述第一用量报告的值与所述第二用量报告的值的差值作 为会话级别的累计用量值。
13、如权利要求 12所述的用量监测系统， 该用量监测系统还包括总允许 用量值更新装置；
所述总允许用量值更新装置设置成： 在所述累计用量值计算装置计算出 所述累计用量值后， 将本地保存的所述用户的会话级别总允许用量值更新为 原总允许用量值与所述累计用量值的差值。
14、如权利要求 13所述的用量监测系统， 该用量监测系统还包括第一阔 值下发装置；
所述第一阔值下发装置设置成： 在所述 PCRF决定继续对所述会话级别 的用量进行监测时， 将根据更新后的会话级别总允许用量值重新设置的所述 会话对应的第一阔值下发给所述策略执行功能实体。
15、如权利要求 12所述的用量监测系统， 该用量监测系统还包括允许用 量阔值更新装置； 所述允许用量阔值更新装置设置成： 在所述用量报告接收装置接收到所 述第二用量"¾告后， 将本地保存的该用户的不需累计入会话级别用量的业务 或应用对应的允许用量阔值更新为原允许用量阔值与所述第二用量 ^艮告的值 的差值。
16、如权利要求 15所述的用量监测系统， 该用量监测系统还包括第二阔 值下发装置；
所述第二阔值下发装置设置成： 在所述用量监测系统决定继续对所述不 需累计入会话级别用量的业务或应用级别的用量进行监测时， 将根据更新后 的允许用量阔值重新设置的不需累计入会话级别用量的业务或应用对应的第 二阔值下发给所述策略执行功能实体。
17、 如权利要求 12所述的用量监测系统， 其中：
所述用量报告接收装置还设置成： 接收在满足所述用户的不需累计入会 话级别用量的业务或应用的用量上报条件时， 所述策略执行功能实体上报的 所述不需累计入会话级别用量的业务或应用对应的第三用量 ^艮告；
所述总允许用量值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量>¾告后， 将本地保存的该用户访问所述不需累计入会话级别用 量的业务或应用所使用的会话级别总允许用量值更新为原总允许用量值与所 述第三用量 告的值的和；
所述允许用量阔值更新装置还设置成： 在所述用量报告接收装置接收到 所述第三用量 告后， 将本地保存的该用户的不需累计入会话级别用量的业 务或应用对应的允许用量阔值更新为原允许用量阔值与所述第三用量 ^艮告的 值的差值。
18、 如权利要求 12-17中任意一项所述的用量监测系统， 其中： 当所述策略执行功能实体为策略和计费执行功能（PCEF )时， 所述会话 级别用量为 IP-CAN会话级别用量；
当所述策略执行功能实体为业务检测功能 （TDF ) 时， 所述会话级别用 量为 TDF会话级别用量。
19、 如权利要求 12-17 中任意一项所述的用量监测系统， 所述用量监测 系统包含于策略控制与计费规则功能实体（PCRF ) 中。
20、 如权利要求 12-17 中任一项所述的用量监测系统， 其中： 所述不需 累计入会话级别用量的业务或应用为：
被赞助数据连接或者根据用户签约或网络策略不需累计入会话级别用量 的业务或应用。
PCT/CN2011/079294 2010-09-27 2011-09-02 用量监测方法及策略控制与计费规则功能实体 WO2012041150A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010102959594A CN102421080A (zh) 2010-09-27 2010-09-27 用量监测方法及策略控制与计费规则功能实体
CN201010295959.4 2010-09-27

Publications (1)

Publication Number Publication Date
WO2012041150A1 true WO2012041150A1 (zh) 2012-04-05

Family

ID=45891913

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079294 WO2012041150A1 (zh) 2010-09-27 2011-09-02 用量监测方法及策略控制与计费规则功能实体

Country Status (2)

Country Link
CN (1) CN102421080A (zh)
WO (1) WO2012041150A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107396333A (zh) * 2016-05-17 2017-11-24 中兴通讯股份有限公司 策略和计费控制方法、系统及用量监测装置
US20230048559A1 (en) * 2013-01-11 2023-02-16 Interdigital Patent Holdings, Inc. User-plane congestion management

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786315B (zh) * 2016-08-29 2021-11-12 中兴通讯股份有限公司 一种用量配额的授权方法及装置
JP7367058B2 (ja) * 2019-04-30 2023-10-23 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 端末デバイスに対する監視を設定するための方法および装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101345632A (zh) * 2007-07-14 2009-01-14 华为技术有限公司 对数据赠送业务计费的方法及系统、及数据业务管理设备
CN101754161A (zh) * 2008-12-18 2010-06-23 中兴通讯股份有限公司 一种实现策略和计费控制的方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101583115A (zh) * 2008-12-24 2009-11-18 中兴通讯股份有限公司 计费费率处理方法及装置、pcrf、pcef

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101345632A (zh) * 2007-07-14 2009-01-14 华为技术有限公司 对数据赠送业务计费的方法及系统、及数据业务管理设备
CN101754161A (zh) * 2008-12-18 2010-06-23 中兴通讯股份有限公司 一种实现策略和计费控制的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED ET AL.: "Support for sponsored data connectivity: Impacts to current stage 2.", 3GPP TSG SAWG2 MEETING #79 TD S2-102096., 14 May 2010 (2010-05-14) *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230048559A1 (en) * 2013-01-11 2023-02-16 Interdigital Patent Holdings, Inc. User-plane congestion management
US11924680B2 (en) * 2013-01-11 2024-03-05 Interdigital Patent Holdings, Inc. User-plane congestion management
CN107396333A (zh) * 2016-05-17 2017-11-24 中兴通讯股份有限公司 策略和计费控制方法、系统及用量监测装置

Also Published As

Publication number Publication date
CN102421080A (zh) 2012-04-18

Similar Documents

Publication Publication Date Title
US11647085B2 (en) Service redirection from a policy and charging control architecture
JP5606617B2 (ja) Ｌｔｅ／ｅｐｃネットワークにおけるローカル・ローミング課金
US9154314B2 (en) Method and system for implementing usage monitoring control
EP2493222B1 (en) Method and system for implementing usage monitoring control
CN102625272B (zh) 一种支持流检测功能的用量监控方法及系统
US9647848B2 (en) Application charging method, device, and system
CN105900524B (zh) 一种计费会话管理方法、装置
KR20120087728A (ko) 무선통신 시스템에서 서비스품질에 따른 서비스 제공 방법 및 장치
WO2006047965A1 (fr) Procede de traitement de facturation en ligne
KR101884048B1 (ko) 네트워크 자원들을 관리하기 위한 방법들과 노드들, 및 상응하는 시스템과 컴퓨터 프로그램
US20120158977A1 (en) Method and System for Transmitting a Bearer Control Mode in Roaming Scenarios
WO2010091635A1 (zh) 一种策略的控制方法、装置
WO2015143851A1 (zh) 用量监控方法、装置和系统
WO2008022602A1 (fr) Procédé, dispositif et système de commande de conditions d&#39;utilisation et de facturation
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2018076974A1 (zh) 一种策略控制方法、装置及系统
WO2012083779A1 (zh) 策略控制方法及装置
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
EP3389218B1 (en) Data service charging method, device and system
WO2012071956A1 (zh) 漫游场景支持被赞助数据连接的方法、系统和装置
WO2012041150A1 (zh) 用量监测方法及策略控制与计费规则功能实体
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
US11223492B2 (en) Wireless communication method and device
WO2012041149A1 (zh) 一种用量监测方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11828046

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11828046

Country of ref document: EP

Kind code of ref document: A1