WO2013013547A1 - 一种组用户用量监控方法及系统 - Google Patents

一种组用户用量监控方法及系统 Download PDF

Info

Publication number
WO2013013547A1
WO2013013547A1 PCT/CN2012/077406 CN2012077406W WO2013013547A1 WO 2013013547 A1 WO2013013547 A1 WO 2013013547A1 CN 2012077406 W CN2012077406 W CN 2012077406W WO 2013013547 A1 WO2013013547 A1 WO 2013013547A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
usage
control entity
policy control
policy
Prior art date
Application number
PCT/CN2012/077406
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
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013013547A1 publication Critical patent/WO2013013547A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • 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/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • 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
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • 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/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H04M15/7657—Linked or grouped accounts, e.g. of users or devices for closed subscriber group [CSG]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/60—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on actual use of network resources

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for monitoring group user usage. Background technique
  • the 3rd Generation Partnership Project (3GPP) defines a Policy and Charging Control (PCC) architecture for mobile networks. As shown in Figure 1, the functions of each entity in the PCC architecture are described as follows:
  • the Policy and Charging Rules Function (PCRF) is used to formulate resource control policies, including QoS (Quality of Service) control policies and charging control, for the service data flows included in the service. Strategy.
  • QoS Quality of Service
  • PCEF Policy and Charging Enforcement Function
  • PCC Policy and Charging Enforcement Function
  • the BBERF (Bearer Binding and Event Report Function) is used to detect IP packets transmitted on the network and map the IP packets to the corresponding bearer channel according to the 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 to request the PCRF to make a corresponding decision.
  • the SPR Subscribescription Profile Repository
  • the SPR Subscribescription Profile Repository
  • OCS Online Charging System
  • OFCS Offline Charging System
  • the PCC dynamically provides QoS guarantees during the transmission process for the service (composed of several service data streams) as follows:
  • Each service data stream included in the service corresponds to a specific PCC rule, which is determined by the PCC rule.
  • the PCRF needs to make decisions and formulate PCC rules for the service data flow according to the relevant information.
  • the relevant information on which the PCRF makes decisions and develops PCC rules includes the following information:
  • the service negotiation information received from the AF is information for conducting the service negotiated with the communication peer when the user conducts the service, for example, the requirement for the QoS of the service, and the communication parties use Information such as the IP address, port number, protocol used, etc.
  • the user subscription information received from the SPR for example, the user subscription information includes the QoS information signed by the user and the operator.
  • the service QoS requirement cannot exceed the QoS information that the user can use according to the user subscription information;
  • the operator-defined policy of the PCRF itself for example, the operator needs to distinguish between the roaming user and the non-roaming user.
  • the operator-defined differentiated control policy can be configured on the PCRF.
  • the access information received from the PCEF or the BBERF for example, when the user attaches to the network, 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;
  • the user's credit information is obtained from the OCS. For example, once the user's credit is exhausted or insufficient, the PCRF cannot authorize the user to conduct business.
  • the PCRF determines the PCC rules for the service data flow and sends the PCC rules to the PCEF. If there is a BBERF in the network, the PCRF needs to formulate the QoS rules and deliver them to the BBERF.
  • the PCEF 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 terminal and the network device can be based on 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 packets constituting the service data stream are matched to the corresponding PCC rules/QoS rules, and the service data stream can be obtained according to the binding relationship between the PCC rules/QoS rules and the bearer. Matching to the corresponding bearer to provide QoS guarantee for the transmission of the service data stream on the bearer network.
  • the corresponding PCC rule needs to be deleted from the bearer network, that is, the QoS resource allocated to the service is released.
  • the corresponding QoS resources can be allocated according to the QoS requirements of the service, and on the other hand, when the QoS resources are needed, the QoS resources can be allocated, and when the QoS resources are not needed, the QoS resources can be released in time. Therefore, the PCC mechanism can be upgraded. User service experience, improving the efficiency of network resource usage.
  • the operator hopes that the first 10M is free for users to use.
  • the fee is charged.
  • the operator wants the user to use the amount.
  • a bandwidth guarantee is used within 10M, and the user's bandwidth needs to be limited after the usage exceeds 10M.
  • the PCRF sends a control policy for the service to the PCEF, and also needs to deliver the usage monitoring indication, and the PCEF is required to perform the usage monitoring on the service, and the traffic of the service reaches the monitoring.
  • the PCEF will report the usage monitoring so that the PCRF can re-determine the policy and generate a new control strategy.
  • the implementation process of the usage monitoring of the related art is shown in FIG. 2, and the process mainly includes the step Al-A3.
  • Steps A1-A3 are processes in which the PCRF delivers the usage monitoring to the PCEF.
  • the service consists of one or more service data flows.
  • the policy control of the service implementation is actually a policy control for the service data flow.
  • the PCRF is used to formulate a control policy (PCC rule) for the service data flow and send it to the PCEF for execution.
  • PCC rule control policy
  • the usage monitoring information includes the monitoring key, the assigned monitoring threshold (threshold), and other information.
  • the process of performing the usage monitoring in the process includes the service data flow-1 and the service data flow-2, and the process of the PCRF sending the usage monitoring indication to the PCEF is as described in steps A1-A3.
  • the PCEF sends a CCR (Credit Control Request) to the PCRF.
  • step A2 the PCRF sends a CCA (Credit Control Answer) to the PCEF, including PCC rule-1 (indicated by charging rule definition-1), PCC rule-2 (indicated by charging rule definition-2), and usage monitoring. Information.
  • CCA Clear Control Answer
  • PCC rule -1 contains the PCC rule name (represented by charging rule name-1), and monitoring key;
  • PCC rule -2 contains the PCC rule name (represented by charging rule name-2), and monitoring key;
  • the usage monitoring information contains the above monitoring key and the monitoring threshold (threshold) assigned by the PCRF.
  • the PCRF may also include the usage monitoring information in the RAR (Re-Auth-Request) message sent to the PCEF.
  • RAR Re-Auth-Request
  • Step A3 The corresponding PCRF sends a RAR message to the PCEF, and the PCEF returns a RAA (Re-Auth-Answer) message to the PCRF.
  • RAA Re-Auth-Answer
  • Step B After receiving the PCC rule sent by the PCRF, the PCEF installs the rule and performs usage monitoring on the service data flow corresponding to the PCC rule (that is, the service data flow 1 and the service data flow 2) according to the usage monitoring information.
  • Steps C1-C2 are the process of reporting the usage monitoring by the PCEF.
  • step C1 when the accumulated amount of the monitoring of the monitoring key by the PCEF reaches the threshold value issued in the step A2, the PCEF performs the usage monitoring report.
  • the PCEF sends a CCR message to the PCRF, carrying the usage monitoring information, which includes the above monitoring key and the used Service Unit.
  • step C2 the PCRF returns the CCA to the PCEF.
  • Step D According to the reported usage, the PCRF re-defines the corresponding control strategy for the service data flow (ie, the service data stream -1 and the service data stream -2) that is monitored by the monitoring key.
  • Steps E1-E2 re-define the policy delivery process for the PCRF.
  • the PCRF sends a RAR message to the PCEF, and re-issues the control policy for the service data streams 1 and 2.
  • Step ⁇ 2 PCEF returns a response to PCRF.
  • the above process describes the usage monitoring of a single service. In addition, in actual operations, it also includes requirements for user usage monitoring. Since users can carry out a variety of services, the usage monitoring of users is actually monitoring the usage of multiple services.
  • the same network device needs to manage the user's subscription usage. Since the user selects a PCRF for the service when the user attaches, that is, the various services carried out by the user are controlled by the PCRF, and therefore, the PCRF manages the subscription amount of the user, and simultaneously allocates the same service for the user. With the monitoring key, it is possible to implement usage monitoring for multiple services performed by users.
  • the operator opens a family package and signs a certain amount of free usage, so that each family member can use the contracted free usage. Once the free usage is exceeded, the usage of the family member is charged.
  • Another example is the group user package. When a group of users experience a certain type of service, they can obtain a higher service experience in the contracted usage. When the contracted usage is exceeded, the experience of the service cannot be guaranteed.
  • group users For the above-mentioned home users or group users (collectively referred to as group users), although each member in the group user can share the contracted usage amount, but cannot guarantee that the users in the group can select the same PCRF when attaching to the network, therefore, the use of the current PCRF
  • the usage monitoring mechanism will not be able to implement usage monitoring for group users.
  • the users in the group may use different SPRs to save the subscription information. For example, the operator chooses to set the PCRF and the SPR in the actual operation, so that the SPR is not suitable for the unified management group users, and the usage monitoring is performed for the group users. . Therefore, for the existing usage monitoring and reporting mechanism, it is not possible to implement the usage monitoring for the group users who share the contracted usage. Summary of the invention
  • the purpose of the embodiments of the present invention is to provide a group user usage monitoring method and system, which realizes monitoring the usage of group users.
  • an embodiment of the present invention provides a method for monitoring a group user usage, including: The first policy control entity sends a usage monitoring request to the second policy control entity; when the second policy control entity receives the usage monitoring request, the second policy control entity performs the usage monitoring decision according to the user group subscription usage, and controls the first policy.
  • the entity sends the usage monitoring information;
  • the first policy control entity monitors the usage of the user according to the received usage monitoring information.
  • the step of the first policy control entity sending the usage monitoring request to the second policy control entity includes:
  • the first policy control entity discovers the second policy control entity by using a Diameter Routing Agent (DRA), and sends the usage monitoring request to the second policy control entity;
  • DRA Diameter Routing Agent
  • the second policy control entity is discovered by the DRA through the user group identifier of the user.
  • the step of the first policy control entity sending the usage monitoring request to the second policy control entity includes:
  • the first policy control entity sends the usage monitoring request to the second policy control entity when obtaining an indication for performing usage monitoring on the user.
  • the usage monitoring information that is sent by the second policy control entity to the first policy control entity includes a monitoring key and a monitoring threshold.
  • the step of monitoring the usage of the user by the first policy control entity according to the received usage monitoring information includes:
  • the first policy control entity sends a control policy and the usage monitoring information to the policy enforcement entity, where the control policy includes the monitoring key, and the usage monitoring information includes the monitoring key and the monitoring threshold ;
  • the policy enforcement entity performs usage monitoring
  • the policy enforcement entity reports the cumulative monitoring usage amount to the first policy control entity; the first policy control entity determines the control policy according to the received cumulative monitoring usage amount, and/or according to the cumulative monitoring usage amount Determining whether to send the usage monitoring request to the second policy control entity.
  • the step of the first policy control entity sending the usage monitoring request to the second policy control entity according to the cumulative monitoring usage decision includes:
  • the first policy control entity decides to send the usage monitoring request to the second policy control entity;
  • the first policy control entity decision does not send the usage monitoring request to the second policy control entity.
  • the embodiment of the present invention further provides a group user usage monitoring system, including: a first policy control entity, a second policy control entity, where: the first policy control entity is configured to: send to the second policy control entity The usage monitoring request; and according to the received usage monitoring information, the user is monitored for usage;
  • the second policy control entity is configured to: when receiving the usage monitoring request, perform the usage monitoring decision according to the user group subscription amount of the user, and deliver the usage monitoring information to the first policy control entity.
  • the first policy control entity is configured to: discover the second policy control entity by using a Diameter Routing Agent (DRA), and send the usage monitoring request to the second policy control entity;
  • DRA Diameter Routing Agent
  • the second policy control entity is discovered by the DRA through a user group identifier of the user.
  • the first policy control entity is configured to: when the indication for performing usage monitoring on the user is obtained, send the usage monitoring request to the second policy control entity.
  • the usage monitoring information includes a monitoring key and a monitoring threshold.
  • the system also includes a policy enforcement entity, wherein
  • the first policy control entity is configured to: after receiving the usage monitoring information, send a control policy and the usage monitoring information to the policy enforcement entity, where the monitoring policy includes the monitoring key, The usage monitoring information includes the monitoring key and the monitoring threshold; and, according to the received cumulative monitoring usage reported by the policy execution entity, the control strategy is determined, and/or, according to the cumulative monitoring usage decision Whether to send the usage monitoring request to the second policy control entity;
  • the policy execution entity is configured to: perform usage monitoring according to the received control policy and the usage monitoring information; and report the cumulative monitoring usage to the first policy control entity.
  • the first policy control entity is configured to: according to the cumulative monitoring usage decision, send the usage monitoring request to the second policy control entity in the following manner:
  • the determining sends the usage monitoring request to the second policy control entity
  • the embodiment of the present invention provides a usage monitoring mechanism for a group user.
  • a policy control entity attached to each member user in the user group requests usage monitoring from the dedicated policy control entity.
  • the usage monitoring of the group users sharing the contracted usage amount solves the shortage of the existing usage monitoring mechanism.
  • FIG. 1 is a schematic diagram of a related art 3GPP PCC R8 architecture
  • Embodiment 3 is a flowchart of group user usage monitoring according to Embodiment 1 of the present invention.
  • Figure 5 is a flow chart according to a third embodiment of the present invention.
  • Figure 7 is a flow chart in accordance with a fifth embodiment of the present invention.
  • an entity is controlled by introducing a dedicated policy (hereinafter referred to as a second policy).
  • a dedicated policy hereinafter referred to as a second policy.
  • Control entity to achieve usage monitoring for group users.
  • the dedicated policy control entity can be set separately or integrated in other policy control entities.
  • the dedicated policy control entity obtains group user subscription information from other network elements, or configures group user subscription information on the dedicated policy control entity.
  • the group user subscription information includes information such as a user group identifier, an identifier of a user in the group, and a user group subscription amount.
  • the embodiment of the invention provides a method for monitoring the usage of a group of users, and specifically adopts the following technical solutions.
  • Step 1 The first policy control entity sends a usage monitoring request to the second policy control entity. Specifically, the first policy control entity passes a DRA (Diameter Routing Agent,
  • the Diameter routing agent discovers the second policy control entity, wherein the second policy control entity is discovered by the DRA according to the user group identifier.
  • the first policy control entity may use an existing PCRF
  • the second policy control entity may be implemented by a PCRF that extends an existing function.
  • Step 2 The second policy control entity performs the usage monitoring decision according to the user group subscription amount, and delivers the usage monitoring information to the first policy control entity.
  • the usage monitoring information includes: a monitoring key and a monitoring threshold allocated by the second policy control entity to the user.
  • Step 3 The first policy control entity performs usage monitoring on the user according to the received usage monitoring information.
  • the step of monitoring the usage of the user further includes:
  • a control policy including the monitoring key
  • the usage monitoring information including the monitoring key and the monitoring threshold
  • a policy enforcement entity such as a PCEF
  • the policy enforcement entity reports the cumulative monitoring usage amount to the first policy control entity; the first policy control entity performs a policy decision according to the cumulative monitoring usage amount of the above “ ⁇ .
  • the first policy control entity is configured according to The cumulative monitoring usage decision Slightly (ie, PCC rule), and according to the cumulative monitoring usage report result, whether to send the usage monitoring request to the second policy control entity.
  • FIG. 3 is a schematic flowchart of a group user usage monitoring method according to an embodiment of the present invention. As shown in FIG. 3, the process in this embodiment mainly includes the following implementation steps.
  • Step 301 The first policy control entity sends a usage monitoring request to the second policy control entity. Specifically, when the first policy control entity obtains an indication that the user performs the usage monitoring, the usage of the usage monitoring request is sent to the second policy control entity.
  • the first policy control entity discovers the second policy control entity by using a DRA, where the second policy control entity is discovered by the DRA according to the user group identifier.
  • Step 302 The second policy control entity performs a usage monitoring decision according to the user group subscription amount, and allocates a monitoring key and a monitoring threshold to the user.
  • Step 303 The second policy control entity sends the monitoring key and the monitoring threshold to the first policy control entity.
  • Step 304 The first policy control entity sends usage monitoring information to the first policy enforcement entity, where the monitoring key and the monitoring threshold are included.
  • Step 305 The first policy enforcement entity performs usage monitoring.
  • Step 306 the first policy enforcement entity receives an indication of usage monitoring delivered by the first policy control entity.
  • Step 307 The first policy enforcement entity reports the cumulative monitoring usage amount to the first policy control entity.
  • Step 308 The first policy control entity performs a policy decision (ie, a PCC rule) according to the reported cumulative monitoring usage, and determines whether to send the usage monitoring request to the second policy control entity according to the cumulative monitoring usage report result. If yes, go to step 309.
  • Step 309 The first policy control entity sends the usage monitoring request to the second policy control entity.
  • the user group includes UE-1 and UE-2.
  • PCEF-1 and PCRF-1 ie, the first policy control entity
  • PCRF-2 the first policy control entity
  • the SPR-1 is used to store the subscription information of the UE-1, and includes an indication that the UE-1 needs to perform group user usage monitoring.
  • the SPR-2 is used to store the subscription information of the UE-2, and includes an indication that the UE-2 needs to perform group user usage monitoring.
  • PCRF-3 is a policy control entity (ie, the second policy control entity) that provides usage monitoring for group users. When the group user is attached to the network, the network device requests the monitoring of the usage of the PCRF-3 according to the usage monitoring indication, and the process of monitoring the usage of the PCRF-3 is shown in FIG. 4 . The process mainly includes the following steps.
  • the PCRF-3 obtains the group user subscription information, including the user group identifier, the identifier of all users in the group, and the user group subscription amount.
  • the group user subscription information may be pre-stored on the PCRF-3, or may be obtained by the PCRF-3 from other network elements that store the group user subscription information.
  • Step 402. UE-1 attaches to the network and selects PCEF-1.
  • the PCEF-1 sends an IP-CAN session establishment request to the PCRF-1 according to the selection of the PCRF-1 for the UE-1 access service, and carries the user identifier.
  • Step 403. The PCRF-1 determines that there is no subscription information of the UE-1 according to the user identifier, and obtains the subscription information of the UE-1 from the SPR-1, which includes an indication that the UE-1 is required to perform the usage monitoring.
  • the PCRF-1 includes an indication for monitoring the usage of the UE-1 according to the subscription information of the UE-1 obtained from the SPR-1, and the PCRF-1 discovers the PCRF-3 and the PCRF-1 according to the user group identifier by using the DRA. Sending a request for monitoring the usage of the UE-1 to the PCRF-3, including the UE-1 identifier, the user group identifier, and the like.
  • the user group identifier may be obtained from an IP-CAN session establishment request message sent by the PCEF-1, or obtained from the UE-1 subscription information of the SPR-1.
  • Step 405. After receiving the request, the PCRF-3 performs a usage monitoring decision according to the user group subscription usage information, and allocates a monitoring key for the UE-1, and targets the monitoring. Key allocation monitoring threshold (threshold).
  • Step 406 PCRF-3 delivers usage monitoring to PCRF-1, including the monitoring key and threshold assigned to UE-1. So far, a policy control session is established between PCRF-1 and PCRF-3.
  • Step 407. The PCRF-1 makes a policy decision for the IP-CAN session establishment request, and generates a control policy.
  • Step 408 The PCRF-1 returns a successful response to the IP-CAN session establishment to the PCEF-1, including the control policy and the monitoring key (threshold), and requires the UE-1 to implement the usage monitoring.
  • Step 409 PCEF-1 executes the policy and performs usage monitoring on UE-1 according to the requirements of PCRF-1.
  • Step 410 The process of attaching UE-2 to the network in the user group, refer to the attaching process of UE-1.
  • the PCRF-2 When the PCRF-2 is selected as the UE-2 access service, the PCRF-2 discovers the PCRF-3 according to the user group identity and establishes a policy control session according to the requirement that the UE-2 performs the usage monitoring according to the requirement received from the SPR-2. Request to monitor the usage of UE-2.
  • the PCRF-3 performs the usage monitoring decision based on the user group's subscription usage information, and generates usage monitoring information for the UE-2 and sends it to the PCRF-2.
  • the PCRF-2 is further sent to the PCEF-2 to initiate monitoring of the usage of the UE-2.
  • the foregoing embodiment 2 shows a process in which UE-1 and UE-2 in the user group are attached to the network.
  • the process of performing a service after the UE is attached to the network is given.
  • the PCEF monitors the UE usage, monitors the usage, and performs a policy adjustment based on the results of the PCRF based on the usage monitoring.
  • this embodiment only shows the process of implementing usage monitoring for UE-1.
  • the process of performing usage monitoring on UE-2 reference may be made to the process of implementing usage monitoring for UE-1.
  • the process of monitoring and reporting the usage of the embodiment and the policy adjustment according to the usage monitoring result is shown in FIG. 5, and the process mainly includes the following steps:
  • Step 501 UE-1 conducts service, and PCEF-1 performs usage monitoring on UE-1.
  • Step 502. PCEF-1 receives an indication from PCRF-1 requesting that the usage monitoring be reported.
  • Step 503. PCEF-1 returns a confirmation message to PCRF-1.
  • Step 504. PCEF-1 reports the cumulative monitoring usage (the cumulative monitoring usage may not reach the monitoring threshold) to PCRF-1.
  • Step 505. The PCRF-1 performs policy decision according to the reported cumulative monitoring usage, and performs policy adjustment for the UE-1, for example, limiting the bandwidth of the UE-1.
  • Step 506. PCRF-1 issues a new control strategy to PCEF-1.
  • Step 507. According to the control strategy issued by PCRF-1, PCEF-1 implements a new control strategy.
  • This embodiment is the same as the scenario described in the foregoing Embodiment 3, and is the process of performing the policy adjustment by the usage monitoring report and the monitoring result according to the usage.
  • the difference is that in the third embodiment, when the cumulative monitoring usage does not reach the threshold value, the PCEF-1 should report the process of monitoring the usage of the PCRF-1; however, in the embodiment, when the cumulative monitoring usage reaches the threshold, PCEF-1 actively reports the process of usage monitoring to PCRF-1.
  • the implementation process mainly includes the following steps:
  • Step 602. When the usage amount of the UE-1 reaches the monitoring threshold issued in the step 408 of the second embodiment, the PCEF-1 reports the usage monitoring to the PCRF-1, carrying the monitoring key and the cumulative monitoring usage.
  • Step 603. After receiving the reported usage monitoring, the PCRF-1 determines that the usage allocated to the UE-1 has been used up by the UE-1, and the PCRF-1 determines to send a usage monitoring request to the PCRF-3, and the request message carries a monitoring key. .
  • Step 604. The PCRF-3 receives the request message, and performs the usage monitoring decision according to the user group contract usage information. If the user group subscription amount is not allocated at this time, the monitoring key is assigned a new monitoring threshold value threshold-2; if the user group subscription amount has been completely allocated to the group user, the PCRF-3 can no longer be used. Assign a new monitoring threshold to the monitoring key.
  • Step 605a If the PCRF-3 allocates a new monitoring threshold to the UE-1, the PCRF-3 sends the monitoring key and the corresponding new monitoring threshold-2 to the PCRF-1.
  • Step 605b If the PCRF-3 does not allocate a new monitoring threshold for the UE-1, the PCRF-3 sends an indication to the PCRF-1 to stop the usage monitoring (the indication may be indicated by an explicit message, or may be sent by The message does not carry any usage monitoring related information to stop the usage monitoring Control).
  • Step 606 According to the result of the usage monitoring reported by PCEF-1 in step 602, PCRF-1 performs a policy decision to generate a new control strategy.
  • Step 607. PCRF-1 sends the monitoring information (monitoring key and threshold-2) received from PCRF-3 to PCEF-1 along with the new control policy.
  • PCEF-1 executes the control policy and continues to perform usage monitoring for UE-1.
  • Embodiments 2, 3 and 4 describe the process of monitoring the usage of the PCRF-3 during the process of establishing an IP-CAN session by the UE in the user group.
  • the process of the usage monitoring in the IP-CAN session modification process is described in this embodiment.
  • the monitoring of the usage of the services for the users in the group is started in the process of starting the service.
  • the present embodiment can also be implemented on the basis of the foregoing embodiments, that is, in the process of attaching the UE to the network, and in the process of conducting the service, the usage monitoring of the services performed by the users in the group is performed.
  • the specific process mainly includes the following steps:
  • Step 702. PCRF-1 receives a trigger for IP-CAN session modification.
  • the trigger may be from the AF, for example, receiving the service authorization request of the AF, the service authorization request will trigger the PCRF-1 to initiate the modification of the IP-CAN session; or receiving the IP-CAN session modification request from the PCEF-1, requesting to establish / Modify the IP-CAN bearer.
  • the PCRF-1 initiates a usage monitoring request to the PCRF-3 according to the indication that the UE-1 subscription information received from the SPR-1 includes the usage monitoring for the UE-1. If the policy control session has not been established by PCRF-1 and PCRF-3 at this time, PCRF-1 discovers PCRF-3 according to the user group identifier through DRA and establishes a policy control session. The PCRF-1 initiates a usage monitoring request to the PCRF-3, where the request message includes the user group identifier and the UE-1 identifier.
  • Step 704. After receiving the request message, the PCRF-3 performs the usage monitoring decision according to the user group subscription usage information, allocates a monitoring key to the UE-1, and allocates a corresponding monitoring threshold (threshold). Step 705.
  • PCRF-3 delivers usage monitoring to PCRF-1, including the above information.
  • the PCRF-1 performs a policy decision for the service carried out by the UE-1, generates a PCC rule, and includes the monitoring key in the PCC rule, and indicates that the service start usage monitoring is performed for the UE-1.
  • Step 707. PCRF-1 delivers control strategy and usage monitoring information to PCEF-1.
  • Step 708 PCEF-1 executes the policy and initiates usage monitoring of the service for UE-1.
  • Step 709 When the accumulated usage monitored by PCEF-1 reaches the monitoring threshold, PCEF-1 reports the usage monitoring to PCRF-1, carrying the monitoring key and the cumulative monitoring usage.
  • Step 710 After the PCRF-1 receives the usage monitoring report result, it is determined to be assigned to
  • the UE-1 performs the monitoring threshold of the service, and the PCRF-1 decides to request the PCRF-3 to continue the usage monitoring for the service carried out by the UE-1, and the request message carries the monitoring key.
  • Step 711 After receiving the request, the PCRF-3 performs a usage monitoring decision according to the subscription usage information of the user group, and allocates a new monitoring threshold value-2 to the monitoring key.
  • PCRF-3 sends a dose monitoring to PCRF-1, including monitoring key and threshold-2.
  • Step 713 The PCRF-1 performs policy decision on the service carried out by the UE-1 according to the usage monitoring result on the PCEF-1, for example, reduces the authorized bandwidth of the UE-1 to carry out the service, and determines to generate a new PCC rule.
  • the monitoring key is still included in the PCC rule.
  • Step 714 PCRF-1 issues a new policy to PCEF-1, including the PCC rules and usage monitoring information (monitoring key and threshold-2)
  • Step 715 The PCEF-1 performs a new policy delivered by the PCRF-1, and continues to monitor the service start usage for the UE-1.
  • the embodiment of the present invention further provides a group user usage monitoring system, where the system mainly includes: a first policy control entity, and a second policy control entity, where: The first policy control entity is configured to: send a usage monitoring request to the second policy control entity; and perform usage monitoring on the user according to the received usage monitoring information;
  • the second policy control entity is configured to: when receiving the usage monitoring request, perform the usage monitoring decision according to the user group subscription amount of the user, and deliver the usage monitoring information to the first policy control entity.
  • the first policy control entity is configured to: discover the second policy control entity by using a DRA, and send the usage monitoring request to the second policy control entity;
  • the second policy control entity is discovered by the DRA through the user group identifier of the user.
  • the first policy control entity is configured to: when the indication for performing usage monitoring for the user is obtained, send the usage monitoring request to the second policy control entity.
  • the usage monitoring information includes a monitoring key and a monitoring threshold.
  • the system also includes a policy enforcement entity, wherein
  • the first policy control entity is configured to: after receiving the usage monitoring information, deliver the control policy and the usage monitoring information to the policy enforcement entity, where the control policy includes the monitoring key, the usage The monitoring information includes the monitoring key and the monitoring threshold; and, according to the received cumulative monitoring usage reported by the policy execution entity, the control policy is determined, and/or, according to the cumulative monitoring usage decision,
  • the second policy control entity sends the usage monitoring request; the policy execution entity is configured to: perform usage monitoring according to the received control policy and the usage monitoring information; and report to the first policy control entity The cumulative monitoring amount.
  • the first policy control entity is configured to: according to the cumulative monitoring usage, decide whether to send the usage monitoring request to the second policy control entity:
  • the determining sends the usage monitoring request to the second policy control entity
  • 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.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • the embodiments of the present invention can implement the monitoring of the usage of the group users sharing the contracted usage, thereby solving the shortcomings of the existing usage monitoring mechanism.

Abstract

一种组用户用量监控方法及系统，所述方法包括：第一策略控制实体向第二策略控制实体发送用量监控请求；所述第二策略控制实体收到所述用量监控请求时，根据用户组签约用量进行用量监控决策，并向所述第一策略控制实体下发用量监控信息；所述第一策略控制实体根据收到的所述用量监控信息，对用户进行用量监控。采用该方法及系统，可以实现对共享签约用量的组用户的用量监控，从而解决了现有用量监控机制的不足。

Description

一种组用户用量监控方法及系统
技术领域
本发明涉及通信技术领域， 尤其涉及一种组用户用量监控方法及系统。 背景技术
第三代合作伙伴计划 （ 3rd Generation Partnership Project, 简称为 3GPP ) 定义了针对移动网络的策略和计费控制（Policy and Charging Control, 简称为 PCC ) 架构。 如图 1所示， PCC架构中各实体功能描述如下：
PCRF ( Policy and Charging Rules Function, 策略和计费规则功能）为业 务包含的业务数据流在传输过程中使用网络资源制定资源控制策略， 包括 QoS ( Quality of Service, 服务质量）控制策略和计费控制策略。
PCEF ( Policy and Charging Enforcement Function, 策略和计费执行功能 ) 用于执行 PCRF下发的或者 PCEF上预配置的 PCC规则， 对网络上传输的 IP ( Internet Protocol, 互联网协议）报文进行检测， 识别该 IP报文隶属的业务 数据流， 并对业务数据流提供 QoS控制和计费控制。
BBERF ( Bearer Binding and Event Report Function, 载绑定和事件上才艮 功能 )主要用于对网络上传输的 IP报文进行检测， 并将 IP报文按照规则映 射到对应的承载通道上。 BBERF还执行承载相关事件的上报， 例如当承载丟 失， 或者发生接入网络切换的时候， 都需要将相应的事件上报给 PCRF, 请求 PCRF进行相应的决策。
SPR ( Subscription Profile Repository, 用户签约数据库）用于保存用户签 约的业务信息， 为 PCRF制订 PCC规则提供必要的用户签约信息。
OCS ( Online Charging System,在线计费系统）和 OFCS ( Offline Charging System, 离线计费系统）分别用于离线和在线计费。
在用户开展业务过程中， PCC按照如下方式为业务（由若干业务数据流 组成）在传输过程中动态提供 QoS保证：
业务包含的每个业务数据流都对应一个具体的 PCC规则， PCC规则中定 义了该业务数据流传输时需要使用的 QoS资源。 在业务数据流在承载网络中 传输之前， PCRF需要依据相关信息为业务数据流决策并制定 PCC规则。 PCRF 决策并制定 PCC规则所依据的相关信息包括如下信息：
从 AF ( Application Function, 应用功能）接收的业务协商信息， 该业务 协商信息就是用户开展业务时和通信对端协商的开展所述业务的信息， 例如 开展所述业务对 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规则和承载的绑定关系，就可以将所述业务数据流 匹配到相应的承载上，从而为业务数据流在承载网络上的传输提供 QoS保证。 当用户开展的业务结束的时候， 相应的 PCC规则需要从承载网络上删除， 即 释放分配给所述业务使用的 QoS资源。
通过上述 PCC机制，一方面可以按照业务对 QoS的需求分配相应的 QoS 资源， 另一方面实现了需要 QoS资源时就可以分配， 不需要 QoS资源时可以 及时释放， 因此， 通过 PCC机制可以达到提升用户业务体验， 提高网络资源 使用效率的目的。
为了提高网络营运的灵活性， 比如， 对于某种业务， 运营商希望前 10M 是供用户免费使用的， 当用户的用量超出 10M之后， 就需要收取费用； 再比 如，运营商希望用户的用量在 10M之内使用一种带宽保证， 当用量超出 10M 之后需要对用户的带宽进行限制。 对于上述场景， 就要求用户开展业务时， PCRF向 PCEF下发针对业务的控制策略的同时， 还需要下发用量监控指示， 要求 PCEF对所述业务实施用量监控， 当所述业务的流量达到监控所要求的 阔值时， PCEF就要对用量监控实施上报， 以便 PCRF重新对所述业务进行策 略决策， 产生新的控制策略。
相关技术的用量监控的实现过程如图 2 所示， 该过程主要包括步骤 Al-A3。
步骤 A1-A3为 PCRF向 PCEF下发用量监控的过程。
业务由一个或者多个业务数据流构成， 对业务实施策略控制在实现时实 际上是针对业务数据流的策略控制， 通过 PCRF为业务数据流制定控制策略 ( PCC规则）并下发给 PCEF执行， 实现针对业务的策略控制。 如果需要对 该业务实施用量监控， 则在 PCRF向 PCEF下发的 PCC规则 （charging rule definition ) 中包含监控键 ( monitoring key ) , 同时 PCRF为该 monitoring key 分配一个用量监控信息（ usage monitoring information )并下发给 PCEF。 Usage monitoring information中包含所述 monitoring key、分配的监控阈值 ( threshold ) 以及其他信息。
例如流程中需要实施用量监控的业务包含了业务数据流 -1和业务数据流 -2, 则 PCRF向 PCEF下发用量监控指示的过程如步骤 A1-A3描述。 步骤 Al , PCEF向 PCRF发送 CCR ( Credit Control Request, 信用控制请 求） 。
步骤 A2, PCRF向 PCEF下发 CCA ( Credit Control Answer, 信用控制应 答）， 包含 PCC规则 -1 (用 charging rule definition-1表示）、 PCC规则 -2 (用 charging rule definition-2表示 ) 以及 usage monitoring information。
其中， PCC规则 -1中包含了 PCC规则名（用 charging rule name-1表示）， 和 monitoring key;
PCC规则 -2中包含了 PCC规则名 （用 charging rule name-2表示） ， 和 monitoring key;
Usage monitoring information中包含了上述 monitoring key, 以及 PCRF为 其分配的监控阔值（threshold ) 。
此外， PCRF也可在发送给 PCEF的 RAR ( Re-Auth-Request, 重鉴权请 求） 消息中包含上述用量监控信息。
步骤 A3 ,对应的 PCRF向 PCEF下发 RAR消息， 则 PCEF向 PCRF返回 RAA ( Re-Auth-Answer , 重鉴权应答） 消息。
步骤 B, 当 PCEF收到 PCRF下发的 PCC规则后， 安装规则， 并按照用 量监控信息， 对 PCC规则对应的业务数据流 (即业务数据流 1和业务数据流 2 ) 实施用量监控。
步骤 C1-C2为 PCEF上报用量监控的过程。
步骤 C1 , 当 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重新下发 控制策略。
步骤 Ε2, PCEF向 PCRF返回响应。
上述流程描述的是对单个业务的用量监控。 另外， 在实际运营中， 还包 括针对用户釆取用量监控的需求。 由于用户可以开展多种业务， 对用户的用 量监控实际上是针对多个业务进行用量监控。 在利用上述用量监控上^艮机制 实现对用户开展的多个业务实施用量监控时， 需要由同一网络设备管理用户 的签约用量。 由于用户附着时就选择了一个为其服务的 PCRF, 即用户开展的 各种业务都由该 PCRF提供策略控制， 因此， 由该 PCRF管理用户的签约用 量， 同时为用户开展的多个业务分配相同的 monitoring key, 就可以实现针对 用户开展的多个业务实施用量监控。
在实际运营中还存在一种需求， 就是需要针对一组用户实施用量监控。 例如， 运营商开通家庭套餐， 签约一定的免费用量， 使得每个家庭成员都可 以使用该签约免费用量， 一旦免费用量超出之后， 针对该家庭成员的用量都 要计费。 再如集团用户套餐， 对于集团内用户在体验某一类业务时在签约用 量内可以获得较高的业务体验， 当超出签约用量时， 就无法保证所述业务的 体验效果。 对于上述家庭用户或集团用户 （统称为组用户） ， 虽然组用户内 的每个成员可以共享签约用量， 但是不能保证组内用户附着到网络的时候都 能选择到同一个 PCRF, 因此，使用现有用量监控机制将无法实现对组用户实 施用量监控。 另外， 组内用户还有可能使用不同的 SPR保存签约信息， 例如 实际运营中运营商选择将 PCRF和 SPR合设，这样 SPR也不适合统一管理组 用户的签约用量， 并对组用户实施用量监控。 因此， 针对现有用量监控上报 机制， 尚无法实现对共享签约用量的组用户实施用量监控。 发明内容
本发明实施例的目的是提供一种组用户用量监控方法及系统， 实现对组 用户的用量监控。
为解决上述技术问题， 本发明实施例提供了一种组用户用量监控方法， 包括： 第一策略控制实体向第二策略控制实体发送用量监控请求； 所述第二策略控制实体收到所述用量监控请求时， 根据用户组签约用量 进行用量监控决策， 并向所述第一策略控制实体下发用量监控信息；
所述第一策略控制实体根据收到的所述用量监控信息， 对用户进行用量 监控。
其中， 第一策略控制实体向第二策略控制实体发送用量监控请求的步骤 包括：
所述第一策略控制实体通过 Diameter路由代理（DRA )发现所述第二策 略控制实体， 并向所述第二策略控制实体发送所述用量监控请求；
其中，所述第二策略控制实体是由所述 DRA通过所述用户的用户组标识 发现的。
其中， 第一策略控制实体向第二策略控制实体发送用量监控请求的步骤 包括：
所述第一策略控制实体在获取到针对所述用户进行用量监控的指示时， 向所述第二策略控制实体发送所述用量监控请求。
其中， 所述第二策略控制实体向所述第一策略控制实体下发的所述用量 监控信息， 包括监控键和监控阔值。
其中， 所述第一策略控制实体根据收到的所述用量监控信息， 对用户进 行用量监控的步骤包括：
所述第一策略控制实体向策略执行实体下发控制策略和所述用量监控信 息， 所述控制策略中包含所述监控键， 所述用量监控信息中包含所述监控键 和所述监控阔值；
所述策略执行实体执行用量监控；
所述策略执行实体向所述第一策略控制实体上报累计监控用量； 所述第一策略控制实体根据收到的所述累计监控用量决策所述控制策 略、 和 /或， 根据所述累计监控用量决策是否向所述第二策略控制实体发送所 述用量监控请求。 其中， 所述第一策略控制实体根据所述累计监控用量决策是否向所述第 二策略控制实体发送所述用量监控请求的步骤包括：
如果所述累计监控用量达到所述监控阔值， 则所述第一策略控制实体决 策向所述第二策略控制实体发送所述用量监控请求；
如果所述累计监控用量没有达到所述监控阔值， 则所述第一策略控制实 体决策不向所述第二策略控制实体发送所述用量监控请求。
本发明实施例还提供了一种组用户用量监控系统， 包括： 第一策略控制 实体， 第二策略控制实体， 其中： 所述第一策略控制实体设置成： 向所述第二策略控制实体发送用量监控 请求； 并根据收到的用量监控信息， 对用户进行用量监控；
所述第二策略控制实体设置成： 收到所述用量监控请求时， 根据所述用 户的用户组签约用量进行用量监控决策， 并向所述第一策略控制实体下发所 述用量监控信息。
其中， 所述第一策略控制实体是设置成： 通过 Diameter路由代理（ DRA ) 发现所述第二策略控制实体， 并向所述第二策略控制实体发送所述用量监控 请求；
其中，所述第二策略控制实体是由所述 DRA通过用户的用户组标识发现 的。
其中， 所述第一策略控制实体是设置成： 在获取到针对所述用户进行用 量监控的指示时， 向所述第二策略控制实体发送所述用量监控请求。
其中， 所述用量监控信息包括监控键和监控阔值。
所述系统还包括策略执行实体， 其中，
所述第一策略控制实体是设置成： 收到所述用量监控信息后， 向所述策 略执行实体下发控制策略和所述用量监控信息， 其中所述控制策略中包含所 述监控键， 所述用量监控信息中包含所述监控键和所述监控阔值； 以及， 根 据收到的所述策略执行实体上报的累计监控用量决策所述控制策略、 和 /或， 根据所述累计监控用量决策是否向所述第二策略控制实体发送所述用量监控 请求； 所述策略执行实体设置成： 根据收到的所述控制策略和所述用量监控信 息， 执行用量监控； 以及， 向所述第一策略控制实体上报所述累计监控用量。
其中， 所述第一策略控制实体是设置为以如下方式根据所述累计监控用 量决策是否向所述第二策略控制实体发送所述用量监控请求：
如果所述累计监控用量达到所述监控阔值， 则决策向所述第二策略控制 实体发送所述用量监控请求；
如果所述累计监控用量没有达到所述监控阔值， 则决策不向所述第二策 略控制实体发送所述用量监控请求。 本发明实施例提供了一种针对组用户的用量监控机制， 通过引入专用的 策略控制实体， 用户组内的每个成员用户附着的策略控制实体， 向该专用的 策略控制实体请求用量监控， 实现对共享签约用量的组用户的用量监控， 从 而解决了现有用量监控机制的不足。
附图概述
此处所说明的附图用作对本发明的进一步理解， 构成本申请的一部分， 本发明的示意性实施例及其说明用于解释本发明技术方案， 并不构成对本发 明技术方案的不当限定。 在附图中：
图 1为相关技术的 3GPP PCC R8架构的示意图；
图 2为根据相关技术的用量监控实现流程图；
图 3为根据本发明实施例一的组用户用量监控的流程图；
图 4为根据本发明实施例二的流程图；
图 5为根据本发明实施例三的流程图；
图 6为根据本发明实施例四的流程图；
图 7为根据本发明实施例五的流程图。
本发明的较佳实施方式
本发明实施例中， 通过引入一个专用策略控制实体（以下称作第二策略 控制实体） ， 实现针对组用户的用量监控。
所述的专用策略控制实体可以单独设置， 也可以集成在其他策略控制实 体中。
所述的专用策略控制实体从其他网元获取组用户签约信息， 或者在所述 专用策略控制实体上配置组用户签约信息。
所述的组用户签约信息包含了用户组标识、 组内用户的标识、 用户组签 约用量等信息。
本发明实施例提供了一种组用户用量监控方法，具体釆用如下技术方案。 步骤一， 第一策略控制实体向第二策略控制实体发送用量监控请求。 具体地， 所述第一策略控制实体通过 DRA ( Diameter Routing Agent,
Diameter路由代理）发现所述第二策略控制实体， 其中， 所述第二策略控制 实体是由所述 DRA根据用户组标识发现的。
其中，所述第一策略控制实体可釆用现有的 PCRF,所述第二策略控制实 体则可通过扩展了现有功能的 PCRF实现。
步骤二，所述第二策略控制实体根据用户组签约用量进行用量监控决策， 并下发用量监控信息给所述第一策略控制实体。
具体地， 所述用量监控信息， 包括： 所述第二策略控制实体为所述用户 分配的监控键 ( monitoring key )和监控阔值（threshold ) 。
步骤三， 所述第一策略控制实体根据收到的所述用量监控信息， 对用户 进行用量监控。
所述对用户进行用量监控的步骤进一步包括：
所述第一策略控制实体向策略执行实体 (如 PCEF )下发控制策略 (包含 所述监控键）和所述用量监控信息 （包含所述监控键和所述监控阔值） ； 所述策略执行实体执行用量监控；
所述策略执行实体向所述第一策略控制实体上报累计监控用量； 所述第一策略控制实体根据上 "^的所述累计监控用量进行策略决策。 具体地， 所述第一策略控制实体根据所述累计监控用量决策所述控制策 略（即 PCC规则 ) , 并根据所述累计监控用量上报结果决策是否向所述第二 策略控制实体发送所述用量监控请求。
下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
实施例一
图 3示出了本发明实施例的组用户用量监控方法的流程示意图， 如图 3 所示， 本实施例流程主要包括如下实施步骤。
步骤 301 , 第一策略控制实体向第二策略控制实体发送用量监控请求。 具体地，当所述第一策略控制实体获取到为用户进行用量监控的指示时， 则向所述第二策略控制实体发送用量监控请求。
所述第一策略控制实体通过 DRA发现所述第二策略控制实体，其中， 所 述第二策略控制实体是由所述 DRA根据用户组标识发现的。
步骤 302, 所述第二策略控制实体根据用户组签约用量进行用量监控决 策， 为所述用户分配监控键 ( monitoring key )和监控阔值（threshold ) 。
步骤 303 , 所述第二策略控制实体将所述监控键和监控阔值下发给所述 第一策略控制实体。
步骤 304, 所述第一策略控制实体向第一策略执行实体下发用量监控信 息， 包含所述监控键和所述监控阔值。
步骤 305, 所述第一策略执行实体执行用量监控。
步骤 306 (可选） ， 所述第一策略执行实体收到所述第一策略控制实体 下发的用量监控上 指示。
步骤 307 , 所述第一策略执行实体向所述第一策略控制实体上报累计监 控用量。
步骤 308, 所述第一策略控制实体根据上报的所述累计监控用量进行策 略决策 (即 PCC规则 )， 并根据所述累计监控用量上报结果决策是否向第二 策略控制实体发送所述用量监控请求， 如果是， 则执行步骤 309。 步骤 309, 所述第一策略控制实体向所述第二策略控制实体发送所述用 量监控请求。
实施例二
本实施例假设用户组包含了 UE-1和 UE-2。 根据现有 UE附着的流程， 当 UE-1附着到网络时， 选择 PCEF-1和 PCRF-1 (即第一策略控制实体）为 其接入服务； 当 UE-2附着到网络时， 选择 PCEF-2和 PCRF-2为其接入服务。
SPR-1用于保存 UE-1的签约信息， 其中包含了 UE-1需要执行组用户用量监 控的指示。 SPR-2用于保存 UE-2的签约信息， 其中包含了 UE-2需要执行组 用户用量监控的指示。 PCRF-3是专门为组用户提供用量监控的策略控制实体 (即第二策略控制实体） 。 当组用户附着到网络， 网络设备根据用量监控指 示向 PCRF-3请求用量监控， 以及 PCRF-3下发用量监控的过程如图 4所示。 该流程主要包括如下步骤。
步骤 401. PCRF-3获取组用户签约信息， 包括用户组标识、 组内所有用 户的标识、 用户组签约用量。 所述组用户签约信息可以预保存在 PCRF-3上， 也可以由 PCRF-3从保存所述组用户签约信息的其他网元获取。
步骤 402. UE-1附着到网络， 选择 PCEF-1。 PCEF-1根据选择 PCRF-1为 UE-1接入服务， 向 PCRF-1发送 IP-CAN会话建立请求， 携带用户标识。
步骤 403. PCRF-1根据用户标识判断还没有 UE-1的签约信息， 从 SPR-1 中获取 UE-1的签约信息， 其中包含要求为 UE-1进行用量监控的指示。
步骤 404.PCRF-1根据从 SPR-1获取的 UE-1的签约信息中包含为 UE-1 进行用量监控的指示， PCRF-1通过 DRA根据用户组标识发现所述 PCRF-3 , PCRF-1向 PCRF-3发送对 UE-1进行用量监控的请求， 包含 UE-1标识、 用户 组标识等信息。
其中，所述用户组标识可以从 PCEF-1发送的 IP-CAN会话建立请求消息 中获取， 或者从 SPR-1的 UE-1签约信息中获取。
步骤 405. PCRF-3接收所述请求后， 根据用户组签约用量信息进行用量 监控决策，为 UE-1分配用量监控键（ monitoring key ) ,并针对所述 monitoring key分配监控阔值 ( threshold ) 。
步骤 406. PCRF-3 向 PCRF-1 下发用量监控， 包含分配给 UE-1 的 monitoring key和 threshold。至此， PCRF-1与 PCRF-3之间建立策略控制会话。
步骤 407. PCRF-1针对所述 IP-CAN会话建立请求进行策略决策，产生控 制策略。
步骤 408. PCRF-1向 PCEF-1返回 IP-CAN会话建立成功的响应， 包含所 述控制策略， 以及用量监控信息 （monitoring key, threshold ) , 要求对 UE-1 实施用量监控。
步骤 409. PCEF-1执行策略， 并根据 PCRF-1的要求， 对 UE-1执行用量 监控。
步骤 410. 用户组下的 UE-2附着到网络的过程， 参考 UE-1的附着过程。 当选择 PCRF-2为 UE-2接入服务时， PCRF-2根据从 SPR-2接收的要求为 UE-2 执行用量监控的指示之后， 根据用户组标识发现 PCRF-3 并建立策略控制会 话， 请求为 UE-2进行用量监控。 PCRF-3根据用户组签约用量信息进行用量 监控决策，为 UE-2产生用量监控信息并下发给 PCRF-2。 PCRF-2进一步下发 给 PCEF-2 , 启动针对 UE-2的用量监控。
实施例三
上述实施例二给出了用户组内的 UE-1和 UE-2附着到网络的过程。 本实 施例中给出了 UE附着到网络之后， 开展业务的过程。 PCEF对 UE进行用量 监控， 并进行用量监控上 以及 PCRF根据用量监控上 >¾结果实施策略调 整的过程。 为简便起见， 本实施例仅给出了对 UE-1实施用量监控的过程。 对 UE-2实施用量监控的过程， 则可参考针对 UE-1实施用量监控的过程。 本实 施例的用量监控上报以及根据用量监控结果进行策略调整的过程如图 5 所 示， 该流程主要包括如下步骤：
步骤 501. UE-1开展业务， PCEF-1对 UE-1实施用量监控。
步骤 502. PCEF-1从 PCRF-1中收到要求上报用量监控的指示。
步骤 503. PCEF-1向 PCRF-1返回确认消息。 步骤 504. PCEF-1将累计监控用量（该累计监控用量可能没有到达监控 阔值 threshold )上报给 PCRF-1。
步骤 505. PCRF-1根据上报的累计监控用量进行策略决策，为 UE-1进行 策略调整， 例如限制 UE-1的带宽等。
步骤 506. PCRF-1将新的控制策略下发给 PCEF-1。
步骤 507. 根据 PCRF-1下发的控制策略， PCEF-1执行新的控制策略。
实施例四
本实施例和前述实施例三描述的场景相同， 同为用量监控上报和根据用 量监控上报结果进行策略调整的过程。 区别在于实施例三中描述的是累计监 控用量没有达到阔值时， PCEF-1应 PCRF-1的要求上报用量监控的过程； 而 本实施例中描述的是当累计监控用量到达阔值时， PCEF-1向 PCRF-1主动上 报用量监控的过程。 如图 6所示， 该实现流程主要包括如下步骤：
步骤 601. UE-1开展业务， PCEF-1对 UE-1实施用量监控。
步骤 602. 当 UE-1使用的用量达到实施例二中步骤 408下发的监控阔值 时， PCEF-1向 PCRF-1上报用量监控， 携带 monitoring key和累计监控用量。
步骤 603. PCRF-1收到上报的用量监控后，判断分配给 UE-1使用的用量 已经被 UE-1用完， PCRF-1决策向 PCRF-3发送用量监控请求， 请求消息中 携带 monitoring key。
步骤 604. PCRF-3收到请求消息， 根据用户组签约用量信息进行用量监 控决策。 如果此时所述用户组签约用量没有分配完， 则为该 monitoring key分 配新的监控阔值 threshold-2; 如果所述用户组签约用量已经完全分配给了组 内用户， 则 PCRF-3无法再为所述 monitoring key分配新的监控阔值。
步骤 605a. 如果 PCRF-3为 UE-1分配了新的监控阔值， 则 PCRF-3将 monitoring key和对应的新的监控阔值 threshold-2下发给 PCRF-1。
步骤 605b. 如果 PCRF-3没有为 UE-1分配新的监控阔值， 则 PCRF-3向 PCRF-1下发停止用量监控的指示（该指示可以通过一个明确的信息表示， 也 可以通过在下发的消息中不携带任何用量监控相关的信息表示停止用量监 控） 。
步骤 606.根据步骤 602 PCEF-1上报的用量监控的结果， PCRF-1执行策 略决策， 产生新的控制策略。
步骤 607. PCRF-1将从 PCRF-3接收的用量监控信息 （ monitoring key和 threshold-2 )连同新的控制策略下发给 PCEF-1。
步骤 608. PCEF-1执行控制策略， 并对 UE-1继续执行用量监控。
实施例五
前述实施例二、 三和四描述的是在用户组内的 UE 附着到网络， 建立 IP-CAN会话的过程中 PCRF-3下发用量监控的过程。 而本实施例中描述的是 在 IP-CAN会话修改过程中下发用量监控的过程， 即 UE附着到网络之后，在 开展业务的过程中， 才启动针对组内用户开展业务的用量监控。 当然， 本实 施例也可在前述实施例的基础上进行实施， 即， 在 UE附着到网络的过程， 以及， 在开展业务的过程中， 均进行针对组内用户开展业务的用量监控。 如 图 7所示， 具体流程主要包括如下步骤：
步骤 701. UE-1开展业务， 和 AF之间完成业务协商过程。
步骤 702. PCRF-1收到 IP-CAN会话修改的触发。其触发可以来自于 AF, 例如收到 AF的业务授权请求， 该业务授权请求将触发 PCRF-1发起 IP-CAN 会话的修改； 或者收到来自 PCEF-1的 IP-CAN会话修改请求， 请求建立 /修 改 IP-CAN承载。
步骤 703.根据从 SPR-1接收的 UE-1的签约信息中包含为 UE-1进行用量 监控的指示， PCRF-1 向 PCRF-3 发起用量监控请求。 如果此时 PCRF-1 和 PCRF-3还没有建立策略控制会话， 则 PCRF-1通过 DRA根据用户组标识发 现 PCRF-3 , 并建立策略控制会话。 PCRF-1向 PCRF-3发起用量监控请求， 请求消息中包含用户组标识、 UE- 1标识。
步骤 704. 当 PCRF-3收到请求消息之后， 根据用户组签约用量信息进行 用量监控决策， 为 UE-1分配监控键（monitoring key ) , 并分配相应的监控阔 值 ( threshold ) 。 步骤 705. PCRF-3向 PCRF-1下发用量监控， 包含上述信息。 步骤 706. PCRF-1为 UE-1开展的所述业务进行策略决策， 产生 PCC规 则， 并在 PCC规则中包含所述 monitoring key, 表示针对 UE-1开展的所述业 务启动用量监控。
步骤 707. PCRF-1向 PCEF-1下发控制策略和用量监控信息。
步骤 708. PCEF-1执行策略， 并启动针对 UE-1开展的所述业务的用量监 控。
步骤 709. 当 PCEF-1监控的累计用量达到所述监控阔值的时候， PCEF-1 向 PCRF-1上报用量监控， 携带 monitoring key和累计监控用量。
步骤 710. 当 PCRF-1 接收到所述用量监控上报结果之后， 判断分配给
UE-1开展所述业务的监控阔值已经到达， PCRF-1 决定向 PCRF-3请求针对 UE-1 开展的所述业务继续进行用量监控， 请求消息中携带所述 monitoring key。
步骤 711. PCRF-3接收到所述请求之后， 根据用户组的签约用量信息进 行用量监控决策， 为所述 monitoring key分配新的监控阔值 threshold-2。
步骤 712. PCRF-3 向 PCRF-1 下发用量监控， 包含 monitoring key和 threshold-2。
步骤 713. PCRF-1对 UE-1开展的所述业务， 根据 PCEF-1上 4艮的用量监 控结果进行策略决策，例如降低 UE-1开展所述业务的授权带宽， 决策产生新 的 PCC规则， 所述 PCC规则中仍然包含所述 monitoring key。
步骤 714. PCRF-1向 PCEF-1下发新的策略， 包含所述 PCC规则和用量 监控信息 ( monitoring key和 threshold-2 )
步骤 715. PCEF-1执行 PCRF-1下发的新的策略， 并继续针对 UE-1开展 的所述业务启动用量监控。
此外， 本发明实施例还提供了一种组用户用量监控系统， 该系统主要包 括： 第一策略控制实体， 第二策略控制实体， 其中： 所述第一策略控制实体设置成： 向所述第二策略控制实体发送用量监控 请求； 并根据收到的用量监控信息， 对用户进行用量监控；
所述第二策略控制实体设置成： 收到用量监控请求时， 根据用户的用户 组签约用量进行用量监控决策， 并向所述第一策略控制实体下发所述用量监 控信息。
所述第一策略控制实体是设置成： 通过 DRA发现所述第二策略控制实 体， 并向所述第二策略控制实体发送所述用量监控请求；
其中，所述第二策略控制实体是由所述 DRA通过所述用户的用户组标识 发现的。
所述第一策略控制实体是设置成： 在获取到针对用户进行用量监控的指 示时， 向所述第二策略控制实体发送所述用量监控请求。
所述用量监控信息包括监控键和监控阔值。
所述系统还包括策略执行实体， 其中，
所述第一策略控制实体是设置成： 收到所述用量监控信息后， 向策略执 行实体下发控制策略和所述用量监控信息， 其中所述控制策略中包含所述监 控键， 所述用量监控信息中包含所述监控键和所述监控阔值； 以及， 根据收 到的所述策略执行实体上报的累计监控用量决策所述控制策略、 和 /或， 根据 所述累计监控用量决策是否向第二策略控制实体发送所述用量监控请求； 所述策略执行实体设置成： 根据收到的所述控制策略和所述用量监控信 息， 执行用量监控； 以及， 向所述第一策略控制实体上报所述累计监控用量。
所述第一策略控制实体是设置为以如下方式根据所述累计监控用量决策 是否向所述第二策略控制实体发送所述用量监控请求：
如果所述累计监控用量达到所述监控阔值， 则决策向所述第二策略控制 实体发送所述用量监控请求；
如果所述累计监控用量没有达到所述监控阈值， 则决策不向所述第二策 略控制实体发送所述用量监控请求。 以上仅为本发明的优选实施案例而已，并不用于限制本发明的保护范围 , 本发明技术方案还可有其他多种实施例， 在不背离本发明精神及其实质的情 形， 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明实施例不限制于任何特定的硬件 和软件结合。
工业实用性 本发明实施例可实现对共享签约用量的组用户的用量监控， 从而解决了 现有用量监控机制的不足。

Claims

权 利 要 求 书
1、 一种组用户用量监控方法， 包括，
第一策略控制实体向第二策略控制实体发送用量监控请求；
所述第二策略控制实体收到所述用量监控请求时， 根据用户组签约用量 进行用量监控决策， 并向所述第一策略控制实体下发用量监控信息；
所述第一策略控制实体根据收到的所述用量监控信息， 对用户进行用量 监控。
2、 如权利要求 1所述的方法， 其中， 第一策略控制实体向第二策略控制 实体发送用量监控请求的步骤包括：
所述第一策略控制实体通过 Diameter路由代理（ DRA )发现所述第二策 略控制实体， 并向所述第二策略控制实体发送所述用量监控请求；
其中，所述第二策略控制实体是由所述 DRA通过所述用户的用户组标识 发现的。
3、 如权利要求 1所述的方法， 其中， 第一策略控制实体向第二策略控制 实体发送用量监控请求的步骤包括：
所述第一策略控制实体在获取到针对所述用户进行用量监控的指示时， 向所述第二策略控制实体发送所述用量监控请求。
4、 如权利要求 1、 2或 3所述的方法， 其中，
所述第二策略控制实体向所述第一策略控制实体下发的所述用量监控信 息， 包括监控键和监控阔值。
5、 如权利要求 4所述的方法， 其中， 所述第一策略控制实体根据收到的 所述用量监控信息， 对用户进行用量监控的步骤包括：
所述第一策略控制实体向策略执行实体下发控制策略和所述用量监控信 息， 所述控制策略中包含所述监控键， 所述用量监控信息中包含所述监控键 和所述监控阔值；
所述策略执行实体执行用量监控；
所述策略执行实体向所述第一策略控制实体上报累计监控用量； 所述第一策略控制实体根据收到的所述累计监控用量决策所述控制策 略、 和 /或， 根据所述累计监控用量决策是否向所述第二策略控制实体发送所 述用量监控请求。
6、 如权利要求 5所述的方法， 其中， 所述第一策略控制实体根据所述累 计监控用量决策是否向所述第二策略控制实体发送所述用量监控请求的步骤 包括：
如果所述累计监控用量达到所述监控阔值， 则所述第一策略控制实体决 策向所述第二策略控制实体发送所述用量监控请求；
如果所述累计监控用量没有达到所述监控阔值， 则所述第一策略控制实 体决策不向所述第二策略控制实体发送所述用量监控请求。
7、 一种组用户用量监控系统， 包括： 第一策略控制实体， 第二策略控制 实体， 其中：
所述第一策略控制实体设置成： 向所述第二策略控制实体发送用量监控 请求； 并根据收到的用量监控信息， 对用户进行用量监控；
所述第二策略控制实体设置成： 收到所述用量监控请求时， 根据所述用 户的用户组签约用量进行用量监控决策， 并向所述第一策略控制实体下发所 述用量监控信息。
8、 如权利要求 7所述的系统， 其中，
所述第一策略控制实体是设置成： 通过 Diameter路由代理（DRA )发现 所述第二策略控制实体，并向所述第二策略控制实体发送所述用量监控请求； 其中，所述第二策略控制实体是由所述 DRA通过所述用户的用户组标识 发现的。
9、 如权利要求 7或 8所述的系统， 其中，
所述第一策略控制实体是设置成： 在获取到针对所述用户进行用量监控 的指示时， 向所述第二策略控制实体发送所述用量监控请求。
10、 如权利要求 7或 8所述的系统， 其中，
所述用量监控信息包括监控键和监控阔值。
11、 如权利要求 10所述的系统， 还包括策略执行实体， 其中，
所述第一策略控制实体是设置成： 收到所述用量监控信息后， 向所述策 略执行实体下发控制策略和所述用量监控信息， 其中所述控制策略中包含所 述监控键， 所述用量监控信息中包含所述监控键和所述监控阔值； 以及， 根 据收到的所述策略执行实体上报的累计监控用量决策所述控制策略、 和 /或， 根据所述累计监控用量决策是否向所述第二策略控制实体发送所述用量监控 请求；
所述策略执行实体设置成： 根据收到的所述控制策略和所述用量监控信 息， 执行用量监控； 以及， 向所述第一策略控制实体上报所述累计监控用量。
12、 如权利要求 11所述的系统， 其中，
所述第一策略控制实体是设置为以如下方式根据所述累计监控用量决策 是否向所述第二策略控制实体发送所述用量监控请求：
如果所述累计监控用量达到所述监控阔值， 则决策向所述第二策略控制 实体发送所述用量监控请求；
如果所述累计监控用量没有达到所述监控阔值， 则决策不向所述第二策 略控制实体发送所述用量监控请求。
PCT/CN2012/077406 2011-07-28 2012-06-25 一种组用户用量监控方法及系统 WO2013013547A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110213553.1A CN102904740B (zh) 2011-07-28 2011-07-28 一种组用户用量监控方法及系统
CN201110213553.1 2011-07-28

Publications (1)

Publication Number Publication Date
WO2013013547A1 true WO2013013547A1 (zh) 2013-01-31

Family

ID=47576791

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/077406 WO2013013547A1 (zh) 2011-07-28 2012-06-25 一种组用户用量监控方法及系统

Country Status (2)

Country Link
CN (1) CN102904740B (zh)
WO (1) WO2013013547A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104244211A (zh) * 2013-06-07 2014-12-24 阿尔卡特朗讯 一种用于确定pcrf的方法与设备
CN104469726A (zh) * 2013-09-22 2015-03-25 阿尔卡特朗讯 一种用于对用户组进行使用监控的方法与设备
CN105813046A (zh) * 2014-12-30 2016-07-27 华为技术有限公司 一种带宽控制的方法、装置及系统
GB2553194B (en) * 2015-12-31 2021-03-03 Pismo Labs Technology Ltd Methods and systems for sharing data usage at a plurality of network devices
CN108512770B (zh) * 2017-02-28 2020-10-23 华为技术有限公司 数据流量分配方法及相关设备
CN109428781B (zh) 2017-08-30 2021-11-05 中兴通讯股份有限公司 会话用量监测控制方法、服务器及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065401A (zh) * 2009-11-17 2011-05-18 中国移动通信集团辽宁有限公司 一种多业务间计费处理方法、装置和系统
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102075908A (zh) * 2009-11-19 2011-05-25 中兴通讯股份有限公司 一种资源接纳控制系统间的用量监测方法及系统
CN102083035A (zh) * 2009-11-30 2011-06-01 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132307B (zh) * 2006-08-22 2010-12-01 华为技术有限公司 控制系统、控制方法、以及控制装置
CN101325780B (zh) * 2007-06-15 2010-07-07 华为技术有限公司 策略控制实现方法和系统、及策略和计费执行实体
WO2009049684A1 (en) * 2007-10-19 2009-04-23 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for notifying an application function of resource restrictions relating to a communication session

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102065401A (zh) * 2009-11-17 2011-05-18 中国移动通信集团辽宁有限公司 一种多业务间计费处理方法、装置和系统
CN102075908A (zh) * 2009-11-19 2011-05-25 中兴通讯股份有限公司 一种资源接纳控制系统间的用量监测方法及系统
CN102075900A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统
CN102083035A (zh) * 2009-11-30 2011-06-01 中兴通讯股份有限公司 一种实现用量监测控制的方法及系统

Also Published As

Publication number Publication date
CN102904740B (zh) 2017-11-07
CN102904740A (zh) 2013-01-30

Similar Documents

Publication Publication Date Title
US8640188B2 (en) Methods, systems, and computer readable media for providing group policy configuration in a communications network using a fake user
WO2013007142A1 (zh) 一种用量监控方法及系统
EP2296309B1 (en) A method for delivering policy rules to an end user, according on his/her account balance and service subscription level, in a telecommunication network
JP5044063B1 (ja) 関連ユーザに対する総使用割当量を考慮した関連セッションに対するポリシー実行方法、装置及びコンピュータプログラム
RU2513711C2 (ru) Триггер события услуги
EP2521305B1 (en) Method, device and system for controlling user session policy
WO2011097911A1 (zh) 策略和计费规则功能实体的选择方法、装置及系统
JP6468502B2 (ja) 課金セッション管理方法および装置
US20100186064A1 (en) Method and device for obtaining capabilities of policy and charging enforcement function
JP2012507223A (ja) ポリシー及び課金制御方法、サーバ、及びコンピュータプログラム
US20110320544A1 (en) Diameter session audits
WO2013013547A1 (zh) 一种组用户用量监控方法及系统
WO2009024050A1 (fr) Procédé, système et dispositif de commande de politique
WO2010069170A1 (zh) 一种实现策略和计费控制的方法
WO2012175123A1 (en) Method for policy control and method for bearer control as well as corresponding servers, systems and computer programs
WO2010091635A1 (zh) 一种策略的控制方法、装置
WO2011063722A1 (zh) 一种实现用量监测控制的方法及系统
EP2997695A1 (en) Advanced policy and charging control methods, network nodes and computer programs for sponsored data connectivity by peers
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2015055063A1 (zh) 应用接入控制方法及应用功能实体装置
WO2011120222A1 (zh) 优先级业务激活、去激活方法、装置和系统
WO2014101239A1 (zh) 策略和计费控制方法及设备
US9485105B2 (en) Method and telecommunications network utilizing more than one online charging system for a given user
WO2011088702A1 (zh) 在全业务融合网络中控制资源的方法和系统
WO2009026812A1 (fr) Procédé, dispositif et système d'application d'une politique de contrôle

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

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

Country of ref document: EP

Kind code of ref document: A1