WO2005109758A1 - A processing method for perfect charging on line based on the service data stream - Google Patents

A processing method for perfect charging on line based on the service data stream Download PDF

Info

Publication number
WO2005109758A1
WO2005109758A1 PCT/CN2005/000665 CN2005000665W WO2005109758A1 WO 2005109758 A1 WO2005109758 A1 WO 2005109758A1 CN 2005000665 W CN2005000665 W CN 2005000665W WO 2005109758 A1 WO2005109758 A1 WO 2005109758A1
Authority
WO
WIPO (PCT)
Prior art keywords
charging
tpf
crf
ocs
address information
Prior art date
Application number
PCT/CN2005/000665
Other languages
English (en)
French (fr)
Inventor
Xiaoqin Duan
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=35320560&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2005109758(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP05745147A priority Critical patent/EP1746772B1/en
Priority to DE602005013661T priority patent/DE602005013661D1/de
Publication of WO2005109758A1 publication Critical patent/WO2005109758A1/zh
Priority to US11/558,774 priority patent/US8798575B2/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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03—Credit; Loans; Processing thereof
    • 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
    • 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
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/745—Customizing according to wishes of subscriber, e.g. friends or family
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0108—Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0188—Network monitoring; statistics on usage on called/calling number
    • 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/22—Bandwidth or usage-sensitve billing
    • 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

Definitions

  • the present invention relates to the field of charging, and in particular to a method for improving charging based on service data flow. Background of the invention
  • FIG. 1 is a flowchart of activating, transmitting, and deactivating a packet data protocol context (PDP Context, Packet Data Protocol Context).
  • PDP Context Packet Data Protocol Context
  • GPRS General Packet Radio Service
  • the implementation process of transmitting data and deactivating includes the following steps:
  • Step 101 The user equipment (UE) sends a PDP Context activation request (Activate PDP Context Request) to a serving general packet radio service support node (SGSN, Serving GPRS Support Node), where the Activate PDP Context Request carries a network layer service access identifier (NS API, Network Layer Service Access Point Identifier), PDP type, access point name (APN, Access Point Name), required quality of service (QoS) parameters, transaction identifier (TI, Transaction Identifier) and other information, where NSAPI is The SGSN and the Gateway General Packet Radio Service Support Node (GGSN) serve as a component of a tunnel identifier (TEID, Tunnel Identifier) to identify the PDP context; PDP types include end-to-end protocols (PPP, Peer- Peer Protocol) type, Internet Protocol (IP, Internet Protocol) type, etc .; APN can be provided by the UE to the SGSN, the SGSN addresses the corresponding GGSN according to the APN, and the GGSN
  • Step 103 The SGSN parses the GGSN address information according to the APN. If the SGSN can parse the GGSN address information according to the APN, a TEID is created for the PDP Context.
  • the TEID may be a combination of an International Mobile Subscriber Identity (IMSI, International Mobile Subscriber Identity) and NSAPI.
  • IMSI International Mobile Subscriber Identity
  • NSAPI International Mobile Subscriber Identity
  • the SGSN For uniquely identifying a PDP Context between the SGSN and the GGSN, and then the SGSN sends a PDP Context creation request (Create PDP Context Request) to the GGSN, where the Create PDP Context Request carries a PDP type, PDP address, APN, QoS parameters, TEID, selection mode, etc., where the PDP address is the UE ’s IP address and is an optional parameter.
  • the Create PDP Context Request may not carry the PDP address.
  • the GGSN may assign an IP address to the UE during subsequent processing.
  • An IP address can be assigned to the UE by a packet data network (PDN, Packet Data Network) that finally establishes a connection with the UE; the selection mode refers to the selection mode of the APN, that is, the APN. Is selected by the UE or by the SGSN. If the SGSN cannot resolve the address information of the GGSN according to the APN, the SGSN rejects the PDP context activation request initiated by the UE.
  • PDN Packet Data Network
  • Step 104 After receiving the Create PDP Context Request, the GGSN determines the external PDN according to the APN, and then allocates a charging ID, starts charging, and negotiates. QoS parameters. If the GGSN can meet the quality of service requirements of the QoS parameters, then A PDP Context creation response (Create PDP Context Response) is returned to the SGSN.
  • the Create PDP Context Response carries information such as a TEID, a PDP address, a Link Bearer (Backbone Bearer) protocol, a QoS parameter, and a Charging ID.
  • Step 105 After receiving the Create PDP Context Response, the SGSN inserts the NSAPI and GGSN address information into the PDP Context to identify the PDP Context, selects the wireless priority according to the QoS parameters, and returns a PDP Context activation response to the UE (Activate PDP Context Accept), the Activate PDP Context Accept carries information such as PDP type, PDP address, TI, QoS parameters, wireless priority, and PDP configuration options, and the SGSN initiates charging. After receiving the Activate PDP Context Accept, the UE establishes a route with the GGSN. At this time, the UE establishes a transmission channel with the PDN, and can perform data transmission.
  • the Activate PDP Context Accept After receiving the Activate PDP Context Accept, the UE establishes a route with the GGSN. At this time, the UE establishes a transmission channel with the PDN, and can perform data transmission.
  • Step 106 The UE performs data transmission through the SGSN, the GGSN, and the PDN.
  • Step 107 After the data transmission is completed, the UE sends a PDP Context deactivation request (Deactivate PDP Context Request) to the SGSN.
  • the Deactivate PDP Context Request carries a TL
  • Step 108 After receiving the Deactivate PDP Context Request, the SGSN performs security check and encryption with the UE. This step is optional.
  • the Delete PDP Context Request (Delete PDP Context Request), the Delete PDP Context Request carries a TEID.
  • the GGSN After receiving the Delete PDP Context Request, the GGSN ends the charging to the UE, deletes the PDP Context corresponding to the TEID, and then sends a PDP Context Delete Response (Delete PDP Context Response) to the SGSN.
  • the Delete PDP Context Response carries the TEID.
  • the SGSN ends the charging to the UE, deletes the PDP Context corresponding to the TEID, and then sends the PDP 'Context to the UE to deactivate the P response (Deactivate PDP Context Response), which is carried in the Deactivate PDP Context Response.
  • the UE After receiving the Deactivate PDP Context Response, the UE deletes the PDP Context corresponding to the TI
  • the starting point is set when the PDP Context is activated, and the end point of charging is set when the PDP Context is deleted. Therefore, charging can only be based on the data traffic transmitted by the PDP Context, or based on the length of time the PDP Context is active.
  • the UE can perform various services based on an activated PDP Context, such as email sending and receiving services, and based on the Wireless Application Protocol (WAP).
  • WAP Wireless Application Protocol
  • Browsing services, and file transfer protocols (FTP, File Transfer Protocol) -based services that is, if a PDN can provide multiple services and services, the UE can establish a transmission channel with the PDN through an activated
  • the PDP Context carries various services that the PDN can provide.
  • operators are likely to adopt different charging methods for various business charging models. For example, for email sending and receiving services, pay-per-use charging based on email receiving and sending events can be triggered.
  • charging can be based on traffic.
  • the file transfer service can also be charged according to the flow rate, the rate of the WAP browsing service and the file transfer service are different. In this way, according to the existing GPRS charging system, it is impossible to differentiate charging for different services carried by the same PDP Context at all.
  • IP Flows IP-based data charging
  • FBC IP-based Charging
  • the charging based on IP data flow can be considered as filtering the IP data flows of different services carried in the same-PDP context through some similar filters, and then calculating the IP data flows filtered by different filters separately. Fees to achieve the purpose of charging different IP data streams separately. In this way, the granularity of charging based on IP data flows is much smaller than The granularity of charging for each PDP Context can be regarded as the size of the sieve hole.
  • the granularity of charging based on a PDP Context is that a PDP Context is a sieve hole, while the charging granularity based on IP data flow is an IP service data.
  • the flow is a sieve hole, that is, for a PDP Context that contains multiple sieve holes. Therefore, compared to the charging based on IP data flow, the charging based on IP data flow can be an operator. Or business' providers provide richer billing methods.
  • 3GPP describes the FBC system structure, functional requirements, and message interaction processes.
  • the FBC system structure that supports online charging is shown in Figure 2A.
  • Customized applications based on mobile network enhanced logic (CAMEL, Customised Application for Mobile Network Enhanced Logic) Service Control Point (SCP) 201 and Service Data Flow Based Credit Control Function 202 (CCF) form an online charging system (OCS, Online Charging System) 206.
  • CCF 202 is connected to a charging function entity (CRF, Service Data Flow Based Charging Rule Function) 203 through an Ry interface, and CRF 203 is connected to an application function entity (AF, Application Function) 204 through an Rx interface.
  • the CRF 203 is connected to a transport plane function entity (TPF, Traffic Plane Function) 205 through a Gx interface, and the CCF 202 is connected to the TPF 205 through a Gy interface.
  • TPF transport plane function entity
  • TPF Traffic Plane Function
  • CRF 203 is connected to AF 204 through the Rx interface
  • CRF 203 is connected to TPF 205 through the Gx interface
  • TPF 205 is connected to the charging gateway functional entity (CGF, Charging) through the Gz interface.
  • the Gateway Function 207 is connected to a Charging Collection Function (CCF) 208. Because the functions of CGF and CCF are generally combined and implemented in the same network entity, the functional entities that provide offline charging and charging gateway functions and charging collection functions are referred to as offline charging function entities (OCF, Offline Charging Function) in this article. ).
  • OCF Online Charging Function
  • TPF 205 carries the number of IPs.
  • the TPF 205 sends a charging rule request to the CRF 203 through the Gx interface, and the charging rule request carries related information of the UE, bearer characteristics, and information related to the network, among which Relevant information of the UE may be the mobile station integrated service service network international number (MSISDN), the international mobile subscriber identity (IMSI), etc., and the network-related information may be the mobile network code (MNC), the mobile country code (MCC), and the like.
  • MSISDN mobile station integrated service service network international number
  • IMSI international mobile subscriber identity
  • MNC mobile network code
  • MCC mobile country code
  • the UE uses the same service. If the QoS parameters are different, the charging rules may also be different. The rate has also fallen. At this time, the TPF 205 may resend the charging rule request to the CRF 203 when the bearer is modified, requesting a new charging rule; the CRF 203 selects an appropriate charging rule according to the input information provided by the TPF 205, and returns to the TPF 205
  • the selected charging rule which includes information such as a charging mechanism, a charging type, a charging key, an IP data stream filter, and a charging rule priority.
  • the charging mechanism can be online charging or offline charging; the charging type can be based on the length of time for charging and data data charging; the charging key is a parameter related to the charging rate,
  • the CRF 203 may not directly provide the charging rate to the TPF 205, but only provide the TPF 205 with parameters related to the charging rate;
  • the IP data stream filter is used to instruct the TPF 205 to filter which IP data streams to filter, and then the TPF 205
  • the filtered IP data flows are charged according to the charging rules.
  • the IP data stream filter may include an IP5 tuple, and the IP5 tuple may include source / destination IP address, source / destination port number (Port Number), protocol ID (Protocol ID) and other information.
  • CRF 203 instructs TPF 205 pairs
  • the source IP address is 10.0.0.1, the destination address is 10.0.0.2, the source / destination port number is 20, and the protocol type is Transmission Control Protocol (TCP).
  • TCP Transmission Control Protocol
  • the IP data stream is filtered, and the filtered IP data stream is filtered according to the charging rules. Perform billing.
  • the TPF 205 may also send a charging rule request to the CRF 203, asking the CRF to provide a new charging rule.
  • the CRF 203 may request the TPF 205 to delete the previously established charging rule.
  • the CRF 203 may also determine the charging rule according to the input information of the AF 204 or the OCS 206. For example, the AF 204 notifies the CRF 203 of the service type currently used by the UE, and the CRF 203 selects a corresponding charging rule according to the service type.
  • OCS 206 is composed of two functional entities, SCP 201 and CCF (Service Data Flow Based Credit Control Function) 202, of which CCF (Service Data Flow Based Credit Control Function) 202 is a functional entity that performs credit control and is only used for online billing
  • CCF Service Data Flow Based Credit Control Function
  • CCF Service Data Flow Based Credit Control Function
  • CCF Service Data Flow Based Credit Control Function
  • CRF Service Data Flow Based Credit Control Function
  • the CCF Service Data Flow Based Credit Control Function
  • the CCF Service Data Flow Based Credit Control Function
  • the TPF 205 provides credits that the UE can use. Users of the UE may also set a shared credit pool for multiple different packet data services.
  • the CCF Service Data Flow Based Credit Control Function
  • the CCF Service Data Flow Based Credit Control Function
  • the credits in the pool are authenticated and the TPF 205 is provided with credits that the UE can use.
  • TPF 205 is GGSN
  • AF is a service gateway or service server in PDN
  • CRF 203 is a newly added logical entity.
  • TPF 205 is the execution point of the charging rules
  • CRF 203 is the control point of the charging rules.
  • Figure 3A is a flowchart of issuing charging rules when a bearer is established. As shown in Figure 3A, the implementation process of issuing charging rules when a bearer is established includes the following steps:
  • Step 301A The UE sends a Establish Bearer Service Request to the TPF.
  • the GGSN receives the Create PDP Context Request.
  • Step 302A After receiving the bearer establishment request, the TPF sends a charging rule request (Request Charging Rules) to the CRF.
  • the charging rule request carries input information for the CRF to determine the charging rule.
  • Steps 303 to 304 After receiving the charging rule request, the CRF may select an appropriate charging rule according to the input information carried in the charging rule request, and then return to the TPF according to the relevant input information provided by the AF.
  • Step 305A After receiving the provision of the charging rule message, the TPF performs corresponding operations on the charging rule selected by the CRF according to the charging rule operation instruction.
  • Steps 306A to 307A When performing online charging, the TPF sends a credit request (Credit Request) to the OCS, and requests the UE's credit from the OCS. After receiving the credit request, the OCS determines the credit of the UE, and then returns a credit response (Credit Response) to the TPF. If the OCS determines the credit of the UE, the credit response carries the credit of the UE, and if the OCS does not determine the credit of the UE , The credit response may carry an error cause value.
  • Step 308A After receiving the credit response, the TPF returns a bearer establishment response (Establish Bearer Service Accept) to the UE. If the credit response carries the UE's credit, the TPF accepts the bearer establishment request initiated by the UE and continues the subsequent bearer establishment process. If the credit response does not carry the credit of the UE, the bearer establishment request initiated by the UE is rejected.
  • a bearer establishment response (Establish Bearer Service Accept)
  • FIG. 3B is a flowchart of issuing a charging rule when the bearer is modified.
  • the implementation process of issuing a charging rule when the bearer is modified includes the following steps:
  • Step 30 IB The UE sends a Modify Bearer Service Request to the TPF.
  • the GGSN receives a PDP Context Update Request (Update PDP Context Request).
  • Step 302B After receiving the bearer modification request, the TPF sends a charging rule request to the CRF.
  • the charging rule request carries input information for the CRF to determine the charging rule.
  • Steps 303B to 304B After receiving the charging rule request, the CRF may select an appropriate charging rule according to the input information carried in the charging rule request, and then return to the TPF to provide the accounting plan.
  • a charging rule message, where the provided charging rule message may carry a selected charging rule and a charging rule operation instruction.
  • Step 305B After receiving the provision of the charging rule message, the TPF performs corresponding operations on the charging rule selected by the CRF according to the charging rule operation instruction.
  • Steps 306B to 307B When charging online, the TPF sends a credit request to the OCS and requests the UE's credit from the OCS. After receiving the credit request, the OCS determines the credit of the UE, and then returns a credit response to the TPF. If the OCS determines the credit of the UE, the credit response carries the credit of the UE. If the OCS does not determine the credit of the UE, the credit The error cause value can be carried in the response.
  • Step 308B After receiving the credit response, the TPF returns a bearer modification response (Modify Bearer Service Accept) to the UE. If the credit response carries the UE's credit, the TPF accepts the bearer modification request initiated by the UE and continues the subsequent bearer modification process. If the credit response does not carry the credit of the UE, the bearer modification request initiated by the UE is rejected.
  • a bearer modification response Modify Bearer Service Accept
  • FIG. 3C is a flowchart of issuing a charging rule when a bearer is deleted.
  • the implementation process of issuing a charging rule when a bearer is deleted includes the following steps:
  • Step 301C The UE sends a Bearer Delete Request (Remove Bearer Service Request) to the TPF.
  • the GGSN receives the Delete PDP Context Request.
  • Step 302C After the TPF receives the bearer delete request, it sends a charging rule request to the CRF.
  • the charging rule request carries input information for the CRF to determine the charging rule.
  • Step 303O and step 304C After receiving the charging rule request, the CRF may select an appropriate charging rule according to the input information carried in the charging rule request, and then return to the TPF to provide charging.
  • a rule message which provides a charging rule message It can carry selected charging rules and charging rule operation instructions.
  • Step 305C After receiving the provision of the charging rule message, the TPF performs corresponding operations on the charging rule selected by the CRF according to the charging rule operation instruction.
  • Step 306O and Step 307C When charging online, the TPF sends a credit report (Final Remaining Credit Report) to the OCS to notify the OCS that the bearer established for the UE has been terminated, and the credit report carries the usage status of the UE ’s credit, such as the UE The length of time the packet data service is used and the amount of traffic using the packet data. After receiving the credit report, the OCS returns a credit report response (Response) to the TPF.
  • a credit report (Final Remaining Credit Report)
  • the OCS After receiving the credit report, the OCS returns a credit report response (Response) to the TPF.
  • Step 308C After receiving the credit report response, the TPF returns a bearer deletion response (Remove Bearer Service Accept) to the UE, accepts the bearer deletion request initiated by the UE, and continues the subsequent bearer deletion process.
  • a bearer deletion response Remove Bearer Service Accept
  • FIG. 4 is a flow chart of CRF actively issuing charging rules to TPF. As shown in Figure 4, the implementation process of CRF actively issuing charging rules to TPF includes the following steps:
  • Step 401 The CRF receives an internal or external trigger event (Internal or External Trigger Event), and information related to the event, such as an event in which the AF sends a charging rule to the CRF to select input information.
  • an internal or external trigger event Internal or External Trigger Event
  • information related to the event such as an event in which the AF sends a charging rule to the CRF to select input information.
  • Step 402 The CRF selects an appropriate charging rule according to the obtained input information.
  • These input information may be charging-related input information provided by the AF.
  • the service has special requirements for charging.
  • the charging rate is different from the charging rates of other services.
  • the AF provides the CRF with the charging input information related to the service; it can also provide the charging related input information provided by the TPF.
  • Step 403 If the charging rule is changed, the CRF sends a charging rule providing message to the TPF, and the charging rule providing message may carry the selected charging rule and the charging rule operation instruction.
  • Step 404 After the TPF receives the charging rule providing message, it operates according to the charging rule operation instruction. Perform corresponding operations on the charging rules selected by the CRF.
  • Steps 405 to 406 When charging online, the TPF sends a credit request to the OCS, and requests the OCS's credit from the UE. After receiving the credit request, the OCS determines the UE ’s credit, and then returns a credit response to the TPF. If the OCS determines the UE ’s credit, the credit response is carried. If the OCS does not determine the UE ’s credit, the OCS The credit response may carry an error cause value.
  • the object of the present invention is to provide a method for processing charging based on service data streams, which improves the implementation process of charging based on service data streams, and further improves the implementation process of charging based on packet data services. Completeness and clarity.
  • the present invention provides a method for processing charging based on service data flow.
  • the method includes steps A1 and CRF: providing address information of a charging system to a TPF.
  • the address information of the charging system in step A1 is OCS address information of the online charging system.
  • the method further includes: The CRF determines that the current charging method of the packet data service is online charging according to the received input information.
  • the step A1 further includes the following steps: Bll.
  • the TPF requests credit from the OCS according to the OCS address information;
  • the method further includes: the TPF provides input information for determining the credit to the OCS; the step C11 includes: the OCS determines the credit according to the input information, and then provides the credit to the TPF .
  • the step A1 includes: the CRF provides more than one OCS address information to the TPF, and provides selection priority corresponding to each OCS; the step B11 is: the TPF according to the selection priority of the OCS and the OCS address information, first to the selection The OCS with the highest priority requests credit. If the credit request is unsuccessful, it requests credit from the OCS according to the selected priority in turn until the credit request is successful.
  • step B11 When the OCS address information in step A1 is empty, the step B11 is: The TPF requests credit from the OCS according to the pre-configured OCS address information.
  • the method further includes: The CRF sends an online charging instruction to the TPF.
  • the OCS address information is carried in an online charging instruction.
  • the OCS address information is CCF address information of a credit control function entity in the OCS.
  • the OCS address information is stored in the CRF.
  • the method further includes: The CRF obtains OCS address information through interaction with the network entity.
  • the address information of the charging system in step A1 is an OCF address letter of the offline charging function entity.
  • the step A1 further includes: The CRF determines that the current charging method of the packet data service is offline charging according to the received input information.
  • step A1 the method further includes:
  • the TPF sends, according to the OCF address information, the statistical charging data information of the UE to the 0CF.
  • the step A1 includes: the CRF provides more than one OCF address information to the TPF, and provides selection priority corresponding to each OCF; the step B21 is: the TPF according to the selection priority of the OCF and the OCF address information, first to the selection The OCF with the highest priority sends the statistical charging data information of the UE. If the transmission is unsuccessful, the statistical charging data information of the UE is sequentially sent to the OCF according to the selected priority until the transmission is successful.
  • the step B21 is: the TPF sends the statistical accounting data letter ir of the UE to the OCF according to the pre-configured OCF address information.
  • the method further includes: CRF sending to the TPF Offline billing instructions.
  • the OCF address information is carried in the offline charging instruction. .
  • the OCF address information is stored in the CRF.
  • the method further includes: The CRF obtains OCF address information through interaction with the network entity.
  • the network entity is a home location register HLR, or a home subscriber server HSS.
  • the input information is provided by the AF to the CRF.
  • the input information is provided by the TPF to the CRF.
  • the present invention also provides a processing method for improving charging based on service data streams, which method includes the following steps:
  • CRF determines whether the current charging method of the packet data service is online charging or offline charging according to the input information provided by the AF;
  • the CRF sends an online charging instruction or an offline charging instruction to the TPF according to the determination result. If the CRF sends an online charging instruction to the TPF, the step B2 further includes: the CRF provides the OCS address information to the TPF.
  • the input information in step A2 is a packet data service identifier.
  • the invention also provides a processing method for improving charging based on service data streams, which method Includes the following steps:
  • the CRF determines whether the current charging method of the packet data service is online charging or offline charging
  • the CRF sends an online charging instruction or an offline charging instruction to the TPF according to the determination result. If the CRF sends an online charging instruction to the TPF, the step B3 further includes: the CRF provides OCS address information to the TPF; if the CRF sends an offline charging instruction to the TPF, the step B3 further includes: the CRF provides an OCF address to the TPF information.
  • the input information in step A3 is the user equipment identity.
  • the CRF can determine whether the charging method for the current packet data service is online charging or offline charging according to input information provided by the AF or input information provided by the TPF.
  • the TPF provides charging rules for "online charging” or "offline charging”.
  • the CRF will provide the OCS address information or OCF address information corresponding to the UE to the TPF, so that the TPF can address the corresponding OCS according to the OCS address information, trigger the subsequent credit request process for the UE, or enable the TPF to be based on the OCF
  • the address information is addressed to the corresponding OCF, and the statistical UE's charging data information is sent to the OCF, which makes the FBC mechanism-based charging implementation process more complete and reasonable.
  • Figure 1 is a flowchart of PDP Context activation, data transmission, and deactivation
  • FIG. 2A is a schematic structural diagram of an FBC system for online charging
  • FIG. 2B is a schematic structural diagram of an FBC system for offline charging
  • Figure 3A is a flowchart of charging when the bearer is established
  • FIG. 3B is a flowchart of charging when the bearer is modified
  • FIG. 3C is a flowchart of charging when the bearer is deleted
  • FIG. 4 is a flowchart of a CRF actively issuing a charging rule to a TPF; 5 is a flowchart of online charging during bearer establishment in the present invention;
  • FIG. 6 is a flowchart of offline charging when the CRF actively issues a charging rule to the TPF in the present invention.
  • the CRF provides OCS address information or OCF address information corresponding to the UE to the TPF, and the TPF addresses the corresponding OCS or OCF according to the OCS address information or the OCF address information, and then Request the credit of the UE from the corresponding OCS, or send the statistical charging data information of the UE to the corresponding OCF.
  • the CRF After the CRF determines that the charging method of a packet data service is online charging, it will provide the TPF with charging rules, and provide the TPF with online charging instructions and OCS address information.
  • the online charging instructions are used to notify the TPF of the packet data.
  • the current charging method of the service is online charging.
  • the OCS address information is used by the TPF to address the OCS corresponding to the UE when requesting the credit of the UE from the OCS. OCS address information can be carried in online charging instructions.
  • the CRF will provide the TPF with charging rules, and provide the TPF with offline charging instructions and OCF address information.
  • the offline charging instructions are used to notify the TPF.
  • the current charging method of the packet data service is offline charging.
  • the OCF address information is used by the TPF to address the OCF corresponding to the UE when sending statistical user charging data information to the OCF. OCF address information can be carried in offline charging instructions.
  • the above OCS address information may be address information of a functional entity in the OCS that can implement the credit control of the UE.
  • CCF Service Data Flow Based Credit Control Fxmction
  • the address information of the OCS may be CCF (Service Data Flow Based Credit) in the OCS Control Function) address information.
  • the CRF may determine whether the current charging method of the packet data service is online charging or offline charging according to the input information provided by the AF. For example, the CRF determines the current packet data according to the service identifier in the input information of the charging rule provided by the AF. The charging method of the service is online charging or offline charging. The CRF can also determine whether the current packet data service charging method is online charging or offline charging based on the UE information. For example, the CRF determines the user of the UE as a prepayment according to the UE identifier in the charging rule input information provided by the TPF.
  • the CRF determines that the current charging method of the packet data service is online charging; for another example, the CRF determines that the user of the UE is a user of the postpaid service according to the UE identifier in the input information of the charging rule provided by the TPF, Therefore, the CRP determines that the current charging method of the packet data service is offline charging.
  • the CRF may store OCS address information or OCF address information corresponding to the UE, and may also interact with other entities in the network to obtain OCS address information or OCF address information corresponding to the UE. For example, the CRF passes Interaction with a Home Location Register (HLR) / Home Subscriber Server (HSS), to obtain OCS address information or OCF address information corresponding to the UE.
  • HLR Home Location Register
  • HSS Home Subscriber Server
  • multiple OCS selection priorities can be set, such as the preferentially selected OCS and
  • the second-selected OCS and CRF can provide the TPF with multiple OCS address information corresponding to the UE, that is, provide the TPF with the preferred OCS address information (primary OCS address) and the second-selected OCS address information (secondary OCS). address).
  • the TPF may initiate a credit request to the secondly selected OCS and request to establish a credit dialogue with the secondly selected OCS.
  • the operator can also configure an OCS address information for all UEs in the TPF.
  • the CRF does not provide the OCS address information to the TPF
  • the CRF provides the TPF
  • the OCS address information is empty
  • the TPF sends a credit request to the configured OCS, requesting to establish a credit dialogue with the configured OCS.
  • the CRF can provide the TPF with multiple OCF address information corresponding to the UE, that is, provide the TPF with the preferred OCF address information (primary OCF address) and the second-selected OCF address information ( secondary OCF address).
  • the TPF may send the accounting data information of the UE to the second selected OCF.
  • the operator can also configure OCF address information for all UEs in the TPF. In this way, when the CRF does not provide the OCF address information to the TPF, that is, when the OCF address information provided by the CRF to the TPF is empty, the TPF sends to the configured OCF Charging data information of the UE.
  • FIG. 5 is a flowchart of online charging during bearer establishment in the present invention. As shown in FIG. 5, the process of implementing online charging during bearer establishment includes the following steps:
  • Step 501 The UE sends a bearer establishment request to the TPF.
  • the GGSN receives the Create PDP Context Request.
  • Step 502 After receiving the bearer establishment request, the TPF sends a charging rule request to the CRF, where the charging rule request carries input information for the CRF to determine the charging rule.
  • Steps 503 to 504 After the CRF receives the charging rule request, first, according to the input information carried in the charging rule request, it may also be determined according to the relevant input information provided by the AF.
  • the current charging method of the packet data service is Online charging; Secondly, select the appropriate charging rule, and determine the address information of the OCS corresponding to it according to the UE information; Thirdly, return the provisioning charging message to the TPF, which can carry the selected charging rule message.
  • Charging rules and charging rule operation instructions and may further carry online charging instructions and OCS address letters.
  • Step 505 After receiving the charging rule providing message, the TPF performs a corresponding operation on the charging rule selected by the CRF according to the charging rule operation instruction.
  • Steps 506 to 507 After the TPF determines that it needs to request the UE's credit from the OCS according to the online charging instruction, it sends a credit request to the corresponding OCS according to the OCS address information.
  • the credit request carries relevant input information for the OCS to determine the credit.
  • the OCS determines the credit of the UE according to the input information provided by the TPF, and then returns a credit response to the TPF. If the OCS determines the credit of the UE for the charging rule, the credit response carries the credit of the UE. The OCS does not determine the credit of the UE, so the credit response may carry an error cause value.
  • Step 508 After receiving the credit response, the TPF returns a bearer establishment response to the UE. If the credit response carries the UE's credit, the TPF accepts the bearer establishment request initiated by the UE and continues the subsequent bearer establishment process. Carrying the UE's credit, the UE initiates a bearer establishment request.
  • the implementation process for bearer establishment, bearer modification, and bearer deletion during offline charging is basically the same as the above-mentioned implementation process for online charging during bearer establishment, except that the CRF charges the current packet data service.
  • the judgment result is offline charging, the address information carried in the transmitted message is OCF address information, and the subsequent credit interaction process of online charging is omitted, so it is not repeated here.
  • FIG. 6 is an offline charging flowchart when the CRF actively sends a charging rule to the TPF in the present invention.
  • the implementation process of offline charging includes the following steps: Step 601: The CRF receives an internal or external trigger event (Internal or External Trigger Event) and information related to the event, such as an event in which the AF sends a charging rule to select input information to the CRF.
  • an internal or external trigger event Internal or External Trigger Event
  • Step 602 Based on the obtained input information, the CRF determines that the current charging method of the packet data service is online charging, selects an appropriate charging rule, and determines the address information of the OCS corresponding to the UE based on the UE information.
  • the input information described above may be charging-related input information provided by the AF.
  • the UE uses a packet data service provided by the AF, and the AF provides a service identifier of the service to the CRF; it may also provide charging-related input provided by the TPF.
  • Information such as the UE identity provided by the TPF to the CRF in the charging rule request.
  • Step 603 According to the received input information, if the CRF determines that the charging rule has changed, for example, the CRF determines the current packet data charging method for online charging according to the service identifier provided by the AF, and the UE's fee for using the packet data service needs to be deducted in real time For another example, if the CRF determines that the user of the UE belongs to a postpaid user according to the UE identity provided by the TPF, the cost of the UE's use of all packet data services can be charged to the user of the UE after the service is used, then the CRF chooses a new charging The rule also sends a provisioning charging rule message to the TPF.
  • the provisioning charging rule message may carry the selected charging rule and charging rule operation instruction, and may further carry offline charging instruction and OCF address information.
  • Step 604 After receiving the provision of the charging rule message, the TPF performs corresponding operations on the charging rule selected by the CRF according to the charging rule operation instruction.
  • Step 605 The TPF counts the charging data information of the UE according to the filter information of the charging rule according to the offline charging instruction, and then sends the calculated charging data information of the UE to the corresponding OCF according to the OCF address information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Technology Law (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Meter Arrangements (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Description

一种完善基于业务数据流计费的处理方法 技术领域
本发明涉及计费领域， 特别是指一种完善基于业务数据流计费的处 理方法。 发明背景
随着分组数据业务应用的逐渐广泛， 如何准确合理地对分组数据业 务进行计费， 已成为运营商普遍关注的问题。
图 1 为分组数据协议上下文（PDP Context, Packet Data Protocol Context )激活、 传输数据、 去激活流程图， 如图 1所示， 在通用分组无 线业务（ GPRS , General Packet Radio Service ) 中， PDP Context激活、 传输数据、 去激活的实现过程包括以下步驟：
步骤 101:用户设备( UE )向服务通用分组无线业务支持节点（ SGSN, Serving GPRS Support Node )发送 PDP Context激活请求（ Activate PDP Context Request ), 该 Activate PDP Context Request中携带有网络层业务 访问标识 ( NS API, Network Layer Service Access Point Identifier )、 PDP 类型、接入点名称（APN, Access Point Name )、要求的服务质量（ QoS ) 参数、 事务标识（TI, Transaction Identifier )等信息， 其中， NSAPI在 SGSN 和网关通用分组无线业务支持节点 （GGSN， Gateway GPRS Support Node )之间作为隧道标识（TEID, Tunnel Identifier ) 的组成部 分， 用于标识 PDP Context; PDP类型包括端对端协议（ PPP， Peer-Peer Protocol ) 类型、 网际协议（IP, Internet Protocol ) 类型等； APN可由 UE向 SGSN提供， SGSN根据 APN寻址到相应 GGSN, GGSN根据 APN 确定 UE所要访问的外部网络， UE也可不向 SGSN提供 APN， 此时， 由 SGSN根据 UE的签约信息选择缺省的 APN; QoS参数为 UE指定的 分组数据业务所要达到的质量要求； TI用于 UE标识一个 PDP context 步驟 102: SGSN收到 Activate PDP Context Request后， 与 UE进行 安全性检查和加密， 该步骤为可选步骤。
步骤 103: SGSN根据 APN解析 GGSN地址信息， 如果 SGSN能够 根据 APN解析出 GGSN的地址信息， 则为 PDP Context创建 TEID , 该 TEID 可为国际移动用户标识 ( IMSI, International Mobile Subscriber Identity )与 NSAPI的组合， 用于在 SGSN和 GGSN之间唯一标识一个 PDP Context, 然后 SGSN向 GGSN发送 PDP Context创建请求（ Create PDP Context Request ), 该 Create PDP Context Request中携带有 PDP类 型、 PDP地址、 APN、 QoS参数、 TEID, 选择模式等， 其中， PDP地 址为 UE的 IP地址， 为可选参数， Create PDP Context Request中可不携 带 PDP地址， 此时， 在后续的处理过程中， 可由 GGSN为 UE分配 IP 地址， 也可由最终与 UE建立连接的分组数据网络（PDN, Packet Data Network )为 UE分配 IP地址； 选择模式是指 APN的选择模式， 即 APN. 是由 UE选定的还是由 SGSN选定的。如果 SGSN无法根据 APN解析出 GGSN的地址信息， 则 SGSN拒绝 UE发起的 PDP Context激活请求。
步骤 104: GGSN收到 Create PDP Context Request后 , 根据 APN确 定外部 PDN, 然后分配计费标识（Charging ID )、 启动计费， 并且协商. QoS参数， 如果 GGSN能够满足 QoS参数的服务质量要求， 则向 SGSN 返回 PDP Context创建响应（ Create PDP Context Response )，该 Create PDP Context Response中携带有 TEID、 PDP地址、链路承载（ Backbone Bearer ) 协议、 QoS参数、 Charging ID等信息。 如果 GGSN无法满足 QoS参数. 的服务质量要求， 则 GGSN拒绝 SGSN发起的 PDP Context创建请求， 然后 SGSN拒绝 UE发起的 PDP Context激活请求。 步骤 105: SGSN收到 Create PDP Context Response后，在 PDP Context 中插入 NSAPI和 GGSN地址信息， 用于标识该 PDP Context, 并根据 QoS 参数选择无线优先权， 然后向 UE 返回 PDP Context激活响应 ( Activate PDP Context Accept ), 该 Activate PDP Context Accept中携带 有 PDP类型、 PDP地址、 TI、 QoS参数、 无线优先权、 PDP配置选项. 等信息， 并且， SGSN启动计费。 UE收到 Activate PDP Context Accept 后， 建立与 GGSN之间的路由， 此时， UE与 PDN建立了传输通道， 可 以进行数据传输了。
步骤 106: UE通过 SGSN、 GGSN与 PDN进行数据传输。
步骤 107: 数据传输完毕， UE向 SGSN发送 PDP Context去激活请 求 ( Deactivate PDP Context Request ), 该 Deactivate PDP Context Request 中携带有 TL
步 108: SGSN收到 Deactivate PDP Context Request后， 与 UE进 行安全性检查和加密， 该步骤为可选步骤。
步骤 109〜步骤 111: SGSN向 GGSN发送 PDP Context删除请求
( Delete PDP Context Request ), 该 Delete PDP Context Request中携带有 TEID。 GGSN收到 Delete PDP Context Request后， 结束对 UE的计费， 删除对应于 TEID的 PDP Context, 然后向 SGSN发送 PDP Context删除 响应 ( Delete PDP Context Response ), 该 Delete PDP Context Response 中携带有 TEID。 SGSN收到 Delete PDP Context Response后， 结束对 UE的计费， 删除对应于 TEID的 PDP Context, 然后向 UE发送 PDP' Context去激活 p向应 ( Deactivate PDP Context Response ), 该 Deactivate PDP Context Response中携带有 TI。 UE收到 Deactivate PDP Context Response后， 删除对应于 TI的 PDP Context
由图 1描述的流程可见， 当前的 GPRS计费系统中， 由于计费的起' 始点设置在激活 PDP Context时，计费的终止点设置在删除 PDP Context 时，因此只能根据 PDP Context传输的数据流量进行计费，或是根据 PDP Context处于激活状态的时间长度进行计费。 然而， 在实际应用中， UE' 与 PDN建立起传输通道后， 该 UE可以基于一个激活的 PDP Context进 行多种业务，如电子邮件（Email )收发业务、基于无线应用协议（ WAP, Wireless Application Protocol ) 的浏览业务、 基于文件传输协议 ( FTP, File Transfer Protocol )的文件传输等业务， 即如果 PDN能够提供多种业 · 务， 则 UE在与该 PDN建立起传输通道后， 可通过一个激活的 PDP Context承载该 PDN能够提供的各种业务。 然而， 运营商对于各种业务 的计费模式很可能采用不同的计费方式， 如对于 Email收发业务可基于 Email接收和发送事件的触发按次计费，对于 WAP浏览业务可根据流量 ' 计费， 对于文件传输业务虽然也可根据流量计费， 但 WAP浏览业务的 费率与文件传输业务的费率却不尽相同。 这样， 根据现有的 GPRS计费 系统， 根本无法对同一 PDP Context承载的不同业务进行区分计费。
针对上述情况， 第三代合作伙伴计划 （3GPP, The 3rd Generation Partnership Project )目前正在讨论如何实现基于 IP数据流的计费（ FBC， Flow Based Charging )0对于一个分组数据业务而言， UE使用该业务时， 传输和接收到的所有 IP数据流（IP Flow ),也可为 IP分组包（IP packet ), 总称为业务数据流（ Service Data Flow ), 即业务数据流是由多个 IP数据 流组成的集合，因此基于 IP数据流的计费能够真实反映某个业务数据流 对资源的占用情况。
基于 IP数据流的计费可被认为是通过一些类似筛子的过滤器将同 — PDP Context中承载的不同业务的 IP数据流分别筛选出来， 然后针对 不同过滤器过滤出的 IP数据流进行分别计费， 以达到对不同的 IP数据 流分别计费的目的。这样，基于 IP数据流的计费粒度要远远小于基于一 个 PDP Context的计费粒度，粒度可看作是篩子孔的大小，基于一个 PDP Context的计费粒度是一个 PDP Context就是一个筛子孔， 而基于 IP数 据流的计费粒度则是一个 IP 业务数据流则为一个筛子孔， 即针对一个 PDP Context中包含多个筛子孔， 因此， 基于 IP数据流的计费与基于一 个 PDP Context的计费相比， 基于 IP数据流的计费能够为运营商或业务' 提供者提供更为丰富的计费手段。
3GPP中对 FBC的系统结构、 功能要求以及消息交互流程等方面均 进行了描述， 支持在线计费的 FBC系统结构如图 2A所示， 基于移动网 絡增强逻辑的客户化应用 （ CAMEL , Customised Application for Mobile Network Enhanced Logic ) 的业务控制点 （SCP, Service Control Point ) 201和基于 IP数据流计费的信用控制功能实体（CCF, Service Data Flow Based Credit Control Function ) 202组成了在线计费系统（ OCS , Online Charging System ) 206。 CCF 202通过 Ry接口与基于 IP数据流计费的计 费规则功能实体 ( CRF , Service Data Flow Based Charging Rule Function ) 203 相连， CRF 203 通过 Rx接口与应用功能实体 ( AF, Application Function ) 204相连， CRF 203通过 Gx接口与传输面功能实体（TPF， Traffic Plane Function )205相连， CCF 202通过 Gy接口与 TPF 205相连。
支持离线计费的 FBC系统结构如图 2B所示， CRF 203通过 Rx接 口与 AF 204相连， CRF 203通过 Gx接口与 TPF 205相连， TPF 205通 过 Gz接口分别与计费网关功能实体（ CGF , Charging Gateway Function ) 207和计费采集功能实体（CCF, Charging Collection Function ) 208相连。 由于 CGF和 CCF的功能一般合并在同一个网络实体中实现， 因此本文 中将提供离线计费的计费网关功能和计费采集功能的功能实体称为离 线计费功能实体（ OCF , Offline Charging Function )。
根据目前 3GPP对于实现 FBC功能实体的划分， TPF 205承载 IP数 据流， 当 IP数据流的承载建立时， TPF 205通过 Gx接口向 CRF 203发 送计费规则请求， 该计费规则请求中携带有 UE的相关信息、 承载特性 以及与网络相关的信息等， 其中 UE的相关信息可为移动台综合业务服 务网国际号码（MSISDN )、 国际移动用户标识（IMSI )等， 与网络相关 的信息可为移动网络编码（MNC )、 移动国家码（MCC )等。 另外， 由 于在 IP数据流传输过程中， 会对承载进行修改， 如对 QoS参数进行重 新协商， UE使用同一业务， 如果 QoS参数不同， 则计费规则也可能不 同， 如 QoS参数下降相应的费率也下降。 此时， TPF 205可在承载修改 时， 重新向 CRF 203发送计费规则请求， 请求新的计费规则； CRF 203 根据 TPF 205提供的上述输入信息选择适当的计费规则， 并向 TPF 205 返回选定的计费规则， 该计费规则中包括计费机制、计费类型、计费键、 IP数据流过滤器、 计费规则优先级等信息。 其中， 计费机制可为采用在 线计费还是离线计费； 计费类型可为基于时间长度进行计费还^ &于数 据流量进行计费； 计费键是与计费费率相关的参数， CRF 203可不直接 向 TPF 205提供计费费率， 而只是向 TPF 205提供与计费费率相关的参' 数； IP数据流过滤器用于指示 TPF 205对哪些 IP数据流进行过滤， 然 后 TPF 205根据计费规则对过滤出的 IP数据流进行计费。 IP数据流过 滤器中可包含 IP5元组， IP5元组可包括源 /目的 IP地址、 源 /目的端口 号（Port Number ), 协议标识（Protocol ID )等信息， 例如， CRF 203指 示 TPF 205对源地址为 10.0.0.1、 目的地址为 10.0.0.2、 源 /目的端口号为 20、 协议类型为传输控制协议（TCP )的 IP数据流进行过滤， 并根据计 费规则对过滤出的 IP数据流进行计费。 最后， 当承载删除时， TPF 205 也可向 CRF 203发送计费规则请求， 要求 CRF提供新的计费规则， 此 时 CRF 203可要求 TPF 205删除先前建立的计费规则。
另外， CRF 203除了根据 TPF 205的输入信息确定计费规则之外， CRF 203还可根据 AF 204或 OCS 206的输入信息确定计费规则， 如 AF 204通知 CRF 203UE当前使用的业务类型， CRF 203根据该业务类型选 择相应的计费规则。
OCS 206由 SCP 201和 CCF ( Service Data Flow Based Credit Control Function ) 202两个功能实体组成， 其中， CCF ( Service Data Flow Based Credit Control Function ) 202是执行信用控制的功能实体，仅应用于在线 计费系统， 可通过在现有的 OCS 206中增加新的功能来实现， 在在线计 费过程中 , CCF ( Service Data Flow Based Credit Control Function ) 202 对 UE的信用进行管理和控制， CCF ( Service Data Flow Based Credit Control Function )202可通过 Ry接口向 CRF 203提供用于选择计费规则 的相关信息。 UE 的用户可对不同的分组数据业务设置多个不同的信用 池，当 UE使用某个分组数据业务时， CCF( Service Data Flow Based Credit Control Function ) 202对与该分组数据业务相对应的信用池中的信用进 行鉴权， 并向 TPF 205提供 UE能够使用的信用。 UE的用户也可对多个 不同的分组数据业务设置一个共享的信用池， 当 UE使用这些分组数据 业务时， CCF ( Service Data Flow Based Credit Control Function ) 202对 与这些分组数据业务相对应的信用池中的信用进行鉴权， 并向 TPF 205 提供 UE能够使用的信用。
对应于 GPRS网络， TPF 205为 GGSN, AF为 PDN中的一个业务 网关或业务服务器， CRF 203为新增的逻辑实体。 TPF 205为计费规则 的执行点， CRF 203为计费规则的控制点。 ' 图 3A为承载建立时下发计费规则流程图， 如图 3A所示，承载建立 时下发计费规则的实现过程包括以下步骤：
步驟 301A: UE向 TPF发送承载建立请求（ Establish Bearer Service Request ),在 GPRS网络中，则是 GGSN收到 Create PDP Context Request。 步錄 302A: TPF收到承载建立请求后， 向 CRF发送计费规则请求 ( Request Charging Rules ), 该计费规则请求中携带有供 CRF确定计费 规则的输入信息。
步驟 303八~步骤 304入： CRF收到计费规则请求后， 根据该计费规 则请求中携带的输入信息， 还可根据 AF提供的相关输入信息， 选择适 当的计费规则，然后向 TPF返回提供计费规则（ Provision Charging Rules ) 消息， 该提供计费规则消息中可携带有选定的计费规则和计费规则操作 指示。
步骤 305A: TPF收到提供计费规则消息后，根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 306A〜步骤 307A: 当为在线计费时， TPF向 OCS发送信用请 求（ Credit Request ), 向 OCS请求 UE的信用。 OCS收到信用请求后， 确定 UE的信用， 然后向 TPF返回信用响应 （Credit Response ), 如果 OCS确定出 UE的信用， 则该信用响应中携带有 UE的信用 , 如果 OCS 未确定出 UE的信用， 则该信用响应中可携带有差错原因值。
步骤 308A: TPF收到信用响应后，向 UE返回承载建立响应（ Establish Bearer Service Accept ), 如果信用响应中携带有 UE的信用， 则 TPF接 受 UE发起的承载建立请求， 并继续后续的承载建立流程； 如果信用响 应中未携带有 UE的信用， 则拒绝 UE发起的承载建立请求。
图 3B为承载修改时下发计费规则流程图， 如图 3B所示， 承载修改 时下发计费规则的实现过程包括以下步骤：
步骤 30 IB: UE向 TPF发送承载修改请求（Modify Bearer Service Request ), 在 GPRS 网络中， 则是 GGSN收到 PDP Context更新请求 ( Update PDP Context Request )„
步骤 302B: TPF收到承载修改请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息。
步骤 303B〜步骤 304B: CRF收到计费规则请求后，根据该计费规则 请求中携带的输入信息， 还可根据 AF提供的相关输入信息， 选择适当 的计费规则， 然后向 TPF返回提供计费规则消息， 该提供计费规则消息 中可携带有选定的计费规则和计费规则操作指示。
步骤 305B: TPF收到提供计费规则消息后，根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 306B〜步骤 307B: 当为在线计费时， TPF向 OCS发送信用请 求， 向 OCS请求 UE的信用。 OCS收到信用请求后， 确定 UE的信用， 然后向 TPF返回信用响应， 如果 OCS确定出 UE的信用， 则该信用响 应中携带有 UE的信用， 如果 OCS未确定出 UE的信用， 则该信用响应 中可携带有差错原因值。
步驟 308B: TPF收到信用响应后，向 UE返回承载修改响应（ Modify Bearer Service Accept )， 如果信用响应中携带有 UE的信用， 则 TPF接 受 UE发起的承载修改请求， 并继续后续的承载修改流程； 如果信用响 应中未携带有 UE的信用， 则拒绝 UE发起的承载修改请求。
图 3C为承载删除时下发计费规则流程图， 如图 3A所示， 承载删除 时下发计费规则的实现过程包括以下步骤：
步驟 301C: UE向 TPF发送承载删除请求（ Remove Bearer Service Request ),在 GPRS网络中，则是 GGSN收到 Delete PDP Context Request 步骤 302C: TPF收到承载删除请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息。
步骤 303O步骤 304C: CRF收到计费规则请求后，根据该计费规则 请求中携带的输入信息， 还可根据 AF提供的相关输入信息， 选择适当 的计费规则， 然后向 TPF返回提供计费规则消息， 该提供计费规则消息 中可携带有选定的计费规则和计费规则操作指示。
步骤 305C: TPF收到提供计费规则消息后，根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 306O步骤 307C: 当为在线计费时， TPF向 OCS发送信用报 告（ Final Remaining Credit Report )， 通知 OCS为 UE建立的承载已经终 止， 该信用报告中携带有 UE的信用的使用情况， 如 UE使用分组数据 业务的时间长度、 使用分组数据的流量大小。 OCS收到信用报告后， 向 TPF返回信用 4艮告响应 （ Response )。
步骤 308C: TPF 收到信用报告响应后， 向 UE返回承载删除响应 ( Remove Bearer Service Accept ), 接受 UE发起的承载删除请求， 并继 续后续的承载删除流程。
图 4为 CRF主动向 TPF下发计费规则流程图， 如图 4所示， CRF 主动向 TPF下发计费规则的实现过程包括以下步骤：
步驟 401： CRF收到某个内部或外部的触发事件 ( Internal or External Trigger Event ), 以及与该事件相关的信息， 如 AF向 CRF发送计费规则 选择输入信息的事件。
步骤 402: CRF根据获取的输入信息选择适当的计费规则。 这些输 入信息可为 AF提供的计费相关输入信息， 例如， UE使用 AF提供的某 一业务， 该业务对计费有特殊要求， 如计费费率与其他业务的计费费率 不同， 因此， AF向 CRF提供与该业务相关的计费输入信息；也可为 TPF 提供的计费相关输入信息。
步驟 403: 如果计费规则发生变化， CRF向 TPF发送提供计费规则 消息， 该提供计费规则消息中可携带有选定的计费规则和计费规则操作 指示。
步骤 404: TPF收到提供计费规则消息后， 根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 405〜步骤 406: 当为在线计费时， TPF向 OCS发送信用请求， 向 OCS请求 UE的信用。 OCS收到信用请求后， 确定 UE的信用， 然后 向 TPF返回信用响应， 如果 OCS确定出 UE的信用， 则该信用响应中 . 携带有 UE的信用， 如果 OCS未确定出 UE的信用， 则该信用响应中可 携带有差错原因值。
由以上描述可见， 在 3GPP规范描述的在线计费实现过程中， TPF 在承载建立、 修改时， 会向 OCS请求 UE的信用， OCS会根据 TPF的 . 信用请求向其返回 UE的信用， 但是 3GPP规范并未对触发在线计费的 机制进行描述， 也没有对 TPF如何寻址到 UE的正确 OCS的过程进行 描述， 因此， 严重影响了整个在线计费实现过程的完整性和明确性。 同 样， 对于离线计费实现过程， 目前的 3GPP规范中也没有描述 TPF如何. 寻址到 UE的正确的 OCF, 严重影响了离线计费实现过程的完整性和明 确性。 发明内容
有鉴于此， 本发明的目的在于提供一种完善基于业务数据流计费的 处理方法， 对基于业务数据流计费的实现过程进行了完善， 进而使分组 数据业务计费的实现过程具有良好的完整性和明确性。
为了达到上述目的， 本发明提供了一种完善基于业务数据流计费的. 处理方法， 该方法包含步驟 Al: CRF向 TPF提供计费系统地址信息。
步骤 A1中所述计费系统地址信息为在线计费系统 OCS地址信息。 所述步骤 A1之前进一步包括： CRF根据收到的输入信息， 确定当 前分组数据业务的计费方式为在线计费。
所述步驟 A1之后进一步包括以下步骤： Bll、 TPF根据 OCS地址信息， 向所述 OCS请求信用；
Cll、 OCS向 TPF提供信用。
执行步驟 B11 中所述的向 OCS请求信用的同时进一步包括： TPF 向该 OCS提供用于确定信用的输入信息； 所述步骤 C11包括： OCS根 据所述输入信息， 确定信用， 然后向 TPF提供信用。
所述步骤 A1中包括： CRF向 TPF提供一个以上的 OCS地址信息， 并提供对应于各 OCS的选择优先权； 所述步驟 B11为： TPF根据 OCS 的选择优先权和 OCS地址信息， 首先向选择优先权最高的 OCS请求信 用， 如果信用请求不成功， 则依次根据选择优先权向 OCS请求信用， 直 至信用请求成功。
步骤 A1中所述 OCS地址信息为空时， 所述步驟 B11为： TPF根据 预先配置的 OCS地址信息， 向所述 OCS请求信用。
该方法进一步包括： CRF向 TPF发送在线计费指示。 所述 OCS地 址信息携带于在线计费指示中。
所述 OCS地址信息为 OCS中的信用控制功能实体 CCF地址信息。 所述 OCS地址信息存储于 CRF中。
所述步骤 A1之前进一步包括： CRF通过与网络实体的交互获取 OCS 地址信息。
步骤 A1中所述计费系统地址信息为离线计费功能实体 OCF地址信 所述步骤 Al之前进一步包括： CRF根据收到的输入信息， 确定当 前分组数据业务的计费方式为离线计费。
所述步骤 A1之后进一步包括：
B21、 TPF根据 OCF地址信息， 向所述 0CF发送统计的 UE的计费 数据信息。 所述步骤 A1中包括： CRF向 TPF提供一个以上的 OCF地址信息， 并提供对应于各 OCF的选择优先权； 所述步骤 B21为： TPF根据 OCF 的选择优先权和 OCF地址信息， 首先向选择优先权最高的 OCF发送统 计的 UE的计费数据信息， 如果发送不成功， 则依次根据选择优先权向 OCF发送统计的 UE的计费数据信息， 直至发送成功。
步骤 A1中所述 OCF地址信息为空时， 所述步骤 B21为： TPF根据 预先配置的 OCF地址信息， 向所述 OCF发送统计的 UE的计费数据信 ir 该方法进一步包括： CRF向 TPF发送离线计费指示。 所述 OCF地 址信息携带于离线计费指示中。 .
所述 OCF地址信息存储于 CRF中。
所述步骤 A1之前进一步包括: CRF通过与网络实体的交互获取 OCF . 地址信息。
所述网络实体为归属位置寄存器 HLR， 或归属用户服务器 HSS。 所述输入信息是由 AF向 CRF提供的。 所述输入信息是由 TPF向 CRF提供的。
本发明还提供了一种完善基于业务数据流计费的处理方法， 该方法 包含以下步骤：
A2、 CRF根据 AF提供的输入信息， 确定当前分组数据业务的计费 方式为在线计费或是离线计费；
B2、 CRF根据确定结果，向 TPF发送在线计费指示或离线计费指示。 如果 CRF向 TPF发送在线计费指示， 则所述步驟 B2进一步包括： CRF向 TPF提供 OCS地址信息。
步驟 A2中所述输入信息为分组数据业务标识。
本发明还提供了一种完善基于业务数据流计费的处理方法， 该方法 包含以下步骤：
A3、 CRF根据 TPF提供的输入信息， 确定当前分组数据业务的计 费方式为在线计费或是离线计费；
B3、CRF根据确定结果，向 TPF发送在线计费指示或离线计费指示。 如果 CRF向 TPF发送在线计费指示， 则所述步骤 B3进一步包括： CRF向 TPF提供 OCS地址信息； 如果 CRF向 TPF发送离线计费指示， 则所述步骤 B3进一步包括： CRF向 TPF提供 OCF地址信息。
步骤 A3中所述输入信息为用户设备标识。
根据本发明提出的方法， 计费实现过程中， CRF能够根据 AF提供 的输入信息，或是 TPF提供的输入信息确定出对于当前分组数据业务的 计费方式为在线计费或是离线计费， 进而向 TPF提供计费机制为 "在线 计费" 或是 "离线计费" 的计费规则。 另外， CRF会向 TPF提供对应于 UE的 OCS地址信息或是 OCF地址信息，从而使 TPF能够根据 OCS地 址信息寻址到相应 OCS，触发后续针对 UE的信用请求流程，或是使 TPF 能够根据 OCF地址信息寻址到相应 OCF, 将统计的 UE的计费数据信 息发送给 OCF, 使得基于 FBC机制的计费实现过程更为完整、 合理。 附图简要说明
图 1为 PDP Context激活、 传输数据、 去激活流程图；
图 2A为在线计费的 FBC系统结构示意图；
图 2B为离线计费的 FBC系统结构示意图；
图 3 A为承载建立时计费流程图；
图 3B为承载修改时计费流程图；
图 3C为承载删除时计费流程图；
图 4为 CRF主动向 TPF下发计费规则流程图； 图 5为本发明中承载建立时在线计费流程图；
图 6为本发明中 CRF主动向 TPF下发计费规则时离线计费流程图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚， 下面结合附图对本 发明作进一步的详细描述。
本发明中， 计费的实现过程中， 由 CRF向 TPF提供对应于 UE的 OCS地址信息或是 OCF地址信息， TPF根据 OCS地址信息或是 OCF 地址信息， 寻址到相应 OCS或是 OCF, 然后向相应 OCS请求 UE的信 用， 或是向相应 OCF发送统计的 UE的计费数据信息。
CRF 在确定某个分组数据业务的计费方式为在线计费之后， 会向 TPF提供计费规则， 并向 TPF提供在线计费指示和 OCS地址信息， 在 线计费指示用于通知 TPF该分组数据业务的当前计费方式为在线计费， OCS地址信息用于 TPF在向 OCS请求 UE的信用时，能够寻址到与 UE 相对应的 OCS。 OCS地址信息可携带在在线计费指示中。
同样的， CRF在确定某个分组数据业务的计费方式为离线计费之后， 会向 TPF提供计费规则，并向 TPF提供离线计费指示和 OCF地址信息， 离线计费指示用于通知 TPF该分组数据业务的当前计费方式为离线计 费， OCF地址信息用于 TPF在向 OCF发送统计的用户计费数据信息时， 能够寻址到与 UE相对应的 OCF。 OCF地址信息可携带在离线计费指示 中。
以上所述的 OCS地址信息可为 OCS中能够实现 UE的信用控制的 功能实体的地址信息， 例如， OCS中的 CCF ( Service Data Flow Based Credit Control Fxmction )是对 UE的信用进行管理和控制的功能实体， 因 此， OCS的地址信息可为 OCS中的 CCF( Service Data Flow Based Credit Control Function )地址信息。
CRF可根据 AF提供的输入信息， 确定当前分组数据业务的计费方 式是否为在线计费或是离线计费， 例如， CRF根据 AF提供的计费规则 输入信息中的业务标识， 确定当前分组数据业务的计费方式为在线计费 或是离线计费。 CRF也可根据 UE信息， 确定当前分组数据业务的计费 方式为在线计费或是离线计费，例如， CRF根据 TPF提供的计费规则输 入信息中的 UE标识确定该 UE的用户为预付费业务的用户，因此， CRF 确定当前分組数据业务的计费方式为在线计费； 又如， CRF根据 TPF提 供的计费规则输入信息中的 UE标识确定该 UE的用户为后付费业务的 用户， 因此， CRP确定当前分组釵据业务的计费方式为离线计费。
CRF中可存储有与 UE相对应的 OCS地址信息或是 OCF地址信息， 也可与网络中的其他实体进行交互，从而获取与 UE相对应的 OCS地址 信息或是 OCF地址信息， 例如， CRF通过与归属位置寄存器（HLR, Home Location Register )/归属用户月良务器（ HSS, Home Subscriber Server ) 的交互， 获取与 UE相对应的 OCS地址信息或是 OCF地址信息。
另外， 出于负荷分担的需要， 在同一个网络中可能有多个 OCS, 而 对于一个 UE可能与多个 OCS实体相对应 , 可设定多个 OCS的选择优 先权， 如优先选择的 OCS和第二选择的 OCS, CRF可向 TPF提供多个 与 UE相对应的 OCS地址信息， 即向 TPF提供 UE的优先选择的 OCS 地址信息（ primary OCS address )和第二选择的 OCS地址信息（ secondary OCS address )。 TPF根据 OCS的选择优先权， 与优先选择的 OCS之间 的信用请求对话建立失败后，可向第二选择的 OCS发起信用请求，请求 建立与第二选择 OCS之间的信用对话。
运营商也可以在 TPF中配置一个针对所有 UE的 OCS地址信息，这 样， 当 CRF没有向 TPF提供 OCS地址信息时， 即 CRF向 TPF提供的 OCS地址信息为空时， TPF向该配置的 OCS发送信用请求， 请求建立 与该配置的 OCS之间的信用对话。
同样的， 出于负荷分担的需要， 在同一个网络中可能有多个 OCF, 而对于一个 UE可能与多个 OCF实体相对应， 可设定多个 OCF的选择 优先权， 如优先选择的 OCF和第二选择的 OCF, CRF可向 TPF提供多 个与 UE相对应的 OCF地址信息，即向 TPF提供 UE的优先选择的 OCF 地址信息（ primary OCF address )和第二选择的 OCF ^址信息（ secondary OCF address )。 TPF根据 OCF的选择优先权， 与优先选择的 OCF之间 的 UE的计费数据信息传送失败后， 可向第二选择的 OCF发送 UE的计 费数据信息。
运营商也可以在 TPF中配置一个针对所有 UE的 OCF地址信息，这 样， 当 CRF没有向 TPF提供 OCF地址信息时， 即 CRF向 TPF提供的 OCF地址信息为空时， TPF向该配置的 OCF发送 UE的计费数据信息。
图 5为本发明中承载建立时在线计费流程图， 如图 5所示， 承载建 立时在线计费的实现过程包括以下步骤：
步骤 501 : UE向 TPF发送承载建立请求， 在 GPRS网络中， 则是 GGSN收到 Create PDP Context Request,,
步骤 502: TPF收到承载建立请求后， 向 CRF发送计费规则请求， 该计费规则请求中携带有供 CRF确定计费规则的输入信息。
步骤 503〜步骤 504: CRF收到计费规则请求后， 首先， 根据该计费 规则请求中携带的输入信息， 还可根据 AF提供的相关输入信息， 确定. 当前分组数据业务的计费方式为在线计费；其次，选择适当的计费规则， 并根据 UE信息确定与其相对应的 OCS的地址信息； 再次， 向 TPF返 回提供计费规则消息， 该提供计费规则消息中可携带有选定的计费规则 和计费规则操作指示， 并可进一步携带有在线计费指示和 OCS 地址信. 步骤 505: TPF收到提供计费规则消息后， 根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 506〜步骤 507: TPF根据在线计费指示确定需要向 OCS请求 UE的信用后， 根据 OCS地址信息， 向相应 OCS发送信用请求， 该信 用请求中携带有供 OCS确定信用的相关输入信息。 OCS收到信用请求 后，根据 TPF提供的输入信息确定 UE的信用， 然后向 TPF返回信用响 应， 如果 OCS确定出针对计费规则的 UE的信用， 则该信用响应中携带 有 UE的信用， 如果 OCS未确定出 UE的信用， 则该信用响应中可携带 有差错原因值。
步骤 508: TPF收到信用响应后， 向 UE返回承载建立响应， 如果信 用响应中携带有 UE的信用 , 则 TPF接受 UE发起的承载建立请求， 并 继续后续的承载建立流程； 如果信用响应中未携带有 UE的信用， 则拒 绝 UE发起的承载建立请求。
以上仅以承载建立时， 实现在线计费的过程为例对本发明进行了说 明， 在承载修改或承载删除时， 与承载建立实现在线计费的过程基本相 同， 不同之处仅在于传送的消息， 因此， 在此不再赘述。
另外， 对于离线计费时的承载建立、 承载修改和承载删除的实现过 程与上述的承载建立时在线计费的实现过程基本相同， 不同之处仅在于 CRF对当前分组数据业务的计费方式的判断结果为离线计费，传送的消 息中携带的地址信息为 OCF地址信息，以及省略后续的在线计费的信用 交互过程， 因此， 在此不再赘述。
图 6为本发明中 CRF主动向 TPF下发计费规则时离线计费流程图， 如图 6所示， CRF主动向 TPF下发计费规则时， 离线计费的实现过程包 括以下步骤： 步骤 601 : CRF收到某个内部或外部的触发事件（ Internal or External Trigger Event ), 以及与该事件相关的信息， 如 AF向 CRF发送计费规则 选择输入信息的事件。
步骤 602: CRF根据获取的输入信息， 确定当前分组数据业务的计 费方式为在线计费， 选择适当的计费规则， 并根据 UE信息确定与其相 对应的 OCS的地址信息。以上所述的输入信息可为 AF提供的计费相关 输入信息， 例如， UE使用 AF提供的某一分组数据业务， AF向 CRF提 供该业务的业务标识； 也可为 TPF提供的计费相关输入信息， 如 TPF 在计费规则请求中向 CRF提供的 UE标识。
步骤 603:根据接收的输入信息，如果 CRF确定计费规则发生变化， 如 CRF根据 AF提供的业务标识，确定当前分组数据的计费方式在线计 费， 需要实时扣除 UE使用该分组数据业务的费用， 又如 CRF根据 TPF 提供的 UE标识， 确定该 UE的用户属于后付费用户， UE使用所有分组' 数据业务的费用都可以在业务使用后再向 UE的用户收取，则 CRF选择 新的计费规则并向 TPF发送提供计费规则消息，该提供计费规则消息中 可携带有选定的计费规则和计费规则操作指示， 并可进一步携带有离线 计费指示和 OCF地址信息。
步骤 604: TPF收到提供计费规则消息后， 根据计费规则操作指示 对 CRF选定的计费规则进行相应操作。
步骤 605: TPF根据离线计费指示， 依据计费规则的过滤器（filter ) 信息统计 UE的计费数据信息， 然后根据 OCF地址信息， 向相应 OCF 发送统计的 UE的计费数据信息。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、 一种完善基于业务数据流计费的处理方法， 其特征在于， 该方法 包含：
Al、 计费规则功能实体 CRF向传输面功能实体 TPF提供计费系统 地址信息。
2、 根据权利要求 1所述的方法， 其特征在于， 步骤 A1中所述计费 系统地址信息为在线计费系统 OCS地址信息。
3、 根据权利要求 2所述的方法， 其特征在于， 所述步骤 A1之前进 一步包括： CRF根据收到的输入信息， 确定当前分组数据业务的计费方 式为在线计费。
4、 根据权利要求 2所述的方法， 其特征在于， 所述步驟 A1之后进 一步包括以下步骤：
Bll、 TPF根据 OCS地址信息， 向所述 OCS请求信用；
Cll、 OCS向 TPF提供信用。
5、 根据权利要求 4所述的方法， 其特征在于，
执行步骤 B11 中所述的向 OCS请求信用的同时进一步包括： TPF 向该 OCS提供用于确定信用的输入信息；
所述步骤 C11 包括: OCS ^^据所述输入信息， 确定信用， 然后向 TPF提供信用。
6、 根据权利要求 4所述的方法， 其特征在于，
所述步骤 A1中包括： CRF向 TPF提供一个以上的 OCS地址信息， 并提供对应于各 OCS的选择优先权；
所述步骤 B11为： TPF根据 OCS的选择优先权和 OCS地址信息， 首先向选择优先权最高的 OCS请求信用，如果信用请求不成功，则依次 根据选择优先权向 OCS请求信用， 直至信用请求成功。
7、根据权利要求 4所述的方法， 其特征在于， 步骤 A1中所述 OCS 地址信息为空时， 所述步骤 B11为： TPF 据预先配置的 OCS地址信 息， 向所述 OCS请求信用。
8、 根据权利要求 2所述的方法， 其特征在于， 该方法进一步包括： CRF向 TPF发送在线计费指示。
9、 根据权利要求 8所述的方法， 其特征在于， 所述 OCS地址信息 携带于在线计费指示中。
10、根据权利要求 2所述的方法， 其特征在于， 所述 OCS地址信息 为 OCS中的信用控制功能实体 CCF地址信息。
11、 根据权利要求 2所述的方法， 其特征在于， 所述 OCS地址信息 存储于 CRF中。
12、 根据权利要求 2所述的方法， 其特征在于， 所述步骤 A1之前 进一步包括： CRF通过与网络实体的交互获取 OCS地址信息。
13、 根据权利要求 1所述的方法， 其特征在于， 步驟 A1 中所述计 费系统地址信息为离线计费功能实体 OCF地址信息。
14、 根据权利要求 13所述的方法， 其特征在于， 所述步骤 A1之前 进一步包括： CRF根据收到的输入信息， 确定当前分组数据业务的计费 方式为离线计费。
15、 根据权利要求 13所述的方法， 其特征在于， 所述步骤 A1之后 进一步包括：
B21、 TPF根据 OCF地址信息， 向所述 OCF发送统计的 UE的计费 数据信息。
16、 根据权利要求 13所述的方法， 其特征在于，
所述步骤 A1中包括： CRP向 TPF提供一个以上的 OCF地址信息， 并提供对应于各 OCF的选择优先权；
所述步骤 B21为： TPF根据 OCF的选择优先权和 OCF地址信息， 首先向选择优先权最高的 OCF发送统计的 UE的计费数据信息，如果发. 送不成功，则依次根据选择优先权向 OCF发送统计的 UE的计费数据信 息， 直至发送成功。
17、 根据权利要求 13 所述的方法， 其特征在于， 步骤 A1 中所述 OCF地址信息为空时， 所述步骤 B21为： TPF根据预先配置的 OCF地. 址信息， 向所述 OCF发送统计的 UE的计费数据信息。
18、根据权利要求 13所述的方法，其特征在于，该方法进一步包括： CRF向 TPF发送离线计费指示。
19、 根据权利要求 18所述的方法， 其特征在于， 所述 OCF地址信 息携带于离线计费指示中。
20、 根据权利要求 13所述的方法， 其特征在于， 所述 OCF地址信 息存储于 CRF中。
21、 根据权利要求 13所述的方法， 其特征在于， 所述步骤 A1之前 · 进一步包括： CRF通过与网络实体的交互获取 OCF地址信息。
22、 根据权利要求 12或 21所述的方法， 其特征在于， 所述网络实 体为归属位置寄存器 HLR， 或归属用户服务器 HSS。
23、根据权利要求 3或 14所述的方法， 其特征在于， 所述输入信息 是由应用功能实体 AF向 CRF提供的。
24、根据权利要求 3或 14所述的方法， 其特征在于， 所述输入信息 是由 TPF向 CRF提供的。
25、 一种完善基于业务数据流计费的处理方法， 其特征在于， 该方 法包含以下步骤：
A2、 CRF根据 AF提供的输入信息， 确定当前分组数据业务的计费 方式为在线计费或是离线计费；
B2、 CRF根据确定结果，向 TPF发送在线计费指示或离线计费指示。
26、 根据权利要求 25所述的方法， 其特征在于， 如果 CRF向 TPF 发送在线计费指示， 则所述步骤 B2进一步包括： CRF向 TPF提供 OCS 地址信息。
27、 根据权利要求 25所述的方法， 其特征在于， 步骤 A2中所述输 入信息为分组数据业务标识。
28、 一种完善基于业务数据流计费的处理方法， 其特征在于， 该方 法包含以下步骤：
A3、 CRF根据 TPF提供的输入信息， 确定当前分组数据业务的计 费方式为在线计费或是离线计费；
B3、 CRF根据确定结果，向 TPF发送在线计费指示或离线计费指示。
29、 根据权利要求 28所述的方法， 其特征在于， 如果 CRF向 TPF. 发送在线计费指示， 则所述步骤 B3进一步包括： CRF向 TPF提供 OCS 地址信息。
30、 根据权利要求 28所述的方法， 其特征在于， 如果 CRF向 TPF 发送离线计费指示， 则所述步骤 B3进一步包括： CRF向 TPF提供 OCF 地址信息。
31、 根据权利要求 28所述的方法， 其特征在于， 步骤 A3中所述输 入信息为用户设备标识。
PCT/CN2005/000665 2004-05-12 2005-05-12 A processing method for perfect charging on line based on the service data stream WO2005109758A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP05745147A EP1746772B1 (en) 2004-05-12 2005-05-12 Service data flow based charging
DE602005013661T DE602005013661D1 (de) 2004-05-12 2005-05-12 Gebührenberechnung von Dienstdatenflüssen
US11/558,774 US8798575B2 (en) 2004-05-12 2006-11-10 Method for improving service data flow based charging and system thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2004100444333A CN1302636C (zh) 2004-05-12 2004-05-12 一种完善基于业务数据流在线计费的处理方法
CN200410044433.3 2004-05-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/558,774 Continuation US8798575B2 (en) 2004-05-12 2006-11-10 Method for improving service data flow based charging and system thereof

Publications (1)

Publication Number Publication Date
WO2005109758A1 true WO2005109758A1 (en) 2005-11-17

Family

ID=35320560

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000665 WO2005109758A1 (en) 2004-05-12 2005-05-12 A processing method for perfect charging on line based on the service data stream

Country Status (6)

Country Link
US (1) US8798575B2 (zh)
EP (1) EP1746772B1 (zh)
CN (1) CN1302636C (zh)
AT (1) ATE427603T1 (zh)
DE (1) DE602005013661D1 (zh)
WO (1) WO2005109758A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007095864A1 (en) * 2006-02-27 2007-08-30 Huawei Technologies Co., Ltd. Charging system and charging method

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1303781C (zh) * 2004-04-01 2007-03-07 华为技术有限公司 一种分组数据业务的计费控制方法
CN1859533A (zh) * 2006-03-20 2006-11-08 华为技术有限公司 电信业务计费系统和方法
CN101072170B (zh) * 2006-05-13 2010-06-23 华为技术有限公司 无线通讯网络中策略和计费规则功能网元的寻址方法
ATE449487T1 (de) * 2006-06-02 2009-12-15 Ericsson Telefon Ab L M Einrichtungen und verfahren zum garantieren einer dienstgüte pro dienstdatenfluss durch die trägerschicht
WO2008021514A2 (en) * 2006-08-17 2008-02-21 Neustar, Inc. System and method for managing domain policy for interconnected communication networks
CN101179402B (zh) * 2006-11-07 2010-09-22 中国电信股份有限公司 对于wcdma业务灵活选择服务在线计费系统的方法
US8077685B2 (en) * 2007-04-24 2011-12-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for avoiding hanging PDP contexts
US9681336B2 (en) * 2007-06-13 2017-06-13 Qualcomm Incorporated Quality of service information configuration
US20090190471A1 (en) * 2008-01-10 2009-07-30 Mahendran Arungundram C Method and Apparatus for Optimized Session Setup with Network-Initiated QoS Policy Control
DE102008024796A1 (de) 2008-05-23 2009-11-26 Deutsche Telekom Ag Verfahren zur Erkennung funktionsspezifischer Datenpakete
CN101431421B (zh) * 2008-11-29 2012-06-20 华为技术有限公司 在线控制业务的方法、内容计费网元和计费系统
US9184924B2 (en) * 2010-02-16 2015-11-10 Telefonaktiebolaget L M Ericsson (Publ) Nodes for communicating credit related information
US8831560B2 (en) * 2010-05-03 2014-09-09 Alcatel Lucent Charging method selection for service data flows based on the data services being requested
EP2466787A1 (en) * 2010-12-15 2012-06-20 Alcatel Lucent Dynamic policy-based charging system and method
EP2525526A1 (en) 2011-05-17 2012-11-21 Telefonaktiebolaget L M Ericsson AB (Publ) Prioritisation of charging in an IMS network
US9485105B2 (en) * 2011-11-15 2016-11-01 Deutsche Telekom Ag Method and telecommunications network utilizing more than one online charging system for a given user
US9848090B2 (en) * 2012-01-24 2017-12-19 Alcatel Lucent Offline charging per service data flow
CN103702306A (zh) * 2012-09-27 2014-04-02 阿尔卡特朗讯 一种在ocs计费失败时对用户设备进行计费的方法与设备
CN102938700A (zh) * 2012-10-12 2013-02-20 北京国电通网络技术有限公司 一种电力光纤到户业务的计费方法及装置
CN105900524B (zh) * 2014-03-04 2019-10-22 华为技术有限公司 一种计费会话管理方法、装置
US9826103B2 (en) * 2014-10-31 2017-11-21 Alcatel-Lucent Usa Inc. Offload of service charging from an online charging system
CN106465084B (zh) 2015-06-30 2020-02-21 华为技术有限公司 计费方法、网络设备及计费系统
CN105847614B (zh) * 2016-03-18 2019-11-12 深圳优克云联科技有限公司 一种计费、数据接入的方法、装置与系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0639013A1 (fr) * 1993-07-12 1995-02-15 France Telecom Procédé et dispositif d'analyse d'informations contenues dans des structures de données
CN1411305A (zh) * 2001-10-10 2003-04-16 英业达集团(上海)电子技术有限公司 用于移动通讯装置的处理系统及其方法
CN1429005A (zh) * 2001-12-25 2003-07-09 深圳市中兴通讯股份有限公司上海第二研究所 一种宽带网络认证、授权和计费的方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6834300B1 (en) * 2000-03-10 2004-12-21 Telefonaktiebolaget Lm Ericsson (Publ) Method in a packet data network of negotiating reporting mechanisms and reporting accounting records
US8699472B2 (en) * 2000-05-24 2014-04-15 Nokia Corporation Common charging identifier for communication networks
WO2003025809A2 (en) * 2001-09-21 2003-03-27 Telefonaktiebolaget Lm Ericsson (Publ) System and method for charging in a communication network and a communication network charging server
US20030152039A1 (en) * 2002-02-08 2003-08-14 Timothy Roberts Customer billing in a communications network
US7116968B2 (en) * 2002-04-25 2006-10-03 Nokia Corporation Method and network system for charging a roaming network subscriber
ATE405123T1 (de) * 2004-05-12 2008-08-15 Ericsson Telefon Ab L M Authentifizierungssystem

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0639013A1 (fr) * 1993-07-12 1995-02-15 France Telecom Procédé et dispositif d'analyse d'informations contenues dans des structures de données
CN1411305A (zh) * 2001-10-10 2003-04-16 英业达集团(上海)电子技术有限公司 用于移动通讯装置的处理系统及其方法
CN1429005A (zh) * 2001-12-25 2003-07-09 深圳市中兴通讯股份有限公司上海第二研究所 一种宽带网络认证、授权和计费的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007095864A1 (en) * 2006-02-27 2007-08-30 Huawei Technologies Co., Ltd. Charging system and charging method
US7860762B2 (en) 2006-02-27 2010-12-28 Huawei Technologies Co., Ltd. Charging system and charging method

Also Published As

Publication number Publication date
EP1746772A1 (en) 2007-01-24
US20070124160A1 (en) 2007-05-31
EP1746772B1 (en) 2009-04-01
CN1697390A (zh) 2005-11-16
ATE427603T1 (de) 2009-04-15
EP1746772A4 (en) 2007-05-09
DE602005013661D1 (de) 2009-05-14
US8798575B2 (en) 2014-08-05
CN1302636C (zh) 2007-02-28

Similar Documents

Publication Publication Date Title
WO2005109758A1 (en) A processing method for perfect charging on line based on the service data stream
US7889650B2 (en) Method for establishing diameter session for packet flow based charging
JP4402714B2 (ja) フローベース課金におけるイベント・トリガと再認証トリガを取り扱う方法
EP1760932A1 (en) A method for processing the online charging
EP1732264B1 (en) A method for controlling the charching of the packet data service
EP1804419B1 (en) A method for processing the re-authorisation based on the charging of the packet data flow
WO2005099184A1 (fr) Procede d'amelioration des regles de taxation dans des services de donnees par paquets et fonctionnement correspondant
WO2007143940A1 (fr) procédé, système et équipement de contrôle des conditions d'utilisation et de la facturation lorsque l'utilisateur est mobile
WO2005109748A1 (fr) Procede de selection de la regle de taxation destine a des utilisateurs
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2006050669A1 (fr) Procede de chargement en fonction d'un flux de paquets de donnees
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
WO2014107985A1 (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
WO2005101734A1 (fr) Procede de facturation de services de donnees par paquets et de controle d'acces de flux de donnees de services
WO2006060964A1 (fr) Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees
WO2006015543A1 (en) A processing method for re-authorization and re-authorization event and event triggers
WO2006050670A1 (fr) Procede de traitement de cle de taxation
WO2006015550A1 (fr) Procede de distribution du numero de dialogue du chargement fonde sur le flux de paquets de donnees

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

Country of ref document: EP

Ref document number: 11558774

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWP Wipo information: published in national office

Ref document number: 2005745147

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 11558774

Country of ref document: US