+

WO2006050669A1 - Procede de chargement en fonction d'un flux de paquets de donnees - Google Patents

Procede de chargement en fonction d'un flux de paquets de donnees Download PDF

Info

Publication number
WO2006050669A1
WO2006050669A1 PCT/CN2005/001897 CN2005001897W WO2006050669A1 WO 2006050669 A1 WO2006050669 A1 WO 2006050669A1 CN 2005001897 W CN2005001897 W CN 2005001897W WO 2006050669 A1 WO2006050669 A1 WO 2006050669A1
Authority
WO
WIPO (PCT)
Prior art keywords
crf
service
credit
user
ocs
Prior art date
Application number
PCT/CN2005/001897
Other languages
English (en)
Chinese (zh)
Inventor
Xiaoqin Duan
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.
Publication of WO2006050669A1 publication Critical patent/WO2006050669A1/fr

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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
    • 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
    • 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/73—Validating charges
    • 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/735—Re-crediting user
    • 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/20—Technology dependant metering
    • H04M2215/2026—Wireless network, e.g. GSM, PCS, TACS
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32—Involving wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
    • H04M2215/7072—Validate charges

Definitions

  • the present invention relates to the field of packet data charging, and more particularly to a processing method and system based on packet data flow charging. Background of the invention
  • FIG. 1 shows a packet data protocol context (PDP Context, Packet Data Protocol Context) activation, data transmission, deactivation flowchart, as shown in FIG. 1, in a general packet radio service (GPRS, General Packet Radio Service), activated
  • PDP Context the data interaction with the external packet data network (PDN, Packet Data Network)
  • PDN Packet Data Network
  • Step 101 The mobile terminal (MS) sends a PDP Context Request (Active PDP Context Request) to the Serving GPRS Support Node (SGSN), where the Activate PDP Context Request carries the network access layer service access point.
  • SGSN Serving GPRS Support Node
  • PDP Type Access Point Name
  • API Access Point Name
  • QoS Quality of Service
  • TI Transaction Identifier
  • the SGSN and the Gateway GPRS Support Node (GGSN) are used as part of the Tunnel Identifier (TID) to identify the PDP Context.
  • the PDP type includes the end-to-end protocol (PPP, Peer).
  • APN can be provided by the MS to the SGSN, and the SGSN is addressed to the corresponding GGSN according to the APN, and the GGSN The MS may not provide the APN to the SGSN according to the APN.
  • the SGSN may select the default APN according to the subscription information of the MS user.
  • the QoS parameter is the quality requirement of the packet data service specified by the MS.
  • TI is used by the MS to identify a PDP context.
  • Step 102 After receiving the Activate PDP Context Request, the SGSN performs security check and encryption with the MS. This step is optional.
  • Step 103 The SGSN parses the address information of the GGSN according to the APN. If the SGSN can parse the address information of the GGSN according to the APN, the TEID is created for the PDP Context, and the TEID can be an International Mobile Subscriber Identity (IMSI) and an NSAPI.
  • the SGSN sends a PDP Context Request to the GGSN.
  • the PDP Context Request contains the PDP type, PDP address, APN. QoS parameter, TEID, and selection mode.
  • the PDP address can be MS.
  • the IP address which is an optional parameter, may not carry a PDP address in the PDP Context creation request.
  • the GGSN may assign a DP address to the MS in the subsequent processing, or may allocate an IP to the MS by the PDN that finally establishes a connection with the MS. Address;
  • the selection mode refers to the APN selection mode, that is, whether the APN is selected by the MS or selected 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 MS.
  • Step 104 After receiving the PDP Context creation request, the GGSN determines the external PDN, then allocates a Charging ID, initiates charging, and negotiates QoS. If the GGSN can meet the quality of service requirements of the QoS parameter, the SGSN is sent to the SGSN.
  • the PDP Context Create Response (Representation PDP Context Response), which carries the TEID, the PDP address, the Backbone Bearer protocol, the agreed QoS parameters, and the Charging ID. If the GGSN cannot meet the quality of service requirements of the QoS parameters, the GGSN rejects the PDP Context creation request initiated by the SGSN. The SGSN then rejects the PDP Context activation request initiated by the MS.
  • Step 105 After receiving the PDP Context creation response, the SGSN inserts NSAPI and GGSN address information for identifying the PDP Context in the PDP Context, and selects a radio priority according to the agreed QoS parameter, and then returns a PDP Context activation response to the MS (Activate PDP Context Accept), the PDP Context activation response carries information such as PDP type, PDP address, TI, agreed QoS parameters, wireless priority, PDP configuration options, and the like. And, the SGSN starts charging.
  • the MS Upon receiving the PDP Context activation response, the MS has established a direct route between the MS and the GGSN, and can perform packet data transmission.
  • Step 106 The MS performs packet data interaction through the SGSN, the GGSN, and the PDN.
  • Step 108 After receiving the PDP Context deactivation request, the SGSN performs security check and encryption with the MS. This step is an optional step.
  • Steps 109 to 111 The SGS sends a PDP Context Request to the GGSN, where the PDP Context delete request carries ⁇ ).
  • the GGSN After receiving the PDP Context deletion request, the GGSN ends the charging of the MS, deletes the PDP Context corresponding to the TEID, and then sends a PDP Context Response (DDP) to the SGSN.
  • the PDP Context delete response carries the TEID.
  • the SGSN After receiving the PDP Context deletion response, the SGSN ends the charging of the MS, deletes the PDP Context corresponding to the TEID, and then sends a PDP Context Deactivation Response (Deactivate PDP Context Response) to the MS.
  • the PDP Context deactivation response carries the TL. After the MS receives the PDP Context deactivation response, it deletes the PDP Context corresponding to ⁇ .
  • the charging termination point is set in the PDP Context.
  • the charging termination point can only be charged according to the data traffic transmitted by the PDP Context, or according to the length of time the PDP Context is activated.
  • the MS can perform multiple services based on an activated PDP Context, that is, if the PDN can provide multiple services, such as an email (email) transceiver service, Based on the WAP (Wireless Application Protocol) browsing service and the file transfer protocol (FTP) file transfer service, the MS can pass an activated PDP after establishing a transmission channel with the PDN.
  • the Context carries various services that the PDN can provide.
  • the charging mode of the operator for various services is likely to adopt different charging methods. For example, for the email receiving and dispatching service, the charging and receiving events can be triggered based on the email, and the WAP browsing service can be used for the flow metering.
  • Fees, for the file transfer service can also be based on the flow rate, the WAP browsing service rate and the file transfer service rate are not the same, thus, according to the existing GPRS billing system, can not be the same PDP Context
  • the different services carried are differentiated and charged.
  • IP Flow IP Data streams
  • the IP data stream-based charging can be considered as filtering out the IP data streams of different services carried in the same PDP Context through some filter-like filters, and then separately filtering the data streams filtered by different filters.
  • the granularity of the IP data-based charging is much smaller than the charging granularity based on a PDP Context.
  • the granularity can be regarded as the size of the screening hole.
  • the charging granularity based on a PDP Context is a PDP Context.
  • the meshing granularity based on the IP data stream is a DP service data stream is a sieve hole, that is, a plurality of sieve holes are included for one PDP Context, and therefore, the charging and ratio based on the IP data stream is based on Compared to the charging of a PDP Context, the charging based on the EP data stream can provide a more abundant charging means for the operator or the service provider.
  • the 3GPP describes the system structure, functional requirements, and message interaction procedures of the FBC.
  • the FBC system structure supporting online charging is shown in Figure 2A.
  • the customized application based on mobile network enhanced logic (CAMEL, Customised Application for Mobile Network Enhanced Logic (SCP) Service Control Point (SCP) and Service Data Flow Based Credit Control Function (CCF) 202 constitute an online charging system (OCS, Online Charging System ) 206.
  • the CCF 202 communicates with the Service Data Flow Based Charging Rule Function (CRF) 203 through the Ry interface, and the CRF 203 communicates with the Application Function Entity (AF) through the Rx interface.
  • the CRF 203 communicates with the Traffic Plane Function (TPF) 205 through the Gx interface, and the CCF 202 communicates with the TPF 205 through the Gy interface.
  • CCF Service Data Flow Based Charging Rule Function
  • AF Application Function Entity
  • TPF Traffic Plane Function
  • the structure of the FBC system supporting offline charging is as shown in FIG. 2B.
  • the CRF 203 communicates with the AF 204 through the Rx interface
  • the CRJF 203 communicates with the TPF 205 through the Gx interface
  • the TPF 205 communicates with the charging gateway function entity through the Gz interface (CGF, Charging).
  • the Gateway Function 207 is interworking with the Charging Data Function (CDF).
  • the TPF 205 carries the DP data stream.
  • the TPF 205 sends a charging rule request to the CP 203 through the Gx interface, where the charging rule request carries information related to the user and the MS, bearer characteristics, and Network related information, etc., wherein the information related to the user and the MS may be a mobile station international number (MSISDN), an international mobile subscriber identity (SI), etc., and the network related information may be a mobile network coding (MNC), a mobile country. Code (MCC), etc.
  • MSISDN mobile station international number
  • SI international mobile subscriber identity
  • MNC mobile network coding
  • MCC mobile country. Code
  • the charging rules may be different, such as the corresponding rate of the QoS parameter falling. Also fell.
  • the TPF 205 may re-send the charging rule request to the CRP 203 to request a new charging rule when the bearer is modified; the CRF 203 selects an appropriate charging rule according to the above input information provided by the TPF 205, and returns to the TPF 205.
  • the selected charging rule includes the charging mechanism, the charging type, the charging key, the service data stream filter, and the charging rule priority.
  • the charging mechanism may be online charging or offline charging; the charging type may be charging based on the length of time or based on data traffic; the charging button is a parameter related to the rate, and the CRF 203 may not be directly
  • the rate is provided to the TPF 205, and only the rate-related parameters are provided to the TPF 205; the service data filter is used to indicate which BP data streams the TPF 205 filters, and then the TPF 205 filters the filtered IPs according to the charging rules.
  • the data stream is billed.
  • the service data filter may include an IP5 tuple, and the EP5 tuple may include source/destination IP address, source/destination port number (Port Number), protocol identifier (Protocol ID), and the like.
  • CRF 203 indicates TPF 205 to source address. Filters the IP data stream of 10.0.0.1, the destination address is 10.0.0.2, the source/destination port number is 20 f , the protocol type is Transmission Control Protocol (TCP), and the filtered BP data stream is filtered according to the charging rule. Billing.
  • TCP Transmission Control Protocol
  • the CRP 203 may provide a trigger event (Event Trigger) to the TPF 205 to request the TPF 205 to request a new charging rule from the CRP 205 when a specific event occurs, such as the CRP 203 requesting the TPF 205 to perform an event modification on some bearers.
  • Event Trigger a trigger event
  • Trigger events can be thought of as events related to billing rules.
  • the 3GPP specification describes the charging mode of the CRF that controls the TPF through the triggering event reporting mechanism, that is, the TPF reports the triggering event to the CRP, and the CRF learns the change of the bearer through the triggering event reported by the TF, and then determines the corresponding The charging rule is delivered to the TPF.
  • Trigger events defined in the 3GPP specifications may include: Common Land Mobile Communication Network (PLMN) changes (PLMN) Change event, QoS changes event, radio access technology (RAT) type change (RAT type change) event, transport stream template (TFT) change (TFT change) event.
  • PLMN Common Land Mobile Communication Network
  • RAT radio access technology
  • TFT transport stream template
  • the CRF 203 may also select an appropriate charging rule based on the input information of the AF 204 or the OCS 206, such as the AF 204 notifying the CRF 203 of the current use by the user.
  • the service type, CRP 203 selects the corresponding charging rule according to the service type.
  • the OCS 206 is composed of two functional entities, SCP 201 and CCF 202, wherein the CCF 202 is a functional entity that performs credit control, and is applied only to an online charging system, which can be added to the existing OCS 206. New features are implemented.
  • the CCF 202 manages and controls the user credit.
  • the CCF 202 authenticates the credit in the user's credit pool, and delivers the user to the TPF 205 through the Gy interface. credit.
  • the OCS 206 may request the TPF 205 to re-assert the user when the re-authorisation triggers occur, and then the OCS 206 re-authenticates the user according to the corresponding re-authentication event reported by the TPF 205, and It is possible to recalculate the user's credit. For example, after the user credit provided by the OCS 206 to the TPF 205 is used, the TPF 205 needs to report the allowed user credit usage expiration event to the OCS 206 according to the allowed credit expiration event in the re-authentication event, and the OCS 206 according to the remaining user account. Information, recalculate the credits allowed to be used by the user.
  • the OCS 206 determines the rate according to the current location of the user, and calculates the credit of the user according to the rate; when the user moves to another location, such as the PLMN changes, TPF 205 is required to report the occurrence of the PLMN change event to the OCS 206 according to the PLMN change event in the re-authentication event, and the OCS 206 re-determines the rate according to the current location of the user, and recalculates the user's credit.
  • the OCS 206 determines the rate according to the current QoS parameters of the service used by the user, when the user performs the QoS parameter
  • the TPF 205 needs to report the occurrence of the bearer modification event to the OCS 206 according to the bearer modification event in the re-authentication event.
  • the OCS 206 determines the rate according to the modified QoS parameter of the user, and recalculates the credit of the user.
  • the 3GRP specification also describes the use of the re-authentication event by the OCS to control the credit usage of the TPF. That is, the TPF reports the re-authentication event reported by the TCS to the OCS after the re-authentication event occurs.
  • the credit usage of the user and the change of the bearer are known, and the credit of the user is recalculated and sent to the TPF.
  • the re-authentication event defined in the 3GPP specifications may include: a credit authorization lifetime expiry event, a user idle state timeout event, a charging rule is changed event, a PLMN change event, a QoS Parameter change event, RAT type change event.
  • the TPF 205 is a GGSN
  • the AF is a service gateway or a service server in the PDN
  • the CRF 203 is a new logical entity.
  • TPF 205 is the enforcement point of the charging rule
  • CRP 203 is the control point of the charging rule.
  • the charging information collection point in the case of offline charging is TPF, and the TPF collects information for the service data stream, such as the data traffic transmitted by the service data stream, the length of time used by the service data stream, etc., and then generates Billing information, and the billing information is sent to the billing center via CGF/CDF 207;
  • the billing information collection point in the case of online billing is TPF and OCS, and the TPF collects information for the service data stream, and the meter
  • the fee information is sent to the billing center via the CGF/CDF, and the OCS collects the charge deduction information, and then generates the billing information, and sends the billing information to the billing center via the CGF/CDF.
  • the operator usually charges the user two kinds of communication fees and service charges, and the communication fee is used to measure the network resources occupied by the user, which is also called the traffic fee or the bearer fee.
  • the business expense is used to measure the business information of the user using the service. It is also called content fee or information fee.
  • the user passes the mobile terminal
  • "watching TV, business operators not only need to charge users to use the "watch TV” business process, the data traffic caused by the transmission of services or the length of time used to use the service, but also need to charge the user to watch the TV
  • the operator not only needs to charge the user for the fee generated by the data flow during the download of the game, but also needs to charge the user for the user to purchase the game.
  • business applications such as TV programs and games can be developed by a dedicated service provider (SP) and provide various business applications to users through cooperation with network operators.
  • SP can directly charge the user for the service fee
  • the SP needs to establish a channel for charging the user for the service fee, such as a billing system, but the method of using the SP to establish the billing system on its own will increase the cost of the SP and improve the cost.
  • the threshold of the SP is not conducive to the SP itself; on the other hand, the SP itself needs to solve the trust problem of the SP by the user to establish the charging system. Therefore, most network operators currently charge the service fee instead of the SP, and perform the same with the SP.
  • the charging mode of business cost sharing such as China Mobile's "Mobile Monternet” platform and China Unicom's "Unicom Unlimited” is a platform that integrates SPs and provides unified billing.
  • the network operator can focus on the operation of the network only.
  • the SP can focus on the development of the business application only.
  • the user only needs to face a unified charging system and one at the same time.
  • User bills for communication charges and business expenses.
  • the TPF cannot know the information about the success or failure of the service, for example, for the download service, if an abnormal interruption occurs during the download process. At this time, only the communication fee should be charged, and the business fee should not be charged; 'And TPF cannot know the user's subscription service. For example, the charging method used by a user when ordering a service is the monthly subscription. Billing, TPF cannot know that the user's business expenses should be deducted uniformly every month, but not every time the user uses the business. Therefore, based on the current FBC system structure, the charging of business expenses cannot be realized, and the requirements for business operations in the network cannot be met. Summary of the invention
  • an object of the present invention is to provide a processing method based on packet data flow charging, and another object of the present invention is to provide a system based on packet data flow charging, which satisfies service operation in a network. Claim.
  • the present invention provides a processing method based on packet data flow charging, the method comprising: a CRF sends a credit request to an OCS, and the OCS returns a credit response to the CRF
  • the credit response carries information on whether the credit line or the credit line is sufficient.
  • the method further includes: the CRF rolls back the credit line that needs to be replenished to the OCS, and the OCS replenishes the received credit line to the user's account.
  • the OCS receives the credit line that needs to be replenished, and then further includes: The OCS returns a response to the CRP for notifying the CRF that the credit line that needs to be replenished has been received.
  • the present invention also provides a processing method based on packet data flow charging, the method comprising: the AF notifying the CRF user to request to use the service, the CRF determining whether to allow the user to use the service according to the service subscription information, and if so, notifying the A to provide the user with the service The service; otherwise, the notification AF does not provide the service to the user.
  • the service subscription information is provided by the AF to the CRF when the user subscribes to the service.
  • the CRF After receiving the service subscription information provided by the AF, the CRF further includes: the CRF returns a response to the AF for notifying that the AF has received the service subscription information.
  • the notification AF provides the user with the service, and further includes: collecting the CRF start billing information.
  • the notification AF provides the user with the service, and then further includes the step al: AF notifying the CRJF user of the service usage.
  • the step a1 further includes: the CRF returns to the AP to notify the AF that it has received Response to business usage.
  • the step al further includes the step bl: CRP stops collecting the charging information.
  • the step bl further includes: the CRJF sending the charging information to the CDF/CGF.
  • the notification AF provides the user with the service, and further includes: the CRF sends a credit request to the OCS, and the OCS returns a credit response to the CRJF.
  • the step al further includes: the CRJF rolls back the credit amount to be replenished to the OCS, and the OCS replenishes the received credit line to the user's account.
  • the present invention further provides a system for charging based on packet data stream, the system comprising: a CRF connected to a TPF, configured to enable a CRF to provide a charging rule to the TPF, and the TPF is connected to the CDF/CGF,
  • the TPF provides charging information corresponding to the bearer to the CDF/CGF;
  • the AF is connected to the CR for transmitting service related information, and the CRF is connected to the CDF/CGF, and the CRF is provided with the corresponding service to the CDF/CGF.
  • Fee information is provided.
  • the CRF is connected to the CDF/CGF via an Rz interface.
  • the system further includes: an OCS, connected to the TPF, for providing credit information to the TPF according to the request of the TPF; and connected to the CRF for providing credit information to the CRF according to the request of the CRF.
  • OCS connected to the TPF, for providing credit information to the TPF according to the request of the TPF
  • CRF for providing credit information to the CRF according to the request of the CRF.
  • the charging information collection function is added in the CRF, and the interaction process between the CRJF and the OCS is increased, so that the OCS can provide credit information to the CRP according to the CRF credit request, such as a specific credit limit and credit limit. Whether the information is sufficient or not can also enable the CRF to return the credit line to be replenished to the OCS, and the OCS will replenish the corresponding credit limit to the user's account; and increase the interaction process between the CF and the AF, so that the CRF can know the user's order.
  • the situation of the business and the ability to know the success or failure of the business.
  • the signaling interface between the CF and the CDF/CGF is added, so that the CRP can report the charging information generated by the online charging or the offline charging to the charging center through the CDF/CGF.
  • FIG. 1 shows a PDP Context activation, data transmission, deactivation flowchart
  • FIG. 2A shows a schematic structural diagram of an FBC system supporting online charging
  • 2B is a schematic structural diagram of an FBC system supporting offline charging
  • FIG. 3A is a schematic diagram showing a process for implementing CRF requesting credit information from an OCS in the present invention
  • FIG. 3B is a schematic diagram showing a process for implementing CRF to OCS replenishment credit line in the present invention
  • FIG. 4A is a view showing a CRF obtaining user through AF in the present invention
  • FIG. 4B is a schematic diagram showing the process of realizing the use of the service by the CRF through the AF in the present invention
  • FIG. 5A is a schematic structural diagram of an FBC system supporting online charging in the present invention
  • FIG. 5B is a schematic structural diagram of an FBC system supporting offline charging in the present invention
  • FIG. 6 is a schematic diagram showing an implementation process of the first embodiment of the present invention. ;
  • FIG. 7 is a schematic diagram showing the implementation process of the second embodiment of the present invention. Mode for carrying out the invention
  • the charging information collection function is added in the CRF, and the interaction process between the CRF and the OCS is increased, so that the OCS can provide credit information to the CRF according to the CRF credit request, such as whether the specific credit limit and the credit limit are sufficient.
  • the information can also enable CRP to 'return the credit line to be replenished to the OCS, and OCS will replenish the corresponding credit limit to the user's account; and increase the interaction process between CRF and AF, so that CKF can know the user subscription.
  • the signaling interface between the CRF and the CDF/CGF enables the CRF to report the charging information generated by the online charging or offline charging to the charging center through the CDF/CGF, thereby implementing the structure based on the FBC system.
  • the collection of business expenses meets the requirements for business operations in the network. '
  • FIG. 3A is a schematic diagram of a process for implementing CRJF requesting credit information from an OCS in the present invention.
  • the process for requesting CRP to request credit information from an OCS includes the following steps: Step 301A to Step 302A: CR sends a credit request to the OCS ( Credit Request), the credit request carries user identification, business information, rate information, and the like for the OCS to determine the input information of the credit information.
  • OCS After receiving the credit request, OCS returns a credit response (Credit Response) to the OCS, and the credit response carries credit information, such as information such as the user credit limit calculated by the OCS and whether the credit limit is sufficient.
  • Credit Request Credit Request
  • the credit request carries user identification, business information, rate information, and the like for the OCS to determine the input information of the credit information.
  • OCS After receiving the credit request, OCS returns a credit response (Credit Response) to the OCS, and the credit response carries credit information, such as information such as the user
  • the CRF can return the credit amount to be replenished to the OCS, and the OCS will replenish the corresponding credit limit to the user's account.
  • FIG. 3B is a schematic diagram showing the process of implementing the CRF to the OCS credit line in the present invention.
  • the process of implementing the CRF to the OCS credit line includes the following steps: Step 301B to Step 302B: CF sends a credit to the OCS.
  • a credit return message which carries information such as a user identifier, business information, and a credit line that needs to be replenished.
  • OCS After receiving the credit replenishment message, OCS will replenish the credit line to be replenished to the user's account, and then return a response (Ack) to the CRF to inform CR that the corresponding credit line has been replenished.
  • the credit line that needs to be replenished as described above may be the remaining credit line after consuming the credit line allocated by the OCS, or may be the entire credit limit of the CRF request.
  • the application scenario of the CRF replenishing the credit line process to the OCS may be: when the business use is unsuccessful, the credit line is not consumed, and the CRF returns all the requested credit lines to the OCS, or the credit line is not After the consumption is completed, the CRP only returns the unconsumed remaining credit line to the OCS, and then the OCS will replenish the received credit line to be replenished to the user's account.
  • the application scenario of the CRF to the OCS credit limit process may also be: When the service is successfully used, if the requested credit limit has not been exhausted, the CRF needs to roll back the unused credit line to the OCS, and then the OCS will receive The credit line to be replenished is replenished to the user's account.
  • FIG. 4A shows a schematic diagram of the implementation process of the user service subscription by the CRF in the present invention.
  • the implementation process of the CRF to learn the user service subscription through the AF includes the following steps:
  • Step 401 to step 402 When the user subscribes to the service, the AF sends a service subscription message (Subscribed Info) to the CRF, where the service subscription message carries service subscription information, such as user identification, service information, and charging mode, and the charging mode. It can be used for monthly billing, billing by number, billing by number, billing by page, and so on.
  • the CRF After receiving the service subscription message, the CRF stores the subscription information and can further return a response to the AF, informing the AF that it has received the service order information it sent.
  • FIG. 4B is a schematic diagram showing the process of implementing the service usage of the CRF through the AF in the present invention.
  • the implementation process of the CRJF learning the service usage by using the AF includes the following steps:
  • Step 401B The AF sends a service start message (Service Start) to the CRF, where the service start message carries the user identifier, the service information, and the like, and notifies the CRJF user to start using the corresponding service.
  • Service Start a service start message
  • Step 402B The CRF determines whether the user can use the corresponding service according to the previously obtained service subscription information. If the user can use the corresponding service, in the case of offline charging, the service continues to send a service continuation message (Service Continue) to the AF, and then records related information. If the collection of billing information is started, step 403B may be subsequently performed; in the case of online billing, CR interacts with the OCS to obtain a corresponding credit line, if the OCS provides a credit limit or returns a credit. If sufficient information is available, the CRF sends a service continuation message to A, and then records relevant information, such as starting the collection of the charging information, and subsequently performing step 403B.
  • Service Continue service continuation message
  • the CKF sends the information to the AF.
  • a service termination message (Service Terminate), which may carry a termination reason. If the user is unable to use the corresponding service, the CRF sends a service termination message to the AF, and the service termination message may carry a termination reason.
  • Step 403B If the user successfully uses the service, the AF sends a service success message (Service Success) to the CRF, and the CRF user is successfully used to use the service. If the user fails to use the service, the service failure message is sent to the CRF. Service Failure), informing the CRP user that the service failed.
  • Service Success a service success message
  • Step 404B After receiving the service success/failure message, the CRF ends the collection of the charging information, and may further return a response to the AF, and notify the AF that the user's service usage is known.
  • the CRP can return the unused credit limit to the OCS.
  • the CF can roll back to the OCS.
  • the credit line that needs to be replenished the OCS will replenish the credit line to be replenished to the user's account; after the CRF receives the service failure message, the credit line is not consumed, and the CRF will refund all the requested credit lines.
  • the CRF only returns the unconsumed credit line to the OCS, and the OCS then replenishes the credit line to be replenished to the user's account.
  • FIG. 5A is a schematic diagram showing the structure of an FBC system supporting online charging in the present invention.
  • the CRF 203 in the case of online charging, the CRF 203 is connected to the CDF/CGF 207 through the Rz interface, and the CRF 203 is used for charging.
  • the information is sent to the CDF/CGF 207, and then the billing information provided by the CRF 203 is reported to the billing center by the CDF/CGF 207, thereby realizing the charging of the service fee based on the FBC system structure in the online case.
  • FIG. 5B is a schematic diagram showing the structure of the FBC system supported by the present invention.
  • CRF 203 in the case of offline charging, CRF 203 is connected to CDF/CGF 207 through the Rz interface, CRF 203 is used to send charging information to CDF/CGF 207, and then CDF/CGF 207 provides the meter provided by CRF 203.
  • the fee information is reported to the billing center, thereby realizing the charging of the business fee based on the FBC system structure under the online situation.
  • connection between the CRF and the CDF/CGF is not limited to being connected through the Rz interface, and other connection methods may be used, such as being indirectly connected through other functional entities.
  • the charging information collection point for service charging is CRP.
  • the CRF collects information for service usage, and then generates charging information, and the charging information is transmitted via CGF/.
  • the CDF 207 is sent to the billing center to collect the business charges based on the FBC system structure.
  • FIG. 6 is a schematic diagram of an implementation process of the first embodiment of the present invention.
  • the specific implementation process of the CRF as the offline charging information collection point in the embodiment includes the following steps: Step 601 to Step 603: AF receives The user subscribes to a service (Subscribe to a Service), and learns that the user subscribes to a certain service, and then sends a service subscription message to the CRF, where the service subscription message carries service subscription information, such as user identification, service information, and charging mode.
  • the billing mode can be monthly billing, billing by number, billing by number, billing by page, and so on.
  • the CRF stores the subscription information and can further return a response to the AF, informing the AF that it has received the service order information sent by it.
  • Step 604 to step 605 After receiving the service request (Service Request) sent by the user, the AF sends a service start message to the CRF, where the service start message carries the user identifier, the service information, and the like, and notifies the CRJF user to start using the corresponding service.
  • Service Request Service Request
  • the AF After receiving the service request (Service Request) sent by the user, the AF sends a service start message to the CRF, where the service start message carries the user identifier, the service information, and the like, and notifies the CRJF user to start using the corresponding service.
  • Step 606 to step 607 The CRF determines whether the user can use the corresponding service according to the previously obtained service subscription information. If yes, sends a service continuation message to the AF, and then records related information, such as collecting charging information, and the AF receives the CRF. After the sent service continues the message, the service acceptance message is returned to the user, and the user is notified that the service request has been accepted, and the subsequent Step 608; Otherwise, the CRF sends a service termination message to the AF, and the service termination message may carry a termination reason. After receiving the service termination message sent by the CRF, the AF sends a service rejection message to the user, where the service rejection message can be carried. There is a reason for rejection.
  • Step 608 to step 609 If the user successfully uses the service, the AP sends a service success message to the CF to notify the CRF user to successfully use the service. If the user fails to use the service, the AP sends a service failure message to the CRF. The CRP user failed to use the service. After receiving the service success/failure message, the CRF ends the collection of the accounting information, and further returns a response to the AF, notifying the AF that the user's service usage is known.
  • the CRF generates charging information related to the service usage, and reports the charging information to the charging center through the CDF/CGF, and the charging center generates a business expense list related to the service usage situation for the user.
  • FIG. 7 is a schematic diagram of the implementation process of the second embodiment of the present invention. As shown in FIG. 7, the specific implementation process of the CRF as the online charging information collection point in the embodiment includes the following steps: Step 701 to Step 705 and Step 601 ⁇ Steps are the same according to 605.
  • Step 706 to step 707 The CR determines whether the user can use the corresponding service according to the previously obtained service subscription information. If yes, the OCS sends a credit request, where the credit request carries the user identifier, the service information, the rate information, etc. for the OCS. After determining the input information of the credit information, the OCS returns a credit response to the OCS after receiving the credit request, and the credit response carries the credit information, such as the credit quota calculated by the OCS, whether the credit quota is sufficient, etc.; otherwise, directly executing step 708
  • the service termination message is sent to the AF, and the service termination message may carry a termination reason.
  • Step 708 to step 709 If the OCS provides the credit limit or returns the credit sufficient information, the CRP sends a service continuation message to the AF, and then records relevant information, such as collecting the collection of the charging information, and the AF receives the service continuation message sent by the CR.
  • the CRF After returning a service acceptance message to the user, notifying the user that the service request has been accepted, and subsequently performing step 710; if OCS If the credit limit is not provided or the credit deficiency information is returned, and the user is unable to use the corresponding service, the CRF sends a service termination message to the AF, and the service termination message may carry the termination reason, and after the AF receives the service termination message sent by the CR, A service rejection message is sent to the user, and the service rejection message may carry a reason for rejection.
  • Step 710 to step 711 are the same as steps 608 to 609.
  • the CRP In the case of online charging, when the service is successful, if the credit limit has not been used or the service fails, the CRP also needs to return the credit limit that needs to be replenished to the OCS, that is, the CRF sends a credit replenishment message to the OCS, in the credit replenishment message. User identification, business information, credit lines that need to be replenished, etc. After receiving the credit replenishment message, OCS will need to replenish the credit line, and then return a response (Ack) to CRP to inform CRF that the corresponding credit line has been replenished.
  • Ack response
  • the CRF generates charging information related to the service usage, and reports the charging information to the charging center through the CDF/CGF, and the charging center generates a business expense list related to the service usage situation for the user.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé qui consiste: à effectuer un chargement en fonction d'un flux de paquets de données; à ajouter une fonction de collecte d'informations de chargement à une fonction de règle de chargement (CRF); à augmenter le flux communications entre le CFR et un système de chargement en ligne (OCS); à permettre au OCS de fournir des informations de crédit au CRF en fonction d'une demande de crédit du CRF, par exemple, une ligne spécifique de crédit si la ligne de crédit est suffisante, le CRF pouvant renvoyer la ligne de crédit remboursable au OSC, et l'OCS pouvant rembourser la ligne de crédit correspondant à un compte utilisateur; et à augmenter le flux de communications entre le CRF et AF, le CRF pouvant connaître le service souscrit par l'utilisateur et si ce service a été réussi. L'invention concerne en outre un système permettant d'effectuer un chargement en fonction d'un flux de paquets de données, d'augmenter une interface de signalisation entre le CRF et CDF/CGF, d'effectuer un compte-rendu d'informations généré par le CRF sur l'état en ligne ou hors ligne vers le centre de chargement via le CDF/CGF de sorte que le chargement de service en fonction d'une structure de système FBC est effectué et la demande d'exécution du service dans le réseau est satisfaite.
PCT/CN2005/001897 2004-11-10 2005-11-10 Procede de chargement en fonction d'un flux de paquets de donnees WO2006050669A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2004100909294A CN100527676C (zh) 2004-11-10 2004-11-10 一种基于分组数据流计费的处理方法及系统
CN200410090929.4 2004-11-10

Publications (1)

Publication Number Publication Date
WO2006050669A1 true WO2006050669A1 (fr) 2006-05-18

Family

ID=36336213

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001897 WO2006050669A1 (fr) 2004-11-10 2005-11-10 Procede de chargement en fonction d'un flux de paquets de donnees

Country Status (2)

Country Link
CN (1) CN100527676C (fr)
WO (1) WO2006050669A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8489756B2 (en) 2009-08-07 2013-07-16 Huawei Technologies Co., Ltd. Method, apparatus, and system for releasing resources
US9215333B2 (en) 2012-01-27 2015-12-15 Alcatel Lucent Charging of calls in a communication network

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101237328B (zh) * 2007-01-30 2012-07-04 朗迅科技公司 为离线收费系统配置自适应模块的方法
CN101488864B (zh) * 2008-01-14 2011-12-21 朗讯科技公司 用于通信网络的计费系统和计费方法
CN101277204B (zh) * 2008-04-23 2011-04-20 中兴通讯股份有限公司 基于多个业务会话的信用控制方法
CN101316175B (zh) * 2008-06-11 2011-03-02 中兴通讯股份有限公司 在线计费方法
CN101877843B (zh) * 2009-04-28 2012-09-05 华为软件技术有限公司 业务数据处理方法、装置及系统
CN102056117B (zh) * 2009-11-03 2015-08-12 中兴通讯股份有限公司 基于策略和计费控制架构的计费方法与系统
CN102111742B (zh) * 2011-02-22 2014-04-16 中国联合网络通信集团有限公司 分组域业务计费方法及系统
CN102957543B (zh) * 2011-08-22 2016-08-17 中国电信股份有限公司 针对时长用户的基于流的计费方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004012389A1 (fr) * 2002-07-26 2004-02-05 Telefonaktiebolaget Lm Ericsson (Publ) Comptage differencie dans un reseau de paquets de donnees
WO2004036890A1 (fr) * 2002-09-20 2004-04-29 Nokia Corporation Procede de facturation de donnees atteignant un element de reseau d'un reseau de communications pendant une session de donnees
WO2004036825A1 (fr) * 2002-10-15 2004-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Systeme assurant un chargement souple dans un reseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004012389A1 (fr) * 2002-07-26 2004-02-05 Telefonaktiebolaget Lm Ericsson (Publ) Comptage differencie dans un reseau de paquets de donnees
WO2004036890A1 (fr) * 2002-09-20 2004-04-29 Nokia Corporation Procede de facturation de donnees atteignant un element de reseau d'un reseau de communications pendant une session de donnees
WO2004036825A1 (fr) * 2002-10-15 2004-04-29 Telefonaktiebolaget Lm Ericsson (Publ) Systeme assurant un chargement souple dans un reseau

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8489756B2 (en) 2009-08-07 2013-07-16 Huawei Technologies Co., Ltd. Method, apparatus, and system for releasing resources
US9215333B2 (en) 2012-01-27 2015-12-15 Alcatel Lucent Charging of calls in a communication network

Also Published As

Publication number Publication date
CN100527676C (zh) 2009-08-12
CN1773922A (zh) 2006-05-17

Similar Documents

Publication Publication Date Title
US7889650B2 (en) Method for establishing diameter session for packet flow based charging
US20070185809A1 (en) Method and system for processing online charging
US8798575B2 (en) Method for improving service data flow based charging and system thereof
US8238873B2 (en) Method and system for charging control
JP2013504909A (ja) 通信ネットワークにおいて、エンドユーザのアカウント残高およびサービス・サブスクリプション・レベルに従って動的ポリシー・ルールをエンドユーザに配信する方法
EP1622304B2 (fr) Procede pour la selection d'une regle de facturation pour un abonne
WO2005096547A1 (fr) Procede permettant de commander la facturation d'un service de commutation de paquets
JP4402714B2 (ja) フローベース課金におけるイベント・トリガと再認証トリガを取り扱う方法
WO2006050669A1 (fr) Procede de chargement en fonction d'un flux de paquets de donnees
EP1804419B1 (fr) Procede de traitement de reautorisation a base de taxation du flux de donnees par paquets
WO2005099184A1 (fr) Procede d'amelioration des regles de taxation dans des services de donnees par paquets et fonctionnement correspondant
CN101183956A (zh) 智能网在线计费交互系统及方法
CN100401675C (zh) 一种计费信息的处理方法
CN100546248C (zh) 一种实现分组数据业务计费及控制业务接入的方法
CN100438412C (zh) 一种对计费键进行处理的方法
WO2006015543A1 (fr) Procede de traitement d'une re-autorisation, evenement de re-autorisation et declencheurs d'evenement
CN100397821C (zh) 一种基于分组数据流计费中的处理方法
WO2006060964A1 (fr) Systeme et procede de traitement permettant une facturation en fonction du flux de paquets de donnees
WO2012041148A1 (fr) Procédé et système de contrôle d'utilisation du volume de ressources
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 KN KP KR KZ LC LK LR LS LT LU LV LY 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): BW GH 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
122 Ep: pct application non-entry in european phase

Ref document number: 05808226

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载