WO2012103770A1 - Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic - Google Patents

Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic 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
English (en)
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/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5029—Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/028—Capturing 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

La présente invention concerne un procédé et un système de contrôle d'utilisation servant de support à une fonction de détection du trafic. Une solution consiste en la distribution par une fonction de règles et de politique de facturation (PCRF) de politique de contrôle d'utilisation correspondant à une application à une fonction d'application de politique de facturation (PCEF) intégrée à fonction de détection de trafic (TDF), ou une fonction PCEF et une fonction TDF séparée, ou une fonction TDF séparée; et la réalisation par la fonction PCEF intégrée à une fonction TDF, ou par la fonction PCEF et la fonction TDF séparée d'un contrôle d'utilisation selon la politique de contrôle d'utilisation. Ainsi, il est possible de résoudre le problème de l'incapacité de la fonction PCRF de contrôler l'utilisation au niveau des flux de données de service d'un modèle de service de flux de données lors du contrôle d'utilisation. Un autre procédé dans une autre solution selon la présente invention comprend les étapes suivantes: lors d'un contrôle à un niveau d'un réseau d'accès de connectivité IP (IP-CAN) dans une architecture de fonction TDF séparée, la réalisation par une fonction PCEF de contrôle d'utilisation au niveau du réseau IP-CAN, et le contrôle et le calcul d'utilisation rejetée par une fonction TDF, et la notification d'utilisation rejetée calculée à une fonction PCRF; et la correction par la fonction PCRF, en fonction de l'utilisation rejetée rapportée par la fonction TDF, d'une erreur dans l'utilisation au niveau du réseau IP-CAN rapportée par la fonction PCEF. Ainsi, il est possible de résoudre le problème de commande de contrôle d'utilisation au niveau du réseau IP-CAN dans l'architecture de fonction TDF lors du contrôle d'utilisation.
PCT/CN2011/084358 2011-01-31 2011-12-21 Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic WO2012103770A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110034149.8A CN102625272B (zh) 2011-01-31 2011-01-31 一种支持流检测功能的用量监控方法及***
CN201110034149.8 2011-01-31

Publications (1)

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

Family

ID=46564919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/084358 WO2012103770A1 (fr) 2011-01-31 2011-12-21 Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic

Country Status (2)

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

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103781041B (zh) * 2012-10-18 2019-02-26 中兴通讯股份有限公司 计费同步方法、装置及***
CN103841538B (zh) * 2012-11-22 2019-06-25 中兴通讯股份有限公司 管理数据流的方法和***
CN103856926A (zh) * 2012-11-28 2014-06-11 中兴通讯股份有限公司 一种计费方法以及策略执行、策略和计费控制功能设备
EP2947906B1 (fr) 2013-01-15 2017-09-20 Huawei Technologies Co., Ltd. Procédé et dispositif de facturation
CN103945359B (zh) * 2013-01-18 2018-12-25 中兴通讯股份有限公司 一种业务数据的处理方法、装置和***
CN105519151B (zh) * 2013-05-31 2019-10-22 华为技术有限公司 策略控制方法和网络侧设备
WO2014198016A1 (fr) * 2013-06-09 2014-12-18 华为技术有限公司 Procédé, dispositif et système de surveillance de flux
WO2015039307A1 (fr) * 2013-09-18 2015-03-26 华为技术有限公司 Procédé et dispositif de facturation
CN103533070A (zh) * 2013-10-22 2014-01-22 华为技术有限公司 业务同步方法、内容管理设备及策略管理设备
CN105591828A (zh) * 2014-10-20 2016-05-18 中兴通讯股份有限公司 用量监控方法及装置
CN106341804B (zh) * 2015-07-08 2020-11-20 中兴通讯股份有限公司 一种应用特征规则的控制方法及应用特征服务器
CN106998543A (zh) * 2016-01-25 2017-08-01 中兴通讯股份有限公司 第三方应用访问方法及装置
WO2017166194A1 (fr) * 2016-03-31 2017-10-05 华为技术有限公司 Procédé et dispositif de rapport d'événement
CN107786315B (zh) * 2016-08-29 2021-11-12 中兴通讯股份有限公司 一种用量配额的授权方法及装置
CN107979707B (zh) * 2016-10-21 2020-02-21 中国电信股份有限公司 用于提升断网控制精度的方法、平台和***
CN108064032A (zh) * 2016-11-07 2018-05-22 中兴通讯股份有限公司 一种应用检测控制方法及装置
CN110324800B (zh) 2018-03-30 2021-01-29 华为技术有限公司 一种策略控制的方法、网元及***
CN110769455B (zh) 2018-07-26 2022-05-31 华为技术有限公司 一种数据收集方法、设备及***
CN111436030B (zh) * 2019-01-15 2022-04-05 华为技术有限公司 数据用量上报的方法、装置及***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (zh) * 2007-04-26 2008-10-29 华为技术有限公司 一种用户会话承载业务建立方法、***及设备
CN101369917A (zh) * 2007-08-17 2009-02-18 华为技术有限公司 扩展策略和计费控制规则的方法、***及装置
CN101730048A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 一种信息传输方法及***

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001402B (zh) * 2006-01-10 2010-10-06 华为技术有限公司 移动通信***及使用归属网络应用功能业务的方法
ATE462266T1 (de) * 2007-04-30 2010-04-15 Nokia Siemens Networks Oy Richtlinienkontrolle in einem netzwerk

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (zh) * 2007-04-26 2008-10-29 华为技术有限公司 一种用户会话承载业务建立方法、***及设备
CN101369917A (zh) * 2007-08-17 2009-02-18 华为技术有限公司 扩展策略和计费控制规则的方法、***及装置
CN101730048A (zh) * 2009-06-26 2010-06-09 中兴通讯股份有限公司 一种信息传输方法及***

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
CN102625272A (zh) 2012-08-01
CN102625272B (zh) 2017-03-29

Similar Documents

Publication Publication Date Title
WO2012103770A1 (fr) Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic
US9191960B2 (en) Methods and apparatus for mitigating service interruption
EP2443865B1 (fr) Établissement d'une session de communication
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
JP5642888B2 (ja) デュアルスタックをサポートするｉｐ−ｃａｎセッションにおいてアプリケーション検出及び制御を実現する方法及びシステム
WO2011060698A1 (fr) Procédé et système de réalisation de contrôle de surveillance d'utilisation
WO2011063722A1 (fr) Procédé et système de mise en œuvre de commande de surveillance d'utilisation
WO2011079773A1 (fr) Procédé, dispositif et système destinés à commander une police de séance d'utilisateur
WO2010072107A1 (fr) Procédé et dispositif de déduction de facture de flux de service d'utilisateur
WO2011063688A1 (fr) Procédé et système de sélection d'entité à fonction de règles de politique et de facturation
WO2012075875A1 (fr) Procédé et système permettant l'enregistrement et la mise en application d'un service de limitation des dépenses
WO2011085614A1 (fr) Procédé de gestion de ressources dans un réseau convergent à service complet et système correspondant
WO2014172858A1 (fr) Procédé de facturation pour application, et dispositif et système de facturation
WO2015143856A1 (fr) Procédé de détection et le contrôle d'application dans un scénario d'itinérance et une v-pcrf
WO2006012798A1 (fr) Procede de traitement de reautorisation a base de taxation du flux de donnees par paquets
US9820183B2 (en) User plane congestion control
WO2015143851A1 (fr) Procédé, appareil et système de surveillance d'utilisation
WO2014094488A1 (fr) Procédé et dispositif de gestion de politique de facturation destinés à un service local d'itinérance
WO2009056046A1 (fr) Procédé de fin de session
WO2011088702A1 (fr) Procédé et système permettant de contrôler des ressources dans un réseau de convergence multiservice
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2010118673A1 (fr) Procédé, système et dispositif de gestion du contrôle des règles d'utilisation et de facturation
WO2012041150A1 (fr) Procédé de contrôle de l'utilisation du volume de ressources et fonction de règles de contrôle de politique et de taxation
WO2011026409A1 (fr) Procédé, appareil et système de mise à jour de session
WO2009117932A1 (fr) Procédé de contrôle des règles, et dispositif associé

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