WO2012041148A1

WO2012041148A1 - Method and system for monitoring volume usage

Info

Publication number: WO2012041148A1
Application number: PCT/CN2011/079207
Authority: WO
Inventors: 周晓云; 宗在峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-09-28
Filing date: 2011-08-31
Publication date: 2012-04-05
Also published as: CN102421081A; CN102421081B

Abstract

A method and system for monitoring volume usage are provided. The method includes: when forwarding a monitoring key to a Policy Enforcement Functional Entity (PE-FE), a Policy and Charging Rules Function (PCRF) instructs the PE-FE not to add the volume usage of the Monitoring Key into the session level volume usage. Said technical solution avoids mistakenly adding the volume used for free into the volume usage of an IP-CAN session, and can also provide separate volume usage monitoring on designated service streams in the IP-CAN session, thus meeting the requirements for separate volume usage monitoring.

Description

Method and system for monitoring usage

Technical field

The present invention relates to dosage monitoring techniques and, more particularly, to a dosage monitoring method and system. Background technique

The 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project)'s Policy and Charging Control (PCC) architecture is a functional framework that can be applied to multiple access technologies. For example, a UMTS Terrestrial Radio Access Network (UMRAN, Global System for Mobile Communication)/GSM data enhancement applied to the Universal Mobile Telecommunications System (UMTS) EDGE (Enhanced Data Rates for Global Evolution) radio access network, interworking wireless local area network (I-WLAN), and evolved packet system (EPS, Evolved Packet System).

1 is a schematic diagram of a prior art Rel-8 PCC non-roaming architecture, which is described below with reference to FIG.

The various logical functional entities in the PCC architecture and their interface functions are described:

The application function entity (AF, Application Function) provides access points for service applications. The network resources used by these service applications need dynamic policy control. When the parameter negotiation is performed on the service plane, the AF transmits the related service information to the Policy and Charging Rules Function (PCRF). If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF accepts the negotiation; The PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment). The interface between AF and PCRF is the Rx interface.

The PCRF is the core of the PCC and is responsible for policy decision making and billing rules. The PCRF provides network control rules based on service data flows, including traffic data flow monitoring, 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), and the PCRF There is also a need to ensure that these rules are consistent with the user's contract information. The basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the user policy charging control subscription information from the SPR (Spent Profile Repository); and acquiring the information related to the bearer related network from the PCEF.

The PCEF is used to enforce the policy and charging rules established by the PCRF on the bearer plane. PCEF according to

The service data flow filter in the rule sent by the PCRF monitors the service data flow, and then executes the policy and charging rules formulated by the PCRF for these service data flows. When the bearer is established, the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF. According to the charging rule sent by the PCRF, the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online billing, PCEF needs to be credit managed with the Online Charging System (OCS). When offline charging, the relevant accounting information is exchanged between the PCEF and the Offline Charging System (OFCS). The interface between PCEF and PCRF is Gx interface, the interface between OCE and OCS is Gy interface, and the interface between OFCS and OFCS is Gz interface. PCEF can also have Application Detection and Control (ADC). The PCEF can perform application detection and perform policy enforcement (such as gating, redirection, bandwidth limitation, and usage monitoring) according to the local configuration or the ADC rules that are sent by the PCRF and include the application detection control policy. The PCEF is usually located in the gateway (Gate-Way, GW for short), such as the GPRS Gateway Support Node (GGSN) in GPRS and the Packet Data Gateway (PDG) in I-WLAN.

In addition, there may be a traffic detection function (TDF) in the network. At this time, the TDF and the PCRF are connected to the Sd interface, and the TDF can perform application detection and policy execution according to the ADC rules delivered by the pre-configuration or the PCRF.

The Bearer Binding and Event Reporting Function (BBERF), whose functions include bearer binding, verification of uplink bearer binding, and event reporting. When the UE accesses through the E-UTRAN, and the PMIPv6 protocol is used between the S-GW and the P-GW, the BBERF is located at the S-GW, and when the UE accesses through the trusted non-3GPP access system, the BBERF is located at the trusted end. The non-3GPP access gateway, when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the Evolved Packet Data Gateway (ePDG). At this time, the PCEF no longer performs the bearer binding function. The User Contracting Database (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 are used to control and manage user credit under online charging mode.

OFCS and PCEF together perform the charging operation in the offline charging mode.

The above PCC architecture implements a packet data network for the UE to access through the functional entities.

(PDN, Packet Data Network) Established policy charging control for IP-Connected Network (IP-Connected Access Network) sessions.

In the prior art, the PCC supports dynamic usage monitoring control to implement dynamic policy decisions based on the real-time usage of network resources. Usage monitoring can be applied to a single service data stream, a group of service data streams, or all traffic flows for an IP-CAN session (IP-CAN session level). If the UE establishes multiple IP-CAN sessions to a PDN, the usage monitoring can also be applied to the multiple IP-CAN sessions. Currently, usage refers to user plane data traffic. Usually, the Monitoring Key is used to identify an instance that requires usage monitoring. For example: When the PCRF assigns a Monitoring Key and a corresponding threshold to all traffic flows of an IP-CAN session, then the PCEF will be based on the threshold. Monitor all traffic flows of the IP-CAN session and use the Monitoring Key to identify the reported usage. When the PCRF assigns a monitoring key and a corresponding threshold to a service flow or a group of service data flows, the PCRF carries the Monitoring Key in the PCC rule corresponding to the service data flow or a set of service data flows, then the PCEF will be based on The threshold value is used to monitor the service data flow corresponding to the PCC rule of the same Monitoring Key, and the usage amount is reported by the Monitoring Key. The current PCC architecture supports simultaneous monitoring of multiple Monitoring Key instances, including monitoring the usage of the entire IP-CAN session and the usage of a specific service data stream. The usage of the IP-CAN session corresponds to the Monitoring Key and the service data flow. The Monitoring Key is not the same.

Similarly, for TDF, usage monitoring can be applied to a single application, a group of applications, or all applications of a TDF session (TDF session level) (TDF sessions are typically associated with IP-CAN sessions). At this time, when the PCRF assigns a monitoring key and a corresponding threshold to an application or a group of applications, the PCRF carries the Monitoring Key in the ADC rule corresponding to the application or a group of applications, then the PCEF or TDF will be based on the The value monitors the traffic of the application corresponding to the ADC rule of the same Monitoring Key, and uses the Monitoring Key to identify the reported amount. At the same time, the total allowed amount of a certain PDN of a user can also be saved in the SPR, that is, the total allowed amount of all service flows for one IP-CAN session, which can also be called the total per PDN per user (Per PDN and UE). Allowable amount. The SPR can also store the total allowed usage of a specific service of a certain PDN of a user, that is, the total allowed usage for a service data stream or a group of service data streams, and can also be identified by a Monitoring Key.

When the user establishes an IP-CAN session to a PDN (the UE can establish one or more IP-CAN sessions with the PDN), the SPR will send the total allowed amount to the PCRF. When the PCRF performs the dose monitoring control, the PCRF subscribes to the PCEF subscription usage report (UR, Usage_Report) event trigger. When the Monitoring Key is included in the PCC rule, the PCC rules with the same Monitoring Key share the threshold corresponding to the Monitoring Key (the usage monitoring is for one or a group of service data streams, that is, the service data flow level). When the Monitoring Key is not included in any PCC rules, all traffic data streams of the IP-CAN session share the threshold corresponding to the Monitoring Key (the usage monitoring is for the IP-CAN session level). When PCEF detects that the usage has reached a threshold, the IP-CAN session is terminated, all PCC rules containing a Monitoring Key are deleted/deactivated, or the PCRF explicitly requests usage, the PCEF will report to PCRF 4 since the last time. The consumption of the related Monitoring Key since 4艮. When the PCRF receives the dose from the PCEF, the PCRF will deduct the reported usage value from the total allowable amount. If the PCEF reports the usage of a Monitoring Key and needs to continue monitoring, the PCRF will provide a new threshold to the PCEF; if no further monitoring is required, the PCRF will not provide a new threshold to the PCEF. When the last IP-CAN session of a user's Access Point Name (APN, Access Point Name) is terminated, the PCRF will save the remaining total allowed amount in the SPR, including the total allowed amount of the PDN or some of the PDN. The total allowable amount of specific business.

Similarly, for TDF, when a user establishes an IP-CAN session to a PDN, SPR will send the total allowed amount to the PCRF. When the PCRF performs the dose monitoring control, the PCRF subscribes to the PCEF subscription usage event trigger. When the Monitoring Key is included in the ADC rule, the ADC rule with the same Monitoring Key shares the threshold corresponding to the Monitoring Key. When the Monitoring Key is not included in any ADC rule, all applications of the TDF session share the threshold corresponding to the Monitoring Key. TDF monitors that the usage has reached a threshold, the TDF session is terminated, all ADC rules containing a Monitoring Key are deleted/deactivated or PCRF explicit When using the quantity "^艮, TDF will report to the PCRF the consumption of the relevant Monitoring Key since the last time. After the PCRF receives the dose from the TDF, the PCRF will deduct the total amount from the total allowable amount. The amount of usage. If the amount of a Monitoring Key is used on the TDF and needs to be monitored, the PCRF will provide a new threshold to the TDF; if it is not necessary to continue monitoring, the PCRF will not provide a new threshold to the TDF.

Currently, the PCC architecture supports usage monitoring called Sponsored Data Connectivity. The so-called sponsored data connection refers to the consumption consumption generated by the user's accessed service, which is not borne by the user but by the service provider. At this time, when the user initiates the service access, the AF provides the PCRF with the usage threshold of the service provider to access the service (that is, the user can access the service for free). In the present invention, the sponsored data connection is equivalent to the sponsored data connection service. At this time, the PCRF sets the amount of the PCEF monitoring according to the amount of the amount of the AF issued. When the threshold is reached, the PCEF notifies the PCRF.

However, the prior art has the following problems: If the user has the IP-CAN session-level usage subscription data in the SPR, that is, the PCRF needs to sign the SPR, and instruct the PCEF to monitor the cumulative usage of all the service data flows of the entire IP-CAN session. . At this time, the user accesses a service that is assisted by the data connection, and the AF will provide the funded amount to the PCRF, and the PCRF instructs the PCEF to monitor the amount of the sponsored data connection service. In this way, the PCEF will calculate the usage of the user's access to the sponsored data connection service in the amount of the entire IP-CAN session, which will eventually lead to errors in the usage monitoring.

In addition, the same problem occurs in the prior art if some or some of the services accessed by the user should not be accumulated into the IP-CAN session level according to the user subscription or network policy.

Similarly, when the PCC architecture introduces TDF and the TDF also performs usage monitoring control, if the user accesses the sponsored data connection or according to the user subscription or network policy, some or some services accessed by the user should not be accumulated into the TDF session level. The same problem occurs in the prior art when the amount is used.

Summary of the invention

The technical problem solved by the present invention is to provide a usage monitoring method and system, which does not accumulate the consumption consumption of the sponsored third party service during the IP-CAN session level usage monitoring. To solve the above technical problem, a usage monitoring method, the method includes: a policy and charging rule function entity (PCRF), when a monitoring key is sent to a policy and charging execution function entity (PCEF), The PCEF does not accumulate the usage of the Monitoring Key into the IP connection access network (IP-CAN session) level.

J3⁄4, the Monitoring Key includes:

The Monitoring Key corresponding to the specified one or a group of service data streams, or the Monitoring Key corresponding to the sponsored data connection

In addition, the PCRF indicates that the PCEF does not accumulate the usage of the Monitoring Key into the IP-CAN session level by sending an independent usage monitoring indication to the PCEF.

In addition, the independent usage monitoring indication includes: an independent usage monitoring indicator bit or identification information. In addition, the independent usage monitoring indication includes: a sponsored data connection indication.

In addition, the PCRF indicates that the PCEF does not accumulate the usage of the Monitoring Key into an IP-CAN session level by assigning a specific Monitoring Key to the service data stream or the sponsored data connection.

The specific Monitoring Key refers to one or more Monitoring Keys that are pre-agreed by the PCRF and the PCEF.

In addition, the independent usage monitoring indication includes: a sponsor identifier and/or an application service provider (ASP) identifier included in the policy and charging control rule formulated by the PCRF for the sponsored data connection service, or a specific Charging Key.

A usage monitoring system, the system includes an independent monitoring indication unit in the PCRF, and the independent monitoring indication unit is configured to: when the Monitoring Key is sent to the PCEF, instruct the PCEF not to accumulate the usage of the Monitoring Key into the IP address. -CAN session level usage.

In addition, the independent monitoring indication unit is further configured to: when the monitoring key corresponding to the specified one or a group of service data flows or the monitoring key corresponding to the sponsored data connection is sent, indicating that the PCEF does not use the monitoring key The amount of usage is accumulated into the IP-CAN session level.

In addition, the system also includes an independent monitoring execution unit in the PCEF. The independent monitoring indication unit is further configured to: indicate that the PCEF does not use the Monitoring Key by sending an independent usage monitoring indication to the PCEF, or assigning a specific Monitoring Key to the service data flow or the sponsored data connection. The amount of usage is accumulated into the IP-CAN session level;

The independent monitoring execution unit is configured to accumulate the usage amount corresponding to the Monitoring Key into an IP-CAN session level according to the independent usage monitoring indication or the specific Monitoring Key;

In addition, the independent usage monitoring indication delivered by the independent monitoring indication unit includes: a sponsored data connection indication, an independent usage monitoring indicator bit or identification information; or, the PCRF formulas a policy for the sponsored data connection and The sponsor identification and/or ASP identification, or a specific charging key included in the charging control rule.

A method for monitoring usage includes:

The Policy and Charging Rules Function Entity (PCRF) sends a monitoring key to the policy enforcement function entity.

(Monitoring Key), indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level.

The Monitoring Key includes:

The specified one or a group of business data streams or the corresponding Monitoring Key of the application; or,

The step of the PCRF indicating that the policy enforcement function entity does not accumulate the usage of the Monitoring Key into the session level includes:

The PCRF sends an independent usage monitoring indication to the policy enforcement function entity, indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level.

The independent usage monitoring indication includes: an independent usage monitoring indicator bit or identification information. The independent usage monitoring indication includes: a sponsored data connection indication. The step of the PCRF indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level includes:

The PCRF indicates that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level by assigning a specific Monitoring Key to the service data flow, the application, or the sponsored data connection;

The specific Monitoring Key refers to one or more Monitoring Keys that are pre-agreed by the PCRF and the policy enforcement function entity.

The independent usage monitoring indication includes:

The PCRF is a sponsor identity and an application service provider (ASP) identifier included in the policy and charging control rule formulated by the sponsored data connection service; or

The PCRF is a specific Charging Key included in the policy and charging control rules formulated by the sponsored data connection service.

The policy execution function entity is a policy and charging execution function PCEF, and correspondingly, the session level usage is an IP-CAN session level usage; or

The policy execution function entity is an application monitoring function TDF. Correspondingly, the session level usage is a TDF session level usage.

Wherein: the specified one or a group of service data streams or applications are:

Business data flows or applications that should not be aggregated into session-level usage based on user subscriptions or network policies.

A usage monitoring system including a policy and charging rule functional entity

Independent monitoring indicator unit (PCRF),

The independent monitoring indication unit is configured to: when the monitoring key is sent to the policy execution function entity, the policy execution function entity is instructed not to accumulate the usage of the monitoring key into the usage level of the session level.

The Monitoring Key includes:

The usage monitoring system further includes an independent monitoring execution unit in the policy enforcement function entity, wherein: the independent monitoring indication unit is configured to instruct the policy execution function entity not to accumulate the usage of the Monitoring Key into a session level according to the following manner In the usage, the independent usage monitoring indication is issued by executing the functional entity to the policy;

The independent monitoring execution unit is configured to: not according to the independent usage monitoring indication

The amount corresponding to the Monitoring Key is accumulated into the session level.

The independent usage monitoring indication includes: an independent usage monitoring indicator bit or identification information. The independent usage monitoring indication includes: a sponsored data connection indication.

The independent usage monitoring indication includes:

The usage monitoring system further includes an independent monitoring execution unit in the policy enforcement function entity, wherein: the independent monitoring indication unit is configured to instruct the policy execution function entity not to accumulate the usage of the Monitoring Key into a session level according to the following manner In an amount of usage, a specific monitoring key is allocated to the service data flow, the application, or the sponsored data connection, indicating that the policy execution function entity does not accumulate the usage of the monitoring key into a session level; The independent monitoring execution unit is configured to: according to the specific monitoring key, not accumulating the usage amount corresponding to the monitoring key into the session level;

The policy execution function entity is a policy and charging execution function PCEF, and correspondingly, the session level usage is an IP-CAN session level usage;

Wherein: the specified one or a group of service data streams or applications are: Service data flow that should not be aggregated into session level usage based on user subscription or network policy or should

The technical solution of the present invention, when the PCRF sends the Monitoring Key to the PCEF, instructs the PCEF not to accumulate the usage of the Monitoring Key into the usage of the IP-CAN session level, thereby avoiding the wrong use of the free usage. Accumulated in the amount of IP-CAN session level. In addition, the technical solution of the present invention can also implement a separate usage monitoring of a specific service flow in an IP-CAN session to meet the requirements of independent usage monitoring.

BRIEF abstract

The drawings are intended to provide a further understanding of the invention, and are intended to be illustrative of the invention. In the drawing:

1 is a schematic diagram of a Rel-8 PCC non-roaming architecture in the prior art;

2 is a schematic flow chart of a method for monitoring usage according to an embodiment of the present invention;

3 is a schematic diagram showing the composition of a quantity monitoring system according to an embodiment of the present invention.

Preferred embodiment of the invention

In the embodiment of the present invention, when the PCRF sends the Monitoring Key, the PCEF indicates that the service data flow that needs to be independently monitored, such as the usage generated by the sponsored data connection service or the usage of other specified service data, is no longer accumulated to the IP-CAN session. Level of usage.

Based on the above idea, a usage monitoring method according to an embodiment of the present invention specifically uses the following technical solutions:

When the PCRF sends the Monitoring Key to the PCEF, the PCRF instructs the PCEF not to accumulate the usage of the Monitoring Key into the IP-CAN session level.

The Monitoring Key includes:

The specified one or a set of business data streams corresponding to the Monitoring Key, or the sponsored data link Connect the corresponding Monitoring Key

The PCRF sends an independent usage monitoring indication to the PCEF, indicating that the PCEF does not accumulate the usage of the Monitoring Key into the IP-CAN session level.

Wherein, for PCEF, TDF, any service or application, the independent usage monitoring indication may be an independent usage monitoring indicator or identification information.

In addition, for the PCEF, when the service is connected to the sponsored data, the independent usage monitoring indication may further include: the sponsored data connection indication.

In addition, the independent usage monitoring indication may further include: a sponsor identifier and an application service provider (ASP) identifier included in the policy and charging control rule formulated by the PCRF for the sponsored data connection service.

The independent usage monitoring indication may further include: a specific charging key included in the policy and charging control rule formulated by the PCRF for the sponsored data connection service.

The PCRF indicates that the PCEF does not accumulate the usage of the Monitoring Key into an IP-CAN session level by assigning a specific Monitoring Key to the service data stream or the sponsored data connection.

In order to facilitate the description of the present invention, the implementation of the technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

2 is a flow chart of a method for controlling usage according to an embodiment of the present invention. As shown in FIG. 2, the process is specifically described as follows:

Step S201: 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 the PDN network requesting access. PDN identifier;

Step S202, the PCEF sends an IP-CAN session establishment indication message to the PCRF, and carries the user identifier, the PDN identifier, and the IP address (IP Address) allocated for the UE in the IP-CAN session establishment indication message; Step S203: The PCRF determines that the subscription information of the user is not yet received according to the user identifier, and sends a subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.

Step S204: The SPR returns the user subscription information (ie, the contracted document response) to the PCRF according to the user identifier and the PDN identifier. The user subscription information includes the total allowed amount (TAU, Totally Allowed Usage) of the PDN (Per PDN and UE) of the user, that is, the total allowable amount of the IP-CAN session level;

Step S205: The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE. The usage monitoring strategy includes setting Monitoring Key 1 and setting the event trigger, which is the Usage_Report and the Usage Threshold (UT). The PCRF allocates the user's usage value UT1 and UT1 ≤ TAU1 according to the TAU1 obtained from the SPR;

Here, the usage monitoring is for all traffic data flows of the IP-CAN session, and the Monitoring Keyl is not included in any PCC rules (the PCRF indicates that the PCEF usage monitoring of the Monitoring Key is IP-CAN session level).

Step S206, the PCEF installation policy includes a usage monitoring policy. The gateway where the PCEF is located returns an IP-CAN session establishment response, and the IP-CAN session establishment response carries an IP Address;

After step S206, the UE may also establish another IP-CAN session with the PDN, at which time the Monitoring Keyl is for all service data flows of all IP-CAN sessions established by the UE and the PDN. That is, Monitoring Keyl is for PDN and UE combination (Per PDN and UE).

Step S207: The PCEF performs a usage monitoring policy to perform usage monitoring on all service data flows of the user accessing the PDN (through one or more IP-CAN sessions) (ie, performing IP-CAN session level usage monitoring). In this process, the PCEF may interact with the PCRF to report the consumed usage value and request a new usage threshold;

Step S208, the UE connects to the server of the third-party application service provider (ASP, Application Service Provider) through the IP-CAN session (including one or more IP-CAN sessions) established in step S201-step S207, and requests the service, ASP. The server decides to provide the sponsored data connection for the user. The ASP server provides dynamic sponsored data connection information to the AF, including the sponsor identification, the ASP identifier, the sponsored user information (such as IP Address), the IP flow information of the sponsored service, and the allowable usage threshold (AUT, Allowed Usage Threshold ) , where The AF is located in the PDN network where the UE establishes an IP-CAN session;

Step S209, the AF provides the sponsored data connection information to the PCRF, where the information includes the sponsor identifier, the ASP identifier, the sponsored user information (such as IP Address), the IP stream information of the sponsored service, and the AUT;

Step S210, after the PCRF saves the information, returning a confirmation message;

Step S211, the PCRF makes a policy decision based on the information obtained from the AF, the network policy, and the user subscription, and formulates the PCC policy;

The PCRF decides to monitor the usage of the sponsored data connection service and develop a usage monitoring strategy, including setting Monitoring Key2 and setting UT2, where UT2≤AUT. The PCRF includes the Monitoring Key2 in the PCC rule corresponding to the service data flow, and also includes an independent usage monitoring indication (in this embodiment, specifically the sponsored data connection indication) in the delivered usage monitoring policy, to indicate that the PCEF is for the Monitoring Key2. The corresponding consumption consumption needs to be deducted from the entire IP-CAN level.

In the actual application, the PCRF can first determine whether the IP-CAN session passed by the user accessing the sponsored data connection performs the IP-CAN session level usage monitoring. If yes, the PCRF carries the independent usage monitoring indication when the Monitoring Key 2 is sent. Otherwise, you do not need to carry an independent usage monitoring indicator.

Step S212: The PCRF sends a PCC rule to the PCEF, where the PCC rule includes a Monitoring Key2, and the PCRF also provides a usage threshold UT2 corresponding to the Monitoring Key2 and an independent usage monitoring indication.

Step S213, after the PCEF installs the policy, returning an acknowledgement message to the PCRF;

In step S214, the PCEF simultaneously performs the usage monitoring and service data flow level of the IP-CAN session level. Due to the receipt of the independent usage monitoring indication, the usage of the Monitoring Key2 is consumed, and the Monitoring Keyl will not be consumed by the accumulated usage;

The independent usage monitoring indication in the above embodiment can be implemented in multiple ways:

(1) An explicit independent usage monitoring indication, such as a separate indicator or identification information;

(2) corresponding to the sponsored data connection service, the independent usage monitoring indication may also be a sponsored data connection indication; (3) Since the PCC rules sent by the PCRF to the PCEF may include the sponsor identification and/or the ASP identifier for charging, it may be provided that the PCRF must include the sponsor identification and/or in the issued PCC rules. The ASP identifier, or a specific charging key, so that when the PCEF receives the PCC rule including the sponsor identifier and/or the ASP identifier, or a specific charging key, the Monitoring Key included in the PCC rule can be determined. Independent usage monitoring is required, and the usage monitoring of the IP-CAN session level no longer accumulates the consumption consumption corresponding to the Monitoring Key.

In addition, in other embodiments of the invention, the PCRF may also instruct the PCEF to perform independent dose monitoring as follows:

PCEF and PCRF pre-agreed one or a group of Monitoring Keys for independent usage monitoring. When the PCRF needs to monitor the sponsored data connection or the specific service flow, it assigns such a Monitoring Key to the sponsored data connection or specific service flow. When the PCEF is based on the specific Monitoring Key, it can be judged that the Monitoring Key requires independent usage monitoring.

Through the above process, when the PCEF receives a monitoring key related to one or a group of service data flows, and the monitoring key is instructed to require independent usage monitoring, the usage monitoring of the IP-CAN session level will no longer accumulate the usage amount corresponding to the Monitoring Key. Consumption, avoiding the use of the wrong amount of usage that should be used for free at the IP-CAN level.

Moreover, embodiments of the present invention are not only applicable to sponsored data connection scenarios. When the PCRF (according to the user subscription or network policy) determines that the usage monitoring of the IP-CAN session level does not accumulate the usage consumption of a certain one or a group of service data streams, the PCRF indicates that one or a group of service data flows need to be independent of the Monitoring Key. Dosage monitoring.

After the TDF function is introduced in the PCC architecture, the UE accesses the sponsored data connection through the IP-CAN session, or a service that does not need to accumulate TDF session level usage according to the user's subscription or network policy, and the execution and interaction process of the PCRF and the TDF It is similar. When the PCRF (according to the user subscription or network policy) determines that the usage monitoring of the TDF session level does not accumulate the usage consumption of a certain one or a group of service data streams or applications, the PCRF indicates that one or a group of service data streams or applications correspond to the Monitoring Key. Need independent monitoring In addition, in the usage monitoring system of the embodiment of the present invention, as shown in FIG. 3, the system mainly includes an independent monitoring indication unit in the PCRF, and the independent monitoring indication unit is configured to: when the Monitoring Key is issued to the PCEF, the indication is The PCEF does not accumulate the usage of the Monitoring Key into the usage of the IP-CAN session level.

The independent monitoring indication unit is corresponding to delivering the specified one or a group of service data flows.

When the Monitoring Key, or the monitoring key corresponding to the sponsored data connection, indicates that the PCEF does not accumulate the usage of the Monitoring Key into the IP-CAN session level.

The system also includes an independent monitoring execution unit in the PCEF.

The independent monitoring indication unit is further configured to: indicate that the PCEF does not use the monitoring key by sending an independent usage monitoring indication to the PCEF, or assigning a specific Monitoring Key to the service data flow or the sponsored data connection. The usage of the IP-CAN session level is integrated into the IP-CAN session level according to the independent usage monitoring indication or the specific monitoring key. Dosage

The independent usage monitoring indication delivered by the independent monitoring indication unit includes: a sponsored data connection indication, an independent usage monitoring indication bit or identification information; or, the PCRF formulas a policy for the sponsored data connection and The sponsor identification and/or ASP identification, or a specific charging key included in the charging control rule.

The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention. The present invention may be embodied in various other embodiments without departing from the spirit and scope of the invention. Various changes and modifications may be made to the invention, and such changes and modifications are intended to be included within the scope of the appended claims.

Obviously, those skilled in the art should understand that the above 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 executed by a computing device The program code is implemented so that they can be stored in the storage device by the computing device, and in some cases, the steps shown or described can be performed in a different order than here, or they can be separately produced. The individual integrated circuit modules are implemented, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

Industrial Applicability According to the technical solution of the present invention, when the PCRF sends a Monitoring Key to the PCEF, the PCRF instructs the PCEF not to accumulate the usage of the Monitoring Key into the usage of the IP-CAN session level, thereby avoiding free use. The usage is incorrectly accumulated in the usage of the IP-CAN session level. In addition, the technical solution of the present invention can also implement a separate usage monitoring of a specific service flow in an IP-CAN session to meet the requirements of independent usage monitoring. Therefore, the present invention has strong industrial applicability.

Claims

Claim

1. A method for monitoring usage, comprising:

The Policy and Charging Rules Function Entity (PCRF), when transmitting a Monitoring Key to the Policy Execution Function Entity, indicates that the Policy Execution Function Entity does not accumulate the usage of the Monitoring Key into the session level.

The usage monitoring method according to claim 1, wherein the monitoring key comprises: a specified one or a group of service data streams or a monitoring key corresponding to the application; or a monitoring key corresponding to the sponsored data connection.

The method for monitoring usage according to claim 2, wherein the step of the PCRF indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level comprises: performing, by the PCRF, the policy The function entity sends an independent usage monitoring indication, indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level.

The usage monitoring method according to claim 3, wherein the independent usage monitoring indication comprises: an independent usage monitoring indicator bit or identification information.

5. The usage monitoring method according to claim 3, wherein the independent usage monitoring indication comprises: a sponsored data connection indication.

The method for monitoring usage according to claim 1, wherein the step of the PCRF indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level comprises: the PCRF passing the service data The flow, the application, or the sponsored data connection allocates a specific Monitoring Key, indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into a session level;

7. The usage monitoring method according to claim 3, wherein the independent usage monitoring indication comprises:

The PCRF is a policy and charging control rule defined by the sponsored data connection service. Including the sponsor logo and the application service provider (ASP) logo; or include,

The usage monitoring method according to any one of claims 1 to 7, wherein the policy execution function entity is a policy and charging execution function PCEF, and correspondingly, the session level usage is

IP-CAN session level usage; or,

The usage monitoring method according to any one of claims 2 to 5, wherein: the specified one or a group of service data streams or applications are:

10. A usage monitoring system, the usage monitoring system comprising an independent monitoring indication unit in a Policy and Charging Rules Function Entity (PCRF),

The independent monitoring indication unit is configured to: send a monitoring key to the policy execution function entity

(Monitoring Key), indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the usage level of the session level.

11. The usage monitoring system of claim 10, wherein the Monitoring Key comprises:

The specified one or a group of business data streams or the corresponding Monitoring Key of the application; or the monitoring key corresponding to the sponsored data connection

12. The usage monitoring system of claim 11 further comprising an independent monitoring execution unit of the policy enforcement functional entity, wherein:

The independent monitoring indication unit is configured to instruct the policy execution function entity not to accumulate the usage of the Monitoring Key into the usage of the session level in the following manner: by issuing an independent usage monitoring indication to the policy execution function entity;

The independent monitoring execution unit is configured to: not according to the independent usage monitoring indication The amount corresponding to the Monitoring Key is accumulated into the session level.

13. The usage monitoring system of claim 12, wherein the independent usage monitoring indication comprises: an independent usage monitoring indicator or identification information.

14. The usage monitoring system of claim 12, wherein the independent usage monitoring indication comprises: a sponsored data connection indication.

15. The usage monitoring system of claim 12, wherein the independent usage monitoring indication comprises:

16. The usage monitoring system of claim 10, the usage monitoring system further comprising an independent monitoring execution unit in the policy enforcement functional entity, wherein:

The independent monitoring indication unit is configured to instruct the policy execution function entity not to accumulate the usage of the Monitoring Key into a usage level of the session level in the following manner: for the service data flow, the application, or the sponsored data The connection assigns a specific Monitoring Key, indicating that the policy execution function entity does not accumulate the usage of the Monitoring Key into the session level; the independent monitoring execution unit is configured to: according to the specific Monitoring Key, the The amount corresponding to the Monitoring Key is accumulated into the session level;

The usage monitoring system according to any one of claims 10-16, wherein the policy execution function entity is a policy and charging execution function PCEF, and correspondingly, the session level usage is an IP-CAN session level. Dosage

18. The usage monitoring system of any of claims 11-15, wherein: the specified one or a set of business data streams or applications are: Business data flows or applications that should not be aggregated into session-level usage based on user subscriptions or network policies.