WO2014110966A1 - Procédé, appareil et système permettant de traiter des données de trafic - Google Patents

Procédé, appareil et système permettant de traiter des données de trafic Download PDF

Info

Publication number
WO2014110966A1
WO2014110966A1 PCT/CN2013/090771 CN2013090771W WO2014110966A1 WO 2014110966 A1 WO2014110966 A1 WO 2014110966A1 CN 2013090771 W CN2013090771 W CN 2013090771W WO 2014110966 A1 WO2014110966 A1 WO 2014110966A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcef
tdf
discarded
packet
data packets
Prior art date
Application number
PCT/CN2013/090771
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 WO2014110966A1 publication Critical patent/WO2014110966A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport
    • 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

Definitions

  • the present invention relates to the field of policy and charging control technologies for mobile communications, and in particular to a service
  • the PCC architecture is a functional framework that can be applied to multiple access technologies.
  • the PCC architecture can be applied to the Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (UMTS Terrestrial Radio Access Network, UTRAN).
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network
  • GSM Global System for Mobile Communication
  • RFID GSM Data Enhanced for GSM Evolution
  • I-WLAN Interworking Wireless
  • EPS Evolved Packet System
  • Figure 1 is a schematic diagram of the composition of the existing Rel-11 PCC. The following describes the logical functional entities and their interface functions in the PCC architecture shown in Figure 1:
  • AF Application Function
  • PCRF Policy and Charging Rules Function
  • the policy control and charging rule function entity may also be called policy control and Billing rules function device. If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation, and The business parameters acceptable to the PCRF are given at the time of feedback. The AF can then return these parameters to the User Equipment (UE).
  • UE User Equipment
  • the interface between the AF and the PCRF is an Rx interface.
  • the PCRF is the core of the PCC and is configured to be responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including network service 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 Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • the basis for the PCRF to formulate policies and charging rules includes: business-related information obtained from AF, subscription information of users obtained from the Subscription Profile Repository (SPR), and obtained from the PCEF through the Gx interface. Carry information about the relevant network.
  • SPR Subscription Profile Repository
  • the PCEF is usually located in the Gateway (GW), such as the Packet Data Network Gateway (PDN-GW) of the EPS and the GPRS Gateway Support Node in the General Packet Radio Service (GPRS).
  • the Gateway GPRS Support Node (GGSN) and the Packet Data Gateway (PDG) in the I-WLAN perform the policy and charging rules defined by the PCRF on the bearer plane.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then 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.
  • Billing can be either online charging or offline charging.
  • the PCEF needs to perform credit management together with the Online Charging System (OCS); when offline charging, the PCEF and the Offline Charging System (OFCS) exchange related calculations.
  • OCS Online Charging System
  • OFCS Offline Charging System
  • Fee information The interface between the PCEF and the PCRF is a Gx interface, PCEF.
  • the interface between the OCS and the OCS is the Gy interface, and the interface between the PCEF and the OFCS is the Gz interface.
  • the PCEF can also have an Application Detection and Control Function (ADC).
  • ADC Application Detection and Control Function
  • the PCEF can perform application detection and perform grid execution (such as gating, redirection, and bandwidth limitation) according to the local configuration or the application detection and control (ADC) issued by the PCRF.
  • the ADC can also be deployed as a Traffic Detection Function (TDF).
  • TDF Traffic Detection Function
  • the TDF and the PCRF are connected through the Sd interface.
  • the TDF can perform application detection and policy execution according to the pre-configured or PCR rules delivered by the PCRF.
  • the Bearer Binding and Event Reporting Function is usually located in the Access Network Gateway.
  • the Bearer Binding and Event Reporting Function is usually located in the Access Network Gateway.
  • PMIPv6 Proxy Mobile Internet Protocol version 6
  • the S-GW There is a BBERF.
  • a BBERF is also present 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 PCEF performs service data flow (SDF) level charging, for the uplink data, after the PCEF performs charging according to the PCC rule, when the uplink data packet passes the TDF, the TDF may be according to the ADC rule. Control the packet, such as packet loss or redirection. As a result, the PCEF does not accurately charge the uplink data. Similarly, if the PCEF performs usage monitoring at the service data flow level, it will also lead to inaccurate usage monitoring.
  • SDF service data flow
  • TDF performs application (Application) level accounting, for downstream data
  • the PCEF may control the data packet according to the PCC rule, such as packet loss or redirection.
  • the TDF charges the downlink data inaccurately.
  • the TDF performs application level usage monitoring, it will also lead to inaccurate usage monitoring.
  • the TDF marks each downstream packet that is billed. As shown in the figure, packets A, B, and C are charged by TDF, and TDF sets the charging keys X, X, and Y for packets A, B, and C, respectively, and counts Charging Key X, Y. The fee information is reported to OCS. After the packet arrives at the PCEF, the PCEF discards the packet A, and the PCEF counts it into the packet discarded by the Charging Key X.
  • the PCEF After that, the PCEF notifies the OCS Charging Key X of the discarded packet's charging information, so that the OCS can The billing information corresponding to the packets discarded by the PCEF is deducted from the billing information of the user.
  • the scheme for performing SDF-level accounting is similar to the scheme for performing application-level accounting, and is not mentioned here.
  • TDF needs to mark the packets that have been billed. It can be marked in the encapsulated packet header after additional encapsulation outside the packet, which increases system overhead.
  • the main purpose of the embodiments of the present invention is to provide a method, a device, and a system for processing service data, which can accurately perform billing and usage monitoring without increasing system overhead and OCS implementation complexity.
  • An embodiment of the present invention provides a method for processing traffic data, where the method includes: The service detection function entity (TDF) determines the data packet to be discarded in the data packet sent by the policy and charging execution function entity (PCEF) according to the policy installed by itself, and sends the determined discarded data packet to the PCEF.
  • the PCEF verifies the billing and/or usage corresponding to the discarded data packet; or
  • the PCEF determines, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the TDF, and sends the determined discarded data packet to the TDF; the TDF core reduces the charging corresponding to the discarded data packet. And / or dosage.
  • the method further includes:
  • the sending the determined discarded data packet to the PCEF is:
  • the method further includes:
  • the sending the determined discarded data packet to the TDF is:
  • the selected dropped data packet is sent to the TDF.
  • the sending the determined discarded data packet to the PCEF is:
  • IP Internet Protocol
  • the discarded data packet is encapsulated in an IP packet whose source address is PCEF and whose destination address is TDF, and the IP packet is sent to the TDF in a tunnel manner.
  • the method further includes:
  • PCEF policy control and charging rule function entity
  • the method further includes: an Internet Protocol Connection Access Network (IP-CAN) session establishment confirmation message carrying the TDF address sent from the PCRF or a fixed configuration Get the TDF address.
  • IP-CAN Internet Protocol Connection Access Network
  • the method before the determining, in the data packet sent by the PCEF, the data packet to be discarded, the method further includes:
  • the TDF performs an application detection and control (ADC) rule on the received data packet, and applies the billing and/or usage monitoring data packet to the billing flag and/or the usage monitoring flag, and processes the processed data packet. Issued to the PCEF; or,
  • the method further includes:
  • the PCEF performs a Policy and Charging Control (PCC) rule on the received data packet, and applies the charging and/or usage monitoring data packet to the charged charging flag and/or the usage monitoring flag, and the processed data is processed.
  • PCC Policy and Charging Control
  • the method further includes:
  • the PCEF decapsulates the IP packet sent by the TDF to obtain a discarded data packet
  • the method further includes:
  • the TDF decapsulates the IP packet sent by the PCEF to obtain a discarded data packet.
  • An embodiment of the present invention further provides a TDF, where the TDF includes: The discarding data packet determining unit is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the PCEF;
  • the data packet sending unit is configured to send the discarded data packet determined by the discarded data packet determining unit to the PCEF.
  • the embodiment of the present invention further provides a PCEF, where the PCEF includes:
  • a data packet receiving unit configured to receive a discarded data packet sent by the TDF
  • the decrement unit is configured to reduce the billing and/or usage corresponding to the discarded data packet received by the data packet receiving unit.
  • the embodiment of the present invention further provides a PCEF, where the PCEF includes:
  • the drop packet determining unit is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the discarded data packet sent by the TDF;
  • the data packet sending unit is configured to send the discarded data packet determined by the discarded data packet determining unit to the TDF.
  • An embodiment of the present invention further provides a TDF, where the TDF includes:
  • a data packet receiving unit configured to receive a discarded data packet sent by the PCEF
  • the decrement unit is configured to reduce the billing and/or usage corresponding to the discarded data packet received by the data packet receiving unit.
  • the embodiment of the invention further provides a processing system for service data, the system comprising:
  • the TDF is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the PCEF, and send the determined discarded data packet to the PCEF;
  • the PCEF is configured to receive the discarded data packet sent by the TDF, and reduce the charging and/or usage corresponding to the discarded data packet;
  • the PCEF is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the TDF, and send the determined discarded data packet to the TDF;
  • the TDF is configured to receive the discarded data packet sent by the PCEF, and reduce the discarded data packet pair.
  • the TDF is further configured to select, from the data packets that need to be discarded, the discarded data packet with the charged charging flag and/or the used usage monitoring; and send the selected discarded data packet to the PCEF; or ,
  • the PCEF is further configured to select, from the data packets that need to be discarded, the discarded data packet with the charged charging flag and/or the usage monitoring; and send the selected discarded data packet to the TDF.
  • the TDF is specifically configured to encapsulate the discarded data packet in an IP packet whose source address is TDF and whose destination address is PCEF, and send the IP packet to the PCEF in a tunnel manner; or
  • the PCEF is specifically configured to encapsulate the discarded data packet in an IP packet whose source address is PCEF and whose destination address is TDF, and send the IP packet to the TDF in a tunnel manner.
  • the TDF is specifically configured to obtain a PCEF address from a TDF session establishment request carrying a PCEF address sent by the PCRF or in a fixed configuration; or
  • the PCEF is specifically configured to obtain a TDF address from an IP-CAN session establishment confirmation message sent by the PCRF or a fixed configuration.
  • the PCEF is further configured to perform a PCC rule on the received data packet, and apply the charging and/or usage monitoring data packet to the charged charging flag and/or the usage monitoring flag, and process the processed data.
  • a packet is sent to the TDF; or,
  • the TDF is further configured to perform an ADC rule on the received data packet, and apply a billing and/or usage monitoring data packet to the billing flag and/or the usage monitoring flag, and send the processed data packet to the TDF.
  • the PCEF is further configured to perform an ADC rule on the received data packet, and apply a billing and/or usage monitoring data packet to the billing flag and/or the usage monitoring flag, and send the processed data packet to the TDF.
  • the technical solution of the embodiment of the present invention includes: a service detection function entity (TDF) determines, according to a policy installed by itself, a data packet that needs to be discarded in a data packet sent by a policy and a charging execution function entity (PCEF), And sending the determined discarded data packet to the PCEF; the PCEF is deducting the charging and/or usage corresponding to the discarded data packet; or, the PCEF is installed according to itself.
  • the policy determines a data packet that needs to be discarded in the data packet sent by the TDF, and sends the determined discarded data packet to the TDF; the TDF core reduces the charging and/or usage corresponding to the discarded data packet. Therefore, the embodiment of the present invention adopts a packet redirection method, and can accurately perform billing and usage monitoring without increasing system overhead and OCS implementation complexity.
  • FIG. 1 is a schematic structural diagram of a PCC of an existing Rel-11
  • FIG. 2 is a schematic diagram of service data processing under the TDF control of the prior art
  • FIG. 3 is a flowchart of an implementation of a method for processing service data according to an embodiment of the present invention
  • FIG. 4 is a flowchart of implementing a method for processing service data according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of service data processing of a second embodiment of a method for processing service data according to the present invention.
  • FIG. 7 is a schematic diagram of service data processing of a fourth embodiment of a method for processing service data according to the present invention.
  • FIG. 8 is a schematic diagram of service data processing of a fifth embodiment of a method for processing service data according to the present invention.
  • FIG. 9 is a flowchart of an implementation of acquiring a TDF address according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of an implementation of acquiring a PCEF address according to an embodiment of the present invention.
  • the embodiments of the present invention provide a method for processing traffic data, as shown in FIG. 3, including the following steps:
  • Step 301 The TDF determines, according to the policy installed by the TDF, the data packet that needs to be discarded in the data packet sent by the PCEF.
  • Step 302 The TDF sends the determined discarded data packet to the PCEF.
  • Step 303 The PCEF core reduces the charging and/or usage corresponding to the discarded data packet.
  • the method may further include:
  • the TDF performs an ADC rule on the received data packet, puts the billing and/or usage monitoring data packet with the billing flag and/or the usage monitoring flag, and sends the processed data packet to the PCEF.
  • the method may further include:
  • the sending the determined discarded data packet to the PCEF is:
  • the sending the determined discarded data packet to the PCEF may be:
  • the discarded data packet is encapsulated in an Internet Protocol (IP) packet whose source address is TDF and whose destination address is PCEF, and the IP packet is tunneled to the PCEF.
  • IP Internet Protocol
  • the sending the determined discarded data packet to the PCEF may be:
  • the PCEF address is obtained from the TDF session establishment request carrying the PCEF address sent from the Policy Control and Charging Rules Function Entity (PCRF) or in the fixed configuration.
  • PCRF Policy Control and Charging Rules Function Entity
  • the method may further include:
  • the PCEF decapsulates the IP packet sent by the TDF to obtain a discarded data packet.
  • the method further includes:
  • the PCEF discards the dropped data packet sent by the TDF.
  • the embodiment of the present invention further provides a method for processing service data. As shown in FIG. 4, the method includes the following steps:
  • Step 401 The PCEF determines, according to the policy installed by the PCEF, the data packet that needs to be discarded in the data packet sent by the TDF.
  • Step 402 The PCEF sends the determined discarded data packet to the TDF.
  • Step 403 The TDF core reduces the charging and/or usage corresponding to the discarded data packet.
  • the method may further include:
  • the PCEF performs a PCC rule on the received data packet, and applies a billing and/or usage monitoring data packet to the billing flag and/or the usage monitoring flag, and sends the processed data packet to the TDF.
  • the method further includes:
  • the sending the determined discarded data packet to the TDF is:
  • the sending the determined discarded data packet to the TDF may be:
  • the discarded data packet is encapsulated in an IP packet whose source address is PCEF and whose destination address is TDF, and the IP packet is tunneled to the TDF.
  • the sending the determined discarded data packet to the TDF may be:
  • the TDF address is obtained from the IPF-enabled Internet Protocol Connection Access Network (IP-CAN) session establishment confirmation message sent by the PCRF or in a fixed configuration.
  • IP-CAN Internet Protocol Connection Access Network
  • the method may further include: The TDF decapsulates the IP packet sent by the PCEF to obtain a discarded data packet.
  • the method further includes:
  • the TDF discards the discarded data packet sent by the PCEF.
  • An embodiment of the present invention provides a TDF, including:
  • the drop packet determining unit is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the PCEF;
  • the data packet sending unit is configured to send the discarded data packet determined by the discarded data packet determining unit to the PCEF.
  • Each unit in this embodiment may be a Central Processing Unit (CPU), a Digital Signal Processor (DSP), or a Field-Programmable Gate Array (FPGA) in the TDF. ) Implementation.
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • FPGA Field-Programmable Gate Array
  • An embodiment of the present invention provides a PCEF, including:
  • a data packet receiving unit configured to receive a discarded data packet sent by the TDF
  • the decrement unit is configured to reduce the billing and/or usage corresponding to the discarded data packet received by the data packet receiving unit.
  • Each unit in this embodiment can be implemented by a CPU, DSP or FPGA in the PCEF.
  • the embodiment of the invention further provides a PCEF, including:
  • the drop packet determining unit is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the discarded data packet sent by the TDF;
  • the data packet sending unit is configured to send the discarded data packet determined by the discarded data packet determining unit to the TDF.
  • Each unit in this embodiment can be implemented by a CPU, DSP or FPGA in the PCEF.
  • the embodiment of the invention further provides a TDF, including:
  • a data packet receiving unit configured to receive a discarded data packet sent by the PCEF;
  • the decrement unit is configured to reduce the billing and/or usage corresponding to the discarded data packet received by the data packet receiving unit.
  • An embodiment of the present invention provides a service data processing system, including:
  • the TDF is configured to determine, according to the policy installed by itself, the data packet that needs to be discarded in the data packet sent by the PCEF, and send the determined discarded data packet to the PCEF.
  • the PCEF is configured to receive the discarded data packet sent by the TDF, and reduce the charging and/or usage corresponding to the discarded data packet.
  • the TDF is further configured to select, from the data packets that need to be discarded, the discarded data packets with the charged charging flag and/or the used usage monitoring.
  • the TDF is specifically configured to encapsulate the discarded data packet at a source address.
  • the IP packet in the IP packet whose destination address is PCEF, the IP packet is tunneled to the
  • the TDF is specifically configured to obtain a PCEF address from a TDF session establishment request carrying a PCEF address sent by the PCRF or in a fixed configuration.
  • the PCEF is further configured to perform a PCC rule on the received data packet, and apply the charging and/or usage monitoring data packet to the charged charging flag and/or the usage monitoring flag, and process the processed data.
  • the packet is sent to the TDF.
  • the embodiment of the present invention further provides a service data processing system, including: a PCEF, configured to determine, according to a policy installed by itself, a data packet to be discarded in a data packet sent by the TDF, and determine the discarded data packet. Send it to TDF,
  • a PCEF configured to determine, according to a policy installed by itself, a data packet to be discarded in a data packet sent by the TDF, and determine the discarded data packet. Send it to TDF,
  • the TDF is configured to receive the discarded data packet sent by the PCEF, and reduce the charging and/or usage corresponding to the discarded data packet.
  • the PCEF is further configured to select, from the data packets that need to be discarded, the discarded data packets with the charged charging flag and/or the used usage monitoring.
  • the PCEF is specifically configured to encapsulate the discarded data packet in an IP packet whose source address is PCEF and whose destination address is TDF, and send the IP packet to the TDF in a tunnel manner.
  • the PCEF is specifically configured to obtain a TDF address in an IP-CAN session establishment confirmation message that carries a TDF address sent by the PCRF or in a fixed configuration.
  • the TDF is further configured to perform an ADC rule on the received data packet, and perform a charging and/or usage monitoring data packet on the charged charging flag and/or the usage monitoring flag, and process the processed data.
  • the packet is sent to the PCEF.
  • This embodiment describes an IP-CAN session for the UE, and only performs application level charging on the TDF.
  • the billing information for the TDF is accurate.
  • the PCEF redirects the data packet discarded according to the PCC rule to the TDF for the TDF to perform the core subtraction.
  • its function examples are described as follows:
  • the TDF receives 4 packets, and the allocation is A, B, C, and D. After TDF performs application detection and control, it does not drop any packets and charges 3 packets of A, B, and C. Assume that A and B belong to the same application and use the charging key Charging KeyX for charging, while C belongs to another application and uses Charging Key Y for charging. There is a billing session between TDF and OCS or OFCS for reporting billing information (including credit control).
  • the PCEF will send the packet A to the TDF.
  • the way PCEF sends packet A to TDF can be tunneled, and packet A is encapsulated at the destination address.
  • TDF the source address is in the IP packet of the PCEF address.
  • the TDF When the TDF receives the data packet with its own address as the destination address, the TDF will decapsulate and obtain the data packet A, and deduct the data related to the data packet A from the Charging Key X charging information. Specifically, the TDF filters the data A according to the filter saved locally when the ADC rule is executed, and can match the Charging Key corresponding to the data packet A to X. After the TDF performs the accounting information reduction on the data packet eight, the data packet A is discarded.
  • the PCEF sends each packet that needs to be discarded to the TDF.
  • some packages may not be billed for TDF, so these packages do not require TDF for deduction. This may result in more unused packets being sent.
  • the TDF can put a special identifier on the packet header sent to the PCEF to indicate that the PCEF is charged by the TDF.
  • the PCEF decides to drop the packet, it judges whether the packet is charged in the TDF based on the identifier. Only when charging is performed, the PCEF sends these packets to the TDF for core deduction of the TDF.
  • the PCEF sends the TDF in the IP packet whose source address is the PCEF address by encapsulating the data packet to be discarded in the IP address whose destination address is TDF. It is also possible to redirect the packet to be dropped directly to the TDF and put a special identifier on the packet header to indicate that the packet needs to be decremented.
  • This embodiment describes an S-level charging for the PCEF only for one IP-CAN session of the UE.
  • the PCEF is the latter policy enforcement point, the charging information of the PCEF is accurate.
  • the control is inconsistent on the TDF and PCEF, resulting in inaccurate accounting information of the PCEF.
  • the TDF redirects the data packets that need to be discarded according to the ADC rules to the PCEF, so that the PCEF performs the core subtraction.
  • the function examples are as follows: In the upstream direction, the PCEF receives 4 packets, and the allocation is A, B, and 0.
  • the PCEF After the PCEF enforces the PCC rules, it does not discard any packets and charges 4 packets of A, B, C, and D. Assume that A and B belong to the same application and charge with Charging Key X, while C and D belong to another application and charge with Charging Key Y. There is a billing session between PCEF and OCS or OFCS for reporting billing information (including credit control).
  • T packet will send packet A to PCEF because packet A needs to be discarded after TDF executes the ADC rule.
  • the TDF sends the packet A to the PCEF in a tunnel manner, and encapsulates the packet A in an IP packet whose destination address is PCEF and whose source address is the TDF address.
  • the PCEF When the PCEF receives the data packet with its own address as the destination address, the PCEF decapsulates the packet A and deducts the packet A related charging information from the Charging Key X charging information. Specifically, the PCEF filters the data A according to the filter of the installed PCC rule, and can match the Charging Key corresponding to the data packet A to X. After the PCEF performs the accounting information reduction on the packet A, the packet A is discarded.
  • TDF sends each packet that needs to be discarded to the PCEF.
  • some packages may not be billed by PCEF, so these packages do not require PCEF for deduction. This may result in more unused packets being sent.
  • the PCEF can put a special identifier on the packet header sent to the PCEF to indicate that the TDF packets are charged by the PCEF.
  • the TDF decides to drop the packet, it judges whether the packet is charged at the PCEF based on the identifier. Only when billing is performed, TDF sends these packets to PCEF for PCEF deduction.
  • the TDF sends the PCEF by encapsulating the data packet to be discarded in an IP packet whose destination address is PCEF and whose source address is the TDF address. It is also possible to directly redirect the packet to be dropped to the PCEF and put a special identifier on the packet header to indicate that the packet needs to be decremented.
  • the first embodiment and the first embodiment may be adopted.
  • This embodiment describes an IP-CAN session for the UE, and only the application level usage monitoring is performed on the TDF.
  • TDF usage monitoring is accurate because TDF is the latter policy enforcement point.
  • the PCEF redirects the data packet discarded according to the PCC rule to the TDF, so that the TDF performs the core subtraction.
  • the function examples are as follows:
  • the TDF receives 4 packets, and the allocation is A, B, C, and D. After TDF performs application detection and control, it does not drop any packets and charges 3 packets of A, B, and C. Assume that A and B are monitored by the monitoring key X, and C is monitored by another monitoring key Y. There is an Sd session between the TDF and the PCRF for the issuance of the ADC policy (including the policy of usage monitoring).
  • the PCEF When A, B, C, and D arrive at the PCEF, the PCEF will send the packet A to the TDF because the PCEF needs to be discarded after the PCC rules are executed.
  • the PCEF sends the packet A to the TDF in a tunnel manner, and encapsulates the packet A in an IP packet whose destination address is TDF and whose source address is the PCEF address.
  • the TDF When the TDF receives a packet with its own address as the destination address, the TDF decapsulates the packet A and deducts the amount associated with the packet A from the amount of consumption that the Monitoring Key has for X. Specifically, the TDF is locally saved based on the execution of the ADC rules. The device A filters the data A again, and can match the monitoring key corresponding to the data packet A to X. After the TDF performs the subtraction of the usage information of the data packet eight, the data packet A is discarded.
  • the PCEF sends each packet that needs to be discarded to the TDF.
  • some packages may not have TDF for usage monitoring, so these packages do not require TDF for deduction. This may result in more unused packets being sent.
  • TDF can put a special identifier on the packet header sent to PCEF to indicate that PCEF is monitored by usage.
  • the PCEF decides to drop the packet, it is judged based on this flag whether the packet is monitored in the TDF. Only when the usage monitoring is performed, the PCEF sends these packets to the TDF for the TDF.
  • the PCEF sends the TDF in the IP packet whose source address is the PCEF address by encapsulating the data packet to be discarded in the IP address whose destination address is TDF. It is also possible to redirect the packet to be dropped directly to the TDF and put a special identifier on the packet header to indicate that the packet needs to be decremented.
  • This embodiment describes an S-level usage monitoring on the PCEF for an IP-CAN session of the UE.
  • the PCEF is the latter policy enforcement point
  • the PCEF usage monitoring information is accurate.
  • the control inconsistency between TDF and PCEF causes the PCEF usage monitoring information to be inaccurate.
  • the TDF redirects the data packets that need to be discarded according to the ADC rules to the PCEF, so that the PCEF performs the core subtraction.
  • the function examples are as follows:
  • the PCEF receives 4 packets, and the allocation is A, B, and 0. After the PCEF enforces the PCC rules, it does not discard any packets and charges 4 packets of A, B, C, and D. Assume that A and B are monitored by Monitoring Key X, and C and D are monitored by Monitoring Key Y. There is a Gx session between PCEF and PCRF Used for the delivery of PCC policies (including the side-track related to usage monitoring).
  • T packet will send packet A to PCEF because packet A needs to be discarded after TDF executes the ADC rule.
  • the TDF sends the packet A to the PCEF in a tunnel manner, and encapsulates the packet A in an IP packet whose destination address is PCEF and whose source address is the TDF address.
  • the PCEF When the PCEF receives a packet with its own address as the destination address, the PCEF decapsulates the packet A and deducts the amount associated with the packet A from the consumed amount of the Monitoring Key for X. Specifically, the PCEF filters the data A according to the filter of the installed PCC rule, and can match the monitoring key corresponding to the data packet A to X. After the PCEF performs the subtraction of the usage information for the packet A, the packet A is discarded.
  • TDF sends each packet that needs to be discarded to the PCEF.
  • some packages may not be monitored by PCEF, so these packages do not require PCEF for verification. This may result in more unused packets being sent.
  • PCEF can put a special identifier on the packet header sent to PCEF to indicate that TDF these packets are monitored by PCEF usage.
  • the TDF decides to drop the packet, it judges whether the packet is monitored by the PCEF based on the identifier. Only when the usage monitoring is performed, TDF sends these packets to PCEF for PCEF deduction.
  • the TDF sends the PCEF in the IP packet whose source address is the TDF address by encapsulating the data packet to be discarded in the IP address whose destination address is PCEF. It is also possible to redirect the packet to be dropped directly to the PCEF and mark it with a special identifier to indicate that the packet needs to be dedurated.
  • the combination of the fourth embodiment and the fifth embodiment can be employed.
  • the PCEF needs to know the TDF address in order to redirect the dropped packets to the TDF or TDF in order to redirect the packets that need to be discarded to the PCEF, or the TDF needs to know the PCEF.
  • One method is to configure the IP address of the other party by PCEF or TDF, and the other is to dynamically allocate the method.
  • the method of dynamically learning the TDF address for the PCEF is applicable to the first embodiment and the fourth embodiment.
  • Step S901 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, where the IP-CAN session establishment request message carries the user identifier and requests for access. PDN ID of the PDN network.
  • Step S902 The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries the user identifier, the PDN identifier, and the IP address allocated for the UE.
  • Step S903 After determining, according to the user identifier, the PCRF does not have the subscription information of the user, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step S904 The SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier (returned by the contracted document response).
  • Step S905 The PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, it may include the formulation of PCC rules and event triggers.
  • the PCRF configures the address of the TDF corresponding to the PCEF.
  • Step S906 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries the PCC rule, the event trigger, and the address of the TDF.
  • Step S907 the PCEF installation policy, the gateway where the PCEF is located returns the IP-CAN to the UE.
  • the call establishes a response, wherein the IP-CAN session setup response carries an IP address.
  • Step S908 the PCRF sends a TDF session establishment request to the TDF, including an ADC rule.
  • the ADC rule includes a charging policy;
  • Step S909 the TDF returns a TDF session establishment confirmation message to the PCRF.
  • Step S910 When the TDF performs online charging according to the ADC detecting the application, the TDF sends a credit control request message to the OCS to request credit control.
  • Step S911 the OCS returns an acknowledgement message to the TDF.
  • the method for dynamically learning the PCEF address for the TDF is applicable to the second embodiment and the fifth embodiment.
  • Step S1001 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, where the IP-CAN session establishment request message carries the user identifier and requests for access.
  • the PDN identity of the PDN network 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, where the IP-CAN session establishment request message carries the user identifier and requests for access.
  • the PDN identity of the PDN network is not limited to establish an IP-CAN session.
  • Step S1002 The PCEF sends an IP-CAN session establishment indication message to the PCRF, where the IP-CAN session establishment indication message carries the user identifier, the PDN identifier, and the IP address allocated to the UE.
  • Step S1003 After determining, according to the user identifier, the PCRF does not have the subscription information of the user, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step S1004 The SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier (returned by the contract document response).
  • Step S1005 The PCRF makes a policy decision according to the returned user subscription information, the network policy, and the access information of the UE. Among them, it may include the formulation of PCC rules and event triggers.
  • Step S1006 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, where the IP-CAN session establishment confirmation message carries a PCC rule and an event trigger.
  • Step S1007 the PCEF installation policy, the gateway where the PCEF is located returns the IP-CAN to the UE.
  • the call establishes a response, wherein the IP-CAN session setup response carries an IP address.
  • Step S1008 the PCRF sends a TDF session establishment request to the TDF, including an ADC rule.
  • the ADC rule includes a charging policy.
  • the PCRF provides the IP address of the PCEF to the TDF;
  • Step S1009 The TDF returns a TDF session establishment confirmation message to the PCRF.
  • Step S1010 When the PCEF determines to perform online charging according to the PCC rule, the PCEF sends a credit control request message to the OCS to request credit control.
  • step S1011 the OCS returns an acknowledgement message to the PCEF.
  • the IP addresses of the TDF and the PCEF can be dynamically notified in conjunction with the processes of FIG. 9 and FIG.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware aspects. Moreover, the invention can take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that stored in the computer readable memory
  • the instructions in the reservoir produce an article of manufacture comprising an instruction device that implements the functions specified in one or more blocks of the flow or in a flow or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention se rapporte à un procédé, à un appareil et à un système permettant de traiter des données de trafic. Selon ledit procédé : une entité de fonction de détection de trafic (TDF pour Traffic Detection Function) détermine, selon une politique déterminée par la fonction TDF, un paquet de données qui est, parmi les paquets de données, envoyé par une entité de fonction d'application de politique et de facturation (PCEF pour Policy and Charging Enforcement Function) et qui doit être supprimé, et envoie à la fonction PCEF le paquet de données déterminé comme devant être supprimé ; et la fonction PCEF déduit des frais et/ou un usage correspondant au paquet de données supprimé ; ou la fonction PCEF détermine, selon une politique déterminée par la fonction PCEF, un paquet de données qui est, parmi les paquets de données, envoyé par la fonction TDF et qui doit être supprimé, et envoie à la fonction TDF le paquet de données déterminé comme devant être supprimé ; et la fonction TDF déduit des frais et/ou un usage correspondant au paquet de données supprimé.
PCT/CN2013/090771 2013-01-18 2013-12-27 Procédé, appareil et système permettant de traiter des données de trafic WO2014110966A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310027010.X 2013-01-18
CN201310027010.XA CN103945359B (zh) 2013-01-18 2013-01-18 一种业务数据的处理方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2014110966A1 true WO2014110966A1 (fr) 2014-07-24

Family

ID=51192795

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/090771 WO2014110966A1 (fr) 2013-01-18 2013-12-27 Procédé, appareil et système permettant de traiter des données de trafic

Country Status (2)

Country Link
CN (1) CN103945359B (fr)
WO (1) WO2014110966A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024031354A1 (fr) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 Procédé et appareil de correction de facturation, et dispositif de communication et support de stockage
CN117859299A (zh) * 2022-08-09 2024-04-09 北京小米移动软件有限公司 信息处理方法、系统及装置、通信设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431423A (zh) * 2008-12-24 2009-05-13 华为技术有限公司 一种用户业务流计费核减方法和装置
WO2012077073A1 (fr) * 2010-12-09 2012-06-14 Allot Communications Ltd. Dispositif, système et procédé de détection de trafic
CN102625272A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137367B (zh) * 2010-01-26 2016-03-30 中兴通讯股份有限公司 增强的策略和计费控制的方法及系统、pcc系统
CN103444226A (zh) * 2011-03-18 2013-12-11 瑞典爱立信有限公司 用于tdf会话建立的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431423A (zh) * 2008-12-24 2009-05-13 华为技术有限公司 一种用户业务流计费核减方法和装置
WO2012077073A1 (fr) * 2010-12-09 2012-06-14 Allot Communications Ltd. Dispositif, système et procédé de détection de trafic
CN102625272A (zh) * 2011-01-31 2012-08-01 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统

Also Published As

Publication number Publication date
CN103945359A (zh) 2014-07-23
CN103945359B (zh) 2018-12-25

Similar Documents

Publication Publication Date Title
US9647848B2 (en) Application charging method, device, and system
WO2012083795A1 (fr) Procédé, dispositif et système de contrôle de service
EP3105974B1 (fr) Sélection de nom de point d'accès (apn) assistée par fonction de règles de politique et de facturation (pcrf)
US9565052B2 (en) Method and system for realizing application detection and control in IP-CAN session supporting dual stack
WO2009124441A1 (fr) Procédé de déclenchement d’une fin de session, procédé de mise en place et appareil
EP3110197B1 (fr) Procédé de détection et de contrôle d'application dans un scénario d'itinérance et une v-pcrf
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
WO2015143851A1 (fr) Procédé, appareil et système de surveillance d'utilisation
KR20150004893A (ko) 크레딧 초과 pcc 규칙의 일시적 디스에이블
US20180309584A1 (en) Data Service Charging Method, Apparutus, and System
WO2012083779A1 (fr) Procédé et dispositif de commande de politique
WO2013135213A1 (fr) Procédé de traitement de session tdf et pcrf
WO2014110966A1 (fr) Procédé, appareil et système permettant de traiter des données de trafic
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
EP2950581B1 (fr) Serveur de politiques, dispositif d'application de politiques et divers procédés d'exclusion dynamique d'add-ons de service actif à partir du ralentissement d'une porteuse pour des terminaux utilisateurs
WO2017161522A1 (fr) Procédé, appareil et système de collecte de statistiques de quantité d'utilisation de flux
WO2011134321A1 (fr) Procédé et système d'envoi de politique pour communication de type machine
WO2016078333A1 (fr) Procédé et appareil de démarrage de commande de politique et de facturation
EP2595445A1 (fr) Procédé et système permettant d'établir une session
WO2012041148A1 (fr) Procédé et système de contrôle d'utilisation du volume de ressources

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

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

Country of ref document: EP

Kind code of ref document: A1