WO2012041149A1 - 一种用量监测方法及系统 - Google Patents

一种用量监测方法及系统 Download PDF

Info

Publication number
WO2012041149A1
WO2012041149A1 PCT/CN2011/079275 CN2011079275W WO2012041149A1 WO 2012041149 A1 WO2012041149 A1 WO 2012041149A1 CN 2011079275 W CN2011079275 W CN 2011079275W WO 2012041149 A1 WO2012041149 A1 WO 2012041149A1
Authority
WO
WIPO (PCT)
Prior art keywords
usage
monitoring
pcrf
report
session
Prior art date
Application number
PCT/CN2011/079275
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 WO2012041149A1 publication Critical patent/WO2012041149A1/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/1432—Metric aspects
    • H04L12/1435—Metric aspects volume-based
    • 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
    • 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

Definitions

  • the invention relates to a dosage monitoring technology, in particular to a dosage monitoring method and system. Background technique
  • 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.
  • UMRAN Universal Mobile Telecommunications System
  • EDGE Enhanced Data Rates for Global Evolution
  • I-WLAN interworking wireless local area network
  • EPS evolved packet system
  • FIG. 1 is a schematic diagram of a related art Rel-8 PCC non-roaming architecture. The following describes various logical functional entities and their interface functions in the PCC architecture with reference to FIG. 1 :
  • the application function entity provides access points for service applications.
  • the network resources used by these service applications need dynamic policy control.
  • the AF passes the related service information to the Policy and Charging Rules Function (PCRF). If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment).
  • PCRF Policy and Charging Rules Function
  • the interface between AF and PCRF is the Rx interface.
  • 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 also needs to ensure that these rules are consistent with the user's subscription information.
  • the basis for formulating policies and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information with the user policy charging control from the SPR (Spent Profile Repository); and obtaining the information related to the bearer related network from the PCEF .
  • the PCEF is usually located in the gateway (GW, Gate-Way) and performs the policy and charging rules established by the PCRF on the bearer plane.
  • 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 the charging rule established 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 a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS).
  • OCS Online Charging System
  • the interface between PCEF and PCRF is Gx interface
  • the interface between OCE and OCS is Gy interface
  • the interface between OFCS and OFCS is Gz interface.
  • the PCEF can also have application detection and control functions (ADC, Application Detection and Control).
  • ADC Application Detection and Control
  • the PCEF can perform application detection and policy execution according to the local configuration or application detection control rules that are sent by the PCRF and include application detection control policies (such as gating, Redirection, bandwidth throttling, and usage monitoring).
  • PCEFs are generally located on the gateway of the network, such as the GPRS Gateway Support Node (GGSN) in GPRS and the Packet Data Gateway (PDG) in I-WLAN.
  • GGSN GPRS Gateway Support Node
  • PGW Packet Data Gateway
  • TDF traffic detection function
  • the TDF and the PCRF are connected to each other through the Sd interface.
  • the TDF can perform application detection and policy execution according to the ADC rules delivered by the pre-configuration or PCRF.
  • Bearer Binding and Event Reporting Function (BBERF, Bearer Binding and Event Reporting Function). Its features include load binding, verification of uplink bindings, and event reporting.
  • BBERF Bearer Binding and Event Reporting Function
  • Its features include load binding, verification of uplink bindings, and event reporting.
  • the non-3GPP access gateway when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the Evolved Packet Data Gateway (ePDG). At this time, the PCEF no longer performs the bearer binding function.
  • ePDG Evolved Packet Data Gateway
  • the SPR stores user policy charging control subscription information related to policy control and charging.
  • SPR The interface between the PCRF and the PCRF is the Sp interface.
  • OCS and PCEF are used to control and manage user credit under online charging mode.
  • 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-Accessed Network) session established by the UE to access a Packet Data Network (PDN).
  • IP-Accessed Network IP-Accessed Network
  • PDN Packet Data Network
  • the PCC supports dynamic usage monitoring control to implement real-time network resource usage totals and perform dynamic policy decisions.
  • Usage monitoring can be applied to a single service data stream, a group of service data streams, or all traffic data streams (IP-CAN session levels) for an IP-CAN session. If the UE establishes multiple IP-CAN sessions to a 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.
  • usage refers to user plane data traffic.
  • a monitoring key is used to identify an instance that requires usage monitoring.
  • the PCRF assigns a Monitoring Key and a corresponding threshold to all traffic flows of an IP-CAN session
  • the PCEF will According to the threshold, all traffic flows of the IP-CAN are monitored, and the Monitoring Key is used to identify the reported usage.
  • the PCRF assigns a monitoring key and a corresponding threshold to a service flow or a group of service data flows
  • the PCRF carries the Monitoring Key in the PCC rule corresponding to the service data flow or a set of service data flows
  • the PCEF will be based on The threshold monitors the traffic of the service data flow corresponding to the PCC rule of the same Monitoring Key, and uses 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.
  • PCEF can also perform usage monitoring control for 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).
  • TDF session level applications of a TDF session
  • 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 Value monitoring has the same Monitoring Key The traffic of the application corresponding to the ADC rule, and the usage amount reported by the Monitoring Key.
  • 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 services of a certain PDN of a user, that is, the total allowed usage for a service data flow/application or a group of service data flows/applications, and can also be identified by a Monitoring Key.
  • the PCRF will deduct the reported usage value from the total allowable amount. If the PCEF reports the usage of a Monitoring Key and needs to continue monitoring, the PCRF will provide a new threshold to the PCEF; if no further monitoring is required, the PCRF will not provide a new threshold to the PCEF.
  • APN Access Point Name
  • 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.
  • 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 TDF subscription usage report ( Usage_Report) event trigger.
  • Usage_Report TDF subscription usage report
  • TDF monitors 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 explicitly requests usage " ⁇ , TDF will report to PCRF ⁇ since the last time Related since The consumption of the Monitoring Key.
  • the PCRF receives the dose from the TDF, the PCRF will deduct the reported usage value from the total allowable amount. If the TDF reports a usage of a Monitoring Key and needs to continue monitoring, the PCRF will provide a new threshold to the TDF; if it is not necessary to continue monitoring, 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 refers to the consumption consumption generated by the user's accessed business, 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 issued by the AF.
  • the PCEF notifies the PCRF 0.
  • the prior art has the following problems: If the user has the IP-CAN session-level usage subscription data in the SPR, that is, the PCRF needs to sign the SPR, and instruct the PCEF to monitor the cumulative usage of all the service data flows of the entire IP-CAN session. . At this time, the user accesses a certain sponsored data connection service, and the AF will provide the sponsored usage amount to the PCRF. The PCRF instructs the PCEF to monitor the amount of the sponsored data connection service, and consumes the consumption due to the service of the sponsored data connection. It is borne by the service provider, resulting in errors in usage monitoring.
  • the technical problem to be solved by the present invention is to provide a usage monitoring method and system, which solves the problem that the PCEF monitoring fails to reflect the user's own consumption amount consumed by the user's IP-CAN session.
  • a method for monitoring usage includes:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCRF IP connection access network
  • the PCRF updates the total allowable usage of the IP-CAN session level
  • the total allowable amount after the update is equal to the original total allowable amount plus the usage report value of the monitoring key corresponding to the sponsored data connection minus the monitoring key of the IP-CAN session level. The usage report value.
  • the usage of all monitoring keys is reported as the usage index of the monitoring key of all IP-CAN sessions of the user to the same packet data network (PDN).
  • PDN packet data network
  • the PCEF needs to report the IP address of the user to the PCRF when the usage of the IP-CAN session level reaches the usage threshold, the PCRF explicitly requests the IP-CAN session level, or the user ends the last IP-CAN session of the PDN. Usage report for CAN session level.
  • the method further includes: when the last IP-CAN session of the user to the PDN is terminated, the PCRF reports the updated total allowed usage to the user subscription database.
  • a method for monitoring usage includes:
  • PCEF Policy and Charging Enforcement Function Entity
  • the PCRF updates the total allowable usage of the user's IP connection access network (IP-CAN) session level, and the updated total allowable usage is equal to the original total allowable amount plus The usage report value of the monitoring key corresponding to the sponsored data connection.
  • IP-CAN IP connection access network
  • the PCEF reports the usage of the monitoring key to the PCRF when the usage of the monitoring key reaches the usage threshold, all the PCC rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the PCEF to report the usage of the monitoring key.
  • a usage monitoring system includes: a Policy and Charging Enforcement Function Entity (PCEF) and a Policy and Charging Rules Function Entity (PCRF), where:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCF Policy and Charging Rules Function Entity
  • the PCEF is used to report the usage report of all the monitoring keys of the user when the usage report of the IP connection access network (IP-CAN) session level of the user needs to be reported to the PCRF;
  • the PCRF is used to update the total allowable usage of the IP-CAN session level. If the monitoring key contains the monitoring key corresponding to the sponsored data connection, the total allowed usage amount after the update is equal to the original total allowable amount plus the sponsored data connection.
  • the usage report value of the monitoring key minus the usage report value of the monitoring key of the IP-CAN session level.
  • the PCRF when the PCEF reaches the usage threshold at the IP-CAN session level, the PCRF explicitly requests the IP-CAN session level, or the user ends the last IP-CAN session of the packet data network (PDN), the PCRF needs to be sent to the PCRF. Report the usage report of the user's IP-CAN session level.
  • PDN packet data network
  • a usage monitoring system includes: a Policy and Charging Enforcement Function Entity (PCEF) and a Policy and Charging Rules Function Entity (PCRF), where:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCF Policy and Charging Rules Function Entity
  • PCEF used to report the usage index of the user's monitoring key to the PCRF
  • the PCRF is used to update the total allowable usage of the IP-CAN session level of the user when the monitoring key is the monitoring key corresponding to the sponsored data connection, and the updated total allowed usage is equal to the original total allowed amount.
  • the PCEF reports the usage of the monitoring key to the PCRF when the usage of the monitoring key reaches the usage threshold, all the PCC rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the PCEF to report the usage of the monitoring key.
  • a method for monitoring usage includes:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCRF Policy and Charging Rules Function Entity
  • the PCRF updates the total allowed usage of the IP-CAN session level
  • the updated total allowed usage amount is equal to the original total allowed usage minus the monitoring key of the IP-CAN session level.
  • the service that does not need to be accumulated into the IP-CAN session level is:
  • the sponsored data connection or the business of the IP-CAN session level usage does not need to be accumulated according to the user's subscription or network policy.
  • the usage of all the monitoring keys is reported as:
  • PDN packet data network
  • the step of reporting the usage report of the IP-CAN session level of the user to the PCRF includes:
  • the usage of the PCEF at the IP-CAN session level reaches a usage threshold, the PCRF explicitly requests the usage of the IP-CAN session level, or the last usage report of the user to the PDN.
  • the usage monitoring method further includes:
  • the PCRF uploads the updated total allowed amount to the user subscription database.
  • a method for monitoring usage includes:
  • TDF service detection function
  • PCF policy and charging rule function entity
  • the PCRF updates the total allowed usage of the TDF session level
  • the total allowed usage amount after the update is equal to the original total allowable amount minus the usage report value of the monitoring key of the TDF session level.
  • the usage report value of the monitoring key corresponding to the application that does not need to be accumulated into the TDF session level is added.
  • the service that does not need to be accumulated into the TDF session level is:
  • the step of reporting the usage report of the TDF session level of the user to the PCRF includes:
  • the usage of the TDF at the TDF session level reaches a usage threshold, and the PCRF is explicitly requested.
  • the usage report of the TDF session level of the user needs to be reported to the PCRF.
  • a method for monitoring usage includes:
  • the PCRF updates the total allowed usage of the session level
  • the total allowed usage amount after the update is equal to the original total allowable amount minus the usage report value of the monitoring key of the session level.
  • the usage report value of the monitoring key corresponding to the service of the session level usage is not required to be accumulated.
  • the service that does not need to be accumulated into the session level usage is:
  • the sponsored data connection or the business of the session level usage is not required to be accumulated according to the user's subscription or network policy.
  • the step of reporting the usage level report of the user to the PCRF includes: the usage of the policy execution function entity reaches the usage threshold at the session level, and the PCRF explicitly requests the usage of the session level.
  • the usage report of the session level of the user needs to be reported to the PCRF.
  • the policy execution function entity is a policy and charging execution function entity (PCEF), and the session is an IP connection access network (IP-CAN) session.
  • PCEF policy and charging execution function entity
  • IP-CAN IP connection access network
  • the policy execution function entity is a service detection function (TDF), and the session is a TDF session.
  • TDF service detection function
  • a method for monitoring usage includes:
  • PCEF Policy and Charging Enforcement Function Entity
  • the PCRF updates and updates the total allowed usage of the IP-CAN session level.
  • the total allowable amount afterwards is equal to the original total allowable amount plus the said The usage report value of the monitoring key of the service of the IP-CAN session level usage.
  • the step of reporting, by the PCEF, the usage of the monitoring key of the user to the PCRF includes: the usage of the monitoring key by the PCEF reaches the usage threshold, and all the policies and charging control (PCC) rules including the monitoring key are deleted.
  • PCC policies and charging control
  • a method for monitoring usage includes:
  • the service detection function reports the usage report of the user's monitoring key to the policy and charging rule function entity (PCRF);
  • the PCRF updates the total allowed usage of the TDF session level, and the updated total allowed usage is equal to the original total allowed amount.
  • the usage report value of the monitoring key of the application that does not need to be accumulated into the TDF session level usage is described above.
  • the step of reporting the usage of the monitoring key of the user by the TDF to the PCRF includes: the usage of the TDF in the usage of the monitoring key reaches a usage threshold, and all application detection and control (ADC) rules including the monitoring key are deleted or When the activation or the PCRF explicitly requests the TDF to report the usage of the monitoring key, the usage report of the monitoring key is reported to the PCRF.
  • ADC application detection and control
  • a method for monitoring usage includes:
  • the policy execution function entity reports the usage report of the user's monitoring key to the policy and charging rule function entity (PCRF);
  • the monitoring key is a monitoring key corresponding to a service that does not need to be accumulated into the session level usage
  • the PCRF updates the total allowed usage of the session level, and the updated total allowed usage is equal to the original total allowable amount plus the usage report value of the monitoring key of the service that does not need to be accumulated into the session level usage.
  • the step of the policy execution function entity reporting the usage report of the user's monitoring key to the PCRF includes:
  • the policy execution function entity reports that the usage of the monitoring key reaches a usage threshold, all rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the policy execution function entity to report the monitoring key. When the dosage is used, the usage report of the monitoring key is reported to the PCRF.
  • the policy execution function entity is a policy and charging execution function entity (PCEF)
  • the session is an IP connection access network (IP-CAN) session
  • the rule is a policy and charging control (PCC) rule.
  • the policy execution function entity is a service detection function (TDF)
  • the session is a TDF session
  • the rule is an application detection and control (ADC) rule.
  • a usage monitoring system includes: a service monitoring function (TDF) and a policy and charging rule function entity (PCRF), wherein:
  • the TDF is configured to report the usage report of all the monitoring keys of the TDF session when the usage report of the user's TDF session level needs to be reported to the PCRF;
  • the PCRF is configured to: update the total allowed usage of the TDF session level, and if the monitoring key includes a monitoring key corresponding to an application that does not need to be accumulated into the TDF session level, the total allowed usage amount after the update is equal to The original total allowable amount minus the usage report value of the monitoring key of the TDF session level plus the usage report value of the monitoring key corresponding to the application that does not need to be accumulated into the TDF session level.
  • TDF is also set to:
  • the PCRF When the usage of the TDF session level reaches the usage threshold, the PCRF explicitly requests the TDF session level, or the TDF session is terminated, the TDF session level of the user needs to be reported to the PCRF. report.
  • a usage monitoring system includes: a Policy and Charging Enforcement Function Entity (PCEF) and a Policy and Charging Rules Function Entity (PCRF), where:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCF Policy and Charging Rules Function Entity
  • the PCEF is configured to report the usage report of all the monitoring keys of the user when the usage report of the user's IP connection access network (IP-CAN) session level needs to be reported to the PCRF; the PCRF is set to: Update the total allowable usage of the IP-CAN session level. If the monitoring key includes a monitoring key corresponding to the service that does not need to be accumulated into the IP-CAN session level, the total allowed usage amount after the update is equal to the original total amount. The usage amount minus the usage report value of the monitoring key of the IP-CAN session level plus the usage report value of the monitoring key corresponding to the service that does not need to be accumulated into the IP-CAN session level.
  • IP-CAN IP connection access network
  • the PCEF is further configured to: The usage of the IP-CAN session level reaches the usage threshold, the PCRF explicitly requests the usage of the IP-CAN session level, or the last IP-CAN session termination of the user to the packet data network (PDN) The usage report of the IP-CAN session level of the user needs to be reported to the PCRF.
  • PDN packet data network
  • a usage monitoring system includes: a policy enforcement functional entity and a policy and charging rules functional entity (PCRF), wherein:
  • the policy execution function entity is configured to report the usage report of all the monitoring keys of the user when the usage report of the session level of the user needs to be reported to the PCRF;
  • the PCRF is configured to: update the total allowed usage of the session level, and if the monitoring key includes a monitoring key corresponding to a service or application that does not need to be accumulated in the session level, the total allowed usage amount after the update is equal to The original total allowable amount minus the usage report value of the monitoring key of the session level plus the usage report value of the monitoring key corresponding to the service or application that does not need to be accumulated into the session level.
  • the policy execution function entity is further configured to:
  • the usage report of the session level of the user needs to be reported to the PCRF.
  • the policy execution function entity is a policy and charging execution function entity (PCEF), and the session is an IP connection access network (IP-CAN) session.
  • PCEF policy and charging execution function entity
  • IP-CAN IP connection access network
  • the policy execution function entity is a service detection function (TDF), and the session is a TDF session.
  • TDF service detection function
  • a usage monitoring system includes: a Policy and Charging Enforcement Function Entity (PCEF) and a Policy and Charging Rules Function Entity (PCRF), where:
  • PCEF Policy and Charging Enforcement Function Entity
  • PCF Policy and Charging Rules Function Entity
  • the PCEF is configured to report a usage report of the user's monitoring key to the PCRF; the PCRF is configured to: when the monitoring key is a service corresponding to the IP-CAN session level that does not need to be integrated into the IP connection access network (IP-CAN) When the monitoring key is used, the total allowed usage of the IP-CAN session level is updated, and the updated total allowed usage is equal to the original total allowable amount plus the corresponding service that does not need to be accumulated into the IP-CAN session level. Monitor the key usage report value.
  • the PCEF is further configured to:
  • the amount of the monitoring key reaches a usage threshold, all policy and charging control (PCC) rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the PCEF to report the usage of the monitoring key. At the time, the usage report of the monitoring key is reported to the PCRF.
  • PCC policy and charging control
  • a usage monitoring system includes: a service detection function (TDF) and a policy and charging rule function entity (PCRF), wherein:
  • the TDF is set to: report the usage report of the user's monitoring key to the PCRF; the PCRF is set to: when the monitoring key is a monitoring key corresponding to an application that does not need to be integrated into the TDF session level, to the TDF
  • the total allowable usage of the session level is updated, and the updated total allowed usage is equal to the original total allowable amount plus the usage report value of the monitoring key corresponding to the application that does not need to accumulate into the TDF session level.
  • TDF is also set to:
  • ADC application detection and control
  • a usage monitoring system includes: a policy enforcement functional entity and a policy and charging rules functional entity (PCRF), wherein:
  • the policy execution function entity is configured to: report a usage report of the user's monitoring key to the PCRF;
  • the PCRF is configured to: when the monitoring key is a monitoring key corresponding to a service or application that does not need to be accumulated into a session level, update the total allowed usage of the session level, and the updated total allowed usage is equal to the original total allowed amount. The amount is added to the usage report value of the monitoring key corresponding to the service or application that does not need to be accumulated into the session level.
  • the policy execution function entity is further configured to:
  • the policy execution function entity is a policy and charging execution function entity (PCEF)
  • PCEF policy and charging execution function entity
  • IP-CAN IP-Connected Access Network
  • PCC Policy and Charging Control
  • the policy execution function entity is a service detection function (TDF)
  • the session is a TDF session
  • the rule is an application detection and control (ADC) rule.
  • the policy execution function entity PCEF after receiving the usage report of the monitoring key of the user reported by the policy execution function entity PCEF and the TDF, if the PCRF includes the monitoring key corresponding to the sponsored data connection, the total allowable usage of the session is included.
  • the usage report value of the monitoring key corresponding to the sponsored data connection is such that the total allowable usage of the session truly reflects the total amount of usage remaining by the user.
  • FIG. 1 is a schematic diagram of a Rel-8 PCC non-roaming architecture in the prior art
  • FIG. 2 is a flowchart of an IP-CAN session-level usage monitoring strategy and a usage monitoring strategy of a sponsored data connection service in a usage monitoring method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of the usage consumption of the IP-CAN session level in the usage monitoring method according to the embodiment of the present invention when the consumption consumption reaches the usage threshold or the PCRF explicitly requests the PCEF to report the usage consumption of the IP-CAN session level;
  • FIG. 4 is a flowchart of reporting a usage report at the end of the last IP-CAN session of the UE to the PDN in the usage monitoring method according to the embodiment of the present invention
  • FIG. 5 is a report of the usage quantity when the consumption of the service data flow level reaches the usage threshold or the all the PCC rules including the Monitoring Key 2 are deleted, deactivated, or the PCRF explicitly requests the PCEF to report the usage of the Monitoring Key 2 in the usage monitoring method.
  • Flow chart of consumption Preferred embodiment of the invention
  • IP-CAN session level usage monitoring monitoring the cumulative usage of all traffic data flows of the user to one or more IP-CAN sessions of the PDN (IP-CAN session level usage monitoring), will also connect the sponsored data accessed by the user.
  • the amount of usage generated by the business is calculated in the usage of the IP-CAN session level, and the consumption consumed by the service that is sponsored by the data connection is borne by the service provider, resulting in
  • the usage monitoring reported by the PCEF to the PCRF fails to reflect the amount of user-owned consumption consumed by the user's IP-CAN session level.
  • FIG. 2 is a flowchart of a method for monitoring an IP-CAN session level usage monitoring strategy and a usage monitoring policy for a data connection service according to an embodiment of the present invention, including:
  • Step S201 In the process that the UE requests to establish an IP-CAN session to the PDN, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and requests for access. PDN identity of the PDN network;
  • Step S202 The PCEF sends an IP-CAN session establishment indication message to the PCRF, and carries the user identifier, the PDN identifier, and the IP address assigned to the UE in the IP-CAN session establishment indication message;
  • Step S203 The PCRF determines that there is no subscription information of the user according to the user identifier, and sends a subscription document request to the SPR, where the subscription document request carries the user identifier and the PDN identifier.
  • Step S204 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier, and the user subscription information includes the total allowed amount (TAU, Totally Allowed Usage) of the user (PDN) of the PDN (Per PDN and User);
  • the user subscription information includes the total allowed amount (TAU, Totally Allowed Usage) of the user (PDN) of the PDN (Per PDN and User);
  • Step S205 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE.
  • the usage monitoring strategy includes setting Monitoring Key 1 ; setting the event trigger, and the values are Usage_Report and UT, Usage Threshold 1.
  • the PCRF allocates the user's usage value UT1 and UT1 TAU1 according to the TAU1 obtained from the SPR.
  • the usage monitoring is for all traffic data flows of the IP-CAN session, and the Monitoring Key 1 is not included in any PCC rules (the PCRF indicates that the PCEF usage of the Monitoring Key 1 is monitored as the IP-CAN session level).
  • Step S206 The PCEF installation policy, including the usage monitoring policy, the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP address is carried in the IP-CAN session establishment response;
  • the UE may also establish another IP-CAN session with the PDN.
  • the Monitoring Key 1 is for all service data flows of all IP-CAN sessions established by the UE and the PDN, that is, the Monitoring Keyl is for Per PDN and UE.
  • Step S207 The PCEF performs a usage monitoring policy to perform usage monitoring on all service data flows of the user accessing the PDN (through one or more IP-CAN sessions) (ie, performing IP-CAN session level usage monitoring);
  • Step S208 The UE connects to the third-party application service provider (ASP, Application Service Provider) server through the IP-CAN session (including one or more IP-CAN sessions) established in steps S201 to S207, and requests the service, the ASP server. Deciding to provide the sponsored data connection for the user, the ASP server provides the dynamic sponsored data connection information to the AF, including the sponsor identification, the ASP identifier, the sponsored user information (such as IP Address), and the IP of the sponsored service. Flow Information and Allowed Usage Threshold ( AUT , Allowed Usage Threshold ) ;
  • the AF is located in the above PDN that establishes one or more IP-CAN sessions with the UE.
  • Step S209 The AF provides the sponsored data connection information to the PCRF, where the information includes the sponsor identifier, the ASP identifier, the sponsored user information (such as IP Address), the IP stream information of the sponsored service, and the Allowed Usage Threshold. ( AUT ) ;
  • Step S210 After the PCRF saves the information, a confirmation message is returned.
  • Step S211 The PCRF makes a policy decision based on the information obtained from the AF, the network policy, and the user signing, and formulates the PCC rule;
  • the PCRF determines the usage monitoring of the service of the sponsored data connection, and formulates the usage monitoring strategy, including setting the Monitoring Key2 and setting the usage threshold UT2, wherein UT2 ⁇ AUT, the PCRF includes the Monitoring Key 2 in the PCC rule corresponding to the service data flow;
  • Step S212 The PCRF delivers the established PCC rule to the PCEF, and the PCC rule includes
  • PCRF also provides the usage threshold UT2 corresponding to Monitoring Key2;
  • Step S213 After the PCEF installs the policy, returning an acknowledgement message to the PCRF;
  • Step S214 The PCEF simultaneously performs the usage monitoring and the number of services of the IP-CAN session level. According to the flow level usage monitoring, at this time, the IP-CAN session level will be accumulated for the usage of the Monitoring Key2.
  • FIG. 3 is a flow chart of reporting consumption consumption when the consumption consumption of the IP-CAN session level reaches the usage threshold or the PCRF explicitly requests the PCEF to report the usage of the IP-CAN session level according to an embodiment of the present invention, including:
  • Step S301 When the usage consumption of the Monitoring Keyl reaches the usage threshold (ie, UT1) or the PCRF explicitly requests the PCEF to report the consumption of the IP-CAN session level, the PCEF triggers the usage reporting process;
  • the usage threshold ie, UT1
  • the PCRF explicitly requests the PCEF to report the consumption of the IP-CAN session level
  • Step S302 The PCEF sends a policy and charging rule request to the PCRF, and reports the usage report. At this time, the PCEF reports all the IP-CAN sessions of the UE to the PDN (the UE establishes one or more IP-CAN sessions to the PDN).
  • Monitoring Key usage report, UR, Usage Reprot includes UR1 corresponding to Monitoring Keyl and UR2 corresponding to Monitoring Key2, where UR1 is used as 4 UT1 and UR2 is 4 UT2;
  • Step S303 The PCRF makes a decision according to the usage report reported by the PCEF. Since the usage corresponding to the Monitoring Key2 belongs to the sponsored data connection, it should not be accumulated in the consumption of the IP-CAN session level (the usage corresponding to the Monitoring Keyl). Therefore, the user at this time The remaining IP-CAN session level total allowable amount TAU1 is updated to the TAU1-UR1 usage report value + UR2 usage value, and the remaining sponsored data connection usage AUT is updated to the AUT-UR2 usage report value;
  • Step S304 If the PCRF decides to continue the usage of the Monitoring Key1, the Monitoring Key and the corresponding usage threshold UT ⁇ (where UT1' ⁇ updated TAU1) are carried in the returned policy and charging rule request confirmation; if the PCRF decides to continue For the usage of Monitoring Key2, the PCRF carries the Monitoring Key2 and the corresponding usage threshold UT2 in the return message, (where UT2, ⁇ updated AUT);
  • Step S305 After the PCEF installs the policy, the usage monitoring of the IP-CAN session level and the service data flow level is continued.
  • 4 is a flowchart of reporting a usage report when a UE ends a last IP-CAN session to a PDN according to an embodiment of the present invention, including:
  • Step S401 The gateway where the PCEF is located receives the trigger of the last IP-CAN session termination of the UE to the PDN;
  • Step S402 The PCEF sends an IP-CAN session termination indication to the PCRF, and the PCEF is only displayed.
  • the usage report of all Monitoring Keys of all IP-CAN sessions of the UE to the PDN includes the UR1 corresponding to the Monitoring Key 1 and the UR2 corresponding to the Monitoring Key 2.
  • Step S403 Since the usage amount corresponding to the Monitoring Key2 belongs to the sponsored data connection, it should not be accumulated in the consumption of the IP-CAN session level (the usage amount corresponding to the Monitoring Keyl), and therefore, the total allowable amount of the remaining IP-CAN session level of the user at this time.
  • TAU1 is updated to the usage report value of TAU1-UR1 and the usage report value of UR2, and the remaining sponsored data connection usage AUT is updated to the usage report value of AUT-UR2;
  • Step S404 The PCRF sends the remaining amount to the AF, that is, the updated AUT in step S403;
  • Step S405 The AF returns an acknowledgement message to the PCRF;
  • Step S406 The PCRF returns an IP-CAN session termination confirmation message to the PCEF.
  • Step S407 The PCRF sends a cancel subscription notification request message to the SPR, carrying the remaining total allowed usage, that is, the updated TAU1 in step S403;
  • Step S408 The SPR returns to cancel the subscription notification response.
  • FIG. 5 is a flow chart of reporting consumption consumption when the consumption of the service data flow level reaches the usage threshold or when all the PCC rules including the Monitoring Key 2 are deleted, deactivated, or the PCRF explicitly requests the PCEF to report the usage of the Monitoring Key 2 according to the embodiment of the present invention.
  • Step S501 Monitoring Key2 (one or a group of service data flow levels) corresponding to the usage threshold (ie, UT2), all PCC rules including Monitoring Key2 are deleted, deactivated, or PCRF explicitly requests the PCEF to report the usage of Monitoring Key2 When consumed, the PCEF triggers the usage reporting process;
  • the usage threshold ie, UT2
  • Step S502 The PCEF sends a policy and charging rule request to the PCRF, and the usage report is reported above.
  • the usage report here includes the UR2 corresponding to the Monitoring Key2, wherein the amount of UR2 is ⁇ 2;
  • Step S503 The PCRF makes a decision according to the reported usage report. Since the usage of the Monitoring Key2 belongs to the sponsored data connection, it should not be accumulated in the consumption of the IP-CAN session level (the usage corresponding to the Monitoring Keyl). Therefore, the user remaining at this time The IP-CAN session level total allowable usage TAU1 is updated to the TAU1+UR2 usage report value, and the remaining sponsored data connection usage AUT is updated to the AUT-UR2 usage report value;
  • Step S504 If the PCRF decides to continue the usage of the Monitoring Key2, the PCRF carries the Monitoring Key2 and the corresponding usage threshold UT2' (where UT2' ⁇ updated AUT) in the returned policy and charging rule request confirmation;
  • Step S505 After the PCEF installs the policy, the usage monitoring is continued.
  • PCRF For the process described in FIG. 2 to FIG. 5, if the UE accesses through the IP-CAN session is not a sponsored data connection, but a service that does not need to accumulate IP-CAN session level usage according to the user's subscription or network policy,
  • the execution and interaction processes of PCRF and PCEF are similar.
  • the PCEF reports the usage report of the IP-CAN session level to the PCRF, it reports the usage index of all the monitoring keys of the user; the PCRF updates the total allowable usage of the IP-CAN session level; if the Monitoring Key contains no need to accumulate IP-CAN
  • the monitoring key of the session-level usage service the total allowed usage is equal to the original total allowable amount plus the usage of the Monitoring Key of the service that does not need to accumulate IP-CAN session-level usage.
  • the advertising value minus the IP-CAN session. The usage value of the level of the Monitoring Key.
  • the PCEF reports the usage key of the user's Monitoring Key to the PCRF. If the Monitoring Key is the Monitoring Key corresponding to the service that does not need to be added to the IP-CAN session level, the PCRF updates the total allowable usage of the IP-CAN session level. The total allowable usage is equal to the original total allowable amount plus the amount of the Monitoring Key of the service that does not need to accumulate IP-CAN session level usage.
  • the UE accesses the sponsored data connection through the IP-CAN session, or does not need to accumulate the TDF session level usage according to the user's subscription or network policy.
  • the execution and interaction processes of the business, PCRF and TDF are similar.
  • the usage report of the TDF session level is reported (ie, All the monitoring keys related to the TDF session; PCRF updates the total allowable usage of the TDF session level; if the Monitoring Key contains the Monitoring Key of the application that does not need to accumulate TDF session level usage, the total allowed usage after the update is equal to the original The total allowable amount plus the usage key of the application that does not need to accumulate TDF session level usage is 4 reported value minus the usage report value of the Monitoring Key of the TDF session level.
  • the TDF reports the usage of the user's Monitoring Key to the PCRF.
  • the usage of the TDF session level reaches the usage threshold, all ADC rules including the Monitoring Key are deleted or deactivated, and the PCRF explicitly requests the report.
  • the PCRF updates the total allowable usage of the TDF session level, and the updated total allowed usage is equal to the original total allowable amount plus the no-accumulation.
  • the embodiment further provides a dosage monitoring system, including: PCEF and PCRF or TDF and PCRF, wherein:
  • the PCEF is configured to report the usage report of all the monitoring keys of the user when the usage report of the IP-CAN session level of the user needs to be reported to the PCRF; the usage of the PCEF at the IP-CAN session level reaches the usage threshold, When the PCRF explicitly requests the usage of the IP-CAN session level or the user to the end of the last IP-CAN session of the PDN, the user needs to report the usage report of the IP-CAN session level of the user to the PCRF.
  • the TDF is set to: report the usage report of all the monitoring keys of the user when the usage report of the TDF session level of the user needs to be reported to the PCRF; the usage of the TDF at the TDF session level reaches the usage threshold, and the PCRF explicit request
  • the usage report of the user's IP-CAN session level is reported to the PCRF when the usage of the TDF session level or the end of the TDF session is reported.
  • the PCRF is set to: update the total allowable usage of the IP-CAN session level. If the monitoring key includes a monitoring key corresponding to the service that does not need to be accumulated into the IP-CAN session level, the total allowed usage after the update is equal to the original Total allowable amount plus the amount of IP-CAN session level that does not need to be accumulated The usage report value of the monitoring key corresponding to the service minus the usage report value of the monitoring key of the IP-CAN session level.
  • the PCRF is set to: update the total allowed usage of the TDF session level. If the monitoring key includes a monitoring key corresponding to the application that does not need to be accumulated into the TDF session level, the total allowed usage after the update is equal to the original total allowed. The usage amount is added to the usage report value corresponding to the monitoring key corresponding to the application that does not need to be accumulated into the TDF session level, and the usage report value of the monitoring key of the TDF session level is subtracted.
  • the PCEF is configured to: report the usage report of the user's monitoring key to the PCRF; the TDF is set to report the usage index of the user's monitoring key to the PCRF; the PCRF is set to: when the monitoring key is When the monitoring key corresponding to the service/application of the IP-CAN/TDF session level usage is not accumulated, the total allowable usage of the IP-CAN/TDF session level of the user is updated, and the total allowable amount after the update is equal to the original total allowable amount. Plus the usage report value of the business/application that does not need to accumulate IP-CAN/TDF session level usage.
  • the PCEF reports the usage of the monitoring key to the PCRF when the usage of the monitoring key reaches the usage threshold, all the PCC rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the PCEF to report the usage of the monitoring key.
  • the TDF reports the usage of the monitoring key to the PCRF when the usage of the monitoring key reaches the usage threshold, all the ADC rules including the monitoring key are deleted or deactivated, or the PCRF explicitly requests the TDF to report the usage of the monitoring key.
  • modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed among multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any particular hard The combination of software and software.
  • the PCRF after receiving the usage report of the monitoring key of the user reported by the PCEF, if the PCRF includes the monitoring key corresponding to the sponsored data connection, the total allowed amount of the user's IP-CAN session is added to the sponsored data connection.
  • the corresponding monitoring key usage report value so that the total allowable usage of the IP-CAN session can faithfully reflect the total amount of remaining user capacity that can be used, and thus the present invention has industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种用量监测方法和系统，该方法包括：策略执行功能实体需要向策略和计费规则功能实体（PCRF）上报用户的会话级别的用量报告时，上报所述会话的全部监测键的用量报告；所述PCRF对所述会话级别的总允许用量进行更新；若所述监测键中包含不需累计入所述会话级别用量的业务对应的监测键，则更新后的总允许用量等于原总允许用量减去所述会话级别的监测键的用量报告值再加上所述不需累计入所述会话级别用量的业务对应的监测键的用量报告值。采用上述技术方案，能够使会话的总允许用量如实反映出用户剩余的能够使用的总用量。

Description

一种用量监测方法及系统
技术领域
本发明涉及用量监测技术， 尤其涉及一种用量监测方法及系统。 背景技术
第三代合作伙伴计划 （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非漫游架构的示意图，以下参照图 1对 PCC 架构中的各个逻辑功能实体及其接口功能进行描述：
应用功能实体（AF, Application Function ) , 提供业务应用的接入点， 这 些业务应用所使用的网络资源需要进行动态的策略控制。 在业务面进行参数 协商时， AF将相关业务信息传递给策略与计费规则功能实体（PCRF, Policy and Charging Rules Function )。 如果这些业务信息与 PCRF的策略相一致， 则 PCRF接受该协商； 否则， PCRF拒绝该协商， 并在反馈中同时给出 PCRF可 接受的业务参数。 随后， AF 可将这些参数返回给用户设备 （UE , User Equipment ) 。 其中， AF和 PCRF之间的接口是 Rx接口。
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 ) 内， 在承载面执行 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下发的包含应用检测控制策略的应用检测控制 规则进行应用检测并进行策略执行（如门控、重定向、带宽限制和用量监控）。 PCEF—般都位于网络的网关上，如 GPRS中的 GPRS网关支持节点（GGSN ) 以及 I-WLAN中的分组数据网关 （ PDG, Packet Data Gateway ) 。
此外，网络中还可能存在业务检测功能（ TDF , Traffic Detection Function )。
TDF与 PCRF通过 Sd接口， TDF可以根据预配置或 PCRF下发的 ADC规则 进行应用检测和策略执行。 承载绑定和事件报告功能实体（BBERF, Bearer Binding and Event Reporting Function ) 。 其功能包括 载绑定、 上行 载绑定 的验证以及事件报告。 当 UE通过 E-UTRAN接入， 并且 S-GW与 P-GW之 间釆用 PMIPv6协议时， BBERF就位于 S-GW, 当 UE通过可信任非 3GPP接 入系统接入时 , BBERF位于可信任非 3GPP接入网关， 当 UE通过不可信任 非 3GPP接入系统接入时、 BBERF位于演进的分组数据网关（ ePDG, Evolved Packet Data Gateway ) , 此时， PCEF不再执行承载绑定功能。
SPR存储了和策略控制与计费相关的用户策略计费控制签约信息。 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 进行用量监测控制时， 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显式请求用量上 ^艮时， PCEF将向 PCRF报告自从上一次上 4艮以来相关 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向 TDF订阅用 量上报（ Usage— Report )事件触发器。 当 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通知 PCRF0
然而， 现有技术存在以下问题： 若用户在 SPR中具有基于 IP-CAN会话 级的用量签约数据， 即 PCRF需要根据 SPR的签约， 指示 PCEF监测整个 IP-CAN会话的所有业务数据流的累计用量。 而此时， 用户又访问了某种被赞 助数据连接的业务， AF将向 PCRF提供赞助的用量， PCRF指示 PCEF监测 该被赞助数据连接业务的用量， 由于被赞助数据连接的业务产生的用量消耗 是由业务提供方承担， 导致用量监测错误。
此外， 若根据用户签约或网络策略， 用户访问的某种或某些业务不应该 累计入 IP-CAN会话级别的用量时， 现有技术也会出现同样的问题。
类似地， 当 PCC架构引入了 TDF并且 TDF也执行用量时， 若用户访问 了被赞助数据连接或根据用户签约或网络策略， 用户访问的某种或某些业务 不应该累计入 TDF会话级别的用量时， 现有技术也会出现同样的问题。
发明内容
本发明要解决的技术问题是提供一种用量监测方法及系统， 解决 PCEF 监测未能反映用户的 IP-CAN会话所消耗的由用户自身承担的用量的 一种用量监测方法， 包括：
策略和计费执行功能实体 （PCEF ) 需要向策略和计费规则功能实体
( PCRF )上报用户的 IP连接接入网 （ IP-CAN )会话级别的用量报告时， 上 报用户的全部监测键的用量报告；
PCRF对 IP-CAN会话级别的总允许用量进行更新；
若监测键中包含被赞助数据连接对应的监测键， 则更新后的总允许用量 等于原总允许用量加上被赞助数据连接对应的监测键的用量报告值减去 IP-CAN会话级别的监测键的用量报告值。
其中， 全部监测键的用量报告为用户到同一分组数据网络（PDN ) 的全 部 IP-CAN会话的监测键的用量报告。
其中， PCEF在 IP-CAN会话级别的用量达到用量阔值、 PCRF显式请求 上报 IP-CAN会话级别的用量或用户到 PDN的最后一个 IP-CAN会话终结时， 需要向 PCRF上报用户的 IP-CAN会话级别的用量报告。
其中， 该方法还包括： 当用户到 PDN的最后一个 IP-CAN会话终结时， PCRF将更新后的总允许用量上报给用户签约数据库。
一种用量监测方法， 包括：
策略和计费执行功能实体（PCEF )向策略和计费规则功能实体（PCRF ) 上报用户的监测键的用量报告；
当监测键为被赞助数据连接对应的监测键时， PCRF对用户的 IP连接接 入网 （IP-CAN )会话级别的总允许用量进行更新， 更新后的总允许用量等于 原总允许用量加上被赞助数据连接对应的监测键的用量报告值。
其中， PCEF在监测键的用量达到用量阔值、 包含监测键的所有 PCC规 则被删除或去激活或 PCRF显式请求 PCEF上报监测键的用量时， 向 PCRF 上报监测键的用量报告。
一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策略和 计费规则功能实体（PCRF ) , 其中：
PCEF, 用于在需要向 PCRF上报用户的 IP连接接入网 （ IP-CAN )会话 级别的用量报告时， 上报用户的全部监测键的用量报告； PCRF, 用于对 IP-CAN会话级别的总允许用量进行更新， 若监测键中包 含被赞助数据连接对应的监测键， 则更新后的总允许用量等于原总允许用量 加上被赞助数据连接对应的监测键的用量报告值减去 IP-CAN会话级别的监 测键的用量报告值。
其中， PCEF在 IP-CAN会话级别的用量达到用量阔值、 PCRF显式请求 上报 IP-CAN会话级别的用量或用户到分组数据网络（PDN ) 的最后一个 IP-CAN会话终结时，需要向 PCRF上报用户的 IP-CAN会话级别的用量报告。
一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策略和 计费规则功能实体（PCRF ) , 其中：
PCEF, 用于向 PCRF上报用户的监测键的用量报告；
PCRF, 用于当监测键为被赞助数据连接对应的监测键时， 对用户的 IP 连接接入网 （IP-CAN )会话级别的总允许用量进行更新， 更新后的总允许用 量等于原总允许用量加上被赞助数据连接对应的监测键的用量报告值。
其中， PCEF在监测键的用量达到用量阔值、 包含监测键的所有 PCC规 则被删除或去激活或 PCRF显式请求 PCEF上报监测键的用量时， 向 PCRF 上报监测键的用量报告。
一种用量监测方法， 包括：
策略和计费执行功能实体 （PCEF ) 需要向策略和计费规则功能实体 ( PCRF )上报用户的 IP连接接入网 （ IP-CAN )会话级别的用量报告时， 上 报所述 IP-CAN会话的全部监测键的用量报告；
所述 PCRF对所述 IP-CAN会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述 IP-CAN会话级别用量的业务对应 的监测键， 则更新后的总允许用量等于原总允许用量减去所述 IP-CAN会话 级别的监测键的用量报告值再加上所述不需累计入所述 IP-CAN会话级别用 量的业务对应的监测键的用量报告值。
其中， 所述不需累计入 IP-CAN会话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述 IP-CAN 会话级别用量的业务。 其中， 所述全部监测键的用量报告为：
所述用户到同一分组数据网络（PDN ) 的全部 IP-CAN会话的监测键的 用量报告。
其中， 需要向所述 PCRF上报用户的 IP-CAN会话级别的用量报告的步 骤包括：
所述 PCEF在所述 IP-CAN会话级别的用量达到用量阔值、 所述 PCRF 显式请求上报所述 IP-CAN会话级别的用量或所述用户到所述 PDN的最后一 的用量报告。
该用量监测方法还包括：
当所述用户到所述 PDN的最后一个 IP-CAN会话终结时， 所述 PCRF将 所述更新后的总允许用量上 给用户签约数据库。
一种用量监测方法， 包括：
业务检测功能（TDF )需要向策略和计费规则功能实体（PCRF )上报用 户的 TDF会话级别的用量报告时，上报所述 TDF会话的全部监测键的用量报 告.
所述 PCRF对所述 TDF会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述 TDF会话级别用量的应用对应的监 测键， 则更新后的总允许用量等于原总允许用量减去所述 TDF会话级别的监 测键的用量报告值再加上所述不需累计入所述 TDF会话级别用量的应用对应 的监测键的用量报告值。
其中， 所述不需累计入 TDF会话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述 TDF会话 级别用量的应用。
其中， 需要向所述 PCRF上报用户的 TDF会话级别的用量报告的步骤包 括：
所述 TDF在所述 TDF会话级别的用量达到用量阔值、所述 PCRF显式请 求上艮所述 TDF会话级别的用量或所述 TDF会话终结时， 需要向所述 PCRF 上报用户的所述 TDF会话级别的用量报告。
一种用量监测方法， 包括：
策略执行功能实体需要向策略和计费规则功能实体（ PCRF )上报用户的 会话级别的用量报告时， 上报所述会话的全部监测键的用量报告；
所述 PCRF对所述会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述会话级别用量的业务对应的监测 键， 则更新后的总允许用量等于原总允许用量减去所述会话级别的监测键的 用量报告值再加上所述不需累计入所述会话级别用量的业务对应的监测键的 用量报告值。
其中， 所述不需累计入所述会话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述会话级别 用量的业务。
其中， 需要向所述 PCRF上报用户的会话级别的用量报告的步骤包括： 所述策略执行功能实体在所述会话级别的用量达到用量阔值、所述 PCRF 显式请求上报所述会话级别的用量或所述用户的所述会话终结时， 需要向所 述 PCRF上报用户的所述会话级别的用量报告。
其中： 所述策略执行功能实体为策略和计费执行功能实体（PCEF ) , 所 述会话为 IP连接接入网 （IP-CAN )会话。
其中： 所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF 会话。
一种用量监测方法， 包括：
策略和计费执行功能实体（PCEF )向策略和计费规则功能实体（PCRF ) 上报用户的监测键的用量报告；
当所述监测键为不需累计入 IP连接接入网（IP-CAN )会话级别用量的业 务对应的监测键时， 所述 PCRF对所述 IP-CAN会话级别的总允许用量进行 更新， 更新后的总允许用量等于原总允许用量加上所述不需累计入所述 IP-CAN会话级别用量的业务的监测键的用量报告值。
其中， PCEF向 PCRF上报用户的监测键的用量报告的步骤包括： 所述 PCEF在所述监测键的用量达到用量阔值、 包含所述监测键的所有 策略和计费控制（PCC )规则被删除或去激活或所述 PCRF显式请求所述 PCEF 上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
一种用量监测方法， 包括：
业务检测功能（TDF )向策略和计费规则功能实体（PCRF )上报用户的 监测键的用量报告；
当所述监测键为不需累计入 TDF会话级别用量的应用对应的监测键时， 所述 PCRF对所述 TDF会话级别的总允许用量进行更新， 更新后的总允许用 量等于原总允许用量加上所述不需累计入所述 TDF会话级别用量的应用的监 测键的用量报告值。
其中， TDF向 PCRF上报用户的监测键的用量报告的步骤包括： 所述 TDF在所述监测键的用量达到用量阔值、 包含所述监测键的所有应 用检测和控制 （ ADC )规则被删除或去激活或所述 PCRF显式请求所述 TDF 上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
一种用量监测方法， 包括：
策略执行功能实体向策略和计费规则功能实体（ PCRF )上报用户的监测 键的用量报告；
当所述监测键为不需累计入会话级别用量的业务对应的监测键时， 所述
PCRF对所述会话级别的总允许用量进行更新，更新后的总允许用量等于原总 允许用量加上所述不需累计入所述会话级别用量的业务的监测键的用量报告 值。
其中， 策略执行功能实体向 PCRF上报用户的监测键的用量报告的步骤 包括：
所述策略执行功能实体在所述监测键的用量达到用量阔值、 包含所述监 测键的所有规则被删除或去激活或所述 PCRF显式请求所述策略执行功能实 体上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。 其中： 所述策略执行功能实体为策略和计费执行功能实体（PCEF ) , 所 述会话为 IP连接接入网（IP-CAN )会话，所述规则为策略和计费控制（PCC ) 规则。
其中： 所述策略执行功能实体为业务检测功能（TDF ) , 所述会话为 TDF 会话， 所述规则为应用检测和控制 （ADC )规则。
一种用量监测系统， 包括： 业务监测功能（TDF )和策略和计费规则功 能实体（PCRF ) ， 其中：
所述 TDF设置成：在需要向所述 PCRF上报用户的 TDF会话级别的用量 报告时， 上报所述 TDF会话的全部监测键的用量报告；
所述 PCRF设置成： 对所述 TDF会话级别的总允许用量进行更新， 若所 述监测键中包含不需累计入所述 TDF会话级别的应用对应的监测键， 则更新 后的总允许用量等于原总允许用量减去所述 TDF会话级别的监测键的用量报 告值再加上所述不需累计入所述 TDF会话级别的应用对应的监测键的用量报 告值。
其中： 所述 TDF还设置成：
在所述 TDF会话级别的用量达到用量阔值、 所述 PCRF显式请求上报所 述 TDF会话级别的用量或所述 TDF会话终结时，需要向所述 PCRF上报用户 的所述 TDF会话级别的用量报告。
一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策略和 计费规则功能实体（PCRF ) , 其中：
所述 PCEF设置成： 在需要向所述 PCRF 上报用户的 IP连接接入网 ( IP-CAN )会话级别的用量报告时，上报所述用户的全部监测键的用量报告； 所述 PCRF设置成： 对所述 IP-CAN会话级别的总允许用量进行更新， 若所述监测键中包含不需累计入所述 IP-CAN会话级别的业务对应的监测键， 则更新后的总允许用量等于原总允许用量减去所述 IP-CAN会话级别的监测 键的用量报告值再加上所述不需累计入所述 IP-CAN会话级别的业务对应的 监测键的用量报告值。
其中： 所述 PCEF还设置成： 在所述 IP-CAN会话级别的用量达到用量阔值、 所述 PCRF显式请求上 报所述 IP-CAN会话级别的用量或所述用户到分组数据网络（PDN ) 的最后 一个 IP-CAN会话终结时，需要向所述 PCRF上报用户的所述 IP-CAN会话级 别的用量报告。
一种用量监测系统， 包括： 策略执行功能实体和策略和计费规则功能实 体（PCRF ) , 其中：
所述策略执行功能实体设置成： 在需要向所述 PCRF上报用户的会话级 别的用量报告时， 上报所述用户的全部监测键的用量报告；
所述 PCRF设置成： 对所述会话级别的总允许用量进行更新， 若所述监 测键中包含不需累计入所述会话级别的业务或应用对应的监测键， 则更新后 的总允许用量等于原总允许用量减去所述会话级别的监测键的用量报告值再 加上所述不需累计入所述会话级别的业务或应用对应的监测键的用量报告 值。
其中： 所述策略执行功能实体还设置成：
在所述会话级别的用量达到用量阔值、 所述 PCRF显式请求上报所述会 话级别的用量或所述会话终结时， 需要向所述 PCRF上报用户的所述会话级 别的用量报告。
其中： 所述策略执行功能实体为策略和计费执行功能实体（PCEF ) , 所 述会话为 IP连接接入网 （IP-CAN )会话。
其中： 所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF 会话。
一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策略和 计费规则功能实体（PCRF ) , 其中：
所述 PCEF设置成： 向所述 PCRF上报用户的监测键的用量报告； 所述 PCRF设置成：当所述监测键为不需累计入 IP连接接入网（ IP-CAN ) 会话级别的业务对应的监测键时， 对所述 IP-CAN会话级别的总允许用量进 行更新， 更新后的总允许用量等于原总允许用量加上所述不需累计入所述 IP-CAN会话级别的业务对应的监测键的用量报告值。 其中： 所述 PCEF还设置成：
在所述监测键的用量达到用量阔值、 包含所述监测键的所有策略和计费 控制（ PCC )规则被删除或去激活或所述 PCRF显式请求所述 PCEF上报所述 监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
一种用量监测系统， 包括： 业务检测功能（TDF )和策略和计费规则功 能实体（PCRF ) ， 其中：
所述 TDF设置成： 向所述 PCRF上报用户的监测键的用量报告； 所述 PCRF设置成： 当所述监测键为不需累计入 TDF会话级别的应用对 应的监测键时， 对所述 TDF会话级别的总允许用量进行更新， 更新后的总允 许用量等于原总允许用量加上所述不需累计入所述 TDF会话级别的应用对应 的监测键的用量报告值。
其中： 所述 TDF还设置成：
在所述监测键的用量达到用量阔值、 包含所述监测键的所有应用检测和 控制（ ADC )规则被删除或去激活或所述 PCRF显式请求所述 TDF上报所述 监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
一种用量监测系统， 包括： 策略执行功能实体和策略和计费规则功能实 体（PCRF ) , 其中：
所述策略执行功能实体设置成： 向所述 PCRF上报用户的监测键的用量 报告；
所述 PCRF设置成： 当所述监测键为不需累计入会话级别的业务或应用 对应的监测键时， 对所述会话级别的总允许用量进行更新， 更新后的总允许 用量等于原总允许用量加上所述不需累计入所述会话级别的业务或应用对应 的监测键的用量报告值。
其中： 所述策略执行功能实体还设置成：
在所述监测键的用量达到用量阔值、 包含所述监测键的所有规则被删除 或去激活或所述 PCRF显式请求所述策略执行功能实体上报所述监测键的用 量时， 向所述 PCRF上报所述监测键的用量报告。
其中： 所述策略执行功能实体为策略和计费执行功能实体（PCEF ) , 所 述会话为 IP连接接入网（IP-CAN )会话，所述规则为策略和计费控制（PCC ) 规则。
其中： 所述策略执行功能实体为业务检测功能（TDF ) , 所述会话为 TDF 会话， 所述规则为应用检测和控制 （ADC )规则。
综上所述， 本发明实施方式中 PCRF在接收到策略执行功能实体 PCEF 和 TDF上报的用户的监测键的用量报告后， 若包含被赞助数据连接对应的监 测键， 则将会话的总允许用量加上被赞助数据连接对应的监测键的用量报告 值， 从而使会话的总允许用量如实反映出用户剩余的能够使用的总用量。 附图概述
图 1为现有技术中的 Rel-8 PCC非漫游架构的示意图；
图 2为本发明实施方式的用量监测方法中下发 IP-CAN会话级别用量监 测策略和被赞助数据连接业务的用量监测策略的流程图；
图 3为本发明实施方式的用量监测方法中 IP-CAN会话级别的用量消耗 达到用量阔值或 PCRF显式请求 PCEF上报 IP-CAN会话级别的用量消耗时上 报用量消耗的流程图；
图 4为本发明实施方式的用量监测方法中 UE到 PDN的最后一个 IP-CAN 会话终结时上报用量报告的流程图；
图 5为本发明实施方式的用量监测方法中业务数据流级别用量消耗达到 用量阔值或包含 Monitoring Key2的所有 PCC规则被删除、 去激活或 PCRF 显式请求 PCEF上报 Monitoring Key2的用量消耗时上报用量消耗的流程图。 本发明的较佳实施方式
考虑到 PCEF是根据 SPR的签约，监测用户到 PDN的一个或多个 IP-CAN 会话的所有业务数据流的累计用量（IP-CAN会话级别用量监测）， 也会将用 户访问的被赞助数据连接的业务产生的用量计算在 IP-CAN会话级别的用量 中， 而被赞助数据连接的业务产生的用量消耗是由业务提供方承担， 导致 PCEF向 PCRF上报的用量监测未能反映用户 IP-CAN会话级别所消耗的由用 户自身承担的用量。
下面结合附图对本实施方式进行详细说明。
实施例 1 :
图 2为根据本发明实施例的下发 IP-CAN会话级别用量监测策略和被赞 助数据连接业务的用量监测策略的流程图， 包括：
步骤 S201 : 在 UE请求建立到 PDN的 IP-CAN会话的过程中， PCEF所 在的网关接收到 IP-CAN会话建立请求消息，在该 IP-CAN会话建立请求消息 中携带有用户标识和请求接入的 PDN网络的 PDN标识；
步骤 S202: PCEF 向 PCRF发送 IP-CAN会话建立指示消息， 并在该 IP-CAN会话建立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP 地址（IP Address ) ；
步骤 S203: PCRF根据用户标识判断还没有该用户的签约信息， 向 SPR 发送签约文档请求， 在该签约文档请求中携带用户标识和 PDN标识；
步骤 S204: SPR根据用户标识和 PDN标识返回用户签约信息 （即， 签 约文档应答）， 用户签约信息中包含该用户该 PDN ( Per PDN and User )的总 允许用量 (TAU , Totally Allowed Usage) 1；
步骤 S205: PCRF根据返回的用户签约信息、 网络策略和 UE的接入信 息等制定策略；
其中， 用量监测策略包括设置 Monitoring Key 1 ; 设置事件触发器， 取值 为 Usage— Report和设置用量阔值（UT, Usage Threshold ) 1。 其中 PCRF根 据从 SPR中获得的 TAU1分配用户的用量阔值 UT1且 UT1 TAU1。
这里， 用量监测针对 IP-CAN会话所有业务数据流， Monitoring Key 1不 包含在任何 PCC规则中 （ PCRF指示 PCEF该 Monitoring Key 1的用量监测为 IP-CAN会话级别 ) 。
步骤 S206: PCEF安装策略， 包括用量监测策略， PCEF所在的网关返回 IP-CAN会话建立应答， 在 IP-CAN会话建立应答中携带有 IP Address; 在步骤 S206后， UE可能还会与该 PDN建立另外的 IP-CAN会话， 此时 Monitoring Key 1针对 UE与 PDN建立的所有 IP-CAN会话的所有业务数据流， 即 Monitoring Keyl是针对 Per PDN and UE。
步骤 S207： PCEF执行用量监测策略， 对用户访问该 PDN (通过一个或 多个 IP-CAN会话 )的所有业务数据流进行用量监测（即执行 IP-CAN会话级 别的用量监测） ；
在这个过程中， PCEF可能会与 PCRF进行交互， 上报消耗的用量值以及 请求新的用量阔值。 步骤 S208: UE通过步骤 S201〜步骤 S207建立的 IP-CAN会话 (包含一 个或多个 IP-CAN会话）与第三方的应用业务提供者（ ASP, Application Service Provider )服务器连接并请求业务， ASP服务器决定为该用户提供被赞助数据 连接， ASP服务器向 AF提供动态的被赞助数据连接信息， 信息中包括赞助 方标识、 ASP标识、 标识被赞助的用户信息 （如 IP Address ) , 被赞助业务 的 IP流信息和允许用量阔值（ AUT , Allowed Usage Threshold ) ；
上述 AF位于与 UE建立一个或多个 IP-CAN会话的上述 PDN中。
步骤 S209: AF向 PCRF提供被赞助数据连接信息， 信息中包括赞助方 标识、 ASP标识、 标识被赞助的用户信息 （如 IP Address ) , 被赞助业务的 IP流信息和允许用量阔值 Allowed Usage Threshold ( AUT ) ；
步骤 S210: PCRF保存信息后， 返回确认消息；
步骤 S211 : PCRF根据从 AF获得的信息， 网络策略以及用户签约等进 行策略决策， 制定 PCC规则；
PCRF决定对被赞助数据连接的业务进行用量监测， 制定用量监测策略， 包括设置 Monitoring Key2和设置用量阔值 UT2 , 其中 UT2 < AUT , PCRF将 Monitoring Key2包含在该业务数据流对应的 PCC规则中；
步骤 S212: PCRF 向 PCEF 下发制定的 PCC规则， PCC规则中包含
Monitoring Key2 , PCRF还提供 Monitoring Key2对应的用量阔值 UT2；
步骤 S213: PCEF安装策略后， 向 PCRF返回确认消息；
步骤 S214: PCEF此时同时执行 IP-CAN会话级别的用量监测和业务数 据流级别的用量监测， 此时， 对于 Monitoring Key2的用量消耗， IP-CAN会 话级别也会累计。
图 3为根据本发明实施例的 IP-CAN会话级别的用量消耗达到用量阔值 或 PCRF显式请求 PCEF上报 IP-CAN会话级别的用量消耗时，上报用量消耗 的流程图， 包括：
步骤 S301 : Monitoring Keyl ( IP-CAN会话级别 )对应的用量消耗达到 用量阔值（即 UT1 )或 PCRF显式请求 PCEF上报 IP-CAN会话级别的用量消 耗时， PCEF触发用量上报流程；
步骤 S302: PCEF向 PCRF发送策略和计费规则请求， 以上报用量报告， 此时 PCEF上报 UE到该 PDN的所有 IP-CAN会话 (UE到该 PDN建立一个或 多个 IP-CAN会话)的所有 Monitoring Key的用量报告， 这里用量报告 ( UR, Usage Reprot ) 包括 Monitoring Keyl对应的 UR1和 Monitoring Key2对应的 UR2, 其中 UR1的用量 4艮告值 UT1 , UR2的用量 4艮告值 UT2;
步骤 S303: PCRF根据 PCEF上报的用量报告进行决策， 由于 Monitoring Key2对应的用量属于被赞助数据连接， 不应该累计在 IP-CAN会话级别用量 (Monitoring Keyl对应的用量)消耗中， 因此， 此时用户剩余的 IP-CAN会话级 别总允许用量 TAU1更新为 TAU1-UR1的用量报告值 +UR2的用量 告值， 剩余的被赞助数据连接的用量 AUT更新为 AUT-UR2的用量报告值；
步骤 S304: 若 PCRF决定继续 Monitoring Keyl的用量， 则在返回的策略 和计费规则请求确认中携带 Monitoring Keyl以及对应的用量阔值 UT Γ (其中 UT1' <更新后的 TAU1);若 PCRF决定继续 Monitoring Key2的用量，则 PCRF 在返回消息中携带 Monitoring Key2以及对应的用量阔值 UT2， (其中 UT2， <更 新后的 AUT);
步骤 S305: PCEF安装策略后， 继续执行 IP-CAN会话级别和业务数据 流级别的用量监测。 图 4为根据本发明实施例的 UE到 PDN的最后一个 IP-CAN会话终结时 上报用量报告的流程图， 包括：
步骤 S401： PCEF所在的网关接收到 UE到 PDN的最后一个 IP-CAN会 话终结的触发；
步骤 S402: PCEF向 PCRF发送 IP-CAN会话终结指示， 此时 PCEF上才艮
UE到该 PDN的所有 IP-CAN会话的所有 Monitoring Key的用量报告，这里用 量才艮告包括 Monitoring Key 1对应的 UR1和 Monitoring Key2对应的 UR2 , 其 中 UR1的用量报告值 UT1 , UR2的用量报告值 UT2;
步骤 S403: 由于 Monitoring Key2对应的用量属于被赞助数据连接， 不应 该累计在 IP-CAN会话级别用量 (Monitoring Keyl对应的用量)消耗中， 因此， 此时用户剩余的 IP-CAN会话级别总允许用量 TAU1更新为 TAU1-UR1的用 量报告值 +UR2 的用量报告值， 剩余被赞助数据连接用量 AUT 更新为 AUT-UR2的用量报告值；
步骤 S404: PCRF向 AF上^艮剩余的用量，即步骤 S403中更新后的 AUT; 步骤 S405: AF向 PCRF返回确认消息；
步骤 S406: PCRF向 PCEF返回 IP-CAN会话终结确认消息；
步骤 S407: PCRF向 SPR发送取消签约通知请求消息， 携带剩余的总允 许用量， 即步骤 S403中更新后的 TAU1；
步骤 S408: SPR返回取消签约通知应答。
图 5为根据本发明实施例的业务数据流级别用量消耗达到用量阔值或包 含 Monitoring Key2的所有 PCC规则被删除、 去激活或 PCRF显式请求 PCEF 上报 Monitoring Key2的用量消耗时上报用量消耗的流程图， 包括：
步骤 S501 : Monitoring Key2 (一个或一组业务数据流级别）对应的用量 达到用量阔值（即 UT2 ) 、 包含 Monitoring Key2的所有 PCC规则被删除、 去激活或 PCRF显式请求 PCEF上报 Monitoring Key2的用量消耗时， PCEF 触发用量上报流程；
步骤 S502: PCEF向 PCRF发送策略和计费规则请求， 以上报用量报告， 这里用量报告包括 Monitoring Key2对应的 UR2 , 其中 UR2的用量^艮告值 UT2;
步骤 S503: PCRF根据上报的用量报告进行决策， 由于 Monitoring Key2 的用量属于被赞助数据连接，不应该累计在 IP-CAN会话级别用量 (Monitoring Keyl对应的用量)消耗中， 因此， 此时用户剩余的 IP-CAN会话级别总允许用 量 TAU1更新为 TAU1+UR2的用量报告值，剩余被赞助数据连接的用量 AUT 更新为 AUT-UR2的用量报告值；
步骤 S504: 若 PCRF决定继续 Monitoring Key2的用量， 则 PCRF在返回 的策略和计费规则请求确认中携带 Monitoring Key2 以及对应的用量阔值 UT2 ' (其中 UT2 ' <更新后的 AUT)；
步骤 S505: PCEF安装策略后， 继续执行用量监测。
对于图 2-图 5所述的流程，若 UE通过 IP-CAN会话访问的不是被赞助数 据连接， 而是一种根据用户的签约或网络策略不需累计入 IP-CAN会话级别 用量的业务， PCRF和 PCEF的执行和交互流程是类似的。 PCEF向 PCRF上 报 IP-CAN会话级别的用量报告时，上报用户的全部 Monitoring Key的用量报 告； PCRF对 IP-CAN会话级别的总允许用量进行更新； 若 Monitoring Key中 包含不需累计入 IP-CAN会话级别用量的业务的 Monitoring Key, 则更新后的 总允许用量等于原总允许用量加上不需累计入 IP-CAN会话级别用量的业务 的 Monitoring Key的用量 ^艮告值减去 IP-CAN会话级别的 Monitoring Key的用 量报告值。 PCEF 向 PCRF 上报用户的 Monitoring Key 的用量报告， 若 Monitoring Key为不需累计入 IP-CAN会话级别用量的业务对应的 Monitoring Key时， PCRF对 IP-CAN会话级别的总允许用量进行更新， 更新后的总允许 用量等于原总允许用量加上所述不需累计入 IP-CAN会话级别用量的业务的 Monitoring Key的用量 4艮告值。
对于 PCC架构引入 TDF功能后， UE通过 IP-CAN会话访问被赞助数据 连接， 或是一种根据用户的签约或网络策略不需累计入 TDF会话级别用量的 业务， PCRF和 TDF的执行和交互流程是类似的。 TDF向 PCRF上报 TDF会 话级别的用量报告时（包括 TDF会话级别的用量达到用量阔值、 PCRF显式 请求上报 TDF会话级别的用量或 TDF会话终结），上报用户的全部 Monitoring Key的用量报告 (即该 TDF会话相关的所有 Monitoring Key )； PCRF对 TDF 会话级别的总允许用量进行更新； 若 Monitoring Key中包含不需累计入 TDF 会话级别用量的应用的 Monitoring Key,则更新后的总允许用量等于原总允许 用量加上不需累计入 TDF会话级别用量的应用的 Monitoring Key的用量 4艮告 值减去 TDF会话级别的 Monitoring Key的用量报告值。 TDF向 PCRF上报用 户的 Monitoring Key的用量 ^艮告 (包括 TDF会话级别的用量达到用量阔值、 包含 Monitoring Key的所有 ADC规则被删除或去激活， PCRF显式请求上报 ) TDF会话级别的用量， 若 Monitoring Key为不需累计入 TDF会话级别用量的 应用对应的 Monitoring Key时 , PCRF对 TDF会话级别的总允许用量进行更 新， 更新后的总允许用量等于原总允许用量加上所述不需累计入 TDF会话级 别用量的业务的 Monitoring Key的用量报告值。
请再次参考图 1 , 本实施方式还提供了一种用量监测系统， 包括： PCEF 和 PCRF或 TDF和 PCRF, 其中：
PCEF设置成： 在需要向所述 PCRF上报用户的 IP-CAN会话级别的用量 报告时，上报所述用户的全部监测键的用量报告； 该 PCEF在 IP-CAN会话级 别的用量达到用量阔值、 PCRF显式请求上报 IP-CAN会话级别的用量或用户 到 PDN的最后一个 IP-CAN会话终结时需要向 PCRF上报用户的 IP-CAN会 话级别的用量报告。
TDF设置成： 在需要向所述 PCRF上报用户的 TDF会话级别的用量报告 时，上报所述用户的全部监测键的用量报告； 该 TDF在 TDF会话级别的用量 达到用量阔值、 PCRF显式请求上报 TDF会话级别的用量或 TDF会话终结时 需要向 PCRF上报用户的 IP-CAN会话级别的用量报告。
PCRF设置成： 对 IP-CAN会话级别的总允许用量进行更新， 若所述监测 键中包含不需累计入 IP-CAN会话级别用量的业务对应的监测键， 则更新后 的总允许用量等于原总允许用量加上所述不需累计入 IP-CAN会话级别用量 的业务对应的监测键的用量报告值减去所述 IP-CAN会话级别的监测键的用 量报告值。 或者， PCRF设置成： 对 TDF会话级别的总允许用量进行更新， 若所述监测键中包含不需累计入 TDF会话级别用量的应用对应的监测键， 则 更新后的总允许用量等于原总允许用量加上所述不需累计入 TDF会话级别用 量的应用对应的监测键的用量报告值减去所述 TDF会话级别的监测键的用量 报告值。
本实施方式的另一种监测系统中， PCEF设置成： 向 PCRF上报用户的监 测键的用量报告； TDF设置成：向 PCRF上报用户的监测键的用量报告； PCRF 设置成： 当监测键为被不需累计入 IP-CAN/TDF会话级别用量的业务 /应用对 应的监测键时， 对用户的 IP-CAN/TDF会话级别的总允许用量进行更新， 更 新后的总允许用量等于原总允许用量加上不需累计入 IP-CAN/TDF会话级别 用量的业务 /应用的用量报告值。
PCEF在监测键的用量达到用量阔值、 包含监测键的所有 PCC规则被删 除或去激活或 PCRF显式请求 PCEF上报所述监测键的用量时，向 PCRF上报 监测键的用量报告。
TDF在监测键的用量达到用量阔值、 包含监测键的所有 ADC规则被删 除或去激活或 PCRF显式请求 TDF上报所述监测键的用量时， 向 PCRF上报 监测键的用量报告。
上述系统中， 各功能实体的其它功能请参考方法内容的描述。
显然， 本领域的技术人员应该明白， 上述的本发明实施方式的各模块或 各步骤可以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可 执行的程序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来 执行， 并且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步 骤， 或者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或 步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬 件和软件结合。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。
工业实用性
本发明实施方式中 PCRF在接收到 PCEF上报的用户的监测键的用量报 告后， 若包含被赞助数据连接对应的监测键， 则将用户的 IP-CAN会话的总 允许用量加上被赞助数据连接对应的监测键的用量报告值， 从而使 IP-CAN 会话的总允许用量能够如实反映出用户剩余的能够使用的总用量， 因此本发 明具有 虽的工业实用性。

Claims

权 利 要 求 书
1、 一种用量监测方法， 包括：
策略和计费执行功能实体 （PCEF ) 需要向策略和计费规则功能实体 ( PCRF )上报用户的 IP连接接入网 （ IP-CAN )会话级别的用量报告时， 上 报所述 IP-CAN会话的全部监测键的用量报告；
所述 PCRF对所述 IP-CAN会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述 IP-CAN会话级别用量的业务对应 的监测键， 则更新后的总允许用量等于原总允许用量减去所述 IP-CAN会话 级别的监测键的用量报告值再加上所述不需累计入所述 IP-CAN会话级别用 量的业务对应的监测键的用量报告值。
2、 如权利要求 1所述的用量监测方法， 其中， 所述不需累计入 IP-CAN 会话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述 IP-CAN 会话级别用量的业务。
3、 如权利要求 1所述的用量监测方法， 其中， 所述全部监测键的用量报 告为：
所述用户到同一分组数据网络（PDN ) 的全部 IP-CAN会话的监测键的 用量报告。
4、如权利要求 1 -3中任一项所述的用量监测方法，其中，需要向所述 PCRF 上报用户的 IP-CAN会话级别的用量报告的步骤包括：
所述 PCEF在所述 IP-CAN会话级别的用量达到用量阔值、 所述 PCRF 显式请求上报所述 IP-CAN会话级别的用量或所述用户到所述 PDN的最后一 的用量报告。
5、 如权利要求 4所述的用量监测方法， 该用量监测方法还包括： 当所述用户到所述 PDN的最后一个 IP-CAN会话终结时， 所述 PCRF将 所述更新后的总允许用量上 给用户签约数据库。
6、 一种用量监测方法， 包括：
业务检测功能（TDF )需要向策略和计费规则功能实体（PCRF )上报用 户的 TDF会话级别的用量报告时，上报所述 TDF会话的全部监测键的用量报 告- 所述 PCRF对所述 TDF会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述 TDF会话级别用量的应用对应的监 测键， 则更新后的总允许用量等于原总允许用量减去所述 TDF会话级别的监 测键的用量报告值再加上所述不需累计入所述 TDF会话级别用量的应用对应 的监测键的用量报告值。
7、 如权利要求 6所述的用量监测方法， 其中， 所述不需累计入 TDF会 话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述 TDF会话 级别用量的应用。
8、 如权利要求 6或 7所述的用量监测方法， 其中， 需要向所述 PCRF上 报用户的 TDF会话级别的用量报告的步骤包括：
所述 TDF在所述 TDF会话级别的用量达到用量阔值、所述 PCRF显式请 求上艮所述 TDF会话级别的用量或所述 TDF会话终结时， 需要向所述 PCRF 上报用户的所述 TDF会话级别的用量报告。
9、 一种用量监测方法， 包括：
策略执行功能实体需要向策略和计费规则功能实体（ PCRF )上报用户的 会话级别的用量报告时， 上报所述会话的全部监测键的用量报告；
所述 PCRF对所述会话级别的总允许用量进行更新；
若所述监测键中包含不需累计入所述会话级别用量的业务对应的监测 键， 则更新后的总允许用量等于原总允许用量减去所述会话级别的监测键的 用量报告值再加上所述不需累计入所述会话级别用量的业务对应的监测键的 用量报告值。
10、 如权利要求 9所述的用量监测方法， 其中， 所述不需累计入所述会 话级别用量的业务为：
被赞助数据连接或根据用户的签约或网络策略不需累计入所述会话级别 用量的业务。
11、 如权利要求 10所述的用量监测方法， 其中， 需要向所述 PCRF上报 用户的会话级别的用量报告的步骤包括：
所述策略执行功能实体在所述会话级别的用量达到用量阔值、所述 PCRF 显式请求上报所述会话级别的用量或所述用户的所述会话终结时， 需要向所 述 PCRF上报用户的所述会话级别的用量报告。
12、 如权利要求 9-11中任一项所述的用量监测方法， 其中：
所述策略执行功能实体为策略和计费执行功能实体（ PCEF ) , 所述会话 为 IP连接接入网 （IP-CAN )会话。
13、 如权利要求 9-11中任一项所述的用量监测方法， 其中：
所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF会话。
14、 一种用量监测方法， 包括：
策略和计费执行功能实体（PCEF )向策略和计费规则功能实体（PCRF ) 上报用户的监测键的用量报告；
当所述监测键为不需累计入 IP连接接入网（ IP-CAN )会话级别用量的业 务对应的监测键时， 所述 PCRF对所述 IP-CAN会话级别的总允许用量进行 更新， 更新后的总允许用量等于原总允许用量加上所述不需累计入所述 IP-CAN会话级别用量的业务的监测键的用量报告值。
15、 如权利要求 14所述的用量监测方法， 其中， PCEF向 PCRF上报用 户的监测键的用量报告的步骤包括：
所述 PCEF在所述监测键的用量达到用量阔值、 包含所述监测键的所有 策略和计费控制（PCC )规则被删除或去激活或所述 PCRF显式请求所述 PCEF 上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
16、 一种用量监测方法， 包括：
业务检测功能（TDF )向策略和计费规则功能实体（PCRF )上报用户的 监测键的用量报告；
当所述监测键为不需累计入 TDF会话级别用量的应用对应的监测键时， 所述 PCRF对所述 TDF会话级别的总允许用量进行更新， 更新后的总允许用 量等于原总允许用量加上所述不需累计入所述 TDF会话级别用量的应用的监 测键的用量报告值。
17、 如权利要求 16所述的用量监测方法， 其中， TDF向 PCRF上报用户 的监测键的用量报告的步骤包括：
所述 TDF在所述监测键的用量达到用量阔值、 包含所述监测键的所有应 用检测和控制 （ADC )规则被删除或去激活或所述 PCRF显式请求所述 TDF 上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
18、 一种用量监测方法， 包括：
策略执行功能实体向策略和计费规则功能实体（PCRF )上报用户的监测 键的用量报告；
当所述监测键为不需累计入会话级别用量的业务对应的监测键时， 所述 PCRF对所述会话级别的总允许用量进行更新，更新后的总允许用量等于原总 允许用量加上所述不需累计入所述会话级别用量的业务的监测键的用量报告 值。
19、 如权利要求 18 所述的用量监测方法， 其中， 策略执行功能实体向 PCRF上报用户的监测键的用量报告的步骤包括：
所述策略执行功能实体在所述监测键的用量达到用量阔值、 包含所述监 测键的所有规则被删除或去激活或所述 PCRF显式请求所述策略执行功能实 体上报所述监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
20、 如权利要求 18或 19所述的用量监测方法， 其中： 所述策略执行功能实体为策略和计费执行功能实体（ PCEF ) , 所述会话 为 IP连接接入网（IP-CAN )会话， 所述规则为策略和计费控制（PCC )规则。
21、 如权利要求 18或 19所述的用量监测方法， 其中：
所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF会话， 所述规则为应用检测和控制 （ ADC )规则。
22、 一种用量监测系统， 包括： 业务检测功能（TDF )和策略和计费规 则功能实体（PCRF ) , 其中：
所述 TDF设置成：在需要向所述 PCRF上报用户的 TDF会话级别的用量 报告时， 上报所述 TDF会话的全部监测键的用量报告；
所述 PCRF设置成： 对所述 TDF会话级别的总允许用量进行更新， 若所 述监测键中包含不需累计入所述 TDF会话级别的应用对应的监测键， 则更新 后的总允许用量等于原总允许用量减去所述 TDF会话级别的监测键的用量报 告值再加上所述不需累计入所述 TDF会话级别的应用对应的监测键的用量报 告值。
23、 如权利要求 22所述的用量监测系统， 其中： 所述 TDF还设置成： 在所述 TDF会话级别的用量达到用量阔值、 所述 PCRF显式请求上报所 述 TDF会话级别的用量或所述 TDF会话终结时，需要向所述 PCRF上报用户 的所述 TDF会话级别的用量报告。
24、 一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策 略和计费规则功能实体（PCRF ) ， 其中：
所述 PCEF设置成： 在需要向所述 PCRF 上报用户的 IP连接接入网 ( IP-CAN )会话级别的用量报告时，上报所述用户的全部监测键的用量报告； 所述 PCRF设置成： 对所述 IP-CAN会话级别的总允许用量进行更新， 若所述监测键中包含不需累计入所述 IP-CAN会话级别的业务对应的监测键， 则更新后的总允许用量等于原总允许用量减去所述 IP-CAN会话级别的监测 键的用量报告值再加上所述不需累计入所述 IP-CAN会话级别的业务对应的 监测键的用量报告值。
25、 如权利要求 24所述的用量监测系统， 其中： 所述 PCEF还设置成： 在所述 IP-CAN会话级别的用量达到用量阔值、 所述 PCRF显式请求上 报所述 IP-CAN会话级别的用量或所述用户到分组数据网络（PDN ) 的最后 一个 IP-CAN会话终结时，需要向所述 PCRF上报用户的所述 IP-CAN会话级 别的用量报告。
26、 一种用量监测系统， 包括： 策略执行功能实体和策略和计费规则功 能实体（PCRF ) ， 其中：
所述策略执行功能实体设置成： 在需要向所述 PCRF上报用户的会话级 别的用量报告时， 上报所述用户的全部监测键的用量报告；
所述 PCRF设置成： 对所述会话级别的总允许用量进行更新， 若所述监 测键中包含不需累计入所述会话级别的业务或应用对应的监测键， 则更新后 的总允许用量等于原总允许用量减去所述会话级别的监测键的用量报告值再 加上所述不需累计入所述会话级别的业务或应用对应的监测键的用量报告 值。
27、 如权利要求 26所述的用量监测系统， 其中： 所述策略执行功能实体 还设置成：
在所述会话级别的用量达到用量阔值、 所述 PCRF显式请求上报所述会 话级别的用量或所述会话终结时， 需要向所述 PCRF上报用户的所述会话级 别的用量报告。
28、 如权利要求 26或 27所述的用量监测系统， 其中：
所述策略执行功能实体为策略和计费执行功能实体（ PCEF ) , 所述会话 为 IP连接接入网 （IP-CAN )会话。
29、 如权利要求 26或 27所述的用量监测系统， 其中：
所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF会话。
30、 一种用量监测系统， 包括： 策略和计费执行功能实体（PCEF )和策 略和计费规则功能实体（PCRF ) ， 其中：
所述 PCEF设置成： 向所述 PCRF上报用户的监测键的用量报告； 所述 PCRF设置成：当所述监测键为不需累计入 IP连接接入网（ IP-CAN ) 会话级别的业务对应的监测键时， 对所述 IP-CAN会话级别的总允许用量进 行更新， 更新后的总允许用量等于原总允许用量加上所述不需累计入所述 IP-CAN会话级别的业务对应的监测键的用量报告值。
31、 如权利要求 30所述的用量监测系统， 其中： 所述 PCEF还设置成： 在所述监测键的用量达到用量阔值、 包含所述监测键的所有策略和计费 控制（ PCC )规则被删除或去激活或所述 PCRF显式请求所述 PCEF上报所述 监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
32、 一种用量监测系统， 包括： 业务检测功能（TDF )和策略和计费规 则功能实体（PCRF ) , 其中：
所述 TDF设置成： 向所述 PCRF上报用户的监测键的用量报告； 所述 PCRF设置成： 当所述监测键为不需累计入 TDF会话级别的应用对 应的监测键时， 对所述 TDF会话级别的总允许用量进行更新， 更新后的总允 许用量等于原总允许用量加上所述不需累计入所述 TDF会话级别的应用对应 的监测键的用量报告值。
33、 如权利要求 32所述的用量监测系统， 其中： 所述 TDF还设置成： 在所述监测键的用量达到用量阔值、 包含所述监测键的所有应用检测和 控制（ ADC )规则被删除或去激活或所述 PCRF显式请求所述 TDF上报所述 监测键的用量时， 向所述 PCRF上报所述监测键的用量报告。
34、 一种用量监测系统， 包括： 策略执行功能实体和策略和计费规则功 能实体（PCRF ) ， 其中：
所述策略执行功能实体设置成： 向所述 PCRF上报用户的监测键的用量 报告；
所述 PCRF设置成： 当所述监测键为不需累计入会话级别的业务或应用 对应的监测键时， 对所述会话级别的总允许用量进行更新， 更新后的总允许 用量等于原总允许用量加上所述不需累计入所述会话级别的业务或应用对应 的监测键的用量报告值。
35、 如权利要求 34所述的用量监测系统， 其中： 所述策略执行功能实体 还设置成：
在所述监测键的用量达到用量阔值、 包含所述监测键的所有规则被删除 或去激活或所述 PCRF显式请求所述策略执行功能实体上报所述监测键的用 量时， 向所述 PCRF上报所述监测键的用量报告。
36、 如权利要求 34或 35所述的用量监测系统， 其中：
所述策略执行功能实体为策略和计费执行功能实体（ PCEF ) , 所述会话 为 IP连接接入网（IP-CAN )会话， 所述规则为策略和计费控制（PCC )规则。
37、 如权利要求 34或 35所述的用量监测系统， 其中：
所述策略执行功能实体为业务检测功能（ TDF ) , 所述会话为 TDF会话， 所述规则为应用检测和控制 （ADC )规则。
PCT/CN2011/079275 2010-09-27 2011-09-02 一种用量监测方法及系统 WO2012041149A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010295973.4 2010-09-27
CN201010295973.4A CN102421106B (zh) 2010-09-27 2010-09-27 一种用量监测方法及系统

Publications (1)

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

Family

ID=45891912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079275 WO2012041149A1 (zh) 2010-09-27 2011-09-02 一种用量监测方法及系统

Country Status (2)

Country Link
CN (1) CN102421106B (zh)
WO (1) WO2012041149A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3104550A1 (en) * 2015-06-10 2016-12-14 Sap Se Mobile digital cellular telecommunication system with advanced functionality for rating correction
CN107295539A (zh) * 2016-03-30 2017-10-24 中国移动通信集团江苏有限公司 一种上网流量使用情况推送方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130326076A1 (en) * 2012-05-29 2013-12-05 Alcatel-Lucent Canada Inc. Per flow and per session metering limit application

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166101A (zh) * 2007-09-25 2008-04-23 中兴通讯股份有限公司 由用户签约信息更新实时触发网络会话交互的方法
WO2009047065A2 (en) * 2007-10-08 2009-04-16 Nokia Siemens Networks Oy Methods, apparatuses, system, and related computer program product for policy control
CN101610492A (zh) * 2008-06-16 2009-12-23 华为技术有限公司 会话处理的方法、服务网关和v-pcrf实体
KR20100050016A (ko) * 2008-11-04 2010-05-13 주식회사 케이티 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
CN101730048A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 一种信息传输方法及系统
CN101730174A (zh) * 2009-05-08 2010-06-09 中兴通讯股份有限公司 演进的分组系统中实现跨系统切换的方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1146188C (zh) * 2001-08-13 2004-04-14 华为技术有限公司 因特网接入服务器的选择性计费方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101166101A (zh) * 2007-09-25 2008-04-23 中兴通讯股份有限公司 由用户签约信息更新实时触发网络会话交互的方法
WO2009047065A2 (en) * 2007-10-08 2009-04-16 Nokia Siemens Networks Oy Methods, apparatuses, system, and related computer program product for policy control
CN101610492A (zh) * 2008-06-16 2009-12-23 华为技术有限公司 会话处理的方法、服务网关和v-pcrf实体
KR20100050016A (ko) * 2008-11-04 2010-05-13 주식회사 케이티 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
CN101730174A (zh) * 2009-05-08 2010-06-09 中兴通讯股份有限公司 演进的分组系统中实现跨系统切换的方法及系统
CN101730048A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 一种信息传输方法及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3104550A1 (en) * 2015-06-10 2016-12-14 Sap Se Mobile digital cellular telecommunication system with advanced functionality for rating correction
US9838862B2 (en) 2015-06-10 2017-12-05 Sap Se Mobile digital cellular telecommunication system with advanced functionality for rating correction
CN107295539A (zh) * 2016-03-30 2017-10-24 中国移动通信集团江苏有限公司 一种上网流量使用情况推送方法及装置

Also Published As

Publication number Publication date
CN102421106B (zh) 2016-05-11
CN102421106A (zh) 2012-04-18

Similar Documents

Publication Publication Date Title
EP2702727B1 (en) Method and device for controlling qos and/or policy and charging control of a guest user
EP2493222B1 (en) Method and system for implementing usage monitoring control
US9191960B2 (en) Methods and apparatus for mitigating service interruption
US20140136378A1 (en) Method and apparatus for controlling service traffic in a communication network
EP2566197A1 (en) Policy application method for machine type communication and policy and charging enforcement function
WO2011060698A1 (zh) 一种实现用量监测控制的方法及系统
US8661145B2 (en) Method and system for transmitting a bearer control mode in roaming scenarios
KR20150047594A (ko) 무선 액세스 네트워크들(ran)에 대한 혼잡 제어
WO2012083795A1 (zh) 业务控制方法、装置及系统
WO2011020498A1 (en) Method, apparatus and computer program for enforcing policy across associated sessions taking into account a total usage quota for associated user
KR101884048B1 (ko) 네트워크 자원들을 관리하기 위한 방법들과 노드들, 및 상응하는 시스템과 컴퓨터 프로그램
WO2010091635A1 (zh) 一种策略的控制方法、装置
CN106304195B (zh) 第三方应用的策略控制方法、scef和pcrf
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及系统
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2015143851A1 (zh) 用量监控方法、装置和系统
CN102547854B (zh) 策略控制方法及装置
WO2018076974A1 (zh) 一种策略控制方法、装置及系统
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
WO2012071956A1 (zh) 漫游场景支持被赞助数据连接的方法、系统和装置
US11223492B2 (en) Wireless communication method and device
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
WO2012041149A1 (zh) 一种用量监测方法及系统
WO2012041150A1 (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: 11828045

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: 11828045

Country of ref document: EP

Kind code of ref document: A1