WO2012103770A1 - Usage monitoring method and system supporting traffic detection function - Google Patents

Usage monitoring method and system supporting traffic detection function Download PDF

Info

Publication number
WO2012103770A1
WO2012103770A1 PCT/CN2011/084358 CN2011084358W WO2012103770A1 WO 2012103770 A1 WO2012103770 A1 WO 2012103770A1 CN 2011084358 W CN2011084358 W CN 2011084358W WO 2012103770 A1 WO2012103770 A1 WO 2012103770A1
Authority
WO
WIPO (PCT)
Prior art keywords
usage
tdf
pcrf
monitoring
pcef
Prior art date
Application number
PCT/CN2011/084358
Other languages
French (fr)
Chinese (zh)
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 WO2012103770A1 publication Critical patent/WO2012103770A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • H04L12/1407Policy-and-charging control [PCC] architecture
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66Policy and charging system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5029Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/02Capturing of monitoring data
    • H04L43/028Capturing of monitoring data by filtering

Definitions

  • the present invention relates to the field of policy and charging control technologies for mobile communications, and in particular, to a method and system for monitoring usage of a traffic detection function (TDF).
  • TDF traffic detection function
  • PCC Policy and Charging Control
  • the PCC architecture is a functional framework that can be applied to multiple access technologies.
  • the PCC architecture can be applied to the UMTS Terrestrial Radio Access Network (UMTS, Universal Mobile Telecommunications System).
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • GSM Global System for Mobile Communication
  • GSM GSM
  • GSM Enhanced Data Rate for GSM Evolution
  • I-WLAN Interworking WLAN
  • EPS Evolved Packets System
  • FIG. 1 is a schematic diagram of a non-roaming composition architecture of a PCC of the existing Rel-11. The following describes the logical function entities and their interface functions in the PCC architecture shown in FIG. 1. As shown in Figure 1:
  • the Service 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 transmitting service information related to the policy and charging rule function (PCRF, Policy and Charging Rules Function ) 0 if the service information consistent with the policy of the PCRF, the PCRF accepts the negotiation; Otherwise, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback.
  • the AF can then return these parameters to the user equipment (UE, User Equipment) caravan where the interface between the AF and the PCRF is the Rx interface.
  • PCRF Policy and Charging Rules Function
  • 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 policy and charging rules to the Policy and Control Enforcement Function (PCEF).
  • PCEF Policy and Control Enforcement Function
  • the basis for the PCRF to formulate policies and charging rules includes: business-related information obtained from AF, and user policy charging control related to policy control and charging obtained from a user subscription database (SPR, Subscription Profile Repository) Information, and information about the bearer-related network obtained from the PCEF through the Gx interface.
  • SPR User subscription database
  • 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 side.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then performs the policy and charging rule defined by the PCRF for the service data flow; when the bearer is established, the PCEF performs the rule according to the PCRF.
  • Resource allocation, and threshold control according to the information provided by the AF; at the same time, the PCEF triggers reporting of events occurring on the bearer network according to the event subscribed by the PCRF; according to the charging rule sent by the PCRF, the PCEF performs corresponding service data flow charging operation,
  • the fee can be either online or offline.
  • the PCEF In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS); when offline charging, the relevant calculation between the PCEF and the Offline Charging System (OFCS) Fee information.
  • OCS Online Charging System
  • OFCS Offline Charging System
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the PCEF and the OCS is a Gy interface
  • the interface between the PCEF and the OFCS is a Gz interface. It also enhances the PCEF function to implement flow detection and integrates PCEF with TDF.
  • the PCEF can perform application detection and policy enforcement (such as threshold control, redirection, and bandwidth limitation) according to the local configuration or PCC rules that are sent by the PCRF and include Application Detection and Control (ADC).
  • ADC Application Detection and Control
  • the PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the packet in the I-WLAN.
  • PDN-GW Packet Data Network Gateway
  • GGSN GPRS Gateway Support Node
  • GPRS General Packet Radio Service
  • I-WLAN I-WLAN.
  • Data Gateway Packet Data Gateway
  • the TDF can also be deployed independently.
  • the TDF interacts with the PCRF through the Sd interface.
  • the TDF can perform application detection and policy execution according to the application detection control rules delivered by the pre-configuration or PCRF.
  • the PCRF provides detection control rules for independent TDF, and the policy control operations of independent TDF include threshold control, redirection, and bandwidth limitation.
  • the TDF reports the related events and information of the detected service/flow to the PCRF (for example, reports the start and end of the detected service/flow to the PCRF), and sends a description of the service data flow to the PCRF, and transmits the flow detection from the PCRF. Signaling for service detection and policy rules.
  • TDF exists in two modes: request service report and active service report: request service report mode, PCRF will inform TDF which services need to be detected and TDF reports to PCRF; active service report mode, which services are pre-configured in TDF for detection and reporting, This approach assumes that the user agrees that no request is required and executable.
  • the Bearer Binding and Event Reporting Function is usually located in the Access Network Gateway.
  • the Serving Gateway S-GW
  • the Packet Data Gateway P-GW
  • BBERF Internet Protocol version 6
  • PMIPv6 Proxy Mobile Internet Protocol version 6
  • BBERF exists in the S-GW.
  • the BBERF also exists in the trusted non-3GPP access gateway.
  • the SPR stores user policy charging control subscription information related to policy control and charging.
  • the interface between SPR and PCRF is the Sp interface.
  • OCS and PCEF jointly complete the control and management of user credit under online charging mode.
  • the OFCS and the PCEF jointly perform the charging operation in the offline charging mode.
  • the above PCC architecture implements policy charging control for IP-CAN (IP-Connected Access Network) sessions established by the UE to access a packet data network (PDN) through various functional entities.
  • IP-CAN IP-Connected 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 business data stream, a set of business data streams, or a
  • 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 an IP-CAN session
  • the PCEF will all of the IP-CAN session.
  • the usage of the traffic data is accumulated in the usage corresponding to the monitoring key.
  • the threshold is reached, the IP-CAN session is terminated, or the PCRF request is reported, the PCEF reports the usage to the PCRF and uses the Monitoring Key to identify the reported usage.
  • the PCRF When 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. After the PCC rules are installed on the PCEF, the usage of the service data flow matching the Service Data Flow Template in the PCC rule is accumulated in the usage corresponding to the Monitoring Key. When the threshold is reached, or the same Monitoring Key is included. When the last PCC rule is deactivated, or when the IP-CAN session is terminated, or when the PCRF request is reported, the PCEF reports the usage to the PCRF, and uses the Monitoring Key to identify the reported usage.
  • the service data flow template is also referred to as a service data flow description, which is not described below.
  • the total allowed amount of a user's PDN can be saved in the SPR, that is, the total allowable amount of all service flows for an IP-CAN session, or the total allowable amount per user per PDN.
  • the SPR can also store the total allowed usage of certain services of 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.
  • the PCEF When the PCEF detects that the usage has reached the threshold, the IP-CAN session is terminated, all PCC rules containing a Monitoring Key are deleted, or the PCRF explicitly requests the usage report, the PCEF will report to the PCRF the usage of the relevant Monitoring Key since the last report. Consumption situation. 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 reports the usage of a Monitoring Key and needs to continue monitoring, 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. When the last IP-CAN session of an APN of the user is terminated, the PCRF will save the remaining total allowed amount in the SPR, including the total allowed amount of the PDN or the total allowed amount of some specific services of the PDN.
  • the PCRF needs to include a Monitoring Key in the PCC rule corresponding to the service data flow, and the PCC rule includes the The service data flow template corresponding to the service data flow.
  • the PCEF accumulates the usage of the service data flow matching the service data flow template in the PCC rule to the usage amount corresponding to the Monitoring Key, thereby implementing the usage monitoring control.
  • multiple PCC rules share a Monitoring Key, the usage of the service data stream matching the service data flow template of the multiple PCC rules is accumulated to the usage corresponding to the Monitoring Key.
  • the PCRF can obtain a business data flow template.
  • the TDF can report the detected application (the application ID is identified by the Application ID) to the PCRF.
  • the PCEF does not report the service data flow template corresponding to the application at any time.
  • the TDF When the TDF is deployed independently, the TDF may not be able to report the service data flow template corresponding to the detected application. In this case, the PCRF cannot send the PCC rule containing the service data flow template to the PCEF, so that the usage monitoring control for the application cannot be implemented. .
  • the TDF When the existing usage monitoring control is for the entire IP-CAN session, if a separate TDF is deployed, the TDF will combine the measurement provided by the PCRF because there may be applications or data streams in the IP-CAN session that cannot be detected and reported by the TDF. And the local policy performs corresponding gating or bandwidth limitation on the application or the data flow (that is, when the bandwidth exceeds the limit, packet loss is performed), and for this type of data flow, the PCEF IP-CAN level (level) usage monitoring processing The usage statistics have been made, but they are actually blocked or redirected after passing through the TDF. This part should not be included in the actual usage. This will result in a cumulative amount of PCEF usage that is inconsistent with the user's final use.
  • the usage monitoring control of the service data flow level cannot be performed.
  • the IP-CAN level usage monitoring function when the IP-CAN level usage monitoring function is executed, there is a problem that the reported usage amount and the actual usage amount are inconsistent, and the IP-CAN level usage monitoring function cannot be accurately performed. It can be seen that how to implement the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain, and the IP-CAN level usage detection control under the TDF architecture have become an urgent problem to be solved in the current usage monitoring technology.
  • the main object of the present invention is to provide a method and system for monitoring the usage of TDF, which can realize the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain, and the TDF architecture. IP-CAN level usage detection control.
  • a usage monitoring method supporting flow detection function including: Policy Control and Charging Rules Function Entity (PCRF) to Integrated Flow Detection Function (TDF) Policy and Charging Execution Function Entity (PCEF), or PCEF and independent TDF Or the independent TDF delivers the corresponding usage monitoring policy; the integrated TDF PCEF, or the PCEF and the independent TDF, or the independent TDF performs usage monitoring according to the usage monitoring policy.
  • PCRF Policy Control and Charging Rules Function Entity
  • TDF Integrated Flow Detection Function
  • PCEF Policy and Charging Execution Function Entity
  • independent TDF delivers the corresponding usage monitoring policy
  • the usage monitoring policy specifically includes any one or a combination of at least one of the following: setting a monitoring key; setting an application identifier; setting an event trigger for triggering a monitoring key or an application identifier; and setting a usage threshold.
  • the value of the event trigger specifically includes: usage reporting ( Usage_Report ); the usage threshold is less than or equal to the application-related total allowed usage.
  • a usage monitoring system supporting a flow detection function comprising: a usage monitoring unit, configured to apply a corresponding usage monitoring strategy to a PCRF to a PCEF integrated with TDF, or a PCEF and a separate TDF, or a separate TDF
  • the integrated TDF's PCEF, or the PCEF and the independent TDF, or the independent TDF perform usage monitoring based on the usage monitoring policy.
  • the usage monitoring policy specifically includes any one or a combination of at least one of the following: setting a monitoring key; setting an application identifier; setting an event trigger for triggering a monitoring key or an application identifier; and setting a usage threshold.
  • a usage monitoring method supporting a flow detection function comprising:
  • the PCEF monitors the IP-CAN level usage.
  • the TDF monitors and collects the discarding usage, and reports the discarded discarding amount to the PCRF.
  • the PCRF corrects the error of the IP-CAN level usage reported by the PCEF according to the discarding amount reported by the TDF;
  • the PCEF does not monitor the IP-CAN level usage
  • the TDF monitors the IP-CAN level usage and reports the usage amount to the PCRF.
  • the type of the discarding amount specifically includes: a time, and/or a flow rate, and/or an event; and the type of the reporting threshold value corresponding to the amount of the discarded TDF reporting discarding amount includes: a reporting threshold of the time, and/or reporting of the flow rate Threshold value for thresholds, and/or events.
  • the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the used amount.
  • the method further includes: triggering the TDF to report the discarded usage amount to the PCRF; and the triggered TDF reporting the discarded usage amount to the PCRF specifically includes:
  • the TDF reports the discarding amount to the PCRF
  • the PCRF finds that when the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops, the PCRF first And sending, by the TDF, the reporting of the discarding amount, and the TDF reporting the discarding amount to the PCRF; or, when the IP-CAN session ends, the TDF reports the discarding amount to the PCRF.
  • the usage threshold value includes: a threshold pre-configured by the TDF, or a threshold sent by the PCRF to the TDF; and when the threshold pre-configured by the TDF and the threshold sent by the PCRF to the TDF are simultaneously When present, it is preferred to use the threshold that is issued by the PCRF to the TDF.
  • a usage monitoring system supporting a flow detection function in which an IP-CAN level usage monitoring is performed under an independent TDF architecture, the system includes: a usage monitoring unit and a usage correction unit;
  • the usage monitoring unit is configured to monitor the IP-CAN level usage by the PCEF;
  • the usage correction unit is configured to monitor and collect the discarded usage amount by the TDF, and report the discarded usage amount to the PCRF; the PCRF corrects the error of the IP-CAN level used by the PCEF according to the discarded usage reported by the TDF;
  • the system includes: a usage monitoring unit, wherein when the PCEF does not monitor the IP-CAN level usage, the TDF monitors the IP-CAN level usage and Report the dosage to the PCRF.
  • the type of the discarding amount specifically includes: a time, and/or a flow rate, and/or an event; and the type of the reporting threshold value corresponding to the amount of the discarded TDF reporting discarding amount includes: a reporting threshold of the time, and/or reporting of the flow rate Threshold value for thresholds, and/or events.
  • the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the used amount.
  • the system further includes: a triggering and reporting unit, used in the IP-CAN session process, when the usage is reached When the threshold is reported, the amount of the TDF is triggered to be reported, and the TDF reports the discarded amount to the PCRF;
  • the PCRF finds that the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops triggering the TDF.
  • the PCRF first sends an indication to the TDF to obtain the discarded usage amount, and the TDF reports the discarded usage amount to the PCRF.
  • the usage of the TDF is triggered, and the TDF reports the discarding amount to the PCRF.
  • a set of solutions of the present invention is: PCRF applies a corresponding usage monitoring strategy to PCEF integrated with TDF, or PCEF and independent TDF, or independent TDF; PCEF integrated with TDF, or PCEF and independent TDF, or independent TDF performs usage monitoring based on the usage monitoring strategy. Therefore, it is possible to solve the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain during the usage monitoring.
  • One of the other solutions of the present invention is: When the IP-CAN level usage monitoring is performed under the independent TDF architecture, the PCEF monitors the IP-CAN level usage, and the TDF monitors and counts the discarded usage, which will be statistically The discarding amount is reported to the PCRF.
  • FIG. 1 is a schematic diagram of a system architecture of a PCC in a non-roaming scenario using SPR in the prior art
  • FIG. 2 is a schematic flowchart of a PCEF integrated TDF and a request reporting mode according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic flowchart of an independent TDF and a request reporting mode according to Embodiment 2 of the present invention
  • FIG. 4 is a schematic flowchart of a PCEF integrated TDF and an unsolicited reporting mode according to Embodiment 3 of the present invention
  • FIG. 5 is a schematic flowchart of an independent TDF and an unsolicited reporting mode according to Embodiment 4 of the present invention
  • FIG. 6 is a schematic flowchart of performing usage monitoring during session creation according to Embodiment 5 of the present invention.
  • FIG. 7 is a schematic flowchart of a discarding usage reporting process when a TDF threshold arrives according to the first application example of the present invention
  • FIG. 8 is a schematic diagram of a process for obtaining a TDF discarding amount by a PCRF according to the second application example of the present invention.
  • FIG. 9 is a schematic flowchart of TDF reporting discarding usage at the end of a session in the third application example of the present invention.
  • DETAILED DESCRIPTION OF THE INVENTION The method for monitoring the amount of the flow detection function of the present invention includes two sets of solutions. Explained separately below.
  • the first solution is based on the usage monitoring control of the application, which can solve the usage monitoring and control of the service data flow level when the PCRF cannot obtain the service data flow template (ie, the service flow description).
  • This method mainly includes the following:
  • the PCRF sends the application corresponding usage monitoring control strategy to the application detection and control entity; the application detection and control entity performs the usage monitoring according to the usage monitoring control strategy.
  • the application detection and control entity is a PCEF or a separate TDF integrated with the TDF
  • the usage monitoring performed and executed includes the following three situations: 1) the PCRF delivers a corresponding usage monitoring strategy to the PCEF integrated with the TDF; The PCEF that integrates the TDF performs the usage monitoring according to the usage monitoring policy; 2) the PCRF sends the corresponding usage monitoring strategy to the PCEF and the independent TDF respectively; the PCEF and the independent TDF are monitored according to the usage.
  • the policy performs usage monitoring; 3) The PCRF sends a corresponding usage monitoring policy to the independent TDF; the independent TDF performs usage monitoring according to the usage monitoring policy.
  • the usage monitoring control strategy includes: setting a monitoring key; setting an application ID; setting an event trigger for triggering a Monitoring Key or an Application ID; and setting a usage threshold (Usage Threshold).
  • the second solution is to solve the IP-CAN level usage monitoring function under the TDF architecture, including the following method 1 and method 2, which are different solutions in the implementation of the IP-CAN level usage monitoring scenario under the independent TDF architecture. , respectively, as explained below.
  • IP-CAN level usage monitoring When the IP-CAN level usage monitoring is performed under the independent TDF architecture, the IP-CAN level usage monitoring is performed on the PCEF, and the discarding amount is reported on the TDF and reported to the PCRF for correcting the usage error of the PCEF report.
  • IP-CAN level usage monitoring function The method mainly includes the following contents:
  • the TDF collects the discarding usage of the IP-CAN session, and reports the discarded discarding amount to the PCRF.
  • the PCRF corrects the error of the PCEF reporting usage according to the discarding amount of the statistics.
  • the type of the discarding amount includes: time, and/or flow rate, and/or an event; the type of the corresponding triggered usage threshold value includes: a time reporting threshold, and/or a flow reporting threshold, and/or Or the reported threshold of the event.
  • the discarding amount is: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the PCEF The amount of the IP-CAN level usage monitoring function has been counted. In this method, the PCEF can perform the IP-CAN level usage detection function according to the prior art.
  • the timing of triggering the TDF to report the discarded discarding amount to the PCRF includes: 1. During the IP-CAN session, when the usage reporting threshold (such as the reporting threshold of time or traffic) arrives, the TDF reports the discarding amount to the PCRF. 2. During the IP-CAN session, the PCRF finds that the usage threshold of the UE's usage monitoring has reached the threshold and the IP-CAN level usage monitoring, or the IP-CAN level usage monitoring function stops, the PCRF sends to the TDF. Obtaining the discarding usage report, the TDF reports the discarding usage amount to the PCRF. 3. When the IP-CAN session ends, the TDF reports the discarding usage amount to the PCRF.
  • the usage reporting threshold such as the reporting threshold of time or traffic
  • the corresponding usage thresholds are the thresholds of the TDF pre-configured, or the PCRF is sent to the TDF. . If the two thresholds of the TDF pre-configured threshold and the threshold for the TDF are sent to the TDF, the priority is processed according to the carrier policy. If the operator does not have the relevant priority policy, the threshold issued by the PCRF takes precedence over the TDF pre- Configure the threshold.
  • the PCRF may decide whether to continue to perform subsequent usage monitoring according to the operator policy (for example, if the usage threshold is exhausted, if the PCRF needs to continue to perform the monitoring function, and the TDF reports the discarded usage amount. If it is enough, you can continue to issue the usage monitoring function.
  • Method 2 When performing IP-CAN level usage monitoring under the independent TDF architecture, the IP-CAN level usage monitoring is not performed on the PCEF.
  • the PCRF sends the IP-CAN level monitoring policy to the TDF, and the TDF executes and reports the IP- The amount of CAN session is given to the PCRF to implement the IP-CAN level usage monitoring function.
  • the invention is illustrated by way of example below.
  • Embodiment 1 The PCEF integrates the TDF, and the TDF uses the request reporting mode.
  • FIG. 2 is a flowchart of a method for monitoring usage according to Embodiment 1 of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step 201 In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN.
  • the session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
  • Step 202 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 (IP Address) allocated to the UE in the IP-CAN session establishment indication message.
  • IP Address IP Address
  • Step 203 The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 204 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier.
  • the user subscription information includes a user document configuration that indicates activation of application detection and control.
  • the user subscription information may also include Total Allowed Usage (TAU), which indicates the total allowable amount of each application monitored by the user for the required usage.
  • TAU Total Allowed Usage
  • Step 205 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE.
  • This step development strategy includes the development of PCC rules and event triggers. Since the user subscription information includes the user document configuration, the detection control policy needs to be applied in the PCC rule.
  • the application detection control includes setting an Application ID, where the Application ID indicates an application that the PCEF needs to detect; setting an event trigger, and the value is a Start of application traffic detection and a Stop of application traffic detection; And setting possible execution policies corresponding to each detected application, including threshold control, maximum bandwidth, and redirection strategy.
  • Step 206 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
  • the PCC rule carries the Application ID and possible execution policies.
  • the event trigger takes at least Start of application traffic detection and Stop of application traffic detection.
  • Step 207 The PCEF installation policy includes an application detection policy and an event trigger.
  • the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
  • Step 208 The PCEF executes the policy, including executing an application detection policy, and detecting an application corresponding to the Application ID included in the PCC rule.
  • Step 209 The PCEF detects the application corresponding to the Application ID.
  • the PCEF sends an IP-CAN session modification indication to the PCRF, carrying the detected Application ID and the event trigger, and the value is Start of application traffic detection.
  • multiple Application IDs can share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage corresponding to one Monitoring Key.
  • Step 212 The PCEF executes the policy, including the usage monitoring control policy, and installs the event trigger Usage_Report.
  • the PCEF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
  • the PCRF includes a Monitoring Key in the PCC rule, and simultaneously delivers the UT corresponding to the Monitoring Key.
  • the PCEF detects the application corresponding to the application ID according to the ADC rule, and performs the usage monitoring according to the usage detection policy delivered in step 206, the usage monitoring strategy is not required in step 211.
  • Embodiment 2 The TDF is deployed independently, and the TDF uses the request reporting mode.
  • FIG. 3 is a flowchart of a method for monitoring usage according to Embodiment 2 of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step 301 In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, and carries the user identifier and the requested PDN in the IP-CAN session establishment request message. PDN identifier.
  • Step 302 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 allocated to the UE in the IP-CAN session establishment indication message.
  • Step 303 The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 304 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier.
  • the user subscription information includes a user document configuration that indicates activation of application detection and control.
  • the user subscription information may also include an application-related TAU, which indicates the total allowable amount of each application monitored by the user for the required amount of subscription.
  • Step 305 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger. Since the user subscription information includes the user document configuration, the PCRF also needs to formulate an ADC rule, where the ADC rule includes setting the Application ID, where the Application ID indicates the application that the PCEF needs to detect; setting the event trigger, the value is Start of application traffic detection and Stop of application traffic detection; and setting possible execution policies for each detected application, including threshold control, maximum bandwidth, and redirection.
  • the PCRF update rule is processed (as described in step 313).
  • Step 306 The PCRF sends a TDF session establishment request to the TDF, carries an ADC rule and an event trigger, and takes values of Start of application traffic detection and Stop of application traffic detection, and/or carries a related monitoring key.
  • Step 307 TDF executes the policy, installs or activates the ADC rules and event triggers.
  • Step 308 The TDF returns an acknowledgement message to the PCRF.
  • Step 309 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
  • Step 310 PCEF installation policy.
  • the gateway where the PCEF is located returns an IP-CAN session establishment response, and carries an IP address in the IP-CAN session establishment response.
  • Step 311 The TDF detects an application corresponding to the Application ID.
  • the TDF sends a service detection report to the PCRF, carrying the detected Application ID and event trigger, and the value is Start of application traffic detection.
  • Step 312 the PCRF performs policy decision and updates the ADC rule.
  • Step 313 The PCRF returns an acknowledgement message to the TDF, where the message carries the updated ADC rule and the UT corresponding to the Monitoring Key.
  • the ADC rule contains a Monitoring Key corresponding to the Applcation ID.
  • multiple Application IDs can share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage corresponding to one Monitoring Key.
  • Step 314 the TDF execution policy, including the usage monitoring control policy, and the event trigger Usage_Report.
  • the TDF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
  • the PCRF includes the Monitoring Key in the ADC rule and simultaneously delivers the UT corresponding to the Monitoring Key.
  • the usage monitoring strategy is not required in step 313.
  • Embodiment 3 The PCEF integrates the TDF function, and the TDF uses the unrequested reporting mode.
  • FIG. 4 is a flowchart of a method for monitoring usage according to an embodiment of the present invention. As shown in FIG.
  • Step 401 In a process in which the UE requests to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-
  • the CAN session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
  • Step 402 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 allocated for the UE in the IP-CAN session establishment indication message.
  • Step 403 The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 404 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier.
  • the user subscription information may also include an application-related TAU, which indicates the total allowed usage of each application monitored by the user for the required usage.
  • Step 405 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE. This includes making PCC rules and event triggers.
  • Step 406 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
  • Step 407 The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
  • Step 408 Since the PCEF integrates the TDF function, and the TDF uses the unrequested reporting mode, the PCEF performs application detection according to the pre-configured application detection policy.
  • the pre-configured application detection policy includes at least an application ID corresponding to the application to be detected. If the application needs to perform usage monitoring, the application also has a corresponding Monitoring Key.
  • Step 409 The PCEF detects the application specified in the pre-configured application detection policy (identified by the Application ID;). The PCEF sends an IP-CAN session modification indication to the PCRF, carrying the detected Application ID and the event trigger, and the value is Start of application traffic detection.
  • Step 411 The PCRF returns an IP-CAN session modification confirmation message to the PCEF, where the message carries the Application.
  • the application detection policy pre-configured in the PCEF may be that multiple Application IDs share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage amount corresponding to one Monitoring Key.
  • Step 412 The PCEF executes the policy, including the usage monitoring control policy, and installs the event trigger Usage_Report.
  • the PCEF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
  • Embodiment 4 The TDF is deployed independently, and the TDF uses the unsolicited reporting mode.
  • FIG. 5 is a flowchart of a method for monitoring usage according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps: Step 501: In a process in which the UE requests to establish an IP-CAN session, the gateway where the PCEF is located receives the IP- The CAN session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
  • Step 502 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 allocated to the UE in the IP-CAN session establishment indication message.
  • Step 503 The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 504 The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier.
  • the user subscription information may also include an application-related TAU, which indicates the total allowed usage of each application monitored by the user for the required usage.
  • Step 505 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger.
  • Step 506 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
  • the monitoring key associated with the application sent by the PCRF to the TDF may be included; or the usage of the IP-CAN level on the TDF monitors the monitoring key of the corresponding command layer.
  • These application or command-related monitoring keys can be included in the ADC rules, or they can be sent out with the rules in addition to the ADC rules, or sent by the PCRF update rule after subsequent applications detect and report them (such as steps). 512 and step 513).
  • Step 507 The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
  • the UE can perform service access.
  • Step 508 When the TDF detects the data stream flowing through it, and finds that the IP address is a new address, the TDF sends a TDF session to the PCRF, and the message carries the IP address.
  • the PCRF associates the TDF session with the IP-CAN session according to the IP address.
  • the PCRF returns a message to the TDF.
  • the TDF performs application detection and control according to pre-configured ADC rules.
  • the ADC rule includes at least the Application ID corresponding to the application to be detected. If the application needs to perform usage monitoring, the application also has a corresponding Monitoring Key.
  • Step 511 The TDF detects the application specified in the pre-configured application detection policy (identified by the Application ID;). The TDF sends a service detection report to the PCRF, and carries the detected Application ID and event trigger. The value is Start of application traffic detection.
  • Step 512 the PCRF makes a policy decision. If the PCRF obtains the TAU of the application in step 504 or the PCRF configures the TAU for the application, the PCRF formulates a usage monitoring policy for the application, including: setting an event trigger, taking the value of Usage_Report, and setting the pre-configured The UT corresponding to the Monitoring Key, in step 513, the PCRF returns an acknowledgement message to the TDF, where the message carries the UT corresponding to the Application ID and the Monitoring Key.
  • the application detection policy pre-configured in the TDF may be that multiple Application IDs share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage amount corresponding to one Monitoring Key.
  • Step 514 the TDF execution policy, including the usage monitoring control policy, and the event trigger Usage_Report.
  • the TDF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
  • the PCEF when the IP-CAN level usage monitoring is performed under the independent TDF architecture in Method 2, the PCEF does not monitor the IP-CAN level usage, and the TDF monitors the IP-CAN level usage and reports the usage to the PCRF.
  • the IP-CAN level usage monitoring is implemented on the independent TDF, and is applicable to the process descriptions and functions of the foregoing Embodiment 2 and Embodiment 4, and is not repeatedly described herein.
  • the PCRF is sent to the monitoring key of the TDF corresponding to the IP-CAN level.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the embodiment of the present invention describes the process of setting the usage threshold to the PCEF during the IP-CAN session.
  • the TDF collects and reports the discarding usage and performs the usage monitoring process.
  • the PCRF needs to send the discarding usage monitoring indication to the TDF, and the TDF performs the monitoring and reporting of the discarding amount.
  • Figure 6 it mainly includes the following steps:
  • Step 601 In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, and carries the user identifier and the requested PDN in the IP-CAN session establishment request message. PDN identifier.
  • Step 602 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 allocated for the UE in the IP-CAN session establishment indication message. If the TDF is in the request reporting mode, the IP address of the TDF is brought to the PCRF.
  • Step 603 The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 604 The SPR returns the subscription information of the user according to the user identifier and the PDN identifier, including the TAU of the user, and indicates that the total allowed usage of each application monitored by the user for the required subscription amount is sent to the PCRF. If the TDF is the request reporting mode, the SPR carries a user document configuration in the response indicating whether the IP-CAN session can perform the ADC function.
  • Step 605 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger. If the user's subscription information includes user documentation configuration, the PCRF also needs to develop ADC rules.
  • Step 606 The PCRF sends a TDF session creation request to the TDF, and provides an ADC rule request to create a TDF session. If the IP-CAN session performs the usage monitoring function of the IP-CAN level, the IP-CAN level discarding usage monitoring indication is simultaneously sent to the TDF. Optionally, the PCRF carries a reporting threshold of the discarding amount (e.g., a reporting threshold of time or traffic) to the TDF.
  • a reporting threshold of the discarding amount e.g., a reporting threshold of time or traffic
  • Step 607 The TDF returns a session creation response message to the PCRF to perform usage monitoring of the discarded data. If the PCRF provides the ADC rule, execute the policy, install or activate the ADC rule and the event trigger.
  • Step 608 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carries the PCC rule and the event trigger, carries the usage threshold of the IP-CAN session, and the PCEF starts to perform the usage monitoring.
  • Step 609 the PCEF executes the policy, installs or activates the PCC rule, and performs the usage monitoring.
  • the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
  • the PCEF and the TDF monitor the usage of the IP-CAN session established by the UE according to the usage monitoring policy delivered by the PCRF.
  • the TDF will report the discarding traffic statistics of the IP-CAN level to the TDF.
  • Application Example 1 During the session, when the time or traffic threshold is reached, the TDF reports the discarding amount to the PCRF. When the reported threshold for the usage (time, flow, or event) of the TDF arrives, the TDF sends a request message to the PCRF to report the IP-CANlevel discard amount counted since the last report. As shown in Figure 7, this example mainly includes the following steps:
  • Step 701 The TDF detects that the discarding amount of the IP-CAN level reaches a time or flow or an event report. Threshold (TDF pre-configuration, or reporting threshold sent by the PCRF) triggers the reporting process of discarding usage.
  • Step 702 The TDF sends a request message to the PCRF to report the discarded usage of the IP-CAN level since the last report.
  • Step 703 The PCRF modifies the relevant PCC rule and/or the ADC rule according to the discarding amount reported by the TDF, and sends a response message to the TDF. If there is an update, the response message carries the modified ADC rule. If there is a PCC rule update, the PCRF will initiate a subsequent IP-CAN session modification process according to the prior art.
  • Step 704 If the monitoring of the usage of the IP-CAN level continues, the TDF repeats the steps 701-703 according to the time, and/or the traffic, and/or the event threshold that the pre-configured or PCRF sends in the response message. Continue to perform the usage monitoring and reporting process for discarding usage.
  • Application example 2 The PCRF finds that the threshold of the usage monitoring of the UE arrives and the usage of the IP-CAN level is monitored, or the monitoring function of the IP-CAN level is stopped, and the PCRF sends an indication of the discarding usage report to the TDF, and the TDF goes to The discarded amount of statistics is reported by the PCRF.
  • the PCRF finds that the UE has the IP-CAN level usage monitoring and the usage monitoring threshold is reached, or the IP-CAN level usage monitoring function is stopped, or the externally triggered UE threshold is changed, and the PCRF sends the discard to the TDF.
  • the usage report of the usage triggers the TDF to report the discarded usage amount to the PCRF.
  • Step 801 There is an IP-CAN level usage monitoring, and the PCRF is internally or externally triggered during the session (for example, the usage monitoring and the usage monitoring threshold arrives, or the usage monitoring function is stopped, or the SPR subscription threshold is changed, etc.), and needs to be obtained.
  • the current TDF discards the traffic to facilitate the proofreading of the actual usage, which triggers the process of obtaining the discarding usage.
  • Step 802 The PCRF sends a request message to the TDF, where the message carries a drop usage indication, and requests the TDF to report the discarded usage amount to the PCRF. If there is an ADC rule modification, the updated rule will be provided to the TDF.
  • Step 803 After receiving the reporting indication, the TDF returns a response message to the PCRF, and carries the discarded amount of the IP-CAN level since the last time.
  • Step 804 The PCRF corrects the actual usage according to the discarded usage amount reported by the TDF, and modifies the relevant rules. If there is
  • the PCRF initiates a subsequent IP-CAN session/TDF session modification process according to the prior art.
  • Step 805 If the monitoring of the usage of the IP-CAN level continues, the TDF repeats the step 701- according to the time, and/or the traffic, and/or the event threshold that the pre-configured or the PCRF sends in the response message. 703 or steps 801-804, continue to perform the usage monitoring and reporting process of the discarding amount.
  • the IP-CAN level discarding amount of the TDF statistics during the session can be reported;
  • the discarding amount that is currently being counted by the TDF is also reported to the PCRF. As shown in Figure 9, the following steps are included:
  • Step 901 The PCEF detects that the trigger needs to terminate the IP-CAN session, and the trigger may be from other network elements, the UE or the PCEF itself (for example, all PCC rules are deleted).
  • Step 902 The PCEF sends an IP-CAN session termination indication message to the PCRF, where the message carries the usage consumption of the usage monitoring.
  • Step 903 The PCRF sends a TDF session termination request to the TDF to notify the TDF of the termination of the IP-CAN session.
  • Step 904 The TDF deactivates all ADC rules related to the IP-CAN session, and sends a response message to the PCRF. The amount of the IP-CAN level carried in the message monitors the discarded usage amount since the last report.
  • Step 905 The PCRF combines the reported usage of the PCEF and the TDF, updates the usage threshold, and sends a cancellation subscription notification request message to the SPR, where the message carries the consumption or the remaining allowed usage.
  • Step 906 The SPR receives the allowed consumption or the remaining allowed usage, updates the total allowed usage, and returns a cancellation subscription notification response to the PCRF.
  • step 907 the PCRF returns an IP-CAN session termination confirmation message to the PCEF.
  • the embodiments related to the first set of solutions and the embodiments related to the second set of solutions are not mutually exclusive, and the embodiments of the second set of solutions can solve the accurate monitoring of the usage of the IP-CAN level. The amount is reported.
  • the embodiment of the second set of solutions may be implemented not only based on the PCEF usage monitoring of the prior art, but also based on the application/data stream based on the PCEF/TDF of the embodiment of the first set of the foregoing solution. Implementation of the application detection strategy including the application ID and/or monitoring key usage monitoring.
  • the first embodiment of the foregoing solution may also implement the usage monitoring by using the Application ID in combination with the existing usage monitoring keyword (setting the usage monitoring key for the application).
  • the Application ID identifies the usage monitoring function of the application that cannot obtain the business data flow template.
  • the Application ID here can be, but is not limited to, the MAP of the Service ID, or the Application ID MAP on the Rx port.
  • the usage monitoring system supporting the flow detection function of the present invention includes two sets of solutions. Explained separately below.
  • the first set of programs mainly includes the following contents:
  • a usage monitoring system supporting a flow detection function includes a usage monitoring unit, and the usage monitoring unit is configured to apply a corresponding usage monitoring strategy to the PCRF to the integrated TDF PCEF, or the PCEF and the independent TDF, or the independent TDF.
  • the PCEF of the integrated TDF, or the PCEF and the independent TDF, or the independent TDF perform usage monitoring according to the usage monitoring policy.
  • the usage monitoring strategy specifically includes any one or a combination of at least one of the following: Set the monitor button;
  • the system here mainly includes the following two aspects: System 1, a usage monitoring system supporting flow detection function, performing IP-CAN level usage under an independent TDF architecture
  • the system includes: a quantity monitoring unit and a quantity correction unit; wherein, the quantity monitoring unit is used for monitoring the IP-CAN level usage by the PCEF; the quantity correction unit is used for monitoring and counting the discarded quantity by the TDF, and the statistics will be The discarding amount is reported to the PCRF; the PCRF corrects the error of the IP-CAN level usage reported by the PCEF according to the discarding amount reported by the TDF.
  • System 2 A usage monitoring system supporting flow detection function, in the case of performing IP-CAN level usage monitoring under an independent TDF architecture, the system includes: a usage monitoring unit for PCEF not monitoring IP-CAN level usage The TDF monitors the amount of the IP-CAN level and reports the amount to the PCRF.
  • the type of discarding amount specifically includes: time, and/or flow rate, and/or event; and the type of the reporting threshold value corresponding to triggering the TDF reporting discarding amount includes: a reporting threshold of time, and/or a reporting valve of the flow rate The value of the value, and/or the reported threshold of the event.
  • the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the counted usage.
  • system further includes a triggering and reporting unit, which has the following three specific implementations:
  • the specific implementation is as follows: When the triggering and reporting unit is used in the IP-CAN session, when the usage threshold is reached, the TDF usage is reported, and the TDF reports the discarding amount to the PCRF.
  • the PCRF finds that the usage monitoring of the UE reaches the usage reporting threshold and the IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops triggering the TDF usage report, PCRF The TDF sends a report indicating the discarding amount to the TDF, and the TDF reports the discarding amount to the PCRF.
  • the specific implementation is as follows: When the IP-CAN session ends, the usage of the TDF is triggered, and the TDF directly reports the discarded usage amount to the PCRF.

Landscapes

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

Abstract

Disclosed are a usage monitoring method and system supporting a traffic detection function. One solution is: a PCRF delivering a usage monitoring policy corresponding to an application to a PCEF integrated with a TDF, or a PCEF and a separate TDF, or a separate TDF; and the PCEF integrated with the TDF, or the PCEF and the separate TDF, or the separate TDF performing usage monitoring according to the usage monitoring policy. In this way, the problem that the PCRF cannot achieve usage monitoring control at the level of service data flows of a service data flow template during usage monitoring can be solved. One method in another solution of the present invention is: when usage monitoring at an IP-CAN level is performed in a separate TDF architecture, a PCEF monitoring usage at the IP-CAN level, and a TDF monitoring and calculating discarded usage, and reporting the calculated discarded usage to a PCRF; and the PCRF correcting, according to the discarded usage reported by the TDF, an error in the usage at the IP-CAN level reported by the PCEF. In this way, the problem of usage monitoring control at the IP-CAN level in the TDF architecture during usage monitoring can be solved.

Description

一种支持流检测功能的用量监控方法及*** 技术领域 本发明涉及移动通信的策略和计费控制技术领域, 尤其涉及一种支持流检测功能 ( TDF , Traffic Detection Function ) 的用量监控方法及***。 背景技术 自第三代合作伙伴计划阶段 7 ( 3GPP Release7 )标准体系以来, 策略和计费功能由 策略和计费控制 (PCC, Policy and Charging Control )框架来实现。 PCC架构是一个能 够应用于多种接入技术的功能框架, 例如, PCC 架构可以应用于通用移动通信*** ( UMTS, Universal Mobile Telecommunications System ) 的陆上无线接入网 (UTRAN, UMTS Terrestrial Radio Access Network ). 全球移动通信*** ( GSM, Global system for Mobile Communication ) /GSM数据增强演进 ( EDGE, Enhanced Data Rate for GSM Evolution )无线接入网、 互通无线局域网 ( I-WLAN, Interworking WLAN ) 以及演进的 分组***(EPS, Evolved Packet System )等。  TECHNICAL FIELD The present invention relates to the field of policy and charging control technologies for mobile communications, and in particular, to a method and system for monitoring usage of a traffic detection function (TDF). BACKGROUND Since the 3rd Generation Partnership Project Phase 7 (3GPP Release 7) standard architecture, policy and charging functions have been implemented by the Policy and Charging Control (PCC) framework. The PCC architecture is a functional framework that can be applied to multiple access technologies. For example, the PCC architecture can be applied to the UMTS Terrestrial Radio Access Network (UMTS, Universal Mobile Telecommunications System). ). Global System for Mobile Communication (GSM) / GSM (Enhanced Data Rate for GSM Evolution) Radio Access Network, Interworking WLAN (I-WLAN) and Evolved Packets System (EPS, Evolved Packet System), etc.
PCC主要实现了策略控制和计费两大功能。 图 1为现有 Rel-11的 PCC的非漫游组 成架构示意图, 以下对图 1所示的 PCC架构中的各个逻辑功能实体及其接口功能进行 描述。 如图 1所示:  PCC mainly implements two functions of policy control and billing. FIG. 1 is a schematic diagram of a non-roaming composition architecture of a PCC of the existing Rel-11. The following describes the logical function entities and their interface functions in the PCC architecture shown in FIG. 1. As shown in Figure 1:
业务功能实体( AF )用于提供业务应用的接入点, 这些业务应用所使用的网络资源 需要进行动态的策略控制。 在业务面进行参数协商时, AF将相关业务信息传递给策略 控制与计费规则功能实体(PCRF, Policy and Charging Rules Function )0 如果这些业务 信息与 PCRF的策略相一致, 则 PCRF接受该协商; 否则, PCRF拒绝该协商, 并在反 馈时给出 PCRF可接受的业务参数。 随后, AF可将这些参数返回给用户设备(UE, User Equipment )„ 其中, AF和 PCRF之间的接口是 Rx接口。 The Service Function Entity (AF) is used to provide access points for service applications. The network resources used by these service applications require dynamic policy control. When the traffic parameter negotiation face, the AF transmitting service information related to the policy and charging rule function (PCRF, Policy and Charging Rules Function ) 0 if the service information consistent with the policy of the PCRF, the PCRF accepts the negotiation; Otherwise, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback. The AF can then return these parameters to the user equipment (UE, User Equipment) „ where the interface between the AF and the PCRF is the Rx interface.
PCRF是 PCC的核心, 用于负责策略决策和计费规则的制定。 PCRF提供基于业务 数据流的网络控制规则, 这些网络控制包括业务数据流的检测、 门限控制 ( Gating Control )、服务质量( QoS , Quality of Service )控制以及基于数据流的计费规则等。 PCRF 将其制定的策略和计费规则发送给策略和计费执行功能实体( PCEF , Policy and Control Enforcement Function )执行; 同时, PCRF还需要保证这些规则和用户的签约信息一致。 其中, PCRF制定策略和计费规则的依据包括: 从 AF获得的与业务相关的信息、 从用 户签约数据库(SPR, Subscription Profile Repository )获得的与策略控制和计费相关的 用户策略计费控制签约信息、以及通过 Gx接口从 PCEF获得的与承载相关网络的信息。 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 policy and charging rules to the Policy and Control Enforcement Function (PCEF). At the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. The basis for the PCRF to formulate policies and charging rules includes: business-related information obtained from AF, and user policy charging control related to policy control and charging obtained from a user subscription database (SPR, Subscription Profile Repository) Information, and information about the bearer-related network obtained from the PCEF through the Gx interface.
PCEF通常位于网关(GW, Gate-Way )内, 在承载面执行 PCRF所制定的策略和计 费规则。 PCEF按照 PCRF所发送的规则中的业务数据流过滤器对业务数据流进行检测, 进而对这些业务数据流执行 PCRF所制定的策略和计费规则; 在承载建立时, PCEF按 照 PCRF发送的规则进行资源分配, 并根据 AF提供的信息进行门限控制; 同时, PCEF 根据 PCRF订阅的事件触发上报承载网络上发生的事件; 根据 PCRF发送的计费规则, PCEF执行相应的业务数据流计费操作, 计费既可以是在线计费, 也可以是离线计费。 如果是在线计费, 则 PCEF需要和在线计费***( OCS , Online Charging System )一起 进行信用管理; 离线计费时, PCEF和离线计费***(OFCS, Offline Charging System ) 之间交换相关的计费信息。 其中, PCEF与 PCRF之间的接口是 Gx接口, PCEF与 OCS 之间的接口是 Gy接口, PCEF与 OFCS之间的接口是 Gz接口。 也可增强 PCEF功能实 现流检测功能, 将 PCEF与 TDF集成在一起。 PCEF可以根据本地配置或是 PCRF下发 的包含应用检测控制策略(ADC, Application Detection and Control ) 的 PCC规则进行 应用检测并进行策略执行 (如门限控制、 重定向和带宽限制)。 PCEF一般都位于网络的 网关上, 如 EPS的分组数据网络网关(PDN-GW )、 通用无线分组业务(GPRS, General Packet Radio Service ) 中的 GPRS网关支持节点 ( GGSN ) 以及 I-WLAN中的分组数据 网关 ( PDG, Packet Data Gateway )等。  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 side. The PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then performs the policy and charging rule defined by the PCRF for the service data flow; when the bearer is established, the PCEF performs the rule according to the PCRF. Resource allocation, and threshold control according to the information provided by the AF; at the same time, the PCEF triggers reporting of events occurring on the bearer network according to the event subscribed by the PCRF; according to the charging rule sent by the PCRF, the PCEF performs corresponding service data flow charging operation, The fee can be either online or offline. In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS); when offline charging, the relevant calculation between the PCEF and the Offline Charging System (OFCS) Fee information. The interface between the PCEF and the PCRF is a Gx interface, the interface between the PCEF and the OCS is a Gy interface, and the interface between the PCEF and the OFCS is a Gz interface. It also enhances the PCEF function to implement flow detection and integrates PCEF with TDF. The PCEF can perform application detection and policy enforcement (such as threshold control, redirection, and bandwidth limitation) according to the local configuration or PCC rules that are sent by the PCRF and include Application Detection and Control (ADC). The PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the packet in the I-WLAN. Data Gateway (PDG, Packet Data Gateway), etc.
TDF也可以独立部署,此时 TDF与 PCRF通过 Sd接口进行交互, TDF可以根据预 配置或 PCRF下发的应用检测控制规则进行应用检测和策略执行。 PCRF为独立 TDF提 供应用检测控制规则, 独立 TDF 的策略控制执行操作包括门限控制、 重定向和带宽限 制。 TDF向 PCRF作被检测业务 /流的相关事件和信息的上报(例如向 PCRF报告检测 到的业务 /流的开始和终结), 以及给 PCRF发送业务数据流描述, 传送来自 PCRF的用 于流检测的业务检测和策略规则的信令。 TDF存在请求业务报告和主动业务报告两种模 式:请求业务报告模式, PCRF将会通知 TDF哪些业务需要检测并且 TDF报告给 PCRF; 主动业务报告模式, 在 TDF 中预配置哪些业务需要检测和报告, 该方式假定用户同意 不需请求并可执行。  The TDF can also be deployed independently. In this case, the TDF interacts with the PCRF through the Sd interface. The TDF can perform application detection and policy execution according to the application detection control rules delivered by the pre-configuration or PCRF. The PCRF provides detection control rules for independent TDF, and the policy control operations of independent TDF include threshold control, redirection, and bandwidth limitation. The TDF reports the related events and information of the detected service/flow to the PCRF (for example, reports the start and end of the detected service/flow to the PCRF), and sends a description of the service data flow to the PCRF, and transmits the flow detection from the PCRF. Signaling for service detection and policy rules. TDF exists in two modes: request service report and active service report: request service report mode, PCRF will inform TDF which services need to be detected and TDF reports to PCRF; active service report mode, which services are pre-configured in TDF for detection and reporting, This approach assumes that the user agrees that no request is required and executable.
承载绑定和事件报告功能实体 (BBERF , Bearer Binding and Event Reporting Function ) 通常位于接入网网关 (Access Network Gateway ) 内。 如当用户设备通过 E-UTRAN接入 EPS、 服务网关 (S-GW ) 与分组数据网关 (P-GW )之间釆用代理移动 互联网协议版本 6 ( PMIPv6, Proxy Mobile Internet Protocol version 6 ) 时, S-GW中就 存在 BBERF。 当用户设备通过可信任非 3GPP接入网接入时, 可信任非 3GPP接入网关 中也存在 BBERF。 The Bearer Binding and Event Reporting Function (BBERF) is usually located in the Access Network Gateway. For example, when the user equipment accesses the EPS through the E-UTRAN, the Serving Gateway (S-GW) and the Packet Data Gateway (P-GW) use proxy mobility. When Internet Protocol version 6 (PMIPv6, Proxy Mobile Internet Protocol version 6), BBERF exists in the S-GW. When the user equipment accesses through the trusted non-3GPP access network, the BBERF also exists in the trusted non-3GPP access gateway.
SPR存储有与策略控制和计费相关的用户策略计费控制签约信息。 SPR和 PCRF之 间的接口是 Sp接口。  The SPR stores user policy charging control subscription information related to policy control and charging. The interface between SPR and PCRF is the Sp interface.
OCS和 PCEF共同完成在线计费方式下用户信用的控制和管理。  OCS and PCEF jointly complete the control and management of user credit under online charging mode.
OFCS与 PCEF共同完成离线计费方式下的计费操作。  The OFCS and the PCEF jointly perform the charging operation in the offline charging mode.
以上 PCC架构通过各功能实体实现了对 UE为访问一个分组数据网络( PDN, Packet Data Network )所建立的 IP连接接入网 ( IP-CAN, IP Connectivity Access Network )会 话的策略计费控制。  The above PCC architecture implements policy charging control for IP-CAN (IP-Connected Access Network) sessions established by the UE to access a packet data network (PDN) through various functional entities.
现有技术中, PCC支持动态的用量监测控制, 以实现基于实时的网络资源使用总量 执行动态的策略决策。 用量监测可应用于单个业务数据流、 一组业务数据流或者一个 In the prior art, 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 business data stream, a set of business data streams, or a
IP-CAN会话的所有业务流。 目前, 用量(usage )指用户面数据流量。 现有技术中, 釆 用监测键 ( Monitoring Key )来标识一个需要监测用量的实例, 比如: 当 PCRF为一个 IP-CAN会话分配了 Monitoring Key以及相应的阈值, PCEF将该 IP-CAN会话的所有业 务数据流的用量累计到该 Monitoring Key对应的用量中, 当到达阈值时、 IP-CAN会话 终结时或 PCRF请求上报时, PCEF向 PCRF上报用量并用该 Monitoring Key来标识上 报的用量。 当 PCRF为一个业务流或一组业务数据流分配了 Monitoring Key以及相应的 阈值, PCRF将 Monitoring Key携带在这个业务数据流或一组业务数据流对应的 PCC规 则中。 PCEF安装 PCC规则后, 将与 PCC规则中的业务数据流模板 ( Service Data Flow Template ) 匹配的业务数据流的用量累计到 Monitoring Key对应的用量中, 当到达阈值 时、或包含同一个 Monitoring Key的最后一个 PCC规则去激活时、或 IP-CAN会话终结 时、 或 PCRF请求上报时, PCEF向 PCRF上报用量, 并用该 Monitoring Key标识上报 的用量。 其中, 所述业务数据流模板也称为业务数据流描述 ( Service data flow description ), 以下不作赘述。 All traffic flows for an IP-CAN session. Currently, usage refers to user plane data traffic. In the prior art, a monitoring key is used to identify an instance that needs to be monitored, for example: When the PCRF assigns a Monitoring Key and a corresponding threshold to an IP-CAN session, the PCEF will all of the IP-CAN session. The usage of the traffic data is accumulated in the usage corresponding to the monitoring key. When the threshold is reached, the IP-CAN session is terminated, or the PCRF request is reported, the PCEF reports the usage to the PCRF and uses the Monitoring Key to identify the reported usage. When 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. After the PCC rules are installed on the PCEF, the usage of the service data flow matching the Service Data Flow Template in the PCC rule is accumulated in the usage corresponding to the Monitoring Key. When the threshold is reached, or the same Monitoring Key is included. When the last PCC rule is deactivated, or when the IP-CAN session is terminated, or when the PCRF request is reported, the PCEF reports the usage to the PCRF, and uses the Monitoring Key to identify the reported usage. The service data flow template is also referred to as a service data flow description, which is not described below.
同时, 在 SPR中还可以保存用户某个 PDN的总允许用量, 即针对一个 IP-CAN会 话的所有业务流的总允许用量, 也可以称为每 PDN每用户的总允许用量。 SPR中还可 以保存用户某个 PDN的某些具体业务的总允许用量, 即针对一个业务数据流或一组业 务数据流的总允许用量, 通常也可以用 Monitoring Key进行标识。  At the same time, the total allowed amount of a user's PDN can be saved in the SPR, that is, the total allowable amount of all service flows for an IP-CAN session, or the total allowable amount per user per PDN. The SPR can also store the total allowed usage of certain services of 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.
当用户建立到某个 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报告自从上一次上报以来相关 Monitoring Key 的用量消耗情况。 当 PCRF收到来自 PCEF的用量上报后 , PCRF将从总允许用量中扣 除上报的用量值。 如果 PCEF上报某个 Monitoring Key的用量并且需要继续进行监测, 那么, PCRF将提供新的阈值给 PCEF; 若无需继续进行监测, PCRF不提供新的阈值给 PCEF。 当用户的一个 APN的最后一个 IP-CAN会话终结时, PCRF将在 SPR中保存剩 余的总允许用量, 包括该 PDN的总允许用量或该 PDN的某些具体业务的总允许用量。 When the user establishes an IP-CAN session to a PDN, SPR will send the total allowed amount to the PCRF. When the PCRF performs the dose monitoring control, the PCRF subscribes to the PCEF subscription usage report ( Usage_Report ) event trigger. when After the monitoring key is sent in the PCC rule, the PCC rules with the same Monitoring Key share the threshold corresponding to the Monitoring Key. When the Monitoring Key is not included in any PCC rules, all traffic data flows of the IP-CAN session share the threshold corresponding to the Monitoring Key. When the PCEF detects that the usage has reached the threshold, the IP-CAN session is terminated, all PCC rules containing a Monitoring Key are deleted, or the PCRF explicitly requests the usage report, the PCEF will report to the PCRF the usage of the relevant Monitoring Key since the last report. Consumption situation. 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 reports the usage of a Monitoring Key and needs to continue monitoring, 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. When the last IP-CAN session of an APN of the user is terminated, the PCRF will save the remaining total allowed amount in the SPR, including the total allowed amount of the PDN or the total allowed amount of some specific services of the PDN.
从现有的用量监测控制方案可以看到, 当现有用量监测控制针对一个或一组业务数 据流时, PCRF需要在业务数据流对应的 PCC规则中包含 Monitoring Key,此时 PCC规 则中包含该业务数据流对应的业务数据流模板。 PCEF安装 PCC规则后, 将与 PCC规 则中的业务数据流模板匹配的业务数据流的用量累计到 Monitoring Key对应的用量中, 从而实现用量监测控制。 当多个 PCC规则共享一个 Monitoring Key时, 与这多个 PCC 规则的业务数据流模板匹配的业务数据流的用量都会累计到这个 Monitoring Key对应的 用量中。  It can be seen from the existing usage monitoring control scheme that when the existing usage monitoring control is for one or a group of service data flows, the PCRF needs to include a Monitoring Key in the PCC rule corresponding to the service data flow, and the PCC rule includes the The service data flow template corresponding to the service data flow. After installing the PCC rule, the PCEF accumulates the usage of the service data flow matching the service data flow template in the PCC rule to the usage amount corresponding to the Monitoring Key, thereby implementing the usage monitoring control. When multiple PCC rules share a Monitoring Key, the usage of the service data stream matching the service data flow template of the multiple PCC rules is accumulated to the usage corresponding to the Monitoring Key.
然而,并不是在任何情况下, PCRF都能获取业务数据流模板。 当 PCEF集成了 TDF 时, TDF可以把检测到的应用(该应用釆用 Application ID标识)上报给 PCRF,但 PCEF 并不是在任何时候都能上报该应用对应的业务数据流模板。  However, it is not in any case that the PCRF can obtain a business data flow template. When the PCDF is integrated with the TDF, the TDF can report the detected application (the application ID is identified by the Application ID) to the PCRF. However, the PCEF does not report the service data flow template corresponding to the application at any time.
当 TDF独立部署时, TDF也可能无法上报检测到的应用对应的业务数据流模板, 此时 PCRF就无法向 PCEF下发包含业务数据流模板的 PCC规则,从而无法实现针对这 个应用的用量监测控制。  When the TDF is deployed independently, the TDF may not be able to report the service data flow template corresponding to the detected application. In this case, the PCRF cannot send the PCC rule containing the service data flow template to the PCEF, so that the usage monitoring control for the application cannot be implemented. .
当现有用量监测控制针对整个 IP-CAN 会话时, 若又部署了独立的 TDF , 因为 IP-CAN会话中可能存在 TDF无法检测和上报流信息的应用或数据流, TDF会结合 PCRF 提供的测量以及本地策略对该类应用或数据流执行相应的门控或带宽限制(即当带宽超 过限制时, 进行丢包), 对于该类数据流, PCEF的 IP-CAN 级别 (level )的用量监控处 理中已经作了用量统计, 但实际在流经 TDF后却被阻断或重定向, 这部分不应计入实 际用量。 这会导致 PCEF累计的用量与用户最终使用的不一致。  When the existing usage monitoring control is for the entire IP-CAN session, if a separate TDF is deployed, the TDF will combine the measurement provided by the PCRF because there may be applications or data streams in the IP-CAN session that cannot be detected and reported by the TDF. And the local policy performs corresponding gating or bandwidth limitation on the application or the data flow (that is, when the bandwidth exceeds the limit, packet loss is performed), and for this type of data flow, the PCEF IP-CAN level (level) usage monitoring processing The usage statistics have been made, but they are actually blocked or redirected after passing through the TDF. This part should not be included in the actual usage. This will result in a cumulative amount of PCEF usage that is inconsistent with the user's final use.
因此, 综上所述, 基于现有技术, 对于 PCEF增强 TDF或独立 TDF架构, 在 PCRF 无法获取业务数据流模板时, 无法进行该类业务数据流 level的用量监测控制。 对于独 立 TDF架构, 当执行 IP-CAN级别的用量监控功能时,存在上报的用量和实际用量不一 致的问题, 无法准确地执行 IP-CAN级别的用量监控功能。 可见: 如何实现 PCRF无法 获取业务数据流模板的该类业务数据流级别的用量监测控制, 以及 TDF 架构下的 IP-CAN级别用量检测控制, 成为了目前用量监控技术中迫切需要解决的问题。 发明内容 有鉴于此, 本发明的主要目的在于提供一种支持 TDF 的用量监控方法及***, 能 实现 PCRF无法获取业务数据流模板的该类业务数据流级别的用量监测控制, 以及 TDF 架构下的 IP-CAN级别用量检测控制。 Therefore, in summary, based on the prior art, for the PCEF enhanced TDF or the independent TDF architecture, when the PCRF cannot obtain the service data flow template, the usage monitoring control of the service data flow level cannot be performed. For independence In the TDF architecture, when the IP-CAN level usage monitoring function is executed, there is a problem that the reported usage amount and the actual usage amount are inconsistent, and the IP-CAN level usage monitoring function cannot be accurately performed. It can be seen that how to implement the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain, and the IP-CAN level usage detection control under the TDF architecture have become an urgent problem to be solved in the current usage monitoring technology. SUMMARY OF THE INVENTION In view of the above, the main object of the present invention is to provide a method and system for monitoring the usage of TDF, which can realize the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain, and the TDF architecture. IP-CAN level usage detection control.
为解决上述技术问题, 本发明的技术方案是这样实现的:  In order to solve the above technical problem, the technical solution of the present invention is implemented as follows:
一种支持流检测功能的用量监控方法,包括:策略控制与计费规则功能实体( PCRF ) 向集成流检测功能( TDF )的策略和计费执行功能实体( PCEF )、或 PCEF和独立的 TDF、 或独立的 TDF下发应用对应的用量监控策略; 所述集成 TDF的 PCEF、 或所述 PCEF 和独立的 TDF、 或所述独立的 TDF根据所述用量监控策略执行用量监测。  A usage monitoring method supporting flow detection function, including: Policy Control and Charging Rules Function Entity (PCRF) to Integrated Flow Detection Function (TDF) Policy and Charging Execution Function Entity (PCEF), or PCEF and independent TDF Or the independent TDF delivers the corresponding usage monitoring policy; the integrated TDF PCEF, or the PCEF and the independent TDF, or the independent TDF performs usage monitoring according to the usage monitoring policy.
其中, 所述用量监控策略具体包括以下任意一种或至少一种的组合: 设置监测键; 设置应用标识; 设置用于触发监测键或应用标识的事件触发器; 设置用量阀值。  The usage monitoring policy specifically includes any one or a combination of at least one of the following: setting a monitoring key; setting an application identifier; setting an event trigger for triggering a monitoring key or an application identifier; and setting a usage threshold.
其中, 所述事件触发器的取值具体包括: 用量上报( Usage_Report ); 所述用量阈值 小于等于应用相关总允许用量。  The value of the event trigger specifically includes: usage reporting ( Usage_Report ); the usage threshold is less than or equal to the application-related total allowed usage.
一种支持流检测功能的用量监控***, 包括: 用量监测单元, 用于在 PCRF向集成 TDF的 PCEF、或 PCEF和独立的 TDF、或独立的 TDF下发应用对应的用量监控策略的 情况下, 所述集成 TDF的 PCEF、 或所述 PCEF和独立的 TDF、 或所述独立的 TDF根 据所述用量监控策略执行用量监测。  A usage monitoring system supporting a flow detection function, comprising: a usage monitoring unit, configured to apply a corresponding usage monitoring strategy to a PCRF to a PCEF integrated with TDF, or a PCEF and a separate TDF, or a separate TDF The integrated TDF's PCEF, or the PCEF and the independent TDF, or the independent TDF perform usage monitoring based on the usage monitoring policy.
其中, 所述用量监控策略具体包括以下任意一种或至少一种的组合: 设置监测键; 设置应用标识; 设置用于触发监测键或应用标识的事件触发器; 设置用量阀值。  The usage monitoring policy specifically includes any one or a combination of at least one of the following: setting a monitoring key; setting an application identifier; setting an event trigger for triggering a monitoring key or an application identifier; and setting a usage threshold.
一种支持流检测功能的用量监控方法, 包括:  A usage monitoring method supporting a flow detection function, comprising:
独立的 TDF架构下执行 IP连接接入网( IP-CAN )级别用量监控时, PCEF对 IP-CAN 级别用量进行监控, 所述 TDF对丢弃用量进行监控并统计, 将统计的丢弃用量上报给 PCRF; 所述 PCRF根据 TDF上报的所述丢弃用量修正 PCEF上报的 IP-CAN级别用量 的误差;  When the IP-CAN access level monitoring is performed in the independent TDF architecture, the PCEF monitors the IP-CAN level usage. The TDF monitors and collects the discarding usage, and reports the discarded discarding amount to the PCRF. The PCRF corrects the error of the IP-CAN level usage reported by the PCEF according to the discarding amount reported by the TDF;
或者, 独立的 TDF架构下执行 IP-CAN级别用量监控时, PCEF不对 IP-CAN级别 用量进行监控, 所述 TDF对 IP-CAN级别用量进行监控并上报用量给 PCRF。 其中, 所述丢弃用量的类型具体包括: 时间、和 /或流量、和 /或事件; 对应触发 TDF 上报丢弃用量的用量上报阀值的类型包括: 时间的上报阀值、和 /或流量的上报阀值、和 /或事件的上报阀值。 Alternatively, when the IP-CAN level usage monitoring is performed under the independent TDF architecture, the PCEF does not monitor the IP-CAN level usage, and the TDF monitors the IP-CAN level usage and reports the usage amount to the PCRF. The type of the discarding amount specifically includes: a time, and/or a flow rate, and/or an event; and the type of the reporting threshold value corresponding to the amount of the discarded TDF reporting discarding amount includes: a reporting threshold of the time, and/or reporting of the flow rate Threshold value for thresholds, and/or events.
其中, 所述丢弃用量具体为: 在 TDF实行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF上的 IP-CAN级别用量监控已统计过的用量。  The discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the used amount.
其中, 所述方法还包括: 触发所述 TDF将统计的所述丢弃用量上报给所述 PCRF; 所触发的 TDF将统计的所述丢弃用量上报给 PCRF具体包括:  The method further includes: triggering the TDF to report the discarded usage amount to the PCRF; and the triggered TDF reporting the discarded usage amount to the PCRF specifically includes:
IP-CAN会话过程中, 当达到所述用量上报阀值时, 所述 TDF上报所述丢弃用量给 所述 PCRF;  During the IP-CAN session, when the usage report threshold is reached, the TDF reports the discarding amount to the PCRF;
或者, IP-CAN会话过程中, 所述 PCRF发现对 UE的用量监控达到所述用量上报 阀值且存在 IP-CAN级别的用量监控、或者所述 IP-CAN级别的用量监控停止时, PCRF 先向所述 TDF发送获取丢弃用量的上报指示, TDF再向 PCRF上报所述丢弃用量; 或者, 当 IP-CAN会话结束时, 所述 TDF向 PCRF上报所述丢弃用量。  Alternatively, during the IP-CAN session, the PCRF finds that when the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops, the PCRF first And sending, by the TDF, the reporting of the discarding amount, and the TDF reporting the discarding amount to the PCRF; or, when the IP-CAN session ends, the TDF reports the discarding amount to the PCRF.
其中,所述用量上报阀值具体包括: 由 TDF预配置的阈值、或由 PCRF下发给 TDF 的阈值;且当所述由 TDF预配置的阈值和所述由 PCRF下发给 TDF的阈值同时存在时, 优选釆用所述由 PCRF下发给 TDF的阈值。  The usage threshold value includes: a threshold pre-configured by the TDF, or a threshold sent by the PCRF to the TDF; and when the threshold pre-configured by the TDF and the threshold sent by the PCRF to the TDF are simultaneously When present, it is preferred to use the threshold that is issued by the PCRF to the TDF.
一种支持流检测功能的用量监控***,独立的 TDF架构下执行 IP-CAN级别用量监 控的情况, 该***包括: 用量监测单元和用量修正单元; 其中,  A usage monitoring system supporting a flow detection function, in which an IP-CAN level usage monitoring is performed under an independent TDF architecture, the system includes: a usage monitoring unit and a usage correction unit;
所述用量监测单元, 用于 PCEF对 IP-CAN级别用量进行监控;  The usage monitoring unit is configured to monitor the IP-CAN level usage by the PCEF;
所述用量修正单元, 用于 TDF对丢弃用量进行监控并统计, 将统计的丢弃用量上 报给 PCRF; 所述 PCRF根据 TDF上报的所述丢弃用量修正 PCEF上报的 IP-CAN级别 用量的误差;  The usage correction unit is configured to monitor and collect the discarded usage amount by the TDF, and report the discarded usage amount to the PCRF; the PCRF corrects the error of the IP-CAN level used by the PCEF according to the discarded usage reported by the TDF;
或者, 独立的 TDF架构下执行 IP-CAN级别用量监控的情况, 该***包括: 用量监 测单元, 用于 PCEF不对 IP-CAN级别用量进行监控时, 所述 TDF对 IP-CAN级别用量 进行监控并上报用量给 PCRF。  Or, in the case of performing IP-CAN level usage monitoring under a separate TDF architecture, the system includes: a usage monitoring unit, wherein when the PCEF does not monitor the IP-CAN level usage, the TDF monitors the IP-CAN level usage and Report the dosage to the PCRF.
其中, 所述丢弃用量的类型具体包括: 时间、和 /或流量、和 /或事件; 对应触发 TDF 上报丢弃用量的用量上报阀值的类型包括: 时间的上报阀值、和 /或流量的上报阀值、和 /或事件的上报阀值。  The type of the discarding amount specifically includes: a time, and/or a flow rate, and/or an event; and the type of the reporting threshold value corresponding to the amount of the discarded TDF reporting discarding amount includes: a reporting threshold of the time, and/or reporting of the flow rate Threshold value for thresholds, and/or events.
其中, 所述丢弃用量具体为: 在 TDF实行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF上的 IP-CAN级别用量监控已统计过的用量。  The discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the used amount.
其中, 该***还包括: 触发及上报单元, 用于 IP-CAN会话过程中, 当达到所述用 量上报阀值时触发 TDF的用量上报, 所述 TDF上报所述丢弃用量给所述 PCRF; The system further includes: a triggering and reporting unit, used in the IP-CAN session process, when the usage is reached When the threshold is reported, the amount of the TDF is triggered to be reported, and the TDF reports the discarded amount to the PCRF;
或者, IP-CAN会话过程中, 所述 PCRF发现对 UE的用量监控达到所述用量上报 阀值且存在 IP-CAN级别的用量监控、或者所述 IP-CAN级别的用量监控停止时触发 TDF 的用量上报, PCRF先向所述 TDF发送获取丢弃用量的上报指示, TDF再向 PCRF上报 所述丢弃用量;  Alternatively, during the IP-CAN session, the PCRF finds that the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops triggering the TDF. When the usage is reported, the PCRF first sends an indication to the TDF to obtain the discarded usage amount, and the TDF reports the discarded usage amount to the PCRF.
或者, 当 IP-CAN会话结束时触发 TDF的用量上报, 所述 TDF向 PCRF上报所述 丢弃用量。  Alternatively, when the IP-CAN session ends, the usage of the TDF is triggered, and the TDF reports the discarding amount to the PCRF.
本发明的一套方案是: PCRF向集成 TDF的 PCEF、 或 PCEF和独立的 TDF、 或独 立的 TDF下发应用对应的用量监控策略; 集成 TDF的 PCEF、 或 PCEF和独立的 TDF、 或独立的 TDF根据用量监控策略执行用量监测。 从而能解决在用量监测时, PCRF无法 获取业务数据流模板的该类业务数据流级别的用量监测控制。本发明的另一套方案的其 中一种方法是: 独立的 TDF架构下执行 IP-CAN级别用量监控时, PCEF对 IP-CAN级 别用量进行监控, TDF对丢弃用量进行监控并统计, 将统计的丢弃用量上报给 PCRF; PCRF根据 TDF上报的丢弃用量修正 PCEF上报的 IP-CAN级别用量的误差。 另一种方 法是: 独立的 TDF架构下执行 IP-CAN级别用量监控时, PCEF不对 IP-CAN级别用量 进行监控, TDF对 IP-CAN级别用量进行监控并上报用量给 PCRF。 从而能解决在用量 监测时, TDF架构下的 IP-CAN级别用量检测控制。 附图说明 图 1为现有技术的使用 SPR的非漫游场景下 PCC的***架构示意图;  A set of solutions of the present invention is: PCRF applies a corresponding usage monitoring strategy to PCEF integrated with TDF, or PCEF and independent TDF, or independent TDF; PCEF integrated with TDF, or PCEF and independent TDF, or independent TDF performs usage monitoring based on the usage monitoring strategy. Therefore, it is possible to solve the usage monitoring control of the service data flow level of the service data flow template that the PCRF cannot obtain during the usage monitoring. One of the other solutions of the present invention is: When the IP-CAN level usage monitoring is performed under the independent TDF architecture, the PCEF monitors the IP-CAN level usage, and the TDF monitors and counts the discarded usage, which will be statistically The discarding amount is reported to the PCRF. The PCRF corrects the error of the IP-CAN level reported by the PCEF according to the discarding amount reported by the TDF. Another method is: When the IP-CAN level usage monitoring is performed under the independent TDF architecture, the PCEF does not monitor the IP-CAN level usage, and the TDF monitors the IP-CAN level usage and reports the usage to the PCRF. Therefore, it can solve the IP-CAN level usage detection control under the TDF architecture during the usage monitoring. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram of a system architecture of a PCC in a non-roaming scenario using SPR in the prior art;
图 2为本发明实施例一的 PCEF集成 TDF且为请求上报模式的流程示意图; 图 3为本发明实施例二的独立 TDF且为请求上报模式的流程示意图;  2 is a schematic flowchart of a PCEF integrated TDF and a request reporting mode according to Embodiment 1 of the present invention; FIG. 3 is a schematic flowchart of an independent TDF and a request reporting mode according to Embodiment 2 of the present invention;
图 4为本发明实施例三的 PCEF集成 TDF且为非请求上报模式的流程示意图; 图 5为本发明实施例四的独立 TDF且为非请求上报模式的流程示意图;  4 is a schematic flowchart of a PCEF integrated TDF and an unsolicited reporting mode according to Embodiment 3 of the present invention; FIG. 5 is a schematic flowchart of an independent TDF and an unsolicited reporting mode according to Embodiment 4 of the present invention;
图 6为本发明实施例五的会话创建时执行用量监控的流程示意图;  6 is a schematic flowchart of performing usage monitoring during session creation according to Embodiment 5 of the present invention;
图 7为本发明应用实例一的 TDF阈值到达时丢弃用量上报流程示意图;  7 is a schematic flowchart of a discarding usage reporting process when a TDF threshold arrives according to the first application example of the present invention;
图 8为本发明应用实例二的 PCRF获取 TDF丢弃用量流程示意图;  8 is a schematic diagram of a process for obtaining a TDF discarding amount by a PCRF according to the second application example of the present invention;
图 9为本发明应用实例三的会话结束时 TDF上报丢弃用量的流程示意图。 具体实施方式 本发明的支持流检测功能的用量监控方法包括两套方案。 以下分别阐述。 FIG. 9 is a schematic flowchart of TDF reporting discarding usage at the end of a session in the third application example of the present invention. DETAILED DESCRIPTION OF THE INVENTION The method for monitoring the amount of the flow detection function of the present invention includes two sets of solutions. Explained separately below.
一、第一套方案是基于应用的用量监测控制, 能解决在 PCRF无法获取业务数据流 模板(即业务流描述) 时, 仍能进行该类业务数据流 level的用量监测控制。 该方法主 要包括以下内容:  First, the first solution is based on the usage monitoring control of the application, which can solve the usage monitoring and control of the service data flow level when the PCRF cannot obtain the service data flow template (ie, the service flow description). This method mainly includes the following:
PCRF向应用检测和控制实体下发应用对应的用量监测控制策略; 应用检测和控制 实体根据该用量监测控制策略执行用量监测。  The PCRF sends the application corresponding usage monitoring control strategy to the application detection and control entity; the application detection and control entity performs the usage monitoring according to the usage monitoring control strategy.
进一步地, 应用检测和控制实体为集成 TDF的 PCEF或独立的 TDF, 则上述下发 及执行的用量监测包括有三种情况: 1 ) PCRF向集成 TDF的 PCEF下发应用对应的用 量监控策略; 所述集成 TDF的 PCEF才艮据所述用量监控策略执行用量监测; 2 ) PCRF 向 PCEF和独立的 TDF分别下发应用对应的用量监控策略; 所述 PCEF和独立的 TDF 才艮据所述用量监控策略执行用量监测; 3 ) PCRF向独立的 TDF下发应用对应的用量监 控策略; 所述独立的 TDF根据所述用量监控策略执行用量监测。  Further, the application detection and control entity is a PCEF or a separate TDF integrated with the TDF, and the usage monitoring performed and executed includes the following three situations: 1) the PCRF delivers a corresponding usage monitoring strategy to the PCEF integrated with the TDF; The PCEF that integrates the TDF performs the usage monitoring according to the usage monitoring policy; 2) the PCRF sends the corresponding usage monitoring strategy to the PCEF and the independent TDF respectively; the PCEF and the independent TDF are monitored according to the usage. The policy performs usage monitoring; 3) The PCRF sends a corresponding usage monitoring policy to the independent TDF; the independent TDF performs usage monitoring according to the usage monitoring policy.
进一步地, 该用量监测控制策略包括: 设置监测键(Monitoring Key ); 设置应用标 识( Application ID ); 设置用于触发 Monitoring Key或 Application ID的事件触发器; 以 及设置用量阀值 (Usage Threshold )。 其中, 该事件触发器的取值可以为用量上报 ( Usage_Report ); 该用量阈值(Usage Threshold )可以筒写为 UT, UT<=TAU, TAU为 应用相关总允许用量(Totally Allowed Usage ) 的筒写。  Further, the usage monitoring control strategy includes: setting a monitoring key; setting an application ID; setting an event trigger for triggering a Monitoring Key or an Application ID; and setting a usage threshold (Usage Threshold). The value of the event trigger can be the usage report ( Usage_Report ); the usage threshold (Usage Threshold ) can be written as UT, UT<=TAU, TAU is the application related total allowed usage (Totally Allowed Usage) .
第二套方案是解决 TDF架构下的 IP-CAN level用量监控功能, 包括以下方法一和 方法二两种方案, 二者是独立的 TDF架构下执行 IP-CAN level用量监控场景下的不同 解决方案, 以下分别阐述。  The second solution is to solve the IP-CAN level usage monitoring function under the TDF architecture, including the following method 1 and method 2, which are different solutions in the implementation of the IP-CAN level usage monitoring scenario under the independent TDF architecture. , respectively, as explained below.
方法一:独立的 TDF架构下执行 IP-CAN级别用量监控时,在 PCEF上执行 IP-CAN level用量监控, TDF上统计丢弃用量并上报给 PCRF, 以用于修正 PCEF报告的用量误 差, 以实现 IP-CAN level用量监控功能。 该方法主要包括以下内容:  Method 1: When the IP-CAN level usage monitoring is performed under the independent TDF architecture, the IP-CAN level usage monitoring is performed on the PCEF, and the discarding amount is reported on the TDF and reported to the PCRF for correcting the usage error of the PCEF report. IP-CAN level usage monitoring function. The method mainly includes the following contents:
PCEF执行 IP-CAN级别用量监控功能时, TDF对该 IP-CAN会话的丢弃用量进行 统计,将统计的丢弃用量上报给 PCRF, PCRF根据该统计的丢弃用量修正 PCEF上报用 量的误差。  When the PCEF performs the IP-CAN level usage monitoring function, the TDF collects the discarding usage of the IP-CAN session, and reports the discarded discarding amount to the PCRF. The PCRF corrects the error of the PCEF reporting usage according to the discarding amount of the statistics.
进一步地, 该丢弃用量的类型包括: 时间、 和 /或流量、 和 /或事件; 对应触发的用 量上报阀值的类型包括: 时间的上报阀值、 和 /或流量的上报阀值、 和 /或事件的上报阀 值。 该丢弃用量为: 在 TDF实行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF的 IP-CAN level用量监控功能已统计过的用量。该方法中 PCEF可按现有技术执行 IP-CAN level用量检测功能。 Further, the type of the discarding amount includes: time, and/or flow rate, and/or an event; the type of the corresponding triggered usage threshold value includes: a time reporting threshold, and/or a flow reporting threshold, and/or Or the reported threshold of the event. The discarding amount is: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the PCEF The amount of the IP-CAN level usage monitoring function has been counted. In this method, the PCEF can perform the IP-CAN level usage detection function according to the prior art.
进一步地, 触发 TDF将统计的丢弃用量上报给 PCRF的时机包括: 1、 IP-CAN会 话过程中, 当用量上报阀值(如时间或流量的上报阈值)到达时, TDF上报该丢弃用量 给 PCRF; 2、 IP-CAN会话过程中, PCRF发现该 UE的用量监控的用量上报阀值到达 且存在 IP-CAN level的用量监控, 或者该 IP-CAN level的用量监控功能停止, 则 PCRF 向 TDF发送获取丢弃用量上报指示, TDF则向 PCRF上报统计的丢弃用量; 3、当 IP-CAN 会话结束时, TDF向 PCRF上报统计的丢弃用量。  Further, the timing of triggering the TDF to report the discarded discarding amount to the PCRF includes: 1. During the IP-CAN session, when the usage reporting threshold (such as the reporting threshold of time or traffic) arrives, the TDF reports the discarding amount to the PCRF. 2. During the IP-CAN session, the PCRF finds that the usage threshold of the UE's usage monitoring has reached the threshold and the IP-CAN level usage monitoring, or the IP-CAN level usage monitoring function stops, the PCRF sends to the TDF. Obtaining the discarding usage report, the TDF reports the discarding usage amount to the PCRF. 3. When the IP-CAN session ends, the TDF reports the discarding usage amount to the PCRF.
进一步地, TDF上报丢弃用量时, 所对应的用量上报阀值(如时间的上报阈值、 和 /流量的上报阈值、 和 /事件的上报阈值) 为 TDF预配置、 或 PCRF下发给 TDF的阈值。 如果 TDF预配置的阀值和 PCRF下发给 TDF的阈值这两个阈值同时存在, 则按运营商 策略执行优先级处理; 如果运营商没有相关优先策略, 则 PCRF下发的阈值优先于 TDF 预配置阈值。  Further, when the TDF reports the discarding usage amount, the corresponding usage thresholds (such as the reporting threshold of the time, and the reporting threshold of the / traffic, and the reporting threshold of the event) are the thresholds of the TDF pre-configured, or the PCRF is sent to the TDF. . If the two thresholds of the TDF pre-configured threshold and the threshold for the TDF are sent to the TDF, the priority is processed according to the carrier policy. If the operator does not have the relevant priority policy, the threshold issued by the PCRF takes precedence over the TDF pre- Configure the threshold.
进一步地, PCRF收到 TDF上报的丢弃用量后, 可以根据运营商策略, 决策是否需 要继续执行后续用量监控(例如, 用量阈值耗尽, 则若 PCRF需要继续执行监控功能, 且 TDF上报的丢弃用量足够, 则可继续下发执行用量监控功能)。  Further, after receiving the discarding amount reported by the TDF, the PCRF may decide whether to continue to perform subsequent usage monitoring according to the operator policy (for example, if the usage threshold is exhausted, if the PCRF needs to continue to perform the monitoring function, and the TDF reports the discarded usage amount. If it is enough, you can continue to issue the usage monitoring function.
方法二: 独立的 TDF 架构下执行 IP-CAN 级别用量监控时, 在 PCEF 上不执行 IP-CAN level的用量监控, PCRF下发 IP-CAN level的监控策略给 TDF, TDF执行并上 报该 IP-CAN会话的用量给 PCRF , 以实现 IP-CAN level用量监控功能。  Method 2: When performing IP-CAN level usage monitoring under the independent TDF architecture, the IP-CAN level usage monitoring is not performed on the PCEF. The PCRF sends the IP-CAN level monitoring policy to the TDF, and the TDF executes and reports the IP- The amount of CAN session is given to the PCRF to implement the IP-CAN level usage monitoring function.
这里需要指出的是: 1 )本文涉及的 "检测" 和 "监测" 虽然都在本文的用量监控 功能描述中出现, 但是并不是同一个概念。 "检测,, 是相对应用而言的, 如 TDF具有应 用检测功能, 属于识别范畴的用语描述; 而 "监测" 是相对所有的应用、 或者 IP-CAN 级别的用量的用量监控( usage monitoring )功能而言的, 属于统计和上报范畴的用语描 述。 2 )本文涉及的 "用量阀值" 与 "用量上报阀值" 也不是同一个概念, "用量阀值" 是指用量监控中该应用可使用的用量; 而 "用量上报阀值" 是指统计丢弃流量时需要上 报的一个触发值。  It should be noted here that: 1) The "detection" and "monitoring" involved in this article appear in the description of the usage monitoring function in this article, but they are not the same concept. "Detection, is relative to the application, such as TDF has application detection function, which is a description of the terms of the identification category; and "monitoring" is the usage monitoring function for all applications, or IP-CAN level usage. In other words, it is a description of the terms of statistics and reporting. 2) The “dosage threshold” and “dosage threshold” are not the same concept. The “quantity threshold” refers to the application that can be used in the usage monitoring. The "dosage threshold" refers to a trigger value that needs to be reported when the traffic is discarded.
以下对本发明进行举例阐述。  The invention is illustrated by way of example below.
实施例一: PCEF集成了 TDF , 并且 TDF釆用请求上报模式。  Embodiment 1: The PCEF integrates the TDF, and the TDF uses the request reporting mode.
图 2为本发明实施例一的用量监控方法的流程图, 如图 2所示, 该流程包括以下步 驟:  2 is a flowchart of a method for monitoring usage according to Embodiment 1 of the present invention. As shown in FIG. 2, the process includes the following steps:
步驟 201 ,在 UE请求建立 IP-CAN会话的过程中, PCEF所在的网关接收到 IP-CAN 会话建立请求消息, 并在该 IP-CAN会话建立请求消息中携带用户标识和请求接入的 PDN的 PDN标识。 Step 201: In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN. The session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
步驟 202, PCEF向 PCRF发送 IP-CAN会话建立指示消息, 并在该 IP-CAN会话建 立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP地址( IP Address )„  Step 202: 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 (IP Address) allocated to the UE in the IP-CAN session establishment indication message.
步驟 203 , PCRF根据用户标识判断还没有该用户的签约信息, PCRF向 SPR发送 签约文档请求, 并在该签约文档请求中携带用户标识和 PDN标识。  Step 203: The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
步驟 204, SPR根据用户标识和 PDN标识返回用户签约信息 (即签约文档应答)。 用户签约信息中包含用户文档配置, 指示激活应用检测和控制。 此外, 用户签约信息中 还可能包括应用相关总允许用量(TAU, Totally Allowed Usage ), 表示用户签约的需要 用量监控的每个应用的总允许用量。  Step 204: The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier. The user subscription information includes a user document configuration that indicates activation of application detection and control. In addition, the user subscription information may also include Total Allowed Usage (TAU), which indicates the total allowable amount of each application monitored by the user for the required usage.
步驟 205 , PCRF根据返回的用户签约信息、 网络策略、 UE的接入信息等制定策略。 本步驟制定策略包括制定 PCC规则和事件触发器。 由于用户签约信息中包括用户 文档配置, 所以 PCC 规则中需要应用检测控制策略。 其中应用检测控制包括设置 Application ID, 这里, Application ID表示 PCEF需要检测的应用; 设置事件触发器, 取 值为应用检测开始 (Start of application traffic detection ) 和应用检测结束 ( Stop of application traffic detection ); 以及设置可能的每个检测的应用对应的执行策略, 包括门 限控制、 最大带宽和重定向策略等。  Step 205: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE. This step development strategy includes the development of PCC rules and event triggers. Since the user subscription information includes the user document configuration, the detection control policy needs to be applied in the PCC rule. The application detection control includes setting an Application ID, where the Application ID indicates an application that the PCEF needs to detect; setting an event trigger, and the value is a Start of application traffic detection and a Stop of application traffic detection; And setting possible execution policies corresponding to each detected application, including threshold control, maximum bandwidth, and redirection strategy.
步驟 206, PCRF向 PCEF发送 IP-CAN会话建立确认消息, 携带 PCC规则和事件 触发器。 其中 PCC规则中携带 Application ID以及可能的执行策略。 事件触发器取值至 少包含 Start of application traffic detection和 Stop of application traffic detection。  Step 206: The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger. The PCC rule carries the Application ID and possible execution policies. The event trigger takes at least Start of application traffic detection and Stop of application traffic detection.
步驟 207, PCEF安装策略, 包括应用检测策略和事件触发器。 PCEF所在的网关返 回 IP-CAN会话建立应答, 在 IP-CAN会话建立应答中携带有 IP地址。  Step 207: The PCEF installation policy includes an application detection policy and an event trigger. The gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
步驟 208 , PCEF执行策略,包括执行应用检测策略,对 PCC规则中包含的 Application ID对应的应用检测。  Step 208: The PCEF executes the policy, including executing an application detection policy, and detecting an application corresponding to the Application ID included in the PCC rule.
步驟 209, PCEF检测到 Application ID对应的应用。 PCEF向 PCRF发送 IP-CAN 会话修改指示, 携带检测到的 Application ID以及事件触发器, 取值 Start of application traffic detection。  Step 209: The PCEF detects the application corresponding to the Application ID. The PCEF sends an IP-CAN session modification indication to the PCRF, carrying the detected Application ID and the event trigger, and the value is Start of application traffic detection.
步驟 210, PCRF进行策略决策, 更新 PCC规则, 包括根据 Application ID调整 QoS 和计费策略等。 若 PCRF在步驟 204中获得了该应用的 TAU或是 PCRF配置了针对该 应用的 TAU, 则 PCRF针对该应用制定用量监测策略, 包括其中用量监测策略包括设置 Monitoring Key; 设置事件触发器, 取值为 Usage_Report, 和设置 UT, 其中 UT<=TAU。 步驟 211 , PCRF向 PCEF返回 IP-CAN会话修改确认消息, 消息中携带更新的 PCC 规则和 Monitoring Key对应的 UT ,其中 PCC规则中携带 Application ID对应的 Monitoring Key。 Step 210: The PCRF performs policy decision, and updates the PCC rule, including adjusting the QoS and the charging policy according to the Application ID. If the PCRF obtains the TAU of the application in step 204 or the PCRF configures the TAU for the application, the PCRF formulates a usage monitoring policy for the application, including the usage monitoring policy including setting a Monitoring Key; setting an event trigger, and setting a value Set the UT for Usage_Report, and UT<=TAU. Step 211: The PCRF returns an IP-CAN session modification confirmation message to the PCEF, where the message carries the updated PCC rule and the UT corresponding to the Monitoring Key, where the PCC rule carries the Monitoring Key corresponding to the Application ID.
根据 SPR的签约或 PCRF配置的策略,多个 Application ID可以共享一个 Monitoring Key, 即多个应用的用量累计到一个 Monitoring Key对应的用量中。  According to the SPR contract or the PCRF configuration policy, multiple Application IDs can share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage corresponding to one Monitoring Key.
步驟 212 , PCEF执行策略,包括用量监测控制策略,安装事件触发器 Usage_Report。 PCEF对 Monitoring Key对应的应用 (用 Application ID标识) 的用量进行用量监控。  Step 212: The PCEF executes the policy, including the usage monitoring control policy, and installs the event trigger Usage_Report. The PCEF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
在其他实施例中, 在步驟 206中, PCRF就在 PCC规则中包含 Monitoring Key, 并 同时下发 Monitoring Key对应的 UT。 PCEF根据 ADC规则检测到 Application ID对应 的应用后, 就根据步驟 206中下发的用量检测策略进行用量监控, 则步驟 211中就不需 要下发用量监测策略了。  In other embodiments, in step 206, the PCRF includes a Monitoring Key in the PCC rule, and simultaneously delivers the UT corresponding to the Monitoring Key. After the PCEF detects the application corresponding to the application ID according to the ADC rule, and performs the usage monitoring according to the usage detection policy delivered in step 206, the usage monitoring strategy is not required in step 211.
实施例二: TDF独立部署, 并且 TDF釆用请求上报模式。  Embodiment 2: The TDF is deployed independently, and the TDF uses the request reporting mode.
图 3为本发明实施例二的用量监控方法的流程图, 如图 3所示, 该流程包括以下步 驟:  FIG. 3 is a flowchart of a method for monitoring usage according to Embodiment 2 of the present invention. As shown in FIG. 3, the process includes the following steps:
步驟 301 ,在 UE请求建立 IP-CAN会话的过程中, PCEF所在的网关接收到 IP-CAN 会话建立请求消息, 并在该 IP-CAN会话建立请求消息中携带用户标识和请求接入的 PDN的 PDN标识。  Step 301: In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, and carries the user identifier and the requested PDN in the IP-CAN session establishment request message. PDN identifier.
步驟 302 , PCEF向 PCRF发送 IP-CAN会话建立指示消息, 并在该 IP-CAN会话建 立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP地址。  Step 302: 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 allocated to the UE in the IP-CAN session establishment indication message.
步驟 303 , PCRF根据用户标识判断还没有该用户的签约信息, PCRF向 SPR发送 签约文档请求, 并在该签约文档请求中携带用户标识和 PDN标识。  Step 303: The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
步驟 304 , SPR根据用户标识和 PDN标识返回用户签约信息(即, 签约文档应答)。 用户签约信息中包含用户文档配置, 指示激活应用检测和控制。 此外, 用户签约信息中 还可能包括应用相关 TAU, 表示用户签约的需要用量监控的每个应用的总允许用量。  Step 304: The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier. The user subscription information includes a user document configuration that indicates activation of application detection and control. In addition, the user subscription information may also include an application-related TAU, which indicates the total allowable amount of each application monitored by the user for the required amount of subscription.
步驟 305 , PCRF根据返回的用户签约信息、 网络策略、 UE的接入信息等制定策略, 包括制定 PCC规则和事件触发器。 由于用户签约信息中包括用户文档配置, 所以 PCRF 还需要制定 ADC规则, 其中 ADC规则包括设置 Application ID , 这里 Application ID表 示 PCEF需要检测的应用; 设置事件触发器, 取值为 Start of application traffic detection 和 Stop of application traffic detection; 以及设置可能的每个检测的应用对应的执行策略, 包括门限控制、 最大带宽和重定向等。 为了支持 TDF上的应用的用量监控, 除了 ADC 规则现有内容外还可能包括 PCRF下发给 TDF的应用相关的 monitoring key; 或者 TDF 上的 IP-CAN level 的用量监控对应的 command 层的 monitoring key; 这些应用或 command相关的 monitoring key可以包括在 ADC规则中,也可能在 ADC规则之外和规 则一同下发, 或者在后续应用检测到并上报后由 PCRF更新规则处理时再下发(如步驟 313中所述)。 Step 305: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger. Since the user subscription information includes the user document configuration, the PCRF also needs to formulate an ADC rule, where the ADC rule includes setting the Application ID, where the Application ID indicates the application that the PCEF needs to detect; setting the event trigger, the value is Start of application traffic detection and Stop of application traffic detection; and setting possible execution policies for each detected application, including threshold control, maximum bandwidth, and redirection. In order to support the usage monitoring of the application on the TDF, in addition to the existing contents of the ADC rules, it may include an application-related monitoring key that is sent by the PCRF to the TDF; or TDF The usage of the IP-CAN level on the monitor monitors the corresponding monitoring layer of the command layer; the monitoring key related to these applications or commands can be included in the ADC rules, or it can be sent out with the rules outside the ADC rules, or in subsequent applications. After being reported and reported, the PCRF update rule is processed (as described in step 313).
步驟 306 , PCRF向 TDF发送 TDF会话建立请求, 携带 ADC规则和事件触发器, 取值 Start of application traffic detection和 Stop of application traffic detection, 和 /携带相 关的 monitoring key。  Step 306: The PCRF sends a TDF session establishment request to the TDF, carries an ADC rule and an event trigger, and takes values of Start of application traffic detection and Stop of application traffic detection, and/or carries a related monitoring key.
步驟 307, TDF执行策略, 安装或激活 ADC规则和事件触发器。  Step 307, TDF executes the policy, installs or activates the ADC rules and event triggers.
步驟 308 , TDF向 PCRF返回确认消息。  Step 308: The TDF returns an acknowledgement message to the PCRF.
步驟 309, PCRF向 PCEF发送 IP-CAN会话建立确认消息, 携带 PCC规则和事件 触发器。  Step 309: The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
步驟 310, PCEF安装策略。 PCEF所在的网关返回 IP-CAN会话建立应答,在 IP-CAN 会话建立应答中携带有 IP地址。  Step 310, PCEF installation policy. The gateway where the PCEF is located returns an IP-CAN session establishment response, and carries an IP address in the IP-CAN session establishment response.
步驟 311 , TDF检测到 Application ID对应的应用。 TDF向 PCRF发送业务检测上 报, 携带检测到的 Application ID 以及事件触发器, 取值 Start of application traffic detection。  Step 311: The TDF detects an application corresponding to the Application ID. The TDF sends a service detection report to the PCRF, carrying the detected Application ID and event trigger, and the value is Start of application traffic detection.
步驟 312, PCRF进行策略决策, 更新 ADC规则。 PCRF根据上报的 Application ID 设置或更新执行策略(如门限控制、 最大带宽和重定向等)若 PCRF在步驟 304中获得 了该应用的 TAU或是 PCRF配置了针对该应用的 TAU, 则 PCRF针对该应用制定用量 监测策略, 其中用量监测策略包括设置 Monitoring Key; 设置事件触发器, 取值为 Usage Report, 和设置 UT, 其中 UT<=TAU。  Step 312, the PCRF performs policy decision and updates the ADC rule. The PCRF sets or updates the execution policy (such as threshold control, maximum bandwidth, redirection, etc.) according to the reported Application ID. If the PCRF obtains the TAU of the application in step 304 or the PCRF configures the TAU for the application, the PCRF targets the The application establishes a usage monitoring strategy, wherein the usage monitoring strategy includes setting a Monitoring Key; setting an event trigger, taking a value of Usage Report, and setting a UT, where UT<=TAU.
步驟 313 , PCRF向 TDF返回确认消息, 消息中携带更新的 ADC规则和 Monitoring Key对应的 UT。 其中 ADC规则中包含与 Applcation ID对应的 Monitoring Key。  Step 313: The PCRF returns an acknowledgement message to the TDF, where the message carries the updated ADC rule and the UT corresponding to the Monitoring Key. The ADC rule contains a Monitoring Key corresponding to the Applcation ID.
根据 SPR的签约或 PCRF配置的策略,多个 Application ID可以共享一个 Monitoring Key, 即多个应用的用量累计到一个 Monitoring Key对应的用量中。  According to the SPR contract or the PCRF configuration policy, multiple Application IDs can share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage corresponding to one Monitoring Key.
步驟 314, TDF执行策略, 包括用量监测控制策略, 安装事件触发器 Usage_Report。 TDF对 Monitoring Key对应的应用 (用 Application ID标识) 的用量进行用量监控。  Step 314, the TDF execution policy, including the usage monitoring control policy, and the event trigger Usage_Report. The TDF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
在其他实施例中, 在步驟 306中, PCRF就在 ADC规则中包含 Monitoring Key, 并 同时下发 Monitoring Key对应的 UT。 TDF根据 ADC规则检测到 Application ID对应的 应用后, 就根据步驟 306步中下发的用量检测策略进行用量监控, 则步驟 313中就不需 要下发用量监测策略了。 实施例三: PCEF集成了 TDF功能, 并且 TDF釆用非请求上报模式。 图 4为本发明实施例的用量监控方法的流程图,如图 4所示,该流程包括以下步驟: 步驟 401 ,在 UE请求建立 IP-CAN会话的过程中, PCEF所在的网关接收到 IP-CAN 会话建立请求消息, 并在该 IP-CAN会话建立请求消息中携带用户标识和请求接入的 PDN的 PDN标识。 In other embodiments, in step 306, the PCRF includes the Monitoring Key in the ADC rule and simultaneously delivers the UT corresponding to the Monitoring Key. After the TDF detects the application corresponding to the Application ID according to the ADC rule, and performs the usage monitoring according to the usage detection policy delivered in step 306, the usage monitoring strategy is not required in step 313. Embodiment 3: The PCEF integrates the TDF function, and the TDF uses the unrequested reporting mode. FIG. 4 is a flowchart of a method for monitoring usage according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps: Step 401: In a process in which the UE requests to establish an IP-CAN session, the gateway where the PCEF is located receives the IP- The CAN session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
步驟 402 , PCEF向 PCRF发送 IP-CAN会话建立指示消息, 并在该 IP-CAN会话建 立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP地址。  Step 402: 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 allocated for the UE in the IP-CAN session establishment indication message.
步驟 403 , PCRF根据用户标识判断还没有该用户的签约信息, PCRF向 SPR发送 签约文档请求, 并在该签约文档请求中携带用户标识和 PDN标识。  Step 403: The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
步驟 404 , SPR根据用户标识和 PDN标识返回用户签约信息(即, 签约文档应答)。 此外,用户签约信息中还可能包括应用相关 TAU,表示用户签约的需要用量监控的每个 应用的总允许用量。  Step 404: The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier. In addition, the user subscription information may also include an application-related TAU, which indicates the total allowed usage of each application monitored by the user for the required usage.
步驟 405 , PCRF根据返回的用户签约信息、 网络策略、 UE的接入信息等制定策略。 包括制定 PCC规则和事件触发器。  Step 405: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE. This includes making PCC rules and event triggers.
步驟 406 , PCRF向 PCEF发送 IP-CAN会话建立确认消息, 携带 PCC规则和事件 触发器。  Step 406: The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger.
步驟 407 , PCEF安装策略, PCEF所在的网关返回 IP-CAN会话建立应答,在 IP-CAN 会话建立应答中携带有 IP地址。  Step 407: The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
步驟 408 , 由于 PCEF集成 TDF功能, 并且 TDF釆用非请求上报模式, PCEF将根 据预配置的应用检测策略进行应用检测。预配置的应用检测策略包括至少包括需要检测 的应用对应的 Application ID , 若该应用需要进行用量监控, 则该应用还有对应的 Monitoring Key。  Step 408: Since the PCEF integrates the TDF function, and the TDF uses the unrequested reporting mode, the PCEF performs application detection according to the pre-configured application detection policy. The pre-configured application detection policy includes at least an application ID corresponding to the application to be detected. If the application needs to perform usage monitoring, the application also has a corresponding Monitoring Key.
步驟 409 , PCEF检测到预配置的应用检测策略中指定的应用 (用 Application ID标 识;)。 PCEF向 PCRF发送 IP-CAN会话修改指示, 携带检测到的 Application ID以及事 件触发器, 取值 Start of application traffic detection。  Step 409: The PCEF detects the application specified in the pre-configured application detection policy (identified by the Application ID;). The PCEF sends an IP-CAN session modification indication to the PCRF, carrying the detected Application ID and the event trigger, and the value is Start of application traffic detection.
步驟 410 , PCRF进行策略决策, 包括根据 Application ID调整 QoS和计费等。 若 PCRF在步驟 404中获得了该应用的 TAU或是 PCRF配置了针对该应用的 TAU ,则 PCRF 针对该应用制定用量监测策略, 包括: 设置事件触发器, 取值为 Usage_Report, 和设置 预配置的 Monitoring Key对应的 UT , 其中 UT<=TAU。  Step 410: The PCRF performs policy decision, including adjusting QoS and charging according to the Application ID. If the PCRF obtains the TAU of the application in step 404 or the PCRF configures the TAU for the application, the PCRF formulates a usage monitoring policy for the application, including: setting an event trigger, taking the value of Usage_Report, and setting the pre-configured The UT corresponding to the Monitoring Key, where UT<=TAU.
步驟 411 , PCRF向 PCEF返回 IP-CAN会话修改确认消息, 消息中携带 Application Step 411: The PCRF returns an IP-CAN session modification confirmation message to the PCEF, where the message carries the Application.
ID和 Monitoring Key对应的 UT。 在 PCEF预配置的应用检测策略可以是多个 Application ID共享一个 Monitoring Key, 即多个应用的用量累计到一个 Monitoring Key对应的用量中。 ID and UT corresponding to the Monitoring Key. The application detection policy pre-configured in the PCEF may be that multiple Application IDs share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage amount corresponding to one Monitoring Key.
步驟 412, PCEF执行策略,包括用量监测控制策略,安装事件触发器 Usage_Report。 PCEF对 Monitoring Key对应的应用 (用 Application ID标识) 的用量进行用量监控。  Step 412: The PCEF executes the policy, including the usage monitoring control policy, and installs the event trigger Usage_Report. The PCEF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
实施例四: TDF独立部署, 并且 TDF釆用非请求上报模式。  Embodiment 4: The TDF is deployed independently, and the TDF uses the unsolicited reporting mode.
图 5为本发明实施例的用量监控方法的流程图,如图 5所示,该流程包括以下步驟: 步驟 501 ,在 UE请求建立 IP-CAN会话的过程中, PCEF所在的网关接收到 IP-CAN 会话建立请求消息, 并在该 IP-CAN会话建立请求消息中携带用户标识和请求接入的 PDN的 PDN标识。  FIG. 5 is a flowchart of a method for monitoring usage according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps: Step 501: In a process in which the UE requests to establish an IP-CAN session, the gateway where the PCEF is located receives the IP- The CAN session establishment request message carries the user identifier and the PDN identifier of the PDN requested to be accessed in the IP-CAN session establishment request message.
步驟 502, PCEF向 PCRF发送 IP-CAN会话建立指示消息, 并在该 IP-CAN会话建 立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP地址。  Step 502: 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 allocated to the UE in the IP-CAN session establishment indication message.
步驟 503 , PCRF根据用户标识判断还没有该用户的签约信息, PCRF向 SPR发送 签约文档请求, 并在该签约文档请求中携带用户标识和 PDN标识。  Step 503: The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
步驟 504, SPR根据用户标识和 PDN标识返回用户签约信息 (即签约文档应答)。 此外,用户签约信息中还可能包括应用相关 TAU,表示用户签约的需要用量监控的每个 应用的总允许用量。  Step 504: The SPR returns the user subscription information (ie, the contracted document response) according to the user identifier and the PDN identifier. In addition, the user subscription information may also include an application-related TAU, which indicates the total allowed usage of each application monitored by the user for the required usage.
步驟 505 , PCRF根据返回的用户签约信息、 网络策略、 UE的接入信息等制定策略, 包括制定 PCC规则和事件触发器。  Step 505: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger.
步驟 506, PCRF向 PCEF发送 IP-CAN会话建立确认消息, 携带 PCC规则和事件 触发器。 为了支持 TDF上的应用的用量监控, 除了 ADC规则现有内容外还可能包括 PCRF下发给 TDF的应用相关的 monitoring key; 或者 TDF上的 IP-CAN level的用量监 控对应的 command层的 monitoring key; 这些应用或 command相关的 monitoring key可 以包括在 ADC规则中,也可能在 ADC规则之外和规则一同下发,或者在后续应用检测 到并上报后由 PCRF更新规则处理时再下发(如步驟 512和步驟 513所述 )。  Step 506: The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carrying the PCC rule and the event trigger. In order to support the usage monitoring of the application on the TDF, in addition to the existing contents of the ADC rule, the monitoring key associated with the application sent by the PCRF to the TDF may be included; or the usage of the IP-CAN level on the TDF monitors the monitoring key of the corresponding command layer. These application or command-related monitoring keys can be included in the ADC rules, or they can be sent out with the rules in addition to the ADC rules, or sent by the PCRF update rule after subsequent applications detect and report them (such as steps). 512 and step 513).
步驟 507, PCEF安装策略, PCEF所在的网关返回 IP-CAN会话建立应答,在 IP-CAN 会话建立应答中携带有 IP地址。  Step 507: The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
经过上述流程, UE可以进行业务访问了。  After the above process, the UE can perform service access.
步驟 508, TDF在对流经它的数据流进行检测时,发现 IP地址为新的地址,则 TDF 向 PCRF发送 TDF会话建立, 消息中携带 IP地址。  Step 508: When the TDF detects the data stream flowing through it, and finds that the IP address is a new address, the TDF sends a TDF session to the PCRF, and the message carries the IP address.
步驟 509, PCRF根据 IP地址将 TDF会话与 IP-CAN会话进行关联。 PCRF向 TDF 返回消息。 步驟 510, TDF根据预配置的 ADC规则进行应用检测和控制。 该 ADC规则至少包 括需要检测的应用对应的 Application ID,若该应用需要进行用量监控,则该应用还有对 应的 Monitoring Key。 In step 509, the PCRF associates the TDF session with the IP-CAN session according to the IP address. The PCRF returns a message to the TDF. In step 510, the TDF performs application detection and control according to pre-configured ADC rules. The ADC rule includes at least the Application ID corresponding to the application to be detected. If the application needs to perform usage monitoring, the application also has a corresponding Monitoring Key.
步驟 511 , TDF检测到预配置的应用检测策略中指定的应用 (用 Application ID标 识;)。 TDF向 PCRF发送业务检测上报, 携带检测到的 Application ID以及事件触发器, 取值 Start of application traffic detection.  Step 511: The TDF detects the application specified in the pre-configured application detection policy (identified by the Application ID;). The TDF sends a service detection report to the PCRF, and carries the detected Application ID and event trigger. The value is Start of application traffic detection.
步驟 512, PCRF进行策略决策。 若 PCRF在步驟 504中获得了该应用的 TAU或是 PCRF配置了针对该应用的 TAU, 则 PCRF针对该应用制定用量监测策略, 包括: 设置 事件触发器, 取值为 Usage_Report, 和设置预配置的 Monitoring Key对应的 UT, 其中 步驟 513 , PCRF向 TDF返回确认消息,消息中携带 Application ID和 Monitoring Key 对应的 UT。  Step 512, the PCRF makes a policy decision. If the PCRF obtains the TAU of the application in step 504 or the PCRF configures the TAU for the application, the PCRF formulates a usage monitoring policy for the application, including: setting an event trigger, taking the value of Usage_Report, and setting the pre-configured The UT corresponding to the Monitoring Key, in step 513, the PCRF returns an acknowledgement message to the TDF, where the message carries the UT corresponding to the Application ID and the Monitoring Key.
在 TDF预配置的应用检测策略可以是多个 Application ID共享一个 Monitoring Key, 即多个应用的用量累计到一个 Monitoring Key对应的用量中。  The application detection policy pre-configured in the TDF may be that multiple Application IDs share a Monitoring Key, that is, the usage of multiple applications is accumulated into the usage amount corresponding to one Monitoring Key.
步驟 514, TDF执行策略, 包括用量监测控制策略,安装事件触发器 Usage_Report。 Step 514, the TDF execution policy, including the usage monitoring control policy, and the event trigger Usage_Report.
TDF对 Monitoring Key对应的应用 (用 Application ID标识) 的用量进行用量监控。 The TDF monitors the usage of the application corresponding to the Monitoring Key (identified by the Application ID).
上述各个实施例是针对本发明的第一套方案而言的, 以下实施例是针对本发明的第 二套方案而言的。  The various embodiments described above are directed to the first set of aspects of the present invention, and the following embodiments are directed to the second set of aspects of the present invention.
第二套方案中,对于方法二"独立的 TDF架构下执行 IP-CAN级别用量监控时, PCEF 不对 IP-CAN 级别用量进行监控, TDF 对 IP-CAN 级别用量进行监控并上报用量给 PCRF" , 则在独立 TDF上实现 IP-CAN level的用量监控, 适用于上述实施例二和实施 例四的流程描述及功能, 这里不作重复描述。 不同于具体的应用的监控处理, 对于 IP-CAN level的用量监控, PCRF下发给 TDF对应 IP-CAN level的 monitoring key。  In the second solution, when the IP-CAN level usage monitoring is performed under the independent TDF architecture in Method 2, the PCEF does not monitor the IP-CAN level usage, and the TDF monitors the IP-CAN level usage and reports the usage to the PCRF. The IP-CAN level usage monitoring is implemented on the independent TDF, and is applicable to the process descriptions and functions of the foregoing Embodiment 2 and Embodiment 4, and is not repeatedly described herein. Different from the monitoring and processing of the specific application, for the monitoring of the usage of the IP-CAN level, the PCRF is sent to the monitoring key of the TDF corresponding to the IP-CAN level.
实施例五:  Embodiment 5:
本发明实施例描述的是用户建立 IP-CAN会话过程中, PCRF下发用量阈值给 PCEF, 当存在 IP-CAN level的用量监控时, TDF统计并上报丢弃用量, 执行用量监控的流程。 和现有技术流程的区别在于, PCRF需要下发丢弃用量监控指示给 TDF, TDF执行丢弃 用量的监控和上报。 如图 6所示, 主要包括以下步驟:  The embodiment of the present invention describes the process of setting the usage threshold to the PCEF during the IP-CAN session. When the usage of the IP-CAN level is monitored, the TDF collects and reports the discarding usage and performs the usage monitoring process. The difference from the prior art process is that the PCRF needs to send the discarding usage monitoring indication to the TDF, and the TDF performs the monitoring and reporting of the discarding amount. As shown in Figure 6, it mainly includes the following steps:
步驟 601 ,在 UE请求建立 IP-CAN会话的过程中, PCEF所在的网关接收到 IP-CAN 会话建立请求消息, 并在该 IP-CAN会话建立请求消息中携带用户标识和请求接入的 PDN的 PDN标识。 步驟 602, PCEF向 PCRF发送 IP-CAN会话建立指示消息, 并在该 IP-CAN会话建 立指示消息中携带用户标识、 PDN标识以及为 UE分配的 IP地址。 若 TDF为请求上报 模式, 则带上 TDF的 IP地址给 PCRF。 Step 601: In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, and carries the user identifier and the requested PDN in the IP-CAN session establishment request message. PDN identifier. Step 602: 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 allocated for the UE in the IP-CAN session establishment indication message. If the TDF is in the request reporting mode, the IP address of the TDF is brought to the PCRF.
步驟 603 , PCRF根据用户标识判断还没有该用户的签约信息, PCRF向 SPR发送 签约文档请求, 并在该签约文档请求中携带用户标识和 PDN标识。  Step 603: The PCRF determines that there is no subscription information of the user according to the user identifier, and the PCRF sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
步驟 604, SPR根据用户标识和 PDN标识返回用户的签约信息,包含该用户的 TAU, 表示用户签约的需要用量监控的每个应用的总允许用量发送给 PCRF。若 TDF为请求上 报方式, 则 SPR在响应中携带用户文档配置, 指示是否该 IP-CAN会话可执行 ADC功 能。  Step 604: The SPR returns the subscription information of the user according to the user identifier and the PDN identifier, including the TAU of the user, and indicates that the total allowed usage of each application monitored by the user for the required subscription amount is sent to the PCRF. If the TDF is the request reporting mode, the SPR carries a user document configuration in the response indicating whether the IP-CAN session can perform the ADC function.
步驟 605 , PCRF根据返回的用户签约信息、 网络策略、 UE的接入信息等制定策略, 包括制定 PCC规则和事件触发器。 如果用户签约信息中包括用户文档配置, 则 PCRF 还需要制定 ADC规则。  Step 605: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE, including formulating a PCC rule and an event trigger. If the user's subscription information includes user documentation configuration, the PCRF also needs to develop ADC rules.
步驟 606 , PCRF发送 TDF会话创建请求给 TDF , 提供 ADC规则请求创建 TDF会 话。 若该 IP-CAN会话执行了 IP-CAN level的用量监控功能, 则同时下发 IP-CAN level 的丢弃用量监控指示给 TDF。 可选地, PCRF携带丢弃用量的上报阈值(例如时间或流 量的上报阈值)给 TDF。  Step 606: The PCRF sends a TDF session creation request to the TDF, and provides an ADC rule request to create a TDF session. If the IP-CAN session performs the usage monitoring function of the IP-CAN level, the IP-CAN level discarding usage monitoring indication is simultaneously sent to the TDF. Optionally, the PCRF carries a reporting threshold of the discarding amount (e.g., a reporting threshold of time or traffic) to the TDF.
步驟 607, TDF返回会话创建响应消息给 PCRF,执行丢弃数据的用量监控;若 PCRF 提供了 ADC规则, 则执行策略, 安装或激活 ADC规则和事件触发器。  Step 607: The TDF returns a session creation response message to the PCRF to perform usage monitoring of the discarded data. If the PCRF provides the ADC rule, execute the policy, install or activate the ADC rule and the event trigger.
步驟 608, PCRF向 PCEF发送 IP-CAN会话建立确认消息, 携带 PCC规则和事件 触发器, 携带该 IP-CAN会话的用量阈值, PCEF开始执行用量监测。  Step 608: The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, carries the PCC rule and the event trigger, carries the usage threshold of the IP-CAN session, and the PCEF starts to perform the usage monitoring.
步驟 609, PCEF执行策略, 安装或激活 PCC规则, 执行用量监测。 PCEF所在的 网关返回 IP-CAN会话建立应答, 在 IP-CAN会话建立应答中携带有 IP地址。  Step 609, the PCEF executes the policy, installs or activates the PCC rule, and performs the usage monitoring. The gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP address.
经过上述流程后, PCEF 和 TDF根据 PCRF 下发的用量监测策略对 UE 建立的 IP-CAN会话进行用量监测。  After the above process, the PCEF and the TDF monitor the usage of the IP-CAN session established by the UE according to the usage monitoring policy delivered by the PCRF.
在 IP-CAN会话过程中, TDF受到触发后会上报该 IP-CAN level的丢弃流量统计给 During the IP-CAN session, the TDF will report the discarding traffic statistics of the IP-CAN level to the TDF.
PCRF。 至少包括如下几种应用场景 (或者也可以称为触发丢弃流量上报的时机): PCRF. At least the following application scenarios (or the timing of triggering the discarding traffic report):
应用实例一:会话过程中,当时间或流量阈值到达时 TDF上报该丢弃用量给 PCRF。 当 TDF的用量(时间, 或流量, 或事件) 的上报阈值到达, TDF会发送请求消息 给 PCRF, 报告上次报告之后统计的该 IP-CANlevel丢弃用量。 如图 7所示, 本实例主 要包括以下步驟:  Application Example 1: During the session, when the time or traffic threshold is reached, the TDF reports the discarding amount to the PCRF. When the reported threshold for the usage (time, flow, or event) of the TDF arrives, the TDF sends a request message to the PCRF to report the IP-CANlevel discard amount counted since the last report. As shown in Figure 7, this example mainly includes the following steps:
步驟 701 , TDF检测到该 IP-CAN level的丢弃用量达到了时间或流量或事件的上报 阈值(TDF预配置、 或 PCRF下发的上报阈值), 触发丢弃用量的上报流程。 Step 701: The TDF detects that the discarding amount of the IP-CAN level reaches a time or flow or an event report. Threshold (TDF pre-configuration, or reporting threshold sent by the PCRF) triggers the reporting process of discarding usage.
步驟 702, TDF发送请求消息给 PCRF, 报告该 IP-CAN level自上次报告后的丢弃 用量。  Step 702: The TDF sends a request message to the PCRF to report the discarded usage of the IP-CAN level since the last report.
步驟 703 , PCRF根据 TDF上报的丢弃用量, 修改相关 PCC规则和 /或 ADC规则, 发送响应消息给 TDF, 若有更新则响应消息中携带修改后的 ADC规则。若有 PCC规则 更新, 则 PCRF将按现有技术发起后续的 IP-CAN会话修改流程  Step 703: The PCRF modifies the relevant PCC rule and/or the ADC rule according to the discarding amount reported by the TDF, and sends a response message to the TDF. If there is an update, the response message carries the modified ADC rule. If there is a PCC rule update, the PCRF will initiate a subsequent IP-CAN session modification process according to the prior art.
步驟 704, 若该 IP-CAN level的用量监控继续, 则 TDF会根据自身预配置的或者 PCRF在响应消息中下发的时间、 和 /或流量、 和 /或事件阈值, 重复步驟 701-703 , 继续 执行丢弃用量的用量监控和上报流程。  Step 704: If the monitoring of the usage of the IP-CAN level continues, the TDF repeats the steps 701-703 according to the time, and/or the traffic, and/or the event threshold that the pre-configured or PCRF sends in the response message. Continue to perform the usage monitoring and reporting process for discarding usage.
应用实例二: PCRF发现该 UE的用量监控的阈值到达且存在 IP-CAN level的用量 监控, 或者该 IP-CAN level的用量监控功能停止, 则 PCRF向 TDF发送获取丢弃用量 上报指示, TDF则向 PCRF上报统计的丢弃用量。  Application example 2: The PCRF finds that the threshold of the usage monitoring of the UE arrives and the usage of the IP-CAN level is monitored, or the monitoring function of the IP-CAN level is stopped, and the PCRF sends an indication of the discarding usage report to the TDF, and the TDF goes to The discarded amount of statistics is reported by the PCRF.
会话过程中, PCRF发现该 UE存在 IP-CAN level的用量监控且用量监控阈值到达, 或者该 IP-CAN level的用量监控功能停止,或者受到外部触发 UE阈值变更等,则 PCRF 向 TDF发送获取丢弃用量上报指示, 触发 TDF向 PCRF上报统计的丢弃用量, 如图 8 所示, 包括以下步驟:  During the session, the PCRF finds that the UE has the IP-CAN level usage monitoring and the usage monitoring threshold is reached, or the IP-CAN level usage monitoring function is stopped, or the externally triggered UE threshold is changed, and the PCRF sends the discard to the TDF. The usage report of the usage triggers the TDF to report the discarded usage amount to the PCRF. As shown in Figure 8, the following steps are included:
步驟 801 ,存在 IP-CAN level用量监控,会话过程中 PCRF受到内部或外部触发(例 如, 该用量监控且用量监控阈值到达, 或者该用量监控功能停止, 或 SPR的签约阈值变 更等), 需要获取当前的 TDF丢弃流量以便于校对实际用量, 则会触发丢弃用量的获取 流程。  Step 801: There is an IP-CAN level usage monitoring, and the PCRF is internally or externally triggered during the session (for example, the usage monitoring and the usage monitoring threshold arrives, or the usage monitoring function is stopped, or the SPR subscription threshold is changed, etc.), and needs to be obtained. The current TDF discards the traffic to facilitate the proofreading of the actual usage, which triggers the process of obtaining the discarding usage.
步驟 802, PCRF向 TDF发送请求消息, 消息中携带丢弃用量上报指示, 请求 TDF 向 PCRF上报统计的丢弃用量。若有 ADC规则修改,则会一并提供更新后的规则给 TDF。  Step 802: The PCRF sends a request message to the TDF, where the message carries a drop usage indication, and requests the TDF to report the discarded usage amount to the PCRF. If there is an ADC rule modification, the updated rule will be provided to the TDF.
步驟 803 , TDF收到上报指示后, 返回响应消息给 PCRF, 携带该 IP-CAN level自 上次 ·ί艮告后的丢弃用量。  Step 803: After receiving the reporting indication, the TDF returns a response message to the PCRF, and carries the discarded amount of the IP-CAN level since the last time.
步驟 804, PCRF根据 TDF上报的丢弃用量, 修正实际用量, 修改相关规则。 若有 Step 804: The PCRF corrects the actual usage according to the discarded usage amount reported by the TDF, and modifies the relevant rules. If there is
PCC规则更新, 则 PCRF会按现有技术发起后续的 IP-CAN会话 /TDF会话修改流程。 When the PCC rule is updated, the PCRF initiates a subsequent IP-CAN session/TDF session modification process according to the prior art.
步驟 805 , 若该 IP-CAN level的用量监控继续, 则 TDF会才艮据自身预配置的或者 PCRF在响应消息中下发的时间、 和 /或流量、 和 /或事件阈值, 重复步驟 701-703或步驟 801-804, 继续执行丢弃用量的用量监控和上报流程。  Step 805: If the monitoring of the usage of the IP-CAN level continues, the TDF repeats the step 701- according to the time, and/or the traffic, and/or the event threshold that the pre-configured or the PCRF sends in the response message. 703 or steps 801-804, continue to perform the usage monitoring and reporting process of the discarding amount.
应用实例三: 当 IP-CAN会话结束时, TDF向 PCRF上报统计的丢弃用量。  Application Example 3: When the IP-CAN session ends, the TDF reports the discarded usage amount to the PCRF.
经过上述流程, 可执行会话过程中 TDF统计的 IP-CAN level的丢弃用量的上报; 除了以上场景的触发用量上报外,会话结束时, TDF当前正在统计的丢弃用量也会上报 给 PCRF, 如图 9所示, 包括以下步驟: After the foregoing process, the IP-CAN level discarding amount of the TDF statistics during the session can be reported; In addition to the triggering usage report of the above scenario, the discarding amount that is currently being counted by the TDF is also reported to the PCRF. As shown in Figure 9, the following steps are included:
步驟 901 , PCEF检测到触发需要终结 IP-CAN会话, 该触发可能来自其他网元, UE或是 PCEF自身 (例如 PCC规则全部删除)。  Step 901: The PCEF detects that the trigger needs to terminate the IP-CAN session, and the trigger may be from other network elements, the UE or the PCEF itself (for example, all PCC rules are deleted).
步驟 902 , PCEF向 PCRF发送 IP-CAN会话终结指示消息, 消息中携带用量监测的 用量消耗。  Step 902: The PCEF sends an IP-CAN session termination indication message to the PCRF, where the message carries the usage consumption of the usage monitoring.
步驟 903 , PCRF发送 TDF会话终结请求给 TDF,通知 TDF该 IP-CAN会话的终结。 步驟 904, TDF去活该 IP-CAN会话相关的所有 ADC规则,发送响应消息给 PCRF, 消息中携带该 IP-CAN level的用量监控自上次报告后的丢弃用量。  Step 903: The PCRF sends a TDF session termination request to the TDF to notify the TDF of the termination of the IP-CAN session. Step 904: The TDF deactivates all ADC rules related to the IP-CAN session, and sends a response message to the PCRF. The amount of the IP-CAN level carried in the message monitors the discarded usage amount since the last report.
步驟 905 , PCRF结合 PCEF和 TDF的上报用量, 将用量阈值更新, 向 SPR发送取 消签约通知请求消息, 消息中携带用量消耗或是剩余的允许用量。  Step 905: The PCRF combines the reported usage of the PCEF and the TDF, updates the usage threshold, and sends a cancellation subscription notification request message to the SPR, where the message carries the consumption or the remaining allowed usage.
步驟 906, SPR收到允许用量消耗或是剩余的允许用量, 将总的允许用量更新, 向 PCRF返回取消签约通知应答。  Step 906: The SPR receives the allowed consumption or the remaining allowed usage, updates the total allowed usage, and returns a cancellation subscription notification response to the PCRF.
步驟 907, PCRF向 PCEF返回 IP-CAN会话终结确认消息。  In step 907, the PCRF returns an IP-CAN session termination confirmation message to the PCEF.
需要说明的是,上述第一套方案涉及的实施例和第二套方案涉及的实施例之间并不 互斥,第二套方案涉及的实施例,能解决 IP-CAN level的用量监控的准确用量上报问题。 且第二套方案涉及的实施例不仅可以基于现有技术的 PCEF用量监控基础上实施, 也可 以基于上述第一套方案涉及的实施例的在 PCEF/TDF上执行的、 基于应用 /数据流的在 应用检测策略中包括 Application ID和 /或 monitoring key的用量监控基础上实施。  It should be noted that the embodiments related to the first set of solutions and the embodiments related to the second set of solutions are not mutually exclusive, and the embodiments of the second set of solutions can solve the accurate monitoring of the usage of the IP-CAN level. The amount is reported. The embodiment of the second set of solutions may be implemented not only based on the PCEF usage monitoring of the prior art, but also based on the application/data stream based on the PCEF/TDF of the embodiment of the first set of the foregoing solution. Implementation of the application detection strategy including the application ID and/or monitoring key usage monitoring.
同时, 上述第一套方案涉及的实施例也可以为 Application ID结合现有的用量监控 关键字(为该类应用设置特殊的用量监控关键字 usage monitoring key )来实现用量监控。 通过 Application ID来识别该类无法获取业务数据流模板的应用的用量监控功能。  At the same time, the first embodiment of the foregoing solution may also implement the usage monitoring by using the Application ID in combination with the existing usage monitoring keyword (setting the usage monitoring key for the application). The Application ID identifies the usage monitoring function of the application that cannot obtain the business data flow template.
此外, 这里的 Application ID可以但不限于 Service ID的 MAP, 或者 Rx 口上的 Application ID MAP。  In addition, the Application ID here can be, but is not limited to, the MAP of the Service ID, or the Application ID MAP on the Rx port.
本发明的支持流检测功能的用量监控***包括两套方案。 以下分别阐述。  The usage monitoring system supporting the flow detection function of the present invention includes two sets of solutions. Explained separately below.
一、 第一套方案主要包括以下内容:  First, the first set of programs mainly includes the following contents:
一种支持流检测功能的用量监控***, 该***包括用量监测单元, 用量监测单元用 于在 PCRF向集成 TDF的 PCEF、 或 PCEF和独立的 TDF、 或独立的 TDF下发应用对 应的用量监控策略的情况下, 所述集成 TDF的 PCEF、 或所述 PCEF和独立的 TDF、 或 所述独立的 TDF根据所述用量监控策略执行用量监测。  A usage monitoring system supporting a flow detection function, the system includes a usage monitoring unit, and the usage monitoring unit is configured to apply a corresponding usage monitoring strategy to the PCRF to the integrated TDF PCEF, or the PCEF and the independent TDF, or the independent TDF. In the case, the PCEF of the integrated TDF, or the PCEF and the independent TDF, or the independent TDF perform usage monitoring according to the usage monitoring policy.
进一步地, 用量监控策略具体包括以下任意一种或至少一种的组合: 设置监测键; Further, the usage monitoring strategy specifically includes any one or a combination of at least one of the following: Set the monitor button;
设置应用标识;  Set the application ID;
设置用于触发监测键或应用标识的事件触发器;  Set an event trigger to trigger a monitor key or application ID;
设置用量阀值。  Set the usage threshold.
二、 对应于上述第二套方案的两个方法, 这里的***主要包括以下两方面内容: ***一、 一种支持流检测功能的用量监控***, 在独立的 TDF架构下执行 IP-CAN 级别用量监控的情况下, 该***包括: 用量监测单元和用量修正单元; 其中, 用量监测 单元用于 PCEF对 IP-CAN级别用量进行监控;用量修正单元用于 TDF对丢弃用量进行 监控并统计, 将统计的丢弃用量上报给 PCRF; 所述 PCRF根据 TDF上报的所述丢弃用 量修正 PCEF上报的 IP-CAN级别用量的误差。  Second, corresponding to the two methods of the second set of solutions, the system here mainly includes the following two aspects: System 1, a usage monitoring system supporting flow detection function, performing IP-CAN level usage under an independent TDF architecture In the case of monitoring, the system includes: a quantity monitoring unit and a quantity correction unit; wherein, the quantity monitoring unit is used for monitoring the IP-CAN level usage by the PCEF; the quantity correction unit is used for monitoring and counting the discarded quantity by the TDF, and the statistics will be The discarding amount is reported to the PCRF; the PCRF corrects the error of the IP-CAN level usage reported by the PCEF according to the discarding amount reported by the TDF.
***二、 一种支持流检测功能的用量监控***, 在独立的 TDF架构下执行 IP-CAN 级别用量监控的情况下, 该***包括: 用量监测单元, 用于 PCEF不对 IP-CAN级别用 量进行监控时, 所述 TDF对 IP-CAN级别用量进行监控并上报用量给 PCRF。  System 2: A usage monitoring system supporting flow detection function, in the case of performing IP-CAN level usage monitoring under an independent TDF architecture, the system includes: a usage monitoring unit for PCEF not monitoring IP-CAN level usage The TDF monitors the amount of the IP-CAN level and reports the amount to the PCRF.
进一步地,丢弃用量的类型具体包括: 时间、和 /或流量、和 /或事件; 对应触发 TDF 上报丢弃用量的用量上报阀值的类型包括: 时间的上报阀值、和 /或流量的上报阀值、和 /或事件的上报阀值。  Further, the type of discarding amount specifically includes: time, and/or flow rate, and/or event; and the type of the reporting threshold value corresponding to triggering the TDF reporting discarding amount includes: a reporting threshold of time, and/or a reporting valve of the flow rate The value of the value, and/or the reported threshold of the event.
进一步地, 丢弃用量具体为: 在 TDF实行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF上的 IP-CAN级别用量监控已统计过的用量。  Further, the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage on the PCEF monitors the counted usage.
进一步地, 该***还包括触发及上报单元, 有以下三种具体实现:  Further, the system further includes a triggering and reporting unit, which has the following three specific implementations:
具体实现一: 触发及上报单元用于 IP-CAN会话过程中, 当达到用量上报阀值时触 发 TDF的用量上报, TDF上报丢弃用量给 PCRF。  The specific implementation is as follows: When the triggering and reporting unit is used in the IP-CAN session, when the usage threshold is reached, the TDF usage is reported, and the TDF reports the discarding amount to the PCRF.
具体实现二: IP-CAN会话过程中, PCRF发现对 UE的用量监控达到用量上报阀值 且存在 IP-CAN级别的用量监控、或者 IP-CAN级别的用量监控停止时触发 TDF的用量 上报, PCRF先向 TDF发送获取丢弃用量的上报指示, TDF再向 PCRF上报丢弃用量。  Specific implementation 2: During the IP-CAN session, the PCRF finds that the usage monitoring of the UE reaches the usage reporting threshold and the IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops triggering the TDF usage report, PCRF The TDF sends a report indicating the discarding amount to the TDF, and the TDF reports the discarding amount to the PCRF.
具体实现三: 当 IP-CAN会话结束时触发 TDF的用量上报, TDF直接向 PCRF上 报所述丢弃用量。  The specific implementation is as follows: When the IP-CAN session ends, the usage of the TDF is triggered, and the TDF directly reports the discarded usage amount to the PCRF.
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保护范围。  The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

权利要求书 Claim
1、 一种支持流检测功能的用量监控方法, 其特征在于, 该方法包括: A method for monitoring usage of a flow detection function, the method comprising:
策略控制与计费规则功能实体( PCRF ) 向集成流检测功能 ( TDF ) 的策略和计费 执行功能实体(PCEF;)、 或 PCEF和独立的 TDF、 或独立的 TDF下发应用对应的用量 监控策略;  Policy Control and Charging Rules Function Entity (PCRF) delivers usage monitoring to the Integrated Flow Detection Function (TDF) Policy and Charging Enforcement Function Entity (PCEF;), or PCEF and independent TDF, or standalone TDF Strategy
所述集成 TDF的 PCEF、 或所述 PCEF和独立的 TDF、 或所述独立的 TDF根据所 述用量监控策略执行用量监测。  The PCEF of the integrated TDF, or the PCEF and the independent TDF, or the independent TDF performs usage monitoring based on the usage monitoring policy.
2、 根据权利要求 1 所述的方法, 其特征在于, 所述用量监控策略具体包括以下任 意一种或至少一种的组合:  2. The method according to claim 1, wherein the usage monitoring policy specifically comprises any one or a combination of at least one of the following:
设置监测键;  Set the monitor button;
设置应用标识;  Set the application ID;
设置用于触发监测键或应用标识的事件触发器;  Set an event trigger to trigger a monitor key or application ID;
设置用量阀值。  Set the usage threshold.
3、 根据权利要求 2所述的方法, 其特征在于, 所述事件触发器的取值具体包括: 用量上报(Usage_Report ); 所述用量阈值小于等于应用相关总允许用量。  The method according to claim 2, wherein the value of the event trigger specifically includes: usage reporting (Usage_Report); the usage threshold is less than or equal to the application-related total allowed usage.
4、 一种支持流检测功能的用量监控***, 其特征在于, 该***包括: 用量监测单 元, 用于在 PCRF向集成 TDF的 PCEF、 或 PCEF和独立的 TDF、 或独立的 TDF下发 应用对应的用量监控策略的情况下, 所述集成 TDF的 PCEF、 或所述 PCEF和独立的 TDF、 或所述独立的 TDF根据所述用量监控策略执行用量监测。  4. A usage monitoring system supporting a flow detection function, characterized in that the system comprises: a usage monitoring unit for transmitting an application corresponding to a PCRF to a PCEF integrated with TDF, or a PCEF and an independent TDF, or an independent TDF. In the case of the usage monitoring policy, the PCEF of the integrated TDF, or the PCEF and the independent TDF, or the independent TDF performs usage monitoring according to the usage monitoring policy.
5、 根据权利要求 4所述的***, 其特征在于, 所述用量监控策略具体包括以下任 意一种或至少一种的组合:  The system according to claim 4, wherein the usage monitoring policy specifically comprises any one or a combination of at least one of the following:
设置监测键;  Set the monitor button;
设置应用标识;  Set the application ID;
设置用于触发监测键或应用标识的事件触发器;  Set an event trigger to trigger a monitor key or application ID;
设置用量阀值。  Set the usage threshold.
6、 一种支持流检测功能的用量监控方法, 其特征在于, 该方法包括:  6. A method for monitoring usage of a flow detection function, the method comprising:
独立的 TDF架构下执行 IP连接接入网( IP-CAN )级别用量监控时, PCEF对 IP-CAN 级别用量进行监控, 所述 TDF对丢弃用量进行监控并统计, 将统计的丢弃用量上报给 PCRF; 所述 PCRF根据 TDF上报的所述丢弃用量修正 PCEF上报的 IP-CAN级别用量 的误差; 或者, 独立的 TDF架构下执行 IP-CAN级别用量监控时, PCEF不对 IP-CAN级别 用量进行监控, 所述 TDF对 IP-CAN级别用量进行监控并上报用量给 PCRF。 When the IP-CAN access level monitoring is performed in the independent TDF architecture, the PCEF monitors the IP-CAN level usage. The TDF monitors and collects the discarding usage, and reports the discarded discarding amount to the PCRF. The PCRF corrects the error of the IP-CAN level usage reported by the PCEF according to the discarding amount reported by the TDF; Alternatively, when the IP-CAN level usage monitoring is performed under the independent TDF architecture, the PCEF does not monitor the IP-CAN level usage, and the TDF monitors the IP-CAN level usage and reports the usage amount to the PCRF.
7、 根据权利要求 6所述的方法, 其特征在于, 所述丢弃用量的类型具体包括: 时 间、 和 /或流量、 和 /或事件; 对应触发 TDF上报丢弃用量的用量上报阀值的类型包括: 时间的上报阀值、 和 /或流量的上报阀值、 和 /或事件的上报阀值。  The method according to claim 6, wherein the type of the discarding amount specifically includes: a time, and/or a flow rate, and/or an event; and the type of the usage threshold threshold corresponding to triggering the TDF reporting discarding amount includes: : The reported threshold for the time, and/or the reported threshold for the flow, and/or the reported threshold for the event.
8、 根据权利要求 6所述的方法, 其特征在于, 所述丢弃用量具体为: 在 TDF实行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF上的 IP-CAN级别用量监控已统计过 的用量。  The method according to claim 6, wherein the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage monitoring on the PCEF has been counted. The amount used.
9、 根据权利要求 7所述的方法, 其特征在于, 该方法还包括: 触发所述 TDF将统 计的所述丢弃用量上报给所述 PCRF;所触发的 TDF将统计的所述丢弃用量上报给 PCRF 具体包括:  The method according to claim 7, wherein the method further comprises: triggering the TDF to report the discarded usage amount to the PCRF; and the triggered TDF reports the discarded usage amount to the The PCRF specifically includes:
IP-CAN会话过程中, 当达到所述用量上报阀值时, 所述 TDF上报所述丢弃用量给 所述 PCRF;  During the IP-CAN session, when the usage report threshold is reached, the TDF reports the discarding amount to the PCRF;
或者, IP-CAN会话过程中, 所述 PCRF发现对 UE的用量监控达到所述用量上报 阀值且存在 IP-CAN级别的用量监控、或者所述 IP-CAN级别的用量监控停止时, PCRF 先向所述 TDF发送获取丢弃用量的上报指示, TDF再向 PCRF上报所述丢弃用量; 或者, 当 IP-CAN会话结束时, 所述 TDF向 PCRF上报所述丢弃用量。  Alternatively, during the IP-CAN session, the PCRF finds that when the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops, the PCRF first And sending, by the TDF, the reporting of the discarding amount, and the TDF reporting the discarding amount to the PCRF; or, when the IP-CAN session ends, the TDF reports the discarding amount to the PCRF.
10、 根据权利要求 7 所述的方法, 其特征在于, 所述用量上报阀值具体包括: 由 TDF预配置的阈值、 或由 PCRF下发给 TDF的阈值; 且当所述由 TDF预配置的阈值和 所述由 PCRF下发给 TDF的阈值同时存在时, 优选釆用所述由 PCRF下发给 TDF的阈 值。  The method according to claim 7, wherein the usage reporting threshold specifically includes: a threshold pre-configured by the TDF, or a threshold sent by the PCRF to the TDF; and when the TDF is pre-configured When the threshold and the threshold sent by the PCRF to the TDF are simultaneously present, the threshold value issued by the PCRF to the TDF is preferably used.
11、 一种支持流检测功能的用量监控***, 其特征在于, 独立的 TDF 架构下执行 IP-CAN级别用量监控的情况, 该***包括: 用量监测单元和用量修正单元; 其中, 所述用量监测单元, 用于 PCEF对 IP-CAN级别用量进行监控;  11. A usage monitoring system supporting a flow detection function, characterized in that, in an independent TDF architecture, an IP-CAN level usage monitoring is performed, the system comprising: a usage monitoring unit and a usage correction unit; wherein, the usage monitoring Unit for PCEF to monitor IP-CAN level usage;
所述用量修正单元, 用于 TDF对丢弃用量进行监控并统计, 将统计的丢弃用量上 报给 PCRF; 所述 PCRF根据 TDF上报的所述丢弃用量修正 PCEF上报的 IP-CAN级别 用量的误差;  The usage correction unit is configured to monitor and collect the discarded usage amount by the TDF, and report the discarded usage amount to the PCRF; the PCRF corrects the error of the IP-CAN level used by the PCEF according to the discarded usage reported by the TDF;
或者, 独立的 TDF架构下执行 IP-CAN级别用量监控的情况, 该***包括: 用量监 测单元, 用于 PCEF不对 IP-CAN级别用量进行监控时, 所述 TDF对 IP-CAN级别用量 进行监控并上报用量给 PCRF。  Or, in the case of performing IP-CAN level usage monitoring under a separate TDF architecture, the system includes: a usage monitoring unit, wherein when the PCEF does not monitor the IP-CAN level usage, the TDF monitors the IP-CAN level usage and Report the dosage to the PCRF.
12、 根据权利要求 11 所述的***, 其特征在于, 所述丢弃用量的类型具体包括: 时间、和 /或流量、和 /或事件;对应触发 TDF上报丢弃用量的用量上报阀值的类型包括: 时间的上报阀值、 和 /或流量的上报阀值、 和 /或事件的上报阀值。 The system according to claim 11, wherein the type of the discarding amount specifically includes: Time, and/or flow, and/or event; the type of escalation threshold corresponding to triggering the TDF reporting discard usage includes: time reporting threshold, and/or reporting threshold for flow, and/or reporting threshold for event .
13、 根据权利要求 11所述的***, 其特征在于, 所述丢弃用量具体为: 在 TDF实 行 IP-CAN会话的流控功能时丢弃的用量, 但 PCEF上的 IP-CAN级别用量监控已统计 过的用量。  The system according to claim 11, wherein the discarding amount is specifically: the amount discarded when the TDF implements the flow control function of the IP-CAN session, but the IP-CAN level usage monitoring on the PCEF has been counted. The amount used.
14、 根据权利要求 12所述的***, 其特征在于, 该***还包括: 触发及上报单元, 用于 IP-CAN会话过程中, 当达到所述用量上报阀值时触发 TDF的用量上报,所述 TDF 上报所述丢弃用量给所述 PCRF;  The system according to claim 12, wherein the system further comprises: a triggering and reporting unit, configured to trigger the TDF usage report when the usage threshold is reached during the IP-CAN session, The TDF reports the discarding amount to the PCRF;
或者, IP-CAN会话过程中, 所述 PCRF发现对 UE的用量监控达到所述用量上报 阀值且存在 IP-CAN级别的用量监控、或者所述 IP-CAN级别的用量监控停止时触发 TDF 的用量上报, PCRF先向所述 TDF发送获取丢弃用量的上报指示, TDF再向 PCRF上报 所述丢弃用量;  Alternatively, during the IP-CAN session, the PCRF finds that the usage monitoring of the UE reaches the usage reporting threshold and there is an IP-CAN level usage monitoring, or the IP-CAN level usage monitoring stops triggering the TDF. When the usage is reported, the PCRF first sends an indication to the TDF to obtain the discarded usage amount, and the TDF reports the discarded usage amount to the PCRF.
或者, 当 IP-CAN会话结束时触发 TDF的用量上报, 所述 TDF向 PCRF上报所述 丢弃用量。  Alternatively, when the IP-CAN session ends, the usage of the TDF is triggered, and the TDF reports the discarding amount to the PCRF.
PCT/CN2011/084358 2011-01-31 2011-12-21 Usage monitoring method and system supporting traffic detection function WO2012103770A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110034149.8 2011-01-31
CN201110034149.8A CN102625272B (en) 2011-01-31 2011-01-31 A kind of consumption monitoring method and system for supporting current detection functionality

Publications (1)

Publication Number Publication Date
WO2012103770A1 true WO2012103770A1 (en) 2012-08-09

Family

ID=46564919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084358 WO2012103770A1 (en) 2011-01-31 2011-12-21 Usage monitoring method and system supporting traffic detection function

Country Status (2)

Country Link
CN (1) CN102625272B (en)
WO (1) WO2012103770A1 (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103781041B (en) * 2012-10-18 2019-02-26 中兴通讯股份有限公司 Charging synchronous method, apparatus and system
CN103841538B (en) * 2012-11-22 2019-06-25 中兴通讯股份有限公司 Manage the method and system of data flow
CN103856926A (en) * 2012-11-28 2014-06-11 中兴通讯股份有限公司 Charging method and strategy execution, strategy and charging control function device
CN104221418B (en) 2013-01-15 2018-07-31 华为技术有限公司 The method and apparatus of charging
CN103945359B (en) * 2013-01-18 2018-12-25 中兴通讯股份有限公司 A kind of processing method of business datum, device and system
CN105519151B (en) * 2013-05-31 2019-10-22 华为技术有限公司 Policy control method and network side equipment
WO2014198016A1 (en) * 2013-06-09 2014-12-18 华为技术有限公司 Method, device and system for flow monitoring
CN104769978B (en) * 2013-09-18 2019-02-19 华为技术有限公司 Charging method and equipment
CN103533070A (en) * 2013-10-22 2014-01-22 华为技术有限公司 Service synchronization method, content management equipment and strategy management equipment
CN105591828A (en) * 2014-10-20 2016-05-18 中兴通讯股份有限公司 Traffic monitoring method and device
CN106341804B (en) * 2015-07-08 2020-11-20 中兴通讯股份有限公司 Control method for application characteristic rule and application characteristic server
CN106998543A (en) * 2016-01-25 2017-08-01 中兴通讯股份有限公司 Third-party application access method and device
EP3425992B1 (en) * 2016-03-31 2020-11-04 Huawei Technologies Co., Ltd. Event reporting method and device
CN107786315B (en) * 2016-08-29 2021-11-12 中兴通讯股份有限公司 Usage quota authorization method and device
CN107979707B (en) * 2016-10-21 2020-02-21 中国电信股份有限公司 Method, platform and system for improving network disconnection control precision
CN108064032A (en) * 2016-11-07 2018-05-22 中兴通讯股份有限公司 A kind of application detects control method and device
CN110324800B (en) * 2018-03-30 2021-01-29 华为技术有限公司 Policy control method, network element and system
CN110769455B (en) 2018-07-26 2022-05-31 华为技术有限公司 Data collection method, equipment and system
CN111436030B (en) * 2019-01-15 2022-04-05 华为技术有限公司 Method, device and system for reporting data usage

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (en) * 2007-04-26 2008-10-29 华为技术有限公司 Method, system and equipment for establishing user conversation bearer service
CN101369917A (en) * 2007-08-17 2009-02-18 华为技术有限公司 Method, system and apparatus for expanding policy and charging control rules
CN101730048A (en) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 Method and system for transmitting information

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001402B (en) * 2006-01-10 2010-10-06 华为技术有限公司 Mobile communication system and method of using attaching network application function service
DE602007005460D1 (en) * 2007-04-30 2010-05-06 Nokia Siemens Networks Oy Policy control in a network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (en) * 2007-04-26 2008-10-29 华为技术有限公司 Method, system and equipment for establishing user conversation bearer service
CN101369917A (en) * 2007-08-17 2009-02-18 华为技术有限公司 Method, system and apparatus for expanding policy and charging control rules
CN101730048A (en) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 Method and system for transmitting information

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP TS 23.203 V11.0.0, 31 December 2010 (2010-12-31) *

Also Published As

Publication number Publication date
CN102625272B (en) 2017-03-29
CN102625272A (en) 2012-08-01

Similar Documents

Publication Publication Date Title
WO2012103770A1 (en) Usage monitoring method and system supporting traffic detection function
US9191960B2 (en) Methods and apparatus for mitigating service interruption
EP2443865B1 (en) Establishing a communication session
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
JP5642888B2 (en) Method and system for realizing application detection and control in an IP-CAN session supporting dual stack
WO2011060698A1 (en) Method and system for realizing usage monitoring control
WO2011063722A1 (en) Method and system for implementing usage monitoring control
WO2011079773A1 (en) Method, device and system for controlling user session policy
WO2010072107A1 (en) User service flow charge deducting method and device
WO2011063688A1 (en) Method and system for selecting policy and charging rules function entity
WO2012075875A1 (en) Method and system for signing and enforcing spending limit service
WO2011085614A1 (en) Method for controlling resources in full service converged network and system therefor
WO2014172858A1 (en) Method for charging for application, and charging device and system
WO2015143856A1 (en) Method for application detection and control in roaming scenario and v-pcrf
WO2006012798A1 (en) A method for processing the re-authorisation based on the charging of the packet data flow
US9820183B2 (en) User plane congestion control
WO2015143851A1 (en) Usage monitoring method, apparatus and system
WO2014094488A1 (en) Charging policy method and device for roaming local service
WO2009056046A1 (en) A method for session termination
WO2011088702A1 (en) Method and system for controlling resources in full-service convergence network
WO2012129992A1 (en) Sponsored data connectivity processing method, and policy and charging rules function
WO2010118673A1 (en) Method, system and device for processing policy and charging control
WO2012041150A1 (en) Volume usage monitoring method and policy control and charging rules functional entity
WO2011026409A1 (en) Session updating method, apparatus and system
WO2009117932A1 (en) Method of policy control and device therefor

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

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

Country of ref document: EP

Kind code of ref document: A1