WO2016062010A1 - 用量监控方法及装置 - Google Patents

用量监控方法及装置 Download PDF

Info

Publication number
WO2016062010A1
WO2016062010A1 PCT/CN2015/075308 CN2015075308W WO2016062010A1 WO 2016062010 A1 WO2016062010 A1 WO 2016062010A1 CN 2015075308 W CN2015075308 W CN 2015075308W WO 2016062010 A1 WO2016062010 A1 WO 2016062010A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
usage
reporting
usage monitoring
function entity
Prior art date
Application number
PCT/CN2015/075308
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 WO2016062010A1 publication Critical patent/WO2016062010A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks

Definitions

  • the present invention relates to the field of communications, and in particular to a method and device for monitoring usage.
  • FIG. 1 is a schematic diagram of a logical architecture of a PCC according to the related art.
  • the PCC architecture includes the following functional entities: a policy. Policy and Charging Rules Function (PCRF), Policy and Control Enforcement Function (PCEF), Bearer Binding and Event Reporting (Bearer Binding and Event) Reporting Function (BBERF), Application Function (AF), Traffic Detection Function (TDF), Subscription Profile Repository (SPR), Offline Billing System (Offline charging system, referred to as OFCS), Online charging system (OCS).
  • PCRF Policy and Charging Rules Function
  • PCEF Policy and Control Enforcement Function
  • BBERF Bearer Binding and Event Reporting
  • AF Application Function
  • TDF Traffic Detection Function
  • SPR Subscription Profile Repository
  • OFCS Offline Billing System
  • OCS Online charging system
  • the PCRF is responsible for the formulation of the policy and accounting rules.
  • the PCC policy and the accounting rules are sent to the PCEF through the Gx interface.
  • the PCEF installs and executes the PCC policy, reports related events, and exchanges accounting information with the charging system.
  • the PCRF sends the service quality of service (QoS) rules to the BBERF through the Gxx interface.
  • QoS quality of service
  • the BBERF does not exchange accounting information with the accounting system. It is only responsible for reporting bearer bindings and related events.
  • the PCRF sends the service information to be monitored to the TDF through the Sd interface.
  • the TDF performs service monitoring and reports it to the PCRF.
  • the AF provides service information to the PCRF through the Rx interface.
  • the SPR saves the service information that the user subscribes to.
  • the PCRF can query the SPR for the service information subscribed by the user through the Sp interface.
  • the OCS reports policy counter status information related to user consumption to the PCRF through the Sy interface.
  • the PCEF sends the online charging information to the OCS through the Gy interface for online charging statistics, and sends the offline charging information to the OFCS through the Gz interface.
  • the TDF sends the service-based online charging information to the OCS through the Gyn interface, and sends the service-based offline charging information to the OFCS through the Gz n interface.
  • the PRCF actively queries the PCEF to report the user usage, and then accumulates the user's daily usage, and the next day usage is cleared and recounted.
  • the PCRF also actively queries the PCEF to report the usage of the user, and collects statistics on the busy hour and idle time respectively, which is convenient for the operator to perform different policies and charging control for busy hours and idle hours.
  • the usage statistics are not timely, there is a certain delay, for example, how long before 0 o'clock (there are many systems that push RAR 5 minutes in advance) Ask for the amount of reporting) to query.
  • the PCRF periodically batches the quantity of the active query to increase the message load between the systems, which may cause the CPU of the PCEF/TDF system to instantaneously rise;
  • PCRF timing batch active query usage whether it is on-time query or a certain amount of advance query, there may be early or late usage statistics, the statistical usage is not accurate, and the precise control of PCRF is not achieved.
  • the embodiment of the invention provides a method and a device for monitoring the quantity to solve at least the above problems in the quantity monitoring mode in the related art.
  • a usage monitoring method including: a policy control and charging rule function entity PCRF sends a usage monitoring rule for monitoring usage information to a function entity that performs usage monitoring, and carries the report The reporting time of the monitoring result corresponding to the usage monitoring rule; the PCRF receives the monitoring result reported by the functional entity that performs the usage monitoring at the reporting time.
  • the PCRF before the PCRF sends the usage monitoring rule for monitoring the usage information to the function entity that performs the usage monitoring, and the reporting time of the monitoring result corresponding to the usage monitoring rule is also reported, the PCRF further includes: Different types set the reporting time.
  • the monitoring object includes at least one of the following types: a user type, a service type, an access network type, and a neighboring office type.
  • the method further includes: the PCRF further carrying control information for the reporting switch, where the reporting switch is set to the indication Whether the function entity that performs the usage monitoring performs the reporting function of reporting the monitoring result according to the reporting time.
  • the function entity that performs the usage monitoring is enabled by default to enable the reporting function.
  • the function entity for performing usage monitoring includes at least one of the following: a policy and charging execution function entity PCEF, and a traffic monitoring function entity TDF.
  • a usage monitoring method including: a function entity that performs usage monitoring receives an usage monitoring rule sent by a policy control and charging rule function entity PCRF, and simultaneously reports the usage monitoring rule The reporting time of the corresponding monitoring result; the function entity that performs the usage monitoring monitors the usage information according to the usage monitoring rule, and reports the monitoring result to the PCRF when the reporting time is reached.
  • the function of the usage monitoring system receives the usage monitoring rule sent by the PCRF and the reporting time of the monitoring result corresponding to the usage monitoring rule.
  • the entity also receives control information for the reporting switch, and the reporting switch is configured to indicate whether the function entity that performs the usage monitoring has the function of reporting the monitoring result according to the reporting time.
  • the reporting function when the control information of the reporting switch is not received, the reporting function is enabled by default.
  • the function entity that performs the usage monitoring receives the shutdown control information of the reporting switch sent by the PCRF, and the function entity that performs the usage monitoring stops according to the foregoing.
  • the monitoring result is reported in the reporting time.
  • the method further includes: before the reporting time, the function entity that performs the usage monitoring receives the update reporting time corresponding to the usage monitoring rule sent by the PCRF; The monitoring result is reported to the PCRF by the update reporting time.
  • the function entity for performing usage monitoring includes at least one of the following: a policy and charging execution function entity PCEF, and a traffic monitoring function entity TDF.
  • a usage monitoring device which is located in a policy control and charging rule function entity PCRF, and includes: a sending module, configured to send a function for monitoring usage information to a function entity that performs usage monitoring
  • the usage monitoring rule carries the reporting time of the monitoring result corresponding to the usage monitoring rule;
  • the first receiving module is configured to receive the monitoring result reported by the functional entity that performs the usage monitoring at the reporting time.
  • another usage monitoring device which is located in a functional entity for performing usage monitoring, and includes: a second receiving module configured to receive the amount sent by the policy control and charging rule function entity PCRF The monitoring rule and the report time of the monitoring result corresponding to the usage monitoring rule are reported; the reporting module is configured to monitor the usage information according to the usage monitoring rule, and report the information to the PCRF when the reporting time is reached. Monitor the results.
  • the PCRF is used to send the usage monitoring rule for monitoring the usage information to the function entity for performing the usage monitoring, and the reporting time of the monitoring result corresponding to the usage monitoring rule is reported, and the PCRF receives the usage amount.
  • the manner in which the monitored functional entity reports the monitoring result reported in the time solves the problem that the usage monitoring mode in the related technology increases the inter-system message load and the statistical usage is inaccurate, and not only enables the PCRF to deliver the usage monitoring.
  • the time points can be dispersed to avoid the instantaneous CPU high caused by the usage monitoring rule, and the reporting time of the monitoring result can be flexibly set according to the usage monitoring rule, which improves the statistical accuracy, and can also spread the reporting time of the monitoring result. Reduce the load of messages between systems.
  • FIG. 1 is a schematic diagram of a PCC logical architecture according to the related art
  • FIG. 2 is a flow chart of a usage monitoring method according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of an amount monitoring device according to an embodiment of the present invention.
  • FIG. 4 is a flow chart of another usage monitoring method according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of another usage monitoring device according to an embodiment of the present invention.
  • FIG. 6 is a flow chart of monitoring the timing report usage according to a preferred embodiment of the present invention.
  • FIG. 7 is a flow chart of adjusting the usage monitoring timing reporting time according to a preferred embodiment of the present invention.
  • Figure 8 is a flow diagram of the usage monitoring timing escalation in accordance with a preferred embodiment of the present invention.
  • FIG. 2 is a flowchart of a usage monitoring method according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps:
  • step S202 the policy control and charging rule function entity (PCRF) sends a usage monitoring rule for monitoring the usage information to the function entity that performs the usage monitoring, and carries the reporting time of the monitoring result corresponding to the usage monitoring rule.
  • PCRF policy control and charging rule function entity
  • Step S204 the PCRF receives the monitoring result reported by the function entity that performs the usage monitoring at the reporting time.
  • the PCRF sends the usage monitoring rule to the functional entity that performs the usage monitoring, and also carries the reporting time of the monitoring result, which solves the problem that the usage monitoring mode in the related technology increases the inter-system message load and statistics.
  • the problem of inaccurate usage can not only make the time of monitoring the amount of the PCRF to be distributed, but also avoid the CPU instantaneous high caused by the usage monitoring rule, and can flexibly set the reporting time of the monitoring result according to the usage monitoring rule, and improve the time.
  • Statistical accuracy in addition, can spread the reporting time of monitoring results and reduce the message load between systems.
  • the PCRF may set the reporting time according to different types of monitoring objects. This can further improve statistical accuracy and reduce the load of messages between systems.
  • the monitoring object may include, but is not limited to, at least one of the following types: a user type, a service type, an access network type, a neighboring office type, and the like.
  • the PCRF may further carry control information for the reporting switch, where the reporting switch is set to indicate the Whether the function entity that performs the usage monitoring performs the reporting function of reporting the monitoring result according to the reporting time.
  • the function entity that performs the usage monitoring may be instructed to enable the reporting function by default.
  • the function entity for performing usage monitoring includes at least one of the following: a Policy and Charging Enforcement Function Entity (PCEF), and a Traffic Monitoring Function Entity (TDF).
  • PCEF Policy and Charging Enforcement Function Entity
  • TDF Traffic Monitoring Function Entity
  • a usage monitoring device is also provided, which is located in a policy control and charging rule function entity (PCRF), and the device is configured to implement the above embodiment and a preferred embodiment, and has been described. No longer repeat them.
  • PCRF policy control and charging rule function entity
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • FIG. 3 is a structural block diagram of a usage monitoring device according to an embodiment of the present invention. As shown in FIG. 3, the device includes a transmitting module 32 and a first receiving module 34. The following describes each module in detail:
  • the sending module 32 is configured to send the usage monitoring rule for monitoring the usage information to the function entity that performs the usage monitoring, and the reporting time of the monitoring result corresponding to the usage monitoring rule is reported; the first receiving module 34, and the sending module 32 Connected, configured to receive the monitoring result reported by the function entity that performs the usage monitoring at the reporting time.
  • FIG. 4 is a flowchart of another usage monitoring method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:
  • step S402 the function entity that performs the usage monitoring receives the usage monitoring rule sent by the policy control and charging rule function entity (PCRF) and the reporting time of the monitoring result corresponding to the usage monitoring rule.
  • PCRF policy control and charging rule function entity
  • step S404 the function entity that performs the usage monitoring monitors the usage information according to the usage monitoring rule, and reports the monitoring result to the PCRF when the reporting time is reached.
  • the PCRF sends the usage monitoring rule to the functional entity that performs the usage monitoring, and also carries the reporting time of the monitoring result, which solves the problem that the usage monitoring mode in the related technology increases the inter-system message load and statistics.
  • the problem of inaccurate usage can not only make the time of monitoring the amount of the PCRF to be distributed, but also avoid the CPU instantaneous high caused by the usage monitoring rule, and can flexibly set the reporting time of the monitoring result according to the usage monitoring rule, and improve the time.
  • Statistical accuracy in addition, can spread the reporting time of monitoring results and reduce the message load between systems.
  • the function entity for performing usage monitoring in this embodiment may include at least one of the following: a Policy and Charging Enforcement Function Entity (PCEF), and a Traffic Monitoring Function Entity (TDF).
  • PCEF Policy and Charging Enforcement Function Entity
  • TDF Traffic Monitoring Function Entity
  • the function entity that performs the usage monitoring may further receive the control information of the reporting switch, and the reporting switch is configured to indicate whether the function entity that performs the usage monitoring reports the monitoring result according to the reporting time. Reporting function.
  • the reporting function may be enabled by default.
  • the function entity that performs the usage monitoring may stop reporting the monitoring result according to the reporting time, if receiving the closing control information of the reporting switch sent by the PCRF. That is, the reporting switch (also referred to as a timing monitoring switch) can stop or turn on the monitoring and reporting of the timing usage, but does not stop the normal reporting of the usage amount of the usage fragment.
  • the monitoring and reporting of the timing usage mentioned here is the PCRF active usage query that can be performed in the protocol, and the scheduling time is reported when the scheduling time is issued, and the interaction process of the active query usage is reduced, thereby reducing the system caused by the active query usage. load.
  • the function entity that performs the usage monitoring may receive the update reporting time corresponding to the usage monitoring rule sent by the PCRF, and may send the PCRF to the PCRF according to the update reporting time. Report the monitoring results.
  • the PCRF makes the control of the reporting time more flexible.
  • another usage monitoring device is provided in the embodiment, which is located in a functional entity for performing usage monitoring, and the device is configured to implement the above embodiment and the preferred embodiment, and has been performed.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of another usage monitoring device according to an embodiment of the present invention. As shown in FIG. 5, the device includes a second receiving module 52 and a reporting module 54. The following describes each module in detail:
  • the second receiving module 52 is configured to receive the usage monitoring rule sent by the policy control and charging rule function entity (PCRF) and the reporting time of the monitoring result corresponding to the usage monitoring rule, and the reporting module 54 and the second The receiving module 52 is connected to be configured to monitor the usage information according to the usage monitoring rule, and report the monitoring result to the PCRF when the reporting time is reached.
  • PCRF policy control and charging rule function entity
  • a method and system for implementing usage timing monitoring control involve a Policy Control and Charging Rules Function (PCRF) and a Policy and Charging Enforcement Function Entity (PCEF,
  • PCRF Policy Control and Charging Rules Function
  • PCEF Policy and Charging Enforcement Function Entity
  • TDF Traffic Detection Function
  • the preferred embodiment provides a method and system for implementing the usage timing monitoring control, including the PCRF according to the operator's traffic planning and system planning, and the PCEF/TDF can be indicated in advance by the invention.
  • the PCEF/TDF stores the reporting time of the monitoring information, and once the reporting time is reached, the monitoring usage is immediately reported.
  • the PCRF sets the reporting time by distinguishing the user type and the service type. After the PCEF/TDF reports the usage, the PCRF can periodically analyze the usage information of different user types and service modes, and then indicate the new policy according to the reported usage information.
  • the preferred embodiment sends the time for reporting the usage according to the user type and service type, specifically:
  • the PCEF/TDF finds that the time for reporting the usage is 1 to report the usage of the monitoring rule.
  • the PCRF performs policy control or charging policy control according to the amount reported by the PCEF/TDF, and delivers the time 2 for reporting the usage timing;
  • the operator Before the scheduled usage time is 2, the operator re-plans the scheduled reporting time 3 according to the usage and other information;
  • the PCRF updates the policy control or charging policy, and issues a new time 3 for timely reporting usage
  • the PCEF/TDF finds that the time for reporting the usage is 3, and reports the usage of the monitoring rule.
  • the PCRF performs policy control or charging policy control according to the amount reported by the PCEF/TDF, and delivers the time 4 for reporting the usage timing;
  • the preferred embodiment carries the time for periodically reporting the usage when the monitoring rule is sent by the PCRF, and can actively adjust the timing reporting time during the monitoring period, or even stop the timing reporting function.
  • the solution is flexible and can be used to set the timing report parameters according to the user type, service type, access network type, and neighboring office type to meet the requirements of various timing queries and analysis usage of the operator.
  • FIG. 6 is a flow chart of the timing report usage monitoring according to a preferred embodiment of the present invention.
  • the PCRF sends the usage monitoring rule to the PCEF/TDF
  • the time required to report the usage of the PCEF/TDF timing and the on-time reporting switch are carried.
  • PCEF/TDF detects the time of reporting the usage time, it reports the usage information of the monitoring usage.
  • the PCRF updates the usage monitoring rule to the PCEF/TDF according to the reported monitoring usage information. If the periodic reporting function is not required, the timing reporting switch is disabled.
  • FIG. 7 is a flow chart of adjusting the usage monitoring timing report time according to a preferred embodiment of the present invention.
  • the PCRF sends the usage monitoring rule to the PCEF/TDF
  • the time 1 and the time required for the PCEF/TDF timing report are carried. Turn on the timing report switch. Due to the operator's planning requirements, the timed reporting time of the usage quantity needs to be modified.
  • the PCRF updates the usage monitoring rule to the PCEF/TDF, and carries the new timed reporting time.
  • the PCEF/TDF detects the timing report usage time 2 to report the usage information of the monitoring usage.
  • the PCRF updates the usage monitoring rule to the PCEF/TDF according to the reported monitoring usage information. If the periodic reporting function is not required, the timing reporting switch is disabled.
  • FIG. 8 is a flowchart of the timing monitoring of the usage monitoring according to the preferred embodiment of the present invention. As shown in FIG. 8 , when the PCRF sends the usage monitoring rule to the PCEF/TDF, the time required to report the usage of the PCEF/TDF timing and the reporting of the opening timing are carried. switch. Then, modify the timing report time and decide whether to close the timing report switch according to the information such as the usage report information and the operator's planning requirements.
  • Step S2 The PCRF presets the usage timing report time 1 according to the user type, the service type, the access network type, the neighboring office, and the distribution of the operating enterprise usage;
  • Step S4 The PCEF/TDF carries information such as a user number and an IP address, and initiates a user online process;
  • Step S6 The PCRF sends a monitoring rule according to the user type and the service type, and carries the monitoring timing reporting time 1 in the monitoring information, and starts the timing reporting switch.
  • Step S8 The PCEF/TDF detects the timing report time of 1 cycle to;
  • Step S10 The usage information of the monitoring is reported by the PCEF/TDF;
  • Step S12 The PCRF sends a monitoring rule according to the user type and the service type, and updates the monitoring timing reporting time in the monitoring information to time 2;
  • Step S14 According to the operator's usage planning adjustment request, the PCRF combines the user type, the service type and other information, and updates the monitoring timing reporting time in the RAR to time 3;
  • Step S16 the PCEF/TDF returns the RAA success response, and updates the monitoring rule timing time 3;
  • Step S18 The PCEF/TDF detects the timing reporting time of 3 cycles to;
  • Step S20 The usage information of the monitoring is reported by the PCEF/TDF;
  • Step S22 The PCRF sends a monitoring rule according to the user type and the service type, and updates the monitoring timing reporting time in the monitoring information to time 4;
  • Step S24 The PCEF/TDF detects the timing report time of 4 cycles to;
  • Step S26 The PCEF/TDF reports the usage information of the monitoring
  • Step S28 The PCRF sends the monitoring rule according to the user type and the service type, and the timing reporting function is no longer needed.
  • the usage fragment is updated in the monitoring information, and the timing reporting switch is closed.
  • Table 1 is an extended timing reporting time and a timing reporting switch information in the usage monitoring information in the Credit Control Control Response (CCA) and RAR messages according to a preferred embodiment of the present invention. Time, the default timing report switch is turned on.
  • CCA Credit Control Control Response
  • the timing of the periodic reporting time and the timing report switch information in the CCA and RAR messages can be as follows (bold identification):
  • a software is provided that is configured to perform the technical solutions described in the above embodiments and preferred embodiments.
  • a storage medium in which the above software is stored, including but not limited to an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network 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 thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method and device for monitoring the usage of the embodiments of the present invention have the following beneficial effects: the problem of increasing the inter-system message load and the inaccurate statistical usage in the usage monitoring mode in the related art is solved, which not only makes the PCRF
  • the time of monitoring the delivery amount can be dispersed, avoiding the instantaneous CPU rise caused by the usage monitoring rule, and the reporting time of the monitoring result can be flexibly set according to the usage monitoring rule, which improves the statistical accuracy and can also spread the monitoring.
  • the reporting time of the results reduces the load of messages between systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种用量监控方法及装置,其中,该方法包括:PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;所述PCRF接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。通过本发明,解决了相关技术中的用量监测方式存在的增加系统间消息负荷且统计用量不准确的问题,不但使得PCRF下发用量监控的时间点能够分散开,避免下发用量监控规则导致的CPU瞬时冲高,而且能够根据用量监控规则灵活设置监控结果的上报时间,提升了统计精确性,此外也能分散开监控结果的上报时间,降低系统间消息负荷。

Description

用量监控方法及装置 技术领域
本发明涉及通信领域,具体而言,涉及一种用量监控方法及装置。
背景技术
随着策略和计费控制(Policy and Charging Control,简称为PCC)架构不断演进,图1是根据相关技术中的PCC逻辑架构示意图,如图1所示,PCC架构包含如下几个功能实体:策略控制与计费规则功能实体(Policy and Charging Rules Function,简称为PCRF)、策略和计费执行功能实体(Policy and Control Enforcement Function,简称为PCEF)、承载绑定和事件上报功能(Bearer Binding and Event Reporting Function,简称为BBERF)、应用功能(Application Function,简称为AF)、流量监测功能实体(Traffic Detection Function,简称为TDF)、用户签约数据库(Subscription Profile Repository,简称为SPR)、离线计费系统(Offline charging system,简称为OFCS)、在线计费系统(Online charging system,简称为OCS)。
PCRF主要负责策略和计费规则的制定,通过Gx接口将制定的PCC策略和计费规则下发给PCEF,PCEF安装、执行PCC策略,并上报相关事件,与计费系统交互计费信息。PCRF通过Gxx接口将业务服务质量(Quality of Service,简称为QoS)规则下发给BBERF,BBERF不和计费系统交互计费信息,只负责承载绑定和相关事件的上报。PCRF通过Sd接口把需要监控的业务信息下发给TDF,TDF执行业务监控,并上报给PCRF。AF通过Rx接口向PCRF提供业务信息。SPR保存了用户签约的业务信息,PCRF可以通过Sp接口向SPR查询用户签约的业务信息。OCS通过Sy接口向PCRF报告与用户消费相关的策略计数器状态信息。PCEF通过Gy接口将在线计费信息发送给OCS进行在线计费的统计,通过Gz接口将离线计费信息发送给OFCS。TDF通过Gyn接口将基于业务的在线计费信息发送给OCS,通过Gz n接口将基于业务的离线计费信息发送给OFCS。
目前PCRF系统有很多场景主动查询PCEF要求上报用户用量,如0点清零,忙闲时切换等场景。在0点时系统用量清零前,PRCF主动查询PCEF要求上报用户用量,然后累计该用户当日用量,次日用量清零重新计数。在忙闲切换时,PCRF也会主动查询PCEF要求上报用户用量,对忙时、闲时用量分别统计,便于运营商对忙时、闲时执行不同的策略、计费控制。
然而,此类PCRF批量主动触发查询用量的方式,存在如下缺陷:
1、不管是0时清零触发,还是忙闲时切换触发用量查询,会增加PCRF系统和PCEF/TDF系统间瞬时消息流量,如推送重授权请求(Re-Auth-Request,简称为RAR)要求PCEF/TDF上报用量,PCEF/TDF在回重授权应答(Re-Auth-Answer,简称为RAA)后,通过信用控制更新请求(Credit-Control-Request Update,简称为CCR-U)主动上报用量;
2、不管是0时清零触发,还是忙闲时切换触发用量查询,都会有用量统计不及时,存在一定的延时,例如在0点前多长时间(有很多系统是提前5分钟推送RAR要求上报用量)去查询。
带来的后果是:
1.PCRF定时批量主动查询用量的方式,增加系统间消息负荷,可能导致PCEF/TDF系统CPU瞬时冲高;
2.PCRF定时批量主动查询用量的时机问题,不管是准时查询还是按一定提前量的方式查询,可能会存在用量提前或滞后统计情况,存在统计用量不准确,达不到PCRF精确控制的目的。
针对相关技术中的用量监控方式存在的上述问题,目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种用量监控方法及装置,以至少解决相关技术中的用量监测方式存在的上述问题。
根据本发明的一个实施例,提供了一种用量监控方法,包括:策略控制与计费规则功能实体PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;所述PCRF接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
本实施例中,在PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间之前,还包括:PCRF根据监控对象的不同类型设定所述上报时间。
本实施例中,所述监控对象包括以下类型至少之一:用户类型、业务类型、接入网类型、邻接局类型。
本实施例中,在PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则的过程中,还包括:所述PCRF还携带对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否开启按照所述上报时间上报所述监控结果的上报功能。
本实施例中,在未携带所述上报开关的控制信息的情况下,默认指示所述进行用量监控的功能实体开启所述上报功能。
本实施例中,所述进行用量监控的功能实体包括以下至少之一:策略和计费执行功能实体PCEF,流量监测功能实体TDF。
根据本发明的另一实施例,提供了一种用量监控方法,包括:进行用量监控的功能实体接收策略控制与计费规则功能实体PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;所述进行用量监控的功能实体根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
本实施例中,在进行用量监控的功能实体接收PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间的过程中,还包括:所述进行用量监控的功能实体还接收对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否开启按照所述上报时间上报所述监控结果的上报功能。
本实施例中,在未接收到所述上报开关的控制信息的情况下,默认开启所述上报功能。
本实施例中,还包括:在到达所述上报时间之前,所述进行用量监控的功能实体接收到PCRF发送的所述上报开关的关闭控制信息;所述进行用量监控的功能实体停止按照所述上报时间上报所述监控结果。
本实施例中,还包括:在到达所述上报时间之前,所述进行用量监控的功能实体接收到PCRF发送的所述用量监控规则对应的更新上报时间;所述进行用量监控的功能实体按照所述更新上报时间向所述PCRF上报所述监控结果。
本实施例中,所述进行用量监控的功能实体包括以下至少之一:策略和计费执行功能实体PCEF,流量监测功能实体TDF。
根据本发明的再一实施例,提供了一种用量监控装置,位于策略控制与计费规则功能实体PCRF中,包括:发送模块,设置为向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;第一接收模块,设置为接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
根据本发明的再一实施例,还提供了另一种用量监控装置,位于进行用量监控的功能实体中,包括:第二接收模块,设置为接收策略控制与计费规则功能实体PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;上报模块,设置为根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
通过本发明实施例,采用PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;所述PCRF接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果的方式,解决了相关技术中的用量监测方式存在的增加系统间消息负荷且统计用量不准确的问题,不但使得PCRF下发用量监控的时间点能够分散开,避免下发用量监控规则导致的CPU瞬时冲高,而且能够根据用量监控规则灵活设置监控结果的上报时间,提升了统计精确性,此外也能分散开监控结果的上报时间,降低系统间消息负荷。
附图说明
此处所说明的附图用来提供对本发明的进一步理解,构成本申请的一部分,本发明的示意性实施例及其说明用于解释本发明,并不构成对本发明的不当限定。在附图中:
图1是根据相关技术中的PCC逻辑架构示意图;
图2是根据本发明实施例的一种用量监控方法的流程图;
图3是根据本发明实施例的一种用量监控装置的结构框图;
图4是根据本发明实施例的另一种用量监控方法的流程图;
图5是根据本发明实施例的另一种用量监控装置的结构框图;
图6是根据本发明优选实施例的定时上报用量监控流程图;
图7是根据本发明优选实施例的调整用量监控定时上报时间的流程图;
图8是根据本发明优选实施例的用量监控定时上报的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中,提供了一种用量监控方法,图2是根据本发明实施例的一种用量监控方法的流程图,如图2所示,该方法包括如下步骤:
步骤S202,策略控制与计费规则功能实体(PCRF)向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;
步骤S204,所述PCRF接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
本实施例通过上述步骤,PCRF在向进行用量监控的功能实体发送用量监控规则的同时,还携带了监控结果的上报时间,解决了相关技术中的用量监测方式存在的增加系统间消息负荷且统计用量不准确的问题,从而不但使得PCRF下发用量监控的时间点能够分散开,避免下发用量监控规则导致的CPU瞬时冲高,而且能够根据用量监控规则灵活设置监控结果的上报时间,提升了统计精确性,此外也能分散开监控结果的上报时间,降低系统间消息负荷。
本实施例中,PCRF可以根据监控对象的不同类型设定所述上报时间。这样能够进一步提升统计精确性,以及降低系统间消息负荷。
其中,所述监控对象可以包括但不限于以下类型至少之一:用户类型、业务类型、接入网类型、邻接局类型等。
本实施例中,在PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则的过程中,所述PCRF还可以携带对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否开启按照所述上报时间上报所述监控结果的上报功能。
其中,在未携带所述上报开关的控制信息的情况下,可以默认指示所述进行用量监控的功能实体开启所述上报功能。
本实施例中,所述进行用量监控的功能实体包括以下至少之一:策略和计费执行功能实体(PCEF),流量监测功能实体(TDF)。
对应于上述方法,在本实施例中还提供了一种用量监控装置,位于策略控制与计费规则功能实体(PCRF)中,该装置设置为实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的一种用量监控装置的结构框图,如图3所示,该装置包括发送模块32和第一接收模块34,下面对各个模块进行详细说明:
发送模块32,设置为向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;第一接收模块34,与发送模块32相连,设置为接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
在本实施例中还提供了另一种用量监控方法,图4是根据本发明实施例的另一种用量监控方法的流程图,如图4所示,该方法包括如下步骤:
步骤S402,进行用量监控的功能实体接收策略控制与计费规则功能实体(PCRF)发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;
步骤S404,所述进行用量监控的功能实体根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
本实施例通过上述步骤,PCRF在向进行用量监控的功能实体发送用量监控规则的同时,还携带了监控结果的上报时间,解决了相关技术中的用量监测方式存在的增加系统间消息负荷且统计用量不准确的问题,从而不但使得PCRF下发用量监控的时间点能够分散开,避免下发用量监控规则导致的CPU瞬时冲高,而且能够根据用量监控规则灵活设置监控结果的上报时间,提升了统计精确性,此外也能分散开监控结果的上报时间,降低系统间消息负荷。
本实施例中的所述进行用量监控的功能实体可以包括以下至少之一:策略和计费执行功能实体(PCEF),流量监测功能实体(TDF)。
本实施例中,所述进行用量监控的功能实体还可以接收对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否按照所述上报时间上报开启所述监控结果的上报功能。
其中,在未接收到所述上报开关的控制信息的情况下,则可以默认开启所述上报功能。
其中,在到达所述上报时间之前,所述进行用量监控的功能实体如果接收到PCRF发送的所述上报开关的关闭控制信息,则可以停止按照所述上报时间上报所述监控结果。也即,上报开关(也可以称为定时监控开关)可以停止或开启定时用量的监控上报,但不会停止达到用量分片进行用量的正常上报。这里所说的定时用量的监控上报,即为协议中可进行的PCRF主动用量查询,通过下发规则时下发预约时间定时上报,减少主动查询用量的交互流程,从而降低了主动查询用量导致的系统负荷。
本实施例中,在到达所述上报时间之前,所述进行用量监控的功能实体如果接收到PCRF发送的所述用量监控规则对应的更新上报时间,则可以按照所述更新上报时间向所述PCRF上报所述监控结果。通过上述更新方式,使得PCRF对上报时间的控制更加灵活。
对应于上述另一种用量监控装置,在本实施例中还提供了另一种用量监控装置,位于进行用量监控的功能实体中,该装置设置为实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本发明实施例的另一种用量监控装置的结构框图,如图5所示,该装置包括第二接收模块52和上报模块54,下面对各个模块进行详细说明:
第二接收模块52,设置为接收策略控制与计费规则功能实体(PCRF)发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;上报模块54,与第二接收模块52相连,设置为根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
下面结合优选实施例进行说明,以下优选实施例结合了上述实施例及其优选实施方式。
在以下优选实施例中,提供了一种实现用量定时监测控制的方法及系统,涉及策略控制与计费规则功能实体(PCRF,Policy and Charging Rules Function)与策略和计费执行功能实体(PCEF,Policy and Control Enforcement Function)/流量监测功能实体(TDF,Traffic Detection Function)之间的用量监控技术,是一种PCC(Policy and Charging Control,策略和计费控制)架构中用量定时监测控制的实现方法。
考虑到PCRF定时批量主动查询用量的方式,会导致系统间负荷瞬时冲高,甚至过冲,批量查询的时机不好把握,存在时延问题。本优选实施例提供了一种实现用量定时监测控制的方法及系统,包括PCRF根据运营商的流量规划和系统规划,能够提前下发明确的上报时间指示PCEF/TDF。PCEF/TDF存储该监控信息的上报时间,一旦监测到上报时间到,即刻上报该监控用量。PCRF通过区分用户类型、业务类型等方式设定上报时间,在PCEF/TDF定时上报用量后,PCRF就可以定时分析不同用户类型、业务方式的用量信息,然后根据上报的用量信息指示新的策略。
本优选实施例在PCRF向PCEF/TDF下发用量监控规则时,根据用户类型、业务类型等方式下发定时上报用量的时间,具体地说:
1、PCRF向PCEF/TDF下发用量监控规则时,携带需要PCEF/TDF定时上报用量的时间1;
2、PCEF/TDF发现定时上报用量的时间1到,上报该监控规则的用量;
3、PCRF根据PCEF/TDF上报的用量,进行策略控制或计费策略控制,下发定时上报用量的时间2;
4、在定时上报用量时间2到之前,运营商根据用量等信息重新规划定时上报用量时间3;
5、PCRF更新策略控制或计费策略,下发定时上报用量的新时间3;
6、PCEF/TDF发现定时上报用量的时间3到,上报该监控规则的用量;
7、PCRF根据PCEF/TDF上报的用量,进行策略控制或计费策略控制,下发定时上报用量的时间4;
8、在定时上报用量时间4到之前,运营商根据用量等信息需要取消定时上报用量;
9、PCEF/TDF对该用量监控规则不再定时上报用量。
本优选实施例通过PCRF在下发监控规则时携带定时上报用量的时间,并且能够在监控期间主动调整定时上报时间,甚至停止定时上报功能。该方案使用灵活,可根据用户类型、业务类型、接入网类型、邻接局类型等参数设置定时上报参数,满足运营商的各种定时查询、分析用量的要求。
图6是根据本发明优选实施例的定时上报用量监控流程图,如图6所示,PCRF向PCEF/TDF下发用量监控规则时,携带需要PCEF/TDF定时上报用量的时间和开启定时上报开关。PCEF/TDF检测到定时上报用量时间到,上报该监控用量使用信息。PCRF根据上报的监控用量信息,向PCEF/TDF更新用量监控规则,若不需要定时上报功能,关闭定时上报开关。
图7是根据本发明优选实施例的调整用量监控定时上报时间的流程图,如图7所示,PCRF向PCEF/TDF下发用量监控规则时,携带需要PCEF/TDF定时上报用量的时间1和开启定时上报开关。由于运营商规划要求,需要修改用量的定时上报时间,PCRF向PCEF/TDF更新用量监控规则,携带新的定时上报用量的时间2。PCEF/TDF检测到定时上报用量时间2到,上报该监控用量使用信息。PCRF根据上报的监控用量信息,向PCEF/TDF更新用量监控规则,若不需要定时上报功能,关闭定时上报开关。
图8是根据本发明优选实施例的用量监控定时上报的流程图,如图8所示,PCRF向PCEF/TDF下发用量监控规则时,携带需要PCEF/TDF定时上报用量的时间和开启定时上报开关。然后,根据用量上报信息、运营商规划要求等信息修改定时上报时间和决定是否关闭定时上报开关。
下面详细介绍定时上报用量监控,其主要步骤可以参见图8:
步骤S2:PCRF根据用户类型、业务类型、接入网类型、邻接局等参数和运营企业用量分布情况,预先设置用量定时上报时间1;
步骤S4:PCEF/TDF携带用户号码、IP地址等信息,发起用户上线流程;
步骤S6:PCRF根据用户类型、业务类型等下发监控规则,在监控信息中携带监控定时上报时间1,开启定时上报开关;
步骤S8:PCEF/TDF检测到定时上报时间1周期到;
步骤S10:PCEF/TDF上报监控的用量使用信息;
步骤S12:PCRF根据用户类型、业务类型等下发监控规则,在监控信息中更新监控定时上报时间为时间2;
步骤S14:根据运营商的用量规划调整要求,PCRF结合用户类型、业务类型等信息,在RAR中更新监控定时上报时间为时间3;
步骤S16:PCEF/TDF回送RAA成功应答,更新监控规则定时时间3;
步骤S18:PCEF/TDF检测到定时上报时间3周期到;
步骤S20:PCEF/TDF上报监控的用量使用信息;
步骤S22:PCRF根据用户类型、业务类型等下发监控规则,在监控信息中更新监控定时上报时间为时间4;
步骤S24:PCEF/TDF检测到定时上报时间4周期到;
步骤S26:PCEF/TDF上报监控的用量使用信息;
步骤S28:PCRF根据用户类型、业务类型等下发监控规则,且不再需要定时上报功能,在监控信息中更新用量分片,同时关闭定时上报开关。
表1是根据本发明优选实施例的在信用控制更新响应(Credit-Control-Answer,简称为CCA)、RAR消息中的用量监控信息中扩展定时上报时间和定时上报开关信息,若只携带定时上报时间,默认定时上报开关开启。
表1
Figure PCTCN2015075308-appb-000001
Figure PCTCN2015075308-appb-000002
定时上报时间和定时上报开关信息在CCA、RAR消息中的位置可以按照如下所示(加粗标识):
Figure PCTCN2015075308-appb-000003
Figure PCTCN2015075308-appb-000004
在另外一个实施例中,还提供了一种软件,该软件设置为执行上述实施例及优选实施例中描述的技术方案。
在另外一个实施例中,还提供了一种存储介质,该存储介质中存储有上述软件,该存储介质包括但不限于光盘、软盘、硬盘、可擦写存储器等。
显然,本领域的技术人员应该明白,上述的本发明的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,可选地,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已,并不用于限制本发明,对于本领域的技术人员来说,本发明可以有各种更改和变化。凡在本发明的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本发明的保护范围之内。
工业实用性
如上所述,本发明实施例提供的一种用量监控方法及装置,具有以下有益效果:解决了相关技术中的用量监测方式存在的增加系统间消息负荷且统计用量不准确的问题,不但使得PCRF下发用量监控的时间点能够分散开,避免下发用量监控规则导致的CPU瞬时冲高,而且能够根据用量监控规则灵活设置监控结果的上报时间,提升了统计精确性,此外也能分散开监控结果的上报时间,降低系统间消息负荷。

Claims (14)

  1. 一种用量监控方法,包括:
    策略控制与计费规则功能实体PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;
    所述PCRF接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
  2. 根据权利要求1所述的方法,其中,在PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间之前,还包括:
    PCRF根据监控对象的不同类型设定所述上报时间。
  3. 根据权利要求2所述的方法,其中,所述监控对象包括以下类型至少之一:用户类型、业务类型、接入网类型、邻接局类型。
  4. 根据权利要求1所述的方法,其中,在PCRF向进行用量监控的功能实体发送用于监控用量信息的用量监控规则的过程中,还包括:
    所述PCRF还携带对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否开启按照所述上报时间上报所述监控结果的上报功能。
  5. 根据权利要求4所述的方法,其中,在未携带所述上报开关的控制信息的情况下,默认指示所述进行用量监控的功能实体开启所述上报功能。
  6. 根据权利要求1至5中任一项所述的方法,其中,所述进行用量监控的功能实体包括以下至少之一:策略和计费执行功能实体PCEF,流量监测功能实体TDF。
  7. 一种用量监控方法,包括:
    进行用量监控的功能实体接收策略控制与计费规则功能实体PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;
    所述进行用量监控的功能实体根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
  8. 根据权利要求7所述的方法,其中,在进行用量监控的功能实体接收PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间的过程中,还包括:
    所述进行用量监控的功能实体还接收对上报开关的控制信息,所述上报开关设置为指示所述进行用量监控的功能实体是否开启按照所述上报时间上报所述监控结果的上报功能。
  9. 根据权利要求8所述的方法,其中,在未接收到所述上报开关的控制信息的情况下,默认开启所述上报功能。
  10. 根据权利要求8所述的方法,其中,还包括:
    在到达所述上报时间之前,所述进行用量监控的功能实体接收到PCRF发送的所述上报开关的关闭控制信息;
    所述进行用量监控的功能实体停止按照所述上报时间上报所述监控结果。
  11. 根据权利要求7所述的方法,其中,还包括:
    在到达所述上报时间之前,所述进行用量监控的功能实体接收到PCRF发送的所述用量监控规则对应的更新上报时间;
    所述进行用量监控的功能实体按照所述更新上报时间向所述PCRF上报所述监控结果。
  12. 根据权利要求7至11中任一项所述的方法,其中,所述进行用量监控的功能实体包括以下至少之一:策略和计费执行功能实体PCEF,流量监测功能实体TDF。
  13. 一种用量监控装置,位于策略控制与计费规则功能实体PCRF中,包括:
    发送模块,设置为向进行用量监控的功能实体发送用于监控用量信息的用量监控规则,同时携带上报所述用量监控规则对应的监控结果的上报时间;
    第一接收模块,设置为接收所述进行用量监控的功能实体在所述上报时间上报的所述监控结果。
  14. 一种用量监控装置,位于进行用量监控的功能实体中,包括:
    第二接收模块,设置为接收策略控制与计费规则功能实体PCRF发送的用量监控规则及同时携带的上报所述用量监控规则对应的监控结果的上报时间;
    上报模块,设置为根据所述用量监控规则监控用量信息,并在到达所述上报时间时向所述PCRF上报所述监控结果。
PCT/CN2015/075308 2014-10-20 2015-03-27 用量监控方法及装置 WO2016062010A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410560303.9A CN105591828A (zh) 2014-10-20 2014-10-20 用量监控方法及装置
CN201410560303.9 2014-10-20

Publications (1)

Publication Number Publication Date
WO2016062010A1 true WO2016062010A1 (zh) 2016-04-28

Family

ID=55760173

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075308 WO2016062010A1 (zh) 2014-10-20 2015-03-27 用量监控方法及装置

Country Status (2)

Country Link
CN (1) CN105591828A (zh)
WO (1) WO2016062010A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107729205A (zh) * 2017-08-22 2018-02-23 国家电网公司 用于业务系统的故障处理方法和装置
CN110851330A (zh) * 2019-11-13 2020-02-28 重庆秦嵩科技有限公司 一种cpu在线监控方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110381455B (zh) * 2016-06-30 2021-02-23 华为技术有限公司 流量监控处理方法和相关装置和系统
CN108076477B (zh) * 2016-11-15 2021-10-29 中兴通讯股份有限公司 一种数据流量监控方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202656A (zh) * 2006-12-15 2008-06-18 中兴通讯股份有限公司 资源监控方法和装置
CN102076009A (zh) * 2009-11-25 2011-05-25 中国移动通信集团广东有限公司 小区监控方法和装置
CN103167636A (zh) * 2011-12-19 2013-06-19 中国移动通信集团公司 一种控制物联网终端的工作状态的方法、系统以及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625272B (zh) * 2011-01-31 2017-03-29 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统
CN103856926A (zh) * 2012-11-28 2014-06-11 中兴通讯股份有限公司 一种计费方法以及策略执行、策略和计费控制功能设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202656A (zh) * 2006-12-15 2008-06-18 中兴通讯股份有限公司 资源监控方法和装置
CN102076009A (zh) * 2009-11-25 2011-05-25 中国移动通信集团广东有限公司 小区监控方法和装置
CN103167636A (zh) * 2011-12-19 2013-06-19 中国移动通信集团公司 一种控制物联网终端的工作状态的方法、系统以及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107729205A (zh) * 2017-08-22 2018-02-23 国家电网公司 用于业务系统的故障处理方法和装置
CN107729205B (zh) * 2017-08-22 2021-01-05 国家电网公司 用于业务系统的故障处理方法和装置
CN110851330A (zh) * 2019-11-13 2020-02-28 重庆秦嵩科技有限公司 一种cpu在线监控方法

Also Published As

Publication number Publication date
CN105591828A (zh) 2016-05-18

Similar Documents

Publication Publication Date Title
US10341496B2 (en) Policy control method and system, and relevant apparatus
US10972613B2 (en) Charging control method, charging trigger apparatus, and online charging system
WO2016062010A1 (zh) 用量监控方法及装置
US20200014549A1 (en) Computer Network Service Providing System Including Self Adjusting Volume Enforcement Functionality
US9596358B2 (en) System and method for corporate mobile subscription management
US20150296531A1 (en) Method and apparatus for controlling ppc rule in preload mode
US11689669B2 (en) Quota allocation to subscribers based on consumption speed, location, allowance, or combinations of the same
WO2015196599A1 (zh) 流量控制方法及装置
CN104735635B (zh) 一种策略控制方法和装置
US10924520B2 (en) Online charging mechanisms during OCS non-responsiveness
US9402003B2 (en) Data allocation for pre-paid group data plans
WO2020048532A1 (zh) Gx会话异常的处理方法及装置
US11038810B2 (en) Active subscriber count based charging and policy control
CN102316432A (zh) 用量的监控方法和系统
EP2563053B1 (en) Method and related device for controlling service charging
US9806893B2 (en) Methods systems and computer readable media for providing real time data network usage information using subscription profile repository (SPR)
WO2017092442A1 (zh) 策略和计费控制快速调整方法、装置及系统
WO2010094188A1 (zh) 业务策略控制方法及系统
WO2018040867A1 (zh) 一种用量配额的授权方法及装置
WO2023208343A1 (en) Quality of service monitoring
WO2017084722A1 (en) Charging system node and method performed by a charging system node for handling services provided to users of a provisioning network

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

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

Country of ref document: EP

Kind code of ref document: A1