WO2012088919A1 - 业务用量监控方法及设备 - Google Patents

业务用量监控方法及设备 Download PDF

Info

Publication number
WO2012088919A1
WO2012088919A1 PCT/CN2011/079313 CN2011079313W WO2012088919A1 WO 2012088919 A1 WO2012088919 A1 WO 2012088919A1 CN 2011079313 W CN2011079313 W CN 2011079313W WO 2012088919 A1 WO2012088919 A1 WO 2012088919A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
information
session
monitoring
level
Prior art date
Application number
PCT/CN2011/079313
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 华为技术有限公司
Priority to RU2012147778/08A priority Critical patent/RU2523962C2/ru
Priority to EP11853578.0A priority patent/EP2587737B1/en
Priority to CN201180001626.9A priority patent/CN102439907B/zh
Publication of WO2012088919A1 publication Critical patent/WO2012088919A1/zh
Priority to US13/690,044 priority patent/US9172760B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • 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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • 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/10—Metering calls from calling party, i.e. A-party charged for the communication
    • 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

Definitions

  • the embodiments of the present invention relate to communication technologies, and in particular, to a service usage monitoring method and device. Background technique
  • the IP network can provide more types of services such as multimedia calls, file downloads, and web browsing. Therefore, the network needs to be able to detect different service flows and collect accounting information such as traffic and duration to report to the billing center.
  • Organizations such as 3GPP and Worldwide Interoperability for Microwave Access (WiMAX) Forums define policy and charging control based on Policy and Charging Control (PCC) architecture, which can be implemented through PCC architecture.
  • PCC Policy and Charging Control
  • the network detects different traffic flows and implements quality of service (QoS) control, accounting statistics, etc. for traffic flows.
  • QoS quality of service
  • the PCC architecture includes functional entities such as a Policy Charging Enforcement Function (PCEF) and a Policy Charging Rules Function (PCRF).
  • PCEF supports listening to individual traffic flows or a set of traffic flows or all traffic within a session.
  • the PCRF supports usage management based on rule level and session level, and can dynamically control bandwidth/accounting rules by using the amount reported by the PCEF.
  • the Gf interface between the PCRF and the PCEF is used for policy delivery and usage reporting.
  • the PCEF requests the PCC rule from the PCRF through the GX interface.
  • the PCRF provides the PCC rule to the PCEF through the GX interface.
  • the PCEF passes the GX interface to the PCRF. Report the amount of business monitored according to the PCC rules.
  • the existing usage monitoring mechanism cannot be satisfied when there are the following requirements: For example, it is necessary to monitor the usage of a specific website such as the Sina website www.sina.com, and also need to monitor the usage of all HTTP protocols in the session for the user to access the Sina. Control the quality of service when a certain threshold is reached, and control the quality of service of a particular website when the HTTP service reaches a certain threshold. If rule-level monitoring is used, PCEF will only accumulate a rule to the service flow of www.sina.com. The usage of the service flow is reported to the corresponding rule of the HTTP protocol, or reported to www.sina.com. rule. The amount of this other rule is not a complete usage.
  • the session-level monitoring is to monitor the user's usage of all the services in the session.
  • any user accessing any website in the session is accumulated in a rule and reported to the PCRF, so that the user cannot access the www.
  • the embodiment of the present invention provides a service usage monitoring method and device, which is used to solve the defect that the service quantity reported by the PCEF to the PCRF is inaccurate in the prior art, and achieves the purpose of accurately collecting the user service usage by the PCRF.
  • the embodiment of the invention provides a method for monitoring a service usage, including:
  • the session-level service monitoring Tasks include session level service monitoring level identification, monitoring The task identifier and the specified service flow information; the monitoring level identifier indicates that the monitoring task is used to monitor the usage of the specified service flow in the session;
  • the monitoring task identifier and the cumulative usage of the service request information in the session-level service monitoring task are reported to the policy and charging rule function entity.
  • the embodiment of the invention provides a service usage monitoring device, which includes:
  • the session-level service monitoring task includes a session-level service monitoring level identifier, a monitoring task identifier, and a specified service flow information.
  • the monitoring level identifier indicates that the monitoring task is used to monitor the usage of the specified service flow in the session;
  • an accumulating module configured to accumulate in the one or more session-level service monitoring tasks when determining that the service request information is the same as the specified service flow information in the one or more session-level service monitoring tasks The amount of business request information
  • the reporting module is configured to report the cumulative usage of the monitoring task identifier and the service request information in the session-level service monitoring task to the policy and charging rule function entity.
  • the service usage monitoring method and device the PCEF monitors multiple specified services in a session of a specific user according to multiple session-level service monitoring tasks delivered by the PCRF, and receives the service request information received in the session.
  • the quintuple information, the protocol information, and the URL information are compared with the specified service flows corresponding to the session-level service monitoring tasks, and are determined to be the same as the service request information.
  • Specify business flow information The usage of the service request corresponding to the same specified service flow information is reported to the PCRF. Therefore, the embodiment of the present invention can accumulate the usage of a service flow to multiple PCR-level service monitoring tasks corresponding to the same specified service flow information, and overcome the problem that the PCEF cannot accumulate a service flow at most. Accurate defects are reported by the usage of the monitoring task, so that the PCRF can collect the accurate business usage of the user. Thereby controlling the subsequent quality of service.
  • Embodiment 1 is a flowchart of Embodiment 1 of a service usage monitoring method provided by the present invention
  • Embodiment 2 is a flowchart of Embodiment 2 of a service usage monitoring method provided by the present invention
  • Embodiment 3 is a flowchart of Embodiment 3 of a method for monitoring a service usage provided by the present invention
  • Embodiment 4 is a schematic structural diagram of Embodiment 1 of a service usage monitoring device provided by the present invention.
  • FIG. 5 is a schematic structural diagram of Embodiment 2 of a service usage monitoring device provided by the present invention.
  • FIG. 1 is a flowchart of Embodiment 1 of a service usage monitoring method provided by the present invention. As shown in FIG. 1, this embodiment includes:
  • Step 11 The PCEF obtains the quintuple information, the protocol information, and the information in the received service request information.
  • One of the URL information determines whether the service request information is the same as the specified service flow information in each session-level service monitoring task.
  • Each session-level service monitoring task includes a session-level service monitoring level identifier, a monitoring task identifier, and specified service flow information.
  • the session-level service monitoring level identifiers of the session-level service monitoring tasks are the same.
  • the monitoring task IDs of the session-level service monitoring tasks are different, and the corresponding specified service flow information is different.
  • the session-level service monitoring level identifier indicates that the monitoring task is used to monitor the usage of a specified service by a user in the current session.
  • the PCEF passes the monitoring task level identifier in the session-level service monitoring task, and it can be known that the PCRF indicates to monitor the usage of a specified service by a user in the current session.
  • each session-level service monitoring task is associated with the protocol, or there may be no association. For example, monitoring session-level service monitoring task A for a specific user to access www.sina.com within a session and monitoring session-level service monitoring task B for all HTTP protocol usage within that particular user session, since the user may use HTTP The agreement visits www.sina.com, so the business usage of www.sina.com should also be accumulated to the session-level business monitoring task B.
  • the PCEF When receiving the service request information in the current session, for example, receiving an HTTP browsing request, an RTSP service request, a short message service request, or a multimedia message service request, the PCEF first identifies the Port quintuple information and the uniform resource locator (Uniform) in the service request information. Resource Locator, called URL) Features such as information and protocol information. Further, one of the quintuple information, the protocol information, and the URL information in the comparison service request information is the same as one of the quintuple information, the protocol information, and the URL information corresponding to the specified service flow information; if the quintuple information, If the protocol information is the same as the URL information, the service request information is determined to be the same as the specified service flow information.
  • URL Resource Locator
  • the Port quintuple information identified from the service request information includes: a source IP address and a source port for sending the service request information. And receiving the destination IP address and the destination port of the service request information, and a protocol number corresponding to the protocol used to process the service request information.
  • Step 12 When determining that the service request information is the same as the specified service flow information in one or more session-level service monitoring tasks, the PCEF accumulates the usage of the service request information in one or more session-level service monitoring tasks.
  • Step 13 The PCEF reports the cumulative usage of the service request information in the monitoring task identifier and the session-level service monitoring task to the PCRF.
  • the service request information is obtained by using the monitoring task identifier corresponding to the monitoring task, that is, the monitoring task identifier corresponding to the specified service flow information.
  • the cumulative amount is reported to the PCRF. It is possible that the specified service flow information corresponding to the multiple session-level service monitoring services is the same as the service request information, and the usage of the service flow information (including the access duration, the access traffic, and the number of accesses, etc.) is respectively accumulated to the same designated service.
  • the session-level service monitoring task corresponding to the flow information is reported to the PCEF by the usage of the different monitoring task identifiers. PCEF reports an intra-session service
  • the amount of the PCRF is used to manage the amount of business reported by the PCEF.
  • the PCEF monitors multiple specified services in a session of a specific user according to multiple session-level service monitoring tasks delivered by the PCRF, and the service request information received in the session is five.
  • the tuple information, the protocol information, and the URL information are compared with the specified service flows corresponding to the session-level service monitoring tasks, and the specified service flow information that is the same as the service request information is determined.
  • the usage of the service request corresponding to the same specified service flow information is reported to the PCRF. Therefore, the embodiment of the present invention can accumulate the usage of a service flow to multiple PCR-level service monitoring tasks corresponding to the same specified service flow information, and overcome the problem that the PCEF cannot accumulate a service flow at most. Accurate defects are reported by the usage of the monitoring task, so that the PCRF can collect the accurate business usage of the user. Thereby controlling the subsequent quality of service.
  • FIG. 2 is a flowchart of Embodiment 2 of a service usage monitoring method provided by the present invention.
  • the PCRF sends a session-level service monitoring task to the PCEF through the Gx+ interface.
  • the usage-Monitoring-Level AVP definition is extended, and a monitoring level is added: SESSION_RULE_LEVEL(2).
  • the monitoring level identifier indicates that the delivered monitoring task is to monitor the usage of the specified service in a session.
  • a new [Session-Usage-Monitoring-Flows] AVP is added to indicate the specified service flow information to be monitored. details as follows:
  • this embodiment includes:
  • Step la The PCEF sends a session creation request to the PCRF through the CCR-Initial message.
  • the PCEF sends a session creation request based on a user, that is, a source IP address, to the PCRF through the CCR (Credit Control Request)-Initial message to request the PCRF to deliver a monitoring task for the user or the IP address. Therefore, after the user goes online, the PCEF monitors the specific service usage of the user according to the monitoring task delivered by the PCRF.
  • CCR Clear Control Request
  • Step 2a The PCRF sends two session-level service monitoring tasks to the PCEF through the GX CCA (Credit Control Answer) message.
  • GX CCA Greenit Control Answer
  • Each session-level service monitoring task includes monitoring level identification, monitoring task identification, and specified service flow information. For example, when the traffic of the user accessing the google website reaches a specified amount, the user reports that the traffic of the user uses the http protocol to reach the specified amount, and the PCRF sends the following two session-level service monitoring tasks to the PCEF (the brackets are actually sent). Value):
  • SESSION_RULE_LEVEL(2) indicates that the level of the monitoring task is level 2
  • Monitor-key (ml) indicates that the task ID of monitoring task A is ml
  • Monitor-key (m2) indicates that the task ID of monitoring task B is m2.
  • Granted-Service-Unit (3MB) indicates that the monitoring task A indicates that the amount of the specified service flow should be 3MB.
  • the flow-description (protocol: http) indicates that the specified service flow of the monitoring task B is the service flow using the http protocol.
  • the URL www.google.com.hk indicates that the specified service flow for monitoring task A is a service flow to www.google.com.hk.
  • Step 3a When receiving the service request information, the PCEF determines, according to one of the port quintuple information, the protocol information, and the URL information in the received service request information, whether the service request information is the same as the specified service flow information in each session-level service monitoring task. .
  • the PCEF can first identify the port quintuple information, URL information, and protocol information in the service request information through the deep packet inspection technology. Compare the characteristics of the quintuple information and the URL information in the service request information with the characteristics of the URL (www.google.com.hk) service indicated by [Session-Usage-Monitoring-Flows] in the monitoring task A, if two One of the information of the person is the same, indicating that the service request information is monitored. The service flow information is specified in task A. When the specified amount is 3 MB, the PCRF is sent to the Monitor-key (ml).
  • the PCEF can also match the characteristics of the quintuple information and the protocol information in the service request information with the characteristics of the Flow-Description (protocol: http) service flow indicated by the [Session-Usage-Monitoring-Flows] in the monitoring task B. If the information of the two is the same, it indicates that the service request information is the specified service flow information in the monitoring task B. When the specified usage is 3 MB, it is reported to the PCRF through the monitor-key (m2).
  • Step 4a When determining that the service request information is the same as the specified service flow information in one or more session-level service monitoring tasks, the PCEF accumulates the usage of the service request information in one or more session-level service monitoring tasks, and monitors the task identifier. The cumulative usage of the service request information in the session-level service monitoring task is reported to the PCRF.
  • the user accesses www.google.com.hk and uses 3MB of traffic.
  • the PCEF recognizes that the service flow is also a service flow using the http protocol, and reports it as follows:
  • PCEF will access by monitoring the task identifier ml
  • the service usage of the www.google.com.hk is reported to the PCRF by 3MB.
  • the PCEF reports the amount of the http traffic flow corresponding to the task ID m2 to the PCRF.
  • the above CCRU The content in parentheses in the information is the data value actually sent by the PCEF to the PCRF.
  • Step 5a The PCRF adjusts the session-level service monitoring task according to the service usage reported by the PCEF, and delivers a new session-level service monitoring task to the PCEF.
  • PCEF sends the traffic used by www.google.com.hk to the user on the PCRF and the traffic of the HTTP protocol in the session.
  • the PCRF accumulates the usage reported by the PCEF to the Google traffic. Control the quality of service on Google's website when a certain threshold is reached, and control the quality of service of a particular website when the HTTP service reaches a certain threshold.
  • FIG. 3 is a flowchart of Embodiment 3 of a method for monitoring service usage provided by the present invention.
  • the PCRF sends the monitoring level identifier and the monitoring task identifier in the session-level service monitoring task to the PCEF through the Gx+ interface, and delivers the session-level service to the PCEF through the newly added service flow synchronization interface.
  • the service flow synchronization interface needs to pass Monitor-key and flow-info. in the CCA message.
  • Flow-info includes Port quintuple and URL information.
  • this embodiment includes:
  • Step lb The PCEF sends a session creation request to the PCRF through the CCR-Initial message.
  • Step 2b The PCRF sends the monitoring level identifier and the monitoring task identifier in the two session-level service monitoring tasks to the PCEF through the GX CCA message.
  • the PCRF sends the monitoring task identifier and the specified service flow information in the session-level service monitoring task to the PCEF through the service flow synchronization interface. For example, send the following message: Flow-ID: ml; URL: www.google.com.hk; Flow-ID: m2; Protocol: http; Granted-Service-Unit: 3MB.
  • the PCRF When receiving the CCR-Initial message of the PCEF, the PCRF identifies the monitoring level and the monitoring task ID in the two session-level service monitoring tasks of the PCEF:
  • the specified service flow information received from the service flow synchronization interface can be associated with the SESSION_RULE_LEVEL(2) in the Usage-Monitoring-Information by the Monitor-key and the Usage-Monitoring-Information Monitor-key received from the service flow synchronization interface. So that you can get complete information about a monitoring task.
  • Step 3b When receiving the service request information, the PCEF determines, according to one of the port quintuple information, the protocol information, and the URL information in the received service request information, whether the service request information is the same as the specified service flow information in each session-level service monitoring task. .
  • Step 4b When determining that the service request information is the same as the specified service flow information in one or more session-level service monitoring tasks, the PCEF is accumulated in one or more session-level service monitoring tasks. The usage of the service request information is reported to the PCRF for the cumulative usage of the monitoring task identifier and the service request information in the session-level service monitoring task.
  • the user accesses www.google.com.hk and uses 3MB of traffic.
  • the PCEF recognizes that the service flow is also a service flow using the http protocol, and reports it as follows:
  • the above CCRU The content in parentheses in the information is the data value actually sent by the PCEF to the PCRF.
  • Step 5b The PCRF adjusts the session-level service monitoring task according to the service usage reported by the PCRF, and delivers a new session-level service monitoring task to the PCEF.
  • the PCEF sends the monitoring level identifiers of the session-level service monitoring tasks that are sent from the Gx+ interface to the PCEF through the PCRF, and learns that the multiple monitoring tasks that are currently delivered are session-level service monitoring tasks that monitor multiple specified service flows in a session. And the identification of the monitoring task.
  • the PCEF obtains the specified service flow information and the corresponding monitoring task identifier in each session-level service monitoring task sent by the PCRF through the service flow synchronization interface.
  • FIG. 4 is a schematic structural diagram of Embodiment 1 of a service usage monitoring device according to the present invention. As shown in Figure 4 The present embodiment includes: a determining module 41, an accumulating module 45, and a reporting module 42.
  • the determining module 41 is configured to determine, according to one of the quintuple information, the protocol information, and the URL information in the received service request information, whether the service request information is the same as the specified service flow information in one or more session-level service monitoring tasks;
  • the service monitoring task includes the session-level service monitoring level identifier, the monitoring task identifier, and the specified service flow information.
  • the level identifier indicates that the monitoring task is used to monitor the specified service usage in the session.
  • the determining module 41 may be specifically configured to determine whether one of the quintuple information, the protocol information, and the URL information in the service request information is the same as one of the quintuple information, the protocol information, and the URL information corresponding to the specified service flow information. If at least one of the quintuple information, the protocol information, and the URL information is the same, it is determined that the service request information is the same as the specified service flow information.
  • the accumulating module 45 is configured to accumulate usage of the service request information in one or more session-level service monitoring tasks when determining that the service request information is the same as the specified service flow information in one or more session-level service monitoring tasks.
  • the reporting module 42 is configured to report the cumulative usage of the service request information in the monitoring task identifier and the session-level service monitoring task to the policy and charging rule function entity PCRF.
  • the embodiment further includes: a session creation module 43 and a receiving module.
  • the session creation module 43 is configured to send a session creation request to the PCRF.
  • the receiving module 44 is configured to receive, by the PCRF, each session-level service monitoring task.
  • the receiving module 44 is specifically configured to receive, by using the Gx+ interface, each session-level service monitoring task sent by the PCRF.
  • the receiving module 44 is configured to receive, by using the Gx+ interface, a monitoring task level identifier and a task identifier of each session level monitoring task sent by the PCRF, and receive the information through the service flow information synchronization interface.
  • the PCEF monitors multiple specified services in a session of a specific user according to multiple session-level service monitoring tasks delivered by the PCRF, and uses the quintuple information and protocol in the service request information received in the session.
  • the information and the URL information are compared with the specified service flow corresponding to each session-level service monitoring task, and the specified service flow information that is the same as the service request information is determined.
  • the usage of the service request corresponding to the specified service flow information is reported to the PCRF. Therefore, the embodiment of the present invention can accumulate the usage of a service flow to multiple PCR-level service monitoring tasks corresponding to the same specified service flow information, and overcome the problem that the PCEF cannot accumulate a service flow at most. Accurate defects are reported by the usage of the monitoring task, so that the PCRF can collect the accurate business usage of the user. Thereby controlling the subsequent quality of service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

业务用量监控方法及 i殳备
本申请要求于 2010 年 12 月 31 日提交中国专利局、 申请号为 CN201010624359.8,发明名称为"业务用量监控方法及设备，，的中国专利申请 的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明实施例涉及通信技术， 尤其涉及一种业务用量监控方法及设备。 背景技术
IP网络可以提供更多种类的业务例如多媒体呼叫、 文件下载和网页浏览 等， 因此需要网络能够检测不同的业务流并统计流量、 时长等计费信息以上 报给计费中心。 3GPP、 微波存取全球互通 (Worldwide Interoperability for Microwave Access; 筒称 WiMAX) 论坛等组织定义了策略和计费控制基于策 略和计费控制 （Policy Charging Control, 筒称 PCC ) 架构， 通过 PCC架构可 以使得网络检测到不同的业务流， 并针对业务流实现服务质量（QoS )控制、 计费统计等需求。
PCC架构包括策略和计费加强功能实体（ Policy Charging Enforcement Function, 筒称 PCEF ) 和策略和计费规则功能实体 ( Policy Charging Rules Function, 筒称 PCRF )等功能实体。 PCEF支持对单独的业务流或者一组业 务流或会话内所有业务流的监听。 PCRF支持基于规则级及会话级的用量管 理， 并可利用 PCEF上报的用量动态控制带宽 /计费规则。 PCRF与 PCEF之间 采用 Gx接口进行策略下发及用量上报： PCEF通过 GX接口向 PCRF请求 PCC 规则， PCRF通过 GX接口向 PCEF提供 PCC规则， PCEF通过 GX接口向 PCRF 上报根据 PCC规则监控到的业务用量。
然而， 存在如下需求时现有用量监控机制无法满足： 例如需要监听特定 网站如新浪网站 www.sina.com的用量， 同时还需要监听用户在会话内所有 HTTP协议的用量， 以在新浪的访问量达到一定门限时控制其服务质量， 同 时当 HTTP业务达到一定门限时控制特定网站的服务质量。 若采用规则级监 控， PCEF在识别 www.sina.com的业务流时只会优先累计至一条规则， 该业 务流的用量或者上报至 HTTP协议对应的规则， 或者上报至 www. sina.com对 应的规则。这样另一条规则的用量不是完整的使用用量。若采用会话级监控， 由于会话级监控是对用户在会话内所有业务用量的监控，在会话内用户采用 任何协议访问任何网站都被累计至一条规则中上报给 PCRF, 从而不能区分 用户访问 www.sina.com的用量与使用 HTTP协议的用量。 因此， 目前 PCEF向 PCRF上报的业务用量不准确， 从而导致后续不能对其他业务的服务质量进 行准确控制。
发明内容
本发明实施例提供一种业务用量监控方法及设备， 用以解决现有技术中 PCEF向 PCRF上报的业务用量不准确的缺陷，达到了 PCRF准确采集用户业务 用量的目的。
本发明实施例提供一种业务用量监控方法， 包括：
根据接收到的业务请求信息中五元组信息、协议信息和 URL信息之一确 定所述业务请求信息是否与一个或者多个会话级业务监控任务中指定业务 流信息相同； 所述会话级业务监控任务包括会话级业务监控级别标识、 监控 任务标识和指定业务流信息； 所述监控级别标识表示所述监控任务用于监控 会话内指定业务流的用量；
在确定所述业务请求信息与所述一个或者多个会话级业务监控任务中 的所述指定业务流信息相同时，在所述一个或者多个会话级业务监控任务中 累计所述业务请求信息的用量；
将所述监控任务标识以及所述会话级业务监控任务中的所述业务请求 信息的累计用量上报给策略和计费规则功能实体。
本发明实施例提供一种业务用量监控设备， 包括：
确定模块， 用于根据接收到的业务请求信息中五元组信息、 协议信息和 URL信息之一确定所述业务请求信息是否与一个或者多个会话级业务监控 任务中指定业务流信息相同； 所述会话级业务监控任务包括会话级业务监控 级别标识、 监控任务标识和指定业务流信息； 所述监控级别标识表示所述监 控任务用于监控会话内指定业务流的用量；
累计模块， 用于在确定所述业务请求信息与所述一个或者多个会话级业 务监控任务中的所述指定业务流信息相同时， 在所述一个或者多个会话级业 务监控任务中累计所述业务请求信息的用量；
上报模块， 用于将所述监控任务标识以及所述会话级业务监控任务中的 所述业务请求信息的累计用量上报给策略和计费规则功能实体。
本发明实施例业务用量监控方法及设备， PCEF按照 PCRF下发的多个会 话级业务监控任务， 对一个特定用户一次会话内的多个指定业务进行监控， 将在会话内接收到的业务请求信息中五元组信息、协议信息和 URL信息与各 会话级业务监控任务对应的指定业务流进行比较，确定与业务请求信息相同 的指定业务流信息。 分别通过相同的指定业务流信息对应的监控任务标识， 将该业务请求对应的用量上报给 PCRF。 因此， 本发明实施例可将一条业务 流的用量分别累计至多个相同的指定业务流信息对应的多条会话级业务监 控任务中上报给 PCRF, 克服了由于 PCEF不能将一条业务流的用量累计至多 个监控任务而导致的用量上报准确的缺陷， 使 PCRF可采集到用户的准确的 业务用量。 从而控制后续的服务质量。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作一筒单地介绍， 显而易见地， 下 面描述中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在 不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明提供的业务用量监控方法实施例一流程图；
图 2为本发明提供的业务用量监控方法实施例二流程图；
图 3为本发明提供的业务用量监控方法实施例三流程图；
图 4本发明提供的业务用量监控设备实施例一结构示意图；
图 5本发明提供的业务用量监控设备实施例二结构示意图。
具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本发 明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于 本发明中的实施例， 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例， 都属于本发明保护的范围。 图 1为本发明提供的业务用量监控方法实施例一流程图。 如图 1所示， 本 实施例包括：
步骤 11 : PCEF根据接收到的业务请求信息中五元组信息、 协议信息和
URL信息之一确定业务请求信息是否与各会话级业务监控任务中指定业务 流信息相同。
PCEF向 PCRF发起 Gx+会话创建请求后， PCRF向 PCEF发送多个会话级 业务监控任务。 每个会话级业务监控任务包括会话级业务监控级别标识、 监 控任务标识和指定业务流信息。各会话级业务监控任务对应的会话级业务监 控级别标识相同， 各会话级业务监控任务对应的监控任务标识不同的， 对应 的指定业务流信息也不相同。会话级业务监控级别标识表示监控任务用于监 控一个用户在当前会话内指定业务的用量。 PCEF通过会话级业务监控任务 中的监控任务级别标识， 可获知 PCRF指示监控一个用户在当前会话内指定 业务的用量。
各会话级业务监控任务中对应的指定业务流信息在协议上存在关联，也 可以不存在关联。 例如， 监控一个特定用户在会话内访问 www.sina.com用量 的会话级业务监控任务 A和监控该特定用户会话内使用所有 HTTP协议的用 量的会话级业务监控任务 B , 由于用户有可能使用 HTTP协议访问 www.sina.com, 因此访问 www.sina.com的业务用量， 也应该累计至会话级业 务监控任务 B。 在当前会话内接收到业务请求信息时， 例如接收到 HTTP浏览请求、 RTSP业务请求、 短信业务请求或彩信业务请求等， PCEF先识别业务请求信 息中 Port五元组信息、统一资源定位符（ Uniform Resource Locator,筒称 URL ) 信息和协议信息等特征。 进一步的， 比较业务请求信息中五元组信息、 协议 信息和 URL信息之一， 是否分别与指定业务流信息对应的五元组信息、 协议 信息和 URL信息之一相同； 如果五元组信息、 协议信息和 URL信息中的至少 一项相同， 则确定业务请求信息与指定业务流信息相同从业务请求信息中识 别出的 Port五元组信息包括： 发送该业务请求信息的源 IP地址和源端口、 接 收该业务请求信息的目的 IP地址和目的端口以及处理该业务请求信息所采 用协议对应的协议号。
步骤 12: 在确定业务请求信息与一个或者多个会话级业务监控任务中的 指定业务流信息相同时， PCEF在一个或者多个会话级业务监控任务中累计 业务请求信息的用量。
步骤 13： PCEF将监控任务标识以及会话级业务监控任务中的业务请求 信息的累计用量上报给 PCRF。
在某个会话级业务监控任务对应的指定业务流信息与业务请求信息相 匹配时， 通过该监控任务对应的监控任务标识， 也即该指定业务流信息对应 的监控任务标识， 将该业务请求信息的累计用量上报给 PCRF。 有可能存在 多个会话级业务监控业务对应的指定业务流信息与该业务请求信息相同， 将 该业务流信息的用量（包括访问时长、 访问流量和访问次数等） ， 分别累计 至相同的指定业务流信息所对应的会话级业务监控任务， 并分别通过不同的 监控任务标识将该业务请求的用量上报给 PCEF。 PCEF上报一次会话内业务 的用量， PCRF对 PCEF上报的业务用量进行累计管理。
本发明实施例业务用量监控方法， PCEF按照 PCRF下发的多个会话级业 务监控任务， 对一个特定用户一次会话内的多个指定业务进行监控， 将在会 话内接收到的业务请求信息中五元组信息、协议信息和 URL信息与各会话级 业务监控任务对应的指定业务流进行比较，确定与业务请求信息相同的指定 业务流信息。 分别通过相同的指定业务流信息对应的监控任务标识， 将该业 务请求对应的用量上报给 PCRF。 因此， 本发明实施例可将一条业务流的用 量分别累计至多个相同的指定业务流信息对应的多条会话级业务监控任务 中上报给 PCRF, 克服了由于 PCEF不能将一条业务流的用量累计至多个监控 任务而导致的用量上报准确的缺陷， 使 PCRF可采集到用户的准确的业务用 量。 从而控制后续的服务质量。
图 2为本发明提供的业务用量监控方法实施例二流程图。 本实施例中， PCRF通过 Gx+接口向 PCEF下发会话级业务监控任务。
本实施例对 Usage-Monitoring-Level AVP定义进行了扩展，新增一个监控 级别： SESSION_RULE_LEVEL(2) , 该监控级别标识表示下发的监控任务为 监控 一 次 会话 内 指 定 业 务 的 用 量 。 另 外 ， 还新 增 加 [Session-Usage-Monitoring-Flows] AVP, 指示需监控的指定业务流信息。 具 体如下：
<CC-Answer>：: =
[Session-Usage-Monitoring-Flows]
[ Monitoring-Key] 〃监控任务标识
[ Flow-Information ] //指定业务流信息 在[ Flow-Information ]处， 也可为 [ URL ] , 表示监控访问特定 URL的业 务流。
如图 2所示， 本实施例包括：
步骤 la: PCEF通过 CCR-Initial消息向 PCRF发送会话创建请求。
PCEF通过 CCR ( Credit Control Request ) -Initial消息向 PCRF发送基于一 个用户也即一个源 IP地址的会话创建请求， 以请求 PCRF下发对于该用户或 该 IP地址的监控任务。 从而该用户上线后 PCEF根据 PCRF下发的监控任务对 该用户的特定业务用量进行监控。
步骤 2a: PCRF通过 GX CCA ( Credit Control Answer)消息向 PCEF下发两 个会话级业务监控任务。
每个会话级业务监控任务包括监控级别标识、监控任务标识和指定业务 流信息。 例如， 监控用户访问 google网站的流量达到指定量时上报， 并监控 该用户使用 http协议的流量达到指定量时上报， PCRF向 PCEF下发如下两个 会话级业务监控任务 (括号内容为实际发送的值)：
CCA::=
Usage-Monitoring-Information II监控任务 A
SESSION_RULE_LEVEL(2)
Monitor-key(ml )
Usage-Monitoring-Information II监控任务 B
SESSION_RULE_LEVEL(2)
Monitor-key(m2)
[Session-Usage-Monitoring-Flows] Monitor-key(ml )
Granted-Service-Unit (3MB)
URL(www . google . com. hk)
[Session-Usage-Monitoring-Flows]
Monitor-key(m2)
Granted-Service-Unit (3MB)
Flow-Description(protocol:http)
在上述消息内容中 SESSION_RULE_LEVEL(2)表示监控任务的级别标 识为 2级， Monitor-key(ml)表示监控任务 A的任务标识为 ml , Monitor-key (m2)表示监控任务 B的任务标识为 m2; Granted-Service-Unit (3MB)表示监控任务 A指示上报指定业务流时应达到的用量为 3MB； Flow-Description(protocol:http)表示监控任务 B的指定业务流为使用 http协议 的业务流； URL(www.google.com.hk) 表示监控任务 A的指定业务流为访问 www.google.com.hk的业务流。
步骤 3a: PCEF接收到业务请求信息时， 根据接收到的业务请求信息中 port五元组信息、 协议信息和 URL信息之一确定业务请求信息是否与各会话 级业务监控任务中指定业务流信息相同。
承上的两个会话级业务监控任务， PCEF可以先通过深度报文检测技术 识别出业务请求信息中 port五元组信息、 URL信息和协议信息等特征。 将业 务请求信息中五元组信息和 URL信息等特征与监控任务 A中 [Session-Usage-Monitoring-Flows]所指示的 URL(www. google. com.hk)业务 ¾ΐ 的特征进行比较， 若两者的各信息中有一项相同表明该业务请求信息为监控 任务 A中指定业务流信息， 在达到指定用量 3MB时， 通过 Monitor-key(ml)上 艮给 PCRF。 同时， PCEF还可以将将业务请求信息中五元组信息和协议信息 等特征与 监控任务 B 中 [Session-Usage-Monitoring-Flows] 指 示 的 Flow-Description(protocol:http) 业务流的特征进行匹配， 若两者的各信息中 有一项相同表明该业务请求信息为监控任务 B中指定业务流信息， 在达到指 定用量 3MB时， 通过 Monitor-key(m2)上报给 PCRF。
步骤 4a: 在确定业务请求信息与一个或者多个会话级业务监控任务中的 指定业务流信息相同时， PCEF在一个或者多个会话级业务监控任务中累计 业务请求信息的用量，将监控任务标识以及会话级业务监控任务中的业务请 求信息的累计用量上报给 PCRF。
用户访问 www.google.com.hk使用了 3MB流量， PCEF识别该业务流还属 于使用 http协议的业务流， 则通过如下方式上报：
CCRU::=
Usage-Monitoring-Information
Monitor-key(ml )
Used-Service-Unit
CC-Total-Octets(3mb)
Usage-Monitoring-Information
Monitor-key(m2)
Used-Service-Unit
CC-Total-Octets(3MB)
在以上 CCRU:消息中 ， PCEF通过监控任务标识 ml将访问 www.google.com.hk的业务用量 3MB上报至 PCRF, PCEF通过监控任务标识 m2对应的 http业务流信息访问用量 3MB上报至 PCRF。 以上 CCRU:信息中括 号中内容为 PCEF向 PCRF实际发送的数据值。
步骤 5a: PCRF根据 PCEF上报的业务用量调整会话级业务监控任务， 并 向 PCEF下发新的会话级业务监控任务。
PCEF向 PCRF上 4艮一次会话内该用户访问 www.google.com.hk使用的流 量和一次会话内该用户使用 HTTP协议的流量， PCRF对 PCEF上报的用量进 行累计管理， 以在谷歌的访问量达到一定门限时控制谷歌网站的服务质量， 同时当 HTTP业务达到一定门限时控制特定网站的服务质量。
图 3为本发明提供的业务用量监控方法实施例三流程图。 本实施例与上 述实施例的区别在于， PCRF只通过 Gx+接口向 PCEF下发会话级业务监控任 务中的监控级别标识和监控任务标识， 通过新增加的业务流同步接口向 PCEF下发会话级业务监控任务中指定业务流信息。 业务流同步接口需要传 递 CCA 消息中 Monitor-key和 flow-info.。 flow-info包括 Port五元组和 URL信 息。
如图 3所示， 本实施例包括：
步骤 lb: PCEF通过 CCR-Initial消息向 PCRF发送会话创建请求。
步骤 2b: PCRF通过 GX CCA消息向 PCEF下发两个会话级业务监控任务 中的监控级别标识和监控任务标识。
例如， 需要监控用户访问 google网站及使用 http协议的流量， PCRF通过 业务流同步接口将会话级业务监控任务中的监控任务标识和指定业务流信 息承载在 SOAP消息上发送给 PCEF。 例如， 发送如下信息： Flow-ID: ml ; URL: www.google.com.hk; Flow-ID: m2; Protocol: http; Granted-Service-Unit: 3MB。
当接收到 PCEF的 CCR-Initial消息时， PCRF向 PCEF两个会话级业务监控 任务中的监控级别标识和监控任务标识：
CCA::=
Usage-Monitoring-Information
SESSION_RULE_LEVEL(2)
Monitor-key(ml )
Usage-Monitoring-Information
SESSION_RULE_LEVEL(2)
Monitor-key(m2)
在以上 CCA消息中只下发 Usage-Monitoring-Information中相关信息， 而 没有下发 [Session-Usage-Monitoring-Flows] 中信息。通过从业务流同步接口 接收到的 Monitor-key和 Usage-Monitoring-Information中 Monitor-key , 可将从 业务流同步接口接收到的指定业务流信息与 Usage-Monitoring-Information中 SESSION_RULE_LEVEL(2)进行关联，从而可获取到一个监控任务的完整信 息。
步骤 3b: PCEF接收到业务请求信息时， 根据接收到的业务请求信息中 port五元组信息、 协议信息和 URL信息之一确定业务请求信息是否与各会话 级业务监控任务中指定业务流信息相同。
步骤 4b: 在确定业务请求信息与一个或者多个会话级业务监控任务中的 指定业务流信息相同时， PCEF在一个或者多个会话级业务监控任务中累计 业务请求信息的用量，将监控任务标识以及会话级业务监控任务中的业务请 求信息的累计用量上报给 PCRF。
用户访问 www.google.com.hk使用了 3MB流量， PCEF识别该业务流还属 于使用 http协议的业务流， 则通过如下方式上报：
CCRU::=
Usage-Monitoring-Information
Monitor-key(ml )
Used-Service-Unit
CC-Total-Octets(3mb)
Usage-Monitoring-Information
Monitor-key(m2)
Used-Service-Unit
CC-Total-Octets(3mb)
以上 CCRU:信息中括号中内容为 PCEF向 PCRF实际发送的数据值。 步骤 5b: PCRF根据 PCRF上报的业务用量调整会话级业务监控任务， 并 向 PCEF下发新的会话级业务监控任务。
PCEF通过 PCRF从 Gx+接口下发的各会话级业务监控任务中监控级别标 识， 获知当前下发的多个监控任务为对一个用户一次会话内多个指定业务流 信息进行监控的会话级业务监控任务以及监控任务的标识。 PCEF通过业务 流同步接口获取 PCRF发下发的各会话级业务监控任务中的指定业务流信息 和相应的监控任务标识。
图 4为本发明提供的业务用量监控设备实施例一结构示意图。 如图 4所 示， 本实施例包括： 确定模块 41、 累计模块 45和上报模块 42。
确定模块 41 , 用于根据接收到的业务请求信息中五元组信息、 协议信息 和 URL信息之一确定业务请求信息是否与一个或者多个会话级业务监控任 务中指定业务流信息相同； 会话级业务监控任务包括会话级业务监控级别标 识、 监控任务标识和指定业务流信息； 级别标识表示监控任务用于监控会话 内指定业务用量。
进一步的， 确定模块 41可以具体用于确定业务请求信息中五元组信息、 协议信息和 URL信息之一， 是否分别与指定业务流信息对应的五元组信息、 协议信息和 URL信息之一相同； 如果五元组信息、 协议信息和 URL信息中的 至少一项相同， 则确定业务请求信息与指定业务流信息相同。
累计模块 45 , 用于在确定业务请求信息与一个或者多个会话级业务监控 任务中的指定业务流信息相同时， 在一个或者多个会话级业务监控任务中累 计业务请求信息的用量。
上报模块 42, 用于述监控任务标识以及会话级业务监控任务中的业务请 求信息的累计用量上报给策略和计费规则功能实体 PCRF。
进一步， 在图 4基础上， 本实施例还包括： 会话创建模块 43和接收模块
44。
会话创建模块 43， 用于向 PCRF发送会话创建请求。
接收模块 44, 用于接收 PCRF发送各会话级业务监控任务。
其中，接收模块 44具体用于通过 Gx+接口接收 PCRF发送的各会话级业务 监控任务。或者，接收模块 44具体用于通过 Gx+接口接收 PCRF发送的各会话 级监控任务的监控任务级别标识和任务标识， 通过业务流信息同步接口接收 PCRF发送的各会话级监控任务的指定业务流信息和监控任务标识。
上述各模块的工作机理参见图 1至图 3对应实施例中描述， 在此不再赘 述。
本发明实施例 PCEF按照 PCRF下发的多个会话级业务监控任务， 对一个 特定用户一次会话内的多个指定业务进行监控，将在会话内接收到的业务请 求信息中五元组信息、协议信息和 URL信息与各会话级业务监控任务对应的 指定业务流进行比较， 确定与业务请求信息相同的指定业务流信息。 分别通 过相同的指定业务流信息对应的监控任务标识，将该业务请求对应的用量上 报给 PCRF。 因此， 本发明实施例可将一条业务流的用量分别累计至多个相 同的指定业务流信息对应的多条会话级业务监控任务中上报给 PCRF, 克服 了由于 PCEF不能将一条业务流的用量累计至多个监控任务而导致的用量上 报准确的缺陷， 使 PCRF可采集到用户的准确的业务用量。 从而控制后续的 服务质量。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的 介质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种业务用量监控方法， 其特征在于， 包括：
根据接收到的业务请求信息中五元组信息、协议信息和 URL信息之一确 定所述业务请求信息是否与一个或者多个会话级业务监控任务中指定业务 流信息相同； 所述会话级业务监控任务包括会话级业务监控级别标识、 监控 任务标识和指定业务流信息； 所述监控级别标识表示所述监控任务用于监控 会话内指定业务流的用量；
在确定所述业务请求信息与所述一个或者多个会话级业务监控任务中 的所述指定业务流信息相同时，在所述一个或者多个会话级业务监控任务中 累计所述业务请求信息的用量；
将所述监控任务标识以及所述会话级业务监控任务中的所述业务请求 信息的累计用量上报给策略和计费规则功能实体。
2、 根据权利要求 1所述业务用量监控方法， 其特征在于， 所述根据接收 到的业务请求信息中五元组信息、协议信息和 URL信息之一确定所述业务请 求信息是否与各会话级业务监控任务中指定业务流信息相同， 包括：
确定所述业务请求信息中五元组信息、协议信息和 URL信息之一是否分 别与所述指定业务流信息对应的五元组信息、 协议信息和 URL信息之一相 同； 如果所述五元组信息、 协议信息和 URL信息中的至少一项相同， 则确定 所述业务请求信息与所述指定业务流信息相同。
3、 根据权利要求 1或 2所述业务用量监控方法， 其特征在于， 在所述确 定所述业务请求信息是否与各会话级业务监控任务中指定业务流信息相同 之前， 还包括： 向所述策略和计费规则功能实体发送会话创建请求；
接收所述策略和计费规则功能实体发送的各所述会话级业务监控任务。
4、 根据权利要求 3所述业务用量监控方法， 其特征在于， 接收所述策略 和计费规则功能实体发送的所述会话内的各所述会话级业务监控任务具体 为：
通过 Gx+接口接收策略和计费规则功能实体发送的各所述会话级业务监 控任务。
5、 根据权利要求 3所述业务用量监控方法， 其特征在于， 还包括： 接收 通过 Gx+接口接收策略和计费规则功能实体发送的所述会话级业务监控 任务中监控任务级别标识和监控任务标识，通过业务流信息同步接口接收所 述策略和计费规则功能实体发送中各所述会话级监控任务的指定业务流信 息和监控任务标识。
6、 一种业务用量监控设备， 其特征在于， 包括：
确定模块， 用于根据接收到的业务请求信息中五元组信息、 协议信息和
URL信息之一确定所述业务请求信息是否与一个或者多个会话级业务监控 任务中指定业务流信息相同； 所述会话级业务监控任务包括会话级业务监控 级别标识、 监控任务标识和指定业务流信息； 所述监控级别标识表示所述监 控任务用于监控会话内指定业务流的用量；
累计模块， 用于在确定所述业务请求信息与所述一个或者多个会话级业 务监控任务中的所述指定业务流信息相同时， 在所述一个或者多个会话级业 务监控任务中累计所述业务请求信息的用量； 上报模块， 用于将所述监控任务标识以及所述会话级业务监控任务中的 所述业务请求信息的累计用量上报给策略和计费规则功能实体。
7、 根据权利要求 6所述业务用量监控设备， 其特征在于， 所述确定模块 具体用于确定所述业务请求信息中五元组信息、协议信息和 URL信息之一是 否分别与所述指定业务流信息对应的五元组信息、协议信息和 URL信息之一 相同； 如果所述五元组信息、 协议信息和 URL信息中的至少一项相同， 则确 定所述业务请求信息与所述指定业务流信息相同。
8、 根据权利要求 6或 7所述业务用量监控设备， 其特征在于， 还包括： 会话创建模块， 用于向所述策略和计费规则功能实体发送会话创建请 求；
接收模块， 用于接收所述策略和计费规则功能实体发送的各所述会话级 业务监控任务。
9、 根据权利要求 8所述业务用量监控设备， 其特征在于， 所述接收模块 具体用于通过 Gx+接口接收策略和计费规则功能实体发送的各所述会话级业 务监控任务。
10、 根据权利要求 8所述业务用量监控设备， 其特征在于， 所述接收模 块具体用于通过 Gx+接口接收策略和计费规则功能实体发送的各所述会话级 业务监控任务中监控任务级别标识和监控任务标识， 通过业务流信息同步接 口接收所述策略和计费规则功能实体发送的各所述会话级监控任务中指定 业务流信息和监控任务标识。
PCT/CN2011/079313 2010-12-31 2011-09-05 业务用量监控方法及设备 WO2012088919A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
RU2012147778/08A RU2523962C2 (ru) 2010-12-31 2011-09-05 Способ и устройство для контроля объема пользования услугами
EP11853578.0A EP2587737B1 (en) 2010-12-31 2011-09-05 Method and device for monitoring service traffic
CN201180001626.9A CN102439907B (zh) 2010-12-31 2011-09-05 业务用量监控方法及设备
US13/690,044 US9172760B2 (en) 2010-12-31 2012-11-30 Method and device for monitoring service usage amount

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010624359.8A CN102142990B (zh) 2010-12-31 2010-12-31 业务用量监控方法及设备
CN201010624359.8 2010-12-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/690,044 Continuation US9172760B2 (en) 2010-12-31 2012-11-30 Method and device for monitoring service usage amount

Publications (1)

Publication Number Publication Date
WO2012088919A1 true WO2012088919A1 (zh) 2012-07-05

Family

ID=44410232

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079313 WO2012088919A1 (zh) 2010-12-31 2011-09-05 业务用量监控方法及设备

Country Status (5)

Country Link
US (1) US9172760B2 (zh)
EP (1) EP2587737B1 (zh)
CN (1) CN102142990B (zh)
RU (1) RU2523962C2 (zh)
WO (1) WO2012088919A1 (zh)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102142990B (zh) * 2010-12-31 2016-11-02 华为技术有限公司 业务用量监控方法及设备
CN103200231B (zh) * 2013-03-04 2016-07-20 华为技术有限公司 策略控制方法及系统
US9501378B2 (en) * 2014-01-01 2016-11-22 Bank Of America Corporation Client events monitoring
CN104955013A (zh) * 2014-03-26 2015-09-30 中兴通讯股份有限公司 用量监控方法、装置和系统
EP2953333A1 (en) * 2014-06-02 2015-12-09 Alcatel Lucent Multiple validity time management
RU2668293C2 (ru) * 2014-06-03 2018-09-28 Телефонактиеболагет Лм Эрикссон (Пабл) Упреждающий кредитный контроль
CN106358232A (zh) * 2015-07-14 2017-01-25 中国移动通信集团公司 蜂窝网中业务速率监测方法、装置和系统
CN106937323B (zh) * 2015-12-30 2021-03-30 华为技术有限公司 一种用户终端数量的监控方法及相关设备
CN108476388B (zh) * 2015-12-31 2020-08-07 华为技术有限公司 处理数据包的方法及装置
CN106445667A (zh) * 2016-09-27 2017-02-22 西安交大捷普网络科技有限公司 提高审计架构cpu负载均衡的实现方法
US10872023B2 (en) * 2017-09-24 2020-12-22 Microsoft Technology Licensing, Llc System and method for application session monitoring and control
WO2019206191A1 (en) * 2018-04-28 2019-10-31 Telefonaktiebolaget Lm Ericsson (Publ) QoS FLOW CONTROL PARAMETERS SIGNALING
CN115225544A (zh) * 2022-07-19 2022-10-21 武汉思普崚技术有限公司 一种网络流量统计和监测方法、装置、电子设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1889475A (zh) * 2006-07-31 2007-01-03 南京信风软件有限公司 一种实时监控p2p应用所消耗带宽的方法
CN1925423A (zh) * 2005-08-30 2007-03-07 飞塔信息科技（北京）有限公司 具有对网络流量进行解析功能的日志装置、系统与方法
CN101465763A (zh) * 2008-12-30 2009-06-24 上海地面通信息网络有限公司 用户端网络设备流量监控及分析的方法
CN102142990A (zh) * 2010-12-31 2011-08-03 华为技术有限公司 业务用量监控方法及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030027566A1 (en) 2001-07-30 2003-02-06 Comverse Network Systems, Ltd. Session management method & system
DE102004009289A1 (de) * 2004-02-26 2005-09-15 Siemens Ag Verfahren zur Steuerung und Auswertung eines Nachrichtenverkehrs einer Kummunikationseinheit durch eine erste Netzwerkeinheit innerhalb eines Mobilfunksystems, sowie dazugehörige Kommunikationseinheit und erste Netzwerkeinheit
AU2006267255B2 (en) * 2005-07-07 2010-03-04 Nokia Technologies Oy Handover method and apparatus between different systems
CN101296169B (zh) 2007-04-26 2010-12-08 华为技术有限公司 一种用户会话承载业务建立方法、系统及设备
CN101325780B (zh) 2007-06-15 2010-07-07 华为技术有限公司 策略控制实现方法和系统、及策略和计费执行实体
US8467367B2 (en) * 2007-08-06 2013-06-18 Qualcomm Incorporated Multiplexing and transmission of traffic data and control information in a wireless communication system
CN101232386B (zh) 2008-02-20 2011-04-20 中兴通讯股份有限公司 一种统计彩信流量的方法
US9858559B2 (en) * 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
WO2011020498A1 (en) * 2009-08-18 2011-02-24 Telefonaktiebolaget Lm Ericsson (Publ) Method, apparatus and computer program for enforcing policy across associated sessions taking into account a total usage quota for associated user

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1925423A (zh) * 2005-08-30 2007-03-07 飞塔信息科技（北京）有限公司 具有对网络流量进行解析功能的日志装置、系统与方法
CN1889475A (zh) * 2006-07-31 2007-01-03 南京信风软件有限公司 一种实时监控p2p应用所消耗带宽的方法
CN101465763A (zh) * 2008-12-30 2009-06-24 上海地面通信息网络有限公司 用户端网络设备流量监控及分析的方法
CN102142990A (zh) * 2010-12-31 2011-08-03 华为技术有限公司 业务用量监控方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2587737A4 *

Also Published As

Publication number Publication date
EP2587737B1 (en) 2016-08-24
CN102142990B (zh) 2016-11-02
CN102142990A (zh) 2011-08-03
US9172760B2 (en) 2015-10-27
EP2587737A1 (en) 2013-05-01
US20130091276A1 (en) 2013-04-11
EP2587737A4 (en) 2013-11-20
RU2523962C2 (ru) 2014-07-27
RU2012147778A (ru) 2014-05-20

Similar Documents

Publication Publication Date Title
WO2012088919A1 (zh) 业务用量监控方法及设备
US11330409B2 (en) Method for processing rate group, method for charging for data service, and related device and system
US8594621B2 (en) Usage sharing across fixed line and mobile subscribers
JP5468180B2 (ja) サービス要求に基づいてｐｃｃルールを生成するためのシステムおよび方法
US9860752B2 (en) Handling of authorization requests for a packet-based service in a mobile network
KR101425327B1 (ko) 다이어미터 세션 검사
JP5855268B2 (ja) ポリシー制御装置を使用するネットワーク統計の生成
US9641346B2 (en) Method and apparatus for performing charging control to application-layer data
EP3331263B1 (en) Policy decision method and charging device
US9450767B2 (en) PCRF and PCC rule setting method in a mobile communication network
WO2011079773A1 (zh) 用户会话策略控制方法、装置及系统
KR101884048B1 (ko) 네트워크 자원들을 관리하기 위한 방법들과 노드들, 및 상응하는 시스템과 컴퓨터 프로그램
US8897749B1 (en) Policy decisions based on subscriber spending limits
WO2008128470A1 (fr) Procédé, système et entité de réalisation de détection d&#39;événement
JP2016509789A5 (zh)
JP2017514338A (ja) 課金セッション管理方法および装置
WO2014172858A1 (zh) 一种进行应用计费的方法、计费设备和系统
WO2011120378A1 (zh) 对用户业务的数据流进行控制的方法和装置
WO2013091410A1 (zh) 网络接入方法、系统及设备
US9654574B2 (en) Methods and apparatuses for determining a user identity token for identifying user of a communication network
JP2018512760A (ja) サービス処理方法、ｐｃｒｆ、及びサービス処理システム
WO2015058549A1 (zh) 业务同步方法、内容管理设备及策略管理设备
WO2016109970A1 (zh) 网络实体及服务策略管理方法
WO2017092442A1 (zh) 策略和计费控制快速调整方法、装置及系统
US20240137276A1 (en) Controlling User Plane Function (UPF) Load

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001626.9

Country of ref document: CN

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

Ref document number: 11853578

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2011853578

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011853578

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2012147778

Country of ref document: RU

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE