WO2006015542A1 - Procede de reduction de la charge d'un tpf - Google Patents

Procede de reduction de la charge d'un tpf Download PDF

Info

Publication number
WO2006015542A1
WO2006015542A1 PCT/CN2005/001230 CN2005001230W WO2006015542A1 WO 2006015542 A1 WO2006015542 A1 WO 2006015542A1 CN 2005001230 W CN2005001230 W CN 2005001230W WO 2006015542 A1 WO2006015542 A1 WO 2006015542A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
tpf
charging rule
information
indication
Prior art date
Application number
PCT/CN2005/001230
Other languages
English (en)
French (fr)
Inventor
Yajuan Wu
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to BRPI0508482-2A priority Critical patent/BRPI0508482A/pt
Priority to AT05772878T priority patent/ATE454765T1/de
Priority to EP05772878A priority patent/EP1777871B1/en
Priority to CA2555254A priority patent/CA2555254C/en
Priority to DE602005018784T priority patent/DE602005018784D1/de
Publication of WO2006015542A1 publication Critical patent/WO2006015542A1/zh
Priority to US11/497,687 priority patent/US7957719B2/en
Priority to US13/099,742 priority patent/US8238873B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • 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
    • 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/1485—Tariff-related aspects
    • 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
    • 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/43—Billing software details
    • 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/62—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • 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/67—Transmitting arrangements for sending billing related information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M17/00—Prepayment of wireline communication systems, wireless communication systems or telephone systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/14—Billing aspects relating to the actual charge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/204—UMTS; GPRS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/48—Sending information over a non-traffic network channel or another connection than the one actually used, e.g. signalling, D-channel, data and voice

Definitions

  • the present invention relates to the field of charging technology for packet radio services, and more particularly to a method for mitigating the load of a transport plane functional entity (TPF).
  • TPF transport plane functional entity
  • the current GPRS network can only recognize the access point name (APN) and the packet data protocol context (PDP Context) level for the user data stream, but in reality, multiple service data streams in parallel (for a packet data service)
  • the amount of data consumed by the user to use the service is called Service Data Flow.
  • a service data stream is composed of multiple packet data streams, that is, IP data streams.
  • a PDP context can carry multiple different services. It is possible to use the same PDP Context bearer, and different services may use different charging methods.
  • 3GPP proposes a new GPRS bearer charging structure, that is, a method based on Traffic Based Charging (FBC). Obviously, the service data flow based charging granularity is smaller than the PDP context based charging granularity, so that operators and service providers can adopt richer charging means.
  • FBC Traffic Based Charging
  • Figure 1 is a schematic diagram of the structure of the FBC system supporting online charging, including the online charging system (OCS), the charging rule function entity (CRF), and the transmission surface functional entity ( TPF), Application Function Entity (AF), and Charging Gateway Function Entity/Charging Collection Function Entity (CGF/CCF).
  • OCS online charging system
  • CRF charging rule function entity
  • TPF transmission surface functional entity
  • AF Application Function Entity
  • CGF/CCF Charging Gateway Function Entity/Charging Collection Function Entity
  • 2 is a schematic structural diagram of an FBC system supporting offline charging, It mainly includes CRF, TPF, AF and CGF/CCF.
  • the TPF is a functional entity that carries a packet data stream, and can distinguish between packets belonging to different service data flows.
  • the TPF requests the charging rule from the CRF through the Gx interface.
  • the request may carry: information related to the user and the terminal, such as the mobile station international ISDN number MSISDN, the international mobile device identity and the service version number IMEISV; bearer characteristics, such as QoS information; network related information, such as mobile network coding MNC, mobile country Code MCC.
  • the TPF performs packet filtering and charging operations on the corresponding service data flow according to the charging rule information returned by the CRF.
  • the charging operation may be to collect and generate charging information, and report the generated charging information. Series and billing related actions.
  • a TPF can be served by one or more CRFs. Specifically, which CRF is provided as a server according to the identification information of the UE; and the TPF supports predefined charging rules and predefined filters.
  • CRP is a functional entity that maintains charging rules and supports dynamic and static charging rules.
  • dynamic refers to the generation of some charging rule data in real time according to the service criteria.
  • static means that the charging rules are static in the process of using the data service, and the static charging rules can be activated by the dynamic charging rules.
  • the CRF can select the appropriate charging rule to send the selected charging rule to the TPF when the TPF request or a scheduled event is triggered.
  • a CRF can correspond to multiple TPFs at the same time, that is, provide services for multiple TPFs.
  • AF stands for all functional entities related to the application, either the carrier's own or a third-party service provider.
  • the AF provides the corresponding information to the CRF, so that the CRF can select or configure the corresponding charging rule.
  • the corresponding information provided by the AF includes: the identification information of the service data flow, the identification information can be the wildcard identification information; Information; Application/Service Identity; Application/Service Charging Rules Trigger Events; Stream Types, such as Video, Audio; Stream Rate. Among them, stream type and stream rate are optional.
  • An AF can correspond to multiple CRFs.
  • the AF can select which CRF to interact with based on the identification information of the UE.
  • the OCS is used to perform the function of online charging, which includes a functional entity CC for performing credit control.
  • the CC is only used in the online charging system, and the OCS provides the CRF with input information for selecting the charging rule through the Ry interface. .
  • the CCF/CGF is used to further process the reported charging data from the TPF to generate a bill.
  • the above FBC system structure is applicable to different access wireless technologies, such as 3GPP, 3GPP2, and WLAN and other network structures.
  • the bearer network is a GPRS network
  • the TPF is located at the GGSN
  • the AF is a service gateway or a service server in the packet data network (PDN)
  • IMS IP Multimedia Subsystem
  • AF is the proxy CSCF (P-CSCF)
  • CRF is the new logical entity.
  • Figure 3 shows the flow chart for offline charging. Specifically, the following steps are included:
  • Steps 301 to 302 The UE sends a bearer setup request message to the TPF. After receiving the bearer setup request, the TPF sends the charging rule request information to the CRF. Step 303 to step 304, the CRF selects the charging rule according to the received charging rule request from the TPF. Of course, if there is input information for determining the charging rule from the AF and/or the OCS, the CRF comprehensively receives the received information. The charging rule request from the TPF, the input information from the AF and/or the OCS for determining the charging rule, the charging rule is selected, and then the selected charging rule is sent to the TPF.
  • the charging rule can include the following items: Specify the charging mode of the service data flow, such as specifying online charging or offline charging, and recording the offline charging, such as recording according to traffic, duration, and traffic and duration. Key, business data stream filter, priority, and billing rule ID.
  • the filter is used to distinguish packet data packets belonging to a specific service data flow, and the basic composition is an IP quintuple, including a source IP address, a destination IP address, a source port number, a destination port number, a transmission protocol number, or an application.
  • the protocol number is used to determine the rate; the priority is used to determine which charging rule to apply when the charging rules overlap; the charging rule identifier is used to identify a specific charging rule, and is mainly used for CRF.
  • step 305 to step 306 the TPF performs a corresponding operation, such as applying or deleting a charging rule, according to the operation instruction of the received charging rule, and then sends a response to the UE that the bearer is successfully established.
  • a corresponding operation such as applying or deleting a charging rule
  • the billing information is generated, and the generated billing information is submitted to the billing related function entity to generate the final bill of the user according to a certain format, for example, a call detail record (CDR, Call Detail Record).
  • CDR Call Detail Record
  • FIG. 4 shows a flow chart of online charging, which specifically includes the following steps:
  • Step 401 to step 402 the UE sends a bearer setup request message to the TPF, and the TPF receives After the bearer setup request, the charging rule request information is sent to the CRF.
  • Step 403 to step 404 the CRF selects the charging rule according to the received charging rule request from the TPf.
  • the CRF comprehensively receives the input.
  • the charging rule request from the TPF the input information from the AF and/or the OCS for determining the charging rule, the charging rule is selected, and then the selected charging rule is sent to the TPF.
  • the charging rule can include the following items: Specify the charging mode of the service data flow, such as specifying online charging or offline charging, and recording the offline charging, such as recording according to traffic, duration, and traffic and duration. Key, business data stream filter, priority, and billing rule ID.
  • Step 405 The TPF performs a corresponding operation, such as applying or deleting a charging rule, according to an operation instruction of the received charging rule.
  • Steps 409 to 410 After receiving the success response of the bearer setup, the UE performs the traffic data transmission.
  • the TPF performs the charging operation after performing the filtering operation on the service data flow to which the charging rule is applied and the statistical operation is performed.
  • the billing information is collected and generated, and the generated billing information is submitted to the billing related functional entity to generate the final bill of the user according to a certain format, for example, after the CDR is filled.
  • the charging information collected and reported by the TPF may not necessarily be generated. End user bills are helpful.
  • online charging is used.
  • the OCS monitors the user's account in real time, and then sends the generated charging information to the charging related functional entity to generate the final bill of the user.
  • the TPF also collects the available billing information and reports it to the billing related functional entity. Since the TPF does not have the account information of the user, the collected charging information is not comprehensively collected by the OCS, and when the TPF and the OCS belong to the same network, the charging information of the user reported by the TPF is useless, even if it is sent.
  • the billing related function entity will also be discarded. In this case, it will increase the load of the TPF device.
  • the operator may not charge the user for operational considerations or for promotion of the service, but according to the existing service data flow-based implementation architecture, even if the user is not charged, the network's medium TPF device is also To collect, generate, and report billing information, these billing information must be sent to the billing related functional entity until it is billed. To a certain extent, this is also a waste of network resources. Summary of the invention
  • the main object of the present invention is to provide a method for mitigating TPF load to optimize the operation of the TPF and reduce the load on the network device.
  • a method for mitigating a TPF load of a transport plane functional entity is applicable to a system for charging based on a data stream, the method comprising the following steps:
  • the transmission plane function entity TPF obtains an indication of whether to perform the charging operation according to the received charging rule information from the charging rule function entity CRF, and determines the content of the indication. If the charging operation is performed, the service data flow is performed. After the filtering is performed, the charging information is collected and generated, and the generated charging information is reported. If the charging operation is not performed, the service data stream is filtered, and the operation ends.
  • the charging rule information received by the TPF from the CRF includes a specific charging rule, and the specific charging rule includes an indication field for performing a charging operation.
  • the process of the TPF obtaining whether to perform the charging operation indication is: directly obtaining an indication of whether to perform the charging operation from the specified field in the received specific charging rule.
  • the charging rule information received by the TPF from the CRF includes one or more specific charging rules and indication information related to whether the charging operation is performed in association with the charging rule;
  • the process of obtaining the charging operation indication by the TPF is: directly obtaining the indication information of whether the charging operation is performed from the directly received charging rule information, and obtaining an indication of whether to perform the charging operation from the indication information.
  • the charging rule information received by the TPF from the CRF includes an identifier of the charging rule and a field for indicating whether the charging operation is performed;
  • the process of the TPF obtaining whether to perform the charging operation indication is: directly obtaining an indication of whether to perform the charging operation from the specified field in the received charging rule information.
  • the charging rule information received by the TPF from the CRF is obtained. Contains the identifier of the charging rule;
  • the process of obtaining the charging operation indication by the TPF is: the TPF obtains the locally stored charging rule according to the received charging rule identifier, and according to the indication information of whether the charging operation is performed corresponding to the charging rule, Obtain an indication of whether to perform a billing operation.
  • the CRF determines the charging rule information based on the received charging rule request from the TPF.
  • the CRF determines the charging rule according to the received charging rule request from the TPF.
  • the method further includes: the CRF receiving input information for determining the charging rule from the online charging system OCS and/or the application function entity AF, synthesizing the charging rule request from the TPF, and using the OCS and/or the AF
  • the charging rule information is determined by determining input information of the charging rule.
  • the TPF determines, according to the obtained indication of whether the charging operation is performed, whether to perform a charging operation on the service data flow to which the corresponding charging rule is applied, and if so, the service data flow.
  • the accounting information is collected and generated, and then reported to the charging related functional entity. Otherwise, only the service data flow is filtered, and the charging operation is not performed. Therefore, the operation of the TPF is optimized, so that the TPF only needs to perform the necessary charging operation, and does not perform the charging operation on the service data flow that does not need to be charged, thereby reducing the burden of the TPF, thereby reducing the load on the network device and improving the system. s efficiency. At the same time, it avoids the waste of network resources due to the implementation of various billing strategies by operators. BRIEF DESCRIPTION OF THE DRAWINGS
  • Figure 1 is a schematic diagram of the structure of an FBC system supporting online charging.
  • Figure 2 is a schematic diagram showing the structure of an FBC system supporting offline charging.
  • FIG. 3 is a flow chart of an offline charging method based on the FBC system in the prior art.
  • FIG. 4 is a flow chart of an online charging method based on the FBC system in the prior art.
  • FIG. 5 is a flowchart of an FBC online charging method according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of an FBC offline charging method according to an embodiment of the present invention. Mode for carrying out the invention
  • the main idea of the present invention According to the obtained indication of whether the charging operation is performed by the TPF, Whether the charging operation is performed on the service data flow to which the corresponding charging rule is applied, that is, whether the charging operation is collected and performed, and then the charging information is reported. That is, if the indication of whether the charging operation is performed by the TPF indicates that the charging operation is to be performed, the TPF needs to collect the information related to the charging after performing the filtering operation on the service data flow to which the charging rule is applied. And generating the charging information, and then reporting the generated charging information; if the indication of whether the charging operation is performed by the TPF indicates that the charging operation is not performed, the TPF only applies the service data of the charging rule. After the flow performs the filtering operation, it is not necessary to perform the collection and generate the accounting information, and the operation of reporting the charging information.
  • the CRF determines, according to the network-related information in the charging rule request message reported by the TPF, such as the mobile country code MCC and the mobile network code MNC, that the user and the TPF belong to the same operating network, and the user is a prepaid user.
  • the charging method for all services is online charging. Therefore, the CRF decides to control the TPF to not perform charging operations for the user.
  • the indication of whether the charging operation is performed is carried in the selected charging rule and sent to the TPF. All billing information is collected by OCS.
  • the flowchart of the method in this embodiment is shown in FIG. 5, and specifically includes the following steps:
  • step 501 to step 502 the UE sends a bearer setup request message to the TPF.
  • the TPF After receiving the bearer setup request, the TPF sends the charging rule request information to the CRF.
  • the CRF selects a charging rule according to the received charging rule request from the TPF.
  • the TPF performs a corresponding operation, such as applying or deleting a charging rule, according to an operation instruction of the received charging rule.
  • step 506 to step 508 the TPF sends the credit request information to the OCS, and the OCS provides the relevant credit to the TPF, and then the TPF sends a response to the UE that the bearer is successfully established.
  • step 509 to step 510 after receiving the success response of the bearer setup, the UE performs service data transmission.
  • the value of the indication field of the charging operation in the charging rule does not perform the charging operation.
  • the TPF directly obtains the indication that the charging operation is not performed, the TPF only counts and counts the service data flows to which the charging rule is applied, that is, only performs the filtering operation, and does not perform the collection, generation, and reporting. The operation of the fee information.
  • the CRF may only issue the meter in the foregoing steps 503 to 504.
  • the charging rule corresponding to the charging rule is identified to the TPF, and the TPF obtains the locally stored charging rule according to the received charging rule identifier, performs the corresponding operation according to the operation instruction of the charging rule, and according to the corresponding charging rule Whether the indication information of the charging operation is performed, whether an indication of whether the charging operation is performed is obtained, thereby determining whether to collect, generate, and report the charging information to the charging related functional entity.
  • the user's online service charging method is monthly subscription, so the operator will charge the user regardless of whether the user uses the service within one month, how long the service is used, and the amount of service data. cost of.
  • the charging system may choose not to perform the charging operation, and the user uses the bearer to occur. All fees can be charged in other ways.
  • the flowchart of the method in this embodiment is as shown in FIG. 6, and specifically includes the following steps:
  • step 601 to step 602 the UE sends a bearer setup request message to the TPF.
  • the TPF After receiving the bearer setup request, the TPF sends the charging rule request information to the CRF.
  • the CRF selects a charging rule according to the received charging rule request from the TPF.
  • the CRF comprehensive receiving The charging rule request from the TPF, the input information from the AF and/or the OCS for determining the charging rule, the charging rule is selected, and the value of the charging operation indication is set to not generated, and then The indication of the charging operation is associated with the selected one or more charging rules, and is sent to the TPF in parallel.
  • the indication of whether or not to perform the charging operation does not perform the charging operation. That is to say, the charging rule information sent by the CRF is one or more charging rules, and indication information that is not associated with the one or more charging rules and does not perform charging operations.
  • step 605 to step 606 the TPF performs an operation, such as applying or deleting a charging rule, according to an operation instruction of the received charging rule, and sends a response to the UE that the bearer is successfully established.
  • an operation such as applying or deleting a charging rule, according to an operation instruction of the received charging rule, and sends a response to the UE that the bearer is successfully established.
  • the UE After receiving the success response of the bearer setup, the UE performs the service data transmission.
  • the indication of the charging operation indicates that the charging operation is not performed. Therefore, the TPF directly from the charging rule information. After obtaining the indication that the charging operation is not performed, only the service data flow to which the charging rule is applied is counted and counted, that is, only the filtering operation is performed, and the operations of collecting, generating, and reporting the charging information are not performed.
  • the CRF may only issue these accounting items.
  • the charging rule corresponding to the charging rule is identified to the TPF, and the TPF obtains the locally stored charging rule according to the received charging rule identifier, performs the corresponding action according to the operation instruction of the charging rule, and according to the corresponding charging rule Whether to enter
  • the indication information of the line charging operation is used to obtain an indication of whether to perform the charging operation, thereby determining whether to collect, generate, and report the charging information to the charging related functional entity.
  • the CRF can be simultaneously sent.
  • the charging rule identifiers corresponding to the charging rules and the indications of whether the service data flows of the charging rules are used for the charging operation are sent to the TPF, that is, the charging rule information delivered by the CRF includes the charging.
  • the rule identifies the field of the charging operation indication, and the TPF finds the corresponding charging rule according to the charging rule identifier, performs the corresponding operation, such as the action of applying or deleting, and the charging rule information according to the operation instruction of the charging rule.
  • the specified field in the field obtains an indication of whether to perform the charging operation, thereby determining whether to collect, generate, and report the charging information to the charging related functional entity.
  • the information sent by the CRF in the prior art only indicates whether the TPF performs online charging or offline charging, and does not indicate whether the TPF performs a charging operation, and the indication added by the present invention indicates whether the TPF is The charging operation is performed.
  • the charging operation is not performed, it means that the TPF only performs the filtering operation, and neither performs online charging nor performs offline charging.
  • the charging operation is, the implementation of collecting, generating, and reporting the charging information.
  • the charging operation may be determined according to the operator's policy. Under what circumstances, the charging operation is not performed, thereby more effectively reducing the load of the TPF and avoiding waste of network resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Meter Arrangements (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Inorganic Compounds Of Heavy Metals (AREA)
  • Separation By Low-Temperature Treatments (AREA)
  • Filtering Of Dispersed Particles In Gases (AREA)
  • Treating Waste Gases (AREA)

Description

一种减轻传输面功能实体负荷的方法 技术领域
本发明涉及分组无线业务的计费技术领域， 特别是指一种减轻传输 面功能实体 ( TPF ) 负荷的方法。 发明背景
随着通用分组无线业务（GPRS )应用范围的不断扩大， 对移动分组 数据业务进行准确合理地计费， 已成为移动运营商普遍关注的课题。
目前的 GPRS网络针对用户数据流只能识别到接入点名称（APN ) 和分组数据协议上下文（PDP Context )这一级别， 然而现实中并行的多 个业务数据流（对于一个分组数据业务来说， 用户使用该项业务所消耗 的数据量称为业务数据流 Service Data Flow, 一个业务数据流是由多个 分组数据流， 即 IP数据流组成的， 一个 PDP context可以承载多个不同 的业务）很可能使用同一个 PDP Context承载， 且不同业务可能采用不 同的计费方式。 针对上述情况， 3GPP提出了一种新的 GPRS承载计费 结构， 即采用一种基于业务数据流计费 （FBC, Flow Based Charging ) 的方法。 显然， 基于业务数据流的计费粒度小于基于 PDP context的计 费粒度， 从而使得运营商以及业务提供商能够采取更为丰富的计费手 段。
下面根据协议 3GPP TS23.125, 对上述 FBC进行描述。 FBC的系统 结构如图 1、 2所示，其中图 1为支持在线计费的 FBC系统结构示意图， 主要包括在线计费系统（OCS )、 计费规则功能实体（CRF )、 传输面功 能实体（TPF )、 应用功能实体（AF ) 以及计费网关功能实体 /计费收集 功能实体（CGF/CCF )。 图 2为支持离线计费的 FBC系统结构示意图， 主要包括 CRF、 TPF、 AF以及 CGF/CCF。
下面基于上述 FBC系统结构，对组成计费系统的各功能实体分别进 行说明。
1、 TPF
TPF是承载分组数据流的功能实体， 可以区分属于不同业务数据流 的分组包， 当承载发生变化时， 比如承载的建立， 修改和删除过程中， TPF通过 Gx接口向 CRF请求计费规则， 该请求中可以携带： 用户和终 端相关的信息， 如移动台国际 ISDN号码 MSISDN、 国际移动设备标识 及服务版本号 IMEISV; 承载特性， 如 QoS信息； 网络相关的信息， 如 移动网编码 MNC,移动国家码 MCC。 TPF根据 CRF返回的计费规则信 息， 在对应的业务数据流上执行分组过滤和计费操作， 该计费操作可以 是收集并生成计费信息， 并将所生成的计费信息进行上报等一系列和计 费有关的动作。
一个 TPF可以由一个或者多个 CRF为其提供服务， 具体的， 根据 UE的标识信息来选择由哪个 CRF为其提供服务器； 并且 TPF支持预定 义的计费规则以及预定义的过滤器。
2、 CRP
CRP是保存计费规则的功能实体， 支持动态和静态的计费规则。 所 谓动态是指根据业务准则实时生成一些计费规则数据； 所谓静态是指在 用户使用数据业务过程中计费规则是一成不变的， 静态计费规则可以由 动态计费规则激活。 CRF可根据接收到的来自 TPF、 AF以及 OCS的输 入信息， 选取适当的计费规则， 在 TPF请求或者有预定事件触发时将选 取的计费规则发送给 TPF 。
一个 CRF可以同时对应多个 TPF, 即为多个 TPF提供服务。 AF代表所有和应用相关的功能实体,可以是运营商自己的，也可以 是第三方业务提供商的。 AF向 CRF提供相应的信息，使得 CRF可以选 择或配置相应的计费规则， AF提供的相应信息包括： 业务数据流的标 识信息， 该标识信息可以是通配的标识信息； 计费规则选择的信息； 应 用 /业务标识； 应用 /业务计费规则触发事件； 流类型， 如视频、 音频； 流速率。 其中， 流类型和流速率是可选项。
一个 AF可以对应多个 CRF。 AF可以根据 UE的标识信息选择与哪 个 CRF进行交互。
4、 OCS
OCS用于执行在线计费的功能， 其内包含用于执行信用控制的功能 实体 CC, 通常 CC只用于在线计费系统内， OCS通过 Ry接口向 CRF 提供用于选择计费规则的输入信息。
5、 CCF/CGF
CCF/CGF用于对来自 TPF的上报的计费数据做进一步处理， 以生 成帐单。
上述 FBC系统结构适用于不同的接入无线技术， 如 3GPP, 3GPP2 以及 WLAN等网络结构。 以 3GPP为例， 如果承载网络是 GPRS网络， 则 TPF位于 GGSN处， AF为分组数据网 （PDN ) 中的一个业务网关或 是业务服务器， 当 IP多媒体子系统（ IMS )承载在 GPRS网络之上时， AF就是代理 CSCF ( P-CSCF ), 此时， CRF为新增的逻辑实体。
下面基于上述 FBC系统结构，以离线计费和在线计费的实现流程为 例说明 TPF所执行的操作。
图 3所示为离线计费的流程图。 具体包括如下步驟：
步驟 301〜步驟 302, UE向 TPF发送建立承载请求消息， TPF接收 到承载建立请求后， 向 CRF发送计费规则请求信息。 步骤 303〜步骤 304, CRF根据接收到的来自 TPF的计费规则请求， 选择计费规则， 当然， 如果有来自 AF和 /或 OCS的用于确定计费规则 的输入信息， 则 CRF综合接收到的来自 TPF的计费规则请求， 来自 AF 和 /或 OCS的用于确定计费规则的输入信息， 选择计费规则， 之后， 将 选取的计费规则下发给 TPF。 计费规则中可以包括以下内容： 指定业务 数据流的计费方式，如指定在线计费或离线计费， 离线计费的记录方式， 如按流量、 时长以及流量和时长进行记录等， 计费键， 业务数据流过滤 器， 优先级以及计费规则标识。
其中， 过滤器， 用于区分属于一个特定业务数据流的分组数据包， 其基本构成是 IP五元组， 包括源 IP地址， 目的 IP地址， 源端口号， 目 的端口号， 传输协议号或者应用协议号； 计费键， 用于确定费率； 优先 级， 用于当计费规则重叠时， 确定应用哪一个计费规则； 计费规则标识， 用于标识特定计费规则， 主要用于 CRF向 TPF下发计费规则时， 如果 TPF中已经储存有相应的计费规则， CRF就没有必要每次下发完整的计 费规则给 TPF，而只需将对应于该计费规则的计费规则标识下发给 TPF。
步驟 305~步骤 306， TPF根据接收到的计费规则的操作指示， 执行 相应操作， 如应用或删除计费规则等， 然后向 UE发送承载建立成功的 响应。
步骤 307〜步骤 308, UE接收到承载建立成功响应后， 进行业务数 据传输， TPF对应用该计费规则的业务数据流进行计数以及统计操作， 即执行过滤操作之后， 执行计费操作， 即收集并生成计费信息， 并将所 生成计费信息按照一定的格式， 如填成呼叫细节记录（CDR, Call Detail Record )后， 上报给计费相关功能实体以生成用户的最终话单。
图 4所示为在线计费的流程图， 具体包括如下步骤：
步骤 401〜步骤 402, UE向 TPF发送建立承载请求消息， TPF接收 到承载建立请求后， 向 CRF发送计费规则请求信息。
步骤 403〜步骤 404, CRF根据接收到的来自 TPf 的计费规则请求， 选择计费规则， 当然， 如果有来自 AF和 /或 OCS的用于确定计费规则 的输入信息， 则 CRF综合接收到的来自 TPF的计費规则请求， 来自 AF 和 /或 OCS的用于确定计费规则的输入信息， 选择计费规则， 之后， 将 选取的计费规则下发给 TPF。 计费规则中可以包括以下内容： 指定业务 数据流的计费方式，如指定在线计费或离线计费， 离线计费的记录方式， 如按流量、 时长以及流量和时长进行记录等， 计费键， 业务数据流过滤 器， 优先级以及计费规则标识。
步骤 405, TPF根据接收到的计费规则的操作指示， 执行相应操作， 如应用或删除计费规则等。
步骤 406〜步骤 408, TPF向 OCS发送信用请求信息， OCS向 TPF 提供与该用户相关信用信息，然后 TPF向 UE发送承载建立成功的响应。
步骤 409〜步骤 410, UE接收到承载建立成功响应后， 进行业务数' 据传输， TPF对应用该计费规则的业务数据流进行计数以及统计操作即 执行过滤操作之后， 执行计费操作， 即收集并生成计费信息， 并将所生 成计费信息按照一定的格式， 如填成 CDR后， 上报给计费相关功能实 体以生成用户的最终话单。
从上述离线计费流程中的步驟 307〜步骤 308以及在线计费流程的步 骤 409〜步骤 410中可以看出， TPF对经过的业务数据流进行过滤后， 会 生成计费信息， 然后对生成的计费信息按照一定的格式上报给计费相关 功能实体以生成最终的话单。 所述计费相关功能实体可包括计费网关 ( CG )和收费系统（BS )，由 CG对收到的计费信息进行合并后送至 BS, 由 BS生成最终的话单。
然而在实际应用中， TPF收集和上报的计费信息， 不一定都对生成 最终用户话单有帮助。 例如， 当用户应用某业务时使用在线计费 , 根据 在线计费的实现， OCS会对用户的帐户进行实时监控， 然后将产生的计 费信息送给计费相关功能实体产生用户的最终话单， 而与此同时， TPF 也收集了能够得到的计費信息并上报给计费相关功能实体。由于 TPF没 有用户的帐户信息， 所以收集的计费信息没有 OCS 收集的计费信息全 面， 而且当 TPF和 OCS归属于同一网络时， TPF上报的用户的计费信 息亳无用处， 即使被送到计费相关功能实体， 也会被丢弃， 在这种情况 下 , 无异于白白增加了 TPF设备的负荷。
此外， 某些情况下运营商出于运营考虑或者出于推广业务考虑， 可 能不对用户计费， 但是按照现有的基于业务数据流的实现架构， 即使不 对用户计费， 网络的中 TPF设备也要收集、 产生和上报计费信息， 这些 计费信息要一直送到计费相关功能实体， 在出帐单时才被丟弃掉， 在一 定程度上这也是对网络资源的浪费。 发明内容
有鉴于此， 本发明的主要目的在于提供一种减轻 TPF负荷的方法， 以优化 TPF的操作， 减轻网络设备的负荷。
为达到上述目的， 本发明的技术方案是这样实现的：
一种减轻传输面功能实体 TPF负荷的方法， 适用于基于数据流进行 计费的系统中， 该方法包括以下步骤：
传输面功能实体 TPF根据接收到的来自计费规则功能实体 CRF的 计费规则信息， 获取是否进行计费操作的指示， 并判断该指示的内容， 如果是进行计费操作， 则对业务数据流进行过滤后， 收集并生成计费信 息， 然后将所生成的计费信息进行上报， 如果是不进行计费操作， 则对 业务数据流进行过滤后， 结束操作。 较佳地， 所述 TPF接收到的来自 CRF的计费规则信息中包含具体 的计费规则， 且该具体的计费规则内包含是否进行计费操作的指示字 段；
所述 TPF获取是否进行计费操作指示的过程为： 从接收到的具体计 费规则中的指定字段内直接获取是否进行计费操作的指示。
较佳地， 所述 TPF接收到的来自 CRF的计费规则信息中包含一条 或一条以上具体的计费规则以及与所述计费规则相关联的是否进行计 费操作的指示信息；
所述 TPF获取是否进行计费操作指示的过程为： 从直接接收到的计 费规则信息中直接获取是否进行计费操作的指示信息 , 并从该指示信息 内获取是否进行计费操作的指示。
较佳地， 当所述 TPF内预先存储有具体的计费规则时， 所述 TPF接 收到的来自 CRF 的计费规则信息中包含计费规则的标识以及是否进行 计费操作指示的字段；
所述 TPF获取是否进行计费操作指示的过程为： 从接收到的计费规 则信息中的指定字段内直接获取是否进行计费操作的指示。
较佳地， 当所述 TPF内预先存储有具体的计费规则， 和对应所述计 费规则的是否进行计费操作指示的对应关系时，所述 TPF接收到的来自 CRF的计费规则信息中包含计费规则的标识；
所述 TPF获取是否进行计费操作指示的过程为： TPF根据接收到的 计费规则标识， 获取本地存储的计费规则， 并根据与该计费规则对应的 是否进行计费操作的指示信息， 获取是否进行计费操作的指示。
较佳地， CRF根据接收到的来自 TPF的计费规则请求， 确定计费规 则信息。
较佳地， CRF根据接收到的来自 TPF的计费规则请求确定计费规则 信息之前， 进一步包括: CRF接收来自在线计费系统 OCS和 /或应用功 能实体 AF的用于确定计费规则的输入信息， 综合来自 TPF的计费规则 请求， 以及来自 OCS和 /或 AF的用于确定计费规则的输入信息， 确定 计费规则信息。
综上所述， 在本发明方法中， TPF根据获取的是否进行计费操作的 指示， 确定是否对应用相应计费规则的业务数据流进行计费操作， 如果 是, 则对该业务数据流的进行过滤操作后， 收集并生成计费信息， 进而 上报给计费相关功能实体， 否则只对该业务数据流的进行过滤操作， 不 进行计费操作。从而优化了 TPF的操作，使得 TPF只需执行必要的计费 操作，而对不必计费的业务数据流不进行计费操作，减轻了 TPF的负担， 进而减轻了网絡设备的负荷， 提高了系统的效率。 同时， 避免了由于运 营商实施多种多样的计费策略，如采用免费策略时，对网络资源的浪费。 附图简要说明
图 1为支持在线计费的 FBC系统结构示意图。
图 2为支持离线计费的 FBC系统结构示意图。
图 3为现有技术中基于 FBC系统的离线计费方法流程图。
图 4为现有技术中基于 FBC系统的在线计费方法流程图。
图 5为本发明实施例的 FBC在线计费方法流程图。
图 6为本发明实施例的 FBC离线计费方法流程图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚， 下面结合附图对本 发明作进一步的详细描述。
本发明的主要思想： TPF根据获取的是否进行计费操作的指示， 确 定是否对应用相应计费规则的业务数据流进行计费操作， 即是否收集并 进行计费操作， 进而上报计费信息。 也就是说， 如果 TPF所获取的是否 进行计费操作的指示表明要进行计费操作，则说明 TPF对应用该计费规 则的业务数据流执行过滤操作后， 还需收集与计费相关的信息， 并生成 计费信息， 然后将所生成的计费信息进行上报； 如果 TPF所获取的是否 进行计费操作的指示表明不进行计费操作，则说明 TPF只对应用该计费 规则的业务数据流执行过滤操作后， 不需要再执行收集并生成计费信 息， 以及上报计费信息的操作。
下面结合具体实施例进一步说明本发明。
本实施例中， CRF根据 TPF上报的计费规则请求消息中的网络相关 信息， 如移动国家码 MCC和移动网编码 MNC, 判断自己和 TPF属于 同一运营网络中， 而且该用户是预付费用户， 其所有业务的计费方式都 是在线计费， 因此， CRF决定控制 TPF对该用户不进行计费操作。 本例 中将是否进行计费操作的指示携带在选取的计费规则当中下发给 TPF。 所有计费信息都由 OCS收集。本实施例的方法流程图如图 5所示，具体 包括如下步骤：
在步骤 501〜步骤 502, UE向 TPF发送建立承载请求消息， TPF接 收到承载建立请求后， 向 CRF发送计费规则请求信息。
在步骤 503〜步骤 504, CRF根据接收到的来自 TPF的计费规则请求， 选择计费规则， 当然， 如果有来自 AF和 /或 OCS的用于确定计费规则 的输入信息， 则 CRF综合接收到的来自 TPF的计费规则请求， 来自 AF 和 /或 OCS的用于确定计费规则的输入信息， 选择计费规则， 并将是否 进行计费操作指示的值设为不进行计费操作， 然后携带在选取的计费规 则中下发给 TPF。 即本例中， CRF下发的计费规则信息为具体的计费规 则， 且是否进行计费操作指示作为计费规则中的一个字段。 在步骤 505 , TPF根据接收到的计费规则的操作指示， 执行相应操 作， 如应用或删除计费规则等。
在步骤 506〜步骤 508, TPF向 OCS发送信用请求信息， OCS向 TPF 提供相关信用， 然后 TPF向 UE发送承载建立成功的响应。
在步骤 509〜步骤 510, UE接收到承载建立成功响应后， 进行业务 数据传输， 本例中， 由于计费规则中的是否进行计费操作的指示字段的 值为不进行计费操作， 因此， TPF从计费规则中直接获取该不进行计费 操作的指示后， 只对应用该计费规则的业务数据流进行计数及统计操 作， 即只执行过滤操作， 不再执行收集、 生成并上报计费信息的操作。
如果 TPF中已经存储有某些计费规则， 同时设置了对应用这些计费 规则的业务数据流是否进行计费操作的指示，那么在上述步驟 503〜步骤 504中， CRF可以只下发该计费规则对应的计费规则标识给 TPF, TPF 根据接收到的计费规则标识， 获取本地存储的计费规则， 按照计费规则 的操作指示， 执行相应操作， 同时根据与该计费规则对应的是否进行计 费操作的指示信息，获取是否进行计费操作的指示，从而决定是否收集、 生成并上报计费信息给计费相关功能实体。
下面通过一个实施例说明本发明的另一种实现方法。 考虑到一类业 务或者一个用户的一个连接上可能应用的计费规则不止一条， 但是凡是 属于这类业务或者该用户的业务数据流都可以不进行计费操作， 这时是 否进行计费操作指示就可以同时应用在多条计费规则上， 因此可以将该 是否进行计费操作的指示与多条计费规则相关联， 并列下发给 TPF。
在本实施例中， 用户的上网业务计费方式为包月计费， 那么不论该 用户在一个月内是否使用该业务、 使用多长时间以及业务数据量有多 少， 运营商都会向该用户收取固定的费用。 在这种情况下， 对于该用户 使用的业务， 计费系统可以选择不进行计费操作， 该用户使用承载发生 的所有费用可以通过其他方式来收取。 本实施例的方法流程图如图 6所 示， 具体包括如下步骤：
在步骤 601〜步骤 602, UE向 TPF发送建立承载请求消息， TPF接 收到承载建立请求后， 向 CRF发送计费规则请求信息。
在步骤 603〜步骤 604 , CRF根据接收到的来自 TPF的计费规则请求， 选择计费规则， 当然， 如果有来自 AF和 /或 OCS的用于确定计费规则 的输入信息， 则 CRF综合接收到的来自 TPF的计费规则请求， 来自 AF 和 /或 OCS的用于确定计费规则的输入信息， 选择计费规则， 并将是否 进行计费操作指示的值设为不产生， 然后将是否进行计费操作的指示与 选取的一条或多条计费规则相关联， 并列下发给 TPF。 本例中， 该是否 进行计费操作的指示的指明不进行计费操作。 也就是说， CRF所下发的 计费规则信息是一条或多条计费规则， 以及与该一条或多条计费规则相 关联的不进行计费操作的指示信息。
在步骤 605〜步驟 606, TPF根据接收到的计费规则的操作指示， 执 行操作，如应用或删除计费规则等， 并向 UE发送承载建立成功的响应。
在步骤 607〜步骤 608, UE接收到承载建立成功响应后， 进行业务 数据传输，本例中， 由于是否进行计费操作的指示指明不进行计费操作， 因此， TPF从计费规则信息中直接获取该不进行计费操作的指示后， 只 对应用该计费规则的业务数据流进行计数及统计操作， 即只执行过滤操 作， 不再执行收集、 生成以及上报计费信息的操作。
如果 TPF中已经存储有某些计费规则， 同时设置了对应用这些计费 规则的业务数据流是否进行计费操作的指示， 那么在上述步驟 603 ~步 骤 604中， CRF可以只下发这些计费规则对应的计费规则标识给 TPF, TPF根据接收到的计费规则标识， 获取本地存储的计费规则， 按照计费 规则的操作指示， 执行相应动作， 同时根据与该计费规则对应的是否进 行计费操作的指示信息， 获取是否进行计费操作的指示， 从而决定是否 收集、 生成并上报计费信息给计费相关功能实体。
在图 5和图 6的实现过程中，如果 TPF中已经存储有某些计费规则， 但是没有设置对应用这些计费规则的业务数据流是否进行计费操作的 指示，那么 CRF可以同时下发与这些计费规则相对应的计费规则标识和 应用这些计费规则的业务数据流是否进行计费操作的指示给 TPF, 也就 是说，此时 CRF下发的计费规则信息中包含计费规则标识和是否进行计 费操作指示的字段， TPF根据计费规则标识找到对应的计费规则， 按照 计费规则的操作指示， 执行相应操作， 如应用或者删除的动作， 同时从 计费规则信息中的指定字段内获取是否进行计费操作的指示， 从而决定 是否收集、 生成并上报计费信息送给计费相关功能实体。
可见， 在现有技术中 CRF下发的信息中仅是指示 TPF是执行在线 计费还是离线计费， 并不指示 TPF是否进行计费操作， 而本发明所增加 的指示所指明的是 TPF是否进行计费操作， 当然， 如不进行计费操作， 也就意味着 TPF仅执行过滤操作， 而既不需要执行在线计费， 也不需要 执行离线计费。
以上所述只是让 TPF不执行计费操作， 即不执行收集、 生成并上报 计费信息的几种实施例， 在实际应用中可根据运营商的策略决定， 在什 么情况下进行计费操作， 在什么情况下不进行计费操作， 从而更有效地 减轻 TPF的负荷， 避免网络资源的浪费。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、 一种减轻传输面功能实体 TPF 负荷的方法， 适用于基于数据流 进行计费的系统中， 其特征在于， 该方法包括以下步驟：
传输面功能实体 TPF根据接收到的来自计费规则功能实体 CRF的 计费规则信息， 获取是否进行计费操作的指示， 并判断该指示的内容， 如果是进行计费操作， 则对业务数据流进行过滤后， 收集并生成计费信 息， 然后将所生成的计费信息进行上报， 如果是不进行计费操作， 则对 业务数据流进行过滤后， 结束操作。
2、 根据权利要求 1所述的方法， 其特征在于， 所述 TPF接收到的 来自 CRF的计费规则信息中包含具体的计费规则，且该具体的计费规则 内包含是否进行计费操作的指示字段；
所述 TPF获取是否进行计费操作指示的过程为： 从接收到的具体计 费规则中的指定字段内直接获取是否进行计费操作的指示。
3、 根据权利要求 1所述的方法， 其特征在于， 所述 TPF接收到的 来自 CRF 的计费规则信息中包含一条或一条以上具体的计费规则以及 与所述计费规则相关联的是否进行计费操作的指示信息；
所述 TPF获取是否进行计费操作指示的过程为： 从直接接收到的计 费规则信息中直接获取是否进行计费操作的指示信息， 并从该指示信息 内获取是否进行计费操作的指示。
4、 根据权利要求 1所述的方法， 其特征在于， 当所述 TPF内预先 存储有具体的计费规则时， 所述 TPF接收到的来自 CRF的计费规则信 息中包含计费规则的标识以及是否进行计费操作指示的字段；
所述 TPF获取是否进行计费操作指示的过程为： 从接收到的计费规 则信息中的指定字段内直接获取是否进行计费操作的指示。
5、 根据权利要求 1所述的方法, 其特征在于, 当所述 TPF内预先 存储有具体的计费规则， 和对应所述计费规则的是否进行计费操作指示 的对应关系时， 所述 TPF接收到的来自 CRF的计费规则信息中包含计 费规则的标识；
所述 TPF获取是否进行计费操作指示的过程为： TPF根据接收到的 计费规则标识， 获取本地存储的计费规则， 并根据与该计费规则对应的 是否进行计费操作的指示信息， 获取是否进行计费操作的指示。
6、 根据权利要求 1所述的方法， 其特征在于， CRF根据接收到的 来自 TPF的计费规则请求， 确定计费规则信息。
7、 根据权利要求 6所述的方法， 其特征在于， CRF根据接收到的 来自 TPF的计费规则请求确定计费规则信息之前，进一步包括： CRF接 收来自在线计费系统 OCS和 /或应用功能实体 AF的用于确定计费规则 的输入信息， 综合来自 TPF的计费规则请求， 以及来自 OCS和 /或 AF 的用于确定计费规则的输入信息， 确定计费规则信息。
PCT/CN2005/001230 2004-08-10 2005-08-10 Procede de reduction de la charge d'un tpf WO2006015542A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
BRPI0508482-2A BRPI0508482A (pt) 2004-08-10 2005-08-10 método para reduzir a carga de função de plano de tráfego
AT05772878T ATE454765T1 (de) 2004-08-10 2005-08-10 Verfahren zur verringerung der tpf-last
EP05772878A EP1777871B1 (en) 2004-08-10 2005-08-10 A method for reducing the load of tpf
CA2555254A CA2555254C (en) 2004-08-10 2005-08-10 Method for reducing load of traffic plane function
DE602005018784T DE602005018784D1 (de) 2004-08-10 2005-08-10 Verfahren zur verringerung der tpf-last
US11/497,687 US7957719B2 (en) 2004-08-10 2006-08-02 Method for reducing load of traffic plane function
US13/099,742 US8238873B2 (en) 2004-08-10 2011-05-03 Method and system for charging control

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410070067.9 2004-08-10
CNB2004100700679A CN100474810C (zh) 2004-08-10 2004-08-10 一种基于业务数据流的承载计费信息收集方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/497,687 Continuation US7957719B2 (en) 2004-08-10 2006-08-02 Method for reducing load of traffic plane function

Publications (1)

Publication Number Publication Date
WO2006015542A1 true WO2006015542A1 (fr) 2006-02-16

Family

ID=35839136

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001230 WO2006015542A1 (fr) 2004-08-10 2005-08-10 Procede de reduction de la charge d'un tpf

Country Status (9)

Country Link
US (2) US7957719B2 (zh)
EP (1) EP1777871B1 (zh)
CN (1) CN100474810C (zh)
AT (1) ATE454765T1 (zh)
BR (1) BRPI0508482A (zh)
CA (1) CA2555254C (zh)
DE (1) DE602005018784D1 (zh)
ES (1) ES2337477T3 (zh)
WO (1) WO2006015542A1 (zh)

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1303781C (zh) * 2004-04-01 2007-03-07 华为技术有限公司 一种分组数据业务的计费控制方法
CN100474810C (zh) 2004-08-10 2009-04-01 华为技术有限公司 一种基于业务数据流的承载计费信息收集方法
CN101047949B (zh) * 2006-03-27 2010-05-12 华为技术有限公司 业务数据流的承载控制方法
CN101083541B (zh) * 2006-05-31 2013-05-01 朗迅科技公司 Ims网关系统和方法
CN100563388C (zh) * 2006-06-01 2009-11-25 华为技术有限公司 一种用户漫游状态下的策略及计费控制方法
US8046019B2 (en) * 2006-08-04 2011-10-25 Futurewei Technologies, Inc. Method and system for optimal allocation of uplink transmission power in communication networks
US20100041366A1 (en) * 2006-11-10 2010-02-18 Peter Zackrisson Method and apparatus for control of service usage in a communications system
US8325654B2 (en) 2006-12-28 2012-12-04 Futurewei Technologies, Inc. Integrated scheduling and power control for the uplink of an OFDMA network
CN101237328B (zh) * 2007-01-30 2012-07-04 朗迅科技公司 为离线收费系统配置自适应模块的方法
US9681336B2 (en) * 2007-06-13 2017-06-13 Qualcomm Incorporated Quality of service information configuration
EP2206281B1 (en) * 2007-10-30 2015-07-29 Alcatel Lucent Method, apparatus and system for supporting distributed ims charging
US20090190471A1 (en) * 2008-01-10 2009-07-30 Mahendran Arungundram C Method and Apparatus for Optimized Session Setup with Network-Initiated QoS Policy Control
US7937300B2 (en) * 2008-07-10 2011-05-03 Bridgewater Systems Corp. System and method for providing interoperability between diameter policy control and charging in a 3GPP network
PL2175588T5 (pl) † 2008-10-13 2014-06-30 Openet Telecom Ltd Sposób i system kontroli pobierania opłat za usługi telekomunikacyjne
CN101873574B (zh) * 2009-04-22 2015-03-25 华为技术有限公司 无线网络点对点数据交换方法、无线接入设备及系统
US20120198046A1 (en) * 2010-04-29 2012-08-02 Mehul Jayant Shah Mobile device bandwidth throttling
US8549116B2 (en) * 2010-05-05 2013-10-01 Alcatel Lucent PCRF triggered rules cleanup
US8954565B2 (en) * 2010-06-25 2015-02-10 Alcatel Lucent Method and system for determining a PCC rule waiting for further action
EP2466866A1 (en) * 2010-12-15 2012-06-20 Alcatel Lucent Unlimited usage policy-based charging system and method
US8774772B2 (en) * 2010-12-21 2014-07-08 Oracle International Corporation Communications service broker for preventing voicemail tromboning in the telecommunications network
EP2509254A1 (en) * 2011-04-06 2012-10-10 Telefonaktiebolaget L M Ericsson (publ) Method and apparatus for controlling service traffic in a communication network
EP4092959A1 (en) 2011-05-06 2022-11-23 Huawei Technologies Co., Ltd. Method for charging for data service, gateway device and related system
US9179007B1 (en) 2013-09-27 2015-11-03 Juniper Networks, Inc. Analytics triggered subscriber policies
WO2016078006A1 (zh) * 2014-11-19 2016-05-26 华为技术有限公司 一种定向统计流量的方法、设备及系统
CN107548046A (zh) * 2016-06-24 2018-01-05 中兴通讯股份有限公司 一种基于分离架构的计费方法、装置和系统
US10291790B2 (en) * 2017-10-06 2019-05-14 Wipro Limited System and method for dynamic charging in communication networks
US11727283B2 (en) 2020-05-19 2023-08-15 International Business Machines Corporation Rule distribution across instances of rules engine

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002041592A1 (en) * 2000-11-14 2002-05-23 Telefonaktiebolaget Lm Ericsson (Publ) Network requested packet data protocol context activation
WO2003047164A2 (en) * 2001-11-28 2003-06-05 Markport Limited Control of services in mobile packet data networks
WO2003081843A1 (en) * 2002-03-27 2003-10-02 Telefonaktiebolaget Lm Ericsson (Publ) Charging in a communications network
WO2004036890A1 (en) 2002-09-20 2004-04-29 Nokia Corporation Method for charging of data reaching a network element of a communication network during a data session

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1395391A (zh) 2001-07-09 2003-02-05 深圳市中兴通讯股份有限公司 一种宽带接入网络计费方法
US7831247B2 (en) * 2002-11-12 2010-11-09 Nokia Corporation Method of communication and communication system
CN1256823C (zh) 2002-12-07 2006-05-17 华为技术有限公司 能够基于用户数据流量计费的无线局域网服务系统及方法
CN100474810C (zh) 2004-08-10 2009-04-01 华为技术有限公司 一种基于业务数据流的承载计费信息收集方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002041592A1 (en) * 2000-11-14 2002-05-23 Telefonaktiebolaget Lm Ericsson (Publ) Network requested packet data protocol context activation
WO2003047164A2 (en) * 2001-11-28 2003-06-05 Markport Limited Control of services in mobile packet data networks
WO2003081843A1 (en) * 2002-03-27 2003-10-02 Telefonaktiebolaget Lm Ericsson (Publ) Charging in a communications network
WO2004036890A1 (en) 2002-09-20 2004-04-29 Nokia Corporation Method for charging of data reaching a network element of a communication network during a data session

Also Published As

Publication number Publication date
CA2555254C (en) 2011-02-08
BRPI0508482A (pt) 2007-07-31
US7957719B2 (en) 2011-06-07
ATE454765T1 (de) 2010-01-15
ES2337477T3 (es) 2010-04-26
DE602005018784D1 (de) 2010-02-25
US20110207432A1 (en) 2011-08-25
CA2555254A1 (en) 2006-02-16
US8238873B2 (en) 2012-08-07
EP1777871A1 (en) 2007-04-25
CN1735022A (zh) 2006-02-15
EP1777871A4 (en) 2007-10-24
US20070123213A1 (en) 2007-05-31
EP1777871B1 (en) 2010-01-06
CN100474810C (zh) 2009-04-01

Similar Documents

Publication Publication Date Title
WO2006015542A1 (fr) Procede de reduction de la charge d'un tpf
EP1622304B2 (en) Method for selecting a charging rule in connection with subscriber
EP2289254B1 (en) Charging in lte/epc communication networks
KR101195691B1 (ko) 방문 네트워크의 프록시 온라인 과금 시스템에서의 로밍 사용자를 위한 온라인 과금
US8023926B2 (en) Offline charging for sessions over a 3GPP network and a WLAN access network
US20070185809A1 (en) Method and system for processing online charging
WO2005109758A1 (en) A processing method for perfect charging on line based on the service data stream
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2005099184A1 (fr) Procede d'amelioration des regles de taxation dans des services de donnees par paquets et fonctionnement correspondant
WO2006012798A1 (fr) Procede de traitement de reautorisation a base de taxation du flux de donnees par paquets
WO2006050669A1 (fr) Procede de chargement en fonction d'un flux de paquets de donnees
WO2011017974A1 (zh) 一种统计资源申请过程中流量的网关、系统及方法
WO2006015543A1 (en) A processing method for re-authorization and re-authorization event and event triggers
WO2006060964A1 (fr) Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees
WO2006050670A1 (fr) Procede de traitement de cle de taxation
WO2009086760A1 (zh) Ims网络中非sip应用的计费方法、系统及计费事件上报单元
CN1323514C (zh) 一种移动分组数据业务的计费方法
WO2007131420A1 (fr) Procédé, dispositif et système de taxation dans le service de diffusion/multidiffusion multimédia
WO2012041148A1 (zh) 一种用量监测方法及系统
CN101159565A (zh) 一种基于业务数据流的承载计费信息收集方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2005772878

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2555254

Country of ref document: CA

Ref document number: 11497687

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2849/CHENP/2006

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 2005772878

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 11497687

Country of ref document: US

ENP Entry into the national phase

Ref document number: PI0508482

Country of ref document: BR