WO2012171431A1 - 数据流的用量监控方法及装置、pcef实体 - Google Patents

数据流的用量监控方法及装置、pcef实体 Download PDF

Info

Publication number
WO2012171431A1
WO2012171431A1 PCT/CN2012/076211 CN2012076211W WO2012171431A1 WO 2012171431 A1 WO2012171431 A1 WO 2012171431A1 CN 2012076211 W CN2012076211 W CN 2012076211W WO 2012171431 A1 WO2012171431 A1 WO 2012171431A1
Authority
WO
WIPO (PCT)
Prior art keywords
usage monitoring
service data
monitoring
usage
indication
Prior art date
Application number
PCT/CN2012/076211
Other languages
English (en)
French (fr)
Inventor
毛玉欣
周晓云
芮通
吴锦花
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201110163684.3A external-priority patent/CN102833123B/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012171431A1 publication Critical patent/WO2012171431A1/zh

Links

Classifications

    • 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
    • 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 communications, and in particular to a method and apparatus for monitoring usage of data streams and a PCEF entity.
  • BACKGROUND The 3rd Generation Partnership Project (3GPP) defines a policy and charging control architecture (PCC) for mobile networks, as shown in the figure.
  • the Policy and Charging Rules Function (PCRF) entity is used to formulate resource control policies, including service quality, for the service data flows included in the service.
  • QoS Quality of Service
  • PCEF Policy and Charging Enforcement Function
  • PCC Policy and Charging Enforcement Function
  • IP packets transmitted on the network are detected, and the IP packets are identified.
  • the traffic of the service and provides QoS and charging control for the traffic.
  • Bearer Binding and Event Report Function (Bearer Binding and Event Report Function, referred to as
  • BBERF is mainly used to detect IP packets transmitted on the network and map IP packets to corresponding bearer channels according to rules.
  • the BBERF also performs the reporting of the bearer-related event. For example, when the bearer is lost or the access network is switched, the corresponding event is reported to the PCRF entity, and the PCRF entity is requested to make a corresponding decision.
  • the Subscription Profile Repository (SPR) is used to store the service information subscribed by the user, and provides the necessary user subscription information for the PCRF entity to formulate PCC rules.
  • Online Charging System (OCS) and Offline Charging System (OFCS) are used for offline and online charging, respectively.
  • the PCC provides QoS guarantees in the transmission process according to the following principles: to improve the service experience of the user and improve the efficiency of network resource usage:
  • Each service data stream included in the service Both correspond to a specific PCC rule, and the QoS resources that can be used when the service data stream is transmitted are defined in the PCC rule.
  • PCRF before the service data stream is officially transmitted on the bearer network Entities need to make decisions and formulate PCC rules for business data flows based on various information.
  • the information on which the PCRF entity determines and formulates the PCC rules includes: the service negotiation information received from the AF, and the service negotiation information is information for conducting the service negotiated with the communication peer before the user officially conducts the service, for example, performing the service.
  • QoS requirements information such as the IP address and quintuple used
  • User subscription information received from the SPR for example, the user subscription information contains the QoS information that the user starts to use.
  • the service QoS requirements must be in the user.
  • the operator-defined policy stored by the PCRF entity itself For example, the operator needs to distinguish between the roaming user and the non-roaming user.
  • the operator-defined policy can be configured on the PCRF; the information received from the PCEF entity or the BBERF.
  • the PCRF needs to obtain the information of the user accessing the network through the PCEF or the BBERF, so that the PCRF can make a policy decision for the user to conduct the service; and obtain the credit information of the user from the OCS. For example, once the user's credit is used up, or not enough, the PCRF entity cannot authorize the user to conduct business.
  • the PCRF entity formulates a PCC rule for the service data flow decision according to the above information, and the PCC rule PCEF entity (if there is a BBERF in the network, the PCRF entity also needs to formulate a QoS rule and deliver it to the BBERF).
  • the PCEF entity needs to establish a corresponding bearer according to the QoS requirements of the PCC rule, and bind the PCC rule to the corresponding bearer (if there is a BBERF in the network, the BBERF establishes a bearer according to the QoS rule). If there is already a bearer in the network that matches the QoS indicated by the PCC rule or the QoS rule, the PCC rule or the QoS rule is bound to the existing bearer.
  • the gateway device may form the service according to the quintuple (composed of the source IP address, the source port number, the destination IP address, the destination port number, and the protocol).
  • the IP packet of the data stream is matched to the corresponding PCC rule/QoS rule.
  • the service data stream can be matched to the corresponding bearer, thereby serving the service data stream.
  • the transport on the bearer network provides the QoS guarantee indicated by the PCC rules/QoS rules. There are other requirements in the operation process. For example, for a certain service, the operator hopes that the first 10M is free for users.
  • the user When the user uses more than 10M, it needs to charge a certain fee. For example, the operator wants to use certain services. Use a bandwidth guarantee before the first 10M, and you need to limit this type of service when you exceed 10M. Bandwidth. For the above scenario, the user is required to perform the service.
  • the PCRF entity sends the PCC rule to the PCEF entity, it also needs to send an indication of the usage monitoring. The PCEF is required to perform the usage monitoring on the service. When the threshold is required, the PCEF entity reports the usage monitoring so that the PCRF entity can re-determine the service and generate a new control policy.
  • Steps A1 - A3 are processes for the PCRF entity to send usage monitoring indications to the PCEF entity.
  • the Charging Rule Definition is used to describe the PCC rules.
  • a Charging Rule Definition corresponds to a business data flow.
  • the Monitoring Key is the usage monitoring identifier. If the Monitoring Key is included in the Charging Rule Definition, it indicates that the traffic data needs to be monitored and the Usage Monitoring Information is generated for the Monitoring Key.
  • the Usage Monitoring Information includes the monitoring key, and also includes the Granted Service Unit corresponding to the Monitoring Key. The information contained in the other information is not related to the present invention and will not be described.
  • step A2 it is seen from step A2 that there are two service data streams (ie, Charging Rule Definition-1 and Charging Rule Definition-2), and the same monitoring key is assigned to the two service data flows, indicating that the two service data flows are required. Implement the same amount of monitoring. If you need to implement the usage monitoring for the two service data flows separately, you need to generate Monitoring Key-1 for the Charging Rule Definition-1 and the Monitoring Key-2 for the Charging Rule Definition-2, and you need to generate the Monitoring Key for each of the two Monitoring Keys. Usage Monitoring Information, this situation is not described here.
  • Step A1 the PCEF entity sends a credit control request CCredit-Control-Request (CCR) to the PCRF entity;
  • Step A2 the PCRF entity sends a credit control response CCredit-Control-Agreement (CCA) to the PCEF entity;
  • CCR Credit control request
  • CCA Credit control response
  • the rule represented by the charting rule definition
  • the rule requires that the PCC rule be monitored for usage, that is, the monitoring key is included in the PCC rule, and the usage monitoring information including the threshold is generated for the monitoring key.
  • the PCRF entity may also be sent to the PCEF entity.
  • the Re-Auth-Request (RAR) message contains the indication of the above-mentioned usage monitoring.
  • Step A3 The corresponding PCRF entity sends a RAR message to the PCEF entity, and the PCEF entity returns a Re-Auth-Response (RAA) message to the PCRF entity.
  • Step B After the PCEF entity receives the PCC rule delivered by the PCRF entity, the rule is installed. At the same time, the service data flow corresponding to the PCC rule (that is, the service data stream 1 and the service data stream 2) is monitored.
  • Steps C1-C2 are processes for reporting the usage monitoring by the PCEF entity. In the step CI, when the cumulative amount of the monitoring of the Monitoring Key by the PCEF entity reaches the threshold sent by the step A2, the PCEF entity performs the usage monitoring report.
  • the PCEF entity sends a CCR message to the PCRF entity, carrying the Usage Monitoring Information, which contains the above Monitoring Key, and also includes the cumulative usage (indicated by Used-Service-Unit).
  • the PCRF entity returns a CCA response to the PCEF entity.
  • Step D According to the reported cumulative usage, the PCRF entity re-defines the corresponding control strategy for the service data flow (ie, service data flow-1 and service data flow-2) that uses the monitoring key for usage monitoring.
  • Steps E1-E2 re-define the policy delivery process for the PCRF entity.
  • the PCRF entity sends a RAR message to the PCEF entity, and re-issues the control policy for the service data streams 1 and 2.
  • step E2 the PCEF entity returns a response to the PCRF entity.
  • the above-mentioned usage monitoring mechanism makes the network control of the service more flexible.
  • the operator initially needs to perform usage monitoring on a group of service data flows (that is, assign the same monitoring key to the group of service data flows, and assign a threshold to the monitoring key, for example, a process.
  • the service data stream 1 and the service data stream 2) shown in Fig. 2 this case is called group usage monitoring.
  • the existing usage monitoring reporting mechanism cannot solve the above requirements. .
  • a primary object of the present invention is to provide a method and apparatus for monitoring usage of data streams and a PCEF entity to solve at least one of the above problems.
  • a method for monitoring usage of a data stream including: in a process of monitoring group usage of multiple service data flows, a policy and charging execution function (PCEF) entity receives a policy from And the charging rule function of the PCRF entity for the usage of a specific service data stream in a plurality of service data streams Control operation indication; The PCEF entity monitors the operation indication according to the received usage amount, and performs adjustment on the usage monitoring of the specific service data flow.
  • the method further includes: the PCRF entity receiving the trigger indication for performing the usage monitoring operation for the specific service data flow; Trigger indicates the instruction to deliver the usage monitoring action.
  • the usage monitoring operation indication includes the following: the usage monitoring revocation indication and the usage monitoring increase indication; wherein the usage monitoring revocation indication is used to stop the usage monitoring for the specific service data flow in the group usage monitoring, and the usage monitoring increase indication It is used to indicate that the usage monitoring for a specific service data flow is added in the group usage monitoring.
  • the method further includes: when the usage monitoring operation indication is the usage monitoring revocation indication, the usage monitoring operation indication includes: a monitoring identifier assigned to a specific service data flow, a usage monitoring revocation identifier for a specific service data flow; and an usage monitoring operation indication When the usage monitoring increases the indication, the usage monitoring operation indication includes: a monitoring identifier assigned to a specific service data flow, and an usage monitoring identifier for a specific service data flow.
  • the PCEF entity When the usage monitoring operation indication is the usage monitoring revocation indication, the PCEF entity performs the adjustment on the usage monitoring of the specific service data flow according to the received usage monitoring operation indication, including: the usage monitoring revocation indication is generated by the PCRF entity for the specific service data flow.
  • the first policy and the accounting control PCC rule and the second PCC rule are two PCC rules.
  • the first PCC rule is a PCC rule that has been installed on the PCEF entity, and includes: a first quintuple, a monitoring identifier, a monitoring key, and a a priority, deleting a PCC rule operation indication;
  • the second PCC rule includes: a second quintuple, a second priority, and an installation PCC rule operation indication; the first priority is lower than the second priority; the first quintuple and The second quintuple is the same;
  • the PCRF entity sends the first and second PCC rules to the PCEF entity; the PCEF entity performs the first and second PCC rules to cancel the usage monitoring of the specific service data flow.
  • a policy and charging execution function entity is further provided, which is used in the process of monitoring group usage of multiple service data flows, including: a first receiving module, configured to receive from a policy And the usage monitoring function indication of the specific service data flow in the plurality of service data flows of the PCRF function; the first adjustment module is configured to monitor the operation instruction according to the usage received by the first receiving module, to the specific service data flow The amount of usage monitoring is adjusted.
  • a device for monitoring usage of a data stream includes: a PCRF entity and a PCEF entity, which are used in a process of monitoring group usage of a plurality of service data flows, wherein the PCEF entity includes: a receiving module, configured to receive from the PCRF entity for multiple service data flows The usage monitoring operation indication of the specific service data flow; the second adjustment module is configured to perform adjustment on the usage monitoring of the specific service data flow according to the usage monitoring operation indication received by the second receiving module.
  • the PCRF entity includes: a third receiving module, configured to receive a trigger indication for performing a usage monitoring operation for a specific service data flow; and a sending module, configured to send a usage monitoring operation indication according to the trigger indication.
  • the usage monitoring operation indication includes the following: the usage monitoring revocation indication and the usage monitoring increase indication; wherein the usage monitoring revocation indication is used to stop the usage monitoring for the specific service data flow in the group usage monitoring, and the usage monitoring increase indication It is used to indicate that the usage monitoring for a specific service data flow is added in the group usage monitoring.
  • the PCRF entity is used to deliver the received usage monitoring operation indication (that is, the PCEF entity receives the usage monitoring operation indication from the PCRF entity) to the PCEF entity, and the related technology can not solve the group usage monitoring.
  • FIG. 2 is a schematic flowchart of an implementation of usage monitoring according to the related art
  • FIG. 3 is a flowchart of a method for monitoring usage of a data stream according to an embodiment of the present invention
  • 4 is a schematic flow chart of a method for monitoring usage of data streams according to Example 2 of the present invention
  • FIG. 5 is a schematic flowchart of a method for monitoring usage of data streams according to Example 3 of the present invention
  • FIG. 6 is a flowchart of data flow according to Example 4 of the present invention.
  • FIG. 7 is a structural block diagram of a policy and charging execution function entity according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a data flow usage monitoring device according to an embodiment of the present invention
  • 9 is a schematic diagram of an apparatus for monitoring usage of data streams in accordance with a preferred embodiment of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • FIG. 3 is a flowchart of a method for monitoring usage of a data stream according to an embodiment of the present invention. As shown in FIG.
  • Step S302 In a process of monitoring group usage of multiple service data flows, the PCEF entity receives the plurality of service data flows from the PCRF entity of the policy and charging rule function.
  • the usage monitoring operation indication of the specific service data flow is performed; in step S304, the PCEF entity performs an adjustment on the usage monitoring of the specific service data flow according to the received usage monitoring operation indication.
  • the specific service data stream may be one or more.
  • the PCEF entity receives the usage monitoring operation indication from the PCRF entity, and the PCEF entity performs adjustment on the usage monitoring of the specific service data flow according to the usage monitoring operation indication (for example, the service data is to be The usage monitoring of the flow is canceled from the monitoring of the group usage, or the monitoring of the usage of the service data flow is added to the monitoring of the group usage, so that the management of the group usage monitoring can be solved.
  • the foregoing method may further include the following process: the PCRF entity receives a trigger indication for performing a usage monitoring operation for a specific service data flow; and the PCRF entity sends a usage monitoring operation indication according to the trigger indication.
  • the above process may be performed before the PCEF entity receives an indication of usage monitoring operations for a particular one of the plurality of service data streams from the PCRF entity.
  • the PCRF entity may send the usage monitoring operation indication after receiving the trigger indication.
  • the foregoing usage monitoring operation indication includes, but is not limited to, one of the following: the usage monitoring revocation indication and the usage monitoring increase indication; wherein the usage monitoring revocation indication is used to indicate that the specific service data is stopped in the group usage monitoring.
  • the usage monitoring of the flow, the usage monitoring increase indication is used to indicate that the usage monitoring for the specific service data flow is added in the group usage monitoring.
  • the method further includes: when the usage monitoring operation indication is the usage monitoring revocation indication, the usage monitoring operation indication includes: a monitoring identifier assigned to a specific service data flow, and a usage monitoring revocation identifier for a specific service data flow. ;
  • the usage monitoring operation instruction is used to increase the indication for the usage monitoring.
  • the control operation indication includes: a monitoring identifier assigned to a specific service data flow, and an usage monitoring identifier for a specific service data flow.
  • the PCEF entity performs an adjustment on the usage monitoring of the specific service data flow according to the received usage monitoring operation indication, and may also include the following processing:
  • the PCRF entity is specific to the specific
  • the service data stream generates the first policy and the charging control PCC rule and the second PCC rule, and the PCC rule is: the first PCC rule is a PCC rule that has been installed on the PCEF entity, and includes: a first quintuple, a monitoring identifier The monitoring key, the first priority, and the deletion of the PCC rule operation indication;
  • the second PCC rule includes: a second quintuple, a second priority, and an installation operation instruction of the PCC rule; the first priority is lower than the second priority;
  • the quintuple is the same as the second quintuple;
  • the PCRF entity sends the first and second PCC rules to the PCEF entity; the PCEF entity performs the first and second PCC rules to cancel the usage monitoring of the specific service data
  • the usage monitoring of the specific service data flow may be directly revoked according to the foregoing usage monitoring operation instruction, or the usage monitoring of the specific service data flow may be revoked according to the foregoing processing procedure.
  • the PCEF after receiving the PCC rule, the PCEF deletes the original PCC rule because the first priority is lower than the second priority, and then deletes the original PCC rule, and since the monitoring key is not included in the new PCC rule, The usage monitoring of the corresponding business data stream will be canceled.
  • the foregoing usage monitoring operation indication may include the first PCC rule and the second PCC rule, and therefore, the foregoing processing procedure and the PCEF entity monitor the operation indication according to the received usage amount, for the specific service.
  • Data flow usage monitoring implementation adjustments do not conflict.
  • Example 1 The problem of monitoring the usage of a specific service data flow from the group usage monitoring cannot be solved for the existing usage monitoring and reporting mechanism. This example proposes a method for implementing the usage monitoring for the service data flow to solve the above problem. It is possible to add usage monitoring of a specific service data stream to the group usage monitoring.
  • the usage monitoring is performed for a specific service data flow, and the PCC rule is sent to the service data flow (represented by a charging rule definition and identified by a charging rule name), where the PCC rule includes a monitoring key,
  • the PCRF sends the usage monitoring information (indicated by Usage Monitoring Information) to the monitoring key.
  • the PCRF sends an indication of the usage monitoring operation for the service data flow to the PCEF;
  • the operation indication includes: the usage monitoring cancellation or the usage monitoring increase; the operation indication is included in the usage monitoring information (Usage Monitoring Information).
  • the usage monitoring information further includes a PCC rule identifier corresponding to the service data flow (ie, a charging rule name).
  • the PCEF monitors the usage of the service data flow corresponding to the PCC rule according to the indication. Content implementation adjustments.
  • the usage monitoring adjustment is specifically: if the indication content is the usage monitoring revocation, the usage monitoring for the service data flow is canceled from the usage monitoring group corresponding to the monitoring key; if the indication content is increased by the usage monitoring, The service data stream is added to the usage monitoring group corresponding to the monitoring key, and the usage of the service data flow is monitored.
  • the present example proposes an alternative: when the PCRF receives an indication of the usage monitoring cancellation of the specific service data flow, the service data is The implementation of the flow usage monitoring implementation revocation is as follows: The PCRF generates the first and second PCC rules for the service data flow decision and delivers the same to the PCEF.
  • the PCC rule wherein the first PCC rule is a PCC rule that has been installed on the PCEF, includes: a first quintuple, a monitoring identifier, a first priority, and an operation instruction for deleting the PCC rule;
  • the second PCC rule includes: a second quintuple, a second priority, and the installation of the PCC rule operation indication; the first priority is lower than the second priority; the first quintuple and The second quintuple is the same, that is, the two rules are used for the business data stream at the same time.
  • Example 2 This example presents an embodiment of the cancellation of usage monitoring for traffic data flow-1.
  • the assumptions of this example are as follows. It is necessary to implement usage monitoring for two service data flows (Service Data Flow-1 and Service Data Flow-2).
  • the Data Flow-1 decision generates a PCC Rule-1 (identified by the charging rule name-1), and generates a PCC Rule-2 (identified by the charging rule name-2) for the Business Data Flow-2 decision, both for the two PCC rules.
  • Step S402 The PCRF receives the authorization request from the PCEF.
  • step S404 the PCRF returns the authorization result to the PCEF, and the PCRF sends the usage monitoring indication for the service data flow-1 and the service data flow-2 to the PCEF. For example, it is issued as follows:
  • Charging rule definition- 1 [charging rule name-1, monitoring key]
  • the PCC rule corresponding to the service data stream-1 is represented by the charging rule definition-1, and includes the PCC rule identifier charging rule name-1 and the usage monitoring identifier monitoring key; the service data stream-2 corresponds to
  • the PCC rule is represented by a charging rule definition-2, which includes a PCC rule identifier, a charging rule name-2, and a usage monitoring identifier, a monitoring key.
  • the PCRF simultaneously sends the usage monitoring information corresponding to the monitoring key to the PCEF, and includes the threshold granted service unit corresponding to the monitoring key.
  • Step S406 The PCEF performs usage monitoring on the service data stream-1 and the service data stream-2 according to the usage monitoring indication delivered by the PCRF.
  • the PCRF receives an indication to cancel the usage monitoring for the service data stream -1.
  • the PCRF sends an indication to the PCEF that the usage monitoring of the service data stream-1 is cancelled. For example, send it as follows:
  • the indication of the cancellation usage monitoring issued by the PCRF is included in the Usage monitoring information.
  • the usage monitoring information includes a monitoring key and a usage monitoring feature, where the monitoring key is the monitoring key used for the usage monitoring of the service data flow-1 in step S404.
  • the usage monitoring feature includes the usage monitoring support and the charging rule name-1, where the usage monitoring support is disabled (that is, the usage monitoring revocation identifier), indicating that the charging rule name-l (that is, the service data flow-1) needs to be canceled.
  • the usage monitoring in the usage monitoring group corresponding to the monitoring key.
  • the PCEF returns an acknowledgement message to the PCRF.
  • Step S414 according to the instruction for canceling the usage monitoring of the service data flow-1 delivered by the PCRF, the PCEF performs the usage monitoring adjustment, that is, deleting the monitoring key from the charging rule defmition-1, and stopping the traffic data flow-1 in the monitoring The usage monitoring in the usage monitoring group corresponding to the key.
  • Example 3 This example presents an embodiment of the cancellation of usage monitoring for Service Data Flow-1. The assumptions of this embodiment are as follows.
  • Step S502 the PCRF receives an authorization request from the PCEF.
  • step S504 the PCRF returns an authorization result to the PCEF, and the PCRF sends an indication of the usage monitoring for the service data stream-1 and the service data stream-2 to the PCEF. For example, it is issued as follows:
  • Charging rule definition- 1 [charging rule name-1, monitoring key-1] Charging rule definition-2
  • Usage monitoring information [monitoring key-1, granted service unit]
  • the PCC rule corresponding to the service data stream-1 is represented by the charging rule definition-1, and includes the PCC rule identifier charging rule name-1 and the usage monitoring identifier monitoring key-1
  • the PCC rule corresponding to the service data stream-2 is represented by a charging rule definition-2, and includes a PCC rule identifier charging rule name-2 and a usage monitoring identifier monitoring key-1.
  • the PCRF sends the usage monitoring information corresponding to the monitoring key-1 to the PCEF, and includes the monitoring key-1 and the corresponding threshold granted service unit.
  • Step S506 The PCEF performs usage monitoring on the service data stream-1 and the service data stream-2 according to the usage monitoring indication delivered by the PCRF.
  • Step S508 the PCRF receives the indication that the service data stream -1 is canceled from the usage monitoring group corresponding to the monitoring key-1, and is added to the usage monitoring group corresponding to the monitoring key-2.
  • Step S510 the PCRF sends the indication to the PCEF. For example, it is issued in the following form: Usage monitoring information- 1
  • the usage monitoring adjustment indication information for the service data flow-1 sent by the PCRF includes Usage monitoring information-1 and Usage monitoring information-2 0, wherein Usage monitoring information-1 is used to indicate that the charging rule name--the service data stream-1) The usage monitoring is canceled from the usage monitoring group corresponding to the monitoring key-1.
  • the usage monitoring information-2 indicates that the charging rule name-1 (that is, the service data stream-1) is added to the usage monitoring group corresponding to the monitoring key-2.
  • the PCEF returns an acknowledgement message to the PCRF.
  • Step S514 according to the indication of the usage monitoring adjustment for the service data stream-1 delivered by the PCRF, the PCEF deletes the monitoring key-1 from the charging rule definition-1, that is, the usage monitoring of the service data stream-1 from the monitoring key- 1
  • the corresponding usage monitoring group is canceled, and in the charging rule definition-1, the monitoring key-2 is added, indicating that the service data stream-1 is added to the usage monitoring group corresponding to the monitoring key-2.
  • Example 4 The assumptions of this example are as follows. It is necessary to implement usage monitoring for two service data flows (Service Data Flow-1 and Service Data Flow-2).
  • Step S602 the PCRF receives an authorization request from the PCEF.
  • step S604 the PCRF returns an authorization result to the PCEF, and the PCRF sends an indication of the usage monitoring for the service data stream-1 and the service data stream-2 to the PCEF. For example, it is issued as follows:
  • the PCC rule corresponding to the service data stream-1 is represented by a charging rule definition-1, and includes a PCC rule identifier charging rule name-1 and a usage monitoring identifier monitoring key; the PCC rule corresponding to the service data stream-2 uses a charging rule definition- 2 indicates that the PCC rule identifier charging rule name-2 and the usage monitoring identifier monitoring key are included.
  • the PCRF sends the usage monitoring information corresponding to the monitoring key to the PCEF, and includes the thresholded granted service unit corresponding to the monitoring key.
  • Step S606 The PCEF performs usage monitoring on the service data stream-1 and the service data stream-2 according to the usage monitoring indication delivered by the PCRF.
  • Step S608 the PCRF receives an indication for canceling the usage monitoring of the service data stream-1.
  • the PCRF re-generates a control policy for the service data flow-1 decision.
  • PCRF is the business data stream
  • PCC rule-1 represented by charging rule definition-1
  • PCC rule-3 represented by charging rule defmition-3
  • PCC rule Bay 1 The information contained in the RAR message sent by the PCRF is as follows:
  • charging rule definition-3 (5 -tuple, precedence)
  • charging rule remove indicates that PCC rule-1 is to be deleted (ie, identified by charging rule name-1)
  • charging rule install indicates that PCC rules are installed - 3 (ie identified by the charging rule name-3).
  • PCC Rule-1 and PCC Rule-3 have the same quintuple information (in 5-tuple).
  • the monitoring key is included in PCC Rule-1, but is not included in PCC Rule-3.
  • the priority setting of PCC Rule-1 is lower than the priority of PCC Rule-3, indicating that PCC Rule-3 is preferentially executed.
  • the PCEF returns a RAA response.
  • Step S614 after receiving the policy delivered by the PCRF, the PCEF performs the priority according to the PCC rule, first installs the PCC rule-3, and then deletes the PCC rule-1. Since PCC Rule-3 and PCC Rule-1 are both bound to Service Data Flow-1, and the currently activated PCC-Rules-3 does not contain a monitoring key, that is, according to the new PCC rule, no traffic data is required. -1 Implement usage monitoring. So the new installation for Business Data Flow-1 does not contain The PCC rule of the monitoring key deletes the PCC rule that originally contains the monitoring key, which can be used to undo the usage monitoring of the service data stream-1.
  • FIG. 7 is a structural block diagram of a policy and charging execution function entity according to an embodiment of the present invention.
  • the PCEF entity in this example is applied to the group usage monitoring of multiple service data flows.
  • the PCEF entity includes: a first receiving module 70, configured to receive the function from the policy and charging rules.
  • the first adjustment module 72 is connected to the first receiving module 70, and is configured to monitor the operation instruction according to the usage received by the first receiving module 70, Implement adjustments to the usage monitoring of specific business data streams.
  • FIG. 8 is a schematic diagram of a device for monitoring usage of a data stream according to an embodiment of the invention. The device in this embodiment is applied to the process of monitoring the group usage of the multiple service data flows. As shown in FIG.
  • the device includes: a PCRF entity 80 and a PCEF entity 82.
  • the PCEF entity 82 includes:
  • the receiving module 820 is connected to the PCRF entity 80, and is configured to receive the usage monitoring operation indication from the PCRF entity 80 for the specific service data flow in the multiple service data flows.
  • the second adjustment module 822 is connected to the second receiving module 820. And being configured to perform adjustment on the usage monitoring of the specific service data flow according to the usage monitoring operation indication received by the second receiving module 820. In the specific application process, as shown in FIG.
  • the PCRF entity 80 includes: a third receiving module 800, configured to receive a trigger indication for performing a usage monitoring operation for a specific service data flow; and a sending module 802, and a third receiving module 800 Connected, set to send the usage monitoring operation indication according to the trigger indication.
  • the usage monitoring operation indication includes one of the following: an usage monitoring revocation indication and an usage monitoring increase indication; wherein, the usage monitoring revocation indication is used to indicate that the usage of the specific service data flow is stopped in the group usage monitoring.
  • the monitoring, usage monitoring increase indication is used to indicate that the usage monitoring for the specific service data flow is added in the group usage monitoring.
  • the technical means for transmitting the received usage monitoring operation indication to the PCEF entity by using the PCRF entity is solved, and the related technology cannot be solved.
  • Group-specific usage monitoring for specific business data streams one or more Management of usage monitoring (eg, removing usage monitoring of the service data flow from the group usage monitoring, or adding usage monitoring for the business data flow to the group usage monitoring)
  • the effect of conveniently managing the group usage monitoring is achieved.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Abstract

本发明提供了一种数据流的用量监控方法及装置、PCEF实体，其中，上述方法包括：在对多个业务数据流进行组用量监控的过程中，策略和计费执行功能实体接收来自于策略和计费规则功能实体的针对多个业务数据流中的特定业务数据流的用量监控操作指示；PCEF实体根据接收的用量监控操作指示，对特定业务数据流的用量监控实施调整。采用本发明提供的上述技术方案，达到了可以方便地对组用量监控中的特定业务数据流（一个或多个）的用量监控进行管理的效果。

Description

数据流的用量监控方法及装置、 PCEF实体 技术领域 本发明涉及通信领域， 具体而言， 涉及一种数据流的用量监控方法及装置、 PCEF 实体。 背景技术 第三代合作伙伴计划（3rd Generation Partnership Project, 简称为 3GPP)定义了针 对移动网络的策略和计费控制架构 （Policy and Charging Control, 简称为 PCC)， 如图
1所示， 各实体功能如下描述： 策略和计费规则功能 (Policy and Charging Rules Function,简称为 PCRF)实体为业 务包含的业务数据流在传输过程中使用网络资源制定资源控制策略， 包括服务质量 (Quality of Service, 简称为 QoS) 控制策略和计费控制策略。 策略和计费执行功能 （Policy and Charging Enforcement Function, 简称为 PCEF) 用于执行 PCRF下发的或者 PCEF上预配置的 PCC规则， 对网络上传输的 IP报文进 行检测， 识别该 IP报文隶属的业务数据流， 并对业务数据流提供 QoS和计费控制。 承载绑定和事件上报功能 （Bearer Binding and Event Report Function, 简称为
BBERF) 主要用于对网络上传输的 IP报文进行检测， 并将 IP报文按照规则映射到对 应的承载通道上。 BBERF还执行承载相关事件的上报， 例如当承载丢失， 或者发生接 入网络切换的时候， 都需要将相应的事件上报给 PCRF实体， 请求 PCRF实体进行相 应的决策。 用户签约数据库 （Subscription Profile Repository, 简称为 SPR) 用于保存用户签 约的业务信息， 为 PCRF实体制订 PCC规则提供必要的用户签约信息。在线计费系统 (Online Charging System, 简称为 OCS)和离线计费系统（Offline Charging System, 简 称为 OFCS) 分别用于离线和在线计费。 在用户开展业务过程中， PCC按照如下原理为业务 （由若干业务数据流组成） 在 传输过程中提供 QoS保证， 以提高用户的业务体验， 提高网络资源使用效率： 业务包含的每个业务数据流都对应一个具体的 PCC规则， PCC规则中定义了该业 务数据流传输时可以使用的 QoS资源。在业务数据流正式在承载网络传输之前， PCRF 实体需要根据各种信息为业务数据流决策并制定 PCC 规则。 PCRF 实体决策并制定 PCC规则所依据的信息包括： 从 AF接收的业务协商信息， 该业务协商信息就是用户正式开展业务之前和通信 对端协商的开展所述业务的信息， 例如开展所述业务的 QoS要求， 所使用的 IP地址、 五元组等信息； 从 SPR接收的用户签约信息，例如用户签约信息中包含用户开始使用的 QoS信息， 则用户开展业务时，业务对 QoS的要求必须在用户签约信息所规定的用户可以使用的 QoS信息内；
PCRF 实体自身存储的运营商自定义的策略。 例如运营商对漫游用户和非漫游用 户开展业务需要区分控制， 此时可以在 PCRF上配置运营商自定义的策略； 从 PCEF实体或者 BBERF上接收的信息。 例如用户附着到网络时， PCRF需要通 过 PCEF或者 BBERF获取用户接入网络的信息，以供 PCRF为用户开展业务进行策略 决策； 从 OCS获取用户的信用信息。 例如一旦用户的信用用完， 或者不够时， PCRF实 体就无法授权所述用户开展业务。
PCRF实体根据上述信息对业务数据流决策制定 PCC规则， 并将 PCC规则 PCEF 实体（如果网络中存在 BBERF,则 PCRF实体还需要制定 QoS规则，并下发给 BBERF )。 PCEF实体需要根据 PCC规则的 QoS要求建立相应的承载， 并将 PCC规则绑定到对 应的承载上 （如果网络中存在 BBERF, 则由 BBERF根据 QoS规则建立承载）。 如果 网络中已经有和 PCC规则或者 QoS规则指示的 QoS相匹配的承载，则将所述 PCC规 则或者 QoS规则绑定到已有的承载上。 此后， 当用户开展业务， 业务数据流在承载网络上传输的时候， 网关设备可以根 据五元组 （由源 IP地址、 源端口号、 目的 IP地址、 目的端口号、 协议组成） 将组成 该业务数据流的 IP报文匹配到相应的 PCC规则 /QoS规则， 根据 PCC规则 /QoS规则 和承载的绑定关系， 就可以将所述业务数据流匹配到相应的承载上， 从而为业务数据 流在承载网络上的传输提供 PCC规则 /QoS规则所指示的 QoS保证。 在运营过程中还存在其他需求， 比如对于某种业务， 运营商希望前 10M是供用户 免费使用的， 当用户使用超出 10M之后， 就需要收取一定的费用； 再比如运营商希望 对某类业务在前 10M之前使用一种带宽保证， 当超出 10M之后需要对该类业务限制 带宽。 对于上述场景， 就要求用户开展业务， PCRF实体向 PCEF实体下发 PCC规则 的同时， 还需要下发用量监控的指示， 要求 PCEF对所述业务实施用量监控， 当所述 业务的流量达到监控所要求的阈值时， PCEF实体就要对用量监控实施上报，以便 PCRF 实体重新对所述业务进行决策， 产生新的控制策略。 用量监控的实现过程如图 2所示的流程： 步骤 A1-A3为 PCRF实体向 PCEF实体下发用量监控指示的过程， 流程图中计费 规则定义 （Charging Rule Definition) 用于描述 PCC 规则， 即一个 Charging Rule Definition对应描述一个业务数据流。 监控标识 （Monitoring Key) 为用量监控标识， 如果 Charging Rule Definition中包含了 Monitoring Key就表明， 需要对该业务数据流 实施用量监控， 同时为该 Monitoring Key产生一个用量监控信息 （Usage Monitoring Information )。 Usage Monitoring Information 包含了该 monitoring key, 还包含了该 Monitoring Key对应的阈值 （Granted Service Unit), 另外包含的信息由于与本发明无 关， 不作描述。 从步骤 A2中看出有两个业务数据流（即 Charging Rule Definition- 1和 Charging Rule Definition-2 )， 为这两个业务数据流分配了相同的 Monitoring Key, 说明 需要为这个两个业务数据流实施同一用量监控。 如果需要为这两个业务数据流分别实 施用量监控， 则需要为 Charging Rule Definition- 1产生 Monitoring Key- 1， 为 Charging Rule Definition-2产生 Monitoring Key-2, 同时需要为这两个 Monitoring Key分别产生 Usage Monitoring Information, 这种情况这里不在描述。 步骤 A1，PCEF实体向 PCRF实体发送信用控制请求 CCredit-Control-Request, 简称 为 CCR); 步骤 A2， PCRF实体向 PCEF实体下发信用控制响应 CCredit-Control- Answer, 简 称为 CCA；)， 包含 PCC规则 （用 charging rule definition表示）， 同时要求为所述 PCC 规则实施用量监控， 即 PCC规则中包含了 monitoring key, 并为 monitoring key产生包 含阈值的 usage monitoring information PCRF实体也可在发送给 PCEF实体的再授权 请求 （Re-Auth-Request,， 简称为 RAR)消息中包含上述用量监控的指示。 步骤 A3， 对应 PCRF实体向 PCEF实体下发 RAR消息， 则 PCEF实体向 PCRF 实体返回再授权响应 （ Re- Auth- Answer, 简称为 RAA) 消息。 步骤 B，当 PCEF实体收到 PCRF实体下发的 PCC规则后，安装规则。同时对 PCC 规则对应的业务数据流 （即业务数据流 1和业务数据流 2) 实施用量监控。 步骤 C1-C2为 PCEF实体上报用量监控的过程。 步骤 CI，当 PCEF实体对 Monitoring Key监控的累计用量 达到步骤 A2下发的阈 值时， PCEF实体进行用量监控上报。 PCEF实体向 PCRF实体发送 CCR消息， 携带 Usage Monitoring Information, 其中包含了上述 Monitoring Key, 另夕卜还包含累计用量 (用 Used-Service-Unit表示)。 步骤 C2， PCRF实体向 PCEF实体返回 CCA响应。 步骤 D， 根据上报的累计用量， PCRF实体对利用该 monitoring key进行用量监控 的业务数据流 （即业务数据流 -1和业务数据流 -2) 重新制定相应的控制策略。 步骤 E1-E2为 PCRF实体重新制定策略下发的过程。 步骤 El， PCRF实体向 PCEF实体下发 RAR消息， 为业务数据流 1和 2重新下发 控制策略。 步骤 E2， PCEF实体向 PCRF实体返回响应。 上述用量监控机制， 使得网络对业务的控制变得更加灵活。 然而运营过程中， 还 存在如下需求， 例如运营商初始希望对一组业务数据流实施用量监控 （即为所述一组 业务数据流分配相同的 monitoring key, 并为该 monitoring key分配阈值， 例如流程图 2中所示的业务数据流 1和业务数据流 2)， 这种情况称为组用量监控。 在对组用量监 控实施过程中， 如果需要对其中的业务数据流撤销用量监控， 即将该业务数据流的用 量监控从上述组用量监控中取消，利用现有的用量监控上报机制尚无法解决上述需求。 另外对于实施组用量监控中的业务数据流的用量监控实施修改， 或者将一个新的业务 数据流加入所述组用量监控中， 利用现有用量监控机制解决上述问题时， 实现复杂， 影响到系统性能。 针对相关技术中的上述问题， 目前尚未提出有效的解决方案。 发明内容 本发明的主要目的在于提供一种数据流的用量监控方法及装置、 PCEF 实体， 以 解决上述问题至少之一。 根据本发明的一个实施例， 提供了一种数据流的用量监控方法， 包括： 在对多个 业务数据流进行组用量监控的过程中， 策略和计费执行功能（PCEF)实体接收来自于 策略和计费规则功能 PCRF实体的针对多个业务数据流中的特定业务数据流的用量监 控操作指示； PCEF 实体根据接收的用量监控操作指示， 对特定业务数据流的用量监 控实施调整。 上述 PCEF实体接收来自于 PCRF实体的针对多个业务数据流中的特定业务数据 流的用量监控操作指示之前， 还包括： PCRF 实体接收针对特定业务数据流执行用量 监控操作的触发指示； PCRF实体根据触发指示下发用量监控操作指示。 上述用量监控操作指示包括以下之一： 用量监控撤销指示、 用量监控增加指示； 其中， 用量监控撤销指示用于指示在所述组用量监控中停止针对特定业务数据流的用 量监控， 用量监控增加指示用于指示在所述组用量监控中增加针对特定业务数据流的 用量监控。 上述方法还包括： 用量监控操作指示为用量监控撤销指示时， 用量监控操作指示 包括： 分配给特定业务数据流的监控标识 monitoring key、针对特定业务数据流的用量 监控撤销标识； 用量监控操作指示为用量监控增加指示时， 用量监控操作指示包括： 分配给特定业务数据流的监控标识 monitoring key、针对特定业务数据流的用量监控执 行标识。 上述用量监控操作指示为用量监控撤销指示时， PCEF 实体根据接收的用量监控 操作指示， 对特定业务数据流的用量监控实施调整， 包括： 所述用量监控撤销指示为 PCRF实体针对特定业务数据流产生第一策略和计费控制 PCC规则和第二 PCC规则两 个 PCC规则； 其中， 第一 PCC规则为已经在 PCEF实体上安装的 PCC规则， 包括： 第一五元组、 监控标识 monitoring key、 第一优先级、 删除 PCC规则操作指示； 第二 PCC规则包括： 第二五元组、第二优先级、 安装 PCC规则操作指示； 第一优先级低于 第二优先级； 第一五元组和第二五元组相同； PCRF实体将第一和第二 PCC规则下发 给 PCEF实体； PCEF实体执行第一和第二 PCC规则取消对特定业务数据流的用量监 控。 根据本发明的另一个实施例， 还提供一种策略和计费执行功能实体， 应用于对多 个业务数据流进行组用量监控的过程中， 包括： 第一接收模块， 设置为接收来自于策 略和计费规则功能 PCRF实体的针对多个业务数据流中的特定业务数据流的用量监控 操作指示； 第一调整模块， 设置为根据第一接收模块接收的用量监控操作指示， 对特 定业务数据流的用量监控实施调整。 根据本发明的再一方面， 提供一种数据流的用量监控装置， 包括： PCRF 实体、 PCEF 实体， 应用于对多个业务数据流进行组用量监控的过程中， 其中， 上述 PCEF 实体包括： 第二接收模块， 设置为接收来自于 PCRF实体的针对多个业务数据流中的 特定业务数据流的用量监控操作指示； 第二调整模块， 设置为根据第二接收模块接收 的用量监控操作指示， 对特定业务数据流的用量监控实施调整。 上述 PCRF实体包括： 第三接收模块， 设置为接收针对特定业务数据流执行用量 监控操作的触发指示； 发送模块， 设置为根据触发指示下发用量监控操作指示。 上述用量监控操作指示包括以下之一： 用量监控撤销指示、 用量监控增加指示； 其中， 用量监控撤销指示用于指示在所述组用量监控中停止针对特定业务数据流的用 量监控， 用量监控增加指示用于指示在所述组用量监控中增加针对特定业务数据流的 用量监控。 通过本发明，采用 PCRF实体向 PCEF实体下发其接收到的用量监控操作指示（即 PCEF实体接收来自于 PCRF实体的用量监控操作指示）的技术手段，解决了相关技术 中， 无法解决组用量监控过程中对特定业务数据流 （一个或多个） 的用量监控进行管 理 （例如将所述业务数据流的用量监控从所述组用量监控中取消， 或者将针对所述业 务数据流的用量监控增加到所述组用量监控中） 的问题， 进而达到了可以方便地对组 用量监控进行管理的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部分， 本发 明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的不当限定。 在附图 中： 图 1为根据相关技术的 3GPP PCC R8架构示意图； 图 2为根据相关技术的用量监控实现流程示意图； 图 3为根据本发明实施例的数据流的用量监控方法的流程图； 图 4为根据本发明实例 2的数据流的用量监控方法的流程示意图； 图 5为根据本发明实例 3的数据流的用量监控方法的流程示意图； 图 6为根据本发明实例 4的数据流的用量监控方法的流程示意图； 图 7为根据本发明实施例的策略和计费执行功能实体的结构框图； 图 8为根据本发明实施例的数据流的用量监控装置示意图； 图 9为根据本发明优选实施例的数据流的用量监控装置示意图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在不冲突的 情况下， 本申请中的实施例及实施例中的特征可以相互组合。 图 3为根据本发明实施例的数据流的用量监控方法的流程图。 如图 3所示， 该流 程包括： 步骤 S302, 在对多个业务数据流进行组用量监控的过程中， PCEF实体接收来自 于策略和计费规则功能 PCRF实体的针对多个业务数据流中的特定业务数据流的用量 监控操作指示； 步骤 S304， PCEF实体根据接收的用量监控操作指示， 对特定业务数据流的用量 监控实施调整。 在实际应用时， 上述特定业务数据流可以为一个或多个。 上述实施例中，由于 PCEF实体接收来自于 PCRF实体的用量监控操作指示， PCEF 实体根据上述用量监控操作指示对特定业务数据流的用量监控在组用量监控中实施调 整 （例如将针对所述业务数据流的用量监控从所述组用量监控中取消， 或者将针对所 述业务数据流的用量监控增加到所述组用量监控中），因此可以解决对组用量监控进行 管理。 在具体应用过程中， 上述方法还可以包括以下处理过程： PCRF 实体接收针对特 定业务数据流执行用量监控操作的触发指示； PCRF 实体根据触发指示下发用量监控 操作指示。 如果包括， 则上述处理过程可以在上述 PCEF实体接收来自于 PCRF实体 的针对多个业务数据流中的特定业务数据流的用量监控操作指示之前进行。 通过上述 处理过程， PCRF实体可以在收到触发指示后再下发用量监控操作指示。 在具体应用过程中， 上述用量监控操作指示包括但不限于以下之一： 用量监控撤 销指示、 用量监控增加指示； 其中， 用量监控撤销指示用于指示停止在所述组用量监 控中针对特定业务数据流的用量监控， 用量监控增加指示用于指示在所述组用量监控 中增加针对特定业务数据流的用量监控。 这样， 通过上述指示信息可以对组用量监控 中的特定业务数据流的用量监控进行撤销或增加。 在具体应用过程中， 上述方法还包括： 用量监控操作指示为用量监控撤销指示时， 用量监控操作指示包括： 分配给特定业务数据流的监控标识 monitoring key、针对特定 业务数据流的用量监控撤销标识； 用量监控操作指示为用量监控增加指示时， 用量监 控操作指示包括： 分配给特定业务数据流的监控标识 monitoring key、针对特定业务数 据流的用量监控执行标识。 在具体应用过程中， 上述用量监控操作指示为用量监控撤销指示时， PCEF 实体 根据接收的用量监控操作指示， 对特定业务数据流的用量监控实施调整， 还可以包括 以下处理过程： PCRF实体针对特定业务数据流产生第一策略和计费控制 PCC规则和 第二 PCC规则两个 PCC规则；其中，第一 PCC规则为已经在 PCEF实体上安装的 PCC 规则， 包括： 第一五元组、 监控标识 monitoring key、 第一优先级、 删除 PCC规则操 作指示； 第二 PCC规则包括： 第二五元组、 第二优先级、 安装 PCC规则操作指示； 第一优先级低于第二优先级； 第一五元组和第二五元组相同； PCRF 实体将第一和第 二 PCC规则下发给 PCEF实体； PCEF实体执行第一和第二 PCC规则取消对特定业务 数据流的用量监控。 在具体实施时， 可以直接根据上述用量监控操作指示撤销上述特 定业务数据流的用量监控， 也可以根据上述处理过程撤销上述特定业务数据流的用量 监控。 在具体实施时， PCEF收到所述 PCC规则之后， 由于第一优先级低于第二优先 级先安装新 PCC规则，再删除原有 PCC规则，并且由于新 PCC规则中不包含 monitoring key, 因此将取消对应业务数据流的用量监控。 需要说明的是， 在上述处理过程中， 可 以认为上述用量监控操作指示可以包括第一 PCC规则和第二 PCC规则， 因此， 上述 处理过程与上述 PCEF实体根据接收的用量监控操作指示， 对特定业务数据流的用量 监控实施调整并不冲突。 实例 1 针对现有用量监控上报机制尚无法解决从组用量监控中取消针对特定业务数据流 的用量监控的问题， 本实例提出了针对业务数据流实施用量监控的方法， 以解决上述 问题， 同时也可以实现将特定业务数据流的用量监控加入组用量监控中。 具体技术方 案如下： 前提条件： 针对特定业务数据流实施用量监控， 为所述业务数据流下发 PCC规则 (用 charging rule definition表示， 同时用 charging rule name标识）， 所述 PCC规则中 包含 Monitoring key, PCRF下发所述 PCC规则的同时， 下发针对所述 Monitoring key 的用量监控信息 （用 Usage Monitoring Information表示）。 对标识了 Monitoring key的 业务数据流实施用量监控。如果多个业务数据流使用相同的 monitoring key, 则对上述 多个业务数据流实施组用量监控。 如果此时 PCRF收到对上述特定业务数据流的用量 监控实施操作的指示， 则对所述业务数据流的用量监控实现方法如下：
PCRF向 PCEF下发针对该业务数据流的用量监控操作指示； 所述操作指示包括： 用量监控撤销或 用量监控增加; 所述操作指示包含在所述用量监控信息 （Usage Monitoring Information) 中。 所述用量监控信息中还包含所述业务数据流对应的 PCC规则标识（即 charging rule name) PCEF收到所述用量监控操作指示后， 对所述 PCC规则对应的业务数据流的用量 监控按照指示内容实施调整。 上述用量监控调整具体为： 如果指示内容为用量监控撤销， 则将针对所述业务数 据流的用量监控从所述 monitoring key对应的用量监控组中取消； 如果指示内容为用 量监控增加， 则将所述业务数据流加入 Monitoring key对应的用量监控组中， 对所述 业务数据流实施用量监控。 针对从组用量监控中撤销针对某一业务数据流的用量监控的需求， 本实例提出了 一种替代方案： 当 PCRF收到对上述特定业务数据流的用量监控取消的指示， 对所述业务数据流 的用量监控实施撤销的实现方法如下： PCRF针对所述业务数据流决策产生第一和第二 PCC规则， 并下发给 PCEF。 所述 PCC规则中，其中第一 PCC规则为已经在 PCEF上安装的 PCC规贝 1」，包括： 第一五元组、 监控标识 monitoring key、 第一优先级、 删除所述 PCC规则操作指示； 所述第二 PCC规则包括： 第二五元组、 第二优先级、 安装所述 PCC规则操作指示； 所述第一优先级低于所述第二优先级； 所述第一五元组和第二五元组相同， 即两个规 则同时为业务数据流所用。
PCEF收到所述 PCC规则之后， 按照优先级先安装第二 PCC规则， 再删除第一 PCC规则。 由于第二 PCC规则中不包含 monitoring key, 因此将取消对应业务数据流的用量 监控。 实例 2 本实例给出了对业务数据流 -1取消用量监控的实施例。 本实例的假设前提如下， 需要对两个业务数据流 （业务数据流 -1 和业务数据流 -2) 实施用量监控， PCRF 为业 务数据流 -1决策产生 PCC规则 -1 (用 charging rule name-1标识）， 为业务数据流 -2决 策产生 PCC规则 -2 (用 charging rule name-2标识）， 同时为这两个 PCC规则分配相同 的 monitoring key, 并为该 monitoring key产生对应的用量监控信息 (usage monitoring information) 0 在用量监控过程中， 需要对业务数据流 -1取消用量监控， 其实现如图 4 所示。 流程描述如下： 步骤 S402， PCRF收到来自 PCEF的授权请求； 步骤 S404， PCRF向 PCEF返回授权结果， 同时 PCRF向 PCEF下发针对业务数 据流 -1和业务数据流 -2的用量监控指示。 例如按照如下形式下发：
Charging rule definition- 1 [charging rule name-1, monitoring key]
Charging rule definition-2
[charging rule name-2, monitoring key] Usage monitoring Information
[monitoring key, granted service unit] 其中，业务数据流 -1对应的 PCC规则用 charging rule definition- 1表示，包含了 PCC 规则标识 charging rule name-1和用量监控标识 monitoring key; 业务数据流 -2对应的 PCC规则用 charging rule definition-2表示， 包含了 PCC规则标识 charging rule name-2 和用量监控标识 monitoring key。 PCRF同时将所述 monitoring key对应的用量监控信 息 usage monitoring information下发给 PCEF, 包含了所述 monitoring key禾口对应的阈 值 granted service unit。 步骤 S406， 按照 PCRF下发的用量监控指示， PCEF对业务数据流 -1和业务数据 流 -2实施用量监控。 步骤 S408， PCRF收到针对业务数据流 -1取消用量监控的指示。 步骤 S410， PCRF向 PCEF下发针对业务数据流 -1的用量监控取消的指示。 例如 按照如下形式下发：
Usage monitoring information
(monitoring key) (usage monitoring feature)
[usage monitoring support = disabled]
[charging rule name-1]
PCRF下发的取消用量监控的指示信息在 Usage monitoring information中包含。 Usage monitoring information包含了 monitoring key禾口 usage monitoring feature, 其中 monitoring key 为步骤 S404 中针对业务数据流 -1 实施用量监控所使用的 monitoring key。 usage monitoring feature包含了 usage monitoring support禾口 charging rule name-1， 其中 usage monitoring support取值为 disabled (即用量监控撤销标识）， 表示需要取消 charging rule name-l(即业务数据流 -1) 在所述 monitoring key对应的用量监控组中的用 量监控。如果 usage monitoring feature中只包含了 usage monitoring support=disabled (即 用量监控增加标识）， 而不包含 charging rule name 则表示需要取消标识了所述 monitoring key的所有业务数据流的用量监控。 步骤 S412， PCEF向 PCRF返回确认消息。 步骤 S414, 按照 PCRF下发的针对业务数据流 -1 的用量监控取消的指示， PCEF 进行用量监控调整， 即从 charging rule defmition-1中删除 monitoring key, 停止对业务 数据流 -1在所述 monitoring key对应的用量监控组中的用量监控。 实例 3 本实例给出了对业务数据流 -1取消用量监控的实施例。本实施例的假设前提如下， 需要对两个业务数据流 （业务数据流 -1 和业务数据流 -2) 实施用量监控， PCRF 为业 务数据流 -1决策产生 PCC规则 -1 (用 charging rule name-1标识）， 为业务数据流 -2决 策产生 PCC规则 -2 (用 charging rule name-2标识）， 同时为这两个 PCC规则分配相同 的 monitoring key- 1， 并为该 monitoring key- 1 产生对应的用量监控信息 （ usage monitoring information )0 在用量监控过程中， 需要对业务数据流 -1从上述用量监控组 中取消， 同时将之加入到另外的用量监控组（用 monitoring key-2表示） 中， 其实现如 图 4所示。 流程描述如下： 步骤 S502， PCRF收到来自 PCEF的授权请求。 步骤 S504， PCRF向 PCEF返回授权结果， 同时 PCRF向 PCEF下发针对业务数 据流 -1和业务数据流 -2的用量监控指示。 例如按照如下形式下发：
Charging rule definition- 1 [charging rule name-1, monitoring key-1] Charging rule definition-2
[charging rule name-2, monitoring key-1]
Usage monitoring Information [monitoring key-1, granted service unit] 其中，业务数据流 -1对应的 PCC规则用 charging rule definition- 1表示，包含了 PCC 规则标识 charging rule name-1和用量监控标识 monitoring key-1 ;业务数据流 -2对应的 PCC规则用 charging rule definition-2表示， 包含了 PCC规则标识 charging rule name-2 和用量监控标识 monitoring key-1。 PCRF同时将所述 monitoring key-1对应的用量监控 信息 usage monitoring information下发给 PCEF，包含了所述 monitoring key-1和对应的 阈值 granted service unit。 步骤 S506， 按照 PCRF下发的用量监控指示， PCEF对业务数据流 -1和业务数据 流 -2实施用量监控。 步骤 S508， PCRF收到将业务数据流 -1从 monitoring key-1对应的用量监控组中取 消， 同时将之加入 monitoring key-2对应的用量监控组的指示。 步骤 S510， PCRF向 PCEF下发所述指示。 例如按照如下形式下发： Usage monitoring information- 1
(monitoring key-1) (usage monitoring feature) [usage monitoring support = disabled]
[charging rule name-1] Usage monitoring information-2
(monitoring key-2)
(usage monitoring feature)
[usage monitoring support = enabled] [charging rule name-1]
PCRF 下发针对业务数据流 -1 的用量监控调整指示信息包含 Usage monitoring information- 1禾口 Usage monitoring information-20 其中 Usage monitoring information- 1 用于指示将 charging rule name- 即业务数据流 -1)的用量监控从 monitoring key-1对应 的用量监控组中取消， Usage monitoring information-2指示将 charging rule name- 1(即业 务数据流 -1)加入到 monitoring key-2对应的用量监控组中。 步骤 S512， PCEF向 PCRF返回确认消息。 步骤 S514, 按照 PCRF下发的针对业务数据流 -1 的用量监控调整的指示， PCEF 从 charging rule definition- 1中删除 monitoring key- 1， 即将业务数据流- 1的用量监控从 所述 monitoring key-1对应的用量监控组中取消， 同时在 charging rule definition- 1中增 力口 monitoring key-2, 表示将业务数据流 -1加入 monitoring key-2对应的用量监控组中。 实例 4 本实例的假设前提如下， 需要对两个业务数据流（业务数据流 -1和业务数据流 -2) 实施用量监控， PCRF为业务数据流 -1决策产生 PCC规则 -1 (用 charging rule name-1 标识）， 为业务数据流 -2决策产生 PCC规则 -2 (用 charging rule name-2标识）， 同时为 这两个 PCC规则分配相同的 monitoring key,并为该 monitoring key产生用量监控信息 (usage monitoring information )0在用量监控过程中， 需要对业务数据流 -1取消用量监 控， 其实现如图 6所示。 流程描述如下： 步骤 S602， PCRF收到来自 PCEF的授权请求。 步骤 S604， PCRF向 PCEF返回授权结果， 同时 PCRF向 PCEF下发针对业务数 据流 -1和业务数据流 -2的用量监控指示。 例如按照如下形式下发：
Charging rule definition- 1
[charging rule name-1, monitoring key] Charging rule definition-2 [charging rule name-2, monitoring key]
Usage monitoring Information
[monitoring key, granted service unit] 其中，业务数据流 -1对应的 PCC规则用 charging rule definition- 1表示，包含了 PCC 规则标识 charging rule name- 1和用量监控标识 monitoring key; 业务数据流 -2对应的 PCC规则用 charging rule definition-2表示， 包含了 PCC规则标识 charging rule name-2 和用量监控标识 monitoring key。 PCRF同时将所述 monitoring key对应的用量监控信 息 usage monitoring information下发给 PCEF， 包含了所述 monitoring key禾口对应的阈 值 granted service unit。 步骤 S606， 按照 PCRF下发的用量监控指示， PCEF对业务数据流 -1和业务数据 流 -2实施用量监控。 步骤 S608， PCRF收到针对业务数据流 -1取消用量监控的指示。 步骤 S610， PCRF重新为业务数据流 -1决策产生控制策略。 PCRF为业务数据流
-1产生两个 PCC规贝 ij， 其中 PCC规则 -1 (用 charging rule definition- 1表示）为原来已 经安装到 PCEF的规则， PCC规则 -3 (用 charging rule defmition-3表示） 为新 PCC规 贝1」。 PCRF下发 RAR消息中 包含的信息如下：
Charging rule remove [charging rule definition- 1 (charging rule name-1, 5 -tuple , monitoring key, precedence)]
Charging rule install
[charging rule definition-3 (charging rule name-3, 5 -tuple, precedence)] 其中 charging rule remove表示要删除 PCC规则 -1 (即用 charging rule name-1标 识）， charging rule install表示安装 PCC规则 -3 (即用 charging rule name-3标识）。 PCC 规则 -1和 PCC规则 -3具有相同的五元组信息 （用 5-tuple表示）。 PCC规则 -1中包含 monitoring key, 但 PCC规则 -3中不包含。 PCC规则 -1的优先级设置低于 PCC规则 -3 的优先级， 表示优先执行 PCC规则 -3。 步骤 S612， PCEF返回 RAA响应。 步骤 S614， PCEF收到 PCRF下发的策略之后， 按照 PCC规则执行优先级， 首先 安装 PCC规则 -3， 然后删除 PCC规则 -1。 由于 PCC规则 -3和 PCC规则 -1都是和业务 数据流 -1绑定的，而当前激活的 PCC-规则 -3中不包含 monitoring key,即按照新的 PCC 规则， 不需要对业务数据流 -1 实施用量监控。 因此为业务数据流 -1 安装新的不包含 monitoring key的 PCC规则， 删除原来包含 monitoring key的 PCC规则， 可以实现撤 销对业务数据流 -1的用量监控。 图 7 为根据本发明实施例的策略和计费执行功能实体的结构框图。 本实例中的 PCEF实体应用于对多个业务数据流进行组用量监控的过程中， 如图 7所示， 该 PCEF 实体包括： 第一接收模块 70， 设置为接收来自于策略和计费规则功能 PCRF实体的针对多个 业务数据流中的特定业务数据流的用量监控操作指示； 第一调整模块 72， 与第一接收模块 70相连， 设置为根据第一接收模块 70接收的 用量监控操作指示， 对特定业务数据流的用量监控实施调整。 图 8为根据本发明实施例的数据流的用量监控装置示意图。 本实施例中的装置应 用于对多个业务数据流进行组用量监控的过程中， 如图 8 所示， 该装置包括： PCRF 实体 80、 PCEF实体 82， 其中， 上述 PCEF实体 82包括： 第二接收模块 820， 与 PCRF实体 80相连， 设置为接 收来自于 PCRF实体 80的针对多个业务数据流中的特定业务数据流的用量监控操作指 示； 第二调整模块 822， 与第二接收模块 820相连， 设置为根据第二接收模块 820接 收的用量监控操作指示， 对特定业务数据流的用量监控实施调整。 在具体应用过程中， 如图 9所示， 上述 PCRF实体 80包括： 第三接收模块 800， 设置为接收针对特定业务数据流执行用量监控操作的触发指示； 发送模块 802， 与第 三接收模块 800相连， 设置为根据触发指示下发用量监控操作指示。 在具体应用过程中， 上述用量监控操作指示包括以下之一： 用量监控撤销指示、 用量监控增加指示； 其中， 用量监控撤销指示用于指示在所述组用量监控中停止针对 特定业务数据流的用量监控， 用量监控增加指示用于指示在所述组用量监控中增加针 对特定业务数据流的用量监控。 需要注意的是， 上述装置或实体中的各模块相关结合的优选工作方式具体可以上 述方法实施例的描述， 此处不再赘述。 从以上的描述中， 可以看出， 本发明实现了如下技术效果： 通过本发明， 采用 PCRF实体向 PCEF实体下发其接收到的用量监控操作指示的 技术手段， 解决了相关技术中， 无法解决组用量监控中对特定业务数据流 （一个或多 个） 的用量监控进行管理 （例如将所述业务数据流的用量监控从所述组用量监控中取 消， 或者将针对所述业务数据流的用量监控增加到所述组用量监控中） 的问题， 进而 达到了可以方便地对组用量监控进行管理的效果。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布在多个计算装置所 组成的网络上， 可选地， 它们可以用计算装置可执行的程序代码来实现， 从而， 可以 将它们存储在存储装置中由计算装置来执行， 并且在某些情况下， 可以以不同于此处 的顺序执行所示出或描述的步骤， 或者将它们分别制作成各个集成电路模块， 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样， 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域的技 术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内， 所作的 任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1. 一种数据流的用量监控方法， 包括：
在对多个业务数据流进行组用量监控的过程中，策略和计费执行功能 PCEF 实体接收来自于策略和计费规则功能 PCRF实体的针对所述多个业务数据流中 的特定业务数据流的用量监控操作指示；
所述 PCEF实体根据接收的所述用量监控操作指示， 对所述特定业务数据 流的用量监控实施调整。
2. 根据权利要求 1所述的方法， 其中， 所述 PCEF实体接收来自于 PCRF实体的 针对所述多个业务数据流中的特定业务数据流的用量监控操作指示之前， 还包 括：
所述 PCRF实体接收针对所述特定业务数据流执行用量监控操作的触发指 示；
所述 PCRF实体根据所述触发指示下发所述用量监控操作指示。
3. 根据权利要求 1或 2所述的方法，其中，所述用量监控操作指示包括以下之一:
用量监控撤销指示、 用量监控增加指示；
其中， 所述用量监控撤销指示用于指示在所述组用量监控中停止针对所述 特定业务数据流的用量监控， 所述用量监控增加指示用于指示在所述组用量监 控中增加针对所述特定业务数据流的用量监控。
4. 根据权利要求 3所述的方法， 其中， 还包括： 所述用量监控操作指示为所述用量监控撤销指示时， 所述用量监控操作指 示包括： 分配给所述特定业务数据流的监控标识 monitoring key、针对所述特定 业务数据流的用量监控撤销标识；
所述用量监控操作指示为所述用量监控增加指示时， 所述用量监控操作指 示包括： 分配给所述特定业务数据流的监控标识 monitoring key、针对所述特定 业务数据流的用量监控执行标识。
5. 根据权利要求 3所述的方法， 其中， 所述用量监控操作指示为所述用量监控撤 销指示时， 所述 PCEF实体根据接收的所述用量监控操作指示， 对所述特定业 务数据流的用量监控实施调整， 包括：
所述用量监控撤销指示为所述 PCRF实体针对所述特定业务数据流产生的 第一策略和计费控制 PCC规则和第二 PCC规则两个 PCC规则；
其中， 所述第一 PCC规则为已经在所述 PCEF实体上安装的 PCC规则， 包括： 第一五元组、 监控标识 monitoring key、 第一优先级、 删除所述 PCC规 则操作指示； 所述第二 PCC 规则包括： 第二五元组、 第二优先级、 安装所述 PCC规则操作指示； 所述第一优先级低于所述第二优先级； 所述第一五元组和 第二五元组相同；
所述 PCRF实体将所述第一和第二 PCC规则下发给所述 PCEF实体； 所述 PCEF实体执行所述第一和第二 PCC规则取消对所述特定业务数据流 的用量监控。
6. 一种策略和计费执行功能实体， 应用于对多个业务数据流进行组用量监控的过 程中， 包括：
第一接收模块， 设置为接收来自于策略和计费规则功能 PCRF实体的针对 所述多个业务数据流中的特定业务数据流的用量监控操作指示；
第一调整模块， 设置为根据所述第一接收模块接收的所述用量监控操作指 示， 对所述特定业务数据流的用量监控实施调整。
7. 一种数据流的用量监控装置， 包括： PCRF实体、 PCEF实体， 应用于对多个业 务数据流进行组用量监控的过程中， 其中， 所述 PCEF实体包括：
第二接收模块， 设置为接收来自于所述 PCRF实体的针对所述多个业务数 据流中的特定业务数据流的用量监控操作指示；
第二调整模块， 设置为根据所述第二接收模块接收的所述用量监控操作指 示， 对所述特定业务数据流的用量监控实施调整。
8. 根据权利要求 7所述的装置， 其中， 所述 PCRF实体包括： 第三接收模块， 设置为接收针对所述特定业务数据流执行用量监控操作的 触发指示；
发送模块， 设置为根据所述触发指示下发所述用量监控操作指示。 根据权利要求 7或 8所述的装置，其中，所述用量监控操作指示包括以下之一: 用量监控撤销指示、 用量监控增加指示；
其中， 所述用量监控撤销指示用于指示在所述组用量监控中停止针对所述 特定业务数据流的用量监控， 所述用量监控增加指示用于指示在所述组用量监 控中增加针对所述特定业务数据流的用量监控。
PCT/CN2012/076211 2011-06-17 2012-05-29 数据流的用量监控方法及装置、pcef实体 WO2012171431A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110163684.3A CN102833123B (zh) 2011-06-17 数据流的用量监控方法及装置、pcef实体
CN201110163684.3 2011-06-17

Publications (1)

Publication Number Publication Date
WO2012171431A1 true WO2012171431A1 (zh) 2012-12-20

Family

ID=47336101

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/076211 WO2012171431A1 (zh) 2011-06-17 2012-05-29 数据流的用量监控方法及装置、pcef实体

Country Status (1)

Country Link
WO (1) WO2012171431A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100050016A (ko) * 2008-11-04 2010-05-13 주식회사 케이티 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102083035A (zh) * 2009-11-30 2011-06-01 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102421081A (zh) * 2010-09-28 2012-04-18 中兴通讯股份有限公司 一种用量监测方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100050016A (ko) * 2008-11-04 2010-05-13 주식회사 케이티 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102083035A (zh) * 2009-11-30 2011-06-01 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102421081A (zh) * 2010-09-28 2012-04-18 中兴通讯股份有限公司 一种用量监测方法及系统

Also Published As

Publication number Publication date
CN102833123A (zh) 2012-12-19

Similar Documents

Publication Publication Date Title
US10623584B2 (en) Charging session management method and apparatus
CA2682979C (en) Method, system and entity of realizing event detection
RU2513711C2 (ru) Триггер события услуги
WO2013007142A1 (zh) 一种用量监控方法及系统
WO2009046678A1 (fr) Procédé et dispositif pour obtenir la capacité de fonction d'application de politique et de facturation
US20130122860A1 (en) Method for providing a monitoring of usage network resources of a user session within a network and a network device
RU2435205C2 (ru) Способ законного перехвата информации и устройство для этого
WO2010121565A1 (zh) 业务优先级更新指示方法、业务优先级更新方法及装置
WO2011097911A1 (zh) 策略和计费规则功能实体的选择方法、装置及系统
WO2012058998A1 (zh) 漫游场景下支持ip流迁移的策略计费控制方法和系统
WO2011079773A1 (zh) 用户会话策略控制方法、装置及系统
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及系统
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2015055063A1 (zh) 应用接入控制方法及应用功能实体装置
WO2015021856A1 (zh) 一种网络容量控制方法及装置
WO2014101239A1 (zh) 策略和计费控制方法及设备
WO2013013547A1 (zh) 一种组用户用量监控方法及系统
WO2014040517A1 (zh) 网络策略的控制方法、装置及系统
KR101007736B1 (ko) 정책 기반 네트워크 시스템 및 네트워크 정책 관리 방법
WO2011088702A1 (zh) 在全业务融合网络中控制资源的方法和系统
US8442480B2 (en) Priority communications in a shared access telecommunications network
WO2013086668A1 (zh) 策略和计费控制方法、实体及系统
WO2011003307A1 (zh) 用于演进分组系统的计费方法及系统
WO2012171431A1 (zh) 数据流的用量监控方法及装置、pcef实体
WO2014079294A1 (zh) 管理数据流的方法和系统

Legal Events

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

Ref document number: 12799983

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

Country of ref document: EP

Kind code of ref document: A1